プライバシーポリシー

1. Introduction

Hush ("we," "us," "our," or "the App") is a baby sleep assistant application developed by Efkan Turen, an independent developer based in California who publishes under the name Efkan Works. This Privacy Policy explains how we collect, use, and protect information when you use the Hush mobile application and related services (collectively, the "Service").

Our core principle: Hush processes audio entirely on your device. We do not record, transmit, or store any audio data on external servers.

By using Hush, you agree to the practices described in this Privacy Policy. If you do not agree, please discontinue use of the App.

2. Information We Do NOT Collect

Unlike many baby monitor applications, Hush does not collect the following:

• Audio recordings from your microphone
• Video or camera data
• Your precise geolocation
• Contact lists, photos, or personal files
• Browsing history or usage data from other applications
• Biometric data of any kind

3. How Audio Processing Works

Hush uses on-device artificial intelligence for cry detection:

1. The microphone captures short audio snippets (approximately 1 second) into temporary device memory (RAM).
2. The on-device AI model (TensorFlow Lite) analyzes the audio locally on your device.
3. Audio data is immediately discarded from memory after analysis — typically within one second.
4. Only a binary signal ("cry detected" or "no cry detected") is generated and used to trigger actions such as auto-soothe playback or parent alert notifications.

No audio data is ever recorded, stored, transmitted to any server, cloud service, or third party. The AI model runs entirely within your device's processor and does not require an internet connection to function.

4. Optional Account System

Hush offers an optional account system for users who wish to share their premium subscription across multiple devices.

4.1 Account Creation

• You may use Hush without creating an account. All core features (sound playback, cry detection, device pairing) work without sign-in.
• If you choose to create an account, you may sign in using Sign in with Apple or Sign in with Google.
• We do not offer username/password-based registration.

4.2 Information Collected Upon Sign-In

When you sign in with Apple or Google, we receive and store the following:

• Email address — for account identification and subscription sync
• Display name — for personalization within the App
• Unique user identifier (UID) — for internal account management
• Authentication provider — sign-in method reference

Note: When using Sign in with Apple, you may choose Apple's "Hide My Email" feature, in which case we receive only an Apple-generated relay email address.

4.3 How Account Data Is Used

• To synchronize your premium subscription across up to 3 devices
• To manage Family Premium Sharing groups (see Section 5)
• To provide account management features (sign out, delete account)
• We do not use your email address for marketing, newsletters, or promotional communications unless you separately opt in

4.4 Account Data Storage

Account data is stored in Firebase Authentication and Firestore (Google Cloud infrastructure) with encryption at rest and in transit. We retain account data only for as long as your account exists.

5. Family Premium Sharing

