Stash Terms of Service

Effective date: October 2, 2026

1. Your agreement with Stash

These Terms govern the Stash iOS and Android apps and their associated community services (the “Service”), provided by Stash Diabetes, Inc. (“Stash,” “we,” or “us”). By accepting these Terms or using the Service after they take effect, you agree to them. If you do not agree, do not use the Service.

Stash is built for the logistical side of diabetes: supply management. Our community features help people understand supply availability, product reliability, and reported safety concerns. We aim to collect only information that serves a stated purpose and to explain where it goes.

Our Privacy Policy explains our handling of information. Accepting these Terms does not, by itself, provide consent to processing that requires a separate, specific choice. A contribution license does not waive your privacy rights.

2. Eligibility and authority to contribute

You must be at least 13 to use Stash. If you are below the age of legal adulthood where you live, a parent or legal guardian must authorize your use and accept these Terms on your behalf where required by law.

People making community contributions or subscribing to newsletters must be 16 or older, subject to any additional parental authorization or higher minimum age required by local law. This age requirement concerns the contributor, not necessarily the person whose supplies are managed. A research study may have different eligibility and consent requirements. An age-range answer in your profile is not proof of eligibility or parental permission.

Caregivers may contribute health information about children under 16. If you manage supplies for someone else, you must have appropriate authority both to handle their information and to make the particular community contribution. By choosing a caregiver relationship during onboarding, you tell us that you act in that role; the answer alone does not verify parental responsibility or supply every consent the law may require. You must be authorized to consent for the child for that use, or have the necessary authorization from a parent, legal guardian, or other legally authorized representative, together with any consent required from the child. The separate sensor-sharing choice and any required research, sharing, or commercial-use authorization still apply. Do not submit another person's name, contact details, or other identifying information in a community report.

3. Supply management, not medical care

Stash helps organize supplies, estimate coverage, record use and placement history, plan trips, and display information about recalls and community reports. Its intended purpose is supply management and the limited recordkeeping and comparisons described here. Stash is not intended to diagnose, treat, cure, prevent, or clinically monitor a medical condition, prescribe treatment, recommend doses or placement rotation, or replace professional medical advice. Stash does not provide emergency monitoring or contact emergency services.

Coverage estimates, days remaining, reorder dates, wear summaries, and trip quantities depend on the information and settings available to the app. They can be incomplete or wrong. Verify your actual supplies, packaging, expiration dates, and manufacturer instructions. Discuss treatment decisions with an appropriately qualified healthcare professional. Do not delay necessary care because of information in Stash.

An optional A1C entry is a record you provide for the purposes described in the Privacy Policy; it is not a clinical interpretation, diagnosis, or treatment recommendation.

Sensor Accuracy Test is an experimental comparison of readings you enter manually. Its charts, average error measures, agreement percentages, and error-grid zones compare those entries; they do not clinically validate a sensor, establish that a device or lot is defective or safe, or determine which reading is correct. The meter is also subject to error, and the number, timing, selection, and accuracy of entries affect the result. This is not continuous glucose monitoring, a dosing calculator, a treatment recommendation, or a substitute for device instructions and professional care. Do not use these comparisons to make dosing or treatment decisions.

4. Your records, devices, and backups

No Stash account is required for the consumer app. Your own records are stored on your device, with platform-specific backup and sharing options described in the Privacy Policy. iOS can use Apple's iCloud services. Android does not currently provide equivalent continuous inventory synchronization or automatic iOS–Android synchronization.

You are responsible for securing your device, choosing appropriate sharing recipients, and keeping backups you need. Uninstalling the app does not necessarily delete cloud copies or community contributions, or create a new Community Data ID: iOS can retain the ID through iCloud, and Android can restore it from system backup or device transfer. A manual backup can contain sensitive health information, including sensor readings and tests; choose its destination carefully.

You retain any rights you have in your records and submissions. Stash does not acquire ownership of your private inventory or health history merely because you use the app.

5. License to use Stash and acceptable use

