Privacy policy
What we collect when you use the dashboard or a site shows a WAU Captcha challenge, and what happens to it.
Last updated 16 October 2026
Draft, under review
1. Who runs WAU Captcha
WAU captcha runs waucaptcha.com, the website and dashboard, and api.waucaptcha.com, the captcha API. For any question about your data, write to contact@waucaptcha.com.
2. Dashboard accounts
- When you sign in with Google we receive, and keep in our database, the email address, the display name and the account id of your Google account, to know which account is yours. We never receive your Google password.
- With the account we keep its plan, when a paid plan ends, when the account was created and whether an administrator banned it.
- Your API keys: their names, site keys and secret keys, whether they are active or suspended, the IP addresses and domains you allow with the descriptions you give them, whether they require behaviour data, and an activity log of what was changed on them, when and by whom (you, an administrator or the system). Secret keys never appear in that log.
- If you ask for a review of a suspended or flagged key, the message you write and the administrator's answer.
3. Each captcha challenge
- For every challenge a site asks for, one row in our database: the API key, the challenge type, when it was issued, whether it was answered and answered right, and the verdict and score of the behaviour check. The row holds no IP address, no browser details and no behaviour data.
- While a challenge can be answered, 2 minutes at most, Redis keeps its answer, the visitor's IP address, the website it was asked for from (its origin) and a hash of the browser's User-Agent, to check that the answer comes from the same browser. Answering it, right or wrong, deletes it.
- A token earned by a right answer stays in Redis until the site's server redeems it, 2 minutes at most, with the API key, the challenge type, when it was solved, the website's host name and the behaviour verdict.
- Against abuse, Redis counts requests per IP address in one-minute windows, and wrong answers, automated verdicts and the automatic passes of auto_check per IP address over the last hour, those without a clearance too. The passes of each auto_check clearance are counted for an hour and a day under its random id, which holds no IP address. Daily counters per account and per key (challenges, answers, right answers) live for 24 hours and hold no IP address.
4. Behaviour data
- While a challenge is on screen, the SDK records where the pointer moves relative to the widget, the time between key presses in the answer box (never the keys), how many input, paste and script-made events happened, how long the page was hidden, and a few hints the browser gives about itself: whether it reports automation, a headless browser or no languages.
- It is sent with the answer, judged in memory and dropped. Only the verdict (human, suspicious, automated or not measured), the score and short reason codes are kept: in the challenge's row and, until it is redeemed, with the token.
5. Payments
For each purchase we keep the plan, the period, the amount, the payment code, its status, SePay's transaction id and when it was paid. You pay on SePay's page by bank transfer; we never see your bank or card details.
6. Cookies and browser storage
- wau_session keeps you signed in, for 24 hours.
- wau_admin_session does the same for administrators, and is sent to /admin only.
- wau_google_nonce ties a Google sign-in to your browser, for one hour.
- wau_locale remembers the language you chose, for one year.
- wau-theme, in local storage, remembers the light or dark theme.
- On the websites that use WAU Captcha, once a visitor solves a puzzle the SDK keeps wau-captcha:clearance:<site key> in local storage: a signed clearance with a random id, the API key, a hash of the User-Agent and its dates, which lets that browser pass auto_check there for up to 7 days. It goes back to WAU Captcha with auto_check answers only.
- There are no analytics or advertising cookies and no tracking scripts. Google's sign-in script loads from accounts.google.com on the sign-in pages only.
7. Server logs
The services write operational logs: errors, with challenge ids, API key ids or payment codes, refused payment notifications with the address they came from, and for each auto_check answer a line with its challenge id, whether it passed, the score, the reason codes, the pointer type, counts of how the mouse moved, whether a clearance came with it and whether the address belongs to a hosting provider, without the visitor's IP address, User-Agent or clearance. They stay on the server for [RETENTION: e.g. 14 days].
8. Where it is stored
Everything is hosted by Amazon Web Services in the ap-southeast-1 region, Singapore: the server, the PostgreSQL database and Redis.
9. How long we keep it
- Challenges and tokens: 2 minutes at most.
- Counters per IP address: one minute, and one hour for the history of wrong answers and of automatic passes. Daily counters: 24 hours.
- Challenge rows, the usage history: there is no deletion rule yet. [RETENTION: e.g. 12 months]
- Accounts, API keys and their activity log: as long as the account exists. A deleted key stays, marked deleted, for its usage history. [RETENTION: e.g. erased 30 days after the account is closed]
- Payments: [RETENTION: e.g. 10 years, as Vietnamese accounting law requires]
- Server logs: [RETENTION: e.g. 14 days]
10. Who can see it
You see your own account, keys, usage and activity. The administrators of WAU captcha see accounts, keys without their secret keys, usage, payments and reviews, to run and protect the service. The processors below handle data only to provide their part of the service. We do not sell data or share it for advertising.
11. Processors
- Amazon Web Services: hosting, in Singapore.
- Google: sign-in with your Google account.
- SePay: payments by bank transfer.
12. Your choices
Write to contact@waucaptcha.com to get a copy of your data, to correct it or to have your account deleted. [RESPONSE TIME: e.g. within 30 days]
13. Changes
Changes to this policy are announced here and on the changelog.