This page lists every cookie set on veracly.app, what it does, who it belongs to, and how long it lasts. Where consent is required (analytics, marketing) we ask for it before the cookie is set.
- 01
What cookies are
Small text files stored by your browser that let websites remember things between page loads.
- 02
What we use them for
Authentication and language preference only. We set no analytics, marketing, or advertising cookies.
- 03
Strictly necessary cookies
These cookies are strictly necessary for the site to function and cannot be disabled. They include: session cookies set by Clerk for authentication (keeps you signed in); a CSRF token cookie to protect form submissions; and a locale cookie that remembers your language preference. No consent is required under ePrivacy Directive Article 5(3) for these cookies as they are essential to the service you have requested. When you choose “Monitor this website”, sessionStorage keeps the domain and selected country in that tab to continue the requested setup. It grants no access to reports or domain ownership. The app ignores and removes the entry when read after two hours, or clears it when you add the site or choose to forget it; closing the tab normally clears sessionStorage. No full scanned URL, email or report ID is saved in this entry.
- 04
Analytics cookies
We use no third-party analytics or analytics tracking cookies. With your explicit analytics consent, we also receive first-party interaction events (such as a pricing click), containing only an event name, random per-event deduplication ID, date (no time of day), and optional plan/currency. These event records contain no email, website URL, IP address or visitor/session identifier and are deleted after 30 days by daily cleanup. If signed in, your existing account ID is used transiently to exclude staff/test activity, not stored with the event. Rejecting or withdrawing analytics consent, or sending Global Privacy Control, stops these optional events. Legal basis for these optional events: Art. 6(1)(a) GDPR consent. Operational account, scan and billing records remain necessary to provide the service.
- 05
Marketing cookies
We do not currently place any marketing or advertising cookies on veracly.app. If we introduce marketing attribution pixels (for example, Google Ads or Meta Pixel) in future, we will add them to this table, update this policy, and require your explicit consent via the cookie banner before any marketing cookie is set.
- 06
How to manage your choices
Use the cookie banner, your browser settings, or the link in the footer to revoke or change consent at any time.
- 07
Third-party cookies
Clerk (authentication): sets one or more session cookies under the veracly.app or clerk.veracly.app domain to keep you signed in. These persist for 30 days or until you sign out. Stripe (billing): if you are on a paid plan, Stripe may set a fraud-detection cookie during checkout only; this is not active outside the Stripe checkout iframe. The certificate-of-representation badge on our privacy policy, imprint, and DPA pages is loaded from app.prighter.com; it sets no cookie, but the request discloses your IP address to our Article 27 representative. We do not use Google Analytics, Facebook Pixel, or any ad-network cookies at this time.
- 08
Changes to this policy
We re-publish this page whenever the cookie inventory changes. The Last updated date reflects the most recent change.