Cookie policy
- StockIQ sets one cookie, only after you sign in. It keeps you signed in and does nothing else.
- No advertising cookies, no analytics cookies, no cross-site tracking, and no third-party scripts to set any.
- The site is served through Cloudflare's reverse proxy, which can set its own strictly necessary security cookies. The note below covers those.
- Everything here is strictly necessary, so there is nothing to consent to and no banner to click.
- Clear it whenever you like. Clearing it signs you out; none of your data is stored in it.
1. The cookie we set
A cookie is a small text file a website asks your browser to store and send back on later requests. StockIQ sets exactly one. The note at the end of this section covers the separate case of the proxy in front of us, which is not ours to set or to clear.
| Name | Purpose | Type | Lifetime |
|---|---|---|---|
| dotomize_session | Keeps you signed in. It is set when you sign in and holds a signed token identifying your session and the account it belongs to, which includes your email address. It does not contain your password or anything about your portfolio. | Strictly necessary. First-party. HttpOnly, Secure, SameSite=Lax. | Expires after 7 days without use, and in any case 30 days after you signed in. |
HttpOnly means no script can read it, which limits what a cross-site scripting flaw could do with it. Secure means it is only ever sent over HTTPS. SameSite=Lax means another site cannot make your browser send it along with a request it made on your behalf.
The cookie belongs to this origin, so if you are signed in it is sent with requests for these marketing pages as well as for the application. Nothing on these pages reads it.
The proxy in front of the site
The site is served through Cloudflare's reverse proxy, which sits between your browser and our server. A reverse proxy can set cookies on this domain without anything on the page asking it to, so the usual reasoning — "the page loads nothing from another host, therefore no third party can set a cookie" — does not settle the question.
Where Cloudflare sets one it is a security cookie: it distinguishes automated traffic from a person, or records that a challenge has been passed. Cookies of that kind are strictly necessary and carry no advertising or analytics purpose, and we do not read them or receive their contents. Clearing site data removes them along with ours.
2. Why there is no consent banner
The Privacy and Electronic Communications Regulations 2003 require consent before storing information on a user's device, with an exemption for storage that is strictly necessary to provide a service the user has explicitly requested.
A cookie that keeps you signed in to a service you asked to sign in to sits squarely inside that exemption. We could not switch it off if you asked us to: without it, signing in would not work at all, because the next page you loaded would not know who you were. So there is no consent to collect, and this site shows no cookie banner.
Signing out, or not signing in, means the cookie is never set. The public pages work perfectly well without it.
3. What we do not use
- No advertising or retargeting cookies.
- No analytics cookies. There is no analytics product on this site at all.
- No cross-site tracking, no social media pixels, no affiliate tags.
- No third-party cookies set by anything on the page. These pages load no fonts, scripts, stylesheets, images or embeds from any other host, so nothing in the page is in a position to set one, and that is checked automatically on every build. The proxy in front of the site is a separate case and is covered in section 1.
- No local storage, session storage or device fingerprinting used for tracking.
4. Clearing it
The tidiest way is to sign out, which ends the session at our end as well as removing the cookie from your browser.
You can also clear it from your browser. In every major browser the control is under settings, in a section named for privacy, cookies or site data, and you can clear cookies for a single site rather than all of them. Browsers can also be set to block or delete cookies generally.
5. Changes to this policy
The date at the top of the page is the date of the current version. If we ever set another cookie, this table changes first, and anything that is not strictly necessary would be asked for rather than assumed.
6. Contact
Questions about this policy go to [email protected]. The privacy notice covers the rest of what we hold and why, and the terms of service set out the agreement itself.