Stash Consumer Health Data Privacy Policy

Effective Date: November 11, 2026

This Consumer Health Data Privacy Policy supplements the Stash Privacy Policy and applies to consumer health data governed by the Washington My Health My Data Act or Nevada’s consumer health data law, NRS 603A.400 through 603A.550. It explains how Stash Diabetes, Inc. (“Stash,” “we,” “us,” or “our”) collects, uses, shares, and protects consumer health data relating to Washington and Nevada consumers. Where the two laws differ, this policy identifies the state-specific right or deadline.

If this policy conflicts with the general Stash Privacy Policy regarding consumer health data covered by Washington or Nevada law, this policy controls for that data.

1. Overview

Stash is a diabetes supply-management application for iOS and Android. Most supply-management information is stored locally on your device. Stash does not receive local records merely because you enter or store them in the app. If you use Shared Stash, the household’s information is stored on Stash’s servers so that invited household members can access it.

You may separately choose to send specified information to Stash through optional features such as Shared Stash, Community contributions, incident reports, barcode contributions, and Sensor-to-Meter Analysis sharing.

Our key commitments are:

  • (a) Core local supply-management features remain available without optional Community participation.
  • (b) Optional Community collection is off by default and requires an affirmative choice.
  • (c) Consent to collect consumer health data does not automatically authorize Stash to share it with an independent third party.
  • (d) Accepting the Terms of Service does not provide consent to optional consumer health data collection, research sharing, or commercial use.
  • (e) We do not currently sell consumer health data, and we do not currently include Community contributions in licensed commercial reports.
  • (f) We do not knowingly sell or commercially license personal or health information concerning anyone under 18.
  • (g) We do not use consumer health data for targeted advertising.

2. Consumer Health Data We May Collect

Consumer health data includes information that identifies or can reasonably be linked to a consumer and that identifies the consumer’s physical or mental health status. It may also include information from which Stash can infer a consumer’s health status, treatment, or use of health-related products and services.

Depending on the features you use and the choices you make, Stash may collect the following categories:

CategoryExamples
Diabetes and profile informationDiabetes type, relationship to diabetes, treatment regimen, insulin products, use of a pump, continuous glucose monitor manufacturer, age range, sex, and whether the information concerns you or someone in your care
Supply and device informationSupply category, manufacturer, product name, product identifier or GTIN, lot number, serial number, expiration date, quantity, stock status, activation and archive information, wear time, placement-zone label, and pre-soak status
Supply-use and availability informationSupply-use events, inventory snapshots, quantities used or remaining, consumption patterns, coverage estimates, product circulation, shortage information, and supply access information
Incident and health-impact informationReported product issues, incident categories, health-impact categories, wear outcomes, completion status, placement information, and optional incident notes
A1C informationA1C values, whether a value is exact or above or below a reporting limit, entry time, and measurement date when provided
Sensor-to-Meter Analysis informationManually entered paired meter and sensor readings, day of wear, hour of day, comparison-session dates, and calculated summaries such as numerical differences, bias, agreement percentages, and Parkes Error Grid information
Shared Stash household informationHousehold names and settings, member email addresses and roles, adult and child profile labels, birth month and year, age range, optional gender, diabetes type, regimen settings, pump and sensor information, supplies, lot and serial numbers, barcodes, expiration dates, currently worn devices, activation and replacement times, body-placement information, dose and usage history, and reminder assignments
Shared Stash Community and research recordsDevice type, product, lot, serial number, wear duration, how a device ended, device-report details, Sensor-to-Meter readings, age in whole years, week of the event, optional country and state, and a random person code, sent only when a Shared Stash owner aged 18 or older turns on Contribute to Community Reports or an adult sends a report
Insurance informationGeneral insurance or coverage category and the date on which that category was recorded; Stash does not request an insurer name, policy number, member number, claims, or billing records through this feature
Regional informationCountry, state, or another broad region selected in the app; incident-location assistance may use a platform geocoding service, but Stash’s Community records retain only the disclosed broad region
Persistent identifiersCommunity Data ID, contribution and record identifiers, session identifiers, consent versions, and related timestamps
Consent and rights informationRecords of Community, research, or other choices; consent or withdrawal date; policy version; choice screen; platform; app version; deletion requests; and request-processing status
Technical and service informationPlatform, app and operating-system version, contribution times, schema version, error categories, record counts, and security or abuse-prevention information
Health-related inferencesInferences concerning diabetes status, treatment or device use, supply availability, product reliability, possible supply disruptions, or relationships among supply access, insurance coverage, device experiences, and health outcomes