Subject to these Terms and applicable store rules, Stash grants you a limited, personal, nonexclusive, nontransferable license to use the app on devices you own or control for lawful supply management. Any applicable statutory rights, open-source licenses, and Apple Family Sharing or volume-purchase rights remain unaffected.

Do not knowingly submit fabricated or misleading reports; upload unlawful, abusive, or infringing content; impersonate another person; interfere with the Service; bypass access controls; scrape restricted records; or attempt to identify community contributors. Security research and reverse engineering permitted by mandatory law remain permitted. Please report suspected security problems to support@stashdiabetes.com.

6. Community contributions and your choices

The Community Alerts control currently combines recall and lot-notice downloads with contributions that support community safety and supply analysis. Depending on platform, version, and enabled features, contributions can include lot observations, incident reports, wear outcomes, inventory snapshots, reduced supply-use records, profile demographics, optional A1C history, and insurance-type history. Optional sensor tests add the separately authorized readings and summaries described below. Sending a first incident report can also join the ongoing Community program, as explained at that step. Barcode contributions use a separate Send to Stash action.

The Privacy Policy identifies the actual fields, platform differences, defaults, initial historical uploads, recipients, and controls. This is not permission to upload your full backup or to collect other information simply because it might later be useful.

Community records generally omit direct identity fields and instead use a random Community Data ID, also called an Install ID. Your app stores this ID, and Stash receives and stores it with your contributions. We can associate records with the same ID without knowing your name and do not maintain a routine mapping from the ID to your identity. This is pseudonymous data, not a guarantee of legal anonymity. Product serials, dates, region, and health context can make records distinctive; free text may identify you if you include identifying details.

We will intentionally link your community contributions to your identity for research only with your separate, explicit, study-specific consent. If a future study offers this option, you may voluntarily provide your Community Data ID and identifying information through its disclosed enrollment process and authorize that connection. We will not otherwise attempt to identify you from community records or permit a partner to do so. Providing your ID for support, deletion, or another privacy request does not authorize a research link. Section 8.4 explains this optional process.

Contributions should be truthful to the best of your knowledge. Do not include names, addresses, contact details, medical-record numbers, or information you do not have permission to share. We may validate, moderate, exclude, correct, or remove submissions to address errors, abuse, or legal obligations.

6.1 Separate sensor-test consent

Sensor Accuracy Test is off by default and requires both Community membership and its own current consent. Turning the feature on in Settings authorizes sharing eligible completed tests, including the paired meter and sensor glucose readings behind them, with Stash's community backend. There is no separate local-only test mode or Send decision for each completed test in the current feature. The Privacy Policy describes the exact fields, including product/lot details, test start/completion times, summary measures, and each pair's values, day of wear and hour of day. Individual reading notes and exact per-reading timestamps are excluded.

Tests with at least three eligible pairs can be submitted when finished or when the associated sensor is archived. They may include earlier readings for that sensor. Failed uploads may be queued and retried; eligible previously recorded or queued tests can become available for submission after you turn sharing back on. These tests are not limited to the 90-day iOS wear-history backfill window.

Acceptance of these Terms or general Community membership does not grant this sensor permission. A material expansion requires the applicable renewed consent. The October 2, 2026 sensor consent version added paired readings to the earlier summary-only contribution and requires an affirmative renewed choice.

Sensor-test contributions are part of community data for the purposes and safeguards in section 8. Appropriately authorized data can support paid or licensed de-identified aggregate products alongside community reports and wear sessions. Properly de-identified individual records may be used for authorized research under section 8.4. This does not permit selling identifiable or pseudonymous individual readings, exceeding the permissions that apply to a contribution, or using a general Terms acceptance in place of required specific consent. Section 10 explains withdrawal and deletion.

7. Limited permission to use contributions

To the extent you hold intellectual-property rights in information you intentionally contribute, you grant Stash a nonexclusive, worldwide, royalty-free permission to receive, store, reproduce, validate, analyze, and combine it, and to create appropriately de-identified outputs, only for the purposes disclosed when you contributed and lawfully authorized under the Privacy Policy. We may authorize our service providers to perform those activities for us under appropriate restrictions.

