Cookies & Storage Policy
How Dralvia uses cookies, browser storage, and related client-side technologies across its public and product surfaces.
Quick links
Public legal route map
These pages are intentionally crawlable and static so buyers, counsel, and operators can reach them without platform login or hash-route context.
Contact
For platform help, onboarding, or support requests, contact [email protected].
For policy, privacy, or contracting questions, contact [email protected].
For security disclosure, contact [email protected].
Current position by Dralvia property
- Marketing site: no cookies are needed to browse
marketing.dralvia.tech. Google Analytics 4 is available and loads only after an explicit analytics consent, and the only thing stored in a clean browser session is the record of that choice. - Product platform: signed-in flows rely on identity-provider and security controls, and the frontend stores some preference and guest-mode state locally.
- Docs site: Google Analytics 4 is wired behind consent logic and should run only after an explicit analytics opt-in.
Cookies and similar technologies in use
Authentication
Dralvia sign-in may set authentication session cookies such as AUTH_SESSION_ID and AUTH_SESSION_ID_LEGACY on sso.dralvia.tech for signed-in product sessions.
Security and abuse prevention
Cloudflare may set anti-abuse cookies such as cf_clearance when a browser is challenged.
Settings and local storage
The platform keeps dralvia_guest_id in local storage so scans run without an account stay yours, dralvia_cookie_prefs_v1 for your analytics answer, and settings you choose such as theme, written only when you change them and never sent to us. It also keeps entries for console settings, getting started, community comments, and a trial or scan you started before creating an account. Every entry, what it holds, and how long it is kept is listed in the platform's Cookies Policy.
Optional analytics
The marketing site, the blog, the docs site and the platform can load Google Analytics 4 cookies such as _ga only after explicit consent. They all use the same Google Analytics 4 property for the same purpose, so one answer applies to every Dralvia site. The answer is remembered for 180 days in the dralvia_consent cookie on dralvia.tech, and each site also keeps a local copy (dralvia_marketing_cookie_prefs_v1 on the marketing site, dralvia_docs_cookie_prefs_v1 on the docs site), so a refusal does not have to be repeated on any page or site. You can change your answer on any of them at any time. On the platform the same answer also covers Dralvia's own usage events (which pages were opened, that a scan started, the outcome of a signup attempt): they are sent only after you accept, never after a refusal, and kept for 180 days.
Consent model
Consent is required before any non-essential cookie or similar tracking technology is activated, and nothing non-essential is written to your device before you answer.
Reject and Accept sit side by side in the banner, so refusing costs the same single click as accepting. Refusing is remembered, and you can change your mind at any time from the Cookie preferences control that stays on every page.
If session replay, heatmaps, ad pixels, or similar tools are added in the future, they are covered by the same rule: they run only after consent, and this policy is updated before they do.
Public-site position
The marketing site exists to explain the platform and direct visitors into the live product. Public legal pages live here so they are crawlable, linkable, and accessible without entering the platform console.
Platform legal center
The product platform also maintains legal-center routes for authenticated and guest users. Use the public pages here for external sharing and the live platform for operational/legal workflow context.