Tidy

Tidy Privacy Policy

DRAFT — not reviewed by counsel. Values in [TBD: …] must be filled in before publishing.

Effective date: [TBD: effective date] Last updated: [TBD: date]

This Privacy Policy explains how [TBD: legal company name] ("Tidy", "we", "us") collects, uses, stores, shares, and deletes information when you use the Tidy desktop app for macOS, the Tidy backend service, and the website at https://tidy.fyi (together, the "Service").

Tidy collects messages and events from the accounts you connect (such as Gmail, Google Calendar, and Slack) into one inbox on your Mac, helps you turn them into tasks, and lets you reply, archive, and schedule from one place. Some features use AI assistants that you sign into yourself.

1. Information we collect

1.1 Account information

  • When you sign in with Google, we receive your Google account email address, name, and profile picture (OpenID Connect scopes openid, email, profile). We use these to create and identify your Tidy account.
  • Sign-in uses Supabase Auth. Your sign-in session is stored in the macOS Keychain on your Mac.

1.2 Google user data

Connecting Gmail or Google Calendar is a separate step from signing in. You choose which services to connect, and some permissions are optional and requested only when you use the feature that needs them.

Google permission What Tidy does with it When it is requested
gmail.modify Read your messages (headers, body, labels, attachment metadata) to show them in your Tidy inbox; mark messages read or unread, archive, and apply labels when you ask; create, edit, and send drafts and replies you write or approve; download attachments when you open them; unsubscribe from mailing lists when you ask. Tidy does not permanently delete your email. When you connect Gmail
calendar.calendarlist.readonly, calendar.events.readonly Show your calendars and events in Tidy. When you connect Google Calendar
calendar.events.owned Create, edit, move, and delete events on calendars you own when you ask. Optional, when you connect Calendar or later
calendar.events.freebusy Check guests' free/busy times when you schedule a meeting. Optional, with calendar write access
contacts.readonly, contacts.other.readonly, directory.readonly Suggest guests' names and email addresses while you add guests to an event. Optional, only when you turn on guest suggestions

Google user data we store:

  • Gmail: message headers (sender, recipients, cc, bcc, reply-to, subject, message IDs), snippet, message body (text and HTML), labels, thread and draft information, read/sent status, and attachment metadata (file name, type, size). We do not store attachment files on our servers; they are fetched from Google when you open them. When you first connect, Tidy imports the last 7 days of mail and then keeps up with new mail.
  • Google Calendar: calendar names, descriptions and time zones; event title, description, location, start and end time, organizer, conference link, and attendees (email, name, response).
  • Google Contacts: contact names and email addresses are fetched from Google when you use guest suggestions and cached only on your Mac. They are not stored on our servers.
  • OAuth tokens: the access and refresh tokens Google issues to Tidy are stored on our servers encrypted with AES-256-GCM, using keys kept in Google Cloud Secret Manager.

1.3 Other connected services

  • Slack: if you connect Slack, we access and store the channels, direct messages, and group messages you can see, along with users, files metadata, and reactions, so they appear in your Tidy inbox and you can reply from Tidy. Slack tokens are stored encrypted. Images you send to Slack from Tidy are briefly stored in Google Cloud Storage and deleted automatically within 1 day.
  • KakaoTalk (optional): Tidy can read the KakaoTalk app's data on your Mac, or connect directly to Kakao with your KakaoTalk credentials. Your KakaoTalk password is not stored; sign-in tokens are kept in the macOS Keychain. KakaoTalk messages stay on your Mac and are not sent to our servers.
  • Apple Messages, macOS Contacts, and macOS Notification Center (optional): with your macOS permission, Tidy reads these locally on your Mac. This data stays on your Mac and is not sent to our servers.
  • Sender logos: to show sender logos, your Mac may look up public DNS records and website icons of the domains that send you email.

1.4 Information you create in Tidy

Tasks, notes, tags, settings, and drafts you create in Tidy. [TBD: confirm which task and settings data is synced to our servers versus kept only on your Mac.]

1.5 Usage data and crash reports

  • If analytics is on, Tidy sends product usage events (for example: app opened, signed in, integration connected, task created or completed, reply sent) to PostHog. Events are linked to your Tidy user ID. They do not include message content, email addresses, or message or task text. Automatic click capture and session recording are off. PostHog discards IP addresses but may derive approximate location (such as city or region) from them.
  • If crash reports are on, Tidy sends error and crash details to PostHog. Before sending, Tidy removes home-folder paths, email addresses, and tokens, and shortens long text.
  • Analytics and crash reports are turned on when you sign in, unless you have already chosen otherwise. You can turn either off at any time in Settings. [TBD: confirm this consent approach with counsel — see drafting notes.]
  • Our servers keep operational logs (such as request status and errors) in Google Cloud Logging. Slack-related logs use pseudonymous IDs.

1.6 Voice dictation

Voice dictation runs entirely on your Mac using Apple's on-device speech recognition or a local speech model. Audio is not sent to us or to any third party, and it is not stored.

2. How we use information

We use the information above only to:

  • provide the features you use: show your messages and events in one inbox, let you reply, archive, label, unsubscribe, and schedule, suggest event guests, and create and organize tasks;
  • run AI features you choose to use (see Section 3);
  • keep your account secure, prevent abuse, and fix bugs;
  • understand how the app is used and improve it, using only the usage and crash data described in Section 1.5 (never the content of your Google user data);
  • comply with the law.

We do not sell your information. We do not use your information for advertising.

3. AI features

