Legal
Privacy Policy
Last updated: October 8, 2026
1. Overview
SQL Practice ("we", "us", "the site") provides browser-based learning and practice for SQL, Python, JavaScript and TypeScript. Your code runs locally and your learning progress stays in your browser. This policy also explains the request information processed by our host, Vercel, the cookieless analytics currently enabled, and information you choose to send when you contact us. Advertising is not currently enabled.
2. How the playgrounds and exercises handle your data
The query editor, sample database, query results and exercise answer checking are powered entirely by code running inside your own browser tab: JavaScript served from this site, and the SQLite database engine compiled to WebAssembly. The site does not upload the SQL you write, your query results, your exercise answers or changes to the sample data for execution or answer checking. Checking an exercise answer runs both your query and the expected solution locally and compares the results in your browser; nothing about your attempt is uploaded. Closing or refreshing the tab clears the in-memory database back to its original state.
The same is true of the other languages that run here. Python, JavaScript and TypeScript programs are executed inside your own browser: JavaScript and TypeScript in an isolated background thread (a Web Worker) without direct access to the page, and Python by a copy of the CPython interpreter compiled to WebAssembly (Pyodide) that this site serves from its own domain. The code you write, the input you give it and the output it prints stay on your device. Lesson examples and exercise tests run the same way. This site does not send your code to an external execution service. Only languages with a working local browser runner are published. Common JavaScript network APIs are disabled, and the site's security policy blocks requests to external origins. Python can still make requests to this site's own origin through its JavaScript bridge; local execution is not a guarantee that every possible program is unable to make a request.
3. Local storage
The site uses your browser's localStorage
to remember a small amount of information between visits:
- your light/dark theme preference;
- your recent query history in the Playground;
- which Practice exercises you have solved, and the dates you practised on, so your progress and streak can be shown;
- the name you optionally type onto a Certificate of Completion;
- whether you switched on the optional practice stopwatch (on/off only — no times are stored);
- the lessons you have marked completed and the coding exercises and challenges you have attempted or solved, with the dates, so the language pages can show your progress;
- code you typed into an exercise or challenge that you have not finished, and what is in the playground editor, so it is still there if you reload the page.
There are no user accounts on this site. This learning record is stored only on your own device and is never sent to us. Because it lives in one browser, it does not follow you to another device, and clearing your browsing data will erase it. You can remove it at any time using the Playground's History panel, the "Reset progress" button on the SQL Practice page for that page's exercise record, or your browser's site settings to clear all local data for this domain. Resetting SQL progress does not erase Python or JavaScript progress or editor drafts.
Separately from local storage, the site registers a service worker, which asks your browser to keep a copy of the site's own files — pages, stylesheets, fonts and the database engine — so that it loads quickly and can work offline. The cache contains copies of served files and their resource URLs, not your program output or exercise results. It does not upload your learning record. Clearing your browsing data removes it. The Python runtime and the TypeScript compiler are large files; your browser can reuse them from its ordinary cache while those copies remain available. Clearing or evicting that cache may require another download.
4. Cookies and advertising
This site sets no cookies of any kind. Not for advertising, not for logins — there are no accounts — and not for the traffic measurement described in Section 5, which is deliberately cookieless. The small amount of information the site remembers between visits is held in your browser's local storage, described in Section 3, which the site does not upload. This storage supports learning preferences and progress; it is separate from the cookieless traffic measurement. No advertising consent banner is currently displayed. If services or their storage behavior change, we will review the disclosure and applicable consent requirements before enabling them.
We may in future display advertisements served by Google AdSense to help cover the cost of running the site. No ads are running today. If they are enabled, those third parties may use cookies, web beacons or similar technologies to serve ads based on your prior visits to this and other websites, and this policy will be updated before that happens. Should that day come, you would be able to opt out of personalised advertising through Google's Ads Settings or www.aboutads.info, and visitors in regions requiring prior consent would be asked for it first.
5. Analytics
Since 22 September 2026 this site measures its traffic with Vercel Web Analytics and Vercel Speed Insights. Vercel is the company that hosts this site, so it already serves every page you read; these two features additionally count page views and measure how quickly pages load.
What they record. The page visited, the referring page if there was one, approximate location information derived from the request, and the general type of device and browser. Speed Insights additionally records loading measurements — how soon the page became visible, how quickly it responded. None of it is linked to a name or a site account. Vercel's Web Analytics documentation says it uses a hash of the incoming request to distinguish visitors within a session and discards that session after 24 hours. This is not a cross-site identifier.
What they do not record: your SQL, or your searches. A page's address
can carry text after a # — a playground link keeps its query there,
and the search page keeps your search words there. Before either feature sends
anything, a short script on every page removes everything after ? or
# from the address, and if it cannot, nothing is sent. The SQL you type
is not included in those measurement events. One correction, stated plainly: from 22 to 24
September 2026 that script was not yet in place, so for a playground page opened from a
tutorial's Run link, the address that was counted included that example's SQL.
Where measurement goes. The two scripts are served from this site's own domain, at
/_vercel/insights/ and /_vercel/speed-insights/, and send measurements to
endpoints on the same domain. Those endpoints are operated by Vercel: a same-domain request is still processed by
our hosting provider. Our October 8, 2026 browser check observed no cookies or Set-Cookie response
headers on the tested pages, and observed page-view events containing the cleaned page address. This observation
describes the tested configuration; it does not mean that Vercel receives no request information.
What we do with it. Find out which tutorials people actually read, and whether the site is fast enough on real devices. That is the whole purpose. The figures are aggregate and are not used by the site to identify individual learners. Local progress, editor drafts and exercise answers are not included in the measurements sent by the site. Vercel processes them for us as our hosting provider. See its Web Analytics privacy documentation, Speed Insights privacy documentation and privacy notice at vercel.com/legal/privacy-policy.
If you would rather not be counted, any content blocker that blocks those two script files will stop it, and the site behaves exactly the same without them — every tutorial, every exercise and the playground work unchanged.
6. Third-party services
Site assets and runtime files are served from this domain. Everything your browser needs — the page itself, the styling, the fonts, the SQL engine (SQLite, compiled to WebAssembly), the Python runtime (Pyodide) and the TypeScript compiler, the code that runs your programs, and the two measurement scripts described in Section 5 — is served from this site's own domain. Vercel receives the requests needed to deliver those files, including the requested path, IP address and browser/request information. Hosting and security processing is separate from the aggregate measurements described in Section 5. We do not claim that no information is processed simply because resources use this domain. The typefaces used to be loaded from Google Fonts, which meant your browser contacted Google's servers and revealed your IP address on every visit; they are now hosted here instead, specifically so that no longer happens.
The open-source components the site is built from, and their licences, are listed on our Open Source Licenses page.
If you follow an external link, the destination's own privacy practices apply. If you email us, your email address and the message you choose to send are processed by our mailbox service so we can respond. Do not include passwords, credentials or private production data in a message.
Google AdSense is not currently enabled on this site and serves no ads today. If it is enabled later, your browser would then load ad code from Google, which may set cookies as described in Section 4. This policy and its "Last updated" date will be revised before that happens.
7. Children's privacy
This site is not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us personal information, please contact us and we will remove it.
8. Your rights over your data
Depending on where you live and the applicable law, you may have rights to access, correct, delete or obtain a copy of personal information, or to object to certain processing. Contact us using the details below to ask about information you have provided or to make a request.
There are no site accounts, and the analytics dashboard provides aggregate statistics rather than a named visitor record. Hosting request information and any correspondence you send can still be processed as described above. We will review requests against the information we actually hold and coordinate with service providers when appropriate; we do not promise that a browser developer-tools check reveals every server-side processing activity.
Your practice progress, theme preference, query history and editor drafts are stored locally, as described in Section 3. The "Reset progress" button on SQL Practice clears that page's progress record. To remove all local records and cached files for the site, clear site data for this domain in your browser settings. Clearing local browser data does not delete an email you have sent or information already processed by the hosting provider.
If you still want to exercise a right or ask a question about any of this, contact us using the details in the section below and we will respond.
9. Accessibility
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. Our automated checks use axe-core on the original SQL and site pages and representative generated page types in light and dark themes. They check issues such as contrast, headings, form labels and landmarks; keyboard and mobile interactions also receive browser checks. This is test coverage, not a claim that every assistive-technology combination has been verified.
Automated checks catch a great deal but not everything, and no site is ever finished on this front. If you hit something that does not work with your screen reader, magnifier or other assistive technology, please tell us using the contact details below — it will be treated as a bug, because that is what it is.
10. Changes to this policy
We may update this Privacy Policy from time to time, for example to reflect a new advertising or analytics integration. The "Last updated" date at the top of this page will always reflect the most recent revision.
11. Contact us
Questions about this policy? Email contact@sqlpractice.co.in.