Cookie Policy

This Cookie Policy explains how Keypra uses cookies, localStorage, and similar client-side technologies when you visit or use the Service. For simplicity, this page refers to these technologies together as "cookies and similar technologies."

Keypra uses a limited set of strictly necessary technologies to run the Service securely and to remember basic user choices. Keypra also offers optional analytics and marketing settings that remain off until you choose to enable them.

Keypra does not use browser fingerprinting. Keypra does use four named third-party technologies: Google Analytics 4 for aggregate audience measurement (described in Section 4 below, gated behind Analytics consent), and the Google Ads conversion tag, the LinkedIn Insight Tag, and the X (Twitter) Pixel for advertising measurement (described in Section 5 below, gated behind Marketing consent). None of them load, and none of their cookies are set, unless you grant the matching consent — and all four are hard-disabled for California visitors and anyone sending the Global Privacy Control signal.

Keypra currently uses the following categories of cookies and similar technologies:

Name / category	Provider	Purpose	Necessary
sb-*-auth-token	Keypra / Supabase	Maintains the signed-in session and related authentication state	Yes
theme	Keypra	Remembers the visitor's display preference, such as light or dark mode	Yes
cookie_consent	Keypra	Records the visitor's cookie category choices	Yes
Google Analytics 4 (gtag.js, G-Y8FE3QV5RG)	Google Ireland Ltd / Google LLC	Aggregate audience measurement: page views, sessions, traffic sources, approximate region	No — Analytics consent required
Google Ads tag (gtag.js, AW-18144700120)	Google Ireland Ltd / Google LLC	Conversion tracking for paid-search and display campaigns	No — Marketing consent required
LinkedIn Insight Tag (Partner ID 10229937)	LinkedIn Ireland Unlimited Company	Conversion tracking and reporting for LinkedIn ad campaigns	No — Marketing consent required
X (Twitter) Pixel (ID rcjxd)	X Corp	Conversion tracking and reporting for X ad campaigns	No — Marketing consent required

Storage type	Duration
localStorage and/or session storage used by the authentication client	Until sign-out, session termination, or token rotation
localStorage (theme)	Until changed or cleared by the user
localStorage (cookie_consent)	12 months, unless changed earlier
Server-side consent records	Up to 12 months from the relevant consent event, unless renewed, withdrawn, or deleted earlier
Google Analytics cookies (_ga, _ga_*)	2 years, only set once Analytics consent is granted; cleared immediately on withdrawal
Google Ads cookies (ad_storage, ad_user_data, ad_personalization)	Up to 13 months, only written once Marketing consent is granted
LinkedIn cookies (li_gc, lidc, bcookie, bscookie, UserMatchHistory, AnalyticsSyncHistory)	Up to 13 months, only set once Marketing consent is granted; cleared immediately on withdrawal
X cookies (_twclid, personalization_id, muc_ads)	Up to 13 months, only set once Marketing consent is granted; cleared immediately on withdrawal
First-party ad click ID (keypra_twclid)	30 days; stored on the device when arriving from an X ad, sent to X only with Marketing consent, cleared immediately on withdrawal

X may also receive server-side conversion events (Conversion API): for email-lane signups these carry only the conversion type and timestamp; for web signups the stored click ID is included only when Marketing consent was granted.

