SQL Mocker
Cookie Policy
This Cookie Policy explains how SQL Mocker uses cookies and similar browser technologies, what they are used for, and the choices available to you.
Last updated: 26 August 2026
What are cookies?
Cookies are small pieces of information stored by a browser and sent with certain website requests. They are commonly used to keep users signed in, protect sessions, remember choices, and understand website usage.
Cookies and similar browser technologies
SQL Mocker also uses localStorage and IndexedDB. These technologies are not cookies: they store workspace drafts, saved-project caches, and application preferences locally in the browser. Where relevant, this policy refers to them together as cookies and similar technologies.
How the categories are used
Strictly necessary
Authentication and checkout technologies support sign-in, session management, account protection, and payment flows. Blocking them can prevent those parts of SQL Mocker from working.
Functional
Browser storage remembers the current workspace, cached saved projects, selected application state, and a small number of product preferences.
Analytics
Vercel Web Analytics records page views and selected product events, while Speed Insights reports web-performance measurements. The current integrations do not create analytics cookies or persistent SQL Mocker browser-storage identifiers.
At present, SQL Mocker does not include advertising pixels, retargeting tools, or marketing cookies. Because the current optional analytics integrations do not use cookies or persistent browser storage, SQL Mocker does not display a separate cookie preference banner. This policy will need to be updated if that implementation changes.
Technology details
| Name / Technology | Provider | Purpose | Category | Duration |
|---|---|---|---|---|
| Clerk authentication cookies, including __session and related cookies | Clerk | Signs users in, maintains authentication state, and supports account protection. Exact cookie names can vary by environment and Clerk configuration. | Strictly necessary | Short-lived tokens are refreshed while a session is active. Overall session duration depends on Clerk configuration. |
| mock_sql_project_v6 (localStorage) | SQL Mocker | Keeps the current workspace draft, including reviewed schema, SQL, relationships, settings, and generated workspace state available in the browser. | Functional | Until the workspace is reset or browser storage is cleared. |
| mock_sql_saved_projects_<scope> (IndexedDB) | SQL Mocker | Caches saved projects in the browser for workspace continuity. Signed-in project records may also be synchronized with SQL Mocker application storage. | Functional | Until a project or the relevant browser storage is removed. |
| SQL Mocker preference keys (localStorage) | SQL Mocker | Remembers the project storage scope, hidden demo workspaces, backup status, and acknowledgement of the SQL Mocker terms for a signed-in user. | Functional / strictly necessary | Until the setting is replaced or browser storage is cleared. |
| Vercel Web Analytics | Vercel | Measures page views, referrers, and selected product events. Vercel documents Web Analytics as cookie-free; the SQL Mocker integration does not create a local browser-storage key for it. | Analytics | No analytics cookie or persistent browser-storage entry is created by the current integration. |
| Vercel Speed Insights | Vercel | Sends web-performance measurements such as Core Web Vitals to help identify loading, responsiveness, and layout issues. | Analytics | No persistent browser-storage key is created by the installed client package. |
| Privacy-enhanced embedded video player | YouTube / Google | Displays optional SQL Mocker demonstration videos using the youtube-nocookie.com privacy-enhanced player. YouTube may use its own cookies or browser storage when a viewer interacts with the player. | Functional third-party content | Controlled by YouTube and the viewer's Google or browser settings. |
| Hosted checkout and billing portal | Stripe | Supports payment sessions, fraud prevention, and billing account management when a user opens Stripe-hosted payment pages. | Strictly necessary for checkout | Controlled by Stripe on its hosted pages. |
Authentication
When authentication is enabled, SQL Mocker uses Clerk. Clerk sets session and related cookies when users sign in or sign up. These technologies are required to identify the active session, protect authenticated routes, and associate saved work and usage with the correct account. Exact cookie names and lifetimes can change with the environment and Clerk configuration.
Third-party services
SQL Mocker currently integrates Clerk for authentication, Vercel for hosting, analytics, and performance measurement, Stripe for hosted billing, and YouTube for privacy-enhanced demonstration videos. Their processing is also governed by their own notices:
Managing browser storage
You can block or delete cookies, localStorage, and IndexedDB through your browser settings. Clearing SQL Mocker browser storage can remove local workspace drafts, cached projects, and remembered preferences. Blocking strictly necessary Clerk cookies can prevent sign-in and authenticated workspace features from working.
Privacy Policy
This policy focuses on cookies and browser technologies. Read the broader explanation of account, project, usage, and service-provider data in the SQL Mocker Privacy Policy.
Privacy Policy →Contact
For a question about this policy or the technologies used by SQL Mocker, use the existing contact form.
Contact SQL Mocker →