chalmsy
Privacy
How we look after your data
Last updated · August 15, 2026
Chalmsy is a private operating system for small businesses and creative studios. We're built around the idea that the data you put into your workspace is yours — not ours, not a third party's, not a model trainer's. This page sets out what we collect, why, and what we never do with it.
What we collect
- Account basics: the name + email address that comes back from your Google sign-in. We use these to identify you across sessions and to send essential account emails.
- Workspace data you create: clients, leads, proposals, invoices, calendar events, files, brand assets, and the like. All of this is stored in your own tenant inside our Supabase database and is scoped by row-level security so other Chalmsy tenants cannot read it.
- Integration tokens: if you connect Gmail, Calendar, Drive, Photos or — once those integrations are available — a social account, we store the OAuth refresh token only — never your password. Tokens are revocable at any time from your account settings or from the provider's account page.
- Operational logs: request timestamps, error stacks, and basic usage metrics to keep the service running. We do not log message bodies, file contents, or anything you'd consider sensitive.
- Website analytics: our public marketing site at chalmsy.com uses Google Analytics to count visits and see which pages are read. It sets cookies in your browser and tells us things like which page you arrived on and roughly where in the world you are — never who you are. This applies to the marketing site only: your workspace itself carries no analytics and no third-party tracking of any kind. You can opt out with any standard browser or extension blocker without affecting the app.
What we never do
- Sell, rent, lease, or share your data with advertisers or data brokers.
- Train AI models on the contents of your workspace.
- Read your emails, files, or calendar events programmatically, except to provide features you've explicitly invoked (e.g. "draft this proposal from this email").
- Send marketing emails. You'll only hear from us about account-essential things like billing, security, or a service-affecting incident.
Who else sees your data
- Supabase (database + auth, hosted in the United States — AWS
us-east-2, Ohio) — our infrastructure provider. If you are in the UK or EU, your data is transferred to and stored in the US under the Standard Contractual Clauses in Supabase's Data Processing Addendum.
- Vercel (web hosting) — serves the app to your browser.
- Stripe (payments) — when you subscribe to a paid plan, checkout happens on Stripe's systems and your card details go directly to Stripe; we receive your subscription status and billing history, never your card number.
- Anthropic (AI features) — when you use an AI feature, the prompt and the relevant context from your workspace are sent to Anthropic's API to produce the result. Under Anthropic's commercial terms, API inputs and outputs are not used to train their models. Where that context includes content you saved from Google — email text loaded into a booking, or an image attached to a proposal — that content is part of what is sent.
- Other AI providers, per feature — some features send material to a specific provider only when you invoke them: voice-note transcription sends the audio to OpenAI; AI image generation sends your prompt and any reference image to Google (Gemini). Each receives only what the feature you invoked needs. Under OpenAI's API terms, submissions are not used to train its models.
- Google — only when you've explicitly connected Gmail/Calendar/Drive/Photos. We call Google APIs on your behalf using your token; Google's own privacy policy applies to that data.
- Social platforms — if you connect a social account (Facebook, Instagram, Pinterest) once those integrations are available, the posts and media you choose to publish are sent to that platform under its own terms.
Your Google data
Chalmsy asks for its Google permissions together, once, when you first sign in — so your inbox, calendar and files are working the moment you arrive instead of after four separate setup steps. You are shown the full list by Google before you agree to any of it, and you can withdraw it at any time. Here is exactly what each permission is used for, and what we do not do with it:
- Gmail — read, draft & send: to show the messages that relate to your work, prepare replies and proposals for you as drafts you review before anything goes out, and send from your own address once you approve. The permission Google grants for this technically also allows labeling and archiving; Chalmsy does neither, and we never delete anything in your mailbox. Messages are read on demand and are not copied into Chalmsy by default — except where you explicitly ask for it: when you use "load this email into a booking" or attach an email attachment to a project, that message text or file is saved into your workspace and stays there until you delete it. Anything saved that way is later included in the context sent to Anthropic if you generate a proposal for that client.
- Calendar — read & create events: to show your existing events alongside your bookings and to create the events you ask Chalmsy to add. We never edit or delete events we didn't create.
- Drive — read your files, and add new ones: so you can browse and search your own Drive from inside Chalmsy when attaching an image or document to a proposal, and so Chalmsy can save what it produces for you — exported proposals, PDFs, brand assets — into a folder you choose. This permission covers your whole Drive, because you choose the file or folder at the moment you need it rather than pre-arranging one. Chalmsy does not edit, overwrite or delete files it did not create.
- Photos — picker only: when you add an image to a proposal or mood board, Google's own picker lets you choose specific photos. Chalmsy only ever receives the items you hand-pick in that picker — it cannot browse or read your wider photo library.
Every Google permission can be revoked at any time from your Chalmsy settings or from your Google Account → Data & privacy → Third-party apps page.
Google API Services — Limited Use
Chalmsy's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, data obtained through Google APIs is:
- used only to provide or improve user-facing features inside Chalmsy that you have explicitly enabled;
- never used for advertising, and never sold, rented, or shared with data brokers;
- never used to train generalized or foundation AI models;
- never read by a human, except with your explicit consent (e.g. when you raise a support request), where required for security or to comply with the law, or in a limited, aggregated, anonymized form for internal operations.
Data retention & deletion
We store your Google OAuth tokens only while the integration is connected. When you disconnect an integration the stored token is removed immediately and the corresponding Google access is revoked with Google.
We do not warehouse your Google data in bulk: Chalmsy never crawls, mirrors or background-syncs your mailbox, calendar, Drive or photo library, and reads them only in response to something you do. But two kinds of content are saved, because saving them is the point of the action you took:
- Things you attach. A Gmail attachment or Drive file you add to a project, and a photo you pick for a proposal or mood board, are stored in your workspace so the project still has them tomorrow. Images attached to a proposal are held in file storage so the proposal can render for the client you sent it to.
- Things you copy in. Email text you load into a booking's notes or a project brief is saved as part of that record, and is included in the context sent to Anthropic when you later generate a proposal for that client.
Both persist until you delete the record they belong to, or until your workspace is deleted. Disconnecting Google revokes our access and removes the token, but does not by itself remove content you had already saved into your workspace — ask us to erase it and we will. Calendar events are only ever read on demand and are never copied into Chalmsy. Operational logs that may reference a request are kept for up to 30 days and then rotated out.
Deleting your workspace. Email privacy@chalmsy.com from the address you signed up with and we will delete the workspace and everything in it — records, stored files, and every Google token, with each Google grant revoked — within 30 days, and confirm when it is done.
Your rights
You can:
- Export your clients, bookings, proposals and invoices as a JSON file from your settings page. Ask us if you need anything the export does not cover and we will send it to you.
- Disconnect any integration at any time from your settings page or from the provider's account page.
- Delete your workspace and all its data permanently, including every stored file and Google token. Email privacy@chalmsy.com from the address you signed up with and we will complete it within 30 days and confirm.
- Ask us what we hold about you. Same address.
How we protect it
All data is transmitted over HTTPS only (HSTS preloaded). Database access is gated by row-level security policies + service-role tokens that never leave server-side functions. Customer workspaces are isolated by tenant: a member of one workspace cannot read another's data even via direct API calls. Database backups are taken automatically by our infrastructure provider, Supabase, on the schedule and retention policy published in Supabase's backup documentation for our hosting plan; restoring from a backup requires an explicit support request.
Children
The Service is a business tool. It is not directed to children under 13, and we do not knowingly collect personal data from children. If you believe a child has provided us personal data, contact us and we will delete it.
Changes to this policy
We may update this policy as the Service evolves. Material changes will be announced by email or by a notice in the app before they take effect, and the date at the top of this page always shows the current version.
Contact
The Service is operated by Chalmsy LLC (United States). Questions, complaints, or deletion requests: privacy@chalmsy.com.