Privacy Policy

Last Updated: October 26, 2026

Version 3.1

1. Introduction

Mirri Diabetes LLC (“Mirri,” “we,” “us,” or “our”) develops and operates MIRRI One, a diabetes and metabolic health management app for Apple iOS and Android, together with related services (the “App”). This Privacy Policy explains what information the App handles, what stays on your device, and what happens when you use the App’s two optional ways to share: Mirri Cloud, which keeps your record (shown in the App as your data) in sync between your devices and lets the people you choose follow it, and Offline Sharing, which shows your data from your screen to another device in person.

This Privacy Policy replaces all prior versions. The App offers Mirri Cloud, an optional, opt-in service that, when you turn it on, seals your health information on your device and uploads it to our servers in that sealed form, so that it stays in sync between your devices and can be read by the Followers you choose. Mirri Cloud is designed so that we hold no key that can open it. Nothing is uploaded to our servers until you turn Mirri Cloud on. If you do not turn it on, the App keeps your health information on your device as described below.

Please read this Privacy Policy together with our Terms of Service. If you use Mirri Cloud, the Mirri Cloud Privacy Policy describes it in full.

2. About This Policy; Our Role; HIPAA

The App is a consumer app intended to help you record, understand, and — at your option — share diabetes- and metabolic-health-related information (covering type 1 diabetes, type 2 diabetes, and general metabolic health) (“health information” or “Health Data”). Some users refer to this as “personal health information” or “PHI”; we use those terms descriptively only.

Mirri is a consumer app and is not a HIPAA covered entity or business associate, and HIPAA does not govern the App. We provide the App to you as an individual. If you choose to share information with a healthcare provider, you do so as an individual directing the disclosure of your own information; we do not act on behalf of, or under contract with, any provider.

Your health information is sensitive, and we handle it 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 to you.

3. Consent

Where required by law, we obtain your affirmative, opt-in consent before we collect or process your health information. Turning on Mirri Cloud is a separate choice, made in the App before any of your health information is uploaded, on a screen titled “Turn on Mirri Cloud.” That screen states, in labeled lines, what the App will send, where it goes, why, who can read it, and how to change your mind, and links the Mirri Cloud Terms of Service, Privacy Policy, and Consumer Health Data Privacy Policy; tapping “Agree and turn on” is your consent. The App records the version and time of your consent on your device and sends our servers a consent record that contains no health information. Sharing your record with each Follower is a further, separate choice that you make when you confirm that Follower on a screen where every kind of information is off until you choose it (Section 6). These consents are requested through clear choices in the App, each with its own screen, and do not rest on your acceptance of our Terms of Service; you can withdraw your consent at any time (see Section 12). Withdrawing consent stops future collection or sharing that depended on it, and we will act on your withdrawal as described in Sections 6 and 11.

4. Information We Handle

a. Health information from your device’s health platform. With your permission, and only for the types you authorize, the App reads health data from your device’s health platform. From Apple Health (HealthKit) on iOS: blood glucose; insulin delivery; carbohydrates, dietary energy, protein, fats, sugar, fiber, sodium, potassium, and cholesterol; alcohol and caffeine; steps, distance, flights climbed, exercise time, active energy, and workouts; heart rate, resting heart rate, heart-rate variability, and respiratory rate; VO2 max, body temperature, body mass, and body fat percentage; sleep; mindful sessions; and menstrual flow and spotting. From Android Health Connect: blood glucose, heart rate, exercise, active calories burned, steps, sleep, menstruation, and intermenstrual bleeding. With your permission, the App writes insulin doses, carbohydrates, and glucose readings you import to Apple Health, and nutrition to Health Connect. You can change or revoke these permissions at any time in the Apple Health app (iOS) or in Android Health Connect or your device settings (Android).

b. Information you log. You can enter information such as glucose values, insulin doses, medications, meals, foods and carbohydrates, physical activity, supplies, symptoms, notes, and photos of meals. You can also ask Iris, the App’s assistant, questions; Iris answers on your device.

