Privacy
Symphony holds the working details of your household. This page says exactly what it keeps, who else touches it, and how to get it deleted. No legalese.
Effective September 26, 2026. Questions: hello@symphony-os.com.
The short version. Your data is yours. We never sell it, never show ads, and never use it to train anything. The only people who can see your household's information are the people you invite into it. Email us and we delete everything within 30 days.
What Symphony keeps
Your account
Your email address and a password, stored as a hash, never in plain text.
If you ask to become a founding household
The email address you leave on the sign-up form, and when you left it. We use it for one thing: writing back to set up your household. It sits in our database until you're onboarded or you ask us to remove it.
What you put in
Tasks, notes, routines, lists, meal plans, projects, and the people you name in your household (names, roles such as partner or child, and anything you add to their profile). Photos of paper plans you snap, and files or photos you attach to items. A home location if you enter one, used for the weather and for directions.
What you connect, if you choose to
- Google Calendar. With your permission Symphony reads your calendars to show events alongside your tasks, and creates, edits, moves, or deletes events when you ask it to.
- Gmail. The same Google connection lets the assistant search and read your mail when you ask it to, and draft or send a message on your behalf when you explicitly tell it to. Symphony never sends email on its own.
- School email. Your household gets a private forwarding address. Emails you forward there are read to pull out the event, the date, and what each child needs. We keep the text of the email so you can always see the source behind an item.
Symphony's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can disconnect Google at any time in Settings, which removes the saved connection. You can also revoke the authorization in your Google account's third-party connections settings.
Technical data
When something breaks we get an error report. A small sample of sessions is recorded for debugging with all text masked and all images and media blocked, so we can see where a layout broke, not what you wrote. If you have not set a home location, your approximate location is estimated from your IP address only to show the weather, and only after your browser declines to share it. There are no advertising trackers, and the marketing site runs no analytics at all.
What Symphony does with it
It runs the product: shows you today, keeps the household in sync, and surfaces context when you need it. Nothing else.
AI features send only what they need. When Symphony extracts events from a forwarded email, reads a photo of your plan, or answers a question in a Discuss thread, the relevant content is sent to Anthropic's Claude API and the answer comes back. Anthropic does not use API data to train its models. We do not send your whole database to anyone.
Household sharing works the way you'd expect. Items you mark Family are visible to everyone in your household. Items in Work or Personal are visible only to you. A Discuss thread on a family item is shared; on a private item it is private.
Who else touches your data
Symphony runs on a small number of services. Each one sees only what its job requires.
| Service | What it does | What it sees |
|---|---|---|
| Supabase | Database and sign-in, hosted on AWS in the United States | Everything you store |
| Vercel | Serves the app and this website | Standard request logs |
| Cloudflare | Receives mail sent to your forwarding address and passes it to Symphony | Forwarded emails in transit |
| Anthropic | AI extraction and the assistant | The item, email, or photo being worked on |
| Calendar and place lookup, only if you connect or search | What you authorize | |
| Open-Meteo | Weather, and finding your home on the map | Your home coordinates, and the town or ZIP you type for home |
| ipapi.co | Location fallback for weather | Your IP address, only if no home location is set |
| Sentry | Error reports and masked session samples | Errors and masked layouts |
We do not sell data, share it with advertisers, or hand it to data brokers. We would disclose data only if required by law, and we would tell you if we were allowed to.
Children
Symphony is for adults. Parents enter their children's names and schedules; children do not get accounts. We do not knowingly collect information directly from anyone under 13. The kitchen wall display shows a child their own day, but it is signed in as the parent.
Keeping it safe
Data is encrypted in transit and at rest. Every table is protected by row-level access rules enforced by the database itself, so a household can only ever read its own rows. The founder can reach the database to fix problems, and does not read household content unless you ask for help with something specific.
Symphony is built and run by one person. That means fewer hands near your data, and it also means you should tell us directly if something looks wrong: hello@symphony-os.com.
Deleting things
- Any item can be deleted in the app. The stored text of forwarded emails is removed with your account, or sooner on request.
- Google access: disconnect in Settings to remove the saved connection. To revoke the authorization itself, remove Symphony from your Google account's third-party connections settings.
- Your account and everything in it: email hello@symphony-os.com from the address on the account. We delete the household's data within 30 days and confirm when it is done. Supabase automated database backups are retained on a rolling seven-day schedule. Deleted database records may remain in those backups until they expire. These database backups do not contain uploaded files.
If you want a copy of your data before it goes, ask in the same email and we will send an export.
Changes
If this page changes in a way that matters, founding households hear about it by email before it takes effect. The effective date at the top always reflects the current version.