Privacy Policy

Last updated: September 16, 2026

What Patina is

Patina is a Mac app that helps you stay organized by connecting to your calendar, email, and messages. It gives you daily briefings, keeps notes on the people in your life, and tracks your goals.

Data we collect

Patina stores your data locally on your device. When you connect Google Calendar or Gmail, we request read-only access to your calendar events and email. This data is used solely to provide you with summaries and context inside the app.

How we use Google data

Patina accesses Google Calendar and Gmail with the following permissions:

• calendar.readonly — Read your calendar events to show your schedule
• gmail.readonly — Read your email to surface relevant messages in briefings
• contacts.readonly — Match the people you reference to their email addresses
• directory.readonly — Resolve names of people in your organization directory
• email, profile — Identify your Google account

Patina's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• We only use Google user data to provide and improve the user-facing features (briefings, context, and search) that requested the data.
• We do not transfer Google user data to others except as needed to provide those features, to comply with applicable law, or as part of a merger or acquisition with user notice.
• We do not use Google user data for serving advertisements.
• We do not allow humans to read Google user data unless we have your explicit consent for specific messages, it is necessary for security or to comply with applicable law, or the data has been aggregated and anonymized.

Data storage

Your files are stored locally on your Mac in a folder you choose. If you opt into GitHub sync, your data is pushed to a private repository only you control. Google OAuth tokens are held server-side encrypted at rest in Cloudflare Workers KV (AES-GCM) so both Mac and iPhone can read the same account. Most MCP service tokens and your Patina sign-in token stay in the device Keychain. Granola credentials can be stored encrypted in the cloud so chat and feed updates share the same connection.

Cloud feed updates

To provide feed updates while your devices sleep, Patina stores an encrypted cloud copy of selected context, including calendar events, to-dos, and excerpts from recent people, project, meeting, and digest files. Connected calendar, email, meeting, and weather sources may supply additional context for these updates. Relevant context is sent to the AI provider to generate feed cards. A copy of your cards is also saved in your Patina folder.

Data sharing

We do not sell your personal data. Patina sends data to third-party services only to operate features you choose: connected account APIs such as Google, GitHub, Beeper, and MCP services; sync destinations you configure; and the AI provider selected in Settings or included with your plan.

AI requests may be routed to Anthropic for Claude or Claude Code, Google Gemini for Patina AI subscription and worker-backed features, OpenAI for OpenAI API key usage and lightweight title generation, or OpenRouter when you configure it. Those requests may include your message, attachments, conversation history, and relevant app context such as calendar events, emails, files, notes, or connected-account snippets needed to answer the request. Patina does not use your data to train its own models.

Data retention

Local files remain in your Patina folder until you delete them. Local context uploaded for the feed expires after 48 hours, and cloud feed cards are retained for 30 days. Disconnecting Google immediately revokes Patina's access at Google and deletes the stored credentials from our servers. Disconnecting any other service removes its stored credentials. Uninstalling the app does not delete files in your Patina folder or iCloud, or immediately remove cloud records subject to these retention periods.

Security

Server-held Google OAuth tokens, Granola credentials, and stored feed content are encrypted at rest with AES-GCM. Device-held tokens live in the macOS or iOS Keychain. All API communication uses HTTPS. The app uses hardened runtime and is notarized by Apple.

Contact

Questions about this policy? Email gabe@valdivia.works.