Subprocessors and Service Providers
This page lists every company and system outside ProofLedger LLC that handles data from the ProofLedger service, what each one receives, and where it runs. It is referenced by the Privacy Policy and the API Terms. We update this page before adding a provider that will receive customer or partner data; the date above changes when we do. Partners who want to be told by email when it changes can ask at support@proofledger.io.
What data exists to be shared
ProofLedger never receives files. The data in our systems is: account email addresses; for each proof, the SHA-256 hash, the filename and record identifier the submitter chose, timestamps, and blockchain transaction details; API key metadata (a hash of the key, not the key); webhook addresses, their secrets and delivery logs; billing records; and ordinary server logs with request times, paths and IP addresses. Every provider below receives a subset of this, as stated.
Service providers that receive data
| Provider | Purpose | What it receives | Location |
|---|---|---|---|
| DigitalOcean, LLC | Hosting of the application server and database | All data listed above, at rest and in transit on the server | New York, United States (NYC3 region) |
| Resend, Inc. | Transactional email: sign-in codes, account notices, webhook and API notices | Recipient email address and the content of each message | United States |
| Stripe, Inc. | Billing and payment processing for paid plans | Name, email, payment details and billing history. ProofLedger does not see full card numbers. | United States |
| Alchemy Insights, Inc.; PublicNode (Allnodes) | Polygon network access (RPC) used by the signing service to broadcast anchoring transactions; PublicNode is the fallback | The anchoring transaction, which contains the hash. The hash is public on the chain either way; no account or filename data is sent. | United States (Alchemy); global (PublicNode) |
| Fulcrum Enterprises LLC (affiliate under common ownership) | Operates the Polygon signing service (the machine that holds the signing key, kept off the public server) and holds encrypted off-site backups of the database; hosts the cookieless website analytics | Hashes to be anchored; encrypted backup copies of the database and configuration; website visit statistics without cookies or personal identifiers | Florida, United States |
Public blockchain network
The Polygon network is not a service provider; it is a public, decentralized ledger operated by thousands of independent parties worldwide. Every proof's SHA-256 hash is written to Polygon in a transaction. These records are permanent, worldwide, and cannot be altered or deleted by ProofLedger or anyone else. No filename, account or personal data is written to the chain. Bitcoin anchoring was discontinued on October 15, 2026; proofs anchored on Bitcoin before then keep that record on their certificate.
Website visitors only
Pages on proofledger.io load fonts from Google Fonts (Google LLC, United States), which receives the visitor's IP address and browser details in the ordinary course of serving the font files. This does not apply to API traffic. Website analytics are self-hosted (Umami on the affiliate infrastructure above) and set no cookies.
Not used
ProofLedger does not use advertising networks, third-party tracking, customer-data platforms, or AI services that receive customer or partner data. Support email is handled in an ordinary mailbox operated by ProofLedger LLC on Google Workspace (Google LLC, United States), which receives the content of messages you send to support@proofledger.io.
Change history
- 2026-10-15: page published, listing the providers above.
Contact
ProofLedger LLC
PO Box 24
Floral City, FL 34436
support@proofledger.io