Objection is
not a form.
A route to an operator, not a request collector.
Contact status
The status below reflects the configured operator contact. If it is inactive, no request has been submitted and there is no hidden form handler. Do not send sensitive documents or copy the full source post.
Single post or whole account
For a single-post request, provide its public source link or the current signal/snapshot reference if available. A credible request should first hide the affected field while it is assessed; heavyweight identity documents are not a prerequisite to simple removal. Account-wide suppression can be requested using the public account link. The operator should clarify ambiguous scope with minimal verification, not collect a biography.
What the operator can do
The operator-only command canonicalises a post or account, stores a persistent versioned HMAC fingerprint in PostgreSQL and invalidates the active snapshot atomically with publication. Future construction and voice opening check suppression again. PostgreSQL never receives the source text or the plaintext identifier used to create the fingerprint. There is no public identifier lookup or unauthenticated suppression endpoint.
Removal requires the migrations role and the separately held HMAC key. Runtime credentials cannot call the removal function or read tables directly. A monitored channel, operator review and response procedure remain prerequisites for real-source publication; an email address alone is not sufficient.
Limits of removal
HEARD cannot delete the original on Bluesky, Mastodon, Hacker News or YouTube or erase a provider’s visitor logs. An original can change, be deleted, or become unavailable; the next verification excludes it, and an open attempt rechecks availability and invalidates the current field on failure. Expired snapshots are never returned, even when cleanup is delayed.