Security and data handling

Evidence stays useful without exposing credentials.

Amplitera is designed to keep crawl evidence inspectable while separating it from credentials, connector secrets, and mutable job-control state.

Request early access →Explore workspace ↗
Complete evidence✦Explicit boundaries✦Verifiable outcomes
01

Operational boundaries

  • WordPress credentials remain server-side
  • Credentials are not written to crawl databases, browser storage, logs, or exports
  • Connected WordPress snapshots are read-only and crawl-scoped
  • Crawl databases remain immutable while job state lives separately
  • MCP access is OAuth-secured and permission-scoped
02

Responsible disclosure

Do not send credentials or private client datasets by email. Report a suspected security issue to hello@amplitera.com with a minimal, non-sensitive reproduction and a way to contact you.

03

Scope of this page

This page describes shipped product boundaries. It is not a certification statement and does not claim compliance programs that have not been independently verified.

Continue exploring
Amplitera

Privacy starts with collecting only the evidence the workflow needs.

A plain-language overview of how Amplitera treats public crawl evidence, connected WordPress snapshots, credentials, exports, and support requests.

Open →Product

Connect the public defect to the WordPress record behind it.

Join public crawl evidence to a read-only WordPress snapshot for clearer diagnosis of templates, translations, metadata, posts, and referenced media.

Open →Product

Give agents the crawl context, not a pasted export.

Use scoped MCP access to query Amplitera crawls, issues, pages, comparisons, monitoring, and approved workflows from compatible agents.

Open →
Private beta

Turn the next crawl into a repair system.

Bring a recurring technical SEO workflow. We will show how Amplitera keeps the evidence, handoff, and verification connected.

Request early access →