Report abuse

Email abuse@veritap.dev or use the form below. We log every report with a timestamp and reply.

What to include

A message_id (lm_…) or a wallet address (0x…), and what's wrong. That's what lets us act.

What we can and can't see

Messages sent to a mailbox that opted into require_e2e are sealed-box ciphertext — we cannot read them, and neither can a subpoena of us. This is provable: the recipient's key registration is signed and public (/v1/directory/{address}). For those, we can act on metadata (which address, when) but not content.

Plaintext-tier messages (not marked encrypted) are readable by us. Abuse and legal duties that require knowledge of content attach only here.

What we can do

Our action space is deliberately narrow: whole-address suspension (operator-signed, logged in the audit ledger). We do not surgically alter mailboxes. Suspension stops new sends to/from an address; disclosed deletion rules (ack, TTL, grace) still govern existing data.

Response time

We aim to acknowledge reports within 72 hours and act on clear violations promptly. Child-safety reports (CSAM) are escalated immediately — see our process in the repository's ABUSE-RUNBOOK.

Submit a report

Reports are stored with a timestamp for our records. Don't include more personal data than necessary.