Built for trust,
not just compliance.
Mimashi doesn't bolt privacy on at the end. It's the founding principle — designed so employees can seek help without any fear of being watched.
Talk to us about privacy
The exact line between employer and employee.
Not a policy promise. An architectural guarantee.
HR never sees
- Who booked a session
- What was discussed in sessions
- Therapist notes or diagnoses
- Individual check-in responses
- Attendance or no-show data per person
- Any personally identifiable information
HR sees (aggregated only)
- Aggregated utilization rate (team-level)
- Cohort wellbeing score trends
- Time-to-first-session averages
- Session count totals (not per-person)
- Department-level trend data
- Program health summary
How privacy works at every layer.
Anonymous by architecture
Individual identity is decoupled from session data at the database level. There is no toggle HR can flip to see who used the service.
Consent at every step
Employees consent to what data Mimashi collects and how it is used. They can opt out of wellbeing check-ins at any time.
Aggregation before reporting
All employer-facing reports are computed on aggregated cohorts. Data is never disaggregated to the individual — in the UI or the API.
No diagnosis, no flagging
Clinical notes stay between the employee and their therapist. Mimashi does not share diagnoses, session summaries, or risk flags with employers.
Minimum cohort size
Employer reports only display data when a cohort is large enough to prevent re-identification — protecting individuals in smaller teams.
Audit trails for employees
Employees can request to see exactly what data Mimashi holds about them and what (if anything) was shared with their employer.
Questions about how privacy works?
We walk every prospective employer through the architecture before signing. No surprises.
Talk to us