c. Account information. To use Mirri Cloud, you log in with your email address and a one-time code we send to it; if there is no account for that address, the code creates one (and, if you give one, a display name). The App keeps your record’s name only in sealed form, which is designed so that our servers cannot read it. Each Follower uses their own Mirri Cloud account; you start sharing by scanning the code their screen shows or, if you are apart, by sending them a single-use link, so we do not need their contact details from you. You give each online connection a name, which the App keeps only in sealed form, and a Follower may give it their own nickname, which stays on their device.

d. Routing and technical information. When you use Mirri Cloud, our servers can read “routing information” needed to store and deliver your sealed entries: which record an entry belongs to; a slot number, one of sixteen that your phone assigns to your kinds of information at random and keeps only in sealed form, so that it does not tell us the kind; the two-week period the entry falls in; its size, rounded up to one of five fixed sizes; the version of your keys it was sealed under; the device that wrote it; and when we received it. The values you recorded, the kind of information, the time it happened, your time zone, and what you changed or deleted are sealed with the entry. Our servers can also see which account holds your record and its email address; your devices, with their public keys and a platform word such as “iPhone” or “Android”; who follows your record, and since when; how many entries arrive, when, and in which slots, which can show a pattern of use; when your record’s keys change, which happens when you change or end a Follower’s access; which two-week periods have entries; your devices’ push tokens; your deletion, closure, and consent records; and a security log of who read your record and when, which contains no health content. Apple and Google, which deliver our wake-ups, can see when each one is sent to your device. We use IP addresses only for rate limiting and security, and we do not use them to track your location. We may also receive limited technical and diagnostic information that Apple or Google make available to us through their standard app-store and developer tools, such as crash reports and app-performance figures. The App itself includes no analytics, advertising, or crash-reporting software. On Android, Google’s ML Kit libraries, which the App runs on your device to scan barcodes and read food labels and photos, may send Google information about how those libraries perform.

Background refresh pings. The App has a “Background refresh pings” switch for Mirri Cloud, which is off unless you turn it on (the switch is shown only when the App’s glucose features are on). While it is on, your phone marks its glucose uploads, and our servers use those marks to send a silent wake-up to your Followers’ phones at your sensor’s cadence, which your phone declares, so that their view stays fresh, and to ask a Live Activity that shows your readings to redraw. Our servers then learn which slot paces the wake-ups and that cadence, never a value. When you turn the switch off, your phone marks no upload and declares no cadence, and our servers pace no wake-ups for your record.

e. Age. Before you sign in to Mirri Cloud or give an email address, the App asks for your birth year. The year stays on your device and is not sent to us.

5. How Your Information Is Stored

On your device (default). By default, the health information you log and the health-platform data you authorize remain on your device. If you never turn on Mirri Cloud, your health information is not uploaded to our servers.

On our servers (only when you turn on Mirri Cloud). When you turn on Mirri Cloud, the App seals your health information on your device and uploads it to our servers in that sealed form, as described in Sections 6 and 7. It uploads the kinds of information it syncs whether or not anyone follows your record yet; you choose which kinds each Follower may read. Your notes, your photos, and your conversations with Iris are not uploaded. Your cycle and other reproductive-health information is sealed on your device like every other kind and uploaded in that sealed form; a Follower receives it only if you turn on the Cycle category for that Follower, which is off by default and asks for its own confirmation.

6. Sharing Your Health Information

Sharing is off by default and is entirely opt-in. You decide whether to share, what to share, and with whom, and you provide separate opt-in consent (Section 3) before sharing begins. If you do not share, this Section does not apply to you.

