Politique de confidentialite

1. Who we are and how to contact us

LittleWatch is a software baby monitoring app that lets a parent or caregiver use one device as a camera and another device or browser as a viewer.

In this policy, LittleWatch, we, us and our refer to the team operating the LittleWatch app, website, cloud routing, web viewer and related services.

• Privacy contact: privacy@littlewatch.app
• Support contact: support@littlewatch.app
• Legal contact: legal@littlewatch.app

2. Important safety and privacy notice

LittleWatch is intended for adult parents and caregivers. It is not directed to children, and children should not create accounts, configure devices, purchase subscriptions, or contact support.

LittleWatch is a convenience monitoring app. It is not a medical device, life-safety device, certified baby monitor, emergency alert system, or substitute for adult supervision.

3. Information we process

The exact information depends on the features and connection mode you use. We aim to minimize cloud processing and avoid storing video or audio content on LittleWatch servers unless a future paid cloud recording feature is expressly enabled and separately disclosed.

• Stream routing data: stream UUIDs, server assignment, connection method, pairing verification data, room state, viewer/source roles, timestamps, and connection events.
• Device and app data: device ID generated by the app, device name chosen by the user, platform, operating system version, app version, device model where available, language, region selection, battery/status values where enabled, and basic diagnostics.
• Network data: IP address, approximate country or region derived from IP or user-selected region, request timestamps, user agent for web viewers, and server logs needed for security and reliability.
• Subscription and purchase data: product IDs, subscription status, store receipt or purchase token validation data, linked device counts, and license-sharing metadata. Payment card details are handled by Apple, Google, or the relevant app store/payment provider and are not stored by LittleWatch.
• Ads data: if the free version shows ads, advertising providers such as Google AdMob may process advertising identifiers, approximate location, device information, consent signals, and ad interaction signals under their own policies.
• Local app data: saved cameras, trusted viewer devices, baby/child profiles, tracker entries, snapshots, recordings, event history, lullaby choices, settings, thumbnails, and exports may be stored locally on your device.
• Optional media and content: if you take snapshots, record clips, attach baby tracker photos, import lullabies, or export a ZIP, those files remain local unless you choose to share them or a future cloud feature is enabled.
• Support communications: if you contact us, we process your email address, message content, attachments, platform, app version, and any diagnostics you choose to send.

4. Camera, microphone, storage, network, Bluetooth and notification permissions

LittleWatch requests permissions only when needed for a feature. Denying a permission can disable the related feature.

• Camera and microphone are used to stream video/audio and support two-way talk.
• Local network, Wi-Fi, hotspot, Bluetooth or nearby-device permissions may be used for local discovery, direct connection, casting, watch support, or compatible sensor/device discovery.
• Storage, photos, media or file permissions may be used for snapshots, recordings, lullabies, tracker photos and exports.
• Notifications may be used for sound, motion, connection, subscription or system alerts.
• Location or approximate region may be used only where required by the operating system for local network/Bluetooth discovery or for selecting a nearby stream server.

5. Ads, Firebase, analytics, identifiers, crash reporting, payments and streaming

For clarity, LittleWatch may use or integrate the following categories of services and data processing depending on platform, region, consent choices, subscription status and the features you use.

• AdMob: Google AdMob may be used to show ads in the free version and may process advertising identifiers, device information, approximate location, consent status and ad interaction signals under Google and platform policies.
• Firebase and analytics: Firebase or similar analytics/diagnostic services may process app events, app version, platform, device identifiers, device model, operating system version, language, region, performance data and aggregate usage statistics to understand reliability and improve the app.
• Crash reporting: Firebase Crashlytics or similar crash reporting services may process crash logs, stack traces, device identifiers, app version, operating system version, device model and diagnostic context to fix bugs and improve stability.
• Device identifiers: LittleWatch may use app-generated device IDs, trusted-device IDs, push tokens, platform advertising identifiers where permitted, subscription/license identifiers and pairing identifiers for security, trusted viewers, subscriptions, fraud prevention, diagnostics and abuse prevention.
• Subscriptions and Google Play payments: on Android, subscriptions and payments are handled by Google Play. LittleWatch may receive product IDs, purchase tokens, subscription status, renewal/cancellation state, validation responses and license-sharing metadata, but does not receive or store payment card details.
• Camera and microphone use: the app uses the camera and microphone when you start a camera stream, listen/talk, record, take snapshots, scan pairing codes or grant related permissions. Camera/microphone data is not used for unrelated purposes.
• Realtime streaming: video, audio, talk-back audio, stream status, viewer presence and signaling messages may be processed in realtime through LittleWatch cloud servers, local network/direct connections, web viewers or custom servers depending on the connection mode you select.

6. Video, audio, snapshots and recordings

By default, LittleWatch cloud servers are designed to route/signaling stream sessions and transfer live data, not to store cloud video streams, audio streams, snapshots, or recordings.