The Community Data ID is a persistent random identifier. Stash does not require a name or account email address to create it, but it allows records associated with the same identifier to be connected over time. Information linked through the Community Data ID is pseudonymous, not anonymous, and may remain consumer health data.

Product serial numbers, precise dates, free-text notes, regional information, and combinations of records may also make information distinctive or reasonably linkable to a person, household, or associated device.

3. Information That Usually Remains on Your Device

The app may store detailed information locally, including inventory, supply-use history, placements, trips, settings, A1C history, insurance history, and manually entered meter and sensor readings.

Stash does not automatically receive the complete local database. Local information is collected by Stash only when an enabled contribution feature transmits the specified fields, when you move a Stash to Shared Stash, or when you otherwise direct the information to Stash, such as through a support request.

Local records may also be processed by Apple, Google, or another provider through operating-system backup, private-cloud synchronization, device transfer, calendar, file export, or another feature you select. Those services operate under their own terms and privacy practices.

4. Sources of Consumer Health Data

We may collect consumer health data from the following sources:

  • (a) You, through information you enter, select, scan, submit, or share;
  • (b) An authorized caregiver, parent, guardian, or other person using Stash on someone else’s behalf;
  • (c) Owners and members who add or update information in a Shared Stash;
  • (d) Your use of Stash, including app-generated events, timestamps, identifiers, calculations, and contribution records;
  • (e) Your device or platform, including app version, operating-system version, device characteristics, and general locale or regional settings;
  • (f) Product packaging and barcode scans, including product identifiers, lot numbers, serial numbers, and user-edited product names;
  • (g) Information you import or restore through a user-directed backup or transfer;
  • (h) Public product and safety sources, such as government or manufacturer reference information; and
  • (i) Service providers, when they return information needed to operate a feature or administer a request.

Stash does not currently collect information from Apple Health, Health Connect, or a direct continuous glucose monitor data stream. Meter and sensor values used in the Sensor-to-Meter Analysis feature are entered manually.

5. Why We Collect and Use Consumer Health Data

We collect and use consumer health data only for purposes disclosed in this policy and in the notice presented when you make the applicable choice.

PurposeHow the information is used
Provide features you requestProcess an incident report, barcode contribution, support request, deletion request, or another action you initiate
Provide Shared StashStore, synchronize, and secure household supply information for authorized household members and administer household roles, invitations, and deletion
Operate optional Community servicesPrepare Community statistics, understand product circulation, analyze supply availability, and present Community-reported information
Analyze supply access and disruptionsStudy shortages, stock patterns, insurance categories, access barriers, and the effects of supply disruptions
Understand product and device experiencesAnalyze reported incidents, wear outcomes, lot patterns, manually entered reading comparisons, and product-reliability trends
Improve StashDiagnose technical problems, improve supply-management calculations, validate product information, and develop app features
Conduct authorized researchSupport properly reviewed research concerning diabetes supplies, access, reliability, device experiences, and health outcomes, subject to separate permissions and safeguards where required
Create authorized aggregate statisticsProduce reports that do not contain information reasonably linkable to a consumer, household, or associated device
Record and honor choicesDocument consent, withdrawal, policy versions, deletion requests, and other privacy-rights activity
Protect the ServicePrevent abuse, secure systems, investigate errors, and comply with applicable legal obligations

We will obtain affirmative consent before collecting a new category of consumer health data or using consumer health data for a purpose not disclosed in this policy, unless Washington or Nevada law, as applicable, permits the collection or use without consent.

6. Optional Community Collection

Stash’s optional Community features may collect specified supply, product, profile, incident, A1C, insurance, and other health-related information.

Before collecting optional Community information, Stash will present a request that identifies:

  • (a) The categories of consumer health data to be collected;
  • (b) The purposes for which the information will be collected and used;
  • (c) How the information will be used;
  • (d) The categories of entities with which it may be shared; and
  • (e) How to withdraw consent.

The choice to participate must be made through a clear affirmative action. We do not treat acceptance of the Terms of Service, continued app use, silence, inactivity, or a preselected setting as consent to optional Community collection.

You may decline Community participation and continue using Stash’s core local supply-management features. Recall and safety information will not be conditioned on agreeing to contribute consumer health data.

7. Sharing Consumer Health Data

Under Washington and Nevada law, “sharing” generally means disclosing consumer health data to a third party or affiliate, subject to statutory exceptions. It does not ordinarily include disclosure to a processor that handles information on Stash’s behalf under appropriate contractual restrictions.