This permission supports community safety information, supply availability and reliability analysis, product improvement, and the partnership activities in section 8 when authorized, including secondary clinical research using properly de-identified contributions under section 8.4. It is subject to consent withdrawal, deletion, purpose limitations, applicable law, and any narrower study-specific terms. It is not an irrevocable license to retain or repurpose personal data indefinitely.

If personal data are deleted or processing consent is withdrawn, this license does not authorize continued processing that privacy law otherwise prohibits. Lawfully created outputs that are genuinely anonymous may continue to be used, including under existing licenses, because they can no longer reasonably be linked to a contributor. This exception does not cover records that merely replace your name with an ID, or identifiable free text.

You are not entitled to payment, royalties, ownership in research results, or a share of partnership revenue merely for contributing. Any study compensation or different arrangement must be stated separately before participation. You retain your statutory rights.

8. Research, nonprofit, industry, and manufacturer partnerships

8.1 Permitted purposes and partners

Stash may work with clinical and academic researchers, universities, hospitals and research institutions, diabetes nonprofits and patient organizations, public-health bodies, industry partners, and supply or device manufacturers. Permitted purposes include understanding supply shortages and access barriers; evaluating real-world supply reliability and failure patterns; improving product quality, availability, and safety; informing community education and advocacy; and conducting appropriately authorized health research.

The purpose must benefit diabetes supply management or the diabetes community. Partner status alone does not authorize access to data or expansion of its permitted uses. A commercial partner may also benefit commercially from a permitted project; that does not remove the restrictions below.

8.2 Sale and licensing of aggregate information

Stash may sell, license, or charge for access to aggregate reports, statistics, and analyses that meet applicable legal standards for de-identification or anonymization. Examples include community-level supply availability, incident and wear-session trends, and sensor device/lot performance analyses derived from authorized tests and paired readings. As of October 2, 2026, Stash has not sold community data or reports derived from it; this clause describes future permitted activities. Payment may support Stash's operations and community work. We do not promise that partnership revenue will be donated to charity or paid to contributors.

Paid aggregate products must not disclose identifiable individuals or contributor-level records. They must exclude Community Data IDs, direct identifiers, product serial numbers, identifying free text, and combinations or small groups that could reasonably identify a person. A table labeled “aggregate” is not sufficient by itself: we must assess the output and its reasonably foreseeable uses before release.

We will not sell or license identifiable or pseudonymous individual health or contribution records under these Terms. We will not use a label such as “research fee” or “aggregate license” to bypass laws that classify a transaction as a sale or sharing of personal or consumer health data. If a proposed arrangement would fall within those rules, it will not proceed under this general permission; any legally permissible arrangement would require its own disclosures and legally sufficient authorization first.

8.3 Partner safeguards

Before providing a partner with a nonpublic dataset or licensed report, we will define its permitted purpose and require appropriate contractual safeguards. For de-identified datasets and reports, these include no attempted re-identification; no matching to external records to identify contributors; and no contact with contributors from the data. All partner arrangements require appropriate security and access limits, no unauthorized onward transfer, and retention or deletion requirements appropriate to the material supplied. A separate identity link that you expressly authorize under section 8.4 is limited to that study and its disclosed recipients; it does not permit anyone to reconstruct identities from de-identified datasets or reports. Public statistics remain subject to applicable law and our prohibition on attempted re-identification when using the Service.

Community data must not be used for targeted advertising, advertising audiences, individual sales leads, discriminatory decisions, or individual decisions about insurance, employment, credit, eligibility for treatment, or access to supplies. Manufacturers do not receive private records to identify complainants, administer warranties, or deny replacement requests. Any user-directed replacement or support handoff would require its own clear action and disclosure.

We will disclose the partner, project purpose, categories of information, and whether the arrangement is paid before a new partner program begins. Sponsorship does not establish the accuracy of a finding or imply Stash's endorsement of a product. Financial relationships must be disclosed with sponsored outputs.

8.4 Clinical studies and secondary research

