Privacy Policy

Effective October 30, 2026

Relegait is provided by Levet Technologies, LLC ("we", "us"), based in Baltimore, Maryland. This policy explains what information we collect when you use the Relegait app and this website (together, the "Service"), how we use it, and the choices you have. Questions? Email support@relegait.com.

Information we collect

• Account information: your name, email address and profile picture, which we receive when you sign in with Google.
• Gmail data: with your permission, we read your email and, when you approve, send replies on your behalf. We store copies of email content so the Service can work.
• Google Calendar data: with your permission, we read your calendar and, when you approve, create and edit events. We store copies of calendar data so the Service can work.
• Microsoft data: if you connect Outlook, Microsoft Calendar, Microsoft To Do or Teams, your mail, calendar events, tasks and chat messages, as described in "Connected services".
• Fathom data: if you connect Fathom, your meeting summaries, action items and transcripts.
• Slack data: if you connect Slack, your workspace and user identifiers and the messages exchanged with Relegait there. See "Connected services".
• Sign-in tokens: the tokens Google, Microsoft and Slack give us so the Service can access your accounts. We store them encrypted.
• Derived data: summaries, tags, to-dos, notes, preferences and chat history the Service creates for you.
• Payment information: if you subscribe, payments are handled by Stripe. We do not store your full card number.
• Technical logs: we do not log the full content of your messages. Logs may include limited details such as email subjects and task names, along with identifiers, timestamps and error information, so we can run and fix the Service.

How we use your information

• To provide the features you ask for: reading and sorting messages, summarizing, drafting replies, managing to-dos and your calendar, and checking in with you about them.
• To keep the Service secure, fix problems and provide support.
• To process payments, if you subscribe.

We do not sell your data. We do not use your Google data for advertising.

Connected services

Each service you connect is described below: what we access, why, what we store, and how to disconnect.

Google (Gmail and Google Calendar)

• What we access: your Google profile (name, email, picture), your Gmail messages, and your Google Calendar events, with your permission.
• Why: to sort and summarize your email, find to-dos, draft replies, plan your day, and suggest events. We send a reply or change your calendar only after you approve.
• What we store: copies of email and calendar content, derived data such as summaries and to-dos, and encrypted sign-in tokens.
• How to disconnect: use the delete button in the app, or remove access at myaccount.google.com/permissions.

In particular:

• We use Google user data only to provide and improve the user-facing features you see in the Service.
• We do not use Google user data to develop, improve or train generalized AI or machine-learning models.
• We do not allow people at our company to read your Google data unless you give us permission for specific messages, it is needed for security or to follow the law, or the data has been aggregated and anonymized.
• We do not transfer Google user data to others except as needed to provide the Service (see "Who we share data with"), to follow the law, or as part of a merger or sale of the business.

Slack

• What we access: with your permission, the Slack workspace you connect: your channels, private channels, direct messages and group messages and their message history, plus member names and email addresses.
• Why: to show your Slack messages alongside your email, sort and summarize them, and find to-dos. We post a message as you, or mark a conversation as read, only when you ask or approve.
• What we store: your Slack workspace and user identifiers, copies of message content so the Service can work, derived data such as summaries and to-dos, and the encrypted access token Slack gives us.
• How to disconnect: disconnect Slack in the app, or remove Relegait from your workspace's installed apps in Slack. Use the delete button in the app to delete the stored data.

Microsoft (Outlook, Microsoft Calendar, Microsoft To Do and Teams)

• What we access: with your permission, your Microsoft profile and email address; for Outlook, your mail (read, send and manage); your Outlook calendar (read and write); optionally your Microsoft To Do tasks; and for Teams, your chat messages. For work or school accounts, reading Teams channel messages also requires your organization's administrator to approve.
• Why: to show your Outlook mail and Teams messages alongside your other inboxes, sort and summarize them, find to-dos, and plan your day. We send a reply, change your calendar or tasks, or post a message only when you ask or approve.
• What we store: copies of mail, calendar and message content so the Service can work, derived data such as summaries and to-dos, and encrypted sign-in tokens.
• How to disconnect: disconnect the account in the app, or remove Relegait at account.microsoft.com/privacy/app-access (work or school accounts: myapps.microsoft.com). Use the delete button in the app to delete the stored data.

Fathom

• What we access: when you paste your Fathom API key, your meeting recordings' details, summaries, action items and transcripts, and the email of the person who recorded them.
• Why: to show meeting summaries alongside your other messages and turn action items into to-dos.
• What we store: your API key (encrypted), copies of meeting summaries and action items, and derived data such as to-dos. Transcripts are read when you open a meeting. We also register a webhook in Fathom so new meetings arrive when they are ready.
• How to disconnect: disconnect Fathom in the app, which removes the webhook and stored key, or delete the API key in Fathom's settings. Use the delete button in the app to delete the stored data.

Who we share data with

We share data only with service providers that help us run the Service:

• AI providers (Anthropic and OpenAI): to generate summaries, tags, drafts and answers, the Service sends the relevant message or calendar text to Anthropic (Claude) and/or OpenAI. We use their API services, which by default do not use API data to train their models. Their handling of data is described in their own policies and terms.
• Hosting and infrastructure (Railway, Cloudflare): the Service and its data are hosted on Railway. Cloudflare provides DNS and serves this website.
• Payments (Stripe): to process subscription payments.

We may also disclose information if required by law.

Retention and deletion

The Service has a delete button that lets you delete your stored data. When you do, we also revoke the Google, Microsoft and Slack access tokens we hold, and remove your Fathom key. Your data is fully removed within 90 days. You can also email support@relegait.com to request deletion.

You can withdraw the Service's access to your Google account at any time at myaccount.google.com/permissions.

Security

We encrypt sign-in tokens and take reasonable steps to protect your information. No method of storage or transmission is completely secure, so we cannot guarantee absolute security.

Children

The Service is for people 18 and older. We do not knowingly collect information from anyone under 18.

Changes to this policy

We may update this policy. When we do, we will change the effective date above, and for significant changes we will notify you through the Service or by email.

Contact

Levet Technologies, LLC, Baltimore, Maryland
support@relegait.com