Everything you agreed to,in one place.

We update this page when the list changes. The date at the top shows when it was last updated.

Railway. Runs the application service and background workers. Everything the service processes passes through Railway infrastructure: digests, record metadata, request logs, and audit trails.

Neon. The primary data store. Holds service records — digests, file metadata, timestamps — plus account email addresses and credit balances. Credentials are hashed before they reach it.

Stripe. Processes every card payment. Card details go to Stripe directly and never reach us; we see the payment outcome and invoice records. Billing contact information may be shared with Stripe to fulfill and reconcile purchases.

hCaptcha. Previously used for checkout abuse checks. hCaptcha processed the browser, network, and challenge signals needed to score a challenge; any retained provider data remains subject to its own terms.

Cloudflare. Serves this website and the console, and runs the Turnstile check on sign-up. As the host of the pages you are reading, it sees the browser and network facts any web host sees.

Alchemy. The primary route for broadcasting anchoring transactions to Base. It receives the signed transaction — which carries the digest and nothing else about your file — on its way to the public chain.

QuickNode. Provides a secondary connection to Base for blockchain queries and transaction submission. Anchoring transactions sent to QuickNode contain the file digest, with no file contents or file metadata.

Resend. Sends service email: sign-up verification, receipts and notices. It receives the recipient address and the message contents, which for a receipt include the record reference.

Slack. When operator notifications are enabled, receives private service alerts and limited account activity: account identifiers, masked email, signup and verification facts, product and payment amounts, currency, fulfillment state, and payment, refund or record references. Files, filenames, digests, authentication tokens and receipt links are excluded. Message storage follows the workspace residency configuration; some service data may be processed elsewhere.

Sentry. Receives service error reports and sanitized browser crash diagnostics. Browser reports contain build/environment, broad page category, code locations and validated request correlation IDs, without raw error messages, authentication URLs, file metadata, digests, request bodies or session replay. The provider receives network connection information such as IP address. It never receives file contents from our error reporting.

Additional Disclosures. Base's public endpoint, operated by Coinbase, may also receive the same signed transaction and its digest-only payload. Once included on Base, the transaction and digest are public and readable by anyone.

Google / YouTube. Where videos are offered, the poster and transcript are hosted locally. Loading a player connects your browser directly to YouTube in privacy-enhanced mode. Google processes browser, network (including IP address), origin referrer, and playback information under its own policies; this is separate from notarization processing. We do not send your files, filenames, customer digests, or receipt tokens to the video player.

This browser interaction is disclosed separately from the service infrastructure above. We make no provider-specific retention, location, or contractual promise for optional playback. See Google's Privacy Policy.