Last updated June 11, 2026
Cookie Policy
How FailPack uses browser storage for secure sign-in, trusted devices, dashboard sessions, and product operation.
1. Overview
FailPack uses cookies, local storage, and similar browser technologies to keep users signed in, protect accounts, remember product state, and operate the dashboard.
We keep this usage focused on authentication, security, billing flows, preferences, and reliability. We do not need advertising cookies to provide the core product.
2. Essential cookies and storage
- Authentication and refresh-session state for the dashboard.
- CSRF, OAuth, CLI device login, and trusted-device state used to protect sign-in flows.
- 2FA flow state, temporary login verification state, and session rotation support.
- Workspace, dashboard, and UI preferences that help the app load the correct view.
- Security, rate-limit, fraud-prevention, and abuse-detection signals.
3. Third-party cookies
OAuth providers and payment providers may set their own cookies when you sign in through Google or GitHub, open checkout, manage billing, or complete payment flows. Those cookies are governed by the relevant provider's policies.
4. Analytics
FailPack may use privacy-conscious analytics or operational metrics to understand reliability, page performance, conversion, and product usage. When used, analytics should be configured to avoid collecting report content or uploaded artifacts.
5. Managing cookies
You can block or delete cookies through your browser settings. Some parts of FailPack, including sign-in, 2FA, dashboard access, checkout, and trusted-device behavior, may stop working if essential cookies or local storage are disabled.
6. Changes
We may update this Cookie Policy as the product and infrastructure change. The latest version is always available on this page.