Authentication & security
- FIRE_DOOR_SUITE — session cookie used for authentication and CSRF protection.
- firedoor_trusted_2fa — optional “trusted device” cookie used to remember a device for 2FA.
Cookie policy
How FireDoorApp uses cookies.
FireDoorApp uses cookies mainly to keep your session secure once you sign in and to support optional features like offline caching on devices.
- Marketing pages: we aim to serve these without setting session cookies for anonymous visitors.
- Signed-in workspaces: we use cookies to keep you authenticated and to help restore your workspace between sessions.
- Optional offline features: we use browser storage to cache assets and data for offline-friendly workflows.
Common cookies
Session
FIRE_DOOR_SUITE Used to keep you signed in and protect CSRF actions.Tenant restore
firedoor_tenant* Helps restore the correct workspace when your session expires.Trusted device
firedoor_trusted_2fa Optional cookie to reduce 2FA prompts on trusted devices.Cookie details
This is a practical description of the cookies FireDoorApp may set. Names and behaviour can evolve as the product changes.
Workspace continuity
- firedoor_tenant — remembers your last workspace key.
- firedoor_tenant_scope and firedoor_tenant_sig — help validate the tenant cookie payload.
Offline caching
- firedoor_cache_version — versions offline caches (e.g. after “Clear offline cache”).
- Browser storage may be used to cache assets/data for offline-friendly workflows.
Managing cookies
- You can clear cookies via your browser settings.
- Clearing session cookies will sign you out.
- For workspace support, sign in and use in-app Support.