First 30 minutes

Goal: In about thirty minutes, understand Erasure well enough to evaluate it.

You will touch the real product loop, not slides.

Use Access & setup if any step below is unclear.

Before you start

• A browser
• A beta invite (or a self-hosted deploy). Cloud access is invite-only via erasurehq.in
• Optional: a staging Postgres (or any supported system) if you want a live deletion, not required to understand consent

Minutes 0–5: Land in the product

1. Open the app from your invite email (or your self-hosted origin).
2. Create an organization if prompted.
3. Create a project (name it after a real surface, e.g. Marketing Site).

You should see project home with clear next actions.

Checkpoint: You can navigate Consent, Develop, and Rights from the product UI.

Minutes 5–15: Consent that leaves a trail

Publish

1. Open Consent.
2. Add categories/purposes (include at least one required purpose).
3. Edit notice text so it sounds like your product, not lorem ipsum.
4. Click Publish.

You now have an immutable consent version. Drafts are not what the SDK serves.

Key + SDK

1. Open Develop → create publishable key → copy pk_live_….
2. Install and init (minimal):

npm install @erasurehq/accord

import { Accord } from "@erasurehq/accord";

const client = await Accord.init({
  publicKey: "pk_live_…",
  apiBaseUrl: "https://app.erasurehq.in", // origin only
});

3. Load a page that runs init, accept the notice.
4. Open Receipts and confirm a new row.

If you cannot wire the SDK in this session: still publish the notice and inspect versions in the console, then return for receipts.

Minutes 15–25: Systems and maps

Deletion without a map is guessing.

1. Open Rights → Systems.

2. Add PostgreSQL (or MySQL / HTTP / Webhook if that matches your stack).

3. Save and run health check.

4. Open Data Map:

   • Discover schema
   • Accept or edit entity mappings
   • Set identifiers (for example email → column)
   • Mark personal-data tables DELETE; mark keepers SKIP

5. Glance at operational readiness on Home or Rights. Resolve anything marked blocked (no systems, empty map, unhealthy connector).

Checkpoint: At least one enabled system with a coherent map (for SQL: ≥1 DELETE entity with identifiers).

Minutes 25–30: Case + evidence

1. Open Operations (Rights cases).
2. Create a test case for a subject you control (operator create), or use public intake if enabled for your org.
3. Ensure verification is VERIFIED.
4. Start when readiness allows.
5. Watch the timeline until COMPLETED or FAILED.
6. Open Evidence → export JSON or report.

Checkpoint: You have seen a case lifecycle and an exportable package, not only a status badge.

What "good" looks like after 30 minutes

What you did not finish (and that is fine)

• Production TLS and network rules for every connector
• Full HTTP/Webhook playbooks
• Legal review of notice copy
• Team RBAC rollout
• Billing upgrade

Those are later guides and ops work, not required to understand the product.

Recommended next reading

1. Getting Started overview, full narrative
2. Access & setup, keys and tenancy
3. DPDP, obligation-oriented framing (expanding)
4. Core Concepts, vocabulary (expanding)
5. Marketing Security, diligence summary