Privacy Policy
What stays on your Mac, what is sent to the AI provider, and what you can delete.
Last updated November 7, 2026 · Applies to the KittyYawn app for macOS, kittyyawn.com and the web console. Controller: Zhongli Social LLC, mailing address 2108 N St, Ste N, Sacramento, CA 95816, USA. Privacy contact: support@kittyyawn.com.
Audio stays on your Mac
Your microphone and system audio are transcribed on your Mac. Raw audio is never uploaded. In-memory audio buffers are discarded, and audio used for on-device transcript refinement is deleted after that step completes unless you turn on "keep audio" in Advanced settings, which keeps it on your Mac only.
What text is sent to the AI provider
KittyYawn's live guidance and post-meeting summary work by sending bounded windows of transcript text — not raw audio and not your whole meeting history — to an AI provider. A short live window (a few minutes of recent conversation) is sent to generate in-call guidance; the whole refined transcript is sent once, after the meeting, to generate the summary. Requests can also include short excerpts from your notes, what KittyYawn remembers about attendees from earlier meetings, relevant workspace knowledge, and screen text if you turned on Screen Context. Follow-up drafts, briefs and suggested actions use the same kind of text.
By default this text goes through KittyYawn's own gateway, which does not log or store the content of these requests — only metadata such as ids, route, model, token counts, cost and timing, which is how plan limits are enforced. If you use your own Anthropic API key ("bring your own key"), the same text is sent directly to Anthropic under your own account and its terms.
Anthropic retains API inputs and outputs for a limited period under its commercial terms and does not use them to train models. We have not arranged zero-data-retention.
Subprocessors
- Anthropic — processes transcript text and context to generate live guidance and summaries.
- Cloudflare — hosts the gateway, the website and the download host.
- Supabase — hosts sign-in, your account record and the sync of your meeting records.
- Resend — delivers sign-in codes and account email from mail.kittyyawn.com.
- Stripe and Link — Link (a Stripe service) sells paid plans as merchant of record and processes payments. They receive your name, email, billing address and payment details and use them under Link's and Stripe's own privacy policies, including for tax and fraud prevention.
If you connect a Google or Microsoft calendar, Google or Microsoft provides your events to us under your account with them; see "Calendars" below.
Account and sign-in data
To create an account we store your email address, when the account was created and how you were admitted (invitation, allowlist or open registration). Sign-in uses a one-time 6-digit code emailed to you; our authentication host (Supabase) keeps the usual authentication records (sessions, code requests and their timestamps). We never see a password because there is none. We also store your display name if you set one, which version of the Terms you accepted and when, and whether you turned usage analytics off.
Waitlist / closed registration. If registration is closed when you try to sign up, we keep only your email address, when you first and last tried, and how many times, so we can admit you when there is room. Ask us and we delete it.
Syncing across your devices
Nothing syncs until you turn it on. The first time an account signs in on a Mac, KittyYawn asks whether to sync that Mac. Each account is asked separately. Until you answer, nothing from your meetings is uploaded. You can switch sync on or off at any time in Settings › Account › Sync.
What syncs when sync is on. Each meeting's record: title and calendar title, date and length, attendee names and the email addresses KittyYawn matched to them, your goal and plan for the meeting (including imported context), the summary (decisions, open questions, commitments), your notes, a follow-up draft if you made one, suggested actions and their state, and which items you resolved or dismissed. Your renames and merges of people and companies sync too, as does anything you chose to forget, so a Forget on one Mac applies on all of them.
What never syncs. Audio, transcripts, session logs, screenshots and their text, your voice profile, your talk report (pace and filler-word metrics), and your personal knowledge folder.
Team workspaces. If you're in a team workspace, its knowledge documents and Approved Answers sync with its other members while sync is on. The sync question names those workspaces before anything is uploaded. Using a workspace's knowledge in a meeting never shares that meeting.
Where it's stored. Supabase stores synced data in your account until you delete it. There is no automatic expiry. Turning sync off stops uploads from this Mac; what's already in your account stays until you delete it.
Calendars
Your Mac's Calendar. If you allow it in macOS, KittyYawn reads your Mac's Calendar on your Mac to recognize the meeting you are in and who is attending. That access stays on your Mac; a meeting's calendar title and attendees become part of that meeting's record (see "Syncing across your devices").
Connected Google and Microsoft calendars. You can connect a Google or Microsoft calendar to your KittyYawn account. KittyYawn asks only for read access to calendar events and never creates, changes or deletes them:
- Google:
calendar.events.readonly(events in your primary calendar), plusopenidandemailto identify the account. - Microsoft:
Calendars.Read(your default calendar), plusopenid,email,profileandoffline_access.
What we store. The connected account's email address and provider account id, the scopes you granted, the connection's status and timestamps, and an OAuth refresh token encrypted (AES-256-GCM) with a key held only by our gateway, never by the database. Access tokens are never stored. While a connection is being set up (at most 10 minutes) we hold the pending grant the same way.
What we don't store. Your events. When the app asks, our gateway fetches events for a time window from Google or Microsoft, passes them to your Mac and keeps no copy and no log of their contents. On your Mac they are held only while you are signed in, to match and prepare your meetings.
Disconnecting. Disconnect a calendar in the app's Settings and we delete the connection and its token at once; for Google we also revoke KittyYawn's access at Google (unless the same Google account is still connected in another KittyYawn connection). Microsoft does not let us revoke access for you, so also remove KittyYawn at myapps.microsoft.com (work or school) or account.live.com/consent/Manage (personal). You can revoke access at any time from your Google or Microsoft account; KittyYawn then shows the calendar as needing to be reconnected. Deleting your KittyYawn account deletes every calendar connection and its token.
Google API Services User Data Policy. KittyYawn's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google calendar data only to show and prepare your meetings in KittyYawn; we do not sell it, use it for advertising, or use it to train AI models, and no person at KittyYawn reads it unless you ask us to for support, it is needed for security, or the law requires it.
Screenshots
KittyYawn never captures your screen automatically. A screenshot is taken only when you pick a window to capture, and its text is read on your Mac. A screenshot and its text are sent to the AI provider only if you chose to use it with AI when it was taken ("Use screenshots with AI" in Settings, off by default, or "Use with AI" when KittyYawn asks) and that setting is still on. Screenshots you kept on your Mac are never sent later, even if you turn the setting on. When allowed, a screenshot is described once by the AI provider, and its image and text can then be used for that meeting's guidance, answers and summary. Screenshots are never synced or stored on our servers.
Usage analytics (first-party)
To learn which parts of KittyYawn help, the app and the web console send product events to KittyYawn's own endpoint: the event name (for example "meeting started", "summary opened", "upgrade viewed"), a pseudonymous id derived from your account, random ids for your device and workspace, your plan, app and macOS version, and timings. Card telemetry (which kind of suggestion was shown and how you rated it) is part of the same stream.
Events never contain meeting content: no audio, transcript, card or summary text, no screen captures, no meeting titles, no names or email addresses of other participants. Nothing is sent while signed out.
Your switch. During setup KittyYawn asks whether to share anonymous usage data (on by default); the same switch is in Settings › Account in the app and in the web console's Account page. Off stops all of it, discards anything queued, and is recorded on your account so every device follows it. Feedback you send on purpose is not affected by the switch.
Where it goes. Events stay in our own database. The code can forward them to PostHog (US), but that forwarding is switched off and will stay off until this policy says otherwise.
This website sets no cookies and runs no scripts or third-party trackers. When you follow a link to the web console, the link names the page you came from (utm_ parameters), and the console may record that with your sign-up.
The app checks for updates from our download host; that request shows our host (Cloudflare) your IP address and app version, as any download does.
Payments
Paid plans are sold by Link, Stripe's merchant of record. Checkout and the Billing page are Stripe-hosted: Link/Stripe collect and store your card details, name, email and billing address, calculate tax and issue your invoices and receipts, under their own privacy policies. KittyYawn never sees or stores your full card number.
What our own systems keep: your plan, billing interval and seat count, subscription status, the current billing period, whether you cancelled at period end, and Stripe's customer and subscription ids for your account. We can also see in Stripe's dashboard the information Stripe holds about your payments (for example billing country, invoice email and the last digits of your card); we do not copy it into our database. Subscription start, cancellation and failed-payment events are also recorded as usage-analytics events (plan only) unless you turned analytics off; refunds are not.
Usage records
To enforce plan limits and the monthly AI allowance we keep a per-request usage ledger: which feature was used, when, token counts and cost, your workspace and device ids. It never contains the text that was processed.
Deletion and retention
| Data | Kept | Deleted |
|---|---|---|
| Synced meeting records, people, workspaces | until you delete them | Delete one meeting in the app (content is cleared on the server too, a tombstone keeps the id so other Macs delete it); or delete your account |
| Local data on your Mac (audio, transcripts, notes, voice profile) | until you delete it | Settings; deleting the app's data folder |
| Account record, Terms acceptance, analytics switch | life of the account | immediately on account deletion |
| Usage analytics events | 13 months, then purged | immediately on account deletion |
| In-app feedback you sent | 365 days after it is closed, 2 years at most | immediately on account deletion |
| Usage ledger (plan-limit records) | for the life of your account | immediately on account deletion |
| Billing records held by Link/Stripe (invoices, receipts, tax) | by Link/Stripe under their own policies and tax law | not deleted with the account |
| Calendar connection (account email and id, scopes, status, encrypted refresh token) | until you disconnect it | on disconnect, or immediately on account deletion |
| Calendar events from Google or Microsoft | not stored on our servers | — |
| Waitlist entry | until you are admitted or ask us | on request |
| Sign-in authentication logs (Supabase) | 13 months, then purged | immediately on account deletion |
| Backups of our database (encrypted copies we take, for example before maintenance, and keep in private storage) | until we delete the backup; we keep backups to recover the service, not to keep data you deleted | deleted data can remain in an existing backup until that backup is deleted |
Deleting your account (Settings › Account in the app) is immediate and permanent: it deletes your account and, with it, your personal workspace and everything synced into it, your usage records, analytics events and feedback. Shared workspaces you own are handed to another owner first; if you are the only owner and members remain, deletion asks you to transfer or remove them. If a paid subscription is billed to you, cancel it first. Deleting your account does not remove invoices Link/Stripe keep, and copies can remain in our existing backups as described in the table above.
Encryption and storage
Data stored locally on your Mac is protected by whatever disk-level protection you have enabled, such as FileVault. KittyYawn does not add its own application-level encryption. Data in our cloud is stored by Supabase and Cloudflare with their standard encryption at rest and in transit.
What we don't claim
KittyYawn is local-first, not local-only: bounded text does leave your Mac during use. We do not claim the app is invisible during screen sharing, and we do not claim any third-party security certification.
Recording consent is your responsibility
Laws about recording and transcribing conversations vary by location and can require you to notify or get consent from other participants. You are responsible for complying with them. KittyYawn reminds you during setup and offers a helper that copies a consent-disclosure line to your clipboard for you to paste into a meeting chat; it does not disclose anything on your behalf automatically.
Your rights and contact
You can read, export (the app's data folder and the web console) and delete your data yourself as described above. For anything else — including requests under GDPR, UK GDPR or CCPA — write to support@kittyyawn.com.