Privacy Policy

Last Updated: October 24, 2026

1. Introduction

Mirri Diabetes LLC (“Mirri,” “we,” “us,” or “our”) provides Mirri Cloud. Mirri Cloud is two things that work together:

• the service that keeps the health record a person creates in MIRRI One, Mirri’s mobile app, in sync between that person’s own devices and shares it with the people they choose; and
• the Mirri Cloud website at cloud.mirridiabetes.com, where people read and analyze their own record and the records other people have chosen to share with them.

This Privacy Policy explains what information Mirri Cloud handles, what we can and cannot see, and the choices you have. Please read it together with the Mirri Cloud Terms of Service, the Mirri Cloud Consumer Health Data Privacy Policy and, if you use MIRRI One, the MIRRI One Privacy Policy. This Privacy Policy replaces all earlier versions.

2. Our Role; Research and Data Analysis; HIPAA

Mirri Cloud is offered to individuals for research and data analysis: reading, arranging, and analyzing their own data and data that other people choose to share with them. Clinical use is not offered yet.

Mirri is not a HIPAA covered entity or business associate. Mirri Cloud is not offered to, and may not be used by, a HIPAA covered entity or business associate in any way that would cause Mirri to create, receive, maintain, or transmit protected health information on its behalf. Mirri Cloud is offered as a non-HIPAA service.

We handle information in accordance with this Policy and applicable privacy laws, including the Federal Trade Commission’s Health Breach Notification Rule; the Washington My Health My Data Act; the Nevada Consumer Health Data Privacy Law; the Connecticut Data Privacy Act; the Indiana Consumer Data Protection Act; the California Consumer Privacy Act (as amended by the California Privacy Rights Act); and similar state laws, where they apply.

3. How Mirri Cloud Protects Your Entries

Sealed on your phone. MIRRI One seals each entry — for example a glucose reading, an insulin dose, a meal, or a workout — on your phone before it is uploaded. Our servers store the sealed entry and hold no key that can open it. Our staff and our service providers have no key that opens your entries either.

Opened only on devices you approve. Your record’s keys stay on your devices. Copies of them are stored only in forms that your devices, a passphrase or passkey you set up, or your Recovery Code can open. A web browser that opens Mirri Cloud makes its own key, which never leaves that browser, and it can read a record only after a phone that holds the record’s keys approves it. Entries are opened on your phone or in your browser, never on our servers. On iPhone, MIRRI One also saves your Recovery Code in your iCloud Keychain, so anyone who can sign in to your Apple Account on a device that knows your passcode could use it.

What our servers can read. To store and deliver sealed entries, our servers need some information in readable form, which we call “routing information.” For each entry, it includes the record the entry belongs to; its kind (for example, “glucose” or “insulin”); the times it covers, its local date, and its time zone; the device that wrote it; its size; and whether it replaces or deletes an earlier entry. Routing information can show that a kind of information was recorded at a certain time, but not the value that was recorded. MIRRI One does not send your cycle or other reproductive-health information to Mirri Cloud. We can also read the account, record, device, and follower details described in Section 4.

Limits. This protection depends on MIRRI One and the Mirri Cloud website working as designed. No method of encryption, transmission, or storage is completely secure, and we do not guarantee that our security measures cannot be circumvented or that security will never fail.

4. Information We Handle

a. Account information. Your email address and, if you give one, a display name for your account. You sign in by entering a one-time code that we send to your email address, and we do not ask for your phone number. Your Mirri Cloud account is the same account you use for Mirri Cloud in MIRRI One. Our sign-in system also keeps a log of sign-in events and the sessions you have open, which can include your email address, IP address, and app or browser details.

b. Record details. When you create a record in MIRRI One, it sends a display name for the record, which we store in readable form.

c. Sealed entries. Once you turn on Mirri Cloud, MIRRI One keeps your record there: it seals the kinds of health information it syncs and uploads them in the sealed form described in Section 3, whether or not anyone follows your record yet. You choose which kinds each Follower may read. The kinds of information a record can hold are listed in the Mirri Cloud Consumer Health Data Privacy Policy. MIRRI One does not send your notes, your photos, your conversations with Iris, or your cycle or other reproductive-health information to Mirri Cloud.

d. Devices and keys. For each phone, tablet, or browser that can read a record: a label, its platform, its public key, and when it was last seen. Your record’s keys are stored only in the sealed forms described in Section 3.

