Privacy policy

Effective 19 October 2026

At a glance

Vigil is designed so home control and sensing run on the computer you own. The current release processes microphone, optional camera, and optional WiFi channel-state information locally. It does not upload those raw sensing streams to Black Label. The app's local database can contain sensitive household information, including residents, rooms, activity, derived presence or vital-sign estimates, and alert history. See the dedicated Consumer Health Data Privacy Notice for the health-data and HIPAA boundary.

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.

Information processed on your computer

Vigil reads data from supported LAN devices and from sensing features you enable. Acoustic sensing reads microphone samples transiently to analyze reflections; optional pose sensing reads camera frames; optional sensor nodes send CSI frames over your network. The release app is designed to reduce those signals locally into features and events rather than store conventional audio or video recordings or send raw streams to Black Label.

Residents, home configuration, device state, activity and alert history, geofence settings, relay configuration, and derived sensing results are stored in Vigil's application-support database on your Mac. Vigil does not add application-level encryption to that database. Its protection therefore depends on your macOS account, device access controls, backups, and disk encryption. We recommend enabling FileVault and protecting any backup that contains your user Library.

Away Alerts

Away Alerts is off until you configure it. For a qualifying event, Vigil sends an alert title, message, and source to the HTTP or HTTPS endpoint you chose. The text can include a resident name and a security or health-adjacent event such as intrusion, fall, no-breathing, or a vitals concern. It does not include raw audio, video, camera frames, or CSI.

Black Label does not receive that alert in the normal relay path. The operator of your chosen endpoint can receive it and applies its own terms and privacy practices. Use an HTTPS endpoint: plain HTTP does not encrypt alert text in transit. Removing the endpoint disables this transfer. Vigil is self-monitored and does not contact a monitoring center or emergency services.

Manual update checks

If you choose Check for updates, Vigil fetches a public version manifest from Black Label. Like an ordinary web request, that exposes request time, requested path, IP address, and user-agent information to our hosting and security provider. The request does not include your home model, sensing readings, resident data, license key, or a Vigil-specific device identifier. The app does not contain an advertising, session-replay, or third-party analytics SDK.

Website, account, and sign-in

Cloudflare serves and protects this website and therefore processes ordinary request and security data such as IP address, user agent, URL, time, cookies, and bot or abuse signals. A Vigil account can include email address, authentication method, account creation and recent sign-in or activity timestamps, preferences, subscription or entitlement status, and download access. A signed-in browser session lasts up to 30 days. Short-lived abuse-prevention records derived from email and IP information can be kept for about 15 minutes.

Checkout and hardware orders

Stripe processes payment credentials and checkout information under its own privacy terms. Black Label receives the information needed to deliver and support your order, including email, product, price, currency, payment or subscription status, and transaction identifiers. For sensor-node preorders, Stripe and Black Label also process the shipping name and address, order contents, amount, and order time for payment, fraud prevention, fulfillment, support, accounting, and legal obligations. Black Label does not receive the full card number from Stripe.

Operational analytics

Vigil pages load PostHog, which measures page views and may record clicks and other page interactions, session replays of page layout, scrolling and clicks, heatmaps, clicks that had no effect, and browser errors. Every form field is masked in recordings, and account, sign-in, checkout and download pages load no analytics. PostHog does not show surveys here. When an account is created or a purchase succeeds, our server can send PostHog a signup or paid event. Depending on the event, fields can include sign-in method, product, amount, currency, payment mode, and status. A deterministic event identifier is derived from the account email or Stripe event ID; the raw email is not included in that PostHog event. This is server-side processing, so browser Do Not Track does not disable it.

Support

If you use the support assistant, your question and the page context needed to answer it are sent to our Cloudflare-hosted support service and processed by Cloudflare Workers AI. Do not enter health information, emergencies, passwords, license keys, or other sensitive personal information. If you email support, our email service and Black Label process the message, contact details, and related account or order information needed to respond.

Service providers and sales

We disclose only the information described above to purpose-limited providers such as Cloudflare, Stripe, PostHog, and our email infrastructure, and to a relay destination you configure. We do not sell personal information or use it for cross-context behavioral advertising. We do not receive the raw sensing streams or normal local activity database from the release app.

Retention and deletion

We keep account and order information for as long as needed to provide access, fulfill orders, prevent fraud, keep financial records, resolve disputes, and meet legal obligations. A verified request can delete your Vigil account record and preferences. Billing, tax, transaction, fraud-prevention, fulfillment, legal-hold, provider, and backup records may remain where required or permitted. Data stored locally by Vigil must be deleted from the Mac and its backups separately.

To request access, correction, or deletion, email support@blvigil.com from the address on the account, or use Vigil support. We may need to verify the request before acting.

Changes and contact

We will post material changes at this URL and update the effective date. Questions about this policy can be sent to support@blvigil.com. BlackLabel Tech operates Vigil.