Cookie Policy
Last updated: [PLACEHOLDER — date of legal review]
[PLACEHOLDER] below are not yet filled in with real, company-specific facts (legal entity name, registered address, governing-law jurisdiction, data protection officer contact, exact retention periods). Do not treat this page as legally binding, and do not publish it as final, until a qualified lawyer has reviewed it and every placeholder has been replaced with an accurate, verified value.The short, accurate version
As of this writing, the Juricare AI web app does not set any browser cookies— verified directly against the codebase, not assumed. Sessions are kept using the browser’s localStorage, not cookies: your access token, refresh token, and cached profile are stored under the keys juricare_token, juricare_refresh_token, and juricare_user. There is also currently no third-party analytics or advertising script (e.g. Google Analytics) wired into the site.
Why this still exists as a page
Many jurisdictions’ cookie-consent rules also cover equivalent local-storage-based tracking, and this document exists so that’s addressed honestly rather than assumed away. Since no tracking or advertising cookies are set today, no cookie-consent banner is currently shown. [PLACEHOLDER — confirm with counsel whether the DPDP Act/GDPR/ePrivacy-equivalent obligations in your actual jurisdiction(s) require an explicit consent mechanism for localStorage-based authentication tokens specifically — this is a genuinely debated point across jurisdictions and shouldn’t be resolved by this document alone].
What’s in localStorage, and why
| Key | Purpose | Cleared when |
|---|---|---|
juricare_token | Short-lived (15 min) JWT access token, sent with every API request | On logout, or automatically replaced on refresh |
juricare_refresh_token | Long-lived (30 day), single-use, rotating token used only to obtain a new access token | On logout (revoked server-side too), or after use (replaced by a new one) |
juricare_user | Cached copy of your own profile, for instant UI on page load | On logout |
If this changes
If a future version of the Service adds analytics, advertising, or any other cookie/tracking mechanism, this page will be updated to accurately describe it — and a consent mechanism will be added if the applicable law requires one, before such tracking begins, not after.