Mirri Cloud. When Mirri Cloud is on, you can let Followers read your record. A Follower is a person with their own Mirri Cloud account, such as a family member, a caregiver, or someone helping you understand your data, who reads your record in the App or on the Mirri Cloud website. You start sharing in one of two ways: if you are together, the person who will receive shows a code on their screen (in the App, or at cloud.mirridiabetes.com) and you scan it with the App, name the connection, and choose what they may read; if you are apart, you send them a link, they open it and tap “Follow,” and you then name the connection and choose what they may read. You confirm each Follower, choose which kinds of information each of them may read, and can change or end their access at any time in the App. A Follower can read the earlier entries of each kind you allow, as well as new ones, not only entries made after you start sharing. Cycle and other reproductive-health information is sealed like every other kind, and a Follower receives it only if you turn on the Cycle category for that Follower, which is off by default and asks for its own confirmation; Offline Sharing can also show it, in person, only when you choose its Cycle option. You confirm each Follower on a screen where every kind of information is off until you choose it, which names the device or account you are authorizing as it appears on the screen, states which kinds they will be able to read (the kinds you tick) so that they can follow your data, and says that this lasts until you end it; you confirm by tapping “Start sharing,” and that tap is recorded as your signature on that authorization, and the App keeps a sealed copy of what you granted that only your own devices can open. Every Follower’s devices receive your record’s sealed entries and can open only the kinds you chose for them. When someone opens your link to follow you, the App first tells them that they will read what you choose to show them, that their phone keeps a copy for up to 72 hours, that they should treat it as yours and not share it on, and that you can stop the sharing at any time. On a Follower’s phone, the App can 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.

Offline Sharing. Offline Sharing shows the days and kinds of information you choose, sealed, from your screen to another device in person — for example, a browser on the Mirri Cloud website or another phone — through that device’s camera. It does not use our servers, and nothing about it is sent to us. The receiving screen shows a one-time code first, and the App seals your days to that code, which is designed so that people who see or film the screens cannot read them.

Who you share with. Followers and the people you show your days to are chosen by you and are not vetted, controlled, or supervised by Mirri.

Ending sharing. When you end a Follower’s access, they can no longer read your record. Information a Follower has already opened — including the short-term copy, for up to 72 hours, that the App keeps of a followed person’s data on a Follower’s phone — and anything a Follower or the person you showed your days to has saved, written down, or photographed cannot be recalled, deleted, or controlled by us, and remains subject to that person’s own practices.

Not an alert system. As explained in our Terms of Service, Mirri Cloud and Offline Sharing are not a medical alert, monitoring, or emergency-notification system, and information may be delayed, incomplete, or undelivered. Do not rely on them for urgent or safety-critical purposes.

We do not sell your health information, and we do not use it for advertising (see Section 14).

7. How Mirri Cloud Handles Your Information

When you turn on Mirri Cloud, we handle your health information as follows:

• Sealed on your device. The App seals each entry on your device before it is uploaded. Our servers store the sealed entry and are designed to hold no key that can open it, and Mirri Cloud is designed so that neither our staff nor our service providers have such a key. Your record’s keys stay on your devices, and copies of them are stored only in forms that your devices or your Recovery Code can open. A web browser or other device you add can read your record only after one of your phones approves it (for a browser, by scanning the code the browser shows), and a new phone needs your Recovery Code, which only you hold. On iPhone, the App also saves your Recovery Code in your iCloud Keychain, if iCloud Keychain is on, unless you turn that off on the Recovery Code screen, so a new iPhone on the same Apple Account can open your data without you typing it, and anyone who can sign in to your Apple Account on a device that knows your passcode could use it. We are designed never to hold your Recovery Code or any key that opens your data. If you remove a lost phone, it is signed out of Mirri Cloud and our servers refuse its requests, and the phone you remove it with changes the record’s data key so that the lost phone cannot open entries made afterwards; it does not undo what was already on that phone. Your phones are designed to refuse a key from our servers that does not match what they already hold. Your cycle and other reproductive-health information is sealed the same way as every other kind. No health information leaves your device except in sealed form; what our servers read is the routing information listed in Section 4(d) and nothing else.
• Opened only on approved devices. Mirri Cloud is designed so that entries are opened only on your own devices and on the devices of the Followers you approve, never on our servers.
• What our servers can read. Our servers can read the routing information and the other details described in Section 4(d). Routing information is designed so that our servers cannot tell what you recorded, which kinds of information you record (including which entries are cycle entries, because the slot number is assigned at random for each record), when within a two-week period the things you recorded happened, or what you later changed or deleted; they can see how many sealed entries arrive, when, and in each slot, and, while background refresh pings are on, which slot paces them.
• If you lose your keys. If you lose every device that can open your record and your Recovery Code, no one can open your entries, including us.
• Records from before this version. Our servers cannot move entries into the new sealed form, because they cannot open them, so on October 24, 2026 we removed every entry Mirri Cloud held, with its sharing keys, and kept accounts, records, devices, and Followers. The first time you open the version of the App that seals routing information, your phone re-uploads your record from the history it holds and shares again with each Follower the categories you had chosen; a Follower whose choices your phone cannot carry across is marked for you to share with again. Our hosting provider’s routine backups from before that date, which hold the earlier routing information, expire within 30 days of it. The Mirri Cloud Privacy Policy, Section 9, describes this in full.

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. See Section 9 and the Mirri Cloud Privacy Policy.