Stash may use contributed data, including A1C history and authorized sensor-test summaries and paired readings, and provide appropriately de-identified research datasets to the partners described in section 8.1, for clinical studies and other health research intended to benefit the diabetes community. This includes secondary research using existing contributions and may include properly de-identified individual records, not only aggregate statistics. The use must remain within the disclosed research purposes, the permissions applicable to the source data, and applicable law. This research pathway does not broaden the separate permission to sell aggregate outputs into a permission to sell individual records.

Before such use or disclosure, Stash and the responsible research institution must document the applicable research and privacy requirements. Where required, the project must obtain Institutional Review Board (IRB), Privacy Board, or other independent ethics review and comply with its conditions. The documentation may instead establish, through the appropriate institutional process, that the activity is exempt or does not constitute human-subjects research. We will not describe every secondary-data study as requiring full IRB approval when the applicable rules provide another pathway.

Research datasets disclosed as de-identified must satisfy an appropriate, documented standard, such as HIPAA Safe Harbor or HIPAA Expert Determination, as applicable to the project, together with any additional protections required by other applicable law. A random Community Data ID alone does not establish that standard. Research partners must comply with the safeguards in section 8.3, including restrictions on re-identification and unauthorized onward disclosure. Applying a HIPAA de-identification method does not itself represent that Stash is a HIPAA covered entity or that every other legal requirement has been satisfied.

A new opt-in for each secondary research project is not required when the applicable law, institutional determination, platform requirements, and permissions already governing the data allow that use without further consent. Where informed consent or a HIPAA authorization is required, it must be obtained unless a legally valid waiver or other applicable exception permits the activity. An IRB determination does not override obligations outside its authority or the earlier commitments addressed in section 8.5.

Research use of existing contributions is distinct from actively recruiting or enrolling you in a study, contacting you, collecting additional study information, linking your identity to clinical records, or intervening in your care. Those activities require an appropriately disclosed study process and the consent, authorization, or other lawful pathway applicable to that activity, subject to our explicit-consent commitment for identity linkage below. A participant-facing study must explain its responsible organizations, purpose, procedures, duration, data handling, risks and benefits, compensation if any, contacts, and withdrawal terms as required. These Terms alone do not enroll you as an active study participant. Declining active participation does not remove access to core supply management.

Optional research identity linkage. If we offer a future study that connects your identity to existing community contributions, the connection will require your voluntary provision of your Community Data ID and identifying information through the study process, together with your separate, explicit, study-specific consent. The study notice must identify who may receive the linked information, which records will be linked, why, how long they will be retained, and how to withdraw consent, including any lawful limits on removing information already used in research. Stash and the named study recipients may make and use only the connection you authorize. We will restrict access to the identity link and keep it separate from de-identified partner datasets. The linked information will be treated as identifiable research information, not anonymous data. Neither acceptance of these Terms, participation in the Community program, disclosure of an ID for support or privacy rights, nor a secondary-research consent waiver substitutes for this explicit choice. Possession of an ID alone is not proof of identity or consent; the study process must appropriately verify the request and record the authorization.

A1C research and future partners. Stash may use contributed A1C history in studies of relationships between supply access, supply disruptions, device failures, recall exposure, insurance coverage, and glycemic outcomes over time. For those purposes, Stash may connect A1C to relevant supply, incident, insurance, and other community records under the same Community Data ID. That internal connection does not authorize identifying the contributor.

Stash may also share appropriately de-identified A1C research datasets and aggregate findings with the academic, clinical, nonprofit, public-health, industry, and manufacturer partners described in section 8.1. Such datasets may include properly de-identified individual A1C records, subject to the permissions applicable to the source data and all research and partner safeguards in this section. Authorized A1C research partners may include commercial organizations. The consent rules above apply, including additional authorization where required and the separate process for active study participation or intentional identity linkage.

The general aggregate-commercialization clause does not remove existing restrictions on selling A1C-derived information. An expanded paid use requires the applicable additional disclosure and authorization, even if the proposed product is described as research. The research permission above does not authorize selling contributor-level records under section 8.2.

8.5 Earlier contributions and continuing research permissions