Tidy's AI features run on your Mac and use AI services that you sign into or configure yourself. Tidy does not run its own AI models and our servers do not send your data to any AI provider.

  • AI assistants (Claude Code, Codex): Tidy's assistant features (such as triage, task suggestions, drafting replies, and agent sessions) call the Claude Code or Codex app installed on your Mac, using your own Anthropic or OpenAI account. When you use these features, the content the assistant needs (for example, a message you are triaging or replying to, or calendar and task details) is sent from your Mac to that provider under your account and the provider's terms and privacy policy.
  • Optional AI analysis with your own API keys: if you enter your own API keys, Tidy can send message content from your Mac to TypeSafe AI (for message analysis) and to OpenAI (for keyword extraction; requests are sent with storage turned off). Your keys are stored in the macOS Keychain.
  • You decide whether to use these features and which provider to connect. You can stop at any time by turning the feature off or removing the provider sign-in or key.

No AI model training. We do not use Google user data, or any other content from your connected accounts, to develop, improve, or train generalized or non-personalized AI or machine-learning models. We do not allow any third party to do so on our behalf. [TBD: confirm the training and retention terms of each provider for the account types users connect — see drafting notes.]

4. Google API Services: Limited Use

Tidy'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:

  • We use Google user data only to provide and improve user-facing features that are visible and prominent in Tidy.
  • We transfer Google user data to others only as necessary to provide or improve those features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to you.
  • We do not use or transfer Google user data for serving ads, including personalized, retargeted, or interest-based advertising.
  • We do not sell Google user data, and we do not use it to determine creditworthiness or for lending purposes.
  • No person reads your Google user data unless you give us permission for specific messages (for example, for support), it is necessary for security purposes such as investigating abuse, it is required to comply with law, or the data is aggregated and anonymized for internal operations.
  • We do not use Google user data to train generalized AI or machine-learning models.

5. Where information is stored

  • Our servers: Tidy's backend runs on Google Cloud in the Seoul region (asia-northeast3). Account data, Google and Slack data, and encrypted tokens are stored in a Supabase PostgreSQL database [TBD: confirm Supabase region — expected Seoul]. Each user's records are protected by row-level access rules so only that user's account can read them.
  • Your Mac: Tidy keeps a local copy of your inbox, calendar, and task data in a local database on your Mac, plus KakaoTalk, Messages, Contacts, and Notification Center data that never leaves your Mac. Sign-in sessions and API keys are stored in the macOS Keychain.
  • Information is encrypted in transit (HTTPS/TLS). [TBD: confirm at-rest encryption statement for the database provider.]
  • PostHog stores analytics and crash data in the United States.

6. Who we share information with

We share information only with the service providers that help us run Tidy, only for the purposes in this policy, or when the law requires it.

Provider Purpose Data
Google Cloud (Cloud Run, Cloud Tasks, Cloud Storage, Secret Manager, Cloud Logging) Hosting the backend, background jobs, temporary file storage, key storage, logs Account data, connected-service data, encrypted tokens, logs
Supabase Database, sign-in, real-time updates Account data, connected-service data, encrypted tokens
PostHog Product analytics and crash reports (only if turned on) Usage events and crash details, linked to your Tidy user ID

AI providers you sign into or configure yourself (Anthropic, OpenAI, TypeSafe AI) receive data directly from your Mac under your own account, as described in Section 3. They are not acting on our behalf. Connected services (Google, Slack, Kakao, Apple) receive the actions you take, such as sending a reply.

We may disclose information if required by law or legal process, to protect the rights and safety of users or others, or as part of a merger or acquisition, with notice to you.

7. How long we keep information

  • We keep your connected-service data and account data while your Tidy account is active, so your inbox and history stay available. [TBD: retention period for data after disconnection and for inactive accounts.]
  • When you disconnect Google entirely in Tidy, we stop syncing, revoke Tidy's access token with Google, stop Gmail and Calendar notifications, and delete your Google OAuth tokens within 24 hours. Messages and events already imported are kept until you ask us to delete them or delete your account (see Section 8). [TBD: decide whether disconnecting should also delete imported data.]
  • Images sent to Slack from Tidy are deleted from temporary storage within 1 day.
  • Data stored only on your Mac stays there until you delete it or uninstall Tidy and remove its app data.
  • [TBD: retention periods for server logs and PostHog data.]

8. Your choices and rights

  • Disconnect a service: disconnect Google or Slack in Tidy's settings at any time. You can also remove Tidy's access to your Google account at https://myaccount.google.com/permissions.
  • Turn off analytics or crash reports: in Tidy's Settings.
  • Delete your data or account: email [TBD: privacy contact email, e.g. privacy@tidy.fyi] from the email address of your Tidy account and ask us to delete your account or specific connected-service data. We will delete the requested data from our servers, including imported Google user data, within [TBD: number] days, and confirm when it is done. [TBD: confirm deletion timeline; there is no in-app account deletion yet.] To remove data stored on your Mac, delete Tidy and its app data folder.
  • Access and correction: you may ask for a copy of your data or ask us to correct it by emailing the address above.
  • Depending on where you live (for example, under the GDPR or Korea's Personal Information Protection Act), you may have additional rights, such as objecting to or restricting processing, and the right to complain to your local data protection authority. [TBD: counsel to confirm required jurisdiction-specific sections, including PIPA items such as a privacy officer and overseas transfer details.]

9. Security

We use encryption in transit, encrypt OAuth tokens with AES-256-GCM, keep encryption keys in a secrets manager, restrict each user's data with access rules, and limit staff access to what is needed to run the Service. No method of transmission or storage is completely secure.

10. Children

Tidy is not intended for children under [TBD: age, e.g. 14 or 16], and we do not knowingly collect their information.

11. Changes to this policy

We may update this policy. If we make material changes, we will notify you in the app or by email before they take effect. [TBD: notice period.]

12. Contact

[TBD: legal company name] [TBD: address] Email: [TBD: privacy contact email] Website: https://tidy.fyi

PrivacyTerms© 2026 Tidy