SQL Mocker
Privacy Policy
This page summarises the information SQL Mocker uses to provide the service. It is a practical product draft and should be reviewed by a qualified legal adviser before public launch.
Information We Store
SQL Mocker may store account profile information such as your email address, display name, optional company and role, usage events, saved projects, uploaded schema metadata, query history, feedback, contact messages, and billing status.
Database Credentials
SQL Mocker does not request or store database usernames, passwords, connection strings, or server access details, and it does not connect directly to your real database. Users provide schema metadata only, such as table names, column names, data types, and relationships.
How Information Is Used
We use this information to authenticate users, provide saved workspaces, generate and refine SQL, track usage limits, improve product quality, respond to feedback, and operate subscription access.
Service Providers
SQL Mocker uses Clerk for authentication, Stripe for payments and billing, OpenAI for AI-assisted generation, and a Postgres database provider such as Supabase or Neon for application storage. Payment card details are handled by Stripe and are not stored by SQL Mocker.
Your Responsibilities
Do not upload information you are not authorised to use with SQL Mocker. Avoid adding production secrets, personal data, confidential records, or sensitive business data unless your organisation allows it.