Privacy Policy

Breve turns your social feeds into a daily edition. It reads them in one of two ways:

• On the web, a Chrome extension reads your feed inside your own browser, using the logins you already have. Our servers never see your social media passwords, cookies, or session tokens.
• In the iPhone app, you log in to X on x.com itself, inside the app, so Breve never sees your password. X gives the app a login session. Breve keeps that session, encrypted, so it can read your feed from its servers on the schedule you set, even when your phone is off. How it's protected, and how to end it, is below under Connected accounts.

The data Breve collects is yours. You can delete it at any time, and we never sell it.

Post content and basic public metadata (text, author handles, engagement counts, timestamps, links) from the home feed you'd see if you were scrolling yourself. In the iPhone app, that's your X "For You" timeline.

We do not capture your direct messages, drafts, notifications, follower lists, account settings, or anything outside the post feed.

When you connect X in the app, Breve stores:

• The login session x.com issues to the app: the cookies that keep you signed in to X. Not your password, which you type into x.com, never into Breve.
• Your X handle, so you can see which account is connected.

How it's protected.

• The session travels from the app to Breve over an encrypted connection and is encrypted the moment it arrives, with its own 256-bit key (AES-256-GCM). That key is itself encrypted by a master key held in Google Cloud Key Management Service, which never leaves Google's hardware.
• Our database only ever holds the session in encrypted form.
• It is decrypted only in memory, by Breve's collection service, for the minute or so it takes to read your feed.
• Use of the master key is limited to that service and to Breve's cloud administrators, and it is never used to open a session for any other purpose.

What it's used for: reading the posts in your For You timeline, when you brew an edition or before a scheduled one. Nothing else.

What it's never used for: posting, liking, reposting, following, or messaging as you; opening your direct messages; or changing anything in your account.

Ending it: disconnect X from Profile in the app, and the stored session is erased right away. Deleting your Breve account erases it too. You can also end it from X's side at any time: logging out of that session in X's settings makes it useless immediately.

• Your email address and display name (and the standard Google profile fields if you sign in with Google).
• Your edition preferences: topics, format, and send schedule.
• The editions Breve has made for you, so you can revisit them.
• When you agreed to this policy, and which version.
• If you turn on notifications in the app, a device token so we can send them.

• Standard web server logs (IP address, browser or app type, timestamps) for security and abuse prevention.
• Crash reports when something breaks, so we can fix it.

• Make your editions from the posts and preferences you've given us.
• Read your connected feed on your schedule (iPhone app), shortly before each scheduled edition.
• Send your scheduled editions to the email on your account.
• Show your past editions in the app and on the web.

Breve uses a small set of third-party services to operate. Each sees only what it needs to do its job:

• An authentication provider: your email, name, and login activity.
• A large language model provider: post text and your preferences, to write the edition. Under their commercial terms, your inputs are not used to train their models.
• An email delivery service: your email address and the content of your scheduled editions.
• A cloud hosting provider (Google Cloud): stores everything described above, and holds the master key that protects connected sessions.
• An error-reporting service: crash stack traces.

X itself sees your connected account reading its timeline, from Breve's servers, just as it sees any session you're signed in to.

We do not sell your data. We do not share it with advertisers, data brokers, or anyone outside this list.

• See your data. Your profile and past editions are the full view of what we have. In the iPhone app, you can also download a copy of your data from Profile.
• Disconnect X from Profile in the app. The stored session is erased at once.
• Delete individual editions with the Delete button on each one. They sit in Recently Deleted for 30 days, then are permanently removed.
• Unsubscribe from any scheduled edition via the one-click link in its email footer.
• Delete your account from Profile. Your account, editions, connected sessions, and collected posts are removed.

• Collected posts: deleted 30 days after collection. Posts quoted in an edition stay with that edition until you delete it.
• Connected sessions: until you disconnect, reconnect (the old session is erased), or delete your account.
• Editions: until you delete them.
• Account data: until you delete your account.
• Server logs and crash reports: a short window for security and debugging, then purged.

All traffic between you and Breve is encrypted in transit. Every account's data is isolated at the database level, so one user cannot read another's. Connected sessions are also encrypted at rest, as described above. Sign-in is handled by an established third-party provider that manages password hashing, session tokens, and two-factor authentication.

If we make material changes, we'll update the effective date at the top and notify you in your next digest email. The current version always lives at breve.now/privacy.

Questions or concerns: support@breve.now.