Privacy Policy

To keep your day current on every Mac, the Oh Snaps servers connect to the services you link — Google Calendar, Outlook, Linear, GitHub and Slack — hold the sign-in tokens for them, and keep a copy of the events, issues and tasks they read. Tokens and synced data are encrypted at rest. Our servers can read this data, because reading it is how they keep your devices up to date.

When you use Snaps, the parts of that data it needs — the events, tasks, issues and messages relevant to your brief, your inbox or your question — are sent to Anthropic's Claude to do the work. Anthropic does not use them to train its models.

We do not sell your data, we do not show advertising, and we do not use your content to train machine learning models.

Account details. Your email address, and your name and profile picture if your identity provider supplies them. Passwords are never stored by us; sign-in is handled by Auth0, and we hold only an identifier for your account there.

Connected accounts and their tokens. For each service you connect, the account's identifier (usually its email address or username) and the OAuth tokens that let us act on your behalf. Tokens are encrypted with AES-256-GCM using a key held by our servers, and each is used only with the service it belongs to. Your Macs are given short-lived access tokens when they need to make a change, such as creating an event or sending a Slack reply you approved.

Calendar events, issues and tasks. Our servers read your events from Google Calendar and Outlook and your issues and pull requests from Linear and GitHub, and keep a copy — titles, times, locations, descriptions, attendees and meeting links — so every Mac shows the same day. We hold events from the past 90 days and the next 180.

Synced records. Your tasks, notes on tasks, and app settings are delivered to your Macs from a sync store where each record is encrypted with AES-256-GCM using a key held by our servers.

What Snaps writes. Your morning brief, the short notes in Needs you (“Sam asked about the migration”), your conversations with Snaps, and the changes it drafts for you are stored so they are the same on every Mac. Each is encrypted with AES-256-GCM before it is written. Slack messages themselves are not stored — see below.

Change notifications. Google, Microsoft, Linear and Slack notify our servers when something you connected changes, so it reaches your Macs within seconds. For Slack this is a notice that you reacted to a message or were mentioned; the notice is not stored.

Billing. Oh Snaps is free while in beta. If you subscribe to a paid plan once they exist, Stripe handles payment: your card details go to Stripe, never to us, and we keep only your plan, its status and Stripe's identifier for your customer record.

Operational records. The minimum needed to run the service: session and refresh tokens for your Macs, when your account was created and last seen, how many requests Snaps has made for you (to keep usage within limits), and server logs that may include IP addresses for a limited period.

Snaps is the assistant inside Oh Snaps. It writes your morning brief, sorts what came in into what it handled and what needs you, and answers when you ask it something. To do that it runs on Anthropic's Claude, through Anthropic's API.

What is sent. For each request, only what it needs: the events, tasks, Linear and GitHub items, Slack messages and free/busy times relevant to your brief, your inbox or your question, and what you type to Snaps. Snaps reads this on our servers from what we already hold, plus live calls to Slack and to Google free/busy.

How Anthropic handles it. Anthropic processes this data to answer the request on our behalf, under its commercial terms. It does not use data sent through its API to train its models, and keeps it only for a limited period for safety and abuse monitoring.

Snaps never acts alone. Snaps does not write to Google, Microsoft, Slack or Linear itself; every change it suggests is carried out by your Mac. Changes that only affect your own calendar or tasks are applied with Undo; anything another person would see — a reply, an RSVP, an invitation, a change in Linear — waits for your Accept.

Your contacts and your organization's directory are read by the app on your Mac directly from Google, to suggest guests and show the names and photos of people in your meetings; they never reach our servers. The layout and preferences of the app sync through the encrypted records above. Crash reports are sent to Sentry without personal information or the contents of your calendar.

Oh Snaps asks Google for access to read your calendars and create, change and answer events (calendar.readonly and calendar.events), so it can show your day, open meeting links in the account that was invited, place tasks on your calendar, and carry out the changes you approve. It asks for your basic profile and email address (openid, email, profile) so it can tell your accounts apart.

It also asks for read-only access to your Google Contacts, your “Other contacts” and, for Google Workspace accounts, your organization's directory. The app on your Mac uses these only to suggest people as you type a guest's name, and to show the names and photos of the people invited to your meetings. It reads only names, email addresses and profile photos.

When you find a time with someone, Oh Snaps asks Google for their free/busy times — when they are busy, never what they are doing.

Oh Snaps' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, we do not sell it, and we do not use it — nor allow it to be used — to develop, improve or train generalized AI or machine learning models.

How we share, transfer or disclose Google user data. Your calendar events, free/busy times, and the name, email address and profile picture of your Google account are shared, transferred or disclosed only in these cases:

• Your own devices, over an encrypted connection: the Macs you sign in on with your Oh Snaps account.
• Railway, our hosting provider, which runs the servers and database where this data is stored, encrypted. Railway processes it only to host our service.
• Anthropic, when you use Snaps: the events and free/busy times relevant to a request are sent to Anthropic's Claude to write your brief, sort your inbox or answer you — a feature you see and use. Anthropic processes them only to answer the request and does not use them to train models.
• Google itself, when you ask Oh Snaps to create, move, answer or cancel an event.
• When the law requires it, such as a valid court order, or to protect against fraud or abuse of the service.
• In a merger, acquisition or sale of Oh Snaps, where the data would pass to the successor under the same commitments as this policy, and we would tell you beforehand.

