Your data in Oatmeal.
A clear view of what stays on your device and what leaves when you choose a connected feature.
This marketing website
This site shows the real macOS app with demo content, plan information, and links to configured destinations. It does not import your notes, activate licenses, or run managed ingestion. This site includes no analytics or advertising trackers, and its fonts are served locally. The hosting provider may process normal request data, such as IP addresses and browser information.
Your local workspace
Imported notes and transcripts power local search, recurring-term themes, graph, timeline, citations, and report preparation. The macOS app reads selected local folders and saves a local parse cache. Oatmeal does not modify imported originals when exploring them.
Local analysis does not require managed ingestion. Removing a local source does not delete its original from the service it came from.
Native recording and local transcription
You can start a native recorder preview using microphone audio on macOS 12 or later and system audio on macOS 13 or later. macOS asks for the applicable microphone, Speech and screen/system-audio permissions. System capture stores audio only, without video frames.
Transcription runs on this Mac, without a cloud transcription fallback. Language availability, interruptions and overlapping voices can leave partial text. If transcription is unavailable, the local audio remains available for recovery. Microphone and system labels identify audio channels, not people or complete attendance.
Audio, drafts and recovery files remain in this Mac’s private app storage until you manage them. After stopping, use Show local audio to find retained recordings. Saving places only reviewed text and metadata into the selected library through its private-conversation rules; the recorder does not copy audio into a shared library. A shared library can expose the saved text to its other members. Optional classification or connected chat can send selected text to their providers as described below.
Google Calendar and Meet connections · Coming soon
When you connect Google Calendar or Meet in the desktop app, Oatmeal asks you to sign in with Google and give consent. Calendar requests read-only event and calendar-list access to show calendar choices and upcoming events, offer reminders while Oatmeal runs, and prepare a call draft. It uses calendar names and time zones, event titles and times, meeting links, and invitee names, email addresses and response status. You choose which calendars to show. Invitees are suggestions, not proof of attendance. Joining a meeting does not start recording.
Meet imports existing transcript text, conference dates and identifiers, and participant metadata used for speaker labels. It uses Google’s read-only meeting-space permission, which is broader than transcript-only access; Oatmeal’s connector does not download audio or video recordings, join calls, or start capture. Available transcripts depend on your Google account’s access and Google’s transcript availability.
Calendar and Meet refresh tokens are stored separately in this Mac’s Keychain, outside transcript files and browser storage. Calendar choices are stored with the Calendar connection; upcoming events and reminder state are cached in memory. Disconnecting Calendar removes its local credentials, choices, cached events and reminders. Forgetting the Meet connection removes its local credentials. These actions leave the other connection and saved library content in place. To revoke Google-side access, use your Google Account connections; revoking an app grant can affect both connections.
Imported transcripts and any saved call context remain in your chosen local workspace until you remove them. Disconnecting does not delete saved copies, backups, or originals in Google. Review saved text, attendance and the destination before sharing; a shared library can expose saved content to its members. Connecting Google or joining an event does not itself send content to an AI provider. If you explicitly choose a connected AI feature after reviewing the content, chosen text and context may be sent for classification or chat as described below. Review the provider’s data-handling policies before using that feature; this is not a promise of third-party zero retention.
Oatmeal’s use and transfer of Google data will comply with the Google API Services User Data Policy and the Google Workspace Limited Use requirements.
Managed ingestion
When you use managed ingestion, Oatmeal sends selected document text, title, classification choices, team names or aliases, and profile name over HTTPS through Oatmeal’s hosted service to TypeSafe’s Jev model, directly or through OpenRouter depending on service configuration, for category, audience, document type and one-on-one classification. This is remote processing, not on-device inference. Classification does not transcribe audio or generate chat answers. Review the provider’s data-handling policies before sending confidential information.
The broker is designed not to persist raw document text or log request bodies. It stores keyed fingerprints, classification results, usage records, seat and subscription identifiers, and hashed email and device bindings to enforce quotas and licensing. Hosting and AI providers have their own data-handling and retention policies. This is not a zero-retention guarantee.
Failed provider requests and technical retries do not consume a second document allowance. A completed result flagged for review still counts. Existing local sources stay available when your allowance runs out.
Usage and activity
The hosted service keeps operational usage records to enforce document allowances and show ingestion attempts, results and available provider costs. Costs may be reported, estimated or unknown; missing cost information is not treated as free usage. These records do not contain your document text or recorded audio.
The desktop activity option is off by default. If you enable it, Oatmeal sends cumulative counts of supported functions, such as imports, ingestion, chat and recording actions, associated with your active access. It does not send document names, transcript text, audio, calendar details or chat messages as activity data. Turning it off stops future activity reporting; it does not erase previously received records. This reporting is separate from the operational records needed for licensing and document allowances. Detailed activity is retained for up to 90 days and limited usage aggregates for up to 13 months.
Email and license activation
Each paid seat has a unique Oatmeal license key. Activation checks the assigned employee email using a time-limited email code, and binds the seat to one active device. Resend delivers email verification codes and receives the destination address and verification message. Lemon Squeezy is the integrated billing provider. Live purchases are currently closed. Lemon Squeezy receives checkout and payment information, and Oatmeal checks subscription status and purchased seat quantity.
In the desktop app, managed license credentials and the random installation secret use macOS Keychain. They are not saved in transcript files, shared workspace settings, or browser local storage. Paid seat activation is desktop-only. The gated website account page verifies your email to manage checkout, billing and employee seat assignments; its short-lived sign-in session stays in tab memory and is lost on reload. It does not store or activate a managed license. Only a verified billing owner can open the Lemon Squeezy billing portal.
Chat and other connections
Asking a question through a connected AI provider sends the bounded evidence packet and recent same-scope chat context to that provider. Its account, costs, and data handling are separate. Source connectors use the credentials and permissions you configure to fetch available notes or transcripts. Fathom and Fireflies connections fetch transcript text rather than recordings; their keys stay in this Mac’s Keychain. Copying evidence to another assistant is a separate action.
Oatmeal does not join as a meeting bot. Review the original evidence and your selected providers’ policies before sending confidential information.