earbiteBack to Earbite ↗

Privacy Policy

Updated 13 November 2026

A clear account of the information Earbite uses, where it lives, and the choices you have.

Who we are

Earbite is operated by Nextkey Inc. This policy covers the Earbite iOS and Android apps, earbite.app and our creator workspace at studio.earbite.app. Nextkey Inc. is responsible for the personal information described here.

For privacy questions or requests, email benchappteam@gmail.com.

Information in the app

You can use the listening app without providing a name, email address or password. After the onboarding questions, Firebase creates a guest account with a random identifier. That identifier still lets us recognise the same account; guest data is not fully anonymous.

On iOS, you can secure that account with Sign in with Apple or Google, or sign in to an existing Earbite account. The current Android app uses guest accounts and does not offer those sign-in options. Firebase receives the provider account identifier, available name and email address; Apple may provide a private relay email. Linking keeps your Earbite account identifier, coins, saves and progress. Signing in does not give Earbite access to your Gmail messages or Google Drive files.

  • Profile preferences: your selected gender, favourite genres, listening mood and usual listening moment. The gender question includes “Prefer not to say.”
  • Account and purchase records: your Earbite identifier, linked sign-in providers and available profile information, a separate purchase-service identifier, account timestamps, coin balance, episode unlocks, product and transaction identifiers, purchase tokens, purchase or refund status, and subscription access and expiry.
  • Contact Us submissions: your selected category, message, optional reply email and story or episode reference, and app version and build. These submissions are stored privately in Firebase with your Earbite account identifier to handle feedback and support requests.
  • Technical information: our hosting and service providers process information such as IP addresses, app and operating-system versions, device or installation identifiers, language and region settings, request times and error information to deliver and secure the service. Superwall derives approximate city, country and region from IP addresses for service delivery and reporting. The listening apps do not request GPS location or device-location permissions.
  • Purchase-screen activity: Superwall receives device and account identifiers, purchase information and SDK events such as app launches, offer views and checkout outcomes for subscription delivery, reporting and offer measurement. Where available, this can include app-install attribution information.

Saved stories and listening progress

Saved stories and episodes, save dates, episode listening positions and times, audio sections heard and completion status are stored in Firebase under your Earbite account identifier. The app keeps a local copy and queues changes when offline. We use this information to restore your place and calculate aggregate story and episode save and play counts.

Playback speed, autoplay and caption preferences stay on your device. Artwork, transcripts and other service data may also be cached locally. Audio playback requests identify the story and episode to check access and stream it.

The sound animation analyses the story audio being played. It does not record you or access your microphone. Word timing is prepared from uploaded story audio and scripts, not from listeners’ voices.

Advertising measurement on iOS

The iOS app uses AppsFlyer to understand which Earbite advertisements lead to app installs, app opens and purchases. AppsFlyer processes device and installation identifiers, app and session activity, device and app technical information and IP addresses. This includes Apple’s identifier for vendors and an AppsFlyer installation identifier. Apple’s advertising identifier is accessed only when you allow tracking through iOS.

We send completed coin and subscription purchase events with the product identifier, transaction identifier, quantity, purchase type and, when available, the actual amount and currency. Our AppsFlyer integration does not pass your Firebase account identifier, name, email address, phone number, onboarding preferences or story-listening history.

AppsFlyer connects to TikTok for Business to measure our advertising. With tracking permission, install and app-open information can be matched with TikTok advertising interactions. Our purchase postbacks are configured for purchases attributed to TikTok and include their event values and revenue. TikTok may use received information under its own privacy policy to measure, optimise and personalise advertising. Advanced matching using contact information is not enabled.

If you do not allow tracking, the iOS app disables advertising-identifier collection. Privacy-preserving measurement, such as Apple’s SKAdNetwork, and permitted app analytics may still operate. Allowing or refusing tracking does not change your access to stories, coins or subscriptions.

This advertising-measurement sharing may be treated as “sharing” or targeted-advertising processing under some US state privacy laws. You can change the iOS tracking permission and contact us to exercise applicable opt-out or deletion rights.

The website and Studio

The public landing and legal pages do not require an account and do not include advertising pixels or a visitor-analytics SDK. Hosting still processes ordinary web-request information, including IP addresses, browser information, requested pages and response details.

Studio is restricted to approved editors. Google sign-in provides Firebase with your account identifier, email address and available basic profile information. We use your verified email and account identifier to control access and attribute uploads and agent approvals. Signing in does not give Earbite access to your Gmail messages or Google Drive files.

Studio stores the selected folder’s files, file names, sizes, hashes, import status and editor identity to prepare and review a story. Files remain private during preparation; publishing makes the story available to listeners under the app’s access rules. Only upload material you have permission to use.

Studio uses browser storage to maintain sign-in and resume an import. The optional agent tool stores a sign-in credential and upload state on the computer where you run it. You can sign out of Studio or use the tool’s logout command to remove its saved credential.

Studio uses Firebase App Check with Google reCAPTCHA Enterprise to verify browser requests and prevent abuse. Google processes browser and device signals for that verification. The public landing and legal pages do not load reCAPTCHA.

How we use information

We use account and purchase information to operate Earbite, deliver stories, verify subscriptions, credit coins, preserve episode unlocks and prevent duplicate or fraudulent purchases. We store onboarding answers as profile preferences and use technical and offer information to maintain, measure and improve the service. If you contact us, we use your message and any reply email or story details you provide to handle your request and improve the service.

