Cookie Policy
Every cookie Parry sets, what it does, how long it lives, and why it is strictly necessary. No tracking, no ad pixels.
Effective May 15, 2026
Cookies we set
| Name | Purpose | Category | Duration | Party |
|---|---|---|---|---|
| ss_session | Opaque session token after GitHub OAuth sign-in. Required to keep you signed in and to authorize API calls. The value is random; no personal data is encoded in it. | Strictly necessary | 30 days | First-party |
| ss_active_org | Remembers which organization you last selected so dashboards and scan pages render in the right scope across navigations. | Strictly necessary | Session / persistent until cleared | First-party |
Local storage
Parry also stores a small value in your browser's localStorage. It is not a cookie and is never sent to our servers.
- parry-cookie-consent (localStorage)
Records your response to the cookie banner so we don't show it again. Stored locally in your browser; never transmitted to Parry.
Categories
- Strictly necessary
Required to deliver the service you asked for. Cannot be disabled — without them sign-in and org selection do not work. No consent is required under GDPR.
- Functional, analytics, marketing
Parry does not set any. We do not run product analytics, ad pixels, fingerprinting, A/B testing, or session replay in the customer-facing app today. If that ever changes you will see the banner re-prompt with an explicit opt-in.
How to control cookies
You can clear or block cookies in your browser settings. Blocking ss_session will sign you out and prevent sign-in. Blocking ss_active_org will force you to re-pick an organization each visit. The rest of the product continues to work.
To revisit your cookie banner choice, clear the parry-cookie-consent key from your browser's localStorage. The banner will appear again on next page load.
Questions?
Reach us at hello@parryai.dev. See also the Privacy Policy and Terms of Service.