Cookie Policy
Effective: November 14, 2026
This page describes the cookies and similar technologies that Decka uses, what they are used for, and how you can control them. It supplements our Privacy Policy.
What is a cookie?
A "cookie" is a small text file that a website places on your device. Some cookies are required for the site to function; others are optional and used for product improvement.
Categories we use
We organize the cookies we set into four categories:
- Strictly necessary cookies are required to operate the Service — for example, to keep you signed in, to protect against cross-site request forgery during sign-in, and to remember your cookie preferences. These cookies do not require consent under applicable privacy laws.
- First-party measurement cookies are set by Decka itself and read only by Decka. They record which marketing page or email brought you to us, or which of two versions of a page you were shown, so we can tell which of our own pages and messages work. They are never shared with an advertising network, are not used to build a profile, do not follow you to other websites, and carry no name or email address — only a short label of our own and, for email, an opaque identifier for the message that was sent.
- Advertising measurement cookies are set by Decka, but unlike the category above, what they hold IS sent to an advertising network. Today there is exactly one: if you arrive from an advert, it stores the click identifier that network put on the link, so that if you go on to create an account we can tell them their advert worked. It holds nothing of ours about you — no name, no email address, not even a label of our own — and we send that network nothing else. Because it shares data with an advertising network, it is treated like the optional analytics cookies below: in regions with an opt-in regime it is set only if you click "Accept" on the cookie banner.
- Optional analytics cookies are used to understand how the Service is used so we can improve it. They are off by default and only set if you click "Accept" on the cookie banner. Associated browser and authenticated server-side product analytics are also sent only while that explicit choice is current.
The private history of how you use Decka, described in our Privacy Policy, sets no cookie and stores nothing in your browser: it is kept on our servers, from requests your signed-in session already makes.
Cookies we set
| Name | Purpose | Category | Duration |
|---|---|---|---|
slidoodle-access-token |
Keeps you signed in (HttpOnly, Secure, SameSite=Lax) | Strictly necessary | 1 hour |
slidoodle-refresh-token |
Re-issues your access token when it expires (HttpOnly, Secure, SameSite=Strict) | Strictly necessary | 90 days |
slidoodle-pending-auth |
Holds the temporary token used during email verification (HttpOnly, Secure, SameSite=Lax) | Strictly necessary | 10 minutes |
slidoodle-auth-flash |
Temporarily carries a sanitized sign-in error between authentication pages (HttpOnly, Secure, SameSite=Lax) | Strictly necessary | 1 minute |
slidoodle-pending-code |
Remembers which address a one-time sign-in code was emailed to while you enter it (HttpOnly, Secure, SameSite=Lax, signed) | Strictly necessary | 10 minutes |
slidoodle-password-fallback |
Remembers, for the address you just typed, that the sign-in page offered you a password field instead of an emailed code, so only that page can accept one (HttpOnly, Secure, SameSite=Lax, signed) | Strictly necessary | 10 minutes |
slidoodle-gsi-nonce |
Ties a "Sign in with Google" prompt to your browser, so a Google credential shown to you cannot be replayed from anywhere else (HttpOnly, Secure, SameSite=Lax) | Strictly necessary | 1 hour |
slidoodle-gsi-signed-out |
Set when you sign out, so Google's automatic sign-in does not sign you straight back in (Secure, SameSite=Lax) | Strictly necessary | 5 minutes |
g_state |
Set by Google's sign-in script on our signed-out pages to remember that you dismissed the "Sign in with Google" prompt, so it is not shown again for a while. Google sets and expires it. | Strictly necessary | Set by Google |
slidoodle_mcp_consent |
Binds a short-lived MCP authorization approval to the signed-in user, requested client, redirect URI, scopes, and PKCE challenge (HttpOnly, Secure, SameSite=Strict) | Strictly necessary | 5 minutes |
decka_start_claim |
Set when you press a button such as "Try it free" or "Use this template" while signed out, so that what you chose is made for you once you sign up. Holds a signed record of that choice and the page it was on, and nothing about you. Only the page that finishes the request reads it (HttpOnly, Secure, SameSite=Strict) | Strictly necessary | 7 days |
decka_idea_template |
The earlier form of the cookie above, set when you press "Use this template" on an Ideas page while signed out, so that template is made for you once you sign up. Holds a signed record of which template you chose, and nothing about you. Only the page that finishes the request reads it (HttpOnly, Secure, SameSite=Strict) | Strictly necessary | 7 days |
decka_template_pending |
Set beside either of the two cookies above, so the dashboard knows after you sign up that something is waiting to be made. Holds a flag, or a random value that is also put into the address you are sent back to after signing up, so that what you chose is made without asking you again only on that return. It holds nothing about you (HttpOnly, Secure, SameSite=Lax) | Strictly necessary | 7 days |
slidoodle-personal-workspace |
Set when you open a link to your personal workspace while you are signed in to an organisation, so Decka shows your personal workspace. Holds your session's identifier and nothing else, and stops applying when you switch organisation, sign out or sign in again (HttpOnly, Secure, SameSite=Lax) | Strictly necessary | 90 days |
decka_participant |
Set when you open a join page, the page a session's code or QR code leads to, or the first time you react to a presentation shared by link, so that Decka recognises your phone or browser as the same participant: it can get back in as itself, its votes on questions count once, its reactions are limited per device, and what it asks us to email, such as a copy of its results, cannot be claimed from another device. Holds a random identifier we issue, with our signature, and nothing about you. Renewed each time you open a join page, and replaced when you choose "join again as someone else" (HttpOnly, Secure, SameSite=Lax) | Strictly necessary | 90 days |
decka_composer_participant |
Set when you open the join page of a Classroom Activity or of an activity made in Decka Studio, the page its code or QR code leads to, so that Decka recognises your phone or browser as the same player in that room: after a reload or a lost answer it gets back the seat it already holds rather than taking a second one, and a report it makes of a Studio activity counts once. Holds a random identifier we issue, with our signature, and nothing about you; a room is given only a one-way fingerprint of it, different in every room. Renewed each time you open such a page (HttpOnly, Secure, SameSite=Lax) | Strictly necessary | 90 days |
decka_mic_drop |
Set when you write a line in Mic Drop's free Daily duel, so the page can show you your lines and their results without an account, keep your own lines out of the pairs you judge, and move your lines to your account if you sign in. Holds a random identifier we issue, with our signature, and nothing about you (HttpOnly, Secure, SameSite=Lax) | Strictly necessary | 90 days |
decka_suspect_daily |
Set when you open a case's line-up in Draw the Suspect's free Daily line-up, so the page can carry on where you left off and keep your streak without an account. Holds a signed record of the day's picks, when each was made, and your streak, and no identifier. Written again each time you open a line-up or pick a face (HttpOnly, Secure, SameSite=Lax) | Strictly necessary | 90 days |
slidoodle-cookie-consent |
Records your cookie banner choice so we don't ask again (SameSite=Lax) | Strictly necessary | 12 months |
slidoodle-campaign |
Remembers which campaign link or landing page brought you to Decka, so we can measure which of our pages lead to an account, and which of our pages your visit has already been counted on, so each of them counts you once (SameSite=Lax, Secure, readable by our own scripts) | First-party measurement | 30 days |
decka_experiments |
Set when you open a page of our public site while we are comparing two versions of it, and you are not signed in, so that you keep seeing the same version of that page and so that we can count, in total, how many people shown each version went on to sign up and to use Decka. For each such test it holds a signed record of which version you were shown, which stage of the test that was and when you were shown it; once the page has loaded, the day, whether your screen counted as a phone, tablet or computer, and whether our systems took the visit for an automated program; and whether you have pressed a sign-up button. It holds no identifier and nothing about you. If you go on to create an account, we keep with it which version you were shown, so that we can count whether those accounts go on to run an activity; that note is deleted with the account. It is set whatever you chose on the cookie banner, and is never shared with anyone. It lasts no longer than 30 days from the day you were first shown a version, and later visits do not extend it (HttpOnly, Secure, SameSite=Lax) | First-party measurement | 30 days |
slidoodle-email-click |
Set only when you click a link in a Decka email, so we can tell that the email brought you back. Holds an opaque identifier for that message and nothing about you (HttpOnly, Secure, SameSite=Lax) | First-party measurement | 7 days |
slidoodle-rdt |
Set only when you arrive from a Reddit advert, so that if you go on to create an account we can tell Reddit their advert worked. Holds the click identifier Reddit itself put on the link, and nothing about you. In opt-in regions it is set only after you accept (HttpOnly, Secure, SameSite=Lax) | Advertising measurement | 7 days |
| OAuth state / nonce cookie | CSRF protection during single-sign-on flows (HttpOnly, Secure) | Strictly necessary | ~10 minutes |
PostHog cookies (ph_*) |
Product analytics, and masked session recordings of the dashboard where your Accept was given on or after October 19, 2026 — only set if you click "Accept" on the cookie banner | Optional analytics | Up to 12 months |
| Stripe cookies and similar browser storage | Payment security, fraud prevention, and payment authentication when a Decka billing form loads Stripe.js | Strictly necessary for billing | Set by Stripe and varies by technology |
Browser storage. Some features keep a small value in your browser's own storage rather than in a cookie. For example, a phone that joins a session keeps the identifier it was given and the name typed into the join form, so that it can get back in without typing it again. A start link that works without signing in keeps its key in the storage of the tab it was opened in, which the browser clears when that tab closes. A signed-in browser remembers which time zone it last reported for your account, so that it reports it again only when it changes. And Draw the Suspect's free Daily line-up keeps the day's sketches in your browser, for the reveal and the share card; they are never sent to us. Each of these is strictly necessary for the feature that sets it. The screens of an activity made in Decka Studio run on deckastudio.com, a separate domain of ours. It sets no cookie and keeps nothing in your browser, and the screens it serves cannot either. PostHog's browser storage, used only after you accept analytics, is described below.
Managing your choice
You can change your optional-cookie choice at any time using the Cookie settings link in the footer. Reopening the banner replaces your earlier choice.
Refusing optional cookies does not block essential cookies — without those, you cannot stay signed in.
You can also block or delete cookies using your browser's settings. Doing so may prevent parts of the Service from working as expected.
Managing first-party measurement cookies
The three FIRST-PARTY measurement cookies above — slidoodle-campaign, decka_experiments and slidoodle-email-click — are set without a banner prompt, because they exist only to attribute our own pages and emails, and the version of a page we showed you, to our own results and are never shared with anyone. The advertising measurement cookie slidoodle-rdt is different: because its contents are sent to the advertising network that referred you, in regions with an opt-in regime it is set only after you accept. You can delete or block any of them in your browser's settings at any time; nothing on the Service stops working if you do. If you do not want to receive marketing email from us at all, every marketing message carries a one-click unsubscribe link, and your email preferences can be changed from your account settings.
Third parties
PostHog sets optional analytics cookies only after you accept analytics. Session recording, which applies only to an Accept given on or after October 19, 2026, uses those same ph_* cookies and PostHog's browser storage, so it adds no cookie of its own. Stripe may set strictly necessary payment-security cookies or similar storage when you open a Decka billing form. Google's sign-in script runs on our signed-out pages to offer "Sign in with Google"; it sets the strictly necessary g_state cookie listed above and nothing else, which is why it runs before you have answered the cookie banner. It is not loaded on participant pages, and not for browsers that send a Global Privacy Control signal except on the sign-in and sign-up pages themselves, where signing in with Google is the purpose of the visit. See the Subprocessors page for the current providers. We do not allow advertising networks to set cookies on the Service.
Changes
We may update this page when we add, remove, or change a cookie. Material changes will be reflected in the version metadata at the top of this page.
Contact
Questions about this policy can be sent to legal@decka.dev.