8. Platform Health Data (Apple HealthKit and Android Health Connect)

If you grant the App access to your device’s health platform, we handle that data in accordance with the platform’s requirements and this Policy:

• We access platform health data only with your permission and only for the categories you authorize.
• We use it solely to provide the health-management features you request and, if you turn it on, Mirri Cloud.
• We do not use platform health data for advertising, marketing, or data-mining purposes, and we do not sell it.
• We do not share it with third parties except as you direct through Mirri Cloud, Offline Sharing, or the connections and voice assistants you choose to use (Section 15), or with service providers who process it on our behalf to operate the App.
• We do not use it for any research or other secondary purpose except with your separate, explicit permission and only as the platform permits.
• We handle Apple HealthKit data in accordance with Apple’s requirements, and Android Health Connect data in accordance with Google’s Health Connect permissions and applicable data-use requirements.
• You can revoke the App’s access at any time in the Apple Health app (iOS) or in Android Health Connect or your device settings (Android).

9. Security

We use administrative, technical, and physical safeguards designed to protect your information, including sealing health information on your device before Mirri Cloud uploads it, encryption in transit, access controls, and monitoring. These safeguards are designed to protect your 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.

10. Data Breach Notification

If a breach of the security of your health information occurs — including any acquisition, access, use, or disclosure of your information without your authorization — we will notify affected individuals without unreasonable delay and no later than 60 days after discovery, and we will notify the Federal Trade Commission, prominent media (where required by the number of affected residents), and applicable state authorities (including the Indiana Attorney General), 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, the name of any third party that acquired the information (if known), steps you can take, what we are doing in response, and how to contact us.

11. Data Retention and Deletion

We retain your information only for as long as needed to provide the App and the features you use, and as required for legal, security, and record-keeping purposes.

