Baby Monitor

Privacy Policy for Baby Monitor Smart Remote

Effective Date: July 8, 2026

Last Updated: July 22, 2026

This Privacy Policy explains how EWS TECHNOLOGY LTD (“EWS Technology,” “we,” “us,” or “our”) collects, uses, shares, stores, and protects information when you use Baby Monitor Smart Remote, our website, and related services.

Baby Monitor Smart Remote is intended for adult parents and legal guardians. Children should not use the website, submit feedback, or provide contact information directly.

For user safety and service security, this public Policy describes data categories, purposes, retention, recipients, user choices, and safeguards at a high level. It does not publish internal hostnames, endpoint paths, implementation variable names, key names, routing rules, or other operational details that could reduce the security of users or the service.

1. Who We Are

Controller:

EWS TECHNOLOGY LTD

Company number: 16299589

Private limited company registered in England and Wales

Registered office: 66 Paul Street, London, England, EC2A 4NE

Website: https://babymonitor.ewstechnology.com

Privacy email: babymonitor@ewstechnology.com

Phone: +420770617422

For privacy questions or requests, contact us at babymonitor@ewstechnology.com.

2. What This Policy Covers

This Policy covers information processed through:

  • - the Baby Monitor Smart Remote app for Android, iOS, and macOS;
  • - the Baby Monitor website;
  • - pairing, monitoring, connectivity, relay, routing, alert, feedback, support, push notification, white-noise, mobile product analytics, crash diagnosis, performance monitoring, website analytics, and voluntary website support payment features;
  • - trusted service providers that help us operate the app and website.

This Policy does not apply to third-party websites, app stores, operating systems, payment providers, or other services that have their own privacy policies, except where we explain how we use them as service providers.

3. Short Privacy Summary

Key points:

  • - The app is intended for adult parents and legal guardians.
  • - The app does not use personal accounts, email/password login, or social login.
  • - We do not sell personal data.
  • - We do not use advertising SDKs.
  • - The production Android and iOS apps use limited Firebase Analytics, Firebase Crashlytics, and Firebase Performance Monitoring for product analytics, crash diagnosis, and reliability. The production macOS app uses Firebase Analytics and Firebase Crashlytics; Firebase Performance Monitoring is not available in the native macOS SDK. These services are not used for advertising or cross-context behavioral tracking.
  • - First-party diagnostic logging is disabled in production mobile-app builds.
  • - We do not use personal data for third-party advertising.
  • - We do not share personal data for cross-context behavioral advertising.
  • - Advertising identifiers, Google signals, and ads personalization are disabled.
  • - We do not collect precise GPS location.
  • - We do not collect contacts, SMS, email inbox, chat messages, calendar data, health or fitness data, browsing history, or an installed apps list.
  • - Live monitoring video, photo, audio, talk-back audio, and live remote-control command content are end-to-end encrypted between paired devices.
  • - Our servers do not have the keys needed to decrypt live monitoring content or live remote-control command content.
  • - We may route or relay encrypted transport data to connect paired devices, but we do not store raw live monitoring video, audio, or photo streams as recordings.
  • - AI cry detection runs locally on the Baby device. We send an alert event, not raw audio recordings for model training.
  • - Users may save photos or videos locally on a Parent device. Saved files are controlled by the user and the device operating system.
  • - Feedback messages and optional attachments are submitted only when the user chooses to send them.
  • - Feedback attachments are not part of the end-to-end encrypted live monitoring stream. If you submit an attachment, we may access it to handle feedback and support.
  • - Push notifications can be disabled in the app and/or in operating system settings.
  • - Voluntary support payments, where available on the website, are not subscriptions, purchases of monitoring features, or a condition of using monitoring.

4. Data We Collect From the App

The information we process depends on your device, platform, permissions, settings, and features you use.

4.1 Device, App, and Installation Information

We may process app platform, app version, app build, app distribution channel, app package or bundle information, app installation identifiers, Firebase-related installation identifiers, user-assigned device name, device model, device manufacturer, operating system name and version, language, locale, timezone, country or region, and basic network information needed to operate the service.

