Trust & Privacy Compact

Version
1.2.0
Effective
2026-03-24
Status
Active
Maintainer
ssny-us/business
Applies to
All products, services, and platforms operated under Success.Build, OurLegion.org, and any branded instance of Factory

Preamble

The American Legion Preamble calls its members to safeguard and transmit to posterity the principles of justice, freedom, and democracy. Two delegates from each Boys State program are selected for Boys Nation in Washington, D.C., where they learn firsthand that governance requires both power and restraint: that justice means protecting the rights of those who trust you with authority.

Privacy is a matter of justice. When a person entrusts their email address, their membership, their communications to a platform, they are extending trust. That trust is not a commodity to be monetized. It is an obligation to be honored.

This Compact is our enforceable commitment to that principle. It is versioned, auditable, and published. Every version is permanent: changes are additive (we can make stronger promises, never weaker ones). If we ever violate this Compact, the violation is documented, disclosed, and remediated publicly.

Article I: What We Will Never Do

These are absolute. They do not have exceptions, carve-outs, or sunset clauses.

  1. We will never sell, broker, or trade contact information. Not to advertisers. Not to data brokers. Not to partners. Not to anyone. Ever.
  2. We will never harvest behavioral data for advertising. No tracking pixels for ad networks. No profiling for targeted advertising. No selling attention.
  3. We will never use dark patterns. No hidden opt-ins. No confusing unsubscribe flows. No bait-and-switch pricing. No guilt-driven retention screens. No pre-checked consent boxes.
  4. We will never hold data hostage. Every user can export everything (contacts, messages, membership lists, configuration) in standard formats (CSV, JSON). If a community outgrows us, they leave with all their data.
  5. We will never weaken a privacy commitment in a new version of this Compact. Version 2.0 can add protections. It cannot remove them. This clause is self-referential and applies to itself.
  6. We will never read, analyze, or mine the content of private group communications for any purpose other than delivering the message to its intended recipients and enforcing the group's own moderation policies.
  7. We will never share member lists across organizations without explicit, recorded, per-instance consent from both the member and the organization's authorized representative.

Article II: What We Promise

These are the active commitments we make to every person whose data passes through our systems.

II.1: Consent Is Recorded, Not Assumed

Every opt-in is a recorded event with:

  • A timestamp
  • The channel (email, SMS, web)
  • The specific permission granted
  • The identity of the granting party
  • An audit trail that cannot be retroactively modified

Consent is never inferred from inaction. Silence is not consent. Pre-checked boxes are not consent. Buried terms-of-service clauses are not consent.

II.2: STOP Means STOP

When a person opts out of any communication channel:

  • Delivery ceases immediately (within the current processing cycle, never more than 24 hours)
  • The opt-out is recorded with the same rigor as the opt-in
  • No "are you sure?" guilt flows. No "you'll miss out" retention tactics
  • The person can re-subscribe at any time, on their own terms

II.3: Data Minimization

We collect only what is necessary to deliver the service. We retain only what is justified. We delete when the justification ends.

For group communications, this means:

  • Message content is retained for archive and digest delivery per the group's configured retention policy
  • Metadata (who sent, when, to which group) is retained for audit and compliance
  • Delivery data (bounces, opens) is retained for operational purposes only, never for profiling
  • When a member leaves a group, their future communications cease. Their historical messages remain in the archive (they were part of the conversation) unless the group's policy requires purging

II.4: Boundaries Between Groups

A member of Post 506NY cannot see the members of Post 138NY unless they are members of both. A County Commander can see aggregate information about posts in their county but cannot access individual post member details unless they are also a member of that post.

This is not a feature. It is a privacy boundary enforced at the architecture level.

The trust hierarchy:

  • Member sees: their own group's members and messages
  • Manager sees: their own group's members, messages, and moderation queue
  • Authorized cross-group poster sees: nothing additional (they can send to a group, but that does not grant them visibility into its membership)
  • Parent group administrator sees: aggregate counts and group-level metadata of child groups, not individual member data
  • Platform administrator sees: everything, and every access is logged

II.5: Portability

At any time, any authorized group administrator can export:

  • Complete member list (name, email, role, join date)
  • Complete message archive
  • Group configuration (posting policy, moderation settings, SMTP configuration)
  • Usage history

Exports are available in CSV and JSON. No vendor lock-in. No "contact us to get your data." Self-service, immediate.

II.6: Audit Trail

Every message that passes through the platform is archived with:

  • Sender identity (email, user ID, authenticated)
  • Group identity (ID, name, posting policy at time of send)
  • Subject and body (per group retention policy)
  • Recipient count and distribution scope
  • Source (webhook, web compose, IMAP, API)
  • Message type (discussion, announcement)
  • Timestamp
  • Processing metadata (provider, duration, IP)

This audit trail is:

  • Known: every participant knows it exists
  • Accessible: group administrators can view and export it
  • Trusted: authenticated, tamper-evident (append-only archive)
  • Allowed: consent to archiving is part of group membership