Google user data is not shared with Auth0, Resend, Sentry, Stripe or Vercel, with other Oh Snaps users, or with any advertiser, data broker or analytics service. Contacts and directory data is not shared, transferred or disclosed to anyone, including Railway and Anthropic: it travels only between Google and your Mac. The only exception is when you add someone as a guest, which sends their email address to Google Calendar as part of the event you create.

Data protection mechanisms for Google user data. We treat all Google user data as sensitive: it travels only over HTTPS/TLS; OAuth tokens and the events we hold are encrypted with AES-256-GCM before they are written, with keys kept apart from the database; refresh tokens never leave our servers; contacts stay on your Mac, in a cache inside the app's sandboxed container that is refreshed weekly; and only the Oh Snaps operator can reach production systems, through accounts protected by multi-factor authentication. More in How we protect your data.

You can disconnect a Google account in Oh Snaps at any time — which deletes its tokens and the events we hold for it — or revoke access from your Google account permissions page.

When you connect an Outlook.com or Microsoft 365 account, Oh Snaps asks for permission to read and write your calendars (Calendars.ReadWrite), keep access while you are away (offline_access), and read your basic profile and email address (User.Read). We use it to show your day, answer invitations, create, move and cancel the events you ask for, and — when you use Snaps — to send the relevant events to Anthropic as described above. Nothing else.

Disconnecting the account in Oh Snaps deletes its tokens and the events we hold for it. To remove Oh Snaps from your account's permissions as well, visit your Microsoft account app permissions (for a work or school account, your organization's My Apps page).

Linear (read and write): issues assigned to you, in the teams and columns you choose, appear as tasks. Checking one off moves it to your team's completed state; Snaps can suggest changes to state, priority, estimate and due date, which your Mac makes once you accept.

GitHub (read:user, user:email, repo): issues and pull requests assigned to you, and reviews requested of you, appear as tasks. GitHub has no read-only permission that reaches private repositories, so the repo scope is requested; Oh Snaps only reads with it.

Slack (user permissions only — Oh Snaps acts as you, never as a bot): messages you react to become tasks, and Snaps searches for messages that mention you or were sent to you directly (search:read) so it can sort them. These are read live when needed and are not stored; only the short note Snaps writes about one, and any reply it drafts, is kept, encrypted. Replies you approve are sent as you (chat:write), into the conversation or a direct message (im:write), now or at a time you choose.

We use a small number of providers to run the service. Each receives only what it needs:

• Railway hosts our servers and database.
• Anthropic runs Claude, the model behind Snaps, as described above.
• Auth0 handles sign-in.
• Resend sends transactional email, such as sign-in and account messages.
• Sentry receives crash reports from the Mac app, without personal information.
• Stripe processes payments, if and when you subscribe.
• Vercel hosts this website.

The services you connect — Google, Microsoft, Linear, GitHub and Slack — receive the requests made on your behalf and nothing else. We never sell your data or share it for advertising. Oh Snaps is not affiliated with, endorsed by, or sponsored by Google, Microsoft, Linear, GitHub, Slack, Zoom, Cisco or Anthropic.

• Encryption in transit. Every connection between the app, our servers, our database and the services you connect uses HTTPS/TLS.
• Encryption at rest. OAuth tokens, synced records and everything Snaps writes are encrypted with AES-256-GCM before they are written to the database, each sealed to your account so it cannot be read as anyone else's. The keys are kept in our server's protected configuration, apart from the database, so a copy of the database alone cannot be read.
• Tokens stay on the server. Long-lived refresh tokens never leave our servers. Your Macs get only short-lived access tokens, and only when they need to make a change.
• Limited access. Only the Oh Snaps operator can access production systems, through accounts protected by multi-factor authentication. Nobody reads your data unless you ask us to (for example, to help with a support request), it is needed to investigate security or abuse, or the law requires it.
• Least privilege. We request only the permissions each feature needs, use each token only with the service it came from, and send Anthropic only what a request needs.

If we learn of a breach that affects your data, we will tell you without undue delay.

Synced records and what Snaps writes are kept while your account exists, so your history is the same on every Mac. Calendar events that ended more than 90 days ago are removed automatically. When you delete a record, or disconnect a service, it is replaced with a marker so the deletion reaches your other Macs, and the marker is cleared after 30 days. Disconnecting a service deletes its tokens and the events and items we held for it.

You can ask us to delete your account and everything attached to it — connections, synced records and everything Snaps wrote — by emailing hello@ohsnaps.app from the address you signed up with. We will confirm once it is done. Anthropic keeps what Snaps sent it only for the limited period described above.

• Connect only the services you want; disconnect any of them at any time.
• Ignore anything Snaps brings up, so it won't again, or decline any change it suggests.
• Turn off automatic update checks, and see diagnostics, in Settings.
• Ask us for a copy of your data, to correct it, or to delete it, at hello@ohsnaps.app. Wherever you live, we'll honour these requests.

ohsnaps.app uses no cookies, no analytics and no tracking. Your light or dark choice is saved in your browser's local storage and never sent to us. Vercel, which hosts the site, keeps standard server logs, which may include IP addresses, for a limited period.

Oh Snaps is not directed at children under 13, and we do not knowingly collect information from them.

If this policy changes in a way that materially affects how your data is handled, we will update the date at the top of this page and, where the change is significant, tell you in the app or by email.

Questions about any of this go to hello@ohsnaps.app. See also our Terms of Service.