• Information stored on your device remains until you delete it or uninstall the App.
• Sealed entries in Mirri Cloud are kept while your record exists. When you delete your record, the deletion runs 24 hours after you ask (you can cancel it until then; deleting a single record has no “at once” option), destroys the record’s keys, and removes its entries and Followers’ access; copies in our hosting provider’s routine backups keep the entries sealed and expire, with everything else they hold, within 30 days.
• When you close your Mirri Cloud account, closing runs 24 hours after you ask, and you can withdraw it until then (after you ask, the App asks you to log in again and then offers “Delete now,” which closes your account at once when you type the word DELETE, and at cloud.mirridiabetes.com you can also close your account at once, after you log in again; closing at once cannot be withdrawn); your sign-in account, with its email address, its sessions, and its sign-in log, is erased within about an hour after closing runs.
• After a deletion, we keep a record that it was requested and carried out, with its times and the identifiers needed to show it; it contains no health content, no record name, and nothing about what kinds of information the record held. The security log is kept for as long as needed to secure the service, investigate misuse, and show that requests were carried out; a record of a read in it says which record, when, and how many entries, never which days. Consent records (that you turned Mirri Cloud on, accepted a version of these documents, or accepted a Follower relationship, with the version, platform, and time) are kept with your account and, after it is closed, with the closure record. Undelivered wake-ups expire after 3 days, delivered ones are deleted after 7 days, and wake-up records are kept no more than 30 days; rate-limit records are deleted after 48 hours; devices that were never used are removed after 7 days, and devices not seen for 180 days are removed when your record has a Recovery Code.
• To delete your Mirri Cloud data, open the Menu in the App, then Mirri Cloud, then Settings, then Delete & close account, or go to cloud.mirridiabetes.com/delete-my-data. The Mirri Cloud Privacy Policy describes retention and deletion in full.
• Information a Follower has already opened, or that someone you showed your days to has kept, cannot be recalled.

12. Your Privacy Rights and Choices

Managing the App. You can control health-platform permissions in the Apple Health app (iOS) or in Android Health Connect or your device settings (Android); turn on Mirri Cloud; choose and remove Followers and what each may read; turn background refresh pings on or off; delete your Mirri Cloud record or close your account; choose what to show by Offline Sharing; and delete information you have logged.

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 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. Because Mirri Cloud is designed so that we cannot open your sealed entries, we cannot give you a readable copy of them; you can read them in the App and on the Mirri Cloud website on your own devices, and we can give you the other information we hold about you, including the list of third parties described in the Consumer Health Data Privacy Policy.

How to exercise them. Contact us at support@mirridiabetes.com, or delete your Mirri Cloud data as described in Section 11. 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.

Opt-out preference signals. We honor the Global Privacy Control (GPC) and other recognized opt-out preference signals where required by law.

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. Consumer Health Data (Washington My Health My Data Act and Similar Laws)

This Section provides the disclosures required for “consumer health data” under the Washington My Health My Data Act and similar state laws, and applies to the consumers those laws protect. We also publish these disclosures as a standalone Consumer Health Data Privacy Policy, which we link from our homepage and within the App.

• Categories of consumer health data we collect: the health information you log and the health-platform categories you authorize (such as glucose, insulin, medications, meals, foods and carbohydrates, activity, sleep, and cycle information), and information about your health conditions and care that you choose to record or share. If you turn on Mirri Cloud, we hold these in sealed form, together with routing information about them.
• Sources: you (information you enter); your device’s health platform (Apple HealthKit or Android Health Connect, with your permission); and your use of the App.
• Purposes: to provide the App’s diabetes- and metabolic-health-management features and, if you turn on Mirri Cloud, to keep your record in sync and make it available to the Followers you choose.
• Categories of third parties and affiliates with whom we may share it: the Followers you choose through Mirri Cloud; and our service providers (such as our cloud hosting provider) who process data on our behalf under contract. We do not share consumer health data with any other third parties or affiliates, and we do not sell it.
• Consent and authorization: we collect consumer health data with your consent and share it only at your direction; we do not sell consumer health data, and we would not do so without first obtaining a separate, valid written authorization from you containing all elements the law requires.
• Your rights: to confirm whether we process your consumer health data, to access it, to withdraw consent, and to have it deleted (and to have us notify our service providers to delete it), subject to applicable law. To exercise these rights or to appeal, contact support@mirridiabetes.com (see Section 12).
• No geofencing: we do not use geofencing to identify or track consumers near, or to collect consumer health data or send notifications or advertisements based on proximity to, any health-care facility.

14. Do Not Sell or Share; No Advertising

