Cookie Policy

1. About this policy

This Cookie Policy explains what cookies and similar technologies Worql, Inc. ("Worql") uses on the website at worql.app and in the in-app product, and how you can control them. It is part of our Privacy Policy.

We use Vercel Analytics and Vercel Speed Insights, which are cookieless and do not place identifying cookies on your device or track individual users across sessions.

2. What cookies are

A cookie is a small text file that a website places on your device to remember information between requests. "Similar technologies" include localStorage, sessionStorage, and pixels — anything that reads or writes state on your device or browser.

Browsers let you block or delete cookies through their settings. Doing so will not break Worql for casual browsing but may sign you out and require you to sign back in.

3. Categories we use

We use only two categories of cookies: strictly necessary, and preference. We do not use advertising, behavioral, or cross-site tracking cookies.

Strictly necessary

These are required for the Service to function. They cannot be turned off without breaking sign-in or session security.

| Cookie name | Set by | Purpose | Duration | |---|---|---|---| | __session, __client_uat, __refresh_* | Clerk (auth provider) | Authentication, session, and refresh tokens. Without these, sign-in cannot work. | Session and up to 1 year (refresh) | | __Host-next-auth.csrf-token and CSRF analogs | Worql / Next.js | CSRF protection on form submissions. | Session | | Stripe checkout cookies | Stripe | Set only during checkout/portal flow on Stripe's domain (not worql.app). Required to complete payment. | Session |

Preference

These persist a non-identifying preference on your device.

| Storage key | Where stored | Purpose | Duration | |---|---|---|---| | worql-cookie-consent | localStorage | Records your cookie banner choice (necessary-only or all). Avoids re-prompting on each visit. | Until cleared |

4. Analytics — cookieless

Worql uses Vercel Analytics and Vercel Speed Insights to understand aggregate page-view counts and performance metrics. These are cookieless — they do not place any identifying cookie on your device, and they do not track individual users across sessions. Page-view aggregation is done at the edge from request metadata, not from per-user identifiers.

We do not use Google Analytics, Meta Pixel, LinkedIn Insight Tag, or any similar third-party tracker.

5. Your choices

Because we use only strictly necessary cookies plus a single preference key, there is little to consent to. The cookie banner you see on first visit asks whether you want to allow "necessary only" or "necessary plus analytics" — but the analytics in question is cookieless, so the practical difference for cookies is zero. The choice is recorded for transparency.

You can:

• Block or delete cookies in your browser settings at any time (this will log you out of the Service).
• Clear worql-cookie-consent from localStorage to re-trigger the banner.
• Email privacy@worql.app with any question about cookies or tracking.

6. Changes

We will update this policy if our cookie use changes — for example, if we add a new sub-processor that requires a cookie. The "Last updated" date at the top of this page reflects the most recent revision.

7. Contact

Questions: privacy@worql.app.