Skip to content

Cookie policy

Cookies and similar storage

This page lists every cookie and browser storage key that precedent.biz and the Precedent app set, what each one is for, who sets it and how long it lasts. It accompanies the privacy policy. Last updated 18 November 2026.

Cookies we set

Visiting the public pages sets no cookies. The cookies below appear only once you sign in or start signing in. All of them are first-party, set by Precedent on its own domain, marked HttpOnly so page scripts cannot read them, and sent only over HTTPS on the hosted service. Browsers show the hosted service’s cookies with a __Secure- or __Host- prefix in front of the names listed here.

CookiePurposeProviderLifetime
authjs.session-tokenKeeps you signed in. Holds a signed token that identifies your account and how you signed in.Precedent (Auth.js)30 days, or until you sign out
authjs.csrf-tokenProtects the sign-in and sign-out forms against cross-site request forgery.Precedent (Auth.js)Until you close your browser
authjs.callback-urlRemembers the page to return you to after you sign in.Precedent (Auth.js)Until you close your browser
authjs.pkce.code_verifierSecures sign-in through Google or your company’s single sign-on by proving the browser that started the sign-in is the one finishing it.Precedent (Auth.js)15 minutes
authjs.stateTies the response from Google or your single sign-on provider to the sign-in you started.Precedent (Auth.js)15 minutes
authjs.noncePrevents a sign-in response from an OpenID Connect provider being replayed.Precedent (Auth.js)Until the sign-in completes or you close your browser
precedent_githubHolds your GitHub sign-in, encrypted, while you choose GitHub accounts and repositories. Set when you sign in with GitHub from Precedent.Precedent8 hours
precedent_github_flowProtects the sign-in with GitHub while it is in progress.Precedent10 minutes
vercel-flag-overridesLets a member of the Precedent team preview a feature flag in their own browser. Never set for visitors or customers; the app only reads it if it is present.Vercel ToolbarUntil the team member clears it

Email sign-in links do not use a cookie at all: the link carries a one-time code that expires after 15 minutes. Signing out deletes the session cookie immediately.

Cookies set by Paddle for payments

Paddle is our merchant of record. Its checkout script loads from Paddle’s servers only when a workspace administrator opens Settings, Billing in a workspace on the hosted service. Nothing from Paddle loads on the public site, on the sign-in page or anywhere else in the app. Billing is not yet enabled on precedent.biz, so today the Billing tab and this script do not appear there.

CookiePurposeProviderLifetime
__cf_bmBot protection for Paddle’s checkout script, set on paddle.com by Paddle’s content delivery network when the script loads. It does not identify you to Precedent.Cloudflare, for Paddle30 minutes

When you open checkout, the payment form runs inside a frame served by Paddle, which sets its own cookies on paddle.com to run the checkout and detect fraud. Those are described in Paddle’s privacy policy, which links to its cookie notice. Precedent never receives your card details.

Browser storage

Browser storage is not a cookie, but it can be used in similar ways, so we list it here. Precedent uses one key.

KeyPurposeWhereLifetime
precedent:ask:<workspace>:<you>:<area>Holds your Ask AI conversation so it survives a page refresh in the same tab. The server keeps no copy of the transcript. The key includes your user id so that a different person signing in on the same tab never sees your thread.sessionStorage, first-partyUntil you close the tab

We do not use local storage, IndexedDB, fingerprinting or any other technique to recognise you across sites or across visits.

What else loads from third parties

precedent.biz is served through Cloudflare, which protects the site from abuse and hides email addresses in the page source from scrapers with a small script served from our own domain. Cloudflare sets no cookie on normal visits. If it ever challenges a request it suspects is automated, the challenge may set a short-lived security cookie such as cf_clearance or __cf_bm on precedent.biz.

The typefaces are files served from our own domain, so your browser does not contact Google Fonts or any other font service when a page renders.

Errors that happen in the page are not reported to any outside service. The integrations your workspace connects, such as Slack, Linear or GitHub, run on their own sites under their own policies.

How to control cookies

Your browser lets you view, block and delete cookies and site data, usually under its privacy or site settings. Deleting Precedent’s cookies signs you out; blocking them stops you from signing in at all, because the session and sign-in protection cookies are how the service knows who you are. Nothing else about the site depends on cookies, and the public pages work with cookies blocked entirely.

Questions about this page, or about anything you see your browser storing while using Precedent, go to [email protected]. If you spot something that is not listed here, tell us: the list is meant to be complete.

Changes to this policy

We will update this page before any new cookie, storage key or third-party script appears, and revise the date at the top. Adding anything that is not strictly necessary would also add a consent banner that asks before it loads.

Discard unsaved changes?

Your changes have not been saved. Stay to keep editing, or discard them and leave.