Cookies

Which cookies Draft2Cut uses, what they do, and why the notice on the sign-in page asks for no consent.

Last updated 9 November 2026

1.In short

Draft2Cut uses strictly necessary cookies only — the ones without which the application does not work — plus one that remembers your chosen language and two anonymous first-party ones for visit statistics. There are no profiling cookies, no advertising cookies and no third-party analytics.

For these, the law requires information, not prior consent: that is why the notice on the sign-in page only informs, with a single button to close it. Asking permission for cookies you cannot refuse without giving up the service is a ritual that protects nobody.

2.The cookies, one by one

NameWhat it does
next-auth.session-tokenKeeps you signed in. It is httpOnly — JavaScript cannot read it — and lasts seven days. Without it you cannot stay logged in.
next-auth.csrf-tokenProtects forms against requests sent from other sites. Lasts for the browser session.
next-auth.callback-urlRemembers where you were heading when you were asked to sign in, so you can be taken back. Lasts for the browser session.
activeTenantIdRemembers which organisation you are working in, for people who belong to more than one. It is httpOnly and lasts thirty days.
d2c_vVisit statistics: a random code that tells one browser from another, to count visitors. It contains nothing about the person and is not derived from anything about them, it is not readable by JavaScript (httpOnly), and it lasts thirteen months.
d2c_sVisit statistics: a random code that groups the pages viewed into one visit. It expires thirty minutes after the last page.
draft2cut-localeRemembers the language you chose before signing in. Lasts one year. Account holders have this preference on their profile, so it follows them between computers.

The light or dark theme, and the fact that you closed the cookie notice (the draft2cut-cookie-notice item), do not use a cookie: they stay in the browser's local storage and are never sent to the server. Clearing local storage brings the notice back.

3.Visit statistics

To understand how the site is used we count page views, visits and visitors, with an average of the time spent and the country they come from. We do it ourselves, on our own site, without third-party tools and without passing the data to anyone.

We do not store the IP address, the account or the organisation; we store the path as the page's pattern (for example /projects/[id]/script, never the real identifier). For the first page of each visit we store where it came from: only the name of the referring site (never its full address) and the campaign labels in the link (utm_source, utm_medium, utm_campaign), reduced to letters, digits and a few symbols; no other parameter of the address is read. The country is told by the network provider. When the beta request form or a guide request form is sent, or an account is created, we also count that event, without the name, email or any other data of the person, together with the name of the referring site and the campaign labels of the visit, to know which origins bring requests and sign-ups. A page viewed while a member of the Draft2Cut team is signed in carries only a yes/no mark, never who it was, so that the team's own visits can be left out of the figures. The data is used only in aggregate form, by whoever administers the platform, and is deleted after fourteen months.

If the browser sends the «Do Not Track» or «Global Privacy Control» signal, we count nothing and set neither cookie. In any case you can delete them from the browser: the only effect is that your next visit counts as new.

4.How to control them

Every browser lets you inspect and delete a site's cookies. Deleting them signs you out and loses your language and active organisation; blocking them entirely makes signing in impossible, because the session cookie is what keeps you signed in.

5.If this changes

If third-party measurement tools or non-essential cookies are ever introduced, this page will be updated and the notice will become a prior consent request, with separate choices and nothing loaded before you answer, as the law requires. Questions: [email protected].