Cookie Policy
1. Overview and Core Principles
This Cookie Policy explains how AdVariq ("we", "us", or "our") uses cookies and similar storage technologies when you visit our website and interact with our studio workspace.
Our Commitment: AdVariq maintains a minimal, privacy-respecting approach to client-side storage. We use technical identifiers for security, sessions and interface preferences, plus optional analytics identifiers with your permission. We do not deploy third-party behavioral advertising trackers or cross-site profiling cookies.
2. What Are Cookies
Cookies are small text snippets placed on your device by websites you visit. They allow web platforms to remember your session or preferences over a period of time, so you don't have to re-authenticate or re-select settings on each page visit.
In addition to standard HTTP cookies, we may use browser web storage (such as LocalStorage) to preserve UI state preferences locally on your device.
3. Cookies and Technologies We Use
AdVariq uses the technical categories below, plus optional PostHog and Microsoft Clarity analytics described at the end of this policy.
3.1 Authentication and Security (Strictly Necessary)
better-auth.session_token/better-auth.csrf_token:- Purpose: Authenticates active user sessions, validates API transactions, and protects against Cross-Site Request Forgery (CSRF).
- Duration: Session duration, or up to 30 days if persistent login is selected.
- Impact: Essential for core functionality. Disabling these cookies prevents signing in to the workspace or triggering image generation.
3.2 Preferences and Functionality (Functional)
locale:- Purpose: Remembers your preferred interface language (e.g., English
enor Frenchfr) across sessions. - Duration: 1 year.
- Purpose: Remembers your preferred interface language (e.g., English
theme:- Purpose: Stores your selected visual theme (Light, Dark, or System).
- Duration: 1 year.
sidebar:state:- Purpose: Preserves the collapsed or expanded state of the workspace navigation sidebar, preventing layout shifts between page transitions.
- Duration: Persisted in local client storage.
3.3 Security and Edge Reliability (Operational)
- Security identifiers (such as Cloudflare edge tokens like
__cf_bm) may be dispatched by our edge proxy to defend against automated bot abuse and DDoS attacks. These tokens are strictly operational and carry no personal identity data.
4. Managing and Disabling Cookies
Most browsers accept cookies by default, but you can configure your browser settings to inspect, restrict, or purge stored cookies:
- Google Chrome: Settings → Privacy and security → Third-party cookies
- Apple Safari: Settings → Privacy → Block all cookies
- Mozilla Firefox: Settings → Privacy & Security → Enhanced Tracking Protection
- Microsoft Edge: Settings → Cookies and site permissions → Manage and delete cookies
Please Note: If you disable strictly necessary authentication cookies, you will be unable to sign in, use the generation workspace, or access purchased credits.
5. Policy Updates and Contact
We may periodically revise this Cookie Policy as our platform evolves. Modifications will appear on this page with an updated date.
If you have questions regarding our use of cookies, contact us:
- Online inquiry: Contact Us
- Email:
support@advariq.com
Optional usage analytics
With your permission, we use PostHog (US region) and Microsoft Clarity to understand visits, feature use and page interactions. Session replay can include visible business content, ordinary form inputs, product descriptions, creative prompts, uploaded product images and generated images. PostHog is configured to record every eligible consented session. Clarity applies its own recording limits and always masks input boxes and dropdown values, even in Relaxed mode. Passwords, one-time codes, API keys and payment credentials are protected. Administration, API-key and security pages and URLs containing authentication credentials are excluded. Ordinary query parameters and fragments do not by themselves prevent recording. Replay reconstructs the page and does not record your entire device screen.
An internal account ID links activity after login. Structured business events exclude email addresses, prompts and image contents; this does not mean those contents are excluded from page replay. Browser exceptions retain only a generic type and public JavaScript asset locations. Request and response bodies and headers are not captured. You can refuse or change your choice using Cookie settings. Refusing stops both browser recorders without affecting core features. On the authenticated App, the choice also controls future server-side analytics after it has synchronized with your account; failed synchronization can delay that change.
PostHog's current free plan retains analytics for up to one year and replay for up to one month. Clarity retains ordinary replay for 30 days and labeled or favorited sessions for up to 9 months. Consent choices, blockers, resource access, provider limits and delivery failures can cause incomplete recordings. Previously masked content cannot be recovered. Deleting a local account does not automatically erase either provider's existing data; contact support for deletion requests.
advariq_analytics_consent stores your choice for up to one year on advariq.com and its subdomains. After consent, PostHog uses ph_*_posthog cookies and browser storage; Clarity uses _clck and _clsk cookies.
Google Analytics 4
With your permission, Google Analytics 4 measures page visits on our website and App using the same web data stream. We send sanitized page paths without query strings, fragments, product IDs or page content; authentication, administration, settings and billing pages are excluded. Advertising storage and personalization are disabled. Declining or withdrawing analytics consent disables GA4 collection. After consent, Google Analytics uses _ga and _ga_* cookies to distinguish visits across our subdomains. This does not send PostHog business events or recordings to Google.
Customer support chat
Crisp uses cookies and browser storage to keep your support chat session and conversation available as you navigate. This functional support service is separate from optional analytics; analytics consent does not control the chat. Blocking its storage may prevent chat continuity.