Privacy policy

Template, to be completed by the operator. This page describes what the software stores and why. Before you open the service, replace every […], check each section against what you really do, and have the text reviewed by a lawyer for the countries you sell in. Delete this note when done.

Last updated: [date].

Who we are

[Legal name of the company], [legal form and registration number], [postal address]. We are the controller of the personal data described here. Contact: [privacy contact email].

What we collect

Data Why Kept for
Email address To sign you in (we email you a sign-in link; there is no password) and to send service messages As long as the account exists
Name and language, if you set them To address you and show the interface in your language As long as the account exists
API keys and tokens of connected applications To recognise the programs you allowed. Only a fingerprint is stored: we cannot read a key back Until you revoke them
Call log: tool, date, result, duration, credits, application, IP address To bill credits, show you your usage, and investigate errors and abuse 90 days
Credit ledger: grants, debits, refunds, purchases To keep your balances right and to meet accounting duties [period required by your accounting law]
Payment records: amount, date, Stripe identifiers To prove a purchase. Card details go to Stripe and never reach us [period required by your accounting law]
Audit entries: sign-ins, changes to your account Security [period]

We do not store the arguments you send to a tool or the results it returns, beyond what a tool needs while it runs and, for a background job, until the job record is purged ([period]).

[If a tool of your product stores or forwards the content it receives, say so here, tool by tool.]

[For the EU and the UK: performance of the contract for the account, the calls and the billing; legitimate interest for security and abuse prevention; legal obligation for accounting records. Adapt to your jurisdictions.]

Who receives data

Recipient What for Where
[Hosting provider] Servers and database [country]
Stripe Payments [country]
[Email provider] Sign-in links and service emails [country]
[Error monitoring provider, if enabled] Technical error reports, without your credentials [country]
[Each service a tool calls on your behalf] To run the tool you asked for; it receives the arguments of that call [country]

We do not sell personal data and we do not use it for advertising. [Describe the safeguards for transfers outside your region, if any.]

Cookies

We set the cookies the service needs to work: one that keeps you signed in, one that protects forms against forgery, and one that remembers your language. Your choice of light or dark theme is kept in your browser's local storage. There is no advertising or analytics cookie. [Change this if you add analytics.]

Your rights

You can, at any time and from your account settings:

  • export your data as a file;
  • delete your account. Your keys and connected applications stop working at once; personal data is erased or made anonymous within 30 days, except records the law requires us to keep.

You may also ask us to correct your data, to restrict or object to a use, and you may complain to your data protection authority [name and link of the authority]. Write to [privacy contact email]; we answer within [30 days].

Security

Connections are encrypted (HTTPS). Keys and tokens are stored as fingerprints only. Access to production data is limited to [who] and is logged.

Changes

We post changes on this page and, when they matter, tell you by email before they apply.