CostScanner has not published a cookie 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 cookie 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 final cookie inventory, which is not settled until authentication and billing are wired up.
- Whether an analytics measurement ID is configured for the production deployment — no analytics cookie is set without one.
- Whether a consent banner is required, which follows from the jurisdiction and from the analytics decision.
- The controller and contact address, shared with the privacy policy.
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.