A user-assigned device name may include a person’s name. We treat it as potentially personal data.

We use this information for pairing, device list display, compatibility checks, support, push notifications, security, and connectivity.

4.2 Pairing, Access, and Session Information

The app uses short-lived QR pairing and trusted device relationships instead of personal accounts. To pair Baby and Parent devices, verify access, reconnect paired devices, and prevent unauthorized access, we may process app-generated device identifiers, pairing credentials, encrypted pairing information, access status, session status, connection status, timestamps, and current monitoring status such as online/offline, streaming, night mode, and media mode.

Pairing information is used to make sure only authorized Parent devices can connect to a Baby device. QR pairing credentials are short-lived and are revoked or expired when they are no longer needed.

Pair, access, session, and connection data is retained while needed for the active relationship and is automatically cleaned after 90 days of inactivity, unless a longer period is required for security, abuse prevention, legal, or dispute purposes.

4.3 Camera, Microphone, Monitoring Media, and Control Content

When monitoring features are used, the app may process live video or photo frames from the Baby device camera, live audio from the Baby device microphone, talk-back audio from the Parent device microphone, local audio processing on the Baby device for cry detection, and monitoring preferences such as audio/video/photo mode, quality, camera choice, brightness, flashlight, night mode, and white-noise settings.

Live monitoring content and live remote-control command content are end-to-end encrypted between paired devices. This includes live video, photo frames, audio, talk-back audio, and remote-control command content used for monitoring features.

Our servers may help paired devices connect and may relay encrypted transport data when needed, but our servers do not have the keys needed to decrypt live monitoring content or live remote-control command content.

We do not store raw live monitoring video, audio, or photo streams on our servers as recordings.

If you save a recording or photo on the Parent device, that saved file is controlled by you and your device operating system. You are responsible for managing, deleting, backing up, or sharing local files.

4.4 Local AI Cry Detection

AI cry detection runs locally on the Baby device. The app may process audio locally to identify likely crying sounds.

We do not send raw audio recordings to our servers for AI model training. When an alert is triggered, we may process alert information needed to notify authorized Parent devices and protect the service.

4.5 Baby and Parent Settings

We may process settings needed to operate the app, including monitoring mode, quality preferences, notification preferences, camera/audio/display settings, night mode, white-noise settings, and settings needed to synchronize authorized devices.

Settings may be stored locally on devices and synchronized between paired devices when connected. Settings associated with inactive or removed pairs are deleted or cleaned as described in this Policy.

4.6 Connectivity and Operational Metadata

To connect paired devices, improve reliability, route traffic, diagnose connection issues, manage capacity, and prevent abuse, we may process limited operational metadata. This may include IP address or privacy-protected IP information, approximate country or region, connection method category, server or relay region category, connection status, device online/offline status, timestamps, diagnostic events, security events, request status, and error information.

To find a working or better connection route, the app and Service may open TCP or UDP connections and send and receive generated test requests or test data among paired devices and authorized Baby Monitor service infrastructure. These tests may measure route availability, latency, transfer speed, throughput, bytes sent and received, test duration, success or failure, and estimated available bandwidth. We use the results to compare available routes, select or switch to a better route, diagnose connection quality, and manage service capacity.

Measurements from one test or connection may also be used to direct, distribute, or reroute other authenticated Baby Monitor connections within the same authorized Baby Monitor session across available TCP or UDP connections and service routes. This may occur automatically while the Service establishes or maintains a connection to improve overall speed, reduce congestion, or use a faster working route. These features are intended only for Baby Monitor connectivity and authorized service diagnostics, not to provide a public proxy, carry unrelated third-party traffic, or move traffic between unrelated Baby Monitor sessions.

Network testing and rerouting may temporarily use Wi-Fi or mobile data and reduce bandwidth available for other activity while they are active. Generated test payloads do not contain live monitoring video, photos, audio, talk-back audio, or remote-control content. Any live monitoring content routed or rerouted through service infrastructure remains end-to-end encrypted as described below. We may process limited test and routing metadata, such as test size, timing, route type, connection result, bytes transferred, and transfer rate. If retained, this metadata is handled under the retention rules in this Policy and is not used for advertising or tracking.

