Cookie Policy

This Cookie Policy explains the technical cookies and local storage used by Generate QR Itself. We do not use profiling or advertising cookies.

Essential cookies

Authentication is provided by Clerk which sets session and security cookies (for example __session, __client_uat, __clerk_db_jwt) to keep you signed in and protect the dashboard. Our hosting or CDN providers may set security cookies for bot protection and traffic management (for example __cf_bm or _cfuvid).

Local storage

The API documentation uses Stoplight Elements and stores UI preferences and security selections in local storage (for example HttpOperation_security_expanded, TryIt_securitySchemeValues, mosaic-theme). If you use the "Try it" console, the API key value can be stored locally until you remove it. Clerk may also store environment and telemetry throttling values (for example __clerk_environment, clerk_telemetry_throttler).

Third-party services

Payments are handled on Stripe Checkout; Stripe may set its own cookies on stripe.com. Error monitoring is provided by Sentry, which may use technical storage to associate error events. Analytics uses a self-hosted Umami instance without cookies.

Managing cookies

You can delete cookies and local storage through your browser settings. Clearing them may sign you out and reset documentation preferences. You can also disable third-party cookies if you prefer.