Legal
Privacy policy
Who is responsible for what
There are two distinct roles, and the split matters because it decides who you ask for what.
- The subscribing Area Service Committee is the controller. It decides who is provisioned, what roles they hold, what gets published on its portal, what it collects in its own forms and how long it keeps it. Requests to see, correct or delete member data go to the Area’s own trusted servants first, because they are the ones who decide.
- Nelson Agentic LLC is the processor. We host the software and act on the Area’s instructions. We do not decide what an Area collects, we do not use tenant data for our own purposes, and we do not sell or share it.
We are the controller for a small, separate set of data: the account you use to sign in, our own billing records, and the server logs needed to keep the service running and secure.
What we store about a member
- A Google account identifier and email address, because sign-in is passwordless Google OAuth and there is no password to store.
- A display name, defaulting to your first name and last initial — derived automatically, and editable by you.
- Your Area role and any service seats you hold, which is what the permission system reads.
- Which groups you are a member of. This is the most sensitive thing in the system and is restricted accordingly.
- An append-only audit trail of consequential actions: seat rotations, group creation, grant decisions, domain verification. It records who did what and when.
There is nowhere to store a date of birth, a home address, a clean date, a sponsor, a criminal record, a full Employer Identification Number or a payment card number. Card details go to Stripe and never reach our servers.
What we deliberately do not do
- No tracking cookies, analytics pixels, tag managers, session recorders or advertising scripts. The content security policy blocks third-party connections outright.
- No selling, renting or sharing of personal data. There is no data-broker relationship to disclose because there is none.
- No AI training on your data, and no member data sent to any AI provider.
- No cross-tenant access. Every tenant-scoped table enforces row-level security in the database, not just in the application.
- No platform-staff browsing of group rosters. The staff flag grants no bypass over member data.
Cookies
Only the session cookies that keep you signed in, which is why you have not been shown a consent banner: there is nothing non-essential to consent to. Sign out and they are gone.
Sub-processors
- Supabase — database, authentication and storage.
- Google Cloud (Cloud Run) — application hosting.
- Cloudflare — DNS, TLS and edge caching for public pages.
- Stripe — payment processing for our own subscription fee, and Connect accounts that belong to the Area.
- Google — OAuth sign-in, and Workspace features where an Area has configured them.
- Slack — only where an Area has configured channels, and only for notifications that carry no roster data.
Retention and deletion
Tenant data is kept while the Area’s subscription is active and for a grace period after it ends, so a lapsed payment never costs a committee its directory. You can export your data at any time. On a verified deletion request from the Area, tenant data is deleted.
The audit trail is append-only by design and cannot be edited or selectively deleted — not by an Area admin, not by us. That is the point of it. It is removed with the rest of the Area’s data when the Area is deleted.
Security incidents
If we become aware of a breach affecting tenant data, we will notify the affected Areas’ administrators without undue delay and tell them what we know, including what we do not yet know. Report a suspected vulnerability or an anonymity incident to support@supportrecovery.org; incidents in progress are handled ahead of everything else, and reporting one is never charged for.
Your rights, and where to send them
Depending on where you live you may have rights to access, correct, delete or export your personal data, or to object to its processing. Send those requests to your Area’s trusted servants, who are the controller. If you do not know who that is, or your Area is unresponsive, write to support@supportrecovery.org and we will route it — and we will tell the Area we did.
See also the traditions and privacy notice and the terms of service.