1. What this covers
This Cookie Policy explains how Voidek uses cookies, local storage, session storage, browser identifiers, and similar technologies on the website, dashboard, snippets, and protected-site integrations.
2. Necessary technologies
Necessary cookies and local storage are required for core service operation and cannot be disabled through the Voidek banner. You can still block them in your browser, but the dashboard, challenge flow, or protected-site verification may not work.
- Session and login status for account access.
- Cookie consent preference such as voidek.cookieConsent.v1.
- Challenge/session continuity tokens for verified browser flows.
- Site registration and dashboard demo state while the beta uses local/demo auth.
- Security, abuse prevention, rate limiting, and fraud prevention signals.
3. Security and browser signals
Voidek may collect or store lightweight browser signals to distinguish normal browser traffic from scripts, headless browsers, credential probes, and path scans. Examples include webdriver indicators, language, timezone, screen size, client hints, token presence, and user agent consistency.
These signals are used for security and service integrity, not to build advertising profiles.
4. Analytics and marketing
The current beta does not require third-party advertising cookies. If we add analytics, attribution, retargeting, or marketing pixels, we will update this policy and keep optional categories behind a consent control where required.
5. Third-party cookies
Hosted providers, payment providers, embedded checkout, support tools, or documentation tools may set their own cookies when those features are enabled. Their policies will apply to their own cookies.
6. Controls
You can use the banner to choose necessary-only or allow-all mode. You can also clear browser storage or block cookies through browser settings. Clearing storage may sign you out, reset preferences, or require new browser verification.
7. Retention
Consent preferences are kept until you clear storage or we rotate the consent version. Session and challenge tokens expire according to their security purpose. Request logs and derived usage are retained according to the Privacy Policy.