Briefly AI

Privacy Policy

Effective date: July 10, 2026

Briefly AI ("Briefly", "we", "us") turns your connected work accounts into read-only daily briefings. This policy explains what data we access, how we use and store it, and how you can delete it. The short version: we only read, we never send or modify anything, we don't sell data, and we don't show ads.

1. Information we collect

Account information. When you sign in with Google we receive your name, email address, and profile photo to create and identify your Briefly account.

Connected source data. When you explicitly connect a source, we access it in read-only mode:

  • Gmail (scope gmail.readonly): email messages and metadata (senders, subjects, snippets, labels, timestamps) needed to build your briefing.
  • Google Calendar (scope calendar.readonly): events, times, attendees, and titles for the periods your briefing covers.
  • Slack: messages, mentions, and threads from workspaces you connect, via Slack's read-oriented APIs.

Content you create. Automation prompts, schedules, and follow-up chat messages you write inside a briefing.

Technical data. Basic logs (timestamps, request status, error messages) needed to operate the service. We do not use advertising trackers or sell analytics data.

2. How we use your data

We use the data above for exactly one purpose: producing the briefings you ask for.

  • When an automation runs (on your schedule or manually), we fetch recent items from the sources you selected and generate a structured briefing.
  • The fetched items and the briefing are saved with that run so you can re-read it and ask follow-up questions grounded in the same data.
  • All access is read-only. Briefly never sends, replies, deletes, archives, schedules, or modifies anything in your email, calendar, or Slack.

We do not use your data for advertising, do not sell it, and do not use it to train our own or third-party generalized AI or machine learning models.

3. Google user data and Limited Use

Briefly's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

  • Google user data is used only to provide the user-facing briefing features described in this policy.
  • We do not transfer Google user data to third parties except as necessary to provide the service (see section 5), to comply with applicable law, or as part of a merger or acquisition with prior notice to you.
  • We do not use Google user data for advertising, and we do not allow humans to read it, except (a) with your affirmative agreement, (b) as necessary for security purposes such as abuse investigation, (c) to comply with applicable law, or (d) when the data is aggregated and anonymized for internal operations.
  • We do not use Google Workspace data to develop, improve, or train generalized AI or machine learning models.

4. AI processing

To generate a briefing or answer a follow-up question, the fetched source items are sent to our AI provider, Anthropic, via its Claude API. Anthropic processes this data solely to return the requested output and, under its commercial API terms, does not use it to train its models. No other AI provider receives your data.

5. Storage, security, and sharing

  • OAuth access and refresh tokens are encrypted at rest with AES-256-GCM. Data in transit uses TLS.
  • Briefings and the source items used to ground them are stored in our database, associated with your account, until you delete them.
  • We share data only with the infrastructure providers required to run the service: our hosting provider, our database provider, and Anthropic (AI processing). Each processes data only on our instructions. We never sell your data.
  • We may disclose data if required by law, or to protect the rights, safety, and security of Briefly and its users.

6. Data retention and deletion

  • Disconnect a source:removing an integration on the Integrations page immediately deletes its stored OAuth tokens. You can also revoke Briefly's access at any time from your Google Account permissions page.
  • Delete an automation: deleting an automation permanently deletes all of its runs, briefings, stored source items, and chat messages.
  • Delete your account: email mhshifat757@gmail.com from your account address and we will delete your account and all associated data within 30 days.

7. Children

Briefly is a professional tool and is not directed at children under 16. We do not knowingly collect data from children.

8. Changes to this policy

If we make material changes, we will update the effective date above and, where the change affects how we handle Google user data, notify you by email before it takes effect.

9. Contact

Questions or requests about your data: mhshifat757@gmail.com.