We do not collect precise GPS location. Approximate country or region may be inferred from network information, IP-to-country lookup services, locale, or device settings for routing, diagnostics, security, abuse prevention, and capacity management.

We do not store live remote-control command content. Live command content is inside the end-to-end encrypted monitoring transport. We may process limited operational metadata needed to operate and protect the service, such as device relationship status, connection state, route category, alert delivery status, timestamps, support records, and feedback records.

4.7 Push Notifications and Alert Events

For cry alerts, battery alerts, and device health alerts, we may process push notification tokens for Android and iOS, protected token information, notification permission and notification mode information, alert identifiers, alert categories, delivery status, provider responses, battery status, device health status, and cry alert status.

We use this information to send alerts to authorized Parent devices and to avoid sending alerts when notifications are disabled.

Push notification payloads are limited to information needed for notification delivery and do not include live video, photo, or audio streams.

Push tokens are retained while notifications are enabled and the pair exists. They are disabled or deleted when notifications are turned off or the pair is revoked. Stale tokens are cleaned after 90 days of inactivity.

4.8 White Noise and Downloaded Media

When you use white-noise features, we may process white-noise track information, playlist information, file version, file size, local download state, play/pause state, volume, and playback settings.

White-noise files may be downloaded from our service and stored locally on the device until you delete them, clear app data, or uninstall the app.

4.9 Feedback From the App

If you submit feedback from the app, we may process the feedback message you write, optional photo or video attachment, attachment metadata, server-generated attachment storage information, app and device information, language, timezone, country or region, user agent, technical request information, and IP address or privacy-protected IP information. When the app opens feedback in the external browser, the app may first send app and device metadata to our server and receive a temporary feedback key. The website may store that key in a short-lived first-party cookie so the browser feedback and optional support development flow can be connected with the same app installation metadata.

Feedback and optional attachments are sent only when you choose to submit the form.

Feedback attachments are not part of the end-to-end encrypted live monitoring stream. If you voluntarily attach a photo or video to feedback, we may access it to review the issue, respond to you, diagnose bugs, improve the product, and prevent abuse.

4.10 Local Data on Your Device

The app may store data locally on your device, including pairing and access information, known paired devices, notification settings, monitoring settings, downloaded white-noise files, temporary photo or recording files until you save, discard, or delete them, and support or review prompt state.

Local app data may be deleted by deleting a pair, clearing app data, using available reset/delete flows, or uninstalling the app. Local recordings and photos saved outside app cache are controlled by the user and the operating system.

5. Data We Collect From the Website

When you visit or use the Baby Monitor website, we may process page views, browser type and version, device type, operating system, approximate country or region derived from network information, user agent, IP address or privacy-protected IP information, request timestamp, requested page or resource category, HTTP status or error status, cookie or analytics consent state, analytics identifiers after consent where required, feedback form data if you submit feedback, and support payment data if voluntary support payment is available on the website and you use it.

Website analytics starts only after cookie or analytics consent where required. We use website analytics to understand basic website usage and reliability. We do not use website analytics for advertising, remarketing, or cross-context behavioral advertising.

6. App Permissions

Depending on platform and feature, Baby Monitor Smart Remote may request operating system permissions.

Camera:

Used on the Baby device for video monitoring and photo mode. Camera may also be used on the Parent device to scan a QR code for pairing.

Microphone:

Used on the Baby device for audio monitoring and local cry detection. Used on the Parent device for talk-back audio.

Local Network:

Used to find and connect paired devices on the same local network where available.

Notifications:

Used to send cry alerts, battery alerts, and device health alerts to authorized Parent devices.

Photos, Videos, Media, or Storage:

Used when you choose to save local photos or videos, attach selected media to feedback, or manage downloaded files, depending on platform behavior.

Internet / Network Access:

Used for pairing, connectivity, TCP/UDP connection and route testing, authorized same-session traffic routing or rerouting, relay, push notifications, feedback, website access, white-noise downloads, and voluntary website support payment flow where available.

You can revoke app permissions in your device settings. Some features may stop working if required permissions are revoked.

