Sheet-Map Privacy Policy
Last updated: 4 October 2026
This explains what Sheet-Map collects, why, who else handles it, and your choices. Sheet-Map is operated by Sheet-Map, a business based in California, United States ("we", "us"). Contact: support@sheet-map.com.
The short version: we keep what's needed to run your account and your Sheet-Maps, and nothing more. We don't sell your data, we don't show ads, and we don't use analytics or tracking cookies.
1. What we collect
If you use Sheet-Map without an account, your data stays in your browser's storage on your device. It never reaches our servers. Map tiles and code libraries still load from third parties (see section 4).
If you create an account, we store:
- Account details: your email address and a securely hashed password (handled by our authentication provider; we never see your password).
- Your content: the sheets, rows, coordinates, map items, folders, custom symbols and team chat messages you create, and the names of your Sheet-Maps.
- Team information: which Sheet-Maps you belong to and your role in each, and invitations, including the email address of anyone you invite.
- Notifications: for example, that you were added to a team.
- Billing records (Pro only): your Stripe customer and subscription identifiers, the subscription's status and its renewal or end date. We never receive or store your card number; Stripe handles that.
Operational data, collected automatically:
- Error reports: when something breaks in the app, we record the error message, the technical stack trace, the page path, your browser's user-agent string, the app version and your user and team identifiers, so we can find and fix it. Error reporting runs only on sheet-map.com.
- Map usage counts: how many map tiles each map provider served to your session, in aggregate, with your user and team identifiers. This tells us how much we rely on each provider. It does not record which places you looked at.
- Server logs: our API servers record errors with your user identifier.
2. Why we use it
- To provide the service: storing, syncing and showing your Sheet-Maps, and letting you collaborate with the people you invite.
- To send the emails you'd expect: sign-up confirmation, password reset, and team invitations sent on your behalf.
- To handle Pro subscriptions and keep your plan in step with your payments.
- To keep the service secure and working: fixing errors, preventing abuse, and enforcing plan limits.
We don't use your data for advertising, and we don't sell it or share it for others' marketing.
Legal bases (for users in the EU/UK): providing the service you signed up for (contract); keeping it secure and fixing errors (legitimate interests); keeping billing records (legal obligation).
3. Who can see your content
- You, and the people you invite into a Sheet-Map, according to their role.
- We don't look at your content, except when you ask us to (for example in a support request), when needed to fix a technical problem, or when the law requires it.
4. Service providers
These companies process data for us to run Sheet-Map:
| Provider | What for | What it receives |
|---|---|---|
| Supabase | Database and sign-in | Your account and content (above). Hosted in Canada (Central, ca-central-1). |
| Cloudflare | Our API servers (billing) | Requests to our API, including your sign-in token and IP address. |
| Stripe | Payments, as merchant of record for Pro | Your payment details and billing address, entered directly with Stripe. Stripe's own privacy policy applies. |
| Resend | Sending email | Recipients' email addresses and the message (confirmations, password resets, invitations). |
| GitHub Pages | Hosting the website | Standard web request data, such as your IP address. |
Third parties your browser contacts directly. Like most web maps, Sheet-Map's pages load resources from other services. They see your IP address, and map providers see which map areas you view:
- Map tiles: OpenStreetMap, OpenTopoMap, Esri (ArcGIS) and Google, depending on the basemap you pick.
- Code libraries and fonts: cdnjs (Cloudflare), jsDelivr, unpkg and Google Fonts.
5. Cookies and local storage
We don't use tracking or advertising cookies. Sheet-Map uses your browser's local storage to:
- keep you signed in;
- keep a copy of your data for speed and offline use;
- remember preferences such as your theme.
Choosing Log Out removes your account's data from that browser. Stripe's checkout and billing pages, which open on stripe.com, set their own cookies.
5a. Do Not Track
Sheet-Map doesn't track you across other websites and shows no ads, so there is nothing for a browser's "Do Not Track" signal to switch off. We treat every visitor the same whether or not the signal is sent.
6. How long we keep data
- Your account and content: until you delete them or ask us to delete your account.
- Backups: we keep weekly backups of the database for up to 12 weeks. Deleted data disappears from backups as they age out.
- Error reports, server logs and map-usage counts: deleted automatically after 90 days.
- Billing records: as long as US federal and California tax law requires (generally up to 7 years).
7. Your choices and rights
- See and export: your data is in the app, and you can export it at any time.
- Correct or delete: edit or delete your content in the app. To delete your whole account, email support@sheet-map.com from your account's email address. We'll delete your account and the content only you own, and remove you from shared Sheet-Maps.
- Depending on where you live (for example in the EU, UK or California), you may have further rights: to access, correct, delete or port your data, or to object to certain uses. Email us and we'll respond within 30 days. You can also complain to your local data protection authority.
8. Security
Data travels encrypted (HTTPS), and access to each Sheet-Map is enforced by the database itself, so only its members can read it. No system is perfectly secure; if a breach affects your data, we'll tell you as the law requires.
9. Children
Sheet-Map isn't intended for anyone under 16, and we don't knowingly collect their data.
10. Changes
If we change this policy in a way that matters, we'll tell signed-in users in the app or by email before it takes effect.