Fair questions.
Straight answers.

Only the people whose role allows it. Access is permissioned per organisation: a staff member sees the group they are responsible for, a clinician sees the whole panel, and a family sees their own child and no one else's. Health data is end-to-end encrypted on the way through — the server only ever holds ciphertext, so what sits on our side is unreadable to us. You decide who holds which role, and you can change it.

Yes. Nothing shows up in Studio unless the individual — or their parent or guardian, if they're a minor — has chosen to share it from their own Mirri app, and they can stop sharing whenever they want. Your organisation accepts the terms, but each person still decides whether their numbers are in the room. Consent isn't a one-time checkbox buried at setup — it lives in their app, right next to the switch that turns it off.

Studio never talks to a sensor. It receives whatever the person's own Mirri app manages to send: five-minute readings when the connection cooperates, best-efforts and never guaranteed. That app already reads from many of the CGM brands people actually wear, so there's a good chance nobody in your group has to change hardware — worth checking rather than assuming. If you need a specific brand or model confirmed before you commit, ask us and we'll tell you plainly whether it works today or is still on the list.

That isn't a badge we'll claim. Mirri is not a HIPAA covered entity, and we are not acting as your business associate. Here's what is true: health data is end-to-end encrypted, the server only ever holds ciphertext, access is scoped by role, and every person shares by their own choice and can stop. Whatever obligations your organisation carries — HIPAA, FERPA, state health-data law, your own policies — remain yours. And the blunt part, because your legal team will find it anyway: Studio is a non-HIPAA service today, so if you are a covered entity or a business associate you cannot use it for protected health information yet — not until we ship a HIPAA version and we both sign a Business Associate Agreement. Clinical and HIPAA-regulated use is on the roadmap, not on the shelf. The Studio Privacy Policy spells out exactly what we hold and what we don't; read it before you bring it to your legal team, because they'll ask.

Studio is an MVP and we're onboarding organisations one at a time, so there's no self-serve signup and no public price list. Pricing is per organisation and depends on how many people you're looking after and what shape your group is — a school district and a summer camp aren't the same thing. Tell us about yours and you'll get a real number rather than a range.

An afternoon, for most groups. Onboarding is hands-on with our team, not a signup form: we create your organisation, set the roles, and walk through inviting people. The part that takes longest is each person connecting from their own Mirri app, because that happens on their schedule, not yours. A cabin at camp or a nurse's caseload is usually on one screen the same day.

You export what's yours, and then it goes. Ending the arrangement ends the sharing on the individual's side too — their data returns to being just theirs. We don't keep a quiet copy to make leaving harder: once sharing ends, the data comes out of Studio's active systems within 30 days and out of routine backups within 90 — sooner if you ask, and only ever held longer where the law requires it. We don't sell or trade any of it. Export and deletion, including the timelines, are set out in the Studio Terms of Service.

Yes — one person is the smallest useful group, and a lot of our early conversations start exactly there. A parent gets the same roster card, the same detail view with the glucose trace, active insulin, carbs on board and CarbIn, and the same permissions as a clinic does; it's simply a roster of one. If your family or your caseload grows, the screen grows with it.