7. Monitoring Video/Audio and End-to-End Encryption

Baby Monitor Smart Remote processes live monitoring content to provide its core function.

When Baby Mode is active and a Parent device is paired and authorized, the Baby device may send live camera, photo, or microphone data to the Parent device through available connectivity routes.

Live monitoring video, photos, audio, talk-back audio, and remote-control command content are end-to-end encrypted between paired devices. Our servers do not have the keys needed to decrypt that content.

Our servers may process encrypted transport data and limited operational metadata needed to connect devices, route data, deliver alerts, prevent abuse, diagnose issues, and maintain service reliability.

We do not store raw live monitoring video, audio, or photo streams on our servers as recordings.

AI cry detection is performed locally on the Baby device. We do not send raw audio recordings to our servers for AI training.

Parent devices may locally save photos or videos created from the received monitoring stream. These local files are controlled by the user and the operating system after saving.

8. Pairing, Connectivity, and Relay

The app uses pairing and connectivity systems to make sure only authorized Parent devices can connect to a Baby device.

Pairing may use QR codes, short-lived pairing credentials, encrypted pairing information, access status, and expiry status. These are used to create or confirm a trusted relationship between devices.

Connectivity may use local network, direct network, or relay-assisted routes depending on device, router, operating system, network, and service availability.

We use connectivity information to find paired devices, choose a working route, restore connections, show status, prevent unauthorized access, diagnose errors, and manage service capacity.

Operational connection data is generally maintained as current state. On new connections, current-state values may be updated or overwritten. Stale connection and pair data is automatically deleted after 90 days of inactivity, unless a longer period is needed for security, abuse prevention, legal, or dispute purposes.

9. Push Notifications and Alerts

Baby Monitor Smart Remote may send alerts to authorized Parent devices, including cry alerts, battery alerts, and device health alerts.

To provide notifications, we use platform notification services for Android and iOS. We may process push tokens, protected token information, notification settings, event identifiers, alert categories, delivery status, and provider errors.

Push notification content is limited to what is needed to notify authorized Parent devices. Notifications may appear on your device lock screen depending on your operating system settings.

You can disable notifications in the app and/or in your device settings. If notifications are disabled or a pair is revoked, related push tokens are disabled or deleted.

10. White Noise and Downloaded Media

The app may offer white-noise tracks for playback on the local device or remotely on the Baby device under Parent control.

When using white noise, the app may request a media list and download files needed for playback. Downloaded white-noise files are stored locally until you delete them, clear app data, or uninstall the app.

11. Feedback and Support Requests

You may submit feedback or support requests through the app or website. Feedback is optional.

When you submit feedback, we may process the message you write, optional selected attachments, app and device information, browser information, language and timezone information, request information, IP address or privacy-protected IP information, and other information needed to respond, diagnose bugs, improve the product, prevent spam, and protect the service.

Children should not submit feedback or contact information directly. Feedback should be submitted by an adult parent or legal guardian.

Feedback messages and optional attachments are retained for 90 days and then automatically deleted, unless a longer period is required for a security investigation, legal obligation, dispute, or abuse prevention.

12. Voluntary Support Payments Through Stripe

This section applies only if voluntary support payments are available on the website.

Support payments are voluntary. They are not purchases of monitoring functionality, subscriptions, or a condition of using monitoring features.

Stripe support payments are not part of the production app payment flow. If a website support payment option is available and you choose to use it, we may process selected amount, currency, payment status, payment provider identifiers, refund or dispute status, and installation-related information used to avoid repeated support prompts.

Payment card number, CVC, and full bank details are processed by Stripe Checkout. The app and our servers do not store card numbers, CVC, or full payment card details.

Support payment records are retained for 7 years for tax, accounting, fraud prevention, refund, dispute, and legal record purposes.

13. Mobile Firebase Services, Push Services, and Website Analytics

13.1 Mobile Firebase Services

The production Android and iOS apps use Firebase Analytics, Firebase Crashlytics, and Firebase Performance Monitoring for limited product analytics, crash diagnosis, and service reliability. The production macOS app uses Firebase Analytics and Firebase Crashlytics; Firebase Performance Monitoring is not available in the native macOS SDK. This provider telemetry is separate from first-party diagnostic logging, which is disabled in production app builds. Operating systems, app stores, and network providers may still process their own technical information under their own policies.

