COOKIE POLICY
Last Updated: 2026-06-12
Scope
This Cookie Policy explains how genjury ("we," "us," or "our") uses cookies and similar client-side storage technologies, including localStorage and sessionStorage, on our public website, waitlist, authenticated product, checkout flow, and related services. It focuses on storing or accessing information on your device.
This policy does not describe all personal data processing that may happen after data is collected. For broader privacy information, including server-side logs, first-party server-side product events, AI processing, analytics events, and billing records, please also see our Privacy Notice.
How We Use These Technologies
We use these technologies for two purposes:
- Strictly necessary technologies, which support authentication, security, session continuity, checkout continuity, and remembering your choice about optional analytics storage.
- Optional analytics technologies, which help us understand public website and product usage after valid consent.
Optional analytics are not required to use core account, waitlist, checkout, or product functions.
Cookie And Storage Inventory
| Name / Pattern | Provider | Storage Type | Purpose | Typical Retention | Consent Required |
|---|---|---|---|---|---|
| Session / __Host-Session | genjury | First-party cookie | Keeps you signed in, stores your authenticated session, and supports token refresh when authenticated product routes are active | Up to 14 days, or cleared sooner on sign-out or expiry | No |
| cookie_consent | genjury | localStorage or first-party cookie | Remembers whether you accepted or rejected optional analytics on the public site | Until you change it or clear browser storage | No |
| cf_clearance | Cloudflare | First-party cookie | Remembers that a Cloudflare managed security challenge was passed when a challenge is triggered | Up to 30 minutes based on the current challenge passage setting | No |
| ph__posthog | PostHog | localStorage and/or cookie | Stores analytics identifiers and related state, such as distinct ID, session or device state, referrer or campaign information, and configuration state when analytics storage is enabled | Up to 365 days by default unless configured shorter | Yes |
| ph__window_id and related PostHog session keys | PostHog | sessionStorage | Maintains tab- or session-scoped analytics state while analytics is active | Current browser session | Yes |
| Paddle checkout cookies and storage | Paddle | Third-party cookies and storage on Paddle-controlled domains | Supports checkout, payment security, fraud prevention, tax calculation, and subscription management | Set by Paddle according to its policies | Determined by Paddle |
| Google sign-in cookies | Third-party cookies on Google-controlled domains | Supports Google authentication and account selection | Set by Google according to its policies | Determined by Google | |
| Apple sign-in cookies | Apple | Third-party cookies on Apple-controlled domains | Supports Apple authentication and account selection | Set by Apple according to its policies | Determined by Apple |
Analytics And Identification
We use PostHog with the EU ingestion host https://eu.i.posthog.com when optional analytics is active.
The intended optional analytics scope is minimal: basic page views and client-side product usage events. We do not use session replay, heatmaps, broad autocapture, advertising pixels, or cross-site marketing tracking for this purpose.
If you use the authenticated product and analytics is active, analytics events may be associated with your account or workspace using a pseudonymous identifier. We avoid sending customer profile text, product change descriptions, simulation reactions, or report content in analytics payloads.
First-party server-side product events are processed for all users. They are generated by the Service backend, are not themselves cookies or browser storage, and do not depend on optional analytics consent. They are described in our Privacy Notice.
Your Choices
Where optional analytics is active, the consent interface lets you accept or reject analytics storage. Strictly necessary technologies remain active because they are used for security, authentication, checkout, session continuity, or to remember your choice.
You can also block or delete cookies and local storage through your browser settings. If you previously accepted analytics storage and want to reverse that stored choice with the current implementation, use the available consent controls, clear site storage in your browser, or contact us using the details in our Privacy Notice.
Legal Framework
Strictly necessary technologies are used under the ePrivacy exemption because they are necessary to provide security, authentication, checkout, session continuity, or to remember your choice about optional technologies.
Optional analytics storage requires consent. We do not rely on legitimate interest to place optional analytics cookies or similar device identifiers.
Where personal data is processed as a result of these technologies, the applicable GDPR or UK GDPR legal bases and other privacy information are described in our Privacy Notice.
Updates To This Policy
We may update this Cookie Policy when our technologies, vendors, product features, or legal requirements change. The latest version will be published on this page with a new "Last Updated" date.
Additional Information
For more information about how we process personal data beyond device storage and access, please refer to our Privacy Notice.
Contact Information
If you have questions about this Cookie Policy, contact us using the details in our Privacy Notice or Imprint.