Privacy
What stays on your computer, what the server keeps, and how long it keeps it.
Last updated 27 September 2026
Qwizzd is a desktop application with a small server behind it. The application does the quizzing; the server exists to know who you are, whether your account has paid, and what is in the marketplace. This page says what each one stores, who else is involved, and what you can ask for. Qwizzd is run from England, and UK data protection law (the UK GDPR and the Data Protection Act 2018) applies to it.
At a glance
| Kind of data | Collected? | Linked to you | Shared with |
|---|---|---|---|
| Contact information | Your email address, only if you make an account. If you sign in with Google, Google tells us the address and that it is verified. | Yes | Clerk, which runs signing in and sends the sign-in emails. Google, only in that it knows you signed in here. |
| Identifiers | A username you choose, your profile picture if you set one, an account id, and a name for each computer you sign in on. | Yes | Your username is public on anything you publish. |
| Purchases | Whether you subscribe and until when. Not your card. | Yes | Stripe holds the card and the invoices. |
| Your decks and answers | Not collected. They stay on your computer. | — | Nobody. |
| Decks you publish | Only those you choose to send to the marketplace, with your username. | Yes, publicly | Everybody, by design. |
| Text you ask the AI to use | Passed through to the model provider for the reply, not stored. | No | OpenRouter and the model provider it routes to, for the reply only. |
| Usage, analytics, diagnostics | Not collected. | — | Nobody. |
| Location, contacts, browsing, advertising | Not collected. No tracking of any kind. | — | Nobody. |
Nothing is sold, and nothing is used for advertising. The rest of this page is the detail.
What stays on your computer
Your decks, your questions, any images and audio you add, every answer you have given
and every score. All of it is in a folder belonging to your user account
(%APPDATA%\Qwizzd on Windows, ~/Library/Application Support/Qwizzd
on macOS). None of it is sent anywhere, and there is no setting that would send it.
There is no analytics, no crash reporting and no telemetry in the application. It makes network requests for these reasons and no others: to check whether your subscription is still current, to look for a new version, to show and download marketplace decks when you open the marketplace, and, if you use them, to send the text of a question you asked to be written or an answer you asked to be marked.
What the server stores
| What | Why | Kept |
|---|---|---|
| Your email address | To know which account is yours and to match it to your subscription. | Until you delete the account. |
| Your username | The public name on anything you publish. Chosen by you, shown to everybody. | Until you delete the account. |
| Your profile picture's address | To show it next to your username on this site and in the app. Only if you set one. | Until you remove it or delete the account. |
| A name for each computer you sign in on | So you can see which machines are signed in and remove one. Taken from the computer's own hostname, with its platform (Windows or macOS). | Until you sign that machine out. |
| Your subscription status | To decide what the application unlocks. | Until you delete the account. |
| A Stripe customer reference | Only if you subscribe, so billing can be looked up. | Until you delete the account. |
| Decks you publish to the marketplace | The deck file, its listing and your username as the byline, so other people can read and take it. Only decks you choose to send. | Until it is withdrawn, removed, or the account is deleted; copies people took stay with them. |
| Your IP address, briefly | To stop anybody hammering the service: counts of requests per address; and while you pair a computer, a scrambled form of the address and the country it came from, so you can be warned if a pairing request did not come from you. | An hour or a day for the counts; ten minutes for pairing. |
Your password, if you have one, is not held by Qwizzd at all: signing in is run by Clerk, which keeps it in a form nobody can read back, along with the record that you signed in.
Cloudflare, which runs the server, keeps short request logs for fixing faults — up to a week.
Who else is involved
Each of these handles your data only to do its part:
| Who | What for |
|---|---|
| Cloudflare | Runs the website, the server, its database and file storage. |
| Clerk | Signing in, and the emails that confirm your address and sign you in. |
| Stripe | Taking payments and keeping invoices. |
| OpenRouter | Passing text to a language model when you use writing or marking. |
| Signing in with Google, if you choose it, and the support mailbox. |
Some of them are in the United States. Where your data goes outside the UK, it goes under the safeguards the law requires, such as the UK International Data Transfer Addendum or the UK–US data bridge.
Payments
Card details are handled by Stripe and are never seen by Qwizzd. What comes back is whether a subscription is active and when the paid period ends.
Writing and marking questions
These two features are optional and part of the paid plan. When you use one, the text you provide is sent to Qwizzd's server, which passes it to OpenRouter, which passes it to a model provider and returns the reply. Every request tells OpenRouter to use only providers that do not keep the text or train on it, so it is not stored on the way through and is not used to train anything, by us or by them. If you would rather it went nowhere, do not use those two features; everything else in the application works without them.
The only emails you get are the ones signing in needs — confirming your address, a sign-in code — sent by Clerk, and Stripe's receipts if you subscribe. No marketing email is sent, because there is no list to send one to.
Cookies
Only the ones the site needs to work, which is why it never asks you to accept any:
- Signing in (Clerk's:
__session,__client,__client_uatand similar). How the site knows you are signed in. They hold a session, not your details. qp: your plan, username and profile picture's address, so the pages can show who is signed in before anything else loads. It lasts 30 days, and signing out or deleting the account clears it.
There are no cookies for advertising or for counting visitors.
Why we are allowed to
Your account, subscription and published decks are handled because they are what you signed up for (performing a contract). The request counts, logs and pairing warnings are there to keep the service and your account safe (legitimate interests). Nothing relies on consent, and nothing is used for any other purpose.
Your rights
You can ask for a copy of what is stored about you, have it corrected, have it deleted, or have it given to you in a form you can take elsewhere, and you can object to how it is used. Write to support@qwizzd.net; you will get an answer within a month. If you are unhappy with the answer, you can complain to the Information Commissioner's Office.
Deleting everything
Delete account, in the Security section of the account page, cancels any subscription and removes the account, its sign-in with Clerk, its registered computers, its subscription record and its marketplace listings. The decks on your computer are yours and are not touched; delete the folder above if you want them gone too. Stripe keeps its invoices for as long as tax law requires.
Children
You must be at least 13 to make an account. Qwizzd collects no more from a young person than from anybody else, which is very little, and nothing about anybody is used for advertising or profiling.
Getting in touch
Questions about any of this go to support@qwizzd.net. If this page changes in a way that matters, the date at the top will move.
This describes what the software actually does, written by the person who built it. It is not legal advice and it is not a lawyer's document.