1. What we collect
At signup: your email address, a password hash, the company name you type and the country your payment instrument reports. On the billing side, a payment processor holds the card and we hold a customer id, the plan, invoices and the tax country. We never see or store a card number, and we do not keep copies of identity documents.
When you verify a target, we store the hostname, the token, the resolver answers, the timestamp of each check and the account that requested it. When you run a test, we store the configuration (method, rate, window, ramp), the maintenance note, the per-second telemetry, the report and the source addresses of our generators for that run. Support conversations are stored as tickets.
We also keep ordinary technical logs: request paths, response codes, IP addresses and user agents on the dashboard and the API, retained for thirty days for security and debugging. If you use single sign-on, we receive the identifier your identity provider asserts and do not receive your password.
2. Why we hold it
Verification records exist to answer one question after the fact: was this run authorised at the moment it started? That is a legal-defence record as much as a product feature, so it is kept even after a run is deleted, in a form that contains no payload data. Run telemetry exists so that the report you paid for can be regenerated if you lose the file.
Billing records exist because tax law requires them. Account and support records exist because we cannot run a service without knowing who to invoice and what they asked for. Security logs exist to detect credential stuffing, scraping and attempts to abuse the verifier. None of these are used to build advertising profiles; we do not run ad networks on this site and we do not sell data.
The lawful bases are contract performance for the account, billing and run data; legal obligation for tax records; and legitimate interest for security logging and fraud prevention. Where we rely on consent (a product update email, for example), you can withdraw it without losing access to the service.
3. What we do not collect
We do not install advertising cookies, we do not embed third-party trackers in the marketing pages, and we do not use session recording on the dashboard. The site sets no cookie that is not required to keep you signed in. Analytics are aggregate page counts with no cross-site identifier, which is why there is no consent banner on this page.
We do not collect the content of the traffic you send. A run generates requests at a target you control; the payload is synthetic and we keep only counters and timings. If you choose to put real customer data into a test payload, that is your processing decision, and our advice is not to do it.
We do not buy contact lists, and we do not enrich your account with data from brokers. The email you gave us is the email we use, and the only third party that sees it is the transactional mail provider that delivers the receipt.
4. How long we keep it
Reports and per-second telemetry are deleted ninety days after the run, or earlier if you delete them from the dashboard. Verification records are kept for twelve months after the last run against that hostname, then reduced to a hash that proves a check happened without keeping the hostname. Security logs are kept thirty days.
Invoices and tax records are kept for the period the relevant law requires, which is usually seven to ten years. Support tickets are kept for two years, because a question asked twice is cheaper to answer the second time. Account records are deleted thirty days after account closure, except where a legal hold or an open abuse investigation requires otherwise.
Backups are encrypted and rotate on a thirty-five day cycle, so a deletion request can take up to that long to reach every copy. You will get a written confirmation when it has.
5. Who processes it
We use a payment processor, a transactional email provider, a cloud host for the dashboard and a separate network provider for the generators. Each is bound by a data processing agreement, each receives the minimum needed for its job, and none is permitted to use your data for its own marketing. The current list is available on request and is updated when a provider changes.
Data is stored in the European Union and the United States. Where a transfer leaves the EU, it relies on the standard contractual clauses or an adequacy decision. We do not transfer data to a jurisdiction that has no lawful transfer mechanism, and we do not route a customer's data through a country because it is cheaper.
We disclose data to authorities only where legally compelled, and we notify you unless a court order forbids it. We publish a transparency count once a year: how many requests we received, how many we challenged and how many we complied with.
6. Your rights
You can request a copy of your data, correct it, delete it, restrict processing, object to processing based on legitimate interest, or receive it in a portable format. Write to [email protected] from the account address and we will respond within thirty days, usually within three working days. There is no fee and no form to fill in.
Deleting run data does not delete the verification record, because that record is what proves the run was authorised; it is reduced to a hash after twelve months. If you need the verification record removed earlier, say so and explain why, and we will balance the request against the legal-defence interest. We will tell you which way we decided.
If you believe we handled a request badly, you can complain to your local data protection authority. We would rather you wrote to us first; most complaints are a retention rule applied to the wrong record, and those are fixable in a day.
7. Changes
We update this page when a processor changes, when a retention period changes or when a new feature collects something new. The effective date at the top is the date of the last change, and material changes are emailed to account holders before they take effect.
This policy does not cover the targets you test. Their logs, their retention and their lawful basis are theirs, and a run will appear in their access logs as traffic from our generators. If that matters for a client engagement, tell them the window in advance; the maintenance note field exists for exactly this conversation.
Questions about a specific record go to [email protected]. Include the account email and the run id if you have it; the run id resolves to everything else.