Erasure

Products

Accord and Rights

Erasure provides two products:: Accord proves consent; Rights runs deletion through real systems.

Product 01

Consent

Accord

Collect choices. Keep proof. React in the backend.

For product and engineering teams who need a real notice + receipt path—not a one-off banner script they cannot defend six months later.

  • Notices & purposes

    Say what you collect and why—structured purposes and categories, not a wall of policy text nobody audits later.

  • Immutable publish

    Draft never goes live by accident. Each publish is a version. Receipts lock to the snapshot the person actually saw.

  • Browser SDK

    Drop in @erasurehq/accord for banner, preferences, and optional withdraw. Publishable keys only—no operator secrets in the client.

  • Receipts you can export

    Append-only proof of choices. Search them in the console; export JSON/CSV when someone asks what happened.

  • Backend webhooks

    consent.updated with HMAC so your own systems can stop processing when consent changes—not just a UI toggle.

Product 02

Deletion

Rights

Verify the request. Run the job. Show the trail.

For teams that get “delete my data” emails and cannot answer with a single SQL file—or a ticket that never closes. Today: DELETE first.

  • Cases & operations queues

    Deletion as work items: needs attention, running, failed. Operators verify, start, and override with a full activity trail.

  • Verified intake

    OTP-gated public API so you do not open cases for emails nobody controls. Spam and abandoned requests stay out.

  • Systems + Data Maps

    Connect Postgres, MySQL, HTTP, or webhooks, then map tables and identifiers so jobs know what to delete vs skip.

  • Durable jobs

    A worker runs rights.delete with retries and honest outcomes—completed, failed, or partial—not one-off production SQL.

  • Operational readiness

    Know if systems, maps, and the worker are ready before the first real deletion—not a vanity “compliance score.”

One platform shell. Auth, organizations, projects, and billing are shared. You do not buy two products and stitch accounts together.

Under the hood of Rights

Systems, maps, and evidence

These are not separate companies. They are the capabilities that make deletion operational—and Evidence also covers Accord publishes.

  • Systems

    PII is never in one database.

    Connect the places data actually lives. Health checks, encrypted credentials, and enable/disable when you need control of outbound work.

    PostgreSQL · MySQL · HTTP API · Webhook

  • Data Maps

    You cannot delete what you cannot find.

    Inventory tables and identifiers before panic. Schema discovery, multi-table maps, dry-run counts, and readiness signals.

    Entities · identifiers · DELETE or SKIP

  • Evidence

    Logs are not a review package.

    Export structured packages for consent publish and deletion outcomes—assembled from real events, not a staged PDF. Operational proof, not a legal seal.

    JSON · CSV · report · on-read

Together

The loop that banners alone cannot close

Start with Accord for proof of consent, or Rights when deletion is the fire drill. The platform is designed so both ends meet without a second vendor.

You do not need every step on day one. Ship the pieces that hurt first.

  1. 01

    Consent

    Accord publishes the notice and collects choices on your product.

  2. 02

    Receipt

    Every decision is stored against the version people actually saw.

  3. 03

    Data Map

    Rights knows which tables and systems hold that subject’s data.

  4. 04

    Deletion job

    A verified case fans out work through Systems you connected.

  5. 05

    Evidence

    Export what ran—and what failed—when you need a record.

Invite-only beta

Run the loop in your own org

No public signup. Request an invite when you are ready to try Accord, Rights, or both—with Guided Setup if you want help deploying.

Read the docsPricing