Philosophical Foundation
On Privacy & Structural Integrity
Interiority is not data to be mined. It is a sanctuary to be honored. When we speak of "privacy" in the BARS Engine, we are not just describing a legal compliance layer; we are defining a design principle for human wholeness.
The Structural Extraction Model
Traditional systems capture your **stories**---the specific details of your life. The BARS Engine captures only the **tension vectors**.
What stays with you
The "Drama"
- Specific names/events
- Raw journal entries
- Detailed shadow voices
- The "Content" of your life
What fuels the game
The "Structure"
- Emotional Charge (e.g. Joy, Fear)
- Intensity Magnitude
- Transformation Moves
- The "Geometry" of the shift
By separating the "charge" from the "story," we can build a collective game field without ever needing to own your private interiority.
The Wholeness Principle (Teal)
In an evolutionary organization (Teal), we recognize that you are not a resource to be managed, but an agent of your own development. Wholeness requires that you can bring your shadow into the light without fear of surveillance.
If you choose to publish a story (via the CYOA Generator), you are consciously turning your private metal into a collective artifact. Until that moment, your work is a closed circuit between you and the witness you choose.
The Role of the Agent
The Agents you interact with are witnesses. They help you "Unpack" and "Clean Up" your charge. They are programmed to support your evolutionary purpose --- not to harvest your vulnerabilities. The data they see is treated as ephemeral fuel for the ritual, never as a persistent profile. See the game rules for how these boundaries are enforced in play.
Course submissions — what we store, and for how long
The sections above describe a design principle. This one is the operational rule for the one place the Mastering the Game of Allyship course sends anything to us: the Day 10 handoff.
What stays on your device
Every answer you write during the thirty days of the course lives in your browser for that session and clears on refresh. The 3-2-1 dialogue, the load check, body weather, beliefs, and card answers stay on your machine. The course records which day numbers you finished, and that stays in your browser too.
What can leave, and only by your choice
On Day 10 you can build a handoff and choose to send it to the Campaign Stewards. You review every field before it goes. This handoff is visible only to MTGOA Campaign Stewards, currently Wendell Britt. It stays unpublished, and it assigns you nothing.
What you are promised in return
Every handoff is read by a Campaign Steward. Asking for a response does not guarantee one, and no submission creates a role, task, or commitment.
Retention — Release 1
We keep your handoff until you withdraw it. Withdrawing deletes your name and contact details immediately. The handoff itself stays in the campaign record with nothing identifying you attached.
Your name, contact route, and region are stored only when you asked for a response and ticked consent. A handoff sent with “no reply needed” creates no contact record at all.
How you withdraw
You get a one-time link to your handoff. It shows the handoff and its steward status, and it lets you withdraw or change how you want to be reached. It reaches only your own submission.
This works for anonymous senders as well. The link is the whole authorization, which is why we show it once and email it to you when you supplied an address.
Effective 2026-08-27, for Release 1 of the Day 10 handoff. Changes to this rule appear here before they take effect.