Cookies and local storage
Bridge Suite only uses cookies and local storage that are needed for the Service to work: to keep you logged in, to remember your settings and to let the tools work. There are no analytics, tracking or advertising cookies, and we do not build profiles. That is why we do not show a cookie banner.
Cookies
| Name | What it does | How long |
|---|---|---|
bridge_token | keeps you logged in across suite.briiidge.dev and the tool subdomains (cannot be read by scripts) | 30 days, or until you log out |
__Host-bridge_game | keeps you logged in on games.briiidge.dev | 30 days, or until you log out |
brv_… | remembers that you entered the password of a shared video | 14 days |
Local storage in your browser
The Suite stores some things in your browser (localStorage and IndexedDB). They stay on your device; we do not read them for tracking.
- your login token for the tool you have open (
chat-token), and a short signal when you log out in another tab; - your language and theme, and layout and tool preferences (for example the last tools you opened, or settings of an editor);
- the name you use in shared editing sessions, and game settings and progress;
- in Talk with end-to-end encryption: your encryption keys (IndexedDB), so only your devices can read those messages;
- an offline copy of the dashboard shell (service worker), without your data.
You can delete all of this at any time via your browser settings. You will then be logged out and your preferences will be reset.
Third parties
- Google Fonts: pages load fonts from Google; Google sees your IP address but sets no cookies for this.
- YouTube: when you play a stock clip in Motions, the video is loaded from YouTube in its privacy-enhanced mode (youtube-nocookie.com). YouTube then sees your IP address and may store its own data in your browser under its own policy.
- Your own API keys: AI and media providers you use with your own key do not set cookies through the Suite.
More about how we handle personal data: Privacy Policy.