This notice explains how PairRail Atlas and its providers use cookies and similar technologies (local storage, session storage). It supplements our Privacy Policy.
What we use today
Essential / authentication
- Firebase Authentication (Google sign-in / GitHub sign-in) may set cookies or use browser storage to complete OAuth, maintain signed-in state, and protect against abuse. These are required for the seller console to function.
- PairRail console session storage: the browser may keep short-lived values such as ID tokens, auth mode flags, and workspace session markers in
sessionStorageso you remain signed in during a tab session. These are cleared when you log out or when the browser session ends, depending on the key.
Security and delivery
Cloudflare or hosting providers may set strictly necessary cookies related to security, load balancing, or bot management when you access pairrail.com.
What we do not currently rely on
PairRail does not currently operate a separate third-party marketing analytics or advertising pixel suite on the Atlas marketing site. If we add optional analytics later, we will update this notice and, where required, request consent.
Why we use them
- Authenticate sellers and operators and keep console sessions working.
- Secure the Service and reduce fraud or abuse.
- Remember basic UI session state needed for workspace use.
Your choices
Most browsers let you block or delete cookies and clear site storage. Blocking authentication cookies or storage will prevent sign-in and console use. You can also revoke Google or GitHub app access from those providers’ account settings.
More information
See the Privacy Policy for broader data practices, and contact support@pairrail.com with questions.