Privacy boundary map

Access rules name the source.

Sofia/Mark conversations, Memory and Guardian context stay outside employer dashboards, Oracle, reports and Recruitment. Non-owner raw access follows the documented security-root break-glass path.

Privacy boundary

Private support stays inside the account.

A private thread can remember chosen context without becoming a manager, reseller or ordinary admin view.

Account-owned support

Sofia, Mark, Memory and Guardian stay with the person.

A private thread can remember chosen context without becoming a manager, reseller or ordinary admin view.

No employer chat access
Memory stays in the account
Guardian stays a safety route

Employers do not receive raw Sofia/Mark conversation text. No employer-facing raw Sofia/Mark conversations, memories, Guardian details, or person-level wellness scoring.

Non-owner raw access stays behind the documented, audited security-root break-glass path.

Pillar

User-owned support track

Sofia/Mark conversations, Memory and Guardian context stay outside employer dashboards, Oracle, reports and Recruitment. Non-owner raw access follows the documented security-root break-glass path.

Pillar

Policy-backed claims

Privacy, Data Safety, Cookie Policy, Terms and Safeguarding pages carry the formal wording. The trust page does not add audit, certification or guarantee claims.

Visible release checks

This is a public boundary checklist, not a legal policy. Formal privacy, DPA, subprocessor and safety wording stays on the linked policy pages.

✓No employer, reseller or recruiter gets raw Sofia/Mark chats, Memory content or Guardian details.
✓No public trust claim names an audit, certification, guarantee or customer traction without a current legal/security source.