Skip to content

Legal

Cookie Policy

Last updated November 13, 2026

Draft — requires review by a lawyer
This document is a working draft published for transparency. It has not yet been reviewed by a lawyer and may change before it becomes final.

1. What cookies are

Cookies are small text files that a website stores in your browser. Similar technologies, such as local storage, work in the same way. This policy explains which ones Eyes Software FZCO ("Snapia", "we") uses on snapia.co and why.

2. Our approach

Snapia runs on cookies and storage that are strictly necessary to provide the features you ask for. On top of those there is one optional category, analytics and advertising measurement. Saying no to it changes nothing about how Snapia works for you.

  • In Türkiye, the European Economic Area, the United Kingdom and Switzerland (and wherever we cannot tell your country), it stays switched off until you choose "Accept" on the cookie notice.
  • In other countries it is on by default, the cookie notice tells you so, and you can switch it off at once with "Decline" or later under "Cookie preferences".

Visit statistics without cookies. We also use Cloudflare Web Analytics to count visits and measure how fast pages load. It sets no cookies, stores nothing in your browser and does not identify you, so it runs for every visitor.

Our own anonymous counts. On our own server we count in how many visits each sign-up step (home page, sign-up button, sign-up form, sign-up) is completed. For this we set no cookie, store nothing in your browser, and record neither your IP address nor who you are: only the name of the step, the page address, any campaign tag in the link, the type of device and browser, and the country. These rows are deleted after 180 days.

We never use advertising cookies on guest pages, on the live photo wall or on venues' own pages, and nothing about guests, albums or photos is ever shared with advertising companies.

3. Cookies and storage we use

Sign-in (authentication) cookies

  • Name: snapia.session_token and related short-lived snapia cookies
  • Purpose: keep hosts and venue users signed in securely and protect accounts
  • Duration: up to 30 days, or until you sign out

Language preference

  • Name: NEXT_LOCALE
  • Purpose: remember the language you chose, so short QR links open in your language
  • Duration: 1 year

Affiliate referral

  • Name: snapia_ref
  • Purpose: record the referral code when you arrive through a partner's link, so the partner can be credited if you sign up. It stores only the referral code, not your browsing history.
  • Duration: 30 days

Guest device token (browser storage)

  • Type: local storage in your browser, not a cookie
  • Purpose: remember your uploads and optional display name for an album, so you can manage and delete your own uploads without an account
  • Duration: until you clear your browser data

Bot protection (Cloudflare Turnstile)

  • Type: cookies or similar browser data set by Cloudflare, only when a Turnstile check is shown
  • Purpose: tell real people from automated bots and protect upload and sign-in forms from abuse
  • Duration: short-lived, as set by Cloudflare

When you pay, Stripe may also use strictly necessary cookies on its own payment pages, for example for fraud prevention, under its own policies.

4. Analytics and advertising measurement (optional)

We advertise Snapia on Facebook and Instagram. To learn which ads bring people who go on to create an album, we use the Meta Pixel in your browser, subject to your cookie choice as described in section 2, and Meta's Conversions API on our servers, subject to the rule under "Events sent from our servers" below. They cover our public pages, sign-up, the host panel and checkout.

  • _fbp (Meta, 90 days): tells Meta that the same browser saw an ad and later visited Snapia.
  • _fbc (Meta, 90 days): stores the click id when you arrive from a Meta ad.
  • snapia_attr (Snapia, 90 days): remembers the campaign you first arrived from (for example the ad's name), so we can see which campaigns work.
  • snapia_consent (Snapia, 180 days): remembers your choice so we don't ask again. This one is necessary and is set whichever button you press.

When this category is on, the Meta Pixel in your browser tells Meta about these moments: a page view, creating an account, creating your first album and starting checkout, together with your IP address and browser type.

Events sent from our servers. Separately from cookies, our servers can report account moments to Meta: creating an account, creating your first album, starting checkout and completing a purchase (with its amount). Along with them we send your IP address and browser type and, in hashed (scrambled) form, your e-mail address, phone number if you gave one, and account id, so Meta can match the event to an ad view.

  • In every country this happens only if you have given the separate account-level consent "Ad measurement and personalisation", asked at sign-up, in the host panel or in the app, and changeable in your account settings. It is off by default; accepting the cookie notice alone is never enough.
  • If you have given the account-level consent, these events are sent whatever your cookie choice (without the _fbp and _fbc cookies if you have not allowed cookies), the pixel also receives the hashed form of your e-mail address and account id when cookies are allowed, and Meta may use the data to show you more relevant ads, for example through custom or lookalike audiences. See section 9 of our Privacy Policy.

Meta Platforms Ireland Ltd. acts as a joint controller for collecting and sending this data and as an independent controller for its later use; see Meta's Privacy Policy. Data may be transferred outside your country, including to the United States.

Google Analytics. Under the cookie choice in section 2 we use Google Analytics 4 (and Google Tag Manager to load it) to understand which pages people visit and where they drop off, so we can improve the site.

  • _ga, ga<id> (Google, up to 2 years): tell visits by the same browser apart, without knowing who you are.

Google Analytics receives page addresses (with private ids left out of our own event data), your approximate location derived from your IP address, your device and browser type, and the same account moments listed above (sign-up, first album, checkout, purchase). Google Analytics is used for measurement only: ad personalisation is switched off, and the account-level consent described above is never sent to Google. Google Ireland Ltd. processes this data on our behalf; it may be transferred outside your country, including to the United States. See how Google uses data.

Microsoft Clarity. Under the same cookie choice we use Microsoft Clarity to see how pages are used (clicks, scrolling, where people get stuck) through session recordings and heatmaps. Text you type into form fields is masked and not recorded. Clarity never runs on guest pages.

  • _clck, _clsk (Microsoft Clarity, up to 1 year and 1 day): link visits from the same browser, and the pages of one session.
  • CLID, MUID (Microsoft, up to 1 year): recognise the same browser on Microsoft's own domains.

Microsoft Ireland Operations Ltd. processes this data on our behalf; it may be transferred outside your country, including to the United States. See the Microsoft Privacy Statement.

Changing your mind: use "Cookie preferences" at the bottom of any page. If you withdraw consent we stop at once and delete these cookies (Meta's, Google's and Microsoft Clarity's) from your browser. The account-level consent is separate: switch off "Ad measurement and personalisation" in your account settings and nothing new is sent to Meta from our servers.

4a. Future changes

If we add any other cookies that are not strictly necessary, we will ask for your consent first and update this policy before doing so.

5. How to control cookies

Most browsers let you view, block and delete cookies and local storage in their settings. Because the items in section 3 are strictly necessary, blocking them may affect how Snapia works:

  • you may not be able to stay signed in;
  • your language choice may not be remembered;
  • if you clear the guest device token, you can no longer delete your uploads yourself from that browser.

If you have lost access to your uploads, you can still ask us to delete them through the data request form.

6. More information and contact

Read more about how we handle personal data in our Privacy Policy and KVKK Information Notice. Questions: [email protected].

Questions about this document? Write to [email protected].