Privacy Policy

Service: Halo Home
Provider: Halo Media Solutions Inc.
Last updated: May 3, 2026
Contact: mike@halomediasolutions.com

This Privacy Policy explains how Halo Media Solutions Inc. ("we", "us", or "our") collects, uses, discloses, and protects information when you access or use Halo Home, including the web application, Android application, desktop helper, local bridge software, websites, and related services that link to this policy (collectively, the "Service").

Halo Home is designed for private camera monitoring and related home or small-property automation workflows. Because the Service may display camera feeds, store recordings, send notifications, and request Android permissions such as Camera and Notifications, this policy describes those practices in detail. By using the Service, you acknowledge the practices described below.

1. Scope and roles

This policy applies to information processed by Halo Media Solutions Inc. for the Service. It does not apply to third-party camera manufacturers, cloud video providers, app stores, identity providers, payment processors, operating systems, internet service providers, or other services that you connect to or access through the Service. Those third parties operate under their own terms and privacy policies.

If you connect cameras, bridges, storage buckets, or cloud accounts that you control, you are responsible for having the rights and permissions needed to monitor those spaces and to process any video, audio, images, metadata, or personal information captured by those systems.

2. Information we collect

2.1 Account and profile information

• Email address, username, account identifiers, authentication status, and related sign-in information.
• Security and verification events, such as sign-in attempts, password reset requests, and session activity.
• Support communications and any information you choose to provide when contacting us.

2.2 Camera, device, and bridge information

• Camera names, labels, connection settings, stream URLs or identifiers, local network addresses, and pairing data.
• Bridge device status, software version, connectivity state, diagnostic signals, and local service availability.
• Camera control activity, including setup actions, refreshes, pan/tilt/zoom commands, and dashboard preferences.
• Recording metadata, such as camera identifier, recording time, duration, event type, and storage object references.

2.3 Video, images, detections, and recordings

The Service can display live camera feeds and may process camera frames for setup, review, recording, motion or person detection, thumbnails, or related camera features. Depending on your configuration, some processing may happen locally on your device, desktop helper, or local bridge, and some data may be transmitted through our hosted services or cloud infrastructure.

• Live streams may pass through browser, mobile, bridge, WebRTC, or camera-provider systems needed to display video.
• Recordings may be stored in cloud storage configured for the Service or in storage resources associated with your deployment.
• Detection results may include timestamps, camera identifiers, bounding boxes, labels, confidence scores, and event summaries.
• We do not sell camera footage, recordings, images, or detection events.

2.4 Android permissions and mobile device information

The Android app may request permissions that are necessary for the Service to function:

• Camera: used for setup workflows such as scanning QR codes or pairing information, and for camera-related features you initiate. We do not use the phone or tablet camera for unrelated background recording.
• Notifications: used to deliver alerts you enable, such as camera, bridge, recording, or security-related updates.
• Network and Wi-Fi state: used to connect to local bridge services, cameras, and network-dependent features.
• Wake lock: used by Android notification and local delivery features where supported.

2.5 Usage, diagnostics, and security information

• IP address, approximate region, device type, operating system, browser or app version, and user-agent information.
• API requests, timestamps, error logs, crash data, performance metrics, and reliability diagnostics.
• Security signals used to prevent abuse, protect accounts, investigate incidents, and maintain service integrity.

2.6 Payment and subscription information

If paid plans, subscriptions, or in-app purchases are offered, payment processing may be handled by third-party processors or app stores. We do not store full payment card numbers. We may receive transaction status, customer identifiers, subscription plan, renewal dates, receipts, and similar billing metadata needed to operate the Service.

3. How we use information

• Provide, maintain, secure, and improve the Service.
• Authenticate users, manage accounts, and protect against unauthorized access.
• Connect cameras, bridges, dashboards, recordings, notifications, and mobile app features.
• Process recordings, detection metadata, thumbnails, alerts, and review timelines when those features are enabled.
• Provide support, troubleshoot issues, investigate outages, and respond to user requests.
• Comply with legal obligations, enforce our terms, and protect the rights, safety, and property of users and others.

4. How information is shared

We do not sell personal information. We may share information in the following limited circumstances:

• Service providers: hosting, storage, authentication, analytics, diagnostics, email, push notification, payment, and infrastructure providers that help us operate the Service.
• Camera and platform providers: third-party camera, streaming, app store, operating system, and cloud services you choose to connect or use.
• Legal and safety purposes: when reasonably necessary to comply with law, respond to legal process, prevent fraud or abuse, protect rights and safety, or enforce our agreements.
• Business transfers: in connection with a merger, acquisition, financing, reorganization, or sale of assets, subject to appropriate protections for personal information.
• With your direction or consent: when you intentionally share data, connect integrations, invite users, export files, or ask us to disclose information.

5. Local processing, home networks, and connected devices

Halo Home is intended to work with devices and networks that you control. Some features depend on a local bridge or desktop helper running inside the same network as your cameras. Local bridge traffic, camera streams, and detection workflows may remain on your local network depending on your configuration, but remote access, cloud recording, notifications, and account features may require transmission through hosted services.

You are responsible for securing your Wi-Fi network, camera credentials, local computers, mobile devices, and any third-party camera accounts you connect to the Service.

6. Cookies, local storage, and device storage

We may use cookies, local storage, secure storage, app storage, and similar technologies to keep you signed in, remember preferences, store device settings, manage push notification subscriptions, and operate security features. You can clear browser or app data through your browser, operating system, or device settings, but doing so may remove saved preferences or require you to sign in again.

7. Data retention

We retain information for as long as reasonably necessary to provide the Service, comply with legal obligations, resolve disputes, enforce agreements, prevent abuse, and maintain security. Retention periods vary by data type:

• Account information is generally retained while your account remains active.
• Recordings and related metadata are retained according to your settings, plan, storage configuration, or deletion requests.
• Logs and diagnostics may be retained for a limited period for security, reliability, and troubleshooting.
• Support communications may be retained as needed for service history and legal compliance.

8. Security

We use reasonable administrative, technical, and organizational safeguards designed to protect information. These may include encryption in transit, access controls, authentication, least-privilege operational practices, monitoring, and secure cloud infrastructure. No system is perfectly secure, and we cannot guarantee that unauthorized access, loss, or misuse will never occur.

9. Your choices and rights

• You can choose whether to grant Android permissions such as Camera and Notifications.
• You can disconnect cameras, bridges, notification subscriptions, or integrations where the Service provides those controls.
• You can request access, correction, deletion, or export of personal information by contacting us.
• You can delete local app or browser data through your device settings.

Depending on where you live, you may have additional privacy rights under applicable law. To make a request, contact mike@halomediasolutions.com. We may need to verify your identity before processing certain requests.

10. International processing

We are based in Canada and may process information in Canada, the United States, and other countries where we or our service providers operate. These countries may have privacy laws different from those in your location.

11. Children

The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information through the Service, contact us so we can take appropriate action.

12. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date above. If changes are material, we may provide additional notice through the Service, by email, or by other reasonable means.

13. Contact

For privacy questions, account deletion requests, or data rights requests, contact Halo Media Solutions Inc. at mike@halomediasolutions.com.

Related: Terms of Service