Privacy boundary map
Trust starts with source separation: Sofia/Mark, Memory and Guardian stay on the user-owned support track; Wellness and Oracle read aggregate company models only after the 10+ anonymity floor; Recruitment stays an HR review record.
Privacy boundary
The boundary is concrete: Sofia/Mark chats, saved Memory context, and Guardian routing stay in the person's account. Workplace tools use their own scoped records instead of reading the support thread.
Account-owned support
A private thread can remember chosen context without becoming a manager, reseller or ordinary admin view.
Separate product surfaces
Wellness, reports, exports and Executive Oracle can only use workplace-scoped data paths. They do not query Sofia/Mark chat text.
Human review boundary
People, Calendar and staged Recruitment can organize records for human review without turning private support into a profile or hiring signal.
Employers do not receive raw Sofia/Mark conversation text. No employer-facing raw Sofia/Mark conversations, memories, Guardian details, or person-level wellness scoring.
Wellness, reports and Oracle must use separate scoped workplace records, not private support content, and stay blocked when the privacy floor fails.
Non-owner raw access stays behind the documented, audited security-root break-glass path.
Pillar
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
Wellness Dashboard, Executive Oracle, reports and exports can answer company questions only after the 10+ anonymity floor passes; thin cohorts return no company view.
Pillar
People and Calendar use operational workspace records. Recruitment/Leviathan can organize candidate evidence for HR review, but it cannot use private support or Wellness input.
Pillar
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.
Use Privacy Policy, Data Safety, Terms, Cookie Policy and Safeguarding for formal wording. Contact Synphoria for DPA or subprocessor scope.
Category map
Emotional AI Companion | Clinic Continuity Platform | HR Wellness Intelligence | ATS Evidence-Based Recruiting | Privacy-Safe Workforce Insights
Private companion support, continuity, and safety model.
Category entry: support for people, signal for teams, and human-owned decisions.
Read-only specimen of companion, company, and recruitment workflows.
Feature page for account-owned support context, review, replacement, and deletion.
Feature page for the private daily support ritual, separate from workplace signal.
Feature page for non-clinical safety routing that stays with the user.