Last updated: April 25, 2026
This policy explains what personal data SQL Boy collects, how we use it, and how data handling differs between browser-only product features and server-side account, AI, and billing features.
SQL Boy is built as a hybrid product. Some experiences run entirely in your browser, while others require server-side storage or third-party processors. We aim to describe those boundaries clearly rather than imply that every feature is purely local.
Many core SQL practice workflows stay on your device:
Other features are server-side by design, including account login, progress sync, AI chat history, usage tracking, billing, and support workflows. If you choose to use those features, the relevant data is processed on SQL Boy infrastructure and by the service providers listed below.
Depending on which features you use, SQL Boy may collect:
If you create an account, SQL Boy stores account identifiers such as your email address and authentication metadata through Supabase so you can sign in and associate usage, history, and billing state with the correct account.
We may store progress records and related activity so they can be tied to your account:
Local playground SQL is intended to stay in the browser. Account-linked progress data is separate from raw playground execution.
If you use SQL Boy AI, we store conversation history, message content, usage counters, lightweight page context, source references, and tool recommendation metadata so the sidebar can support history, retrieval, and entitlement enforcement.
AI is not a browser-only feature. When you send a message, the relevant prompt and context are processed server-side and sent to an external AI provider to produce a response.
If you purchase SQL Boy Pro, SQL Boy stores subscription state, entitlement snapshots, customer IDs, invoice-linked billing metadata, refund records, dispute records, and access-block status needed to operate recurring billing and fraud controls.
We and our infrastructure providers may collect technical information such as IP address, browser type, device data, request logs, and interaction analytics to operate, secure, and improve the service.
The information we collect is used solely for:
We do not sell your personal data to advertisers or third parties.
We use trusted third-party services to operate standard infrastructure:
SQL Boy may use Google AdSense or other advertising partners to fund free educational content and tools. If ads are enabled, Google and its partners may use cookies to serve personalized or non-personalized ads based on your visit to this and other websites.
You can learn more about how Google uses information from sites and apps, and you can manage ad settings through your Google account. If you do not want personalized ads, Google may still show contextual or non-personalized ads where legally permitted.
You may request access, correction, or deletion of your personal data, subject to legal and operational retention requirements. Individual AI conversations can be deleted from the product where that control is available. For broader account deletion or privacy requests, contact us directly.
We keep data for as long as needed to provide the feature you used, maintain account history, investigate abuse, comply with legal obligations, and resolve billing or support issues. Chat history may remain in your account until you delete it, while billing and fraud-related records may be retained longer.
If you have any questions about this Privacy Policy, email [email protected] or visit our Contact page for the current support channels.
For how SQL Boy reviews educational content, see our Editorial Standards. For team background and product context, visit the About page.