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, language preference, basic analytics, and (only with consent) marketing attribution.
- 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.
- 04
Analytics cookies
We use Vercel Web Analytics and Speed Insights on the marketing site. These tools use daily-rotated hashed IP addresses and do not set cookies or fingerprint devices — they qualify as "cookieless" analytics and operate under our legitimate interest (GDPR Article 6(1)(f)). We do not currently use any cookie-based analytics. If we introduce cookie-based analytics in future, we will update this page and require your consent before setting any analytics cookie.
- 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. 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.