Categories of Consumer Health Data We May Share

Depending on the feature, your choices, and the recipient’s role, the categories disclosed may include:

  • (a) Community Data ID and related record identifiers;
  • (b) Diabetes, regimen, age-range, and caregiver-relationship information;
  • (c) Supply, product, manufacturer, lot, and serial information;
  • (d) Inventory, supply-use, incident, wear, and health-impact information;
  • (e) Regional information;
  • (f) A1C and insurance-category information;
  • (g) Manually entered paired meter and sensor readings and calculated comparison summaries;
  • (h) Consent, withdrawal, and privacy-request information; and
  • (i) Technical information needed to host, secure, or deliver the applicable service.

We limit each disclosure to information appropriate for the relevant purpose.

Categories of Recipients

Consumer health data may be disclosed to the following categories of recipients:

Recipient categoryPurpose
Hosting and infrastructure providersHost Community records, process database requests, maintain system availability, and support security
Technical service providersOperate app features, prevent abuse, troubleshoot errors, and provide necessary infrastructure
Email and support providersDeliver communications and process support or privacy requests when you contact Stash
Apple, Google, and user-selected providersProvide private-cloud storage, operating-system backup, device transfer, calendar, file export, or sharing features you choose
Shared Stash membersAccess Shared Stash records according to the member’s role and the access an owner sets
Government and product-reference servicesRespond to product-identification or safety-reference queries initiated through applicable app features
Professional advisers and authoritiesProvide legal, compliance, security, or other professional services, or respond to valid legal process
Business transaction participantsEvaluate or complete a merger, financing, acquisition, reorganization, or similar transaction, subject to applicable privacy commitments and legal requirements

Stash does not currently share consumer health data with independent universities, manufacturers, or commercial partners for their own research or commercial purposes.

If Stash later proposes to share consumer health data with an independent research institution, manufacturer, industry partner, affiliate, or other third party, Stash will first obtain a consent that is separate and distinct from the consent used to collect the information, unless an exception under Washington or Nevada law applies.

That sharing request will identify the categories of consumer health data involved, the purpose of the sharing, the categories of recipients, and how to withdraw the choice.

Stash currently has no affiliate that receives consumer health data under this policy. We will update this policy before beginning such sharing with an affiliate.

8. Service Providers and Processors

Stash uses service providers to perform functions on its behalf. Depending on the feature used, these providers may include:

  • (a) Supabase, which hosts Stash-operated Community data, Shared Stash records, and sign-in records in the United States;
  • (b) TelemetryDeck, which provides limited app analytics;
  • (c) Cloudflare and Loops, which support requested newsletter communications;
  • (d) Apple and Google, which provide platform, backup, synchronization, transfer, distribution, and user-directed services;
  • (e) Stash’s support mailbox provider; and
  • (f) Network, security, and infrastructure providers.

A service provider may process only the information needed for the contracted service. Stash requires processors handling consumer health data to follow appropriate confidentiality, security, use, retention, and deletion restrictions.

Stash’s analytics configuration is not intended to send diabetes type, treatment regimen, age range, caregiver relationship, insurance information, device-profile information, A1C values, glucose readings, inventory records, product lots, serial numbers, free-text notes, or child-profile information to TelemetryDeck.

9. Research

Stash may offer opportunities to support research concerning diabetes supply access, shortages, device experiences, product reliability, and related health outcomes.

General Community collection consent does not automatically authorize every external research disclosure.

Before providing a nonpublic research dataset to an independent research organization, Stash will determine whether:

  • (a) The dataset is deidentified under the applicable legal standard;
  • (b) A separate sharing consent is required;
  • (c) The project qualifies for a statutory research exclusion;
  • (d) An Institutional Review Board or similar independent body must review or monitor the project;
  • (e) A participant consent, parental permission, or child or teen assent is required; and
  • (f) A data use or research agreement provides appropriate restrictions.

External research datasets must not contain the global Community Data ID. When record-level data is permitted, Stash will use a new project-specific code and apply safeguards appropriate to the project.

Research agreements may prohibit:

  • (a) Reidentifying contributors;
  • (b) Matching research records with external identity records;
  • (c) Contacting contributors;
  • (d) Linking data to clinical records without separate authorization;
  • (e) Using the data outside the approved research purpose;
  • (f) Unauthorized onward disclosure; and
  • (g) Retaining the data beyond the approved period.

Accepting the Stash Terms of Service or joining the Community does not enroll you in an active clinical study.

10. Sale of Consumer Health Data and Future Sale Authorization

Stash does not currently sell consumer health data.

