Privacy for a record that can be checked.

What we collect

When you configure an event, we process the operation and parameters you choose. Optional intention or context is hashed in your browser for order binding; the original text is not used to influence the physical event or outcome.

When a purchase is completed, we retain the identifiers and records needed to operate and preserve the transaction: order, transaction, payment reference, allocation, result, receipt, verification, and delivery status. We also process ordinary technical and security logs needed to protect the service and investigate failures or misuse.

When you use the contact form or versioned JSON agent inquiry, we process your name or self-declared agent identity, reply email when supplied, inquiry category, optional organization, and message only to route and respond to the inquiry. Message content is sent through our email provider and is not stored in the site database. The provider and destination mailbox may retain it under their configured policies. The legacy JSON-RPC collaboration format separately retains text for up to 30 days in an owner-only review queue; it does not imply email delivery. Both email interfaces use one server-controlled destination and a shared aggregate rate limit, with no automatic replies to caller-supplied addresses.

Payments and delivery

Payments use Stripe-hosted Checkout. Stripe processes card details and, where eligible, Apple Pay or Google Pay. Authentic Random does not collect or store raw card numbers, security codes, or wallet credentials. Stablecoins are not offered through human checkout at this time.

If a receipt email is requested through Checkout, we use Resend to deliver the receipt-derived artifact. We retain a hashed recipient reference and delivery state for recovery; the result, receipt, and allocation do not change if delivery is retried. The contact form also uses Resend, without storing contact message content in the site database.

Public and private receipt data

Public verification is designed to expose only the information required to assess a receipt: receipt ID, provider, source, transaction binding, Pool allocation, measurement commitment, health and warnings, protocol version, result, signature status, and verification status. We do not automatically publish requester identity, payment details, raw optional context, or private evidence packages.

Private evidence and delivery material are handled separately from the public receipt view. A public receipt is preserved so a completed result can be checked; it is not a promise of perfect randomness, prediction, luck, or IBM endorsement.

Why we use information

We use information to configure and fulfill an event after verified payment, prevent duplicate or altered orders, preserve the no-reroll record, provide receipt and verification access, deliver requested artifacts, respond to inquiries, secure the service, provide support, and comply with applicable obligations.

Retention and security

Receipt metadata and verification records are retained to preserve issuance and public verification. Order, allocation, and fulfillment records are retained as necessary for the service, support, security, accounting, and legal obligations. Private evidence packages may have a separate retention period and are not made public by default.

We use access controls, signed receipts, hashed bindings, hosted payment processing, and operational safeguards intended to reduce unauthorized access and alteration. No system can promise absolute security.

Your choices and questions

You may request access to or correction of personal information that we can reasonably identify. You may also request deletion where applicable. Requests may be limited when a record must remain preserved for transaction integrity, security, legal obligations, or a public receipt’s verification function.

For privacy questions or requests, contact results@authenticrandom.com. We may update this notice as the service changes; the effective date above identifies the current version.

Related terms

Use of the service is also governed by the Terms of Service.