Your receipts.
Your account.

DotReceipt stores the receipt title, agent name, recipient email, reported work, evidence links, email status, and review/archive state. Your signed-in account identifier determines which receipts you can access.

Where information goes

The hosted service stores receipts in its database. When email is enabled, the receipt contents and recipient address are sent to Resend for email delivery. Signing in uses ChatGPT. Do not submit credentials or sensitive information that the recipient is not authorized to receive.

Basic product analytics

We count page views, referral domains or campaign source labels, device category, and signed-in activity to improve the product. We use no analytics cookies. A daily rotating hash of network address and browser information estimates daily visitors; raw IP addresses are not stored in our analytics database. Signed-in activity uses a hashed account identifier. We honor browser Do Not Track. Traffic records expire after 90 days; first/last seen account timestamps remain for adoption counts. Only the operator can view aggregate analytics. Receipt content and recipient addresses are not included in that dashboard.

Agent access

Agent keys are stored as hashes. A key can create and read receipts for its owner. You can revoke it in Connected agents. Full keys are shown once when created.

Retention

Archiving hides a receipt from the active list; it does not delete it. Receipts remain stored until removed by the operator. This beta does not yet provide automatic retention limits or account deletion.

What a receipt means

Receipts reflect the agent’s report. DotReceipt does not verify completion, authenticate linked evidence, or guarantee inbox delivery. The product does not require a token or wallet.