The research and community-benefit activities described in this section may include contributions made before these Terms take effect. Earlier contributions are not excluded merely because they predate this version. Stash may continue to use them for purposes already authorized under the Terms and privacy disclosures applicable when they were contributed, subject to applicable law and your privacy rights.

Earlier Terms expressly addressed these uses. Sections 6.4 and 6.6 of the Terms dated May 29, 2026, retained in the June 10 and September 17, 2026 versions, described analysis of Community Network contributions and sharing aggregate, non-identifying summaries with manufacturers, researchers, and public-health bodies to improve supply quality or community safety. They also granted Stash a license to use, store, analyze, aggregate, anonymize, and distribute contributions for those stated purposes. Sections 9.5 and 9.6, included from the June 10, 2026 version, provided corresponding purposes and license terms for Lot Observations. Section 21 of the September 17, 2026 Terms expressly described research using optional profile and A1C information to examine supply disruptions, device failures, recall exposure, and glycemic outcomes over time.

Stash may rely on those existing permissions for covered research, community analysis, and partner activities, including clinical research under section 8.4 when it falls within the previously authorized scope. Restating or clarifying an already authorized use in these Terms does not, by itself, require a new contribution or a new consent solely because the data were contributed earlier.

The scope of each earlier permission remains relevant: an authorization for aggregate sharing does not automatically authorize disclosure of individual records, and a research permission does not automatically authorize every commercial use. Any applicable restrictions on particular data, recipients, sale, or other purposes continue to apply, as do withdrawal and deletion rights. If a proposed use goes beyond the applicable prior permission, Stash will obtain any additional authorization required before including those contributions in that use.

9. Recall information, lot notices, and community statistics

An active internet connection through Wi-Fi or cellular data is required to download or refresh recall alerts, manufacturer notices, and community alerts. Without connectivity, Stash cannot retrieve new or updated alerts and notices. Previously downloaded information may remain visible while offline but may be out of date.

Recall notices, manufacturer information, public FDA records, and community reports have different sources and evidentiary value. A community report is not an official recall, a verified defect, proof of causation, or an estimate of risk for all users of a product. Voluntary reporting is subject to bias, incomplete information, differing sample sizes, and reporting errors.

Stash may publish aggregate statistics and limited structured report summaries with identifying fields removed, as described in the Privacy Policy. Some source information is public. No alert list is guaranteed to be complete, current, or delivered on time. Absence of an alert does not establish that a supply is unaffected or safe. Follow official manufacturer and regulator instructions and verify relevant recall information at its source.

A report to Stash is not automatically a report to a manufacturer, healthcare provider, FDA, or another regulator, and does not start a replacement or reimbursement request.

10. Withdrawal and deletion

You can turn Community Alerts off to withdraw permission for further community contributions from that device and stop the associated alert downloads. Leaving Community also withdraws sensor sharing. You can instead turn off Sensor Accuracy Test alone while remaining a Community member; doing so disables that feature but leaves core supply management available. Neither control disables unrelated channels such as analytics, user-directed sharing, barcode lookups, or email you have separately requested. Limited consent-withdrawal and deletion-request records can still be transmitted to carry out your choice.

Withdrawal does not itself erase records already received or recall a network request already transmitted, and a contribution batch already prepared or in flight when you withdraw may still be delivered. Editing or deleting local readings does not automatically correct or delete their server copies.

Use Settings → Data Management → Delete My Community Data to request removal of backend records associated with the Community Data ID submitted by your device, including contributed sensor-test summaries and paired readings, A1C, and insurance history. Processing is manual; “Requested” confirms submission, not completed deletion. The Privacy Policy explains timing, coverage, implementation conditions, exceptions, and alternatives if you cannot access the app.

Deletion does not automatically turn Community Alerts off. Turn it off on each contributing device if you also want uploads to stop. Both platforms can have more than one device contributing under the same ID. New uploads, rejoining, or later barcode contributions can create new records. Deleting community data does not delete your local inventory or health records, Apple private-cloud records, Shared Stash copies, exported files, newsletter subscription, or support correspondence.

11. Sharing and other services