e. Followers and invitations. Who follows which record; which kinds of information each Follower may read; when each Follower was confirmed and when their access ended; and when each Follower’s device last opened the record. An invitation can be used only once and expires within 24 hours, and we store its code only in scrambled (hashed) form.

f. Notification tokens. If you use MIRRI One, we store your device’s Apple or Google push token, with when it was registered and when notices were delivered. Our notices carry no health information: they only wake MIRRI One to sync, tell it to fetch and open new entries itself, or ask it to redraw what it already shows. On a Follower’s phone, MIRRI One can also show reminders and Lock Screen widgets about the followed person’s recent doses, such as when a prebolus time has passed; that phone makes them from the entries it opened, and our servers do not send them.

g. Security records and technical information. Our servers keep a security and privacy log of events such as a Follower’s reads of a record (which record, and when, never which days), refused requests, device approvals and removals, deletions, and changes our staff make to key tables. It is designed to contain no health content, and an account can read its own recent events. When a request is refused, a shortened form of the IP address it came from is recorded in that log. We use IP addresses only for rate limiting and security. Our hosting provider also keeps short-lived technical logs of requests to our servers, which can include IP addresses and browser or app details. Our servers are designed not to write the contents of requests and responses to logs.

h. Information kept in your browser. The Mirri Cloud website keeps some information in your own browser: your browser’s key and sign-in session, which by default stay until you choose to forget the browser, with a fresh sign-in every 90 days or at another interval you choose between 30 and 180 days; in guest mode, for a shared or borrowed computer, the key and session are kept only for that tab and are removed when you close it, sign out, or leave it unused for 12 hours (or a period you choose between 5 minutes and 24 hours); and a few settings, such as the theme. Keys that open entries are held only in memory while a page is open. The Mirri Cloud website’s own code does not set cookies; see Section 7 for a security cookie Cloudflare may use.

i. Visual Share. When you receive a Visual Share (called Offline Sharing in MIRRI One), the days arrive through your browser’s camera from the sharer’s phone screen and are opened in that browser tab’s memory. Nothing about a Visual Share is sent to us, and the days are gone when you end the Visual Share, reload the page, or close the tab.

j. Requests you make. Deletion, account-closure, and privacy requests, with their times.

5. How We Use Information

We use information to: provide Mirri Cloud; sign you in; keep records in sync between your devices; deliver sealed entries to the devices and Followers you approve; send the notices described in Section 4(f); secure Mirri Cloud and investigate misuse; carry out deletion and other requests; and comply with law.

We do not use your information for advertising or data mining, and we do not sell it. We cannot use the content of your entries for any purpose, because we cannot open them, and we do not use routing information to draw conclusions about anyone’s health.

6. Who Can Read Your Entries

• You, on the phones and browsers you have approved.
• Followers you choose, on the devices they use, for the kinds of information you allow each of them. You confirm each Follower in MIRRI One and can change or end their access at any time. Ending a Follower’s access stops their reads; it cannot recall what they have already opened. MIRRI One keeps a short-term copy, for up to 72 hours, of a followed person’s data on each Follower’s phone.
• Someone you show your days to by Visual Share, in the browser tab that receives them, while that tab stays open.
• Not Mirri. Mirri Cloud is designed so that we cannot open your entries.

People you share with are chosen by you and are not vetted, controlled, or supervised by Mirri. What they do with information they have opened is their responsibility under the Mirri Cloud Terms of Service.

7. Service Providers

We use a small number of service providers to run Mirri Cloud. They process information on our behalf under contracts that require them to protect it at least as well as this Policy does and to use it only to provide services to us. We do not share personal information with third parties for their own marketing.

• Supabase, on Amazon Web Services in Ohio, United States, hosts our database, sign-in system, and server functions. It holds the information described in Section 4(a) to (g) and (j), with entries only in sealed form.
• Amazon Web Services (Simple Email Service) sends sign-in codes by email. It receives your email address and the code, and no health information.
• Apple (Apple Push Notification service) and Google (Firebase Cloud Messaging) deliver our notices to MIRRI One. They receive a push token and a notice that carries no health information.
• Cloudflare delivers the Mirri Cloud website’s pages and runs our domain’s name service. It handles ordinary requests for the website’s pages, including the IP address and browser details that come with them, and may use a strictly necessary security cookie when it checks a visit for automated traffic. Cloudflare also provides the network in front of our hosting provider, so it carries every request to our servers, including sealed entries, routing information, and sign-in codes; it has no key that opens entries.

