Version 2026-08-23 · Effective August 23, 2026

Privacy Policy

This Policy explains how Hummingly, the developer or service operator identified in the applicable app-store listing (“Hummingly,” “we,” “us,” or “our”), collects, uses, discloses, protects, and deletes information in its apps, website, and related services.

At a glance

• Hummingly is directed to and available only to people age 18 or older.
• Your birth date is used for a single eligibility decision and is not retained or used for advertising, personalization, or analytics.
• Google Gemini processes content for lyrics and safety; Google Lyria 3 processes approved lyrics and style to create SynthID-watermarked music.
• Apple or Google processes purchases. Hummingly receives signed transaction identifiers, product, status, renewal period, and expiration—not your full payment-card details.
• We do not sell personal or consumer health data or use it for cross-context behavioral advertising.

1. Information we collect

Eligibility and legal records

Before login, you enter a date of birth and separately confirm adult eligibility, accuracy, agreement to the Terms, and acknowledgement of this Policy. The raw date is securely transmitted for one request, evaluated in memory, and discarded. We store a one-way, short-lived proof while the flow completes and retain the eligibility result, acceptance timestamp, and policy version identifiers. We do not retain the birth date or calculated age.

Account and profile

We may process an account identifier, email, display name, username, password hash, Apple or Google sign-in identifier, guest status, preferences, notification tokens, device/app details, and account-security records. Passwords are hashed, not stored in plaintext.

Membership and purchase records

For App Store and Google Play subscriptions, we process the store platform, product and base-plan identifier, original and current transaction or purchase-token identifiers, start and expiration dates, environment, renewal or lifecycle status, acknowledgement state, an account-binding token or one-way account hash, and verification time. We store creation-allowance counters by account and period. Administrators may record a selected complimentary plan, optional expiration, and internal support reason. Apple and Google process payment credentials and billing details under their policies; Hummingly does not receive your complete payment-card number.

Creative, library, and sharing data

We process affirmations, prompts, provided and generated lyrics, titles, styles, presets, generated audio, karaoke timing, favorites, playlists, history, playback state, and library metadata. For private sharing, we process sender and recipient identifiers, usernames used for lookup, invitations, tokenized access records, delivery state, acceptance, revocation, blocks, reports, and the protected copy needed for in-app streaming. Links do not embed playable audio.

If you flag generated lyrics or music, we process your account identifier, the content category, reason, optional song reference, optional details you choose to provide, review status, and an internal resolution note. The report record does not create another copy of the lyrics or audio. Do not place passwords, private links, or unnecessary sensitive information in report details.

Wellness and health data

With permission, we process eligible playback duration and wellness-minute records and may read or write limited mindful-session data through Apple Health or Android Health Connect. We do not use consumer health data for advertising or unrelated profiling. See the notice below.

Backup, sync, support, and operations

We process backup choice, provider status, last backup or sync time, cursors, conflict metadata, protected provider identifiers, support messages, diagnostics you choose to send, IP address, device/app version, security events, request timing, provider cost, rate-limit counters, crash data, and coarse logs. Logs are designed not to contain birth dates, raw creative text, authentication tokens, or song audio.

2. How we use information

We use information to validate eligibility and document acceptance; create, moderate, align, deliver, play, sync, back up, and privately share songs; verify purchases, provide entitlements, restore memberships, apply monthly allowances, prevent receipt reuse and fraud, and respond to refunds or expiration; calculate wellness minutes; protect against prompt injection, abuse, offensive content, and unauthorized access; provide support; operate reliably; comply with law; and improve features with aggregate or appropriately de-identified operational information.

3. AI generation, safety, and provenance

Inputs are normalized and isolated from model instructions. Hummingly checks for manipulation and inappropriate content before generation, uses strict provider safety settings, checks generated lyrics before Lyria, and checks returned text metadata and a temporary private transcript before delivery. The transcript is used for safety and alignment during the request and is not retained as a separate profile field. Requests may be rejected. Crisis signals may produce support resources instead of a song. Generated audio retains SynthID or other provider provenance.

Do not enter passwords, payment credentials, government identifiers, health records, or unnecessary sensitive information in creative fields.

4. Service providers and disclosures

Google AI request handling follows the applicable paid Gemini API terms and data-use commitments. Provider terms and preview offerings can change; we do not promise provider-level zero retention unless a binding commitment applies to our account and request.

We may disclose information at your direction, to comply with law, protect people or the Service, investigate fraud or abuse, respond to valid process, or complete a corporate transaction with appropriate safeguards. We do not sell personal information or share it for cross-context behavioral advertising.

5. Storage, security, and retention

Controls include transport encryption, account and recipient authorization, short-lived tokens, secret separation, signed store receipt validation, store lifecycle notifications, rate limits, prompt isolation, content checks, database constraints, transient delivery, deletion queues, and monitored backups. No system is perfectly secure.

• Date of birth: request memory only; not retained.
• Eligibility and legal proof: retained with the account as needed to document current acceptance.
• Purchase and entitlement records: retained for the account and as necessary for restoration, fraud prevention, tax/accounting, disputes, refunds, and legal compliance.
• AI-content reports: retained with the account while needed for safety review, policy enforcement, appeals, security, and legal obligations; deleted with the account unless a narrow legal or safety hold requires otherwise.
• Transient generated audio: deleted after confirmed device download or expiry, normally within 24 hours.
• Library Sync and private-share audio: retained while the feature or access is active, then deleted or queued for bounded cleanup, subject to security or moderation holds.
• Account/library records: retained while active and deleted or de-identified after a valid deletion request, subject to narrow legal, fraud, chargeback, security, and moderation obligations.
• Provider backups: controlled through iCloud or Google Drive and may remain until removed there.

6. Your choices and rights

You can edit profile information; manage or restore subscriptions; disable notifications, Library Sync, backup, and health permissions; revoke shares; remove songs; sign out; and request account deletion. Deleting a Hummingly account does not cancel a store subscription. Depending on location, you may request access, correction, deletion, portability, restriction, objection, or an appeal. We may verify identity and limit a request where law permits. Contact hello@hummingly.app or your regulator.

7. International processing and U.S. notices

Information may be processed in the United States and other provider locations. Where required for EEA, UK, and Swiss information, bases include contract performance, consent for optional health/provider features, legitimate security and operational interests, and legal obligations, with appropriate transfer safeguards.

For California notice-at-collection purposes, categories include identifiers, account/commercial information, internet or device activity, user content, and—with permission—wellness information. We use and retain them as described. We do not sell or share personal information for cross-context behavioral advertising or use sensitive information to infer unrelated characteristics.

9. Adults only

The Service is not offered to people under 18 because the Google AI API services used by Hummingly require an adult-directed client. The birthday check occurs before login and the raw date is not retained. If you believe an ineligible person used the Service or submitted information, contact us to investigate and delete as appropriate.

10. Changes and contact

Material updates may require a new acknowledgement tied to an immutable version. Prior accepted versions remain available at their versioned URLs.

Privacy requests: hello@hummingly.app. Support: Help & Support.