If you enable Shared Stash, disclose a sharing code, export a backup or report, add information to a calendar, or open an external service, you direct that transfer. Shared Stash may include a display name and detailed supply information; it is not anonymous community contribution. Anyone with a valid sharing code may be able to view the snapshot. Revoking access cannot recall copies a recipient has already made.

Apple, Google, hosting providers, TelemetryDeck, email providers, and government reference services have their own applicable terms and privacy practices. We remain responsible for obligations that apply to our selection and use of service providers. We do not endorse an external service merely by linking to it.

12. Availability, pricing, and changes

Stash is currently free. Future optional paid features or subscriptions would require clearly disclosed pricing and an affirmative purchase through the applicable payment flow. These Terms do not authorize a charge.

We may improve, change, suspend, or discontinue features, taking account of applicable law and reasonable user expectations. Where practicable, we will give reasonable notice of a material discontinuation and an opportunity to export local records. We cannot guarantee uninterrupted availability, compatibility with every device, or preservation of records after a device or service failure.

13. Warranties and responsibility

To the extent permitted by law, the Service is provided “as is” and “as available,” without implied warranties of merchantability, fitness for a particular purpose, or noninfringement. We do not promise that forecasts, third-party information, community reports, or research outputs are error-free.

Nothing in these Terms excludes mandatory consumer guarantees or our responsibility for fraud, deliberate misconduct, gross negligence where it cannot be excluded, death or personal injury caused by negligence where liability cannot be excluded, or any other nonexcludable liability.

Subject to those protections, Stash is not responsible for indirect or consequential losses to the extent their exclusion is lawful. Our total liability arising from the Service is limited to the greater of US$100 or the amount you paid Stash for the Service during the preceding 12 months, except where this limit is prohibited or does not apply to the claim under mandatory law. Consumers retain all mandatory remedies available where they live.

14. Ending use, enforcement, and changes to these Terms

You may stop using Stash at any time. Export or delete records and withdraw optional contributions as appropriate before uninstalling. We may restrict access to online features where reasonably necessary to address material misuse, security risks, or legal requirements, with notice where practicable. Restrictions do not remove your data-protection rights.

We will identify the effective date of changes and provide reasonable notice of material changes through the app or another appropriate channel. A change affecting consent-based processing or research does not take effect for that processing until any required fresh consent is obtained. Changes do not retroactively remove accrued rights or override earlier privacy commitments.

Provisions intended to survive termination do so only to the extent needed for their purpose, including lawful use of genuinely anonymous outputs, accrued claims, and mandatory rights. No survival clause overrides a valid withdrawal or deletion obligation.

15. Governing law and disputes

Delaware law governs these Terms, excluding conflict-of-law rules, except that you retain mandatory protections of the law where you habitually reside. Subject to those protections and any mandatory local jurisdiction rights, disputes may be brought in the state or federal courts in New Castle County, Delaware. Nothing requires a consumer to litigate outside their home jurisdiction where local law provides otherwise. These Terms impose no mandatory arbitration or class-action waiver.

If a provision cannot be enforced, the remaining provisions continue to apply to the extent lawful. A failure to enforce a provision is not a waiver. Any assignment by Stash must preserve applicable privacy commitments and your mandatory rights.

16. Apple and Google distribution terms

These Terms are between you and Stash, not Apple or Google. Stash is responsible for the app and for support and applicable product, consumer, and intellectual-property claims. Apple and Google do not undertake support obligations under these Terms.

For the iOS app, the license is limited by the applicable Apple usage rules, including permitted Family Sharing or volume purchasing. If the app fails to conform to an applicable warranty, you may notify Apple; Apple may refund any purchase price paid for the app, and, to the extent permitted by law, has no further warranty obligation. Stash is responsible for handling applicable third-party intellectual-property claims. Apple and its subsidiaries are third-party beneficiaries of the iOS license provisions and may enforce them. You must comply with applicable third-party agreements and export or sanctions laws; you represent that applicable law does not prohibit you from receiving the app.

For the Android app, applicable Google Play terms also govern your use of that store. Neither store's involvement limits rights you have against Stash under applicable law.

17. Contact

Stash Diabetes, Inc.
support@stashdiabetes.com