Local screenshots, recordings, thumbnails, baby tracker photos and exports are stored on the device or in the storage location you choose. If you share them using the operating system share sheet, the receiving app or service processes them under its own policies.

If we later add paid cloud playback, event clips, or cloud storage, that feature must have separate in-app disclosure, storage controls, retention settings and updated privacy terms before release.

7. How we use information

• Provide camera streaming, viewer access, QR/manual pairing and connection routing.
• Authorize trusted viewer devices and enforce pairing/security checks.
• Operate cloud, local network, direct and custom server connection modes.
• Validate purchases, manage subscriptions and enforce sharing limits.
• Show ads in the free version, where enabled and permitted by consent and platform rules.
• Send alerts, status updates, quality indicators and service messages.
• Protect against stream guessing, unauthorized access, abuse, fraud, spam and security attacks.
• Maintain logs, troubleshoot bugs, improve reliability, and understand aggregate usage.
• Comply with law, app-store rules, tax/accounting obligations and legal requests.

8. Legal bases where GDPR/UK GDPR applies

• Contract: to provide the app, streaming, pairing, subscriptions, support and requested features.
• Legitimate interests: security, abuse prevention, diagnostics, service reliability, non-invasive analytics and business administration.
• Consent: optional permissions, personalized ads where required, marketing messages where used, and optional features that need explicit approval.
• Legal obligation: tax, accounting, consumer protection, lawful requests and compliance duties.
• Vital interests: LittleWatch is not intended for emergency use and should not be relied on for life-safety monitoring.

9. Sharing with third parties

We do not sell video or audio streams. We may share limited data with service providers that help operate the app.

• Cloud hosting, routing, database, logging, security and infrastructure providers.
• App stores and payment processors for purchases, subscriptions, refunds and receipt validation.
• Advertising and consent providers for free-tier ads, subject to platform rules and user consent choices.
• Analytics, crash reporting or diagnostic providers if enabled for the app.
• Email/support tools used to answer user requests.
• Law enforcement, regulators, courts or legal advisors where required by law or to protect rights and safety.
• A buyer, successor or affiliate if LittleWatch is involved in a merger, acquisition, financing, restructuring or sale, subject to appropriate privacy protections.

10. Custom servers, local network and direct mode

When you use local network, direct connection, casting or a custom/self-hosted streaming server, the privacy and security of the connection may depend on your network, device settings, operating system permissions, router/firewall configuration, SSL/TLS setup and the third-party or self-hosted server you choose.

LittleWatch cannot control, audit or guarantee third-party custom servers, local networks, DNS, Wi-Fi hotspots, routers, VPNs or browser extensions.

11. Children and COPPA-style protections

LittleWatch is for parents and caregivers, not for use by children. We do not knowingly collect personal information directly from children under 13 or the applicable digital-consent age.

Because the app can process information about a baby or child, parents and guardians are responsible for deciding what they record, store, export, share, or enter in child profiles and tracker notes. If you believe a child provided personal information directly to us, contact privacy@littlewatch.app so we can review and delete it where required.

12. Retention

• Live stream content: not intentionally stored on LittleWatch cloud servers by default.
• Routing/session logs: kept only as long as reasonably needed for operation, security, abuse prevention and diagnostics.
• Subscription/license records: kept while the subscription or shared license is active and for a reasonable period needed for audits, disputes, fraud prevention and legal obligations.
• Support emails: kept as long as needed to handle the request and maintain support history.
• Local data: remains on your device until you delete it, uninstall the app, clear app data, or delete/export files using operating system tools.
• Backups: deleted on a rolling schedule according to infrastructure backup practices.

13. Security

We use technical and organizational safeguards designed for a baby-monitoring app, including UUID-based stream identifiers, pairing codes, rate limiting, role checks, blocked-device support, HTTPS/WSS/TLS in production, and restricted admin access.

No internet, Wi-Fi, Bluetooth, browser, device or cloud system is perfectly secure. You are responsible for keeping devices updated, using trusted networks, protecting QR codes and pairing codes, approving only trusted viewers, and securing custom servers.

14. Your choices and rights

• Change app settings, language, region, connection method, permissions, trusted viewers and local storage settings.
• Delete saved cameras, trusted devices, child profiles, tracker entries, snapshots, recordings and exports from the app or operating system storage.
• Request access, correction, deletion, restriction, portability or objection where privacy law grants those rights.
• Withdraw consent for optional permissions or personalized ads where applicable.
• Cancel subscriptions through the relevant app store account settings.
• Contact privacy@littlewatch.app for privacy requests. We may need to verify your identity and device/license relationship before acting.

15. International transfers

LittleWatch services and providers may operate in multiple countries. Where required, we use appropriate safeguards such as contractual protections, data processing agreements and regional configuration options.

16. Changes to this policy

We may update this policy when features, laws, providers or business operations change. Material changes should be communicated in the app or on the website. The effective date shows when this policy was last updated.