DATA ARMOURBack to Data Armour

Legal

Cookie Policy

Data Armour sets one cookie. It keeps you signed in. There is nothing else, and that is why you have not been asked to accept anything.

Last updated 17 September 2026

This page is not finished. It is still missing the registered company name, the registered office address, the grievance officer's name. Until those are filled in at app/lib/legal/company.ts, this page must not be treated as published. It should also be read by a lawyer qualified in India before it is.

The one cookie

Name
strix_session
What it does
Holds the reference to your signed in session, so that moving between pages does not sign you out.
What is in it
A random identifier. Nothing about you, nothing readable, and nothing that means anything away from our server.
How it is set
HttpOnly, so no script can read it. Secure, so it only travels over HTTPS. SameSite=Lax, so another site cannot make your browser send it.
How long
Until the session expires or you sign out, whichever comes first.
Whose it is
Ours. It is not shared with anybody.

What we do not set

  • No analytics. We do not measure you, and we have no analytics provider.
  • No advertising or retargeting cookies. We do not advertise to you anywhere.
  • No third party scripts. Nothing on our pages is loaded by anybody else.
  • No cross site tracking, no fingerprinting, no pixels.

If you signed in with Google or GitHub, their sign in page is theirs and sets their own cookies while you are on it. Once you are back with us, only ours applies.

Other things stored in your browser

Not cookies, but worth naming since they are stored on your machine just the same. Both are readable only by this site and neither is sent to us.

  • Your theme. Whether you chose light or dark, so the page does not flash the wrong one while it loads.
  • Small interface preferences, such as which filter you last used. Clearing your browser data resets them and nothing is lost.

Turning it off

You can block or delete the session cookie in your browser settings. The product will not work, because there will be no way for us to know you are signed in. There is no version of this that works without it, which is exactly what makes it a strictly necessary cookie rather than one you should be asked about.

More

What we do with the data behind that session is in the Privacy Policy. Questions go to our Grievance Officer.