Where EU or UK data-protection law applies, our bases include performing our agreement with you for accounts and purchases; our legitimate interests in service security, reliability, support and proportionate improvement; and legal obligations for required records. Profile preferences are used for our legitimate interest in understanding listener preferences. Where a particular use requires consent, including device-level advertising tracking, we rely on that consent rather than treating use of this policy as consent.

We do not use automated processing to make decisions with legal or similarly significant effects on you.

Services that help us run Earbite

Google Firebase and Google Cloud provide authentication, the database, media storage, app configuration, hosting and backend processing. Firebase Remote Config uses an installation identifier to deliver app configuration.

Firebase App Check processes app or device attestation material and short-lived tokens to protect service access. The iOS app uses Apple’s device-attestation services; the Android app uses Google Play Integrity; Studio uses Google reCAPTCHA Enterprise. These checks verify the app, device or browser and do not record story audio or use your microphone.

Superwall provides purchase screens, subscription and purchase validation where supported, entitlement information and related SDK reporting. Apple processes App Store payments and manages App Store subscriptions on iOS; Google processes Google Play payments and manages Google Play subscriptions on Android. For Android purchases, Earbite sends purchase tokens and product information to our backend to verify them with Google Play before crediting coins or granting subscription access. Signing in to a linked Earbite account can restore its subscription access, coin balance and episode unlocks. Earbite does not receive or store your full payment-card number.

We may disclose relevant information to authorised service providers, to comply with law, to protect people and the service, or in a business transfer subject to appropriate protections. Earbite does not show third-party ads. The iOS advertising-measurement sharing with AppsFlyer and TikTok is described above; it is used to measure our own advertising.

External services and links have their own privacy notices, which explain their separate handling of information.

Firebase privacy information ↗Superwall privacy information ↗AppsFlyer privacy information ↗TikTok privacy information ↗Apple privacy policy ↗

Storage, retention and security

Our application database and media are hosted in the United States. Google, Apple, Superwall, AppsFlyer and TikTok may also process information in other countries where they or their providers operate. For transfers subject to EU or UK requirements, applicable provider data-processing terms include safeguards such as standard contractual clauses. Contact us for information about the safeguards relevant to your data.

We keep profiles, saved stories and episodes, listening progress, wallet balances and unlock records to maintain your account and access. These records do not currently expire automatically when you stop listening. Purchase and fraud-prevention records may need to remain longer for accounting, legal requirements or disputes. Retention depends on the record’s purpose, account status, applicable obligations and any valid deletion request.

Temporary Studio import files are scheduled for deletion after seven days. Agent-approval records are scheduled for deletion after one day, and an unused approval link expires after five minutes. Published story files remain while needed for the catalog. Provider backups and logs can follow separate retention schedules, and scheduled deletion may not be immediate.

We use encrypted connections, authenticated access and restricted server permissions. No internet service or storage system can guarantee complete security.

Your choices and rights

You can remove saved stories or episodes and change listening settings in the app. You can sign out of a secured account or choose Delete Account in the Profile tab. Deletion removes the Firebase sign-in account, profile, saved items, listening history, wallet, unlocks and feedback submissions from our application database. Apple sign-in access is revoked when deleting an Apple-linked account. If a request is interrupted, cleanup retries and the app offers a deletion retry.

We retain aggregate story play totals and minimal purchase records with account and provider identifiers removed to prevent a receipt being credited twice. We temporarily retain your Superwall identifier in a private deletion-request record only to request and follow through on erasure of associated provider data. Our team handles that request manually and removes the identifier after Superwall confirms completion. Our providers may retain records under their own policies, and backups or logs may follow separate retention schedules. Clearing app data or browser storage does not itself delete server records or cancel an App Store or Google Play subscription.

On iOS, you can change tracking permission in Settings > Privacy & Security > Tracking. Withdrawing that permission restricts future device-level advertising tracking; it does not automatically erase previously collected provider records. For advertising-measurement data requests, contact us so we can help identify the relevant device record and coordinate the request with the provider.

Depending on the law where you live, you may request access, correction, deletion, a portable copy or restriction of your personal information. You may also object to processing based on legitimate interests, withdraw any applicable consent and complain to your local data-protection authority. Applicable US state rights may include an appeal of a refused request. We do not discriminate against you for exercising privacy rights.

Contact us with your request if you need help. For an unsecured guest account, we may need information from your app session or purchase receipt to locate and verify the correct account. Keep that session available while we help. Do not send passwords, authentication tokens or full payment-card details.

We respond within the deadlines required by applicable law. Some records may be retained where permitted or required by law; we will explain relevant limits. Deleting an account removes its coins and episode access, and does not cancel an App Store or Google Play subscription.

Children and policy updates

Earbite’s minimum age is 13, or the higher minimum age required locally. The iOS app and website use this 13+ eligibility policy; the Android app is recommended for older teens and adults aged 16 or older. Users below the local age of adulthood need a parent or guardian’s consent and supervision. We do not knowingly collect personal information from children under 13. If you believe a child has provided it, contact us so we can investigate and take appropriate action.

We may update this policy as Earbite changes. The date above identifies the current version. We will provide an appropriate notice of material changes and obtain consent where legally required.

TermsPrivacy