Legal · Last updated 1 September 2026
Sub-processors
The complete list, published rather than available on request. There are two.
| Sub-processor | Purpose | Location |
|---|---|---|
| DigitalOcean Everything the product holds, at rest and in memory. | Compute and the database. | San Francisco, United States. |
| DigitalOcean Spaces A full database dump. | Encrypted nightly database backups, pruned after 30 days. | San Francisco, United States. |
Who is not on this list, and why
Google and Meta
Campaign spend is read from the Google Ads and Meta APIs. Data moves in one direction only: totals come in, nothing goes out. Neither platform receives visitor data, event data, or anything else, so neither is processing personal data on our behalf and neither is a sub-processor.
They are, of course, processing your advertising data under whatever agreement you already have with them. That relationship is yours and predates this one.
Analytics on this website
This marketing site measures itself with its own Pear Metrics instance: cookieless, first-party, no personal data stored, exactly as described on the privacy page. It runs on the same infrastructure listed above, so it adds no entry to this list. There is no tag manager, no chat widget and no advertising pixel.
Why the list is this short
Customers share one deployment and one database, which we run. What keeps this list to two entries is not the shape of the hosting, it is what never gets collected: no analytics vendor, no tag manager, no CDN in front of the tracker, no advertising pixel, and no third party that visitor data is passed to. Every name that would normally appear on a page like this is missing because there is nothing to send it.
Changes
Customers are notified at least 30 days before a sub-processor is added, with the opportunity to object as set out in the data processing agreement. This page is the authoritative version and is dated at the top.
Questions: privacy@pearmetrics.com