Stash does not sell or license identifiable or pseudonymous contributor-level health records. Stash also does not knowingly sell or commercially license personal or health information concerning anyone under 18.

Stash does not currently include Community contributions in licensed commercial reports. If Stash later offers an optional data-donation or licensed-report program, Stash will provide a separate notice identifying the categories of information, purposes, recipient categories, whether Stash may receive payment, and how to withdraw, and will obtain any consent or authorization required before including your information.

If a proposed transaction would legally constitute a sale of consumer health data, Stash will not rely on:

  • (a) Acceptance of the Terms of Service;
  • (b) General Community consent;
  • (c) Research consent; or
  • (d) An ordinary in-app toggle.

Before a sale, Stash would obtain a separate written authorization satisfying Washington or Nevada law, as applicable. The authorization would identify the consumer health data involved, the seller and purchaser, the purpose of the sale, and the authorization’s expiration date. Signing would not be a condition of receiving the core Stash service.

11. Deidentified Data

Stash treats information as deidentified only when it cannot reasonably be linked to a particular consumer, household, or device linked to a consumer.

When Stash relies on the Washington or Nevada deidentified-data standard, Stash will:

  1. Take reasonable measures to ensure that the information cannot reasonably be associated with a consumer;
  2. Publicly commit to maintaining and using it only in deidentified form and not attempting to reidentify it; and
  3. Contractually require any recipient to comply with the same restrictions.

Accordingly, Stash publicly commits not to reidentify information that it maintains as deidentified data except to determine whether the deidentification measures remain effective or as otherwise expressly permitted by law.

Replacing a name with a Community Data ID does not make information deidentified. Contributor thresholds, aggregation, removal of direct identity fields, or labeling a dataset “anonymous” also do not independently satisfy the Washington or Nevada standard.

Stash reviews factors such as small groups, precise dates, product serial numbers, unusual device histories, repeated queries, and information reasonably available to a recipient when assessing whether an output is deidentified.

12. Children and Caregiver Information

A caregiver may use Stash’s local supply-management features for a child or another person when legally authorized to do so.

Selecting a caregiver relationship does not independently verify parental responsibility, guardianship, or authority to disclose another person’s consumer health data.

Child profiles are excluded by default from:

  • (a) Optional Community contributions;
  • (b) Third-party health-context analytics;
  • (c) External research; and
  • (d) Commercial use.

If Stash offers a caregiver an optional Community or research feature involving a child’s information, Stash will provide a separate explanation of the information, purposes, recipients, and available controls. The caregiver must have the authority required to make that specific choice.

In Shared Stash, only a parent, legal guardian, or another adult authorized to manage the child’s information may create a child profile. A separate parent or caregiver confirmation is required before Stash receives a pediatric device or wear report.

Research involving a child or teenager may also require Institutional Review Board oversight, parental permission, and the child’s or teenager’s assent.

Stash does not knowingly sell or commercially license personal or health information concerning anyone under 18.

13. Your Washington and Nevada Privacy Rights

Subject to applicable law and appropriate verification, Washington and Nevada consumers have the following rights:

RightWhat it means
Confirm and accessConfirm whether Stash is collecting, sharing, or selling your consumer health data and obtain access to that information, including a list of third parties and affiliates with which it has been shared or sold
Withdraw consent or stop processingWithdraw consent for Stash to collect or share consumer health data and, for Nevada consumers, request that Stash stop collecting, sharing, or selling consumer health data
DeleteRequest deletion of consumer health data collected about you
AppealAppeal Stash’s refusal to act on a request
No unlawful discriminationExercise consumer health data rights without unlawful discrimination

Withdrawing consent does not affect processing that lawfully occurred before withdrawal. It ends Stash’s authority to continue consent-dependent processing for the withdrawn purpose.

Turning off a sharing control does not automatically delete information Stash previously received. You must make a deletion request if you also want previously collected information deleted.

14. How to Exercise Your Rights

You may submit a request by:

Please describe the right you want to exercise and the information involved. If your request concerns Community contributions, include your Community Data ID when available.

Stash does not ordinarily maintain a name or email address linked to the Community Data ID. As a result, we may be unable to locate Community records from your name or email address alone.

We may request information reasonably necessary to:

  • (a) Authenticate the request;
  • (b) Locate the relevant records;
  • (c) Confirm that you are authorized to act for another person; and
  • (d) Protect consumer health data against unauthorized access, alteration, or deletion.

We will not require you to create an account to exercise a right. Do not send government identification unless we explain why additional verification is reasonably necessary.

