This site stores almost nothing in your browser, and nothing at all until you answer the question below. It does count page views on every visit, without keeping anything on your device. If you accept, Google measures whether an advertisement brought you here, records how the site is used, and adds the visit to an advertising audience, and two services try to recognise which company the visit came from. That is the whole of it. This page describes each piece and names who is involved.
What a cookie is
A cookie is a small file that a website asks your browser to keep between page views. Related technologies, in particular local storage, do the same job in a different place. This policy covers both, and uses "cookie" for all of them.
What this site stores
For an ordinary visit, nothing. Reading any page on sandsiv.com sets no cookie and writes nothing to your browser's storage. There are three exceptions.
Security
sandsiv.com is delivered through Cloudflare, our content delivery network. To separate human visitors from automated traffic, Cloudflare may set a short-lived cookie in your browser. It holds no profile of you and is never used for advertising or measurement. It is strictly necessary: without it we cannot keep the site online and safe.
Counting page views
Every page load is counted. Our website platform, Lovable, runs a small script served from sandsiv.com that records the page you opened, the page you came from, your browser and language, rough loading times and your IP address. The counts are processed by Tinybird on Lovable's behalf. We see totals, not people.
It writes nothing to your browser. No cookie, no local storage, nothing that outlives the visit. It runs on every visit, including before you answer the question below, and we would rather say so here than leave it out because it happens to be invisible.
Measuring our advertising
We advertise on Google. To learn whether an advertisement produced an enquiry, we use the Google tag. It loads only after you press Accept on the cookie notice, and not before: until then your browser does not contact Google at all.
If you accept, Google places two things. A cookie called _gcl_au, which holds a random identifier that lets Google match a click on one of our advertisements to a form you later submit here, and which expires after 90 days. And an entry called _gcl_ls in your browser's local storage, which serves the same measurement and stays until you clear it.
That identifier does two jobs. It tells us whether a click on one of our advertisements led to an enquiry here. It also adds your visit to an advertising audience held by Google, which is what allows our advertisements to be shown again to people who have already visited this site. That second one is remarketing, and we would rather name it than describe it in softer words. We never learn who you are from that identifier. We see counts and audience sizes.
There is one more step, and it only happens if you have accepted and then send us a form. Google's advertising tag may take the email address, telephone number, name or postal address you typed in, turn it into a code that cannot be turned back before it leaves your browser, and send that code to Google. Google compares the code with Google accounts to tell us whether one of our advertisements led to your enquiry. Google calls this enhanced conversions and does it on our behalf under its data processing terms. We receive only totals, never the codes or the accounts they match.
If you press Decline, or leave the question unanswered, nothing loads and neither item is created. The site behaves identically either way.
Understanding how the site is used
If you accept, we also run Google Analytics. It records which pages you open, in which order, which language version you use, roughly where in the world you are, and whether you sent us a form. It sets two cookies, _ga and _ga_8M2R7L78WZ, which hold a randomly generated number and expire after thirteen months.
This is ordinary website measurement and it exists so that we can tell which pages do their job. Our Analytics and advertising accounts are linked, so Google can also use this information to add your visit to the advertising audience described above and to report which advertisements led to an enquiry. It does not run at all unless you accept, and pressing Decline leaves it off.
Recognising which company visits
If you accept, we also try to work out which company a visit comes from. We sell to businesses, and knowing that someone from a particular organisation read our pages helps us decide who to talk to. It works from the IP address of the network you use, which at work usually belongs to your employer. We see the company name, the pages opened and when. We do not receive your name or your email address from this, and we do not use it to find out who you are.
Two services do this for us. We are testing both for a limited period to decide which one to keep.
Leadfeeder, run by Leadfeeder Finland Oy, sets a cookie called _lfa, which holds a randomly generated number and expires after one year. It also writes two entries to your browser's local storage, called _lfa and _lfa_expiry, which hold the same number and the date it expires, and which stay until you clear them. It records the pages you open, the page you came from and your IP address, and matches the address to a company. If Google Analytics is also running, it reads the identifier in the _ga cookie so that both tools count the same visit.
lemlist, run by lemlist SAS in France, writes nothing to your browser. It records the page you arrive on and your IP address and matches the address to a company. Its data is stored in France.
Neither runs unless you accept, and pressing Decline leaves both off.
Staying signed in to the editor
Our blog is written and edited by SANDSIV staff on this same domain. When one of them signs in, their browser keeps a single session entry in local storage so they are not asked to sign in again on every page. It is created only after a successful sign-in, it never leaves that browser, and it is deleted on sign out. If you have never signed in, it does not exist.
What we do not use
No session recording and no heat maps. Nobody watches your pointer or replays your visit. No identification of individual visitors. The company recognition described above stops at the company, and we do not try to put a person's name to an anonymous visit. No social media trackers and no embedded share widgets. No fingerprinting. No advertising network other than Google.
Apart from the page view count described above, everything that is not strictly necessary waits for your answer, and Decline means none of it loads.
Third parties
Six, and three of them are optional. Cloudflare delivers the page and keeps it available. Supabase runs the backend of this website, so anything you send us through a form passes through it. Tinybird processes the page view counts for Lovable. Google measures our advertising and how the site is used, and Leadfeeder and lemlist recognise which company a visit comes from, all three only after you have accepted. Everything else this site needs, including both of its typefaces, is served from sandsiv.com itself, so an ordinary page load contacts Cloudflare and no one else.
Your choice
The first time you open sandsiv.com you are asked one question, with Accept and Decline given the same size and the same weight. Nothing loads while the question is open. Your answer is kept in your browser, in an entry called ss_consent, for twelve months, so that you are not asked again.
You can change it whenever you like through Cookie settings at the foot of any page. Declining after having accepted stops any further measurement. To remove what was already placed, delete it in your browser as described below.
This page is about this website
sandsiv+ is a platform that processes customer feedback on behalf of our clients. That data sits in the region each client chooses, is governed by our contract with them, and has nothing to do with the storage described here. Nothing a visitor does on sandsiv.com is ever mixed with it, and no advertising technology of any kind touches it.
When you send us something
The demo, contact and enterprise forms do not use cookies, but this is where people look for the answer. What you type is transmitted to us so that a person can reply to you. How it is stored, who can see it and for how long is set out in the Privacy notice.
The newsletter signup on the blog is a form like the others. It sets no cookie and writes nothing to your browser's storage. The address you type is stored so that we can send you the confirmation email and, once you confirm, the newsletter you asked for; the Privacy notice explains how long we keep it and who can see it.
Managing what is stored
Every browser lets you inspect, block and delete cookies and local storage, usually under Settings, then Privacy. Blocking the Cloudflare security cookie may prevent the site from loading, because it protects availability. Deleting the four Google items, the _gcl_au and _ga and _ga_8M2R7L78WZ cookies and the _gcl_ls entry in local storage, together with the Leadfeeder cookie _lfa and its _lfa and _lfa_expiry entries in local storage, stops all of the measurement and company recognition described above and costs you nothing else. Nothing else here depends on browser storage, so blocking the rest costs you nothing.
Changes to this policy
We revise this page whenever what the site stores changes, and the date below moves with it.
Last updated 16 September 2026. Questions about this policy: privacy@sandsiv.com. SandSIV Schweiz AG, Technoparkstrasse 1, 8005 Zürich.
This document is published in English. The English version is the authoritative one.