Cookie Policy
Last updated: 9 November 2026
DigiArte uses a small number of cookies and browser storage items to keep you signed in, protect your account and remember your preferences. Optional tags remain blocked until the consent choice permits them.
1. Essential
Always on, because the site cannot work without them.
| What | Purpose |
|---|---|
| Sign-in session (Supabase) | Keeps you logged in and authorises checkout, downloads and payouts. |
| Language and currency | Remembers the language and currency you chose. |
| Theme and recent searches | Remembers light or dark mode and your last searches on this device. |
| Support chat | Lets a guest reopen their live-chat conversation. |
| App prompts | Remembers whether you dismissed the install or notification prompt. |
| Security | Rate limiting, fraud prevention and bot protection on sign-in and payments. |
Device security ID (da_did) | A random identifier kept for up to 2 years. It is stored by us only as a salted hash and is used to detect self-referrals, duplicate accounts and payout fraud. |
| Bot check (Cloudflare Turnstile or hCaptcha) | When enabled, the provider may set cookies or read device signals on sign-up, sign-in, contact, copyright and payment forms to tell people and bots apart. |
| Cookie choice | Remembers the choice you made in the cookie banner. |
2. Analytics (optional)
With permission we may use Google Analytics 4 and/or Vercel Analytics to measure pages, searches, product views, cart/checkout steps and purchases. Configuration is disabled when no analytics ID is supplied. EEA/UK/Swiss visitors are opt-in; DigiArte currently applies the same protective default elsewhere until a choice is made.
With the same permission, DigiArte records first-party page beacons (path, dwell-time bucket, device/browser class, approximate city/country from the hosting edge, returning flag, and UTM/campaign params) plus one marketing-session landing per browser session (campaign source, landing page and funnel depth). These stay on DigiArte infrastructure (Supabase) for the admin Audience dashboard — including a near-live recent feed and anonymous “hot leads” for returning browsers that never converted. Rejecting Analytics cookies stops the anonymous id, visit beacons and GA4. Advertising click ids (gclid, fbclid, igshid, …) are only kept when Advertising cookies are allowed.
3. Marketing (optional)
When the owner enables Google AdSense, ad storage may measure delivery, prevent fraud and personalise ads where allowed. AdSense is never loaded on checkout, payment, login, wallet or withdrawal pages and is not loaded before advertising consent. Google Consent Mode v2 receives denied/granted signals for analytics storage, ad storage, ad user data and ad personalisation.
When the owner configures them, and only after marketing consent, the following advertising tags measure campaign results and build audiences for re-engagement: Meta Pixel (_fbp), TikTok Pixel (_ttp), Pinterest Tag (_pin_unauth) and Google Ads (_gcl_au). They receive page views, product views, add-to-cart, checkout and purchase events, never payment details.
4. Region and Global Privacy Control
EEA, UK and Swiss visitors receive an opt-in choice. Other visitors receive notice and an opt-out choice, subject to local law. If your browser sends Global Privacy Control (GPC), DigiArte treats it as an opt-out of sale/sharing and advertising for that browser and records the signal. Necessary security and checkout storage remains active.
5. Changing your choice
You can change your choice at any time:
You can also delete cookies in your browser settings. Blocking essential cookies will sign you out and stop checkout from working.
6. Providers and duration
DigiArte choice, theme, language and currency storage normally remains until you clear it or replace the choice. Authentication duration follows session settings. Google and Vercel cookie duration, when enabled, follows their published terms and our configured retention. We periodically review enabled tags and do not permit providers to use marketplace data beyond contracted services and applicable consent.
7. More information
How we handle personal data is described in the Privacy Policy.