PRIVACY

Privacy Policy

Last updated: September 26, 2026

PrivacyTermsSupportContact

HummingLab is designed to keep your voice data on your device. This policy explains exactly when the microphone is used, what the app derives from your voice, what is saved, and how to delete it.

Who we are

HummingLab is a mobile application provided by HummingLab LLC, a New Jersey limited liability company (“HummingLab,” “we,” “us,” or “our”). This policy applies to the HummingLab mobile app and the HummingLab website.

App privacy at a glance

  • Microphone: used only for voice profiling and active guided humming.
  • Raw audio: analyzed momentarily on your device and not recorded, saved, or uploaded.
  • Voice and session data: voice-profile names, frequency measurements, session results, preferences, favorites, and route history remain on your device.
  • App analytics: Firebase Analytics records app opens, basic app and device information, purchases, and fixed steps in the app, without names, entered concerns, audio, voice measurements, or session results.
  • Subscriptions: Google Play and RevenueCat process limited purchase, subscription, identifier, and technical information needed to offer plans, verify purchases, restore purchases, and determine Premium access.
  • Ad measurement: Our Analytics property is linked to Google Ads so we can measure selected app conversions. The current Android app does not request the Android Advertising ID and disables Firebase ad-personalization signals. It does not display third-party ads.
  • Accounts: HummingLab does not currently require a HummingLab online account. RevenueCat assigns the installation an anonymous App User ID for subscription management.

Microphone access and processing

HummingLab asks for microphone permission because listening to your humming is necessary for its core pitch-feedback features. The microphone is used during a short voice-profile step and while an active guided humming round is listening for your voice. The app analyzes the incoming signal on the device to estimate pitch, frequency, harmonic relationship, signal quality, and whether the selected target has been sustained.

The app does not use speech recognition and does not create a transcript. Raw microphone samples exist only temporarily in working memory while analysis is occurring. HummingLab does not create or retain an audio recording, and raw audio is discarded as it is processed.

The app displays an active listening state while the microphone is in use. You can stop microphone processing by leaving the listening step, ending the session, closing the app, or revoking microphone permission in your device settings. Pitch-based features will not function without microphone permission.

Information stored locally on your device

The current app may store the following information in its local app storage:

  • a profile name you choose;
  • derived voice-profile measurements, such as estimated vocal range and usable frequency relationships;
  • pitch-performance and signal-quality results;
  • session history and route-performance history used to adapt later sessions;
  • favorites, preferences, and other app settings.

These items are used only to operate and personalize HummingLab on your device. They are not used for advertising, user tracking, eligibility decisions, or the creation of a marketing profile.

What leaves your device

HummingLab does not transmit raw microphone audio, voice recordings, profile names, voice-profile measurements, frequency results, humming-session results, favorites, routines, or route history to HummingLab, RevenueCat, Google Play, or another third party. These items are processed and stored locally on your device.

The Android app uses Google Analytics for Firebase to measure app opens and a limited set of fixed actions: starting onboarding, choosing an intention, starting or completing a voice profile, preparing a session, viewing the paywall, choosing a plan, starting or restoring a purchase, and completing a session. We send only the event name for these app-defined actions, without typed concerns, profile names, target frequencies, measured pitches, session results, microphone audio, or other free-text details. Analytics also records automatic app-lifecycle and screen events, and may record Google Play purchase and subscription events with product identifiers, product names, prices, and currency.

Firebase Analytics automatically uses an app-instance identifier and technical information such as app and operating-system versions and device characteristics. It derives coarse location from masked IP addresses; HummingLab does not request your device’s location permission. We do not supply a HummingLab profile name or account user ID to Analytics. These data help us understand app use, diagnose where people leave the signup or purchase flow, and measure subscription acquisition. We have linked this Analytics property to Google Ads and imported selected conversion events to evaluate advertising campaigns.

The current Android build blocks access to the Android Advertising ID and disables Analytics ad-personalization signals. It does not use your voice, entered concerns, or session history to build ad audiences. We will update this policy and the applicable app-store disclosures before enabling additional advertising identifiers, personalized app audiences, or other tracking in a later release.

When the app checks, purchases, restores, or manages a subscription, limited subscription-related information is transmitted to Google Play and RevenueCat. This may include an anonymous App User ID, the Firebase Analytics app-instance identifier, device type and operating system, product identifiers, Google Play purchase tokens, transaction information, subscription status, renewal or expiration information, and the last time the subscription service was accessed. The app sends the Firebase app-instance identifier to RevenueCat so subscription events can be associated with the same Analytics installation. RevenueCat may send subscription purchase and renewal events, including product and transaction value information, to Firebase Analytics for subscription reporting and Google Ads conversion measurement.