No optional analytics or marketing technologies are activated before the user chooses to enable them. The Google Ads base script tag is present on every page load (so Google's Consent Mode v2 can receive your choice as soon as you make it), but it writes no advertising cookies and performs no conversion tracking until Marketing consent is granted.

Category	Required for service	What it covers
Necessary	Yes	Authentication, security, session continuity, consent recordkeeping, and basic interface preferences
Analytics	No	Behavioral telemetry, competence and retention measurement, product analytics, and documentation analytics used to improve the Service
Marketing	No	Product updates, onboarding or educational communications, and related engagement measurement where enabled

Necessary technologies cannot be switched off because the Service would not function properly without them.

Analytics and Marketing are optional and remain disabled unless you give consent.

If you enable Analytics, Keypra may process first-party usage and learning-improvement data such as feature usage events, documentation page visits, behavioral telemetry connected to prompt-crafting activity, and competence or retention signals used to improve the learning experience.

Enabling Analytics also activates Google Analytics 4 (gtag.js, measurement ID G-Y8FE3QV5RG, operated by Google Ireland Ltd / Google LLC), which Keypra uses for aggregate audience measurement — page views, sessions, traffic sources, approximate country/region, and non-identifying product-event counts. It sets the _ga and _ga_* cookies (2 years).

Google Analytics 4 measurement data is treated as personal data under our Privacy Policy (see Privacy Policy Section 8a, "When Data Stops Being Personal Data"); the safeguards below reduce the data collected but do not make it anonymous.

Safeguards applied to Google Analytics 4: IP anonymisation is on; Google Signals and ads personalisation are switched off on the property; granular location and device data collection is off; event and user data is retained for 2 months before Google deletes it; and Keypra never sends user IDs, e-mail addresses, prompt content, document content or organisation names to Google Analytics. Withdrawing Analytics consent removes the script and clears the _ga / _ga_* cookies immediately. Google Analytics is also hard-disabled for California visitors and any browser sending the Global Privacy Control (GPC) signal, regardless of your Analytics-cookie choice.

Apart from Google Analytics 4, these analytics activities are designed as first-party product and learning analytics. Keypra does not use third-party advertising cookies for this purpose.

Where analytics data is linked to your account, you can later review or change the relevant settings in your account privacy controls.

If you enable Marketing, Keypra may use your contact and engagement data to send product updates, onboarding guidance, feature education, and similar communications. Enabling Marketing also activates three named third-party advertising technologies used for ad-campaign conversion tracking:

• Google Ads conversion tag (gtag.js, account AW-18144700120, operated by Google Ireland Ltd / Google LLC) — records whether a visitor who clicked a Keypra Google Ads advert went on to sign up or purchase.
• LinkedIn Insight Tag (Partner ID 10229937, operated by LinkedIn Ireland Unlimited Company) — records whether a visitor who clicked a Keypra LinkedIn advert went on to sign up or purchase.
• X (Twitter) Pixel (ID rcjxd, operated by X Corp) — records whether a visitor who clicked a Keypra X advert went on to sign up or purchase.

None of these three technologies load, and none of their cookies are set, until you grant Marketing consent. Withdrawing Marketing consent removes the LinkedIn and X scripts and clears their cookies immediately, and denies all Google Ads advertising-cookie storage going forward. California residents and any browser sending the Global Privacy Control (GPC) signal: all three technologies are hard-disabled regardless of your Marketing-cookie choice — see the Privacy Policy §16.3.

Keypra does not use any other third-party advertising network, retargeting pixel, or cross-site advertising tracker beyond the three named above. Full vendor detail, the categories of data received by each provider, and the international-transfer safeguards that apply are published on the Sub-Processors page (§2a).

You can withdraw Marketing consent at any time, including through your privacy settings or the unsubscribe option included in the relevant communication where applicable.

Keypra relies on service providers to operate parts of the Service, including authentication, infrastructure, hosting, communications, and AI functionality.

Where a third-party provider is involved in data processing connected to the Service, the relevant provider details and transfer information are described in the Privacy Policy and Sub-Processors page.

For current provider information, see:

• Privacy Policy
• Sub-Processors

You can manage your preferences in the following ways:

• From the cookie banner when you first visit the Service.
• At any time through the Cookie Policy preference controls on this page.
• If you have an account, through Settings → Privacy for account-level consent management and data controls.
• Through your browser controls, including clearing localStorage or stored site data.

Withdrawing consent is as easy as giving it. If you withdraw consent, Keypra will stop using the relevant optional technologies on a going-forward basis. Withdrawal does not affect processing that took place before the withdrawal.

Keypra keeps strictly necessary authentication-related storage only for as long as needed to maintain the session and secure access to the Service.

Preference records for cookie_consent are kept for up to 12 months unless changed earlier.

Server-side records showing whether optional consent was granted or withdrawn are kept for no longer than necessary to demonstrate and manage the relevant choice, ordinarily within a 12-month consent cycle unless a shorter period is required by a later implementation update or a user exercises deletion rights.

Where optional analytics or marketing data is collected after consent, the retention of that data is governed by the Privacy Policy and the relevant internal retention schedule for that category.

Keypra may update this Cookie Policy when technologies, purposes, service providers, or legal requirements change.

If a change materially affects optional technologies or the purposes for which they are used, Keypra will ask for fresh consent before enabling the new optional processing.

Continued browsing alone will not be treated as consent for new optional cookies or similar technologies.

For questions about this Cookie Policy or your privacy choices, contact:

Email: privacy@keypra.com

Privacy Policy: /privacy

For the current controller and provider details, please also consult the Privacy Policy and Sub-Processors page.