Cookie Policy
Effective: September 2026
Last updated: September 2026
There are two separate things to cover here: cookies on vistiqo.online itself, and what the Vistiqo tracking script does on our customers' websites. They are different, and the second one is what most people are asking about.
1. Cookies on vistiqo.online
When you sign in to your Vistiqo account, the application sets a small number of strictly necessary cookies. They exist to make signing in work and to protect forms from cross-site request forgery. Separately, vistiqo.online uses Google Analytics to measure how this website itself is used, which sets analytics cookies that are not strictly necessary. We do not set advertising cookies and we do not run marketing or advertising tags.
| Cookie | Purpose | Type |
|---|---|---|
| Authentication cookie | Keeps you signed in as you move between pages. Set by ASP.NET Core Identity after a successful Google sign-in. | Essential |
| Antiforgery cookie | Protects form submissions (such as sign-in and sign-out) against cross-site request forgery. | Essential |
| Sign-in correlation cookies | Short-lived cookies used only during the Google sign-in redirect, to tie the response back to the request that started it. Discarded once sign-in completes. | Essential |
_ga, _ga_* |
Google Analytics. Distinguishes one visitor from another so we can see how many people visit vistiqo.online and which pages they read. Set on this marketing site only - never by the Vistiqo tracking script on your own website. | Analytics |
The cookies marked Essential are strictly necessary for a service you have asked to use, so no consent is sought for them. Blocking them will prevent sign-in from working. Signing out clears the authentication cookie; you can also clear cookies in your browser at any time.
The Google Analytics cookies are not essential: blocking them, using your browser's do-not-track or an ad blocker, or declining them costs you nothing - every part of Vistiqo works exactly the same without them. They tell us how vistiqo.online is found and read; they are not used for advertising, and they are never set on the websites you track with Vistiqo. Google processes this data under its own policies - see Google's Privacy Policy.
Signing in goes through Google, and Google may set its own cookies in that process under its own policies. See Google's Privacy Policy. Similarly, when you go to checkout you are handed to Creem, which operates its own site and cookies - see its Privacy Notice.
2. The tracking script sets no cookies
The Vistiqo script that our customers install on their websites does not set any cookies. It uses two browser storage entries instead:
| Entry | Storage | What it holds |
|---|---|---|
_vistiqo_vid |
localStorage | A random identifier generated in the browser, so repeat visits to that same website can be recognised as returning rather than new. It contains no personal information and is not derived from anything about the visitor. |
_vistiqo_sid |
sessionStorage | Groups page views into a single visit. Because it lives in sessionStorage, the browser discards it when the tab is closed. |
Both entries are scoped by the browser to the website that set them. They are not shared between different websites, so Vistiqo cannot follow a visitor from one customer's site to another's, and cannot build a cross-site profile.
The script also reads a few values the browser exposes to any page - screen size, browser language, and the referring URL - and sends them with the page view. It does not read cookies, and it does not access anything requiring a permission prompt.
3. Does this need a cookie banner?
We are not going to answer that for you, because the honest answer depends on your jurisdiction and how you use the product. What we can tell you plainly is the technical fact: the tracking script stores two identifiers in browser storage on the visitor's device, and it does not use cookies.
Several privacy laws - including the EU ePrivacy rules - cover storing or accessing information on a user's device generally, not cookies specifically, so using localStorage rather than cookies does not automatically remove a consent obligation. As the operator of your website you decide what notice or consent is required for your visitors, and you are responsible for that decision. If you use a consent tool, you can load or delay the Vistiqo script accordingly. We would rather state this clearly than imply Vistiqo is exempt because it avoids cookies.
4. Visitor choices
If you are a visitor to a website that uses Vistiqo, clearing your browser's site data removes both entries described above, and the next visit will be counted as new. Browser settings that block scripts or site storage will also prevent the script from working. Vistiqo receives no data about you if the script does not run.
5. Changes and contact
If we add or change what the application or the script stores, we will update this page and its "last updated" date. Questions: support@vistiqo.online. For the wider picture of what is collected and why, see the Privacy Policy.
Questions about this policy?
Contact us at support@vistiqo.online for support, billing, privacy or data requests. This is the contact point for every topic covered by our policies.
Related