Cookie Policy
Version 2.0 · Last updated 23 September 2026
This policy explains the cookies and similar technologies used on tidehawk.co, app.tidehawk.co and docs.tidehawk.co. It should be read with our Privacy Policy.
1. Our approach
We use only cookies and browser storage that are strictly necessary to provide the service you have asked for: keeping you signed in, protecting forms and sign-in flows, and remembering a preference you have set. We do not use analytics, advertising or social-media cookies, we do not load third-party tracking scripts, and we do not use cookies to profile you or follow you across other websites.
Because every item below is strictly necessary, the Privacy and Electronic Communications Regulations 2003 do not require us to ask for your consent to it, and we do not show a cookie banner.
2. Cookies we set
| Name | Purpose | Set when | Lasts |
|---|---|---|---|
Session cookie (authjs.session-token or __Secure-authjs.session-token) |
Keeps you signed in to the application | You sign in | 7 days, or until you sign out |
authjs.csrf-token and authjs.callback-url |
Protect the sign-in and sign-out forms against cross-site request forgery | You visit a sign-in page | The browser session |
psa_oauth_state |
Secures the round trip to your PSA when you connect one that uses OAuth | You start connecting a PSA | 10 minutes |
sa-pending-login |
Holds the first step of a Tidehawk staff sign-in while the second factor is checked | Staff sign-in only | Minutes |
sa-session-token |
Keeps a member of Tidehawk staff signed in to the administration console | Staff sign-in only | Until sign-out or expiry |
All of these are first-party cookies, marked HttpOnly so that scripts cannot read them, Secure so that they are sent only over HTTPS, and SameSite so that other sites cannot send them.
3. Browser storage
The application uses your browser's local storage, which is not a cookie and is never sent to our servers, for two things: whether you have dismissed the first-time tour of the dashboard, and your choice of light or dark theme. Neither identifies you.
4. Third-party services
When you subscribe you are taken to a payment page hosted by Stripe, our payment provider. Stripe sets its own cookies on its own domain for fraud prevention and to operate the payment page; they are covered by Stripe's privacy policy. We do not control them and they are not set on our domains.
The documentation site's search runs entirely in your browser and sets no cookies.
5. Managing cookies
You can block or delete cookies in your browser's settings. Because the cookies above are needed to sign in, blocking them will stop you using the application, although you can still read the website and documentation. Browser help pages explain how: Chrome, Firefox, Safari, Edge.
6. Changes
If we ever introduce a cookie that is not strictly necessary, we will update this policy and ask for your consent before setting it. Questions: privacy@tidehawk.co.