Hush allows premium subscribers to share their subscription with family members across up to 3 devices total (including the subscriber's own device).

5.1 How It Works

• The premium subscriber ("Owner") creates a Family Group and generates a 6-character invite code.
• Family members ("Members") enter the invite code on their own device to join the group.
• Invite codes expire after 24 hours and can be regenerated at any time.

5.2 Information Stored for Family Groups

The following information is stored in Firebase Firestore to manage Family Groups:

• Owner's user identifier and email address
• Each member's user identifier and display name
• Each member's device platform (iOS or Android)
• The invite code (temporary, expires after 24 hours)
• Group creation and membership timestamps

5.3 Cross-Device Premium Verification

To verify and synchronize premium status across devices, we communicate with RevenueCat (our subscription management provider) using your Firebase user identifier. RevenueCat checks subscription status — no audio, personal files, or device content is shared.

5.4 Leaving a Family Group

• Members may leave a group at any time through the App.
• Owners may remove members or dissolve the group entirely.
• When a group is dissolved or a member leaves, shared premium access is revoked immediately.

6. Information We May Collect

To provide and improve the Service, we may collect minimal, non-identifying information:

6.1 Anonymous Crash Reports

If the App crashes, anonymous diagnostic data (device type, OS version, crash stack trace) may be collected via Firebase Crashlytics. This data contains no personal identifiers and is used solely to fix bugs.

6.2 Subscription Data

All payment processing is handled entirely by Apple (App Store) or Google (Play Store). We do not have access to your credit card, bank account, or payment details. We receive only a transaction confirmation and subscription status through RevenueCat.

6.3 Anonymous Analytics

We may collect anonymized, aggregated usage data (e.g., which sounds are most popular, general session duration) to improve the App. This data cannot be linked to any individual user.

6.4 Push Notification Tokens

If you enable parent alerts (device pairing) or use Family Premium Sharing, Firebase Cloud Messaging tokens are used to deliver notifications. These tokens are device-specific and are not linked to personal identity for users who have not signed in. They are stored in the pairing session described in Section 7.

7. Device Pairing (Parent Alerts)

When you pair two devices using a QR code:

• A pairing session is created and stored in Firebase Firestore (Google Cloud, United States). It contains anonymous device identifiers, the notification tokens of the paired parent devices, device names (on Android, the name set on the device, which may include your name; the baby device can rename paired devices in the App), the App's language and version, Smart Nanny's status with timestamps (for example, when a cry was last detected), and the date the App was last used. It never contains audio.
• Only a "cry detected" signal (not audio) is sent between paired devices via Firebase Cloud Messaging.
• The baby device shows the names of the paired parent devices. No other personal information is exchanged between paired devices.
• You can unpair at any time by disconnecting in the App.

Pairing and account sign-in are independent features. You do not need to sign in to use device pairing, and signing in does not automatically pair devices.

8. Third-Party Services

Hush uses the following third-party services, each with their own privacy policies:

• Firebase Authentication — Optional account management. Google Privacy Policy
• Firebase Firestore — Pairing sessions and family group data storage. Google Privacy Policy
• Firebase Cloud Messaging — Push notifications. Google Privacy Policy
• Firebase Crashlytics — Anonymous crash reporting. Google Privacy Policy
• RevenueCat — Subscription management. RevenueCat Privacy Policy
• Apple App Store / Apple Sign-In — App distribution, payments, and optional authentication. Apple Privacy Policy
• Google Play Store / Google Sign-In — App distribution, payments, and optional authentication. Google Privacy Policy

We do not sell, rent, or share your personal information with any third parties for advertising or marketing purposes.

9. Children's Privacy

Hush is designed as a tool for parents and caregivers — it is not intended for use by children. The App does not knowingly collect any personal information from children under the age of 13 (or the applicable age in your jurisdiction).

• The App is operated by the parent or caregiver, not by the child.
• Audio captured for cry detection is processed transiently in device memory and is never stored or transmitted.
• If you believe we have inadvertently collected personal information from a child, please contact us immediately at support@hush-baby.app, and we will promptly delete such information.

10. Data Retention

• Audio data: Never stored — discarded from RAM within ~1 second
• Account data (email, name, UID): Until you delete your account
• Family group data: Until the group is dissolved or you leave
• Anonymous crash reports: Automatically deleted after 90 days
• Push notification tokens: Until you unpair the device or the pairing session is deleted
• Pairing sessions: Deleted automatically 7 days after last use if no parent device is paired, otherwise after 90 days without use. A device you unpair is removed from the session immediately.
• Alert records: A one-way hash of the notification token and the time of the last alert, kept for 24 hours to prevent duplicate alerts; server logs that include the pairing session identifier, kept for 30 days.
• Subscription records: Maintained by Apple/Google and RevenueCat per their policies

11. Account Deletion

You have the right to delete your account at any time. Open Hush → Settings → Account → "Delete Account" and confirm. Upon account deletion:

• Your Firebase Authentication account is permanently deleted
• Your Family Group is dissolved (if you are the Owner) or you are removed (if you are a Member)
• All associated Firestore data (family group records) is deleted
• RevenueCat subscription association is reset
• This action is irreversible. Your existing App Store or Google Play subscription continues until its expiration — manage cancellation through your device's subscription settings.

For step-by-step instructions, visit: hush-baby.app/delete-account

12. Your Rights

Depending on your jurisdiction, you may have rights regarding your personal data, including access, correction, deletion, portability, and objection. Since Hush collects minimal personal data (account data if you create one, and pairing data if you use parent alerts), many data-related requests may not be applicable. To exercise any of these rights, contact us at support@hush-baby.app.

California Residents (CCPA): We do not sell personal information. You may request disclosure of the categories and specific pieces of personal information we have collected.

European Residents (GDPR): Our legal basis for processing personal data is your consent (for account creation), the performance of our contract with you, that is, providing the service you request (for pairing and parent alerts; Art. 6(1)(b) GDPR), and legitimate interest (for crash reporting, short-term server logs and app improvement; Art. 6(1)(f) GDPR). You may withdraw consent at any time by deleting your account. You may object to processing based on legitimate interest, and you have the right to lodge a complaint with your local data protection authority.

13. International Data Transfers

If you create an account, your account data may be processed and stored on servers located in the United States (Google Cloud / Firebase infrastructure). Pairing data (Section 7) is also stored on Google Cloud servers in the United States, whether or not you create an account.

For personal data of people in the European Economic Area, the United Kingdom and Switzerland, we rely on the adequacy decisions for the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework, under which Google LLC is certified; Google's data processing terms also provide for Standard Contractual Clauses if that framework no longer applies. Subscription status is handled by RevenueCat, Inc., which stores data on servers in the United States; RevenueCat's data processing addendum incorporates the EU Standard Contractual Clauses, with the UK addendum, for personal data transferred from the European Economic Area, the United Kingdom and Switzerland. You can ask us for more information about these safeguards at support@hush-baby.app.

14. Security

We employ industry-standard security measures: TLS/SSL encryption in transit, AES-256 encryption at rest in Firebase, OAuth 2.0 authentication, and 24-hour expiry on family group invite codes. On-device audio processing eliminates the largest potential attack surface entirely. No system is 100% secure, and we cannot guarantee absolute security.

15. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date at the top of this page and notify users through the App or our website. Your continued use of the App after changes are posted constitutes your acceptance of the updated Privacy Policy.

16. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy, please contact us at:
support@hush-baby.app
Efkan Works, California, United States