For employers
Six tools built on one private intake. Personal answers stay on the employee’s device — not in your HR stack.
At a glance
What employees get
Most wellbeing benefits offer one thing — an app, a hotline, a portal. Almavivo covers six concrete jobs an employee runs into during a working year, all built on one shared intake.
Why it lands where others stalled
Industry-average completion on health-assessment-style platforms sits around 22%. Employees suspect their answers may be visible to management or exposed in a breach, so they answer cautiously or not at all. Almavivo removes that friction by design — the most sensitive answers don’t need to leave the device.
Household value, not a family health record
An employee can keep separate profiles on the same device for adult household members — a partner, an adult child, a parent they’re helping — each with their consent and on a personal device. Profiles are independent and stay on-device. Almavivo and the employer don’t receive dependant data. For under-18s, the supplement engine routes to a paediatrician.
What employers see, and what they don’t
| An employer can receive | An employer does not receive |
|---|---|
|
|
Cohort reporting beyond seat allocation is a separate, agreed capability — not a default. Where it’s enabled, your normal employment and data-protection obligations apply.
Best fit
Auditable by your DPO and medical advisor
Every question, supplement rule, excluded item, and safety guard is published openly under Apache 2.0. Your medical advisor reviews the rules. Your DPO reviews the data flow. Your security team reads the source. Nothing on trust.
github.com/almavivo/open-health-enginemethodologywhat we excludeprivacy architecture
Start with a controlled pilot
12 weeks, 50–100 seats, full premium tier free at point of use for every covered employee. Pilot pricing for the first few firms in each segment. Both sides decide at week 12 whether to expand.
Email [email protected] with rough team size, target start month, and the primary concern you want the pilot to address.
FAQ
No. Intake answers, lab values, plans, ratings, and favourites live only in the employee's browser. They are not transmitted to our servers during normal use.
No. Employers do not receive individual reports. We do not maintain a server-side employee health record an employer can inspect.
Only if the employee initiates it. The share path composes a message in the employee's browser and hands it to their own mail client. There is no admin-side ingest.
No. Almavivo is an educational tool. Red-flag symptoms are routed toward clinical review.
A survey collects answers into a database. Almavivo doesn't. The intake stays on the device, the recommendation runs on the device.
No. A deterministic rules engine produces recommendations. A language model never generates supplement decisions.
Yes — an employee can keep separate profiles on the same device for adult household members, with consent, on a personal device. Profiles are independent. For under-18s, the supplement engine routes to a paediatrician.
No. Almavivo complements, not replaces. The prep sheet routes employees toward their existing GP/PMI relationship.
Intake answers are not transmitted to our servers during normal use, so no central duty arises for them. Anything you separately agree (seat lists, activation counts, cohort reporting) is within your normal employment-and-privacy obligations. Your DPO or legal counsel should be involved in defining cohort data and lawful basis.
We've designed it not to be. It does record-keeping and question-generation only. It does not calculate doses, check interactions, or output a clinical recommendation. The boundary rationale is documented internally and shareable under NDA.