We do not sell your health information, and we do not share it for cross-context behavioral advertising, as those terms are defined by applicable law. We do not use your health information for advertising or data mining, and we do not use third-party analytics or advertising software development kits (SDKs). Aside from limited information that Apple or Google may automatically collect as the app-store and platform providers (which is governed by their own privacy policies), we do not collect information about you beyond what you provide to us or authorize, or as described in Section 4(d). We do not allow third parties to collect personal information about your online activities over time and across different websites or online services through the App, other than what the connections you choose receive (Section 15), and because the App 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 the App to train large language models.

15. Service Providers and Connections You Choose

Service providers. We use a small number of service providers to operate Mirri Cloud. They process information on our behalf under contracts requiring them to protect it at least as well as this Policy does and to use it only to provide services to us: Supabase, which hosts our database and sign-in system on Amazon Web Services in Ohio, United States, and holds your entries only in sealed form; Resend, Inc., which sends your sign-in codes and account emails and delivers them through Amazon Web Services’ email infrastructure; and Apple (Apple Push Notification service) and Google (Firebase Cloud Messaging), which deliver notices to the App that carry no health information; and Cloudflare, which carries requests to our servers, including sealed entries and routing information, as the network in front of our hosting provider. On Android, Google’s messaging service may create an installation identifier for the App. We do not sell your personal information, and we do not share it with third parties for their own marketing.

Connections you choose. Some App features connect your device directly to another company’s service, only when you use them. That company receives what the feature sends, under its own privacy policy, and we do not receive it:

• Food lookups. When you scan a barcode or search for a food, the barcode or search words go to Open Food Facts, a public food database, and to any other food database you add with your own key.
• Photo analysis. Meal photos are analyzed on your device. If you turn on cloud analysis and add your own Anthropic API key, a photo you choose to analyze is sent from your device directly to Anthropic under your own account with Anthropic.
• Dictation. When you dictate, your device’s speech recognition (Apple’s on iOS, Google’s on Android) converts your words to text, on your device where your device supports it and otherwise on Apple’s or Google’s servers.
• Voice assistants and shortcuts. If you use Siri, Shortcuts, or (on Android) your phone’s assistant with the App’s actions, the App gives that assistant the information the action asks for, such as your recent doses, carbohydrates, or glucose, or those of a person you follow; the assistant’s provider handles it under its own policy.

16. Children and Teens

The App is a general-audience service and is not directed to children under 13. You must be at least 13 years old to use the App. If you are under 18 (or the age of majority where you live), use the App and Mirri Cloud only with the permission of your parent or legal guardian. Subscriptions and in-app purchases are offered to adults; if you are under 18, your parent or guardian buys any subscription or purchase for you through the Apple App Store or Google Play.

Before you sign in to Mirri Cloud or give an email address, MIRRI One asks for your birth year and keeps that year on your device: if you are 13 to 17, it asks you to confirm that a parent or guardian knows you are using Mirri Cloud and agrees before you continue, and if you are under 13, it does not let you sign in or set up Mirri Cloud, no account or record is made, and nothing is uploaded. The App does not currently offer accounts, records, or profiles that a parent or guardian keeps for a child.

We do not knowingly collect personal information from a child under 13. If we learn that a child under 13 has created a Mirri Cloud account, we will delete that account and the associated information. If you believe a child’s information has been provided to us improperly, contact us at support@mirridiabetes.com and we will address it.

17. International Users

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

18. 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 additional notice as required by law (for example, in the App or by email). If a change materially affects how we collect, use, or share your health information, we will obtain your fresh, affirmative opt-in consent in the App before it applies to you, rather than relying on your continued use.

19. 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 Mirri Cloud is designed so that we hold no key that opens them. Our servers are designed not to hold which kinds of information you record, when within a two-week period the things you recorded happened, your time zone, or what you changed or deleted, so we cannot produce those either; what we could be required to produce is limited to the information our servers can read, described in Section 4(d). 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; Cycle and other reproductive-health information is held, like every other kind, only in sealed form that we cannot open, and our servers cannot tell which entries are cycle entries, so we have no readable reproductive-health information to produce. We keep a record of each request we receive and how we answered it.

20. 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