Privacy Policy

Last updated: August 2026 — applies to BeatPoket 1.5.1

1. Information We Collect

BeatPoket separates stems on your device. We never receive your music. The only data that can leave your device is listed below, and the optional items are off until you turn them on:

  • Optional usage analytics: allowlisted in-app events, your language, platform, and OS and app versions (Amplitude, off by default)
  • Optional release performance: app start, bundle load, first render, navigation and update timings (Expo/EAS Observe, off by default)
  • Always on: critical JavaScript error reports, redacted before they are sent (Sentry)
  • Optional enhanced diagnostics: additional error context and in-app breadcrumbs, redacted (Sentry, off by default)
  • Purchase and subscription status, Premium entitlements, and a pseudonymous identifier (RevenueCat)
  • An operational update check when the app launches (Expo/EAS Update)

2. What Never Leaves Your Device

The following are processed only on your device and are never transmitted to BeatPoket, Amplitude, Expo, Sentry, or RevenueCat:

  • Your audio files and any stems produced from them
  • Track titles, artist names, album artwork, and durations
  • Your playlists and their names
  • File paths, file names, and content URIs
  • Your searches and library contents

Separation, mixing, and export run entirely on your device and work with no network connection. Route parameters that could carry this information — URIs, paths, file names, titles, artists, identifiers, searches, and tokens — are filtered out of performance metrics before they are sent.

3. Data Processing

All audio processing happens locally on your device. We do not upload, store, or have access to your music files. Your creative work remains entirely private. Purchases, app updates, and any telemetry you have consented to do use the network; audio never does.

4. Third-Party Services

We use the following third-party services:

  • Amplitude: optional usage analytics, enabled only with your consent (processed in Amplitude's EU region)
  • Expo / EAS Observe: optional release performance monitoring, enabled only with your consent
  • Expo / EAS Update: operational delivery of compatible app updates
  • Sentry: error monitoring, with redacted critical JavaScript errors always collected (processed in Sentry's EU region)
  • RevenueCat: purchase and subscription status and Premium entitlements
  • Apple App Store: payment processing and app distribution

5. Analytics (Amplitude)

Amplitude is optional and disabled by default. It is activated only after you consent, and you can turn it off at any time in Settings > Privacy & Data. When enabled, it receives:

  • Allowlisted usage events, such as starting a separation or opening a screen
  • Your language setting
  • Your platform and OS version
  • The app version

Our configuration explicitly disables country, enriched IP address, device model, device manufacturer, carrier, IDFA, IDFV, App Set ID, and other advertising identifiers. BeatPoket never sends your BeatPoket or RevenueCat identifier to Amplitude, so analytics usage is anonymous. Track and file metadata, paths, and raw error text are removed before any event is queued.

Usage events are retained according to the retention period configured for our Amplitude project and Amplitude's applicable terms. We do not state a fixed period here because it follows those settings.

6. Release Performance (Expo / EAS Observe)

EAS Observe is optional and follows the same Analytics consent as Amplitude: it is disabled before the app starts and dispatches nothing until you opt in. It measures how a release performs, not what you do with your music:

  • App start and launch timings
  • JavaScript bundle load time
  • Time to first render
  • Navigation timings between screens
  • Performance of over-the-air updates

Observe uses a pseudonymous identifier scoped to your installation. It persists across app updates and is reset when you uninstall and reinstall the app. It never receives a BeatPoket account identifier or a RevenueCat identifier. Route parameters carrying URIs, paths, file names, titles, artists, artwork, durations, identifiers, searches, or tokens are filtered out before dispatch. Development builds dispatch nothing.

Expo documents a minimum retention of 60 days for EAS Observe data.

7. App Updates (Expo / EAS Update)

When the app launches it performs a network check to see whether a compatible update is available. This is an operational function required to deliver fixes, not analytics, so it is not governed by the Analytics toggle.

  • The check sends only what is needed to identify a compatible update, such as the app's runtime version, platform, and release channel
  • It never sends audio files, stems, track metadata, or library contents
  • If there is no network connection, the app starts immediately from the bundle already installed on your device

Turning off Analytics stops Amplitude and EAS Observe. It does not stop these operational update checks, and it does not stop redacted critical error reports.

8. Error Monitoring and Crash Reports (Sentry)

Sentry is used in two levels. Critical JavaScript errors are always collected so release-blocking failures can be diagnosed; every report passes through central redaction before it is sent. Enhanced diagnostics are optional and off by default.

  • Always on: critical JavaScript error messages and stack traces, redacted
  • Optional: additional error context, app state, and in-app breadcrumbs (Enhanced Crash Reporting)
  • Redaction removes content URIs, device-local paths, file names, stable device, user and RevenueCat identifiers, credentials, and sensitive values from messages, stacks, contexts, extras, and breadcrumbs

Native crash capture, watchdog terminations, and app hangs are disabled in Sentry, because native events would bypass our JavaScript redaction. Screenshots, session replay, and automatic session tracking are also disabled. No music files or user content are ever included.

Error events are retained according to the retention period configured for our Sentry organisation and Sentry's applicable terms.

9. Purchases and Subscriptions

RevenueCat processes your purchase and subscription status, your Premium entitlements, and a pseudonymous identifier so your subscription can be restored across your devices. Payments themselves are processed by the Apple App Store; BeatPoket never sees your card details.

10. No Advertising Tracking

BeatPoket does not perform advertising or cross-app tracking. We do not use advertising identifiers, we do not build advertising profiles, and we do not sell or share your data with data brokers or advertising networks.

11. Your Choices and Rights

You can enable or disable Amplitude analytics and EAS Observe, and enable or disable Enhanced Crash Reporting, at any time in Settings > Privacy & Data. Changes take effect immediately. You can request deletion of any personal data by contacting hello@beatpoket.com.

12. Contact Us

For privacy concerns, contact us at hello@beatpoket.com. BeatPoket is owned and operated by Yoshimyra SARL.

Back to Home