At the revision date of this Policy:

  • - Firebase Analytics may process automatic app lifecycle, session, installation, device, and app interaction information;
  • - custom analytics events are limited to the successful type of monitoring connection, playback of a built-in white-noise track, and an actual change to the Auto Mix or Replay setting;
  • - we do not set a Firebase User ID or user properties, and analytics events do not include names, Baby or Parent identifiers, pairing or session identifiers, IP or local network addresses, URLs, credentials, monitoring media or audio, user-authored content, or arbitrary diagnostic text;
  • - Firebase Crashlytics may process app crashes and related technical diagnostics, including Android application-not-responding events and native crash diagnostics, stack traces or processed minidump data, app/device information, and related installation signals;
  • - we do not add Crashlytics custom logs, custom keys, a User ID, manual non-fatal reports, pairing data, network addresses, monitoring media, or user-authored content;
  • - Firebase Performance Monitoring may process Android app lifecycle and screen performance information and a limited connection-attempt trace on Android and iOS; it is not included in the native macOS app;
  • - automatic network instrumentation is disabled on iOS, automatic local-network HTTP instrumentation is not enabled on Android, and the custom trace does not include local URLs, hostnames, IP addresses, device names, pairing identifiers, monitoring media, or user-authored content;
  • - Firebase App Check uses platform app-integrity services to help verify that requests come from an authentic app installation and may process an app-integrity token, Firebase user agent, app identifier, and related device or installation signals;
  • - the app sends the short-lived App Check token to our protected service requests for security and abuse prevention; our service verifies the token and does not store the raw token in application records;
  • - Android uses Firebase Cloud Messaging for push notification delivery;
  • - iOS uses Apple Push Notification service directly and does not include the Firebase Messaging SDK;
  • - the app does not use an Ads SDK;
  • - advertising identifiers are disabled;
  • - Google signals are disabled;
  • - ads personalization is disabled.

Firebase Analytics is used for product analytics, Crashlytics and Performance Monitoring are used for app functionality, diagnostics, analytics, and reliability, Firebase App Check is used for app integrity, service security, and abuse prevention, and Firebase Cloud Messaging is used for Android push delivery. These services are not used for third-party advertising or cross-context behavioral tracking.

13.2 Website Analytics

The website may use Firebase/Google Analytics after cookie or analytics consent where required.

Website analytics helps us understand page views, device/browser categories, approximate usage, and website reliability. We do not use website analytics for third-party advertising, remarketing, or cross-context behavioral advertising.

14. How We Use Data

We use data for app functionality, pairing and access control, live monitoring, talk-back audio, alerts, white-noise playback, device status, user settings, security, abuse prevention, connectivity, mobile product analytics, crash diagnosis, performance monitoring, reliability, support, feedback, consent-based website analytics, voluntary website support payments, legal compliance, and protection of users and the service.

15. How We Share Data / Service Providers

We do not sell personal data.

We do not use personal data for third-party advertising.

We do not share personal data for cross-context behavioral advertising.

We may disclose data to the following categories of recipients:

Baby Monitor infrastructure:

Used to provide pairing, access control, device status, connectivity, relay, push routing, white-noise downloads, feedback, diagnostics, and security. Live monitoring content and live remote-control command content are end-to-end encrypted and cannot be decrypted by our servers.

Hosting, network, and server infrastructure providers:

Used to host and operate the website, app services, databases, routing, reliability, and security systems.

Google / Firebase:

Used for mobile Firebase Analytics, Firebase Crashlytics, Firebase Performance Monitoring, Firebase App Check and related installation services, Android Firebase Cloud Messaging, and consent-based website Firebase/Google Analytics.

Apple:

Used for iOS app distribution, iOS platform services, and iOS push notifications.

Stripe:

Used for voluntary support payments on the website if the payment flow is available.

Country/IP-derived routing and security providers:

Used for approximate country or region detection, routing, diagnostics, reliability, and abuse prevention. We do not use precise GPS location.