An in-app confirmation that a deletion request was submitted means that Stash received the request. It does not mean that deletion has been completed.

15. Deletion Requests

After authenticating a valid deletion request, Stash will delete the consumer health data covered by the request from its records, subject to applicable exceptions.

Stash will also notify processors, service providers, contractors, and other third parties as required so that the consumer health data is deleted from their records.

We will act on a request without undue delay and no later than 45 days after authentication. For a Nevada consumer, Stash will delete the consumer health data covered by a valid deletion request, and notify the applicable processors and third parties, no later than 30 days after authenticating the request. When reasonably necessary and permitted by law, we may extend the response period once by up to 45 additional days. If we use an extension, we will notify you during the initial response period and explain the reason.

Deletion from archived or backup systems may be delayed when immediate deletion is not technically feasible. Consumer health data subject to a valid request will be deleted from backups as soon as practicable and, for a Washington request, no later than six months after authentication, or for a Nevada request, within the period permitted by Nevada law. Until deletion, backup information will remain protected and will not be restored to active use except as permitted by law. If it is restored, the deletion request will be reapplied.

A Community deletion request does not automatically:

  • (a) Turn off Community or Sensor-to-Meter Analysis contributions;
  • (b) Delete information stored locally on your device;
  • (c) Delete information held in Apple private-cloud services or operating-system backups;
  • (d) Delete Shared Stash records or a sign-in account, which are handled as described in the Privacy Policy;
  • (e) Delete exported files or copies held by recipients;
  • (f) Delete calendar entries;
  • (g) Delete newsletter or support records;
  • (h) Delete analytics maintained under a separate identifier; or
  • (i) Delete records associated with a different Community Data ID.

Turn off applicable contribution settings on every contributing device if you also want future contributions to stop.

Information that has been rendered deidentified and can no longer reasonably be linked to you, your household, or an associated device may not be attributable to your request and may remain in aggregate statistics or research results.

16. Appeals

If Stash refuses to act on all or part of your request, we will provide an explanation and instructions for appealing the decision.

To submit an appeal, email support@stashdiabetes.com with the subject line “Consumer Health Privacy Appeal.” Include:

  • (a) The original request;
  • (b) The date of Stash’s response;
  • (c) The portion of the decision you want reviewed; and
  • (d) Any additional information you would like us to consider.

A person who did not make the original decision will review the appeal when reasonably practicable. We will respond within the period required by applicable law and explain the outcome.

If the appeal is denied, we will provide information about how you may contact the Washington State Attorney General or the Nevada Attorney General, as applicable.

17. Security and Retention

Stash uses administrative, technical, and organizational safeguards appropriate to the nature and sensitivity of consumer health data. These measures include transport encryption, restricted access to backend records, and controls intended to limit information to its authorized purposes.

Stash’s server-held Community records and Shared Stash household information are not end-to-end encrypted against Stash. Authorized Stash personnel and service providers may access them when necessary for an approved purpose.

We retain consumer health data only as long as reasonably necessary for the disclosed purpose or as required or permitted by law. Retention may depend on factors such as:

  • (a) The period during which the information supports the requested Community feature;
  • (b) The need to study supply reliability or access over time;
  • (c) The sensitivity and reidentification risk of the information;
  • (d) Consent withdrawal or deletion requests;
  • (e) Research or contractual requirements;
  • (f) Security and abuse-prevention needs; and
  • (g) Applicable legal obligations.

Research records that carry a project-specific code linking a person’s records over time are consumer health data, not deidentified data. Stash retains them for no longer than 5 years after collection and then deletes or deidentifies them.

Consent records and limited request records may be retained as reasonably necessary to demonstrate and honor your choices. They are not used as Community research contributions.

No security measure can eliminate every risk. If an incident involving consumer health data triggers a notification obligation, Stash will provide the notifications required by applicable law.

18. Changes to This Policy

We may update this policy to reflect changes to Stash, our practices, or applicable law.

We will identify the effective date of the updated policy and provide appropriate notice of material changes.

We will obtain affirmative consent before collecting a new category of consumer health data or using previously collected consumer health data for a materially different purpose not disclosed when it was collected, unless Washington or Nevada law, as applicable, permits the activity without consent.

An updated policy does not retroactively expand the permissions governing information collected under an earlier notice. Information collected under an earlier policy remains subject to the commitments and choices that applied when it was collected unless you separately agree to an expanded use.

19. Contact Us

To ask a question, exercise a right, or submit an appeal, contact:

Stash Diabetes, Inc.
Email: support@stashdiabetes.com