Cookie Policy
Last updated 15 October 2026.
Brigaly uses as little browser storage as it can: only what keeps you signed in and carries you from one sign-in step to the next.
1. What we use
A cookie is a small file a website stores in your browser. Brigaly uses cookies only to keep you signed in securely. These are strictly necessary: without them you could not sign in, so they do not need your consent.
During sign-in and sign-up we also keep a few details in your browser's session storage — such as the email address a code was sent to — so the next screen knows where you are. Session storage is cleared when you close the tab.
2. The full list
| Name | Type | Purpose | Lasts |
|---|---|---|---|
| brigaly2.session-token | Cookie, strictly necessary | Keeps you signed in | Up to 30 days |
| better-auth.session_data | Cookie, strictly necessary | A short-lived copy of your session, so pages load without checking the database each time | 5 minutes |
| brigaly.pending-signin | Session storage | The email a sign-in code was sent to, between the email and code screens | Until the tab closes |
| brigaly.start | Session storage | Your choice while creating or claiming an institute, kept across sign-in | Until the tab closes |
If you sign in with Google, Google sets its own cookies on its sign-in pages, under Google's privacy policy.
3. What we do not use
No advertising cookies, no analytics or tracking cookies, and no third-party trackers on Brigaly pages. If that ever changes, we will update this page first and ask for your consent where the law requires it.
4. Your choices
You can delete cookies in your browser settings at any time; you will simply be signed out. Blocking them altogether will stop sign-in from working.
5. Contact
Questions: help@brigaly.com. See also our Privacy Policy.