App stores and operating systems:

Google Play, Apple App Store, Android, iOS, and related platform services may process data for app distribution, permissions, notifications, app review prompts, and platform functionality.

Legal, safety, and security recipients:

We may disclose data if required by law, legal process, or government request, or when necessary to protect users, the service, our rights, safety, security, or property.

16. Data We Do Not Collect

Baby Monitor Smart Remote is not designed to collect precise GPS location, contacts, address book, SMS, email inbox, chat messages, calendar data, health or fitness data, installed apps list, browsing history, general files or documents except user-selected feedback attachments and user-saved local recordings or photos, passwords or account login credentials, advertising data for ads, card number, CVC, or full payment card data.

We may still process technical request data, device metadata, app metadata, approximate country/region, website analytics identifiers after consent where required, feedback data, payment status data, pairing identifiers, push tokens, operational metadata, and encrypted monitoring transport data as described in this Policy.

17. Children’s and Family Privacy

Baby Monitor Smart Remote is intended for adult parents or legal guardians, not for use by children.

The app may process a child’s image or voice only because an adult parent or legal guardian configures Baby Mode and pairs authorized Parent devices. The child does not create an account and should not submit data directly.

Parents and legal guardians are responsible for using Baby Monitor Smart Remote only where they have legal authority and in a lawful manner, including in relation to any child, caregiver, household member, visitor, or other person who may be captured by camera or microphone.

Live monitoring video, photos, audio, talk-back audio, and live remote-control command content are end-to-end encrypted between paired devices. Our servers do not have the keys needed to decrypt that content.

We do not store raw live monitoring video, audio, or photo streams on our servers as recordings.

We do not sell children’s personal information.

We do not share children’s personal information for cross-context behavioral advertising.

We do not use children’s personal information for third-party advertising.

Parents and legal guardians may request deletion of pair, access, push, feedback, and other applicable data by contacting babymonitor@ewstechnology.com.

If we learn that a child has submitted feedback, contact information, or other data directly without appropriate parent or guardian involvement, we will take reasonable steps to delete that information.

18. Cookies and Website Analytics Consent

The website may use cookies, local storage, or similar technologies for analytics consent state, website functionality, Firebase/Google Analytics after consent where required, security and abuse prevention, and support or feedback flow state if needed.

Where required, website analytics starts only after the user gives analytics or cookie consent. You can manage website analytics or cookie consent through the website consent controls where available.

At this revision, accepted website analytics consent may be stored in browser local storage for up to 12 months, unless you clear browser/site data earlier or website code changes or removes the consent version. Rejecting cookies is not stored; it closes the notice for the current page, keeps analytics off, and allows the notice to appear again on a later page load.

For more information, see our Cookie Notice at https://babymonitor.ewstechnology.com/cookies.

19. Data Retention

We keep data only for as long as reasonably necessary for the purposes described in this Policy, unless a longer retention period is required or permitted by law.

Pair and access data:

Retained while the pair is active. Deleted when the pair is deleted or revoked, or automatically cleaned after 90 days of inactivity.

Pairing credentials:

Short-lived and used only for pairing. They are revoked, used, or expired when no longer needed.

Session and connection state:

Operational connection data is generally maintained as current state. On new connections, current-state values may be updated or overwritten. Stale session and connection data is automatically cleaned after 90 days of inactivity.

Push tokens:

Retained while notifications are enabled and the pair exists. Disabled or deleted when notifications are turned off or the pair is revoked. Stale tokens are cleaned after 90 days of inactivity.

Live monitoring video/audio/photo and live command content:

Realtime or transient end-to-end encrypted transport only. Not stored by our servers as recordings. Our servers cannot decrypt live monitoring content or live command content.

Operational metadata:

We may store limited operational metadata needed for pairing, access control, status, routing, alerts, diagnostics, support, feedback, and security. Current-state operational metadata may be overwritten on new connection, and stale records are cleaned after 90 days of inactivity unless a shorter period applies or a longer period is required.

Local recordings/photos:

Controlled by the user and the device operating system. Temporary files are deleted after save, discard, or delete according to app/OS behavior.

