CostScanner has not published a privacy policy yet. We are pre-launch: accounts are not open, no payment is taken, and the product processes no customer data. Rather than show boilerplate that would name the wrong company and the wrong service providers, this page is honest about the gap.
A privacy policy will be published here before accounts open, and before this site collects anything from anyone. It will be a statement about what actually happens, not a template.
What has to be settled first
- The data controller: which legal entity, in which jurisdiction, under which regime (GDPR, KVKK, or both).
- A data-protection contact address for rights requests.
- The sub-processors actually in use — hosting, database, email delivery, payments and analytics. Naming the wrong ones is the commonest fault in a copied policy.
- Retention periods, which follow from the statutory record-keeping rules of the chosen jurisdiction.
- Whether an analytics measurement ID is configured for the production deployment, and on what legal basis.
In the meantime
This site serves public pages only. It sets no analytics cookie unless a measurement ID is configured for the deployment, and it stores nothing you have not typed into a form — and there is currently no form that submits anywhere.
See also the status page for what is and is not running.