Privacy

We use Vercel Web Analytics to count page views and see which pages are popular. It is cookieless and does not collect personal data.

• What is counted: the page path (without query strings), referrer, country, and browser / device type.
• No cookies are set, IP addresses are not stored, and visitors can't be followed across sites or across days.
• Only aggregated numbers are visible to us.

Everything you enter in the practice apps — carts, bookings, transfers, test logins — is fake and stays in your own browser (localStorage). It is never sent to our servers. Clear your browser's site data to reset it.

Please don't enter real personal, payment or login details anywhere on this site — use the test data shown on each page.

The QA Assistant's instant answers are computed in your browser and send nothing to a server.

When you use an AI feature (the AI tools, Generate script, the AI coach or Ask AI), the text you submit is sent to our server and on to a third-party AI model provider to generate the answer. We don't store it. To prevent abuse, the server counts your requests over the last hour using your IP address. That count lives only in server memory — it isn't written to a database or used for analytics — and is discarded when the server restarts.

Don't paste secrets, credentials or personal data into the AI tools.

The RAG practice bot uses no AI model. On its page, answers are computed in your browser. Its practice API (/api/rag-bot) computes the answer on our server and returns it; questions are not stored, and the same short-lived, in-memory rate limit applies. Its store and policies are fictional.

The SQL Playground runs your queries in your own browser. To do that, it loads the open-source sql.js library from the jsDelivr CDN — like any website, jsDelivr sees your IP address when your browser downloads it. Your queries are never sent anywhere; your solved exercises are remembered only in your browser.

The Code Playground runs your code in your own browser, in a background worker — running it sends nothing to us. For Python and TypeScript it first loads the open-source Pyodide (Python) or TypeScript compiler from jsDelivr, which, like any website, sees your IP address when your browser downloads them. For C#, the .NET runtime and compiler come from our own site. For Java, it loads the CheerpJ Java runtime from Leaning Technologies’ CDN (cjrtnc.leaningtech.com), which likewise sees your IP address; your code is compiled and run in your browser and is not sent to them. If you are signed in, the files you write and the input you type are saved to your account on our server so they are there next time, on any device; we store only that code, under your sign-in id. As a guest, nothing is saved: your work is kept only in the open browser tab. If your own code calls fetch, those requests go from your browser to the address you wrote.

The Practice REST API runs on your own computer. Requests you send to it — including from the console on that page — go straight from your browser to your machine and never reach our servers. Its optional Swagger page loads its viewer from jsDelivr.

The daily challenge works without an account. As a guest, your streak and badges stay in your own browser. When you pick an answer, your choice is sent to our server only to be checked; it is not stored.

If you choose to sign in with Google, your streak is kept on our server so it can't be edited and it follows you to other devices. In that case:

• We ask Google only for your basic profile. We do not ask for or store your email address, contacts or anything else.
• We store the account's numeric id from Google, which daily questions you answered and whether each was right, and the badges you earned. This is held in a hosted database (Upstash Redis).
• Your display name is kept only in the sign-in cookie in your browser, not in our database.
• You can remove everything at any time with Delete my data on the daily challenge page. That includes the code you saved in the Code Playground.

We store your light/dark theme choice and practice-app state in your browser's localStorage. These are functional only and never leave your device.

We set cookies only if you sign in to the daily challenge: one that keeps you signed in for 30 days, and one that tells the page you are signed in. A short-lived cookie is also used while the Google sign-in is in progress. They are not used for tracking or advertising, and signing out removes them.

The site is hosted on Vercel, which may keep standard, short-lived server logs (such as request paths and IP addresses) for security and reliability, under Vercel's own privacy policy.

Bug reports and feature requests go to a public GitHub repository. Anything you write there is public and handled under GitHub's own privacy policy.

Questions about privacy? Email contact@practiceqaautomation.com or see the About page.