Memory you choose
Memory Continuum keeps only the context you decide to save, so Sofia or Mark can pick the thread back up without you retelling the whole story.
Some days you just need to get it out of your head. Talk to Sofia when you want to be heard, or Mark when you need a plan. It stays private, it remembers you, and it's only ever yours.
Private by default. Your chats stay in your account, and no one else reads them.
A thread can remember you without becoming anyone else's data. Memory Continuum stays in your account, and you choose what it keeps.
Private by default. Your chats stay in your account, and no one else reads them.
Two voices, one thread
Sofia slows the moment down. Mark turns pressure into one workable move. Both stay inside your account.
Private, not scored
Nothing you say is mined, rated, or turned into a profile. Guardian watches only for real safety moments and helps you find support.
Privacy boundary
Private support stays inside the account.
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.
01
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
02
Separate product surfaces
Workplace tools start from their own records.
Wellness, reports, exports and Executive Oracle can only use workplace-scoped data paths. They do not query Sofia/Mark chat text.
- Scoped workplace records
- No raw private text
- No recruiting input from support
03
Human review boundary
People and Recruitment stay operational, not psychological.
People, Calendar and staged Recruitment can organize records for human review without turning private support into a profile or hiring signal.
- No person-level wellness scoring
- No raw private conversations in reports
- No automated hiring decisions
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.
Private by default
A private thread continues
Memory Continuum keeps the context a user chooses to save, so Sofia or Mark can pick up the next session without asking for the whole story again.
Keep it privateTwo voices, one boundary
Choose Sofia when you need a softer reflection. Choose Mark when you need pressure sorted into one next action.
See what's rememberedGuardian routes safety language
When a message signals possible crisis or escalation, Guardian shows safety guidance without turning the chat into an employer-visible incident.
How privacy worksWorkplace tools stay separate
Wellness, Executive Oracle, People, Calendar and Recruitment use their own scoped records. They cannot read Sofia/Mark chats or Memory content.
How Guardian keeps you safeChoose a companion
Pick the style that fits this moment
Sofia and Mark share continuity, but they do different jobs: Sofia slows the conversation down; Mark turns pressure into one workable step.
private supportmemory you chooseyours alone
Companion style
Sofia
Sofia: quiet reflection
Sofia is the calmer voice for grief, loneliness or uncertainty. She keeps the thread of what the user has shared and helps name the feeling before choosing a next step.
heavy feelingsmemory you choosea gentler next step
Companion style
Mark
Mark: pressure into action
Mark is the structured voice for pressure, burnout signals or decision fatigue. He separates facts from noise and turns the moment into one practical next step.
sorting the pressurefact from noiseone workable move
Category map
Explore the connected system
Emotional AI Companion | HR Wellness Intelligence | Privacy-Safe Workforce Insights | Adoption & Activation
Private companion support, continuity, and safety model.
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.
Companion philosophy, Guardian boundaries, and privacy commitments.
Private start
Open a support thread first.
Begin with Sofia or Mark, save only the context you want to carry forward, and review the product boundary before inviting a workplace conversation.