The short version
CloudVerdict sets no advertising cookies, no tracking cookies, and no third-party analytics cookies. Everything it stores is needed to sign you in or to remember how you have set the screen up. There is no consent banner because there is nothing here that requires consent.
What is stored
| Name | What it is for | How long |
|---|---|---|
cloudverdict_session |
Your signed-in session. Without it you cannot stay signed in. A long session is split across cloudverdict_session.0, cloudverdict_session.1, and so on |
Until the session expires or you sign out |
cloudverdict_session-code-verifier, cloudverdict_session-flows-code-verifier, and cloudverdict_session-flow- followed by an identifier and -code-verifier |
That a link you asked for, to confirm your address or to choose a new password, is on its way to you. Each holds a secret that only this browser has, so the link signs you in here and nowhere else. 1 is kept for each link waiting, up to 5 | Until the link is used or you sign out, and a day at most |
cloudverdict_theme |
Whether you chose light, dark, or your machine's own setting, so the page arrives in the right one rather than changing in front of you | 1 year |
cloudverdict_nav |
Whether you folded the navigation into a rail, so it stays as you left it | 1 year |
cv-sign-in-notices |
That you have just signed in, so a notice we show at sign-in is shown to you once each time you sign in, and not on every screen | Until you choose Continue under those notices, or close your browser |
Besides those cookies, 2 kinds of item are kept in your browser's own storage while you use the product. Neither is sent to us or to anybody else.
| Name | Where | What it is for | How long |
|---|---|---|---|
cloudverdict-last-active |
Local storage | When you last did something in any tab, so a tab in which you are working keeps the others signed in, and you are signed out of all of them together after the period with nothing done | Until you clear it, and overwritten as you work |
cloudverdict-chart: followed by a use case's identifier |
Local storage | Which chart you last chose for that use case's result, so it opens on that chart again. 1 is kept for each use case whose chart you change | Until you clear it, and overwritten when you choose another chart |
All of these are strictly necessary in the sense the law uses: the session cookie because the service cannot be provided without it, the link cookies because a link we email could otherwise sign in whoever it was sent on to, the activity time because it keeps your account secure when you step away, the sign-in mark because it is how a notice we give at sign-in reaches you, and the rest because they exist only to deliver the interface in the state you asked for.
What is not stored
- No advertising or marketing cookies.
- No cross-site tracking.
- No analytics of any kind: we do not count page views or measure your visit, with or without cookies.
- No fingerprinting.
- No cookies set by the cloud providers CloudVerdict compares. We read their published prices; they are not present on this site and receive nothing about you.
Measuring the site
We do not measure the site. Nothing counts your page views, records where your visit came from, or times how pages load, and nothing is added to the page to do so. The Privacy Notice sets out the ordinary records a web server keeps to answer your requests.
Controlling them
Your browser can block or delete cookies for this site. If you block the session cookie you will not be able to sign in. If you block the two preference cookies the product still works, but it will not remember your theme or your navigation between visits. If you block the link cookies, a link we email to confirm your address or to choose a new password will not work in this browser. If you clear your browser's storage, a result opens on its first chart.
Your theme preference is also kept against your account, so that it follows you to another device once you are signed in. That is described in the Privacy Notice.
Questions
Anything about cookies goes to privacy@
Contact points
Each kind of correspondence has its own address. Using the right one matters: a data rights request has a statutory clock running on it, and a security report should not wait in a support queue.
| Purpose | |
|---|---|
| General and sales enquiries | contact@ |
| Product support | support@ |
| Billing, invoices, VAT, refunds, and payments | billing@ |
| Privacy, cookies, and data rights | privacy@ |
| Legal notices and contractual correspondence | legal@ |
| Security reports and suspected personal data breaches | security@ |