Privacy, Terms & Support

Choose an app to find its privacy policy, terms and support information. Existing legal URLs remain available for bookmarks and store listings.

Study Beats Privacy Policy

Last updated: 3 October 2026

Who we are

Study Beats is published by Gobias Ltd. You can contact us at gobiasltd@gmail.com.

Optional usage analytics

If you choose Share usage data, Study Beats uses Google Analytics for Firebase to understand how people use the app and improve it. Collection is off by default and is enabled only after consent in an eligible production App Store build. Ordinary TestFlight builds do not send production Firebase analytics. You can change your choice later in Settings.

Our custom events can cover:

• screens and features used, and time spent while the app is in the foreground;
• public music-package and lesson identifiers;
• practice-completion, recording and export outcomes;
• import attempts and outcomes, including fixed failure categories;
• requests for Pro features and the places from which a paywall is opened; and
• subscription-action outcomes.

When Analytics is enabled, Firebase can also collect automatic app lifecycle and session events alongside those custom events. Supported automatic StoreKit purchase and subscription events may include product identifiers, product names, currency and prices. Automatic screen reporting is disabled in Study Beats, but that does not disable the other supported automatic events.

With the same optional agreement, Study Beats requests Apple Ads attribution information from Apple. When Apple makes it available, the app sends campaign, ad-group and keyword identifiers, attribution status, and recognised attribution and conversion types to Firebase and RevenueCat. We use this information to understand which advertisements lead to useful app activity and subscription results. We do not send subscription conversions back to Apple Ads, use this integration to target advertising or track you across other companies’ apps, or automatically change advertising campaigns or bids.

Identifiers and technical information

Firebase uses a pseudonymous app-instance identifier for a particular installation of Study Beats. It also processes technical information such as app version, device model, operating system and language. Google Analytics can derive general location from a masked IP address; Study Beats does not use Apple Location Services for analytics.

We do not set a Google Analytics user ID or send a name or email address to Analytics. The app’s Firebase configuration disables collection of Apple’s advertising identifier and vendor identifier. The Apple attribution token is used only to request attribution information from Apple and is not stored in analytics. Because Firebase assigns an app-instance identifier, this data is pseudonymous rather than fully anonymous. That Firebase installation identifier is not sent to RevenueCat.

What our custom analytics events exclude

The custom event calls inspected for this release do not include:

• recordings or audio files;
• lyrics, user-entered titles or file paths;
• pitch measurements or lesson scores; or
• raw error messages.

The app reports fixed outcome codes rather than raw error text. Your recordings, lyrics and song titles stay on your device unless you explicitly choose to export or share them. The current AWS implementation downloads app content and does not provide a path for uploading your recordings.

Subscriptions and RevenueCat

Study Beats uses RevenueCat to provide subscription features independently of your Firebase Analytics choice. Because the app does not supply a custom account identifier, RevenueCat generates and stores a random, pseudonymous App User ID for the installation. RevenueCat processes App Store receipts and purchase history, subscription status and entitlements so the app can provide Pro access, restore eligible purchases and show subscription analytics such as customer history and charts.

If you agree to share usage data and Apple provides attribution information, RevenueCat associates the app’s custom campaign, ad-group, keyword, attribution-status, attribution-type and conversion-type attributes with that existing pseudonymous customer record. This helps us compare advertising effectiveness with subscription results. The app does not send RevenueCat the Firebase app-instance identifier.

Apple processes the purchase and billing through the App Store. Turning off optional Firebase Analytics does not stop Apple or RevenueCat from processing information needed to purchase, validate, restore or manage a subscription.

Content delivery through AWS

Study Beats uses Amazon Web Services, including Amazon Cognito and Amazon S3, to deliver catalogues, announcements, previews and tracks. The app obtains a pseudonymous Cognito guest identity and temporary, limited AWS credentials so it can request these files. AWS necessarily processes technical request information such as IP address, request time, requested object and response or error details to deliver and secure the service.

AWS services can retain operational or security logs when the relevant server-side logging is enabled. The app code does not establish which AWS logs are enabled, so we do not claim a particular app-specific AWS log retention or deletion period. Turning off optional Firebase Analytics does not disable the AWS requests needed to provide downloadable app content.

Your choices

Analytics is off until you accept the app’s one-time choice. Choosing Not now keeps it off, and the app remembers your choice. You can change it later using Share usage analytics in Settings. Actions taken before you accept are not replayed later.

Turning sharing off stops future optional Firebase usage-analytics collection and resets Firebase Analytics data stored locally by the app. It also cancels pending app-controlled Apple Ads attribution work, clears locally cached campaign information and requests removal of the app’s custom campaign attributes from RevenueCat. A request that has already been sent cannot be recalled. Withdrawal does not erase historical information already received by Google, Apple or RevenueCat, and it does not erase subscription, transaction or service records held by Apple, RevenueCat or AWS. It also does not stop the processing needed to purchase, validate, restore or manage a subscription. You can email us at gobiasltd@gmail.com with questions or privacy requests.

Retention

The Google Analytics property was verified on 23 September 2026 as configured to retain event-level data for two months and user-level data for fourteen months. The user-level retention period restarts when Google Analytics receives new activity from the same app-instance identifier. These settings do not control how long data remains in standard aggregated Analytics reports.

Learn more in Google’s Firebase data collection and Analytics data retention documentation.

Service providers

• Google Firebase: optional usage analytics and consent-controlled measurement of Apple Ads effectiveness. See Firebase privacy and security.
• RevenueCat: subscription validation, entitlements and subscription analytics, plus consent-controlled custom Apple Ads campaign attributes used to compare advertising and subscription results. See RevenueCat’s privacy policy.
• Amazon Web Services: Cognito identity and credentials, and S3 content delivery. See the AWS Privacy Notice.
• Apple: App Store purchases, subscriptions and billing, and consent-controlled Apple Ads attribution requests. See Apple’s privacy policy.

Why we use analytics

• To understand which features are useful and where people spend time.
• To understand whether practice, recording, export and import flows work as intended.
• To understand which Pro features people request, where paywalls are opened and the outcomes of subscription actions.
• With consent, to measure which Apple Ads campaigns lead to useful sessions and subscription results, without using the integration for advertising targeting or cross-app tracking.
• To make informed product decisions.

Children

Study Beats isn’t directed to children under 13. If you believe a child provided us information, please contact us and we’ll assist.

Changes

We may update this policy. We’ll change the “Last updated” date above and, where appropriate, notify users in the app.

For App Store submission, Apple requires a publicly accessible Privacy Policy URL. This page fulfills that requirement.