Privacy starts with collecting only the evidence the workflow needs.

Data used by the product

A crawl stores technical evidence from the configured public website scope, such as URLs, responses, delivered markup, links, metadata, structured data, headings, and referenced assets. A connected WordPress audit can add a read-only crawl-scoped snapshot for configured projects.

Credentials and exports

Connector credentials remain server-side and are not included in crawl databases, browser storage, logs, or exports. Exports contain the selected audit evidence and should still be handled according to the website owner's own privacy obligations.

Access requests and marketing measurement

The access form stores the information a person submits, the requested plan, the page and campaign parameters that led to the request, and the time of consent in an EU-restricted Cloudflare D1 database. Amplitera also records a small set of anonymous conversion events such as opening pricing, starting the form, or requesting access.

The public marketing measurement does not use advertising cookies, cross-site identifiers, IP-address storage, or behavioural profiles. Request data is used to prepare and communicate about self-service access. A person can ask hello@amplitera.com to access or delete their request data.

Questions and requests

For a privacy or data-handling question, contact hello@amplitera.com. Do not include passwords, access tokens, or unnecessary personal data in the message.