A short, honest note on cookies.
Solves keeps cookies to the minimum. We set one essential first-party cookie so you can sign in and so forms are protected against cross-site request forgery, and we use first-party, metadata-only telemetry to spot and fix problems. We do not use advertising or marketing cookies, and we do not track you across other websites.
Solves is at pilot stage. Full legal documents are in preparation before public paid launch; this notice describes how we handle cookies today.
The short answer
What cookies we use and why
A cookie is a small piece of text a website stores in your browser. Solves uses cookies sparingly and only for things that have to work: keeping you signed in and protecting the forms you submit. We do not run advertising, profiling or cross-site tracking cookies.
The one cookie we depend on is a strictly necessary, first-party session cookie, set when you sign in. It holds a session reference, not your password or any customer content, and it lets each request prove it came from your logged-in session. The same cookie underpins our cross-site request forgery protection, so a state-changing action can only be submitted from a genuine Solves page.
First-party telemetry, metadata only
Alongside the session cookie, we collect first-party telemetry to diagnose problems before a customer has to report them. It is metadata only: timings, bucketed route families, error signals and a correlation identifier that threads a request through our system. It stays within Solves and is never handed to an advertising network.
By design, this telemetry never records message bodies, email addresses, secrets or request payloads. A sanitiser strips forbidden fields and redacts anything sensitive before an event is written, and it fails closed if anything slips through. It tells us that something was slow or broke, not what any customer wrote.
What we do not do
We set no advertising cookies, we embed no ad pixels or social tracking tags, and we do not sell or share your browsing for marketing. Because we are not doing any of that, there is no consent-manager banner to click through: the only cookie in play is the essential one needed to run the app.
How to control cookies in your browser
You stay in control through your browser, which lets you view, block or delete cookies from its privacy or site-data settings and set per-site rules. A private or incognito window discards cookies when you close it.
- Chrome: Settings, then Privacy and security, then Cookies and other site data.
- Firefox: Settings, then Privacy and Security, then Cookies and Site Data.
- Safari: Settings or Preferences, then Privacy, to manage and remove site data.
- Edge: Settings, then Cookies and site permissions, then Manage and delete cookies and site data.
If you block the essential session cookie, the public marketing pages will still load, but you will not be able to sign in, because that cookie keeps you logged in and protects your forms.
At a glance
The cookies we set
A short reference for the cookies and telemetry Solves uses today.
| Session cookie (first-party, essential) | Keeps you signed in and protects forms against cross-site request forgery. Holds a session reference only, never your password or customer content. Required for the app to work. |
|---|---|
| First-party telemetry | Metadata-only diagnostics: timings, bucketed route families, error signals and a correlation identifier. Never records message bodies, addresses, secrets or payloads. |
| Third-party advertising cookies | Not used. Solves sets no ad cookies, ad pixels or cross-site tracking tags. |
| Consent-manager cookie | Not used. With only an essential cookie and first-party telemetry, there is no consent banner to store. |
Honest about pilot stage
Solves is in pilot, and this notice describes how we handle cookies right now. If we ever add anything beyond an essential session cookie and first-party metadata telemetry, we will add clear controls and update this page before that change goes live.
FAQ
Cookie questions
Do you show a cookie consent banner?
Not at the moment. Solves only sets a strictly necessary session cookie for sign-in and CSRF protection, which a site may set without prior consent, and our telemetry is first-party and metadata-only. We run no advertising or cross-site tracking that would need a consent manager. If that ever changes, we will add clear controls and update this notice first.
Do you use third-party advertising or marketing cookies?
No. Solves sets no advertising cookies, embeds no ad pixels or social tracking tags, and does not sell or share your browsing for marketing. The only cookie we rely on is our own first-party session cookie.
What happens if I block the session cookie?
You can still read the public marketing pages, but you will not be able to sign in. The session cookie keeps you logged in and protects forms against cross-site request forgery, so blocking it stops authenticated areas from working.
What does first-party telemetry record?
Metadata only: timings, bucketed route families, error signals and a correlation identifier that threads a request through our system. It never records message bodies, email addresses, secrets or request payloads, and a sanitiser redacts anything sensitive before it reaches a log.
How can I control cookies in my browser?
Every major browser lets you view, block and delete cookies from its privacy or site-data settings, and a private or incognito window discards them on close. Blocking our session cookie will prevent sign-in, as described above.
Read how we handle your data
The privacy notice explains what we collect and why; the security page covers encryption at rest and metadata-only logs.