8. No Sale, No Advertising, No Tracking

We do not sell personal information or health information, and we do not share it for cross-context behavioral advertising, as those terms are defined by applicable law. The Mirri Cloud website’s own code includes no analytics, advertising, or session-recording tools, and it loads no scripts or fonts from other companies. Cloudflare adds a small script to the pages it delivers to check for automated traffic; the website’s security settings stop it from running. We honor the Global Privacy Control and other recognized opt-out preference signals where required by law. We do not allow third parties to collect personal information about your online activities over time and across different websites or online services through Mirri Cloud, and because Mirri Cloud does no such tracking there is nothing for a browser’s “Do Not Track” signal to stop. We do not collect, use, or sell personal information from Mirri Cloud to train large language models.

9. Data Retention and Deletion

We keep information only as long as needed to provide Mirri Cloud and as required for legal, security, and record-keeping purposes.

• Sealed entries and their routing information are kept while the record exists. When you delete an entry in MIRRI One, Mirri Cloud records the deletion and the entry no longer appears to you or your Followers; its sealed copy, which we cannot open, is removed when the record is deleted.
• A record you delete is deleted 24 hours after you ask, unless you cancel from any signed-in device before then. Deletion destroys the record’s keys and removes its entries, devices, and Followers’ access. Copies in our hosting provider’s routine backups are not removed at that moment: the entries in them stay sealed, and the backups, with the routing information, display names, and email addresses they hold, expire within 30 days.
• When you close your account, closing runs 24 hours after you ask, or at once if you choose to delete now. Records that only you hold are deleted as described above; a record that another account also holds is released to that account; your pairings end; and your sign-in account, with its email address, is erased within about an hour; entries about you in our sign-in system’s log can remain as security records.
• Devices are kept until you or your phone removes them. A device that was enrolled but never used for 7 days, or not seen for 180 days when your record has a Recovery Code, is removed the next time your devices are checked; a removed device can no longer read the record.
• Notice and wake-up records are kept for no more than 30 days (except the most recent one for each record), and undelivered notices expire after 3 days.
• Security records are kept for as long as needed to secure Mirri Cloud, investigate misuse, and show that requests were carried out. After a deletion, we keep a record that it was requested and carried out, with its times, and the identifiers needed to show it, such as the closed account’s identifier and the deleted record’s display name and dates; none of it includes the contents of any entry.
• Rate-limit records, which can include an IP address, are deleted after 48 hours.
• Our hosting provider’s technical request logs are kept for a short period, no longer than 90 days.
• Visual Shares are never received by us, so we keep nothing from them.

Starting over. If you lose every device that can open your record and your Recovery Code, no one can open your entries, including us. Start Over in MIRRI One then deletes the unreadable entries, keys, devices, and Follower access at once, and your record begins again on your phone.

How to delete. In MIRRI One, open the Menu, then Mirri Cloud, then Settings, then Delete & close account. Or go to cloud.mirridiabetes.com/delete-my-data and sign in with a code sent to your email address. The deletion page stays available even if we pause the rest of the Mirri Cloud website.

What deletion cannot do. Deletion cannot recall information that a Follower has already opened on their own device, including the short-term copy MIRRI One keeps for a person someone follows, or anything a Follower or the recipient of a Visual Share has saved, written down, or photographed.

10. Security

We use administrative, technical, and physical safeguards designed to protect information, including sealing entries on your phone so that our servers cannot open them; keeping health tables out of reach of the database’s public interface; access controls on every table; limits on how often each account can call each function; a log of changes our staff make to key tables; and keeping the contents of requests out of our logs. These safeguards are designed to protect information but are not a guarantee; no application, server, or transmission method is 100% secure, and we do not warrant that our safeguards will prevent every incident.

11. Data Breach Notification

If a breach of the security of health information occurs — including any acquisition, access, use, or disclosure of information without authorization — we will notify affected individuals and applicable authorities (including the Federal Trade Commission, prominent media where required, and applicable state authorities such as the Indiana Attorney General), without unreasonable delay and no later than 60 days after discovery, as required by law, including the FTC Health Breach Notification Rule and applicable state breach-notification and consumer-health-privacy laws. Our notice will describe, to the extent required, what happened and when, the categories of information involved, steps you can take, what we are doing in response, and how to contact us.

