Privacy

Subprocessors

When a business uses Counterseal, we process its data on its behalf. One company helps us do that: Cloudflare.

Last updated 9 October 2026

The list

SubprocessorWhat it does for CountersealDataWhere
Cloudflare, Inc. (San Francisco, United States)Runs the service: Cloudflare Workers (the code), D1 (the database: accounts, the encrypted vault, holds, the audit log), a Durable Object (the public log), static hosting for this site, and its network in front of all of itEverything the privacy policy lists. Vaulted API keys are encrypted before they are stored; Cloudflare's database never holds one readableRequests are handled at the Cloudflare location nearest to the person or agent making them; the database lives in one Cloudflare region

Cloudflare's Customer Data Processing Addendum is part of its subscription agreement. It names Cloudflare as a processor (or subprocessor) and covers transfers out of the EU, the UK and Switzerland with the EU Standard Contractual Clauses, the UK Addendum, and Cloudflare's EU-U.S. Data Privacy Framework certification (as that page said on 9 October 2026).

Workers Logs are off for this service, so Cloudflare does not keep our request logs or our log lines. Cloudflare may still process request metadata, such as IP addresses, to run and protect its network, under its own terms.

Who is not a subprocessor, and why

Changes

Before we add a subprocessor, we update this page first and give the date. Businesses with a data processing agreement with us get the notice that agreement sets (the template says 30 days), and can object. Questions: privacy@gautamkhosla.com.