Keep the recovery reference.

Use the branded support address for payment review, refunds, project corrections, privacy requests, and responsible security reports.

Resend receives and stores inbound support mail. A limited plain-text copy may be forwarded to a private operator mailbox; attachments and HTML are not included in that automated forward. See Privacy for details.

• The shielded.bid recovery reference, if one was shown.
• The project URL or handle used for the placement.
• The approximate date and time of the attempted payment.
• A plain description of what the site displayed.

Never send a seed phrase, spending key, wallet backup, API key, dashboard token, webhook secret, full payment URI, or private service credential. shielded.bid support does not need them.

If the payment screen says manual review is required, do not send another payment for the same quote. Support will compare the private shielded.bid ledger with CipherPay's canonical invoice before applying credit or confirming an on-chain refund.

Read the refund process before requesting resolution.

For a vulnerability, use the same address with the subject “shielded.bid security report.” Do not test with real customer funds, access data that is not yours, publish credentials, or degrade availability. The machine-readable contact is available at security.txt.