Legal
Traditions and privacy
Self-support: we are a vendor, and nothing more
FellowshipOS sells hosting and software for a monthly fee, the way a landlord rents a meeting room or a printer prints a schedule. Paying a vendor from committee funds does not compromise self-support; accepting outside money, or letting an outside enterprise direct committee decisions, would.
- We take no percentage of any contribution. Stripe Connect accounts are the Area’s or the group’s own, and the code refuses to set a platform fee.
- We never hold your funds. Money moves from contributor to the committee’s own account without passing through us.
- We accept no outside funding, sponsorship or advertising that would be placed in front of your members. There are no ads in the product, and there will not be.
- Hardship grants waive our own fee. They are a discount we give, not money from anyone outside the fellowship.
Seventh Tradition receipts are not tax-deductible
Receipts FellowshipOS generates for an Area without a 501(c)(3) determination therefore state plainly that the contribution is not tax-deductible, and name no charitable status. This wording is not editable into something more flattering, because a receipt that overstates deductibility is a problem for the contributor who relies on it and for the committee that issued it.
An Area that genuinely holds a 501(c)(3) determination letter can record that, and its receipts change accordingly. We are a software vendor, not a tax adviser; if your committee is unsure which case it is in, the determination letter is the test — you either have one or you do not.
Anonymity is a design constraint, not a setting
- Display names default to a first name and last initial, derived at sign-in. Full names are not required anywhere.
- There are no tracking cookies, no analytics pixels, no tag managers and no third-party advertising scripts. The content security policy does not permit them.
- Care-group rosters are readable only by that group’s own members and seat holders, and by Area admins and moderators. Platform staff browsing with their own account cannot read them — the super-admin flag deliberately grants no bypass over member data.
- Member data is never sent to an AI model. Compliance checks read content drafted for publication; OCR reads the document you hand it.
- Public pages are cached at the edge only when the response carries no session cookie at all.
Group autonomy is enforced in the schema
An autonomous homegroup chooses its own answer on money — cash only, a custodial Area ledger, or its own Stripe account — and the Area cannot override that choice through the portal. An Area subcommittee is a different thing: it is an organ of the Area, it is not autonomous, and it routes through the Area treasury. The database holds that distinction as a constraint, so no interface change can quietly erase it.
Events inherit it too. An event hosted by an autonomous group is reviewed in the widest zone; an event hosted by an Area subcommittee carries tighter guardrails, because an Area speaks for the fellowship as a whole in a way a single group does not.
Who to write to
Questions about a specific Area’s practices go to that Area’s trusted servants; we do not speak for them. Questions about how the software behaves go to Nelson Agentic LLC — see the privacy policy for the controller and processor split.