What we hold
What we cannot hold
Weald Protocol, a Delaware limited liability company, operates Weald.
Workspace content is encrypted on member devices under keys we never receive.
Version 2, published August 10, 2026. These terms govern the hosted service from the day it opens for purchase.
What we do hold
We hold billing and instance data, connection metadata, storage totals, and access-set data needed to operate the relay.
If you join the waitlist, we hold that email address until you ask us to delete it.
Access sets do not identify workspace members.
Why we hold it
We use this data to operate, secure, bill, and support the service. We do not sell or advertise with it.
How long
| Data | Kept for |
|---|---|
| Request and application logs | 30 days |
| Error-tracking events | 30 days |
| Verified webhook payloads | 30 days |
| Hourly usage samples | 35 days |
| Daily usage and rating receipts | 15 months |
| Account audit events and signed checkpoints | 2 years |
| Support requests | 180 days after closure |
| Abuse/legal reports | 7 years |
Deletion follows this schedule unless a documented legal hold applies.
Who else sees it
Providers run hosting, storage, authentication, payments, email, and aggregate public-page measurement. None can read workspace content. Each one is named, with what it is given, on our subprocessor list.
Your rights
Request account-data access, correction, or deletion. We respond within 30 days.
Privacy requests go to hunter@getweald.com.
Report a vulnerability to hunter@getweald.com.
Cookies
The dashboard uses essential sign-in and request-protection cookies. Stripe has its own notice. The measurement described below sets no analytics or advertising cookie.
Two cookies are set on public pages, both first party and neither used for advertising or profiling. weald_ref holds the referral code of the creator link you arrived on, with the time you arrived, and lasts 90 days.
weald_join holds the invitation token from an ambassador link so the claim survives signing in, and lasts 30 days. It is cleared as soon as the claim is spent. Both are strictly necessary to carry out something you asked for by following that link, which is why neither waits on the banner and no third party reads either.
That measurement is Google Analytics, on marketing pages only, and it runs only after you accept it. Declining is remembered and no tag is loaded. Denying the cookie does not deny the request, so when it does run, Google receives an IP address and a user agent.
Change that answer here, whenever you like. The footer of every page links to this control. Turning it off also stops the tag on this page.
We also count our own purchase steps, first party, with a random id in your tab’s session storage that is never a cookie, never shared between tabs and gone when the tab closes. It travels only to our API, with the step, the page path without its query string, and the referring site’s host. No third party receives any of it.