GATEKEEPERQA
Free usage & privacy
Know what you can run and what happens to your data.
Last updated October 16, 2026. Free scanning is available with usage limits. Pro is available at $19.99/month or $191/year. We are not promising unlimited access or a permanent free tier.
What is free today?
Guests receive 2 single-page scans per browser per UTC day. Free accounts receive 5 page scans per UTC day, with up to 5 same-site pages per run. A three-page run uses three page scans. Saved accounts keep their latest 10 reports for up to 30 days. Opening, comparing and downloading saved reports do not use scan credits.
Can my team rely on unlimited daily availability?
The online scanner has shared limits of 50 page attempts per day, 500 per calendar month and 8 per network per day. Scans queue when capacity is busy and new scans stop when a shared allowance is exhausted. This service has no availability guarantee; it should not be your only release check. Failed or incomplete pages restore personal allowance, while shared safety limits still count attempts.
When do allowances reset?
Daily allowances reset at 00:00 UTC; the shared monthly allowance resets on the first day of each calendar month, UTC. Signing in from another browser does not reset an account allowance.
What will paid plans cost?
GatekeeperQA Pro is in final verification at $19.99 USD/month or $191 USD/year. Both billing options include 300 page scans refreshed monthly for one user, with up to 25 pages per batch and three website origins. Sign in to choose a Pro plan and continue to Stripe checkout. Shared team workspaces are not included. Read the Pro plans and full limits.
Can I sign in with a work email?
Yes, with an email verification code. Gmail, Outlook and other email providers are supported. Outlook delivery is still being investigated because some codes arrive in Junk; check that folder if your code is missing. Reports are private to the account; company-wide shared workspaces are not available yet.
Does a passing report certify compliance?
No. The scan checks an initially loaded page state. Human testing, assistive technology testing and judgment remain necessary. The founder's DHS Trusted Tester certification is an individual qualification, not DHS approval of this product.
When capacity is full
The interactive sample and before-and-after example remain available without credits. The local CLI does not consume web scanner allowances. Signing in gives an account allowance but does not bypass shared limits.
What the hosted scanner processes
We load the public URLs you submit and generate evidence that can include page URLs, element selectors, HTML snippets, findings and report files. Saved reviews can also contain the names and notes you enter. Do not submit private data, credentials or sensitive content. The scanner does not support logging into a target website.
| Data | Storage and retention |
|---|---|
| Guest reports | Available for 15 minutes after completion; removed during scheduled cleanup. Queue URLs are removed when the job completes or fails. |
| Saved reports and review notes | Latest 10 reports per account, up to 30 days. You can delete a saved report from your account. Downloaded copies remain wherever you save them. |
| Email and sign-in | Supabase verifies email codes and, when you choose Continue with Google, verifies your Google identity and maintains the authentication account. Google shares your basic identity, email address and profile information with Supabase. GatekeeperQA uses your verified email and Supabase account identifier for sign-in and report ownership; it does not request Gmail or Drive access, and does not store Google access or refresh tokens as application sessions. Scanner sign-in challenges last 10 minutes and application sessions last up to 7 days. Email is used for sign-in, not added to a marketing list. Contact Feedback for account deletion; report expiry does not delete your authentication account. |
| Essential cookies and abuse controls | A guest browser cookie lasts up to one day; a signed-in session lasts up to seven days. The service processes network addresses for rate limiting and stores daily keyed network hashes for shared allowances. These controls are separate from journey analytics. |
| Journey analytics | Daily aggregate counts for homepage views, scanner handoffs, accepted scan runs, complete/incomplete reports, verified sign-ins and new sign-ups. Kept for 30 days. No scanned URLs, emails, report content, referrers or visitor identifiers are stored in these counters. |
Account activity and administrator access
Account activity measurement is being introduced to help us understand service use and reliability. When enabled, we keep a pseudonymous account identifier, the date we first observed the verified account and whether it is an internal test account. This minimal account record is retained until account deletion.
We also keep the latest successful scan or saved-report activity time for up to 30 days, removed during scheduled cleanup. This includes opening, reviewing, exporting, renaming or deleting a saved report. These activity records contain no email addresses, scanned URLs or report contents. They are separate from the authentication and report records described above.
A separate MFA-protected administrator dashboard displays aggregate account counts, scanner health and capacity. Signed-in counts mean accounts with an unexpired session, not people currently online. Active counts reflect successful use, not continuous presence. Internal test accounts are separated where identified; account counts begin when tracking is enabled and do not represent all historical registrations.
Contact us using the privacy link below to request deletion of your account and its activity records. Recovery backups may retain deleted scanner data for up to 30 days.
Saved test sets
A test set stores a private name and page URL list with your account, plus its ID, edit version, page-list revision and creation/update times. Up to 10 sets with 1–20 URLs each remain until you delete them. Enter only URLs you are authorized to test, without credentials, query parameters or fragments. Saving a URL does not cause a request to that website.
When a scan or upload uses a set, its saved report metadata retains the set's name, ID, revision and URL list as they were at acceptance. Later edits do not rewrite earlier runs. Names and IDs are not added to public share snapshots, but scanned URLs remain part of report evidence. The report metadata follows the same latest-10/30-day retention as the report. Deleting a set does not delete those reports or revoke their existing share links; use report deletion or link revocation separately. Cloudflare processes and stores this data, and backups may retain deleted data for up to 30 days.
Uploading local CLI reports
CLI uploads are optional. When you explicitly confirm an upload, GatekeeperQA receives the report's page URLs, findings, captured HTML and text, guidance, and any source mappings. Inspect the JSON report for sensitive information first and upload only evidence you are authorized to store. The service does not visit those URLs or independently verify the uploaded findings.
Uploads are private saved reports, labeled as user-supplied CLI evidence. They use the same review, comparison and sharing controls. Original scan dates are preserved; the 30-day storage period starts when the report is saved. Your latest 10 saved reports include hosted scans and uploads. Adding a report can remove an older retained report and revoke its share link. Identical uploads are reused while retained without extending expiry.
The separate upload allowance is 10 reports per account and 100 across the service per UTC day, with up to 20 pages and 2 MB of JSON per report. Uploading does not consume hosted page-scan credits. Unknown metadata and pre-rendered downloads are discarded; HTML and Markdown are generated from structured evidence.
Create or revoke upload-only tokens from your signed-in scanner account. Up to three can be active, each expiring after 90 days. Only a token hash is stored, along with its name, creation/expiry and last-use time; the raw token is shown once. A token can add reports but cannot read them, share them or manage your account. Adding reports can trigger the retention limit. Keep tokens in an environment variable or CI secret store and revoke them if exposed. Daily upload budgets and expired token metadata are removed during scheduled cleanup. Cloudflare processes this data; recovery backups may retain deleted data for up to 30 days.
Sharing a saved report
Reports are private unless you create a share link. Signed-in users can create one read-only snapshot per saved report. Anyone with that link can view and save the scanned URLs, findings and captured HTML evidence without signing in. Check for private information before creating or sending a link.
Your account email and private report name are excluded. Saved manual-review notes, reviewer names and evidence are excluded by default; you can choose to include them. Later edits and retests do not update an existing snapshot.
Choose a one-day or seven-day expiry, or keep the link until the saved report expires. A link never extends the source report’s retention: it stops working if revoked, deleted, expired, or removed from your latest 10 reports. Revoke it from Share report. To share updated results, revoke the old link and create a new snapshot. Creating or viewing a link does not use scan credits.
Links are unguessable and shared pages request no indexing. This is not password protection: anyone receiving a forwarded link can open it. Revoking prevents future access through GatekeeperQA but cannot recall saved copies. Cloudflare hosts the snapshot; recovery backups may retain deleted data for up to 30 days.
Analytics choices and limitations
Our separate aggregate journey counters use no analytics cookies or local storage. It respects Do Not Track and Global Privacy Control. Server-side aggregate service counts do not identify people. Page views can include repeats; stages are not linked to a person, so counts are directional, not a tracked conversion funnel.
Cloudflare processes requests and hosts scanner data; Supabase manages authentication; our email provider delivers verification messages. Infrastructure providers necessarily process network information. Recovery backups may retain deleted scanner data for up to 30 days. This is not a promise of zero infrastructure logging.
Optional website analytics
With your permission, Google Analytics measures visits and selected actions (scanner opens, sample views, PDF clicks, developer-guide visits, video starts and contact clicks) on public marketing and guide pages on gatekeeperqa.com. It is not installed in the scanner or private reports. Google processes page paths, browser and device information, network information and cookie identifiers. We remove query strings and fragments from the page address we send and omit referrers. After you allow analytics, approved campaign labels can identify LinkedIn, Reddit, YouTube or DEV links and their named promotion. Other query values are discarded. Campaign labels are not stored separately in your browser. We do not send account emails, scanned URLs, report evidence or form entries. Automatic enhanced measurement and advertising personalization are disabled.
No Google Analytics tag loads before you allow analytics. No thanks keeps it off; Do Not Track and Global Privacy Control also keep it off. Use Analytics preferences in the footer to change your choice. Your choice is saved in this browser for six months; optional analytics cookies expire after six months. Withdrawing consent clears these cookies and stops future measurement, but does not remove previously collected data from Google. Google privacy policy.
Questions or deletion requests
Contact us about privacy or account deletion. Do not attach sensitive reports unless requested through an appropriate channel.