Cookie Policy
1. What Are Cookies?
Cookies are small text files stored on your device when you visit a website. They help the website function, improve performance, and provide information to the site owners.
2. How We Use Cookies
Prescrivia uses cookies for the following purposes:
2.1 Essential Cookies
Essential cookies and browser storage support authentication, security and consent choices. You can delete or block this storage in your browser, but doing so may prevent account access or cause the consent banner to appear again. Essential storage is separate from optional analytics and marketing consent.
2.2 Performance Cookies
Optional performance measurement helps us understand use of permitted public pages. It requires prior analytics consent, which you can withdraw through your privacy settings.
2.3 Functional Cookies
These cookies remember your preferences such as language settings and display options to provide a personalised experience.
2.4 Analytics Cookies
After analytics consent, Google Analytics may use cookies with pseudonymous browser identifiers to measure traffic on permitted public pages. Pseudonymous data is not the same as anonymous data. Reports may be aggregated; this does not make all underlying data anonymous.
3. Health Data Safeguards
We take special care with cookies in the context of health data:
- Cookies and browser storage must not contain assessment answers, prescriptions or clinical narratives. Session, consent and attribution identifiers can still be personal data and may link to health-related records; this storage is not treated as anonymous.
- Clinical roles have a shorter inactivity timeout, separate from browser-storage expiry
- Analytics collection is blocked on clinical and authenticated account routes; page context is stripped of query strings and record identifiers
- We do not use cookies for health-related advertising targeting
4. Your Choices
Use the cookie banner or privacy settings to accept, reject, or withdraw optional analytics and marketing consent. You can also refuse or delete cookies and other browser storage through your browser settings. Blocking essential storage may affect platform functionality.
5. Third-Party Cookies
Some cookies are set by third-party services we use, such as analytics providers and payment processors. These cookies are governed by the respective third party's privacy policy.
Diagnostic SDKs may use session storage when their configured tracing features are enabled. The exact SDK keys and provider retention must be verified for the deployed release; we do not claim a generic one-year diagnostic cookie duration. Operational recovery flags such as prescrivia:marketing-stale-module-reload:last-handled use session storage until the tab is closed or storage is cleared.
6. Cookie Duration
- Session cookies — Deleted when you close your browser
- Persistent cookies — Remain on your device for a set period or until manually deleted
- Clinical access — Default 15-minute inactivity timeout for clinical roles; this is an access control, not a cookie expiry period. Authentication uses session or local storage depending on sign-in preferences.
sb-*-auth-token— Keeps the authenticated session and refresh information; it is not an analytics identifier. Session storage for session-only sign-in; persistent sign-in until sign-out or clearing. The default durable-session validity is 12 hours; clinical inactivity controls apply separately.prescrivia_auth_persistence,prescrivia_auth_persistence_expires_at— Records the selected sign-in persistence and, where applicable, session-validity deadline. Until updated or cleared; a stored deadline controls session validity rather than automatic deletion of the preference key
Draft pending qualified legal review: the partner_attribution row retains its draft status and does not establish approval or operational verification.
7. Cookie list
| Cookie or storage key | Purpose | Type | Duration | Set by |
|---|---|---|---|---|
prescrivia_locale_pref | Stores selected country and language. | First-party, strictly necessary | 1 year for the cookie; the related local-storage preference remains until changed or cleared | Prescrivia |
medical_data_consent_subject_id | Links an explicit pre-assessment consent event to the later account when the user proceeds. | First-party, consent evidence | Consent subject expires after 30 days; removed on adoption or local deletion, and stale entries are cleared when read | Prescrivia |
_ga, _ga_* | Optional analytics measurement after consent. | Third-party analytics | Up to 2 years | Google Analytics |
privacy_consent, privacy_preferences | Stores optional-cookie consent choices, consent version and the recorded choice time. | First-party, necessary consent-preference storage (local storage) | Until changed or cleared; the marketing consent record has no automatic browser-storage expiry | Prescrivia |
_GRECAPTCHA | Automatic security check on sign-up, assessment, booking and referral forms to block automated or abusive submissions. | Third-party, strictly necessary security | Up to 6 months | Google reCAPTCHA |
partner_attribution | Stores a partner referral attribution token after marketing-cookie consent. If the visitor registers within 30 days, the account is attributed to the referring partner. | First-party, marketing/attribution (local storage) | 30 days | Prescrivia |
8. Updates
This cookie-policy text was revised on 10 October 2026. We may update it from time to time and will publish material changes on this page. Cookie consent does not itself authorize the planned health-data processing using an OpenAI model through OpenRouter.
9. Contact
For questions about our use of cookies, please contact us.