Skip to content
Back to skills

Purge

ASecurity

Deleting one user's or visitor's product events (account deletion, a data-subject request) with observe.RequestPurge — a purge request sent as a product event through the app's own telemetry pipeline, which the Reliant control plane verifies, executes against the environment's product_events and records once per request id.

  • 10 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added November 13, 2026
ai-agentsgo

Works with

  • cli

Security analysis

A100/100

Scanned November 13, 2026

npx -y skills add reliant-labs/forge --skill purge --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Purge?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Purge
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/reliant-labs-purge/badge)](https://www.skillsdirectory.com/skills/reliant-labs-purge)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: observability/product-events/purge
description: Deleting one user's or visitor's product events (account deletion, a data-subject request) with observe.RequestPurge — a purge request sent as a product event through the app's own telemetry pipeline, which the Reliant control plane verifies, executes against the environment's product_events and records once per request id.
---

# Deleting a user's events: `observe.RequestPurge`

```go
id, err := observe.RequestPurge(ctx, "account-"+accountID, observe.PurgeSubject{UserID: userID})
```

The app asks; the platform that stores the events deletes them. There is no
new endpoint or credential: the request is one product event,
`forge_purge_requested`, written through the context's logger like every
`observe.Track` event, with the subject in its props (`purge.user_id`,
`purge.visitor_id`) and a request id (`purge.request_id`).

- **Who.** `UserID` is the id your events carry as `user.id`; `VisitorID` the
  one they carry as `visitor.id` (a browser at the `full` tier, a CLI's install
  id). Set either or both: a row matching either is deleted.
- **Idempotent.** The platform records each request once by (org, environment,
  request id). Pass an id derived from the deletion (the account id) and a
  retried call is the same request; pass `""` and RequestPurge mints a random
  one and returns it.
- **Never refused by consent or the PII guard**, unlike `Track`: a purge is
  how withdrawn consent is honoured, and the ids are the point. It fails only
  on a request that cannot be honoured: no subject, an id over 256 characters
  (the pipeline would truncate it and miss the rows) or a malformed request id
  (`observe.ErrInvalidPurge`).
- **No actor.** The record carries no `user.id`, `org.id` or `visitor.id`, so
  it is nobody's activity.

## What the Reliant control plane does with it

- **Authenticated as your environment.** It acts only on a request that
  arrived through the environment's own server-side ingest (a workload's OTLP
  token or the cluster's log agent). A request sent with a publishable browser
  or CLI key is recorded as rejected and never executed, so a page cannot
  purge another user's data.
- **Scoped by the gateway.** The org and environment are the ones the ingest
  gateway stamped, not anything in the record, and the delete runs in that
  org's own `product_events` table, restricted to that environment. A request
  cannot reach another org's or another environment's rows.
- **Recorded.** One audit row per request: the environment, the request id,
  SHA-256 hashes of the subject ids (never the ids), the outcome and the rows
  deleted. The request's own row is deleted after it runs, so the ids do not
  outlive the purge.
- **What it covers.** The long-retention `product_events` table, as stored
  when the purge runs (within minutes). Raw logs and traces keep their own
  short retention. Stop emitting events for the subject first: an event
  stored after the purge ran is not purged.

A local `forge env up` has no purge executor: the request is an ordinary log
line there.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.