Three actors. Three separate data scopes. A clean, plain-English picture of where data lives — and what is structurally impossible for an employer to ever see.
Every piece of data in Glimetry sits inside one of three boundaries. Nothing crosses unless it has been deliberately stripped of identifiers.
A private dashboard with full personal history. Nothing is mirrored back up to the employer.
A live dashboard of aggregate, anonymized engagement metrics. No row of data is tied to a name.
A studio dashboard scoped to a single location. Members are anonymized IDs, never names.
The employer portal queries only aggregate tables. Individual records are never joined to employer-visible queries — not by policy, but by architecture.
A check-in becomes a number on the employer dashboard without any name, history, or identifier ever crossing the wall.
The app shows an anonymized session token — never a name, ID, or health detail.
The studio records a timestamped event tied to the anonymized member, scoped to their location.
The verified check-in raises the employee's engagement score in real time — visible to them only.
Population averages and participation rates recalculate. No individual record ever appears.
Read the FAQ for the full breakdown — or get in touch and we'll walk you through it.
