Consumer Health Data Privacy Notice

Health data, HIPAA, and Vigil

Effective 31 August 2026

Health-related information Vigil can process

Depending on the features, hardware, permissions, and resident details you choose, Vigil can process:

• derived breathing-rate and heart-rate estimates, signal quality, motion, stillness, and presence;
• possible fall, no-breathing, or vitals-concern events;
• room occupancy, activity patterns, timestamps, modes, and alert history;
• resident names or labels you enter and associations between a resident, room, and event; and
• microphone samples, optional camera frames, and optional WiFi channel-state frames used transiently to derive those results.

These data can reveal sensitive facts about a household even when they are not protected health information under HIPAA.

Platform guidance: References below to the Mac application-support database, macOS permissions, and FileVault describe the Mac app. On Windows, use a protected Windows account and device encryption or BitLocker where available, and protect backups. Feature availability and storage locations vary by platform.

Sources and purposes

Information comes from details you enter, supported smart-home devices, the Mac microphone, an optional camera, optional sensor nodes, app state, and computations performed by Vigil. Vigil uses it locally to show room state, run automations and security modes, keep the activity log, apply signal-quality checks, and create an alert when a configured rule is met.

Where the information goes

Local processing by default

The current release is designed to process raw microphone, camera, and CSI signals in memory on your Mac. It does not send those raw streams to Black Label. Derived results, resident details, configuration, and event history are stored in Vigil's local application-support database. Anyone with access to the Mac, its user account, or an unprotected backup may be able to access that data. Vigil does not add application-level database encryption, so use macOS access controls, enable FileVault, and protect backups.

Optional Away Alerts

Away Alerts is off until you enter an endpoint. A qualifying alert sends a title, message, and source to that user-selected destination. The text may include a resident name and a fall, no-breathing, vitals, or security concern; it does not include raw audio, video, camera frames, or CSI. The destination operator receives the alert under its own practices. Use HTTPS because plain HTTP does not encrypt alert text in transit. Black Label does not receive the alert in the normal relay path.

Website services

The Vigil website, account, checkout, and support services process the information described in the Privacy Policy. They are separate from in-home sensing and do not receive Vigil's normal local activity database. Do not put health information into the website support assistant or an account field.

HIPAA boundary

HIPAA applies based on the parties and the work they perform; it is not a general product certification. The U.S. Department of Health and Human Services explains that health information sent to a consumer app that is neither a covered entity nor its business associate may no longer be protected by HIPAA. A vendor can be a business associate when it handles protected health information on behalf of a covered entity for a covered function.

Do not use the consumer edition to create, receive, maintain, or transmit protected health information on behalf of a HIPAA covered entity or business associate unless Black Label first completes a written review and signs the agreements required for that deployment. Read the official HHS health-app guidance and HHS covered-entity and business-associate guidance.

Other consumer-health protections

Health data outside HIPAA can still be protected by state privacy laws, the Federal Trade Commission Act, and the FTC Health Breach Notification Rule, depending on the facts. The FTC provides official Health Breach Notification Rule guidance. This notice describes Vigil's current data flows; it does not narrow rights available under applicable law.

No medical or emergency use

Vigil suppresses some estimates that do not pass internal signal-quality checks. Those checks do not establish medical accuracy. The readings and alerts have not been clinically validated and can be delayed, missed, or wrong. Do not use Vigil for diagnosis, treatment, emergency decisions, or as a substitute for medical, fire, carbon-monoxide, intrusion-alarm, or other life-safety equipment. Vigil does not contact emergency services.

Your choices and rights

• Choose inputs: deny or revoke microphone and camera permissions in macOS and disconnect optional sensor nodes.
• Stop sharing: remove the Away Alerts endpoint to stop future relay transmissions, and contact the destination operator about information it already received.
• Access or delete local data: use Vigil's controls and remove its local application-support data and related backups from your Mac. Removing the app alone may not remove its data folder.
• Website requests: request access, correction, or deletion of account data by emailing support@blvigil.com from the account address. Some transaction, tax, fraud-prevention, fulfillment, legal-hold, provider, and backup records may remain where required or permitted.
• Appeal: if we deny a consumer-health-data request, reply with “Appeal” and the reason you believe the decision should change. A person will review it.

Sale and disclosure

Black Label does not sell consumer health data. It does not disclose Vigil's local health-related results to advertising networks or data brokers. Information is disclosed only when you direct the app to a relay destination, when you choose to send it to support, when needed by purpose-limited service providers for a service you requested, or when law requires it.

Contact and changes

Questions and rights requests: support@blvigil.com. We will post material changes at this URL and update the effective date. BlackLabel Tech operates Vigil.