Contents (7)
Every cookie the Platform sets, what it is for, how long it lasts and how to refuse the ones that are not essential.
What a cookie is
A cookie is a small file a site stores in your browser so it can recognise the browser on the next request. Some are deleted when you close the browser, others last a set number of days. Related technologies — browser local storage, for instance — do the same job, and this policy covers those too.
Strictly necessary cookies
These make the Platform work and cannot be switched off from inside it. Refusing them in your browser means you cannot sign in.
- Session and authentication cookies, set when you sign in, which keep you signed in as you move between pages and across our subdomains.
- A password-reset flag, set only during a reset, which sends you to the page where you set a new password.
- Short-lived sign-in state cookies, set for a few minutes when you connect a trading platform through its OAuth flow, which prove the request that comes back is the one we sent.
- A checkout hand-off cookie, kept for three days, which remembers the plan and billing cycle you picked so the choice survives signing up and confirming your email.
- A consent cookie, kept for a year, which records the choice you made on the cookie notice so it is not shown to you again. It holds that choice and nothing else.
- Cookies set by Stripe on its own checkout and billing pages, which secure the payment session. Stripe's own privacy and cookie notices govern those.
Attribution, referral and site-use cookies
These are not strictly necessary. They are first-party, they contain no advertising identifier and they are not shared with an ad network, but they exist to attribute a sign-up, so you should know about them.
- A referral cookie, kept for thirty days, set only when you arrive through an affiliate link. It records the referral code so the affiliate is credited and any referral discount is applied at checkout.
- A first-visit stamp, kept for thirty days and written only alongside the referral cookie. It records the code and the moment you first arrived through that link, because the thirty days run from your first visit: coming back through the same link later does not restart them.
- A campaign cookie, kept for thirty days, set only when you arrive with campaign parameters in the link. It records the campaign that first brought you, and a later campaign does not replace it, so we can tell which of our own content works.
- A first-visit record, kept for thirty days and written once: when you accept these cookies, or on your first visit after accepting them. It holds the page you first arrived on (the page only, not its full address), the name of the site that sent you, if one did, and when you arrived, so we can tell how people find us. It holds no search term and nothing that identifies you.
- A visitor cookie (_vid), kept for thirteen months, set only after you accept. It holds a random number and nothing else, so we can recognise your browser when you come back and see which pages people read before they sign up or subscribe. It is first-party: it is set by us, for our own sites, and is never shared with anyone.
- A visit cookie (_sid), set only after you accept, which lapses thirty minutes after your last page view. It holds a random number so the pages of one visit can be grouped together.
Analytics and advertising
We do not run a third-party analytics suite or any advertising pixel, and we do no cross-site tracking. We count the pages visitors view on our own sites. Without your consent that count uses no cookie and keeps nothing that identifies you: no network address and no device identifier, only the page, the name of the site that sent you, the campaign in the link, the kind of device, the browser's name, the country and the time. If you accept, the visitor and visit cookies above let us connect the pages of one visit, and your later visits, so we can see which pages help people decide; if you then create an account, those page views are linked to it. If your browser sends a Global Privacy Control or Do Not Track signal, we treat it as a refusal of these two cookies, whatever you chose on the notice. We also count visits that arrive through a partner's link or one of our tagged campaign links, as a total per day.
Your choices
Every browser can block or delete cookies, per site or entirely, and can be set to clear them when you close it. Blocking the strictly necessary cookies will stop you signing in. Blocking the attribution cookies costs you nothing, though an affiliate who sent you may not be credited and a referral discount may not apply automatically. Your notice preference is stored in your browser, so clearing site data brings the notice back. Refusing the attribution and site-use cookies, or withdrawing your consent later by clearing site data and choosing Reject, removes the visitor and visit cookies; the pages you view are then counted without identifying you.
Changes
We will update this policy if the set of cookies changes, and the date above tells you when it was last revised.
Who sets these cookies
TradinSolutions is the trading name of a sole trader — an eenmanszaak under Dutch law, which means an individual rather than an incorporated company — registered with the Netherlands Chamber of Commerce (Kamer van Koophandel) under KvK number 42152786, at Tonkensstraat 55, 9723 ZV Groningen, Netherlands. We are the controller for the first-party cookies described here; the Privacy Policy explains what we do with what they collect. For anything ordinary, write to contact@tradinsolutions.com or open a ticket at the support desk in your dashboard. For a formal notice, a legal question or anything you want on the record, write to legal@tradinsolutions.com, or by post to TradinSolutions, Tonkensstraat 55, 9723 ZV Groningen, Netherlands.