This information is used to display available plans, process and validate purchases, prevent purchase fraud, determine whether Premium access is active, restore purchases, provide subscription support, and produce subscription-service reporting. It is not used by HummingLab for behavioral advertising or cross-app tracking.

Payments are processed by Google Play. HummingLab and RevenueCat do not receive your complete payment-card or bank-account information.

For more information, see the Google Privacy Policy and RevenueCat Privacy Policy.

Your operating system may include app data in a device backup depending on your Apple or Google backup settings. Those backups are controlled by your device platform and account settings, not by HummingLab.

Third-party services in the mobile app

HummingLab uses the following third-party services:

  • Google Play Billing: processes subscription purchases, renewals, cancellations, refunds, and payment methods through the user’s Google Play account.
  • Google Analytics for Firebase: processes the app, device, lifecycle, fixed action, and purchase information described above for reporting and Google Ads conversion measurement.
  • RevenueCat: provides subscription infrastructure, purchase validation, entitlement status, purchase restoration, and subscription reporting. RevenueCat processes subscription-related information on HummingLab’s behalf.
  • React Native and Expo: provide the application framework, native-device functionality, and app updates. Update requests may include limited app, device, and installation information.

These services are not configured by HummingLab to receive raw microphone audio, voice profiles, frequency measurements, or humming-session history.

The current Android app includes Firebase Analytics for app measurement. It does not include an in-app ad-serving SDK or social-login SDK. If a future release adds a service that collects or transmits other data, we will update this policy and the applicable app-store disclosures before that release is distributed.

Retention and deletion of app data

Local app data remains on your device until you delete it. To remove one person’s information, open that person’s profile in HummingLab, choose the remove or delete option, and confirm. To remove all locally stored HummingLab data, use Menu → About & Privacy → Delete All Local Data, clear the app’s storage, or uninstall the app.

  1. To remove one person’s information, remove that profile within HummingLab.
  2. To remove every local profile and its app data, use Delete All Local Data in the app. On Android, clearing HummingLab’s storage or uninstalling it also removes local app data.

If your device restores HummingLab from a device backup, backed-up local data may also be restored. Manage or delete device backups through your Apple or Google account settings. HummingLab does not maintain a server-side voice-profile or humming-session database.

Deleting a profile, clearing HummingLab’s local storage, or uninstalling the app removes or makes inaccessible locally stored HummingLab information, but it does not cancel an active subscription or automatically delete purchase records maintained by Google Play or RevenueCat, or Analytics information already sent to Google. Google Analytics retains data according to the settings in our Analytics property and Google’s applicable rules. You can send us a privacy or deletion request using the contact options below; we will assess requests concerning data under our control, subject to applicable retention obligations.

Subscriptions can be managed or canceled through Menu → HummingLab Premium → Manage Subscription in HummingLab or through the user’s Google Play subscription settings. After cancellation, access generally continues through the end of the already-paid billing period, subject to Google Play policies and applicable law.

Google Play and RevenueCat may retain transaction and subscription records for as long as necessary to provide subscription functionality, maintain financial and security records, prevent fraud, resolve disputes, and comply with legal obligations. Privacy or deletion requests concerning information controlled by HummingLab may be submitted through our contact form. Some transaction records may need to be retained or may remain under the independent control of Google Play.

Website and support communications

The website does not access your microphone. If you submit our contact form, we receive the name, email address, subject, and message you provide. The website stores the submission so it can be delivered and answered. Website infrastructure may also process basic request information such as IP address, browser type, timestamps, and security logs.

Our website is hosted using Cloudflare infrastructure. Contact-form submissions are delivered through Google Apps Script and Google Workspace. Those providers process information on our behalf under their own terms and privacy commitments. We do not sell contact information or use it for targeted advertising.

We retain support and business correspondence only as long as reasonably necessary to respond, maintain business records, prevent abuse, and meet legal obligations. You may request deletion of a contact submission through our contact form, subject to records we must retain for legal, security, or dispute-resolution purposes.

Security

Keeping microphone and profile processing on the device limits exposure of voice information. We also use reasonable administrative and technical safeguards for information submitted through the website. No storage or transmission method can be guaranteed completely secure.

Children’s privacy

HummingLab is not directed to children under 13, and we do not knowingly collect personal information from children under 13. A parent or guardian who believes a child submitted information through the website may contact us to request deletion.

Changes to this policy

We may update this policy when the app, website, or applicable requirements change. We will post the revised policy here and change the effective date. Material changes to mobile-app data handling will also be reflected in the app and store disclosures as required.

Contact us

For privacy questions, deletion requests, or complaints, use our contact form and choose “Privacy or data request.” You may also write to HummingLab LLC, 971 US Highway 202N, Suite 6282, Branchburg, NJ 08876, United States.