Create account
Menu

PRIVACY BY DESIGN

Collect what protects the request. Keep no more than needed.

Privacy is an architectural constraint across signals, tokens, analytics, logging, exports, and retention—not a marketing add-on.

Create your workspace Read documentation
03 core areas 01Minimized security evidence02Short-lived state03Retention with boundaries

Trust architecture

Minimized security evidence

Analytics and logs avoid raw secrets, presented tokens, challenge answers, and unnecessary client detail.

  • Redacted structured logs
  • Minimized reason codes
  • No advertising profiles

Trust architecture

Short-lived state

Challenge, replay, rate-limit, and session state uses explicit lifetimes appropriate to its security purpose.

  • Expiring challenges
  • One-time tokens
  • Temporary risk state

Trust architecture

Retention with boundaries

Teams control analytics retention, expired projections are pruned, and private exports expire automatically.

  • Tenant-scoped retention
  • Hourly cleanup
  • Private storage

CONTINUE EXPLORING

Follow the most relevant path without losing the context of this page.

01

Security

Inspect the verification boundaries.

 02

Bot protection

Layer controls against abuse.

START WITH A REAL SITE

Build a safer user journey.

Register a hostname and choose the amount of verification friction each action deserves.

Create account