Privacy Policy
What FloatChart stores, and what it never does with it
The short version: your boards are yours; we store them so you can open them anywhere and share them; we do not read them, sell them, advertise on them or train models on them; the AI features are off until you switch them on; and you can export or delete everything at any time.
1. Who is responsible
The controller of your personal data is [LEGAL ENTITY NAME], doing business as FloatChart, [POSTAL ADDRESS]. Questions about this policy go to hello@floatchart.com.
2. What we collect, and why
| Data | Why | Where it comes from |
|---|---|---|
| Email address, display name, sign-in method | Your account; telling collaborators who wrote what | You, or Google if you sign in with it (we receive your email, name and avatar URL — no access to your Google files) |
| Your files: boards, tiles, dependencies, labels, questions, notes, comments, folder names | The service itself | You, your collaborators, and anything you import (Mermaid, .fcx, other tools) |
| Version history: snapshots of a file as it changes, with the author and time | So you can go back | Generated as you work |
| Workspace membership, roles, invitations, sharing policy, an audit log of admin actions | Working with a team; letting admins see what changed | Workspace owners and admins |
| Share-link tokens and how often each was opened | Sharing; letting you see whether a link is in use | Generated when you make a link |
| Plan, subscription status, invoices | Billing | Stripe (we never see your card number) |
| AI usage: request counts, token counts, cost, which workspace and file | Metering and limits for FloatChart AI | Generated when you use the hosted AI |
| Operational logs: request timing, error codes, IP address, browser type | Keeping the service running and secure | Our hosting providers, kept about 30 days |
| Anonymous daily counts: how many visits reached each step — opened the app, changed a board, signed up — grouped by day, by the site that referred them, and by whether that browser had been here before | Telling a channel that sends the wrong people from a sign-up that is too hard | Counted in your browser. No identifier of any kind is sent: no visitor ID, no session ID, no fingerprint, no IP address, no page address. Nothing in it is linked to you, so there is nothing in it to show you or to delete |
We do not run advertising, tracking pixels or third-party analytics on floatchart.com or in the app. The app's security policy actively blocks third-party scripts, including our host's own analytics beacon. The counts in the last row of the table are ours alone and are only ever numbers: we can see that forty people who arrived from a particular site went on to draw something, and we cannot see which forty, or follow any one of them from one visit to the next — by design, because we never collect what that would take.
3. Where it lives
- Without an account, your boards live only in your browser's local storage on that device. We never receive them.
- With an account, files, versions, workspaces and settings are stored in a database hosted by Supabase in the United States, protected by row-level security so that only you and the people you have shared with can read a file.
- The app and website are delivered by Cloudflare, which sees requests and IP addresses as any host does, and stores none of your files.
- Payments are processed by Stripe, which holds your card details under its own privacy policy.
4. AI features — the honest version
- Nothing AI-related runs unless you invoke it.
- Your own key. If you enter an API key from Anthropic or OpenAI, it is stored in your browser on that device only, and your browser sends the board and your request straight to that provider under your account and their terms. FloatChart's servers are not in that path.
- FloatChart AI (hosted add-on), when offered. Requests pass through our server to Anthropic, our named sub-processor, whose API terms prohibit training on the content sent to it. We keep the chat history you can see (deleted after 90 days by default, adjustable by your workspace admin, and deletable by you at any time) and usage metadata for billing. We do not claim zero data retention at the provider; if that matters to you, bring your own key and your own agreement with the provider.
- Team keys stored on our side are encrypted with a key held outside the database; no member, admin or endpoint can read a stored key back — only its last four characters.
- We never train models on your content, and we never permit our providers to.
5. Sharing
A share link gives whoever holds it the access it grants. Guests who open a link without an account are anonymous to us. Questions and notes you mark internal are removed on the server before a file goes to a guest, along with the names of whoever wrote them; the author of anything else a guest can see is shown as “someone signed in” rather than by email. Members of a workspace can see the files in that workspace and who changed them.
6. How long we keep things
- Files and workspaces: until you delete them or your account.
- Version history: the most recent automatic snapshots per file (the number depends on your plan), and any version you name, until the file is deleted.
- Deleted files: removed at once; they may persist in encrypted backups for up to 30 days.
- Account deletion removes your account, files, versions and memberships, after which they cannot be recovered. Invoices are kept as long as tax law requires.
- Audit logs of workspace admin actions: 12 months.
7. Your rights
Wherever you live, you can: export every file from inside the app; correct your name and email; delete your account and everything in it; and ask us what we hold about you. If you are in the EU, UK or a jurisdiction with similar rights, you also have the rights to restriction, portability and objection, and to complain to your supervisory authority; the legal bases we rely on are performance of our contract with you, our legitimate interest in running a secure service, and your consent for optional features. Write to hello@floatchart.com; we answer within 30 days.
8. Security
Everything travels over TLS. Data is protected in the database by row-level security enforced on the server, not only in the app. Share tokens are random and revocable. We deploy behind a strict content-security policy and test the sharing boundary adversarially. No system is perfect: if we learn of a breach affecting your data, we will tell you without undue delay.
9. Children
FloatChart is not directed at children under 16 and we do not knowingly collect their data. If you believe a child has created an account, tell us and we will delete it.
10. Changes
When this policy changes materially we will show a notice in the app or email account holders before the change takes effect. The effective date at the top says which version you are reading.
11. Sub-processors
| Provider | Purpose | Region |
|---|---|---|
| Supabase | Database, authentication, file storage | United States |
| Cloudflare | Hosting, DNS, delivery, server functions | Global edge; functions run near the visitor |
| Stripe | Payments and invoicing | United States |
| Anthropic | FloatChart AI (hosted add-on) — only when invoked | United States |
| Sign in with Google — only if you choose it | United States |
12. Contact
hello@floatchart.com · [LEGAL ENTITY NAME], [POSTAL ADDRESS]