Privacy

A future deployment would make name ownership and owner-approved card fields public. A delivery record should bind evidence, an acceptance rule, a verifier and a Pass, Fail or Unproven conclusion. Public chain data may be impossible to delete. No TapeID name or card has been published by this project.

• The repository supports an in-memory index and a PostgreSQL schema for local tests.
• Tests may use synthetic wallets, names, payments and records; they are not user history.
• Local request logs and rate-limit counters are development data, not a production service.
• No production database, sponsorship ledger or invitation history is configured.

Never submit a seed phrase or private key to a chat interface. A future card flow should publish only fields explicitly marked public. Source-project incidents and historical card records are not TapeID privacy history and are not republished here.

No support mailbox has been configured; support@example.invalid is an invalid placeholder, not a contact channel. A real privacy policy, retention period and contact must be published before the service accepts public data.