Cookie policy
Last updated
ClueTrail uses only the cookies it needs to work, such as the one that keeps you signed in. We use no analytics, advertising or tracking cookies.
The short version
- We use only essential cookies, all of them on ClueTrail’s own website.
- Our sign-in cookies are set only when you sign up, sign in or confirm your email address.
- We use no analytics, advertising or social media cookies, and no tracking pixels.
- The quest studio keeps a backup of edits you have not saved yet in your own browser, until they are saved.
- When you pay for a reveal, the play page keeps a note of the payment in your browser until you close the tab.
- Stripe’s payment page and Google sign-in are on their own websites, which set their own cookies.
What cookies are
Cookies are small text files that a website stores in your browser, so it can recognise your browser when you come back, for example to keep you signed in.
UK law (the Privacy and Electronic Communications Regulations, known as PECR) says a website must ask for your consent before it stores cookies or similar technologies on your device, unless they are strictly necessary to provide a service you have asked for. All of our cookies are strictly necessary, so we do not need to ask for consent, and you will not see a cookie banner.
Cookies we set
All of these are first-party cookies, sent only to ClueTrail, and none of them can be read by scripts on the page. They are set only when you sign up, sign in or confirm your email address. The __Secure- at the start of some names means your browser only ever sends those cookies over a secure (HTTPS) connection.
Sign-in session
- Name
__Secure-ct.session_token- What it does
- Keeps you signed in, so the game knows which runs and reveals are yours.
- When it is set
- When you sign in, including through an emailed sign-in or confirmation link.
- How long it lasts
- Up to 30 days, renewed while you keep using ClueTrail. Signing out or deleting your account removes it.
Account type choice
- Name
ct_intended_role- What it does
- Remembers whether you chose to play quests or create them while you finish signing up.
- When it is set
- When you choose Play quests or Create quests on the sign-up page.
- How long it lasts
- 10 minutes, or until you confirm your account type.
Google sign-in security
- Name
__Secure-ct.state- What it does
- Protects Sign in with Google against forgery, by checking that the sign-in really started on ClueTrail (the OAuth state).
- When it is set
- When you choose Continue with Google.
- How long it lasts
- 5 minutes at most. It is removed when you come back from Google.
Email confirmation security
- Name
__Secure-ct.password_proof- What it does
- Shows that this browser knows your password while your email address is still unconfirmed, so confirming the address here keeps your password. It stops someone who signed up with your address before you from keeping access to it.
- When it is set
- When you sign up with a password, or enter your password before your email address is confirmed.
- How long it lasts
- 1 hour. Your browser sends it only when you confirm your email address.
Storage in your browser
Creators only: while you edit a quest, the quest studio keeps a copy of any change it has not saved yet in your browser’s local storage, under names that start with ct.studio.. If your connection drops, or your phone closes the page while you take a photo, the studio offers to restore those changes when you come back.
This backup stays on your own device: it is never sent to us by itself, and each change is removed as soon as it is saved. It is strictly necessary for the editor you chose to use, so it needs no consent.
Players: when you pay for a reveal, the play page keeps a short note in this tab’s session storage, under the name ct.checkout, while you are on Stripe’s payment page: which run and clue you are paying for, and when you left. When you come back, it uses the note to show you the right message about your payment. It also remembers which payment messages you have closed, under ct.payment-notices, so they do not show again.
Your browser deletes both when you close the tab. They are never sent to us, and they are strictly necessary for the payment you asked to make, so they need no consent.
Cookies on other websites
Two steps happen on other companies’ websites, which set their own cookies under their own policies:
- Paying for a reveal. Stripe’s secure checkout page runs on Stripe’s website. Stripe sets cookies there, for example to prevent fraud, as explained in its cookie policy.
- Sign in with Google. If you choose it, you sign in on Google’s website, which uses Google’s cookies, as explained in its privacy policy.
We do not control these cookies and cannot read them.
No analytics or advertising
We do not use analytics or advertising cookies, tracking pixels, fingerprinting or similar technologies, and our pages load no advertising or analytics scripts from other companies. To see how people find ClueTrail, we look at our server logs, for example which website linked to us, which needs no cookies. Our privacy policy explains what those logs contain.
Controlling cookies
You can see and delete cookies, or block them for any website, in your browser’s settings. Most browsers explain how in their help pages, usually under privacy or site data.
If you block ClueTrail’s cookies, you can still read our pages, but you will not be able to sign in, play or create quests. Signing out removes the sign-in session cookie.
Changes to this policy
If we ever want to use a cookie that is not strictly necessary, we will ask for your consent first and update this page. The date at the top of this page shows when it last changed.
Contact us
If you have a question about cookies, please email us at info@nlsql.com.