The audit trail serves the group's interests, not the platform's. It exists so that when leadership transitions happen, the new leader inherits a complete record of organizational communications. It is never used for behavioral profiling, advertising, or surveillance.

II.7: Transparency

We publish:

  • This Compact (versioned, in git, with full change history)
  • Our data retention policies per feature
  • Our subprocessor list (SendGrid, Twilio, FOSSBilling, etc.) with what data each touches
  • Our security incident history (if any; we hope this section stays empty)

Article III: Trust Circles

Trust in the platform is hierarchical and mirrors the organizational structures it serves.

III.1: The Legion Model (Reference Implementation)

Department (State)
  └── Zone
       └── District
            └── County
                 └── Post
                      └── Member

Each level has a defined trust boundary:

LevelCan authorizeCan viewCan communicate to
Post CommanderPost members, post managersPost membership, post messagesPost members
County CommanderPost commanders in countyCounty aggregate, county groupCounty group, authorized posts
District AdjutantCounty commanders in districtDistrict aggregate, district groupDistrict group, authorized counties
DepartmentAll within jurisdictionAll within jurisdiction (logged)Organization-wide

Key principle: Authorization to communicate does not imply authorization to view. A District Adjutant can send a message that reaches every post in the district (via authorized groups), but they cannot browse individual post member lists unless they are also a member of those posts.

III.2: The General Model

The Legion model is a reference implementation. The same trust hierarchy applies to any organizational structure:

Organizational termPlatform concept
Post / Team / ChapterGroup
County / Division / RegionParent group with authorized children
District / DepartmentFederation of parent groups
Commander / Director / ChairManager role with posting authority
Adjutant / Secretary / AdminManager role with administrative authority
MemberMember

III.3: Cross-Group Trust

When Group A authorizes Group B for cross-group posting (#336):

  • Members of Group B can send to Group A
  • Members of Group B cannot see Group A's member list
  • Members of Group B cannot access Group A's message archive
  • Messages from Group B members are subject to Group A's moderation policy
  • Group A's ban list overrides Group B's authorization

Trust is granted explicitly, per-group, by the group's administrator. It is not inherited, assumed, or automatic.

Article IV: Pricing and Access

IV.1: Fair Pricing

  • A free tier is real and permanent. That tier is not a trial and does not expire. It stays useful, but it may not include every feature, especially features that strain shared resources.
  • Other free tiers may carry a time limit. We state the limit before anyone signs up (Article I.3).
  • Pricing tiers reflect usage capacity, not feature gatekeeping (until features justify track differentiation)
  • No per-seat pricing. A post with 50 members and a post with 500 members pay the same tier price if they use the same capacity
  • Annual pricing offers genuine savings (9-20%), not artificial monthly inflation

IV.2: No Bait-and-Switch

  • Published prices are the prices. No "contact us for enterprise pricing" opacity.
  • If we change pricing, existing subscribers keep their current rate for the remainder of their billing period
  • We will never raise prices on an existing subscriber without 90 days written notice

IV.3: The Promise Document

Every subscriber can access their complete entitlement record (#337):

  • What limits they were told they have
  • What they've used
  • What changed and when
  • Exportable as JSON

This is the "promise document": a portable, auditable record of what we committed to and what we delivered.

Article V: Enforcement and Accountability

V.1: This Compact Is Versioned

Every change to this Compact is tracked in git with a commit message explaining what changed and why. The version number follows semantic versioning:

  • Major (e.g., 2.0.0): New articles or structural changes
  • Minor (e.g., 1.1.0): Strengthened protections or clarifications
  • Patch (e.g., 1.0.1): Typo fixes or formatting (no substantive change)

Per Article I.5, no version change can weaken a protection established in a previous version.

V.2: Violations Are Disclosed

If we discover that we have violated any provision of this Compact:

  1. We disclose the violation publicly within 72 hours of discovery
  2. We document the root cause
  3. We implement a fix
  4. We document what we did to prevent recurrence
  5. We update this Compact if the violation reveals a gap in our commitments

V.3: The Compact Survives

If Success.Build, SSNY, or any operating entity ceases operations:

  • All user data is exported and delivered to the group administrators
  • No data is sold, transferred, or retained by the defunct entity
  • This Compact's obligations survive the entity that made them

Changelog

VersionDateChange
1.0.02026-03-24Initial version
1.1.02026-03-24Added Article II.6: Audit Trail (known, accessible, trusted, allowed)
1.2.02026-11-17Clarified IV.1: a free tier is permanent and useful, not a fixed feature set; other free tiers may carry a stated time limit

Source References

  • ETHOS.md: Build philosophy (parent document)
  • REFERENCE_stewardship-model.md: Stewardship relationship framework
  • American Legion Preamble: "to safeguard and transmit to posterity the principles of justice, freedom, and democracy"
  • Boys Nation: "where they serve as U.S. senators in a week of mock sessions" (governance requires both power and restraint)
  • Factory Release Model: docs/REFERENCE_release-feature-model.md
  • Authorized Groups: factory#336
  • Entitlement Ledger: factory#337