⚠ Draft — not yet published

This is a starting draft based on what the codebase actually collects and does, written for you to review and edit — it is not legal advice. Fill in the bracketed placeholders (company name, contact address, hosting location, retention periods) before this goes live, and have it checked by whoever handles legal/compliance for the business if you're not confident doing that yourself.

Privacy Policy

Last updated: [date]

This policy explains what personal data [Your Company Name] ("we", "us") collects through the Gain Calculator Widget service (the embeddable tuning-gain calculator, its pricing site, customer portal, and admin dashboard — together, the "Service"), why, and what rights you have over it. It applies to two groups of people: site owners who subscribe to and embed the widget, and visitors who use an embedded widget on a site owner's website and submit an enquiry.

1. Who we are

[Your Company Name], [company address / registration details]. Contact for any privacy question or request: [privacy contact email].

2. What we collect, and why

If you subscribe (site owners)

Email address — collected via Stripe Checkout when you subscribe. Used to create and identify your license, send billing/subscription-related communications, and provide support. Legal basis: performance of the contract between us.
Payment details — handled entirely by Stripe, our payment processor. We never see or store your card number; Stripe's own privacy policy governs that data (stripe.com/privacy).
Widget configuration — the domains you whitelist, your chosen colours, logo URL, and widget title. This is configuration data about your embed, not personal data about you beyond being tied to your account.

If you fill in the "Get a quote" form on an embedded widget (visitors)

Name, email, phone (optional), message (optional), and the vehicle/tune you were viewing — collected only if you choose to submit that form. Used to pass your enquiry to the site owner whose widget you used, so they can respond to you directly. Legal basis: legitimate interest (responding to a request you initiated) on behalf of the site owner, who is the one actually following up with you.
We do not collect anything if you only browse the make/model/engine picker without submitting the form.

3. Cookies

The Service itself does not set any cookies. The admin dashboard and customer portal store a session credential (an admin password or license key, respectively) in your browser's localStorage so you don't have to log in on every visit — this stays on your device and is never sent anywhere except back to our own server. If you go through Stripe Checkout to subscribe, Stripe's own hosted payment page will set its own cookies under Stripe's privacy policy, not ours.

4. Who we share data with

Stripe — processes payments and stores billing details as a data processor on our behalf.
The site owner whose widget you submitted an enquiry through — they receive your name, contact details, and enquiry so they can reply to you. We do not sell or share your data with anyone else.
[Hosting provider name] — hosts the application and database. [State hosting region/country here once decided, e.g. "servers are located in the UK/EU."]

5. How long we keep data

[To be finalised.] As a starting point: account/subscription data for as long as your subscription is active, plus [X months/years] afterwards for accounting and legal purposes. Enquiry (lead) data for [X months/years] from submission, or until the site owner's account is closed, whichever is sooner. There is currently no automatic deletion job — removal today is a manual process on request (see below).

6. Your rights

Depending on where you live, you may have the right to:

ask what personal data we hold about you and get a copy of it;
ask us to correct inaccurate data;
ask us to delete your data ("right to be forgotten");
object to or restrict certain processing;
ask for your data in a portable format.

To exercise any of these, email [privacy contact email]. We'll respond within [30 days / your target]. This is currently handled manually rather than through a self-service tool.

7. Security

Widget embeds are restricted to whitelisted domains, contact-form submissions are verified with a signed token rather than trusted at face value, and all user-submitted content is encoded before being displayed in the admin/portal dashboards to prevent it being used to run code in another user's browser. No online service can guarantee perfect security, but these are the concrete measures currently in place.

8. Changes to this policy

If this policy changes materially, we'll update the date at the top of this page. [Consider adding: and notify active subscribers by email.]

9. Contact

Questions about this policy or your data: [privacy contact email].