White-noise downloads:

Stored locally until the user deletes them, clears app data, or uninstalls the app.

Baby/Parent settings:

Stored while needed for the pair and expected monitoring state. Deleted or reset when the pair is removed or after 90 days of inactivity, subject to local device behavior and limited diagnostics.

Feedback messages and attachments:

Retained for 90 days and then automatically deleted, unless a longer period is required for a security investigation, legal obligation, dispute, or abuse prevention.

Support payment records:

Retained for 7 years for tax, accounting, fraud prevention, refund, dispute, and legal record purposes.

Security, delivery, and current-state records:

The service does not retain routine application runtime, web access, or error logs. Limited functional records may still be retained where needed to enforce rate limits, prevent abuse, represent current Baby/Parent and connection state, deliver alerts, process feedback, or satisfy a legal obligation. These records are not general-purpose runtime logs and are retained only for their stated function.

Firebase mobile services and Android push:

Our service does not retain raw App Check tokens and does not create a separate raw copy of Firebase Analytics, Crashlytics, or Performance Monitoring reports. Firebase/Google may process and retain analytics, performance, app-integrity, installation, and Android push-delivery data according to Firebase settings and terms. Firebase Crashlytics crash stack, processed minidump, and related installation data is retained for about 90 days before deletion starts.

Website analytics consent:

At this revision, accepted website analytics consent may be stored in browser local storage for up to 12 months, unless the user clears browser/site data earlier or website code changes or removes the consent version. Rejecting cookies is not stored; it closes the notice for the current page, keeps analytics off, and allows the notice to appear again on a later page load.

Legal records:

Retained as required or permitted by applicable law.

20. Security

We use technical and organizational measures designed to protect data, including encrypted network connections, short-lived pairing credentials, access revocation, protected push notification information, end-to-end encryption of live monitoring content and live command content between paired devices, no server-side decryption keys for live monitoring content or live command content, limited operational metadata, restricted use of payment data through Stripe Checkout, and security controls designed to protect users and infrastructure.

End-to-end encryption reduces risk, but it does not protect against every possible risk. Security can still be affected by device compromise, malware, weak device passcodes, screenshots, local saves, shared QR codes, lost devices, operating system bugs, network attacks, or user mistakes.

No method of transmission or storage is 100% secure. We cannot guarantee absolute security.

21. Your Choices and Privacy Rights

In the app, you may delete a pair, delete or revoke a Parent device, revoke Baby or Parent access, disable notifications, change notification mode, stop monitoring, change camera/microphone/stream/night-mode/white-noise/display settings, delete downloaded white-noise files, delete local recordings or photos from device storage, clear app data, or uninstall the app.

In operating system settings, you may revoke or change permissions for camera, microphone, local network, notifications, photos/media/storage, where applicable. Some features may stop working if required permissions are disabled.

On the website, you may manage analytics or cookie consent where consent controls are available.

The app does not yet provide a full in-app “Delete Data / Reset” flow for all server-side data. Some partial actions are available, such as deleting a pair, deleting a Parent device, revoking access, and clearing local data. For full deletion requests, contact us manually at babymonitor@ewstechnology.com.

You may contact babymonitor@ewstechnology.com to request access, correction, deletion, restriction, objection, data portability where applicable, withdrawal of consent where applicable, or information about processing and service providers.

We may need to verify your request before fulfilling it. Because the app does not use personal accounts, verification may require information related to your installation, pair, device, feedback submission, support payment, or other technical identifiers.

22. California Privacy Notice

This section applies to California residents where the California Consumer Privacy Act, as amended by the California Privacy Rights Act, applies to us. If those laws do not apply to us because we do not meet applicable thresholds, we provide this section for transparency only.

Depending on your use of the app or website, we may collect identifiers, internet or electronic network activity information, approximate geolocation, audio/electronic/visual information, commercial information if you use voluntary website support payments, device and app information, user content, and limited service-related inferences.

We collect personal information from you, your Baby and Parent devices, your operating system and browser, network and server interactions, Google/Firebase, Apple platform services, Stripe if website payments are used, hosting/network/server infrastructure, and country/IP-derived routing and security providers.

