RespireLYFTMLive Your FullestFor your buying team
See what participants get, how the first group starts and what your buying team needs to review privacy, delivery and support.
Cough and inhaler use captured for the participant, watch measurements, connected peak flow and local weather, pollen and air quality—one platform. A respiratory food rating, personal patterns and one small step at a time. Participants start on a phone; a compatible smartwatch adds inhaler logging and technique coaching. No smart inhaler or clip-on sensor to buy, ship or recover.
Explore the product
Read the current policy for data categories, purposes, sharing, retention and individual choices. Deployment-specific data flows and contracts are reviewed for the proposed service.
Read the privacy policy
Respire LYF supports everyday respiratory self-management and care conversations. Explore the published technical research and the care and FDA policy explanation for your review. Respire LYF operates under FDA’s general-wellness policy: it supports everyday self-management alongside usual care and is not an FDA-cleared device. It does not diagnose, predict attacks or change medicines.
Explore the evidenceStart your internal review
Share the proposed population, device scope, fees, responsibilities and readout with your benefits, clinical and procurement colleagues. Bring your security questionnaire to the same scoping conversation so deployment requirements can be resolved in parallel.
AI4LYF’s published privacy policy describes encrypted connections, role-based access, infrastructure monitoring and incident handling. Hosting, subprocessors, retention and contractual evidence for your proposed deployment belong in the deployment review.
Define the eligible adult population, invitations, voluntary participation and the permissions needed for each enabled feature.
Employer programs receive aggregate reporting only, never employees’ personal health records. Practice, health-plan and care-management programs choose the staff route before launch—shared report, export or staff access—with roles and permissions written into the agreement.
Review hosting, subprocessors, access controls, retention, deletion and incident handling for the actual deployment. Identify which records stay in the app and which, if any, need to move.
Define the service, data roles, support and any required data-protection or business-associate agreement. Resolve requirements before participant data is transferred.
Set the activation definition, reporting denominators, privacy safeguards and review date before launch. Clinical or claims-savings evaluation needs its own agreed method and scope.
Tell us your population, data requirements, decision owner and launch window.
