How VEX handles AI and client consent.

Told before, not after

Every client is told, before the reading begins, that completing it shares the result with their coach. No one discovers after the fact that a coach was watching.

Sharing requires an explicit yes

When a client finishes, they see their own result first. Sharing it with their coach requires their explicit yes at that reveal. If they decline, the coach sees nothing.

The coach sees the brief, never the raw answers

What the coach receives is a brief: where the client is, what moves them, what to open with. The client's raw answers stay with the client. They are theirs, and theirs to delete.

AI use is disclosed

The brief is AI-generated from what the client chose to share. Clients are told this. Coaches can say it plainly to clients because it is written down here, on a page anyone can read.

Group views require five or more

Any aggregate or team view is drawn only from clients who consented, and only when five or more have. Below that floor, no group read exists, so no individual can be singled out by subtraction.

Clients can withdraw

Consent is not a one-time gate. A client can withdraw sharing, and their data drops out of what the coach and any group view can see.

What the record actually stores

A yes is not one checkbox on our side. At the moment a client says yes, VEX writes a named record against that person, for that one coach or organization. These are the fields, under the names they carry in the code:

• granted_at timestamp
  The moment of the yes.
• share_current_read granted
  The coach may see the brief from the client's current reading.
• allow_1on1_prep granted
  The coach may use that brief to prepare a session with the client.
• allow_timeline not granted
  Being read once is not a standing grant to be followed over time.

One record per person, per relationship

Two coaches means two records, each with its own timestamp, each withdrawn on its own. A client who consents to one coach has consented to that coach, and to nothing else. Nothing is granted account wide and nothing is inherited by a second coach or a later employer.

What is enforced today, stated plainly

Access is gated on the recorded consent for that relationship as a whole. Withdraw it and every coach facing and leader facing view for that relationship goes dark at once, because they all read the record live. The four fields above are the record of what was asked and answered. They are not yet four separate switches: the movement view a coach can see across a client's readings runs off the same single consent today. We will keep saying that here until per field enforcement ships, rather than describe a control that is not in force.

The client can read their own record

Not a policy the client has to take on faith. Any client can open noctaracorp.com/consent, see every coach and organization that can currently see their read, see the named fields above exactly as stored for each one, and close any of them from that page.