We use personal information for app functionality, pairing and access control, baby monitoring, push alerts, white-noise downloads, consent-based website analytics, support and feedback, voluntary support payments, security and fraud prevention, service reliability, and legal compliance.

We may disclose the categories above to service providers and processors described in the “How We Share Data / Service Providers” section.

We do not sell personal information.

We do not share personal information for cross-context behavioral advertising.

We do not use personal information for third-party advertising.

Where applicable, California residents may have the right to know/access categories and specific pieces of personal information, delete personal information, correct inaccurate personal information, opt out of sale or sharing, limit use of sensitive personal information where applicable, receive information about disclosure practices, and not be discriminated against for exercising privacy rights.

To exercise rights, contact babymonitor@ewstechnology.com.

Because we do not sell or share personal information for cross-context behavioral advertising, we do not offer a “Do Not Sell or Share” opt-out for those practices.

23. EEA / UK Privacy Notice

This section applies where the EU GDPR, UK GDPR, Swiss data protection law, or similar privacy laws apply.

The controller is:

EWS TECHNOLOGY LTD

Company number: 16299589

Registered office: 66 Paul Street, London, England, EC2A 4NE

Privacy email: babymonitor@ewstechnology.com

Depending on the processing activity, we rely on the following legal bases:

  • - performance of a service requested by the user for pairing, access control, monitoring, connectivity, white-noise downloads, and core app functionality;
  • - performance of a service and legitimate interests for end-to-end encrypted live monitoring transport;
  • - consent where required, or service functionality and legitimate interests, for push notifications;
  • - consent or user request for optional feedback messages and attachments;
  • - consent where required for website analytics cookies;
  • - legitimate interests for security, abuse prevention, functional delivery records, and service reliability;
  • - user request/payment processing and legal obligation for voluntary support payments and accounting/tax records;
  • - legal obligation for legal compliance.

Where we rely on legitimate interests, our interests include preventing unauthorized access, protecting children, families, users, and the service, maintaining secure connectivity and reliability, preventing abuse, fraud, and spam, improving product quality, and maintaining necessary security and delivery records.

Depending on your location and applicable law, you may have the right to access your personal data, rectify inaccurate personal data, erase personal data, restrict processing, object to processing based on legitimate interests, receive data portability, withdraw consent where processing is based on consent, and lodge a complaint with a supervisory authority.

You may exercise rights by contacting babymonitor@ewstechnology.com.

If you are in the United Kingdom, you may also contact the UK Information Commissioner’s Office. If you are in the EEA, you may contact your local data protection authority.

Some data is necessary to provide the service. For example, pairing identifiers, connection metadata, device metadata, camera/microphone access, local network access, and push tokens may be required for pairing, monitoring, connectivity, and alerts. If you do not provide required data or permissions, some features may not work.

We do not use automated decision-making or profiling that produces legal or similarly significant effects.

24. International Transfers

We are established in the United Kingdom. We and our service providers may process data in countries other than where you live, including the United Kingdom, United States, European Economic Area, and other countries where our infrastructure or providers operate.

These countries may have data protection laws different from your country. Where required, we use appropriate safeguards for international transfers, such as data processing agreements, standard contractual clauses, UK transfer addenda or equivalent safeguards, and provider transfer mechanisms.

25. Changes to This Policy

We may update this Policy from time to time. When we update it, we will revise the “Last Updated” date above.

If changes are material, we may provide additional notice through the app, website, or other appropriate means.

Your continued use of the app or website after the updated Policy becomes effective means that you acknowledge the updated Policy, subject to applicable law.

26. Contact Us

For privacy questions, requests, or concerns, contact:

EWS TECHNOLOGY LTD

Company number: 16299589

Registered office: 66 Paul Street, London, England, EC2A 4NE

Website: https://babymonitor.ewstechnology.com

Email: babymonitor@ewstechnology.com

Phone: +420770617422

Parents or legal guardians may contact us to request deletion of pair, access, push, feedback, support, or other applicable data.

We use optional analytics cookies to understand basic website usage. Learn more.