12. Your Privacy Rights and Choices

Your choices. In MIRRI One you can turn Mirri Cloud on, choose your Followers and what each of them may read, end a Follower’s access, remove a device, delete a record, and close your account. On the Mirri Cloud website you can stop following a record, use guest mode, forget the browser, and delete your data.

Your rights. Depending on where you live, you may have the right to: confirm whether we process your information and access it; correct it; delete it; obtain a portable copy; withdraw consent to the processing of your health information; opt out of any sale, sharing for targeted advertising, or certain profiling; limit the use of sensitive personal information; and appeal a decision we make about your request. We do not discriminate against you for exercising these rights.

Entries we cannot open. Because we cannot open your entries, we cannot give you a readable copy of them. You can read them on your own approved devices, in MIRRI One and on the Mirri Cloud website, and we can give you the other information we hold about you.

How to exercise them. Contact us at support@mirridiabetes.com, or delete your data as described in Section 9. We will confirm receipt within 10 days and respond within 45 days (extendable once by an additional 45 days with notice). We take reasonable steps to verify your identity before acting, and we accept requests from authorized agents with proof of authorization. If we deny your request, you may appeal by replying to our decision or contacting support@mirridiabetes.com; if your appeal is denied, you may contact your state Attorney General.

State privacy rights. Residents of Washington, Nevada, Connecticut, California, Virginia, Texas, Indiana, and other states should also read our U.S. State Health Privacy Notice, which gives additional disclosures and rights for health information in those and other states, and which we apply to everyone in the United States.

13. Children and Teens

Mirri Cloud is not directed to children under 13, and a person under 13 may not create a Mirri Cloud account or record. MIRRI One asks for your birth year before you set up Mirri Cloud and keeps that year on your device: if you are 13 to 17, it shows a notice for you and your parent or guardian before setup continues, and if you are under 13, it stops setup. Mirri Cloud does not create or hold records that a parent or guardian keeps for a child.

If you are under 18 (or the age of majority where you live), use Mirri Cloud only with the permission of your parent or legal guardian. We do not knowingly collect personal information from a child under 13; if we learn that we have, we will delete it. If you believe a child’s information has reached Mirri Cloud, contact us at support@mirridiabetes.com and we will address it.

14. Consumer Health Data

We treat the health information in Mirri Cloud, and the routing information and record details that relate to it, as “consumer health data” under laws such as the Washington My Health My Data Act and similar state laws. We do not sell consumer health data, we do not use it for advertising, and we do not use geofencing. For the full disclosures, see the Mirri Cloud Consumer Health Data Privacy Policy, which we link from our homepage and from the Mirri Cloud website.

15. Research

Mirri Cloud is a tool for research and data analysis by the people who use it. Mirri does not use the information in Mirri Cloud for its own research. If Mirri ever invites you to share your record for a study, it will ask for your separate, explicit permission first. If you share your record with a researcher, they are a Follower like any other: you choose what they may read, and you can end their access at any time. Their research is theirs, not Mirri’s, and Mirri does not oversee it.

16. International Users

Mirri Cloud is intended for use in the United States, and we operate it and store information in the United States. We do not offer Mirri Cloud to individuals in the European Economic Area or the United Kingdom. If you use Mirri Cloud from outside the United States, you understand that information will be processed in the United States.

17. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will revise the “Last Updated” date and, for material changes, provide notice as required by law (for example, in MIRRI One, on the Mirri Cloud website, or by email). If a change materially affects how we collect, use, or share health information, we will obtain any consent required by law before it applies to you.

18. Legal Process and Government Requests

Legal process and government requests. We disclose information only when valid legal process (such as a subpoena, court order, or search warrant) requires it, or when the law otherwise requires us to. We cannot produce the contents of your entries, because we hold no key that opens them. We review every request for scope and validity, we object to requests that are overbroad or that seek more than the law requires, and we provide only what the request lawfully requires. Unless we are legally prohibited from doing so, we tell you about a request for your information before we respond, so that you can object. We do not voluntarily disclose information to any government body, and we treat requests concerning reproductive or sexual health exactly as we treat every other request. If we receive a request, we record it in our security log.

19. Contact Us

If you have questions about this Privacy Policy or our privacy practices, or to exercise your rights, contact us at:

Mirri Diabetes LLC

300 Main St., Ste. 900

Lafayette, IN 47901, United States

support@mirridiabetes.com