Roles and trust
One athlete, four roles. Each role sees a different slice of the same memory, on permissions the athlete chose. No surprises, no shadow access.
Avelok has exactly four roles. Anyone using the product is in at least one of them; many people are in more than one (a coach who also plays, a parent who runs a small club).
Default-private, opt-in-shared
A player creates an account. By default, nobody else sees anything. No coach, no club, no parent. The player has to invite each one explicitly, and they pick the depth of the share each time.
There are three depths:
Profile only
The other person sees the public face of the memory — current strengths and weaknesses in plain language. No raw context, no chat, no plans.
Profile + sessions
Adds the timeline of training sessions and matches the player has logged, going forward from the moment they granted access. Past sessions stay private unless explicitly back-shared.
Working coach
Adds the AI's draft analysis, planning surface, and the ability to write new sessions on the player's behalf. This is the only depth that a coach can use to actually coach.
The player can downgrade or revoke any of these at any time, from a single screen. Revoking is immediate — no 30-day cooldown, no "the coach will be notified." If you want out, you're out.
Parents and minors
For athletes under 13, the legal owner of the account is the parent or guardian. They sign up first, then create the player profile, then optionally hand over day-to-day operation to the child. Avelok hides every "Ask AI" surface from under-13 accounts unless a parent explicitly turns it on, and even then the AI runs in a calmer, more conservative mode (no nutrition advice, no body-image comments, no peer comparisons).
Between 13 and 18, the player owns the account but the parent retains a read-only view of two things: training attendance, and any safety flags the AI raised. They cannot read the raw conversation.
What clubs can and cannot see
Clubs are the most constrained role on purpose. A club admin who runs a 200-member academy can see:
- Each member's name, age band, payment status, attendance at club-organised events
- Their own coaches' schedules, lesson notes (only the ones the coach chose to mark as "club visible"), package consumption
- Aggregate club-level stats: retention, churn, average sessions per member
A club admin cannot see:
- Any individual player's AI conversations, ever
- Any coach's private session notes (only the ones marked "club visible")
- Any parent's communication with their child's coach
This is why we built Club OS as a separate surface from Coach Studio. They use the same backend, but they show different things, and the line between them is not negotiable.
What the AI sees
The AI is the fifth quasi-role, but with severe constraints:
AI access is per-conversation, not global
When an athlete asks the AI a question, the AI gets read access to that athlete's memory only — and only the slices relevant to the question. A coach asking the AI "what should we work on with Jamie next week?" gets the AI to read Jamie's memory, but only because Jamie granted that coach a "working coach" share.
The AI never sees data from one athlete's memory while answering another athlete's question. Cross-athlete patterns (e.g. "most of my players struggle with the third-ball attack") are computed on the coach's local view, not by the AI looking across players.