Service policies · Updated 9 November 2026
Privacy policy
Data used to operate certificate issuance, validation and account management.
Service records
The ACME service stores operational records in Cloudflare D1. Depending on your requests, these include:
- Account identifiers, public keys and key fingerprints, optional contact information, account status, creation time and the URL of agreed terms when consent is enabled.
- Requested domain names, orders, authorization and challenge tokens, validation status, errors and timestamps, plus counters used to enforce rate limits.
- Issued certificate contents, serial numbers, domain names, validity periods, issuing CA references, account associations, renewal relationships and revocation status or reasons.
Your account and certificate private keys remain with your client; normal ACME requests supply public keys, signatures and certificate signing requests. The service separately uses its configured CA signing keys to issue certificates.
Why these records are used
Records support request authentication, replay prevention, proof of domain control, issuance, renewal information, revocation, abuse limits and account or terms management. Certificate and revocation information is intended to be shared with parties that need to validate certificates; do not treat domain names included in a certificate as confidential.
Infrastructure and validation services
Cloudflare Workers processes requests and serves these pages, Workers Assets stores the web resources, and D1 stores ACME records. Cloudflare also processes network and request information as the infrastructure provider. See Cloudflare's privacy policy for its own practices.
Domain validation makes DNS-over-HTTPS queries, including through Cloudflare and Google resolvers. IP validation connects directly to the public IP over TCP, without an initial DNS lookup. HTTP-01 requests expose the challenge token and key authorization exchange to the target; redirects may contact additional public IPs or domains. HTTPS targets use certificate-verified TLS. These queries disclose the queried names to the resolver. HTTP-01 validation contacts the domain's web server and may follow permitted redirects, disclosing challenge paths to the contacted servers. CAA lookups are also used to check certificate issuance permissions.
Logs and website features
The checked-in configuration disables observability overall while retaining settings for persisted Cloudflare invocation logs and traces. Collection depends on the active deployment settings. Application error logging uses limited diagnostic fields, such as an error reference, path and error type, rather than intentionally logging private keys or complete ACME request bodies. If infrastructure logging is enabled, its logs may contain additional request metadata.
These pages contain no browser scripts, analytics integrations or application-set cookies. Following links to GitHub, Cloudflare or another site makes a request to that site, whose own policies apply.
Account changes and stored data
You can update contact information and deactivate an account through ACME. Deactivation does not delete the account, related orders or certificate records. The current implementation does not provide a general account-data deletion endpoint or a fixed automatic retention schedule for these records.
Service data is not automatically removed merely because a certificate or order expires. This policy does not promise a fixed retention period or deletion deadline. For project information, use the source repository; do not include sensitive account data in public discussions.