Privacy
Results are from the release that's live, deployed 17 Nov 2026 (667a7eb): 453 of the 459 checks behind the security, privacy and terms pages passed.
Sam Cheney runs PocketQA. This page says what PocketQA collects, why, where it's kept and for how long, and what you can do about it. It's written to match what the service actually does; the technical detail is in Security.
What we collect
About you. Your name and email address (or GitHub username) from the way you sign in, and which teams you're on. We don't get or keep your password: GitHub, Google, Apple, Microsoft, your company's single sign-on or an emailed link proves who you are, and we keep a signed cookie that says so for 30 days after you last opened PocketQA (90 at most), and one that says which way you signed in (not who you are), for a year, so we can take you back that way. Signing out removes both. While you sign in, a few more last only for that step (at most 15 minutes), and an early-access invite code you enter is kept in one for an hour.
Checked by 13 tests before every release: all passed on the live release
- one sign-in page, every way in end to end Passed
- never past 90 days from signing in end to end Passed
- signing out forgets the way in end to end Passed
- and the link works once end to end Passed
- signing out ends that person end to end Passed
- it works only in the browser that asked for it end to end Passed
- an email link asked for from another site is refused end to end Passed
- SSO: a public email provider can end to end Passed
- its client secret signed with the team end to end Passed
- required: a company email can only sign in through SSO end to end Passed
- cookies: every one the Worker sets is described on the page service Passed
- signing out removes both sign-in cookies service Passed
- for N days after you last opened service Passed
Your network address. Cloudflare sees it on every request, as it carries them. The service keeps it only in counts: how often one address signs up, asks for a sign-in link, joins the waitlist, tries an invite or pairing code, or makes hundreds of requests a minute, so one place can't crowd out the rest. Each count is deleted once its minute, hour or day is over, as is the count of sign-in links an email address asked for. It's never kept with your account.
Checked by 4 tests before every release: all passed on the live release
- network addresses: counted only for sign-ups service Passed
- never with an account service Passed
- every count older than the minute, hour or day it counts goes service Passed
- allow, pairTry and mlinkPut each sweep first service Passed
The waitlist. If you join the waitlist before you have an account, your email address and the day you joined, and nothing else. We use it only to invite you to PocketQA, and delete it once you've joined or as soon as you ask.
Checked by 3 tests before every release: all passed on the live release
- waitlist: an email address and when, nothing more service Passed
- joining the waitlist says so, once end to end Passed
- an operator can take someone off the waitlist end to end Passed
About your sites. The addresses and pages you add, the flows you write, and the settings you choose.
Checked by 2 tests before every release: all passed on the live release
- a change from somewhere other than the dashboard is refused end to end Passed
- a teammate can't let support in; only the owner end to end Passed
Test results. For each test: which device, whether it passed, how long pages took, each page's errors and failed requests, the last few lines of each device's console, and each flow step's words and whether it passed, with what each tap hit and a line of what was on the screen after it (unless your team switches that off). Before anything leaves your lab computer, addresses lose their query strings, tokens and email addresses are masked, and anything a flow typed is left out.
Checked by 21 tests before every release: all passed on the live release
- nothing of anyone else's: no customers, projects or results installer Passed
- what leaves: addresses without their query strings lab Passed
- no tokens or emails lab Passed
- never what a journey typed lab Passed
- the last 15 console lines at most lab Passed
- screen text only while the team sends it lab Passed
- keyed by the lab lab Passed
- the computer sends no network name lab Passed
- the computer sends its model identifier (which model and year), never its serial number or its name lab Passed
- the computer's battery leaves as its level lab Passed
- the Wi-Fi network's name never leaves the computer lab Passed
- no internet: the phone's Wi-Fi network name never leaves the computer lab Passed
- the site's stack leaves as plain names only lab Passed
- readings that move every look aren't a change worth sending lab Passed
- a page that looks different from its last clean run says how much lab Passed
- a flow step live is what the result sends for it, screen text on lab Passed
- a flow step live is what the result sends for it, screen text off lab Passed
- and with screen text off, no tapped words and no screen text lab Passed
- lab/agent.py tells each run the team's screen-text choice lab Passed
- masked by the result's own rule: no query string, no typed text, no email end to end Passed
- and with the team's screen text switched off, no tapped words and no screen text end to end Passed
About your lab computers. Their model and operating system, the phones plugged into them (model and version, with a short id we make, never the serial number), their setup checks and the end of their own log.
Checked by 30 tests before every release: all passed on the live release
- pairing again leaves the key readable by this user alone lab Passed
- setup never keeps a computer awake always lab Passed
- the lid watcher runs a closed Mac only on its charger lab Passed
- installed once, as root lab Passed
- and undoes an older setup that did lab Passed
- the real list is read over https only, from Chrome for Testing lab Passed
- a download that says it's another version is refused, not used lab Passed
- a Linux lab runs as its user's own systemd service, never as root lab Passed
- and setup uses sudo only to install packages lab Passed
- ChromeDriver downloads only use Google's Chrome for Testing storage (#1091) lab Passed
- ChromeDriver downloads refuse redirects to another host (#1091) lab Passed
- ChromeDriver versions from arguments and the list cannot form paths (#1091) lab Passed
- Safari repair refuses to quit when idle time is unknown (#1217) lab Passed
- Safari repair waits for the person when Safari will not quit (#1217) lab Passed
- Safari quit never force-ends the browser when a prompt keeps it open (#1217) lab Passed
- and the code doesn't work twice end to end Passed
- guessing pairing codes is cut off after ten a minute end to end Passed
- a computer that isn't this one can't take its work end to end Passed
- a message caught on the way and sent again is refused end to end Passed
- its computer is cut off at once end to end Passed
- a code works once, and the installer says why installer Passed
- the lab's key (issue 523): on a Mac, pairing keeps it in the login Keychain, not in a file lab Passed
- never on a command line lab Passed
- an older lab's key file moves into the Keychain on its next start lab Passed
- elsewhere (Linux) a file only this user can read lab Passed
- its key readable by this user alone installer Passed
- uninstalling takes it off its account lab Passed
- refused for five minutes, it counts as removed and says so once lab Passed
- and then nothing leaves it lab Passed
- its setup check says it was removed lab Passed
Screenshots, only if you choose. If your team switches on step screenshots, small screenshots of each flow step, kept 30 days. If your team switches on a site's picture, one small screenshot of its first page after each test, the newest only, shown only to your team. If you add a public site, the service takes one look at it at phone and laptop size (First look) and keeps the latest one.
Checked by 13 tests before every release: all passed on the live release
- a site's own step screenshots: on for that site with the account's off end to end Passed
- switched off for the site, its kept ones are gone at once end to end Passed
- step screenshots are off unless the team switches them on end to end Passed
- a lab's screenshots aren't kept while it's off end to end Passed
- switched off, the ones kept are gone at once end to end Passed
- and the run's report link shows them too end to end Passed
- from its report link too end to end Passed
- a site's picture isn't kept until the team turns it on for that site end to end Passed
- on, the newest is kept and shown to the team (and nobody else) end to end Passed
- off, the lab's is gone at once end to end Passed
- First look opens the site at phone and laptop size end to end Passed
- and stays out of the way for an address that isn end to end Passed
- lookable: public web addresses only service Passed
Usage. How far each account has got with setting up (when it added a site, was shown the install command, connected a lab, had a device ready, ran its first test and saw its first pass), counted without names; and for each request to the service, its route, status and timing, to keep the service working.
Checked by 13 tests before every release: all passed on the live release
- every event name and field is on the allowlist service Passed
- a site address, a URL or an email in any field refuses the event service Passed
- an error's message has them taken out by the same patterns service Passed
- an event carries the random usage id, never the account service Passed
- usage data: a signed-in batch lands end to end Passed
- signed out, refused end to end Passed
- from another site, refused end to end Passed
- a site address in an event is refused end to end Passed
- Do Not Track or Global Privacy Control: nothing kept end to end Passed
- switched off for the account: dropped end to end Passed
- the dashboard sends its own usage end to end Passed
- and with Global Privacy Control, nothing at all end to end Passed
- the sanitiser refuses every fixture that carries a site address, a URL or an email service Passed
How the dashboard and agent tools are used. To see where people get stuck, the dashboard tells PocketQA which pages and dialogs are opened, when Test now, a fix button or a setting is used, how long each page took to get its data, the same button pressed again within a second, and the dashboard's own script errors (the message only, with addresses, URLs and emails taken out); and for agents, each tool's calls and errors and where in test, wait, read, fix and test again they stop. Each is counted against a random number made for your account, never its name, a person, an email, a site, an address, a URL or an IP, and anything that looks like an address, a URL or an email is refused. It goes only to PocketQA's own service (no analytics company, no scripts or pixels from anywhere else, no recording of your screen). Your browser sends none of it when it's set to Do Not Track or Global Privacy Control, and an admin can switch it off for the whole account (People › Usage data).
Checked by 13 tests before every release: all passed on the live release
- every event name and field is on the allowlist service Passed
- a site address, a URL or an email in any field refuses the event service Passed
- an error's message has them taken out by the same patterns service Passed
- an event carries the random usage id, never the account service Passed
- usage data: a signed-in batch lands end to end Passed
- signed out, refused end to end Passed
- from another site, refused end to end Passed
- a site address in an event is refused end to end Passed
- Do Not Track or Global Privacy Control: nothing kept end to end Passed
- switched off for the account: dropped end to end Passed
- the dashboard sends its own usage end to end Passed
- and with Global Privacy Control, nothing at all end to end Passed
- the sanitiser refuses every fixture that carries a site address, a URL or an email service Passed
Where your account came from. Once, when your account is made: whether you came through a coding agent (and that agent's app name and major version, such as "claude-code 2") or the website, the domain of the site that linked you here (only the domain, such as "github.com": never the page or anything in its address), and a short tag from our own links (npm, pypi, listing or launch). Until you sign up, the website keeps that domain and tag in a cookie of its own for 30 days; if you connect an agent before you have an account, we keep its app name and major version against your sign-in until your account is made. We also keep your account's plan and price, with the date each began. We use these, counted by source, to see which places bring people who stay; they're stored without your account's name and go when you delete your account. Nothing else about you, your address or the page you came from is kept.
Checked by 9 tests before every release: all passed on the live release
- an account made through MCP: arrival agent, its client service Passed
- a referrer with a path and query is its domain only service Passed
- nothing else is stored: only the allowed fields service Passed
- the source is kept by the funnel's anonymous key service Passed
- the landing cookie: domain and ref only, first-party, HttpOnly, 30 days service Passed
- a pending note older than 30 days service Passed
- deleting the account deletes its source and plans service Passed
- ref tags: only ours service Passed
- cookie (HttpOnly, N days) service Passed
Reports about PocketQA itself. When your coding agent reports a problem with PocketQA (its report_to_pocket_lab tool): what it wrote, its lab's state and, for a test, each flow step and what each tap hit. Never console output, page contents, screenshots or anything typed into your site. And in a new account's first week, before its first passing test, the service notes by itself a test that ran nothing or setup that stopped for 30 minutes, in its own fixed words.
Checked by 38 tests before every release: all passed on the live release
- report_to_pocket_lab: a reference, grouped with others end to end Passed
- an account sends 10 reports an hour at most end to end Passed
- a customer's account sends 10 reports an hour and 40 a day at most service Passed
- PocketQA's own accounts, testing PocketQA itself, 30 an hour and 200 a day service Passed
- a typed step keeps the field, never the text service Passed
- the issue says how many accounts, never which service Passed
- and no site addresses service Passed
- scrub: addresses, emails, tokens and long numbers go service Passed
- scrub: a site's name goes whatever it ends in, and so does an address on a network service Passed
- and marks what was reported as untrusted evidence service Passed
- a customer's first report: filed at once service Passed
- its words never leave early: the body has the service's facts and its reference service Passed
- and issueBody leaves them out unless told they may leave service Passed
- two accounts, three reports: words not yet service Passed
- a third account: its words may leave service Passed
- five reports from one account: its words may leave service Passed
- a report from one of PocketQA's own accounts: filed on its first, with its words service Passed
- one a customer's report shares keeps its words in like a customer's service Passed
- a session tester's report: filed on its first with its words, labelled hotfix and urgent service Passed
- not once the session is off (no testers): its words wait as any customer's service Passed
- and another customer's report in the same issue keeps the words in, though a tester shares it service Passed
- failures labelled the lab's aren't reports: they wait for three accounts or five service Passed
- labels by rule: a wrong verdict is accuracy, urgent, the fixer service Passed
- a customer's with none of its words, its reference instead service Passed
- said: on, until, testers as a count (never their accounts) service Passed
- hours: more than 0, at most 12 service Passed
- a first-hour issue is filed on its first note, with no agent and no session mode service Passed
- labelled hotfix and urgent service Passed
- the issue says how many accounts, never which, and what the service saw service Passed
- a cause is a plain code, whatever came in service Passed
- and the five-minute issue sync notes stalls before filing, ours left out service Passed
- an issue's fields are only known values service Passed
- close its own quote service Passed
- a test_id that is not a test id is refused end to end Passed
- something wrong here: emails, web addresses service Passed
- "Something wrong here?" from a setup step: a report end to end Passed
- with no email or address in it end to end Passed
- a report never carries console output, page contents, screenshots or typed text service Passed
We never collect your source code, and PocketQA's lab computers visit your site as a visitor would.
Cookies and browser controls
The sign-in, sign-in preference and attribution cookies described above serve different purposes. You can remove or block cookies in your browser; blocking sign-in cookies can prevent the dashboard from working. Removing a cookie does not delete your account or its stored results. The usage-data controls described above are separate from signing in.
Checked by 2 tests before every release: all passed on the live release
- cookies: every one the Worker sets is described on the page service Passed
- for as long as it says service Passed
Connected agents and shared reports
Only connect an agent or share a report with people and services you intend to give the results to. Your agent provider handles information it receives under its own terms and privacy policy. Check those before connecting it, and avoid putting personal or confidential information into test sites and flow instructions unless you are authorised to do so.
Why
To run the tests you ask for and show you the results (and, when a device fails your site, to test that device once more on its own, to confirm whose the failure is); to tell you and your team when something breaks (by the webhook or email you set); to keep accounts apart and the service safe; and to see where people get stuck setting up, so we can fix it. We don't sell personal information, and we don't use it for advertising.
Who else handles it
- Cloudflare runs the service and stores its data (including backups, encrypted with a key Cloudflare doesn't hold).
Checked by 8 tests before every release: all passed on the live release
- backups: every object, encrypted, by day end to end Passed
- for operators only end to end Passed
- encrypted: no site address in the bucket service Passed
- production restores only on the day a person set ALLOW_RESTORE to service Passed
- a corrupt final encrypted piece is refused before any object is wiped service Passed
- an unfinished sequence is refused before any object is wiped service Passed
- a piece changed after validation is refused before it is written service Passed
- where it's kept service Passed
- GitHub, Google, Apple and Microsoft when you sign in with them.
Checked by 13 tests before every release: all passed on the live release
- one sign-in page, every way in end to end Passed
- never past 90 days from signing in end to end Passed
- signing out forgets the way in end to end Passed
- and the link works once end to end Passed
- signing out ends that person end to end Passed
- it works only in the browser that asked for it end to end Passed
- an email link asked for from another site is refused end to end Passed
- SSO: a public email provider can end to end Passed
- its client secret signed with the team end to end Passed
- required: a company email can only sign in through SSO end to end Passed
- accounts.google.com service Passed
- appleid.apple.com service Passed
- login.microsoftonline.com service Passed
- PocketQA's issues on GitHub hold what it files about problems in PocketQA itself, on its own private repository: grouped by cause, with counts, devices, releases and test ids. Never your account's name, a site's address, an email or anything a person typed. What an agent wrote in a report goes there only once three accounts or five reports share the same problem; until then it stays in the service.
Checked by 39 tests before every release: all passed on the live release
- report_to_pocket_lab: a reference, grouped with others end to end Passed
- an account sends 10 reports an hour at most end to end Passed
- a customer's account sends 10 reports an hour and 40 a day at most service Passed
- PocketQA's own accounts, testing PocketQA itself, 30 an hour and 200 a day service Passed
- a typed step keeps the field, never the text service Passed
- the issue says how many accounts, never which service Passed
- and no site addresses service Passed
- scrub: addresses, emails, tokens and long numbers go service Passed
- scrub: a site's name goes whatever it ends in, and so does an address on a network service Passed
- and marks what was reported as untrusted evidence service Passed
- a customer's first report: filed at once service Passed
- its words never leave early: the body has the service's facts and its reference service Passed
- and issueBody leaves them out unless told they may leave service Passed
- two accounts, three reports: words not yet service Passed
- a third account: its words may leave service Passed
- five reports from one account: its words may leave service Passed
- a report from one of PocketQA's own accounts: filed on its first, with its words service Passed
- one a customer's report shares keeps its words in like a customer's service Passed
- a session tester's report: filed on its first with its words, labelled hotfix and urgent service Passed
- not once the session is off (no testers): its words wait as any customer's service Passed
- and another customer's report in the same issue keeps the words in, though a tester shares it service Passed
- failures labelled the lab's aren't reports: they wait for three accounts or five service Passed
- labels by rule: a wrong verdict is accuracy, urgent, the fixer service Passed
- a customer's with none of its words, its reference instead service Passed
- said: on, until, testers as a count (never their accounts) service Passed
- hours: more than 0, at most 12 service Passed
- a first-hour issue is filed on its first note, with no agent and no session mode service Passed
- labelled hotfix and urgent service Passed
- the issue says how many accounts, never which, and what the service saw service Passed
- a cause is a plain code, whatever came in service Passed
- and the five-minute issue sync notes stalls before filing, ours left out service Passed
- an issue's fields are only known values service Passed
- close its own quote service Passed
- a test_id that is not a test id is refused end to end Passed
- something wrong here: emails, web addresses service Passed
- "Something wrong here?" from a setup step: a report end to end Passed
- with no email or address in it end to end Passed
- an agent's words reach GitHub only at FILE_AT service Passed
- api.github.com service Passed
- Anthropic runs Claude, which PocketQA's own engineering agents use to fix problems in PocketQA. They read those GitHub issues and the customer suggestions there, and nothing else of yours.
Checked by 33 tests before every release: all passed on the live release
- a fire: one POST to the API's own address for that routine, the token as a bearer service Passed
- a redirect isn't followed (the token goes nowhere else) service Passed
- never a token service Passed
- sent once and never again service Passed
- runFires: each claim it may take is saved as started before its fire is sent service Passed
- the body sent is the Role: line and the claim's start text, nothing else service Passed
- a refusal (4xx): the claim is given back service Passed
- and a second runFires sends nothing for it service Passed
- a claim older than 13 minutes isn't the service's service Passed
- for any claim age, whatever the service may take the dispatcher can't service Passed
- a routine whose hold ended under 2 minutes ago isn't the service's yet service Passed
- at every moment around a hold's end, the hourly limit's end and a new token service Passed
- a token newly set: the service notes when it first saw it and fires nothing for 2 minutes service Passed
- "the dispatcher saves after runFires", "the dispatcher saves while runFires is part way" service Passed
- every fired claim stays started with its session, the dispatcher's take of another claim stands, and the next runFires sends nothing service Passed
- a refresh made from claims read earlier keeps each claim's newest started, posted and fired service Passed
- a claim that hung, claimed again by a refresh at the same sha, is stored unstarted with no fired, and is listed to start service Passed
- two refreshes from the same state, the first saved and fired, then the second saved: every fired claim stays started with its session and the next runFires sends nothing service Passed
- a refresh that drops a claim while its take waits on GitHub: nothing is sent for it, and the next refresh's claim of the item is fired once service Passed
- "the second saves while the first waits", "the first saves while the second waits" service Passed
- two runFires both read a claim unstarted, ${order}: one fire for it, and the claim keeps one started and its session service Passed
- its claim on GitHub isn't posted twice service Passed
- 30 fires of one runner in the hour service Passed
- tokens: only those set, by runner service Passed
- no runner token set: runFires sends nothing and every claim is listed for the dispatcher at once service Passed
- 100 fires on the account in the hour service Passed
- runFires: a start refused for a limit on opus goes at once, the same claim with the same text, to fable service Passed
- any other refusal doesn't move the role service Passed
- nor does a token that isn't set service Passed
- never past the floor service Passed
- both at a limit: each model tried once, the claim given back to the dispatcher service Passed
- refused: no why, a role the service doesn't start, an unknown model, a model with no runner listed service Passed
- api.anthropic.com service Passed
- Customer suggestions you submit: the text you choose to send is filed in our private GitHub issue tracker for manual review. We do not attach your account identity. Common addresses and secrets are redacted automatically, but do not include confidential information. Suggestions remain on GitHub until deleted; contact privacy@pocketqa.dev with the request number to ask for removal.
Checked by 1 test before every release: passed on the live release
- Customer requests service Passed
- Our email provider sends sign-in links and alerts to the addresses you give.
Checked by 1 test before every release: passed on the live release
- api.resend.com service Passed
- The webhook your team sets for alerts (Slack, Discord, Microsoft Teams or another service) gets each alert: the site's name, whether it failed or passes again, and a link to the result.
Checked by 2 tests before every release: all passed on the live release
- alerts: a webhook gets the site's name service Passed
- alerts: a webhook into a private network is refused end to end Passed
- Your coding agent (Claude, for example) sees results when you connect it.
Checked by 10 tests before every release: all passed on the live release
- signed in to the dashboard, connecting is one page end to end Passed
- and pressing Connect without a sign-in is refused end to end Passed
- a revoked token stops working at once end to end Passed
- a person's tokens stop working the moment they're taken off the account or made a viewer end to end Passed
- who could test and can't now: taken off, or made a viewer service Passed
- tokens go with who lost testing; an older token (no seat) service Passed
- can't look at the lab's computers end to end Passed
- a script's token can't change sites, people or computers end to end Passed
- agents and scripts are capped at 30 tests an hour end to end Passed
- an address with a password in it is refused end to end Passed
- Anyone you give a report link to sees that report. After 30 days, only your team sees its details.
Checked by 3 tests before every release: all passed on the live release
- a report link older than 30 days shows the verdict only end to end Passed
- and its reports are gone end to end Passed
- After N days, only your team sees service Passed
Who at PocketQA can see it
PocketQA's operators see counts across the service, never your names, sites or results. They can open your account only while its owner has let support in (for seven days, and the owner can switch it off at once), and every look is recorded on the account for its people to see.
Checked by 11 tests before every release: all passed on the live release
- the owner lets support in for seven days end to end Passed
- turning it off shuts support out at once end to end Passed
- operators see reports by a code end to end Passed
- its line to the operators' alert webhook names the account by a code end to end Passed
- an agent can only ask to hold a rollout end to end Passed
- and the connector log names nobody end to end Passed
- the operator page: anyone else gets not found end to end Passed
- customers as counts: no account, person or site named end to end Passed
- its actions only from the page itself end to end Passed
- confirmed, the rollout is held and the action written down with who did it end to end Passed
- support access: the page's seven days service Passed
Where it's kept
PocketQA runs on Cloudflare. Today we don't choose where your account's data is stored: Cloudflare keeps it in one of its data centres, near where the account was first used, and doesn't move it. That may be outside Australia, including in the United States or Europe. Backups go to one Cloudflare storage bucket whose location Cloudflare chooses, and sign-in state is copied across Cloudflare's network. The other services above keep what they handle in their own places, some of them in the United States. If you need your data kept in a particular country, ask us at privacy@pocketqa.dev before you add sites.
Checked by 1 test before every release: passed on the live release
- where it's kept service Passed
How long
The waitlist: until you join or ask us to remove you. Results: 90 days on the service and 90 days on the lab computer, then they're deleted. Step screenshots: 30 days. A site's picture and its First look: the newest one, while the site exists. Backups: 30 days. Reports about PocketQA and the issues they're grouped into: in the service until it holds 300 of them, then the oldest go; an issue filed on GitHub stays there until it's deleted. Delete your account (People › Delete this account) and its sites, results and computers go at once; backups holding them age out within 30 days.
Checked by 16 tests before every release: all passed on the live release
- results are kept 90 days, as the computer keeps them service Passed
- a table's rows older than the cut go, newer ones stay service Passed
- a result older than 90 days is never kept by the service (issue 525) end to end Passed
- and one that turns 90 days old is deleted by the nightly sweep end to end Passed
- and its reports are gone end to end Passed
- and its badges (issue 525) end to end Passed
- backups: every object, encrypted, by day end to end Passed
- for operators only end to end Passed
- encrypted: no site address in the bucket service Passed
- production restores only on the day a person set ALLOW_RESTORE to service Passed
- a corrupt final encrypted piece is refused before any object is wiped service Passed
- an unfinished sequence is refused before any object is wiped service Passed
- a piece changed after validation is refused before it is written service Passed
- Results: N days on the service service Passed
- Step screenshots: N days service Passed
- issues kept in the service service Passed
Your choices
You can see and change what PocketQA holds about your team on the dashboard, switch step screenshots, a site's picture and each step's screen text on or off (Sites › the site › Settings › Privacy), remove a computer, and delete your account. To ask what we hold about you, to correct it, or to complain, email privacy@pocketqa.dev with the account concerned and what you want us to check or correct. We may need to verify your identity before providing account information. For a privacy complaint, explain what happened and the outcome you are seeking so we can investigate and respond. If you're not happy with our answer, you can contact the Office of the Australian Information Commissioner (oaic.gov.au).
Checked by 2 tests before every release: all passed on the live release
- your choices: Delete this account and Usage data are on People service Passed
- a site's privacy switches service Passed
Changes
When this page changes in a way that matters, we'll say so on the dashboard before it takes effect.
Last changed 2026-11-16.