Who else
Who else is involved
Weald Protocol uses the providers below to run Weald. None of them can read workspace content, because it is encrypted on member devices under keys we never receive, so what reaches a provider is ciphertext, metadata, or billing data.
Version 2, published August 10, 2026. These terms govern the hosted service from the day it opens for purchase.
The list
| Processor | What it is given | Where |
|---|---|---|
| Render | Containers, both databases, request logs. No workspace content. | United States |
| Cloudflare R2 | Blob and backup objects, as ciphertext with no key. | Region chosen at creation |
| Stripe | Billing email, payment method, plan, amount. | United States |
| Clerk | Dashboard sign-in identity, organization membership, auth events. | United States |
| GitHub (GHCR) | Published relay images, pinned by digest. | United States |
| Resend | Billing and lifecycle email addresses, and the message sent. | United States |
| Google (Analytics) | Public marketing pages only: an IP address and a user agent. It gets no cookie, identifier, dashboard or creator URL. | United States |
Changes
We give 30 days notice of a new processor, as the terms say. A provider that would be handed readable workspace content is not on this list and could not be added to it. Adding one would change the product itself.
Questions go to hunter@getweald.com.