Flex - Music Player Privacy Policy

Last updated: 21 October 2026

Developer and contact

Flex - Music Player is developed and operated by Elixir Consultancy Services Ltd, 7 Croftflat Drive, Fenay Bridge, Huddersfield, HD8 0FS, United Kingdom.

Privacy enquiries and data-deletion requests can be sent to support@elixircs.com.

Application identity

This policy applies to the Flex - Music Player app on the App Store and Google Play.

Flex - Music Player is an independent application and is not affiliated with or endorsed by Plex, Inc.

Overview

Flex - Music Player connects to a Plex account and a user-selected Plex Media Server so that the user can browse, stream and manage their personal music library and playlists.

Elixir Consultancy Services Ltd does not operate a central Flex - Music Player user-account service and does not receive or store the user’s personal music files.

Plex authentication and server data

Plex authentication takes place through Plex’s browser-based sign-in process.
Flex - Music Player does not receive or see the user’s Plex password.
The Plex access token, selected server address and Plex account display name are stored locally on the user’s device.
The app communicates directly with Plex and the user-selected Plex Media Server to retrieve music-library metadata, stream audio, manage playlists, save ratings and perform requested library actions.
Library metadata may include track titles, artist names, album names, artwork, playlist contents, ratings and playback information.
Audio is streamed from the selected Plex Media Server and is not uploaded to Elixir Consultancy Services Ltd.
Offline downloads, cached artwork, lyrics, playback state and app preferences may be stored locally on the user’s device.
This locally stored information can be removed by clearing the app’s data, switching Plex servers where applicable, or uninstalling the app.

Plex’s own processing is governed by the Plex privacy policy.

Lyrics

When lyrics are not available from the selected Plex server, Flex - Music Player may request lyrics from LRCLIB.

To perform the lookup, the app may send track metadata such as the track title, artist, album and duration to LRCLIB. Audio files are not sent to LRCLIB.

LRCLIB operates independently of Elixir Consultancy Services Ltd.

Purchases and subscriptions

Flex - Music Player uses RevenueCat, together with the billing system of the store the app was installed from, to provide, validate and restore Flex - Music Player Pro purchases and subscriptions. That is Google Play Billing on Android and Apple’s In-App Purchase system on iOS, iPadOS and watchOS.

Google Play or Apple processes the payment, according to the store the app was installed from. Flex - Music Player and Elixir Consultancy Services Ltd do not receive or store full payment-card details.

RevenueCat may process:

Google Play or Apple App Store purchase history and transaction or receipt information;
purchased product identifiers;
subscription and entitlement status;
an anonymous or pseudonymous app user identifier; and
limited app, platform and device information required to operate and analyse the purchase service.

This information is used for app functionality, purchase validation, entitlement management, purchase restoration, customer support and purchase-related analytics. It is not used for advertising.

Advertising and tracking

Flex - Music Player does not contain advertising.
Flex - Music Player does not use an advertising identifier.
Flex - Music Player does not sell personal information.
Flex uses optional product analytics as described below. It does not use analytics to track users across other companies’ apps or websites.
RevenueCat’s purchase-related analytics are used only to operate and understand purchases and entitlements.

Optional usage statistics

In version 2.0 and the earlier 1.1.0 test builds from build 2073, Flex uses PostHog, hosted in the EU, to understand app usage and improve the app. When Usage statistics is enabled, we collect app opens, visited screens, selected setting changes, search-result availability, mix starts and upgrade-prompt views. Events include app/build, operating-system and device information, timestamps, session identifiers and a random installation identifier used to measure returning use.

We do not link this identifier to your Plex account or send music titles, search text, server addresses, credentials, custom-theme contents or screen recordings. Session replay and advertising tracking are disabled. PostHog receives the network address needed to deliver requests; Flex disables geographic enrichment of these events.

Usage statistics is on by default in configured builds and can be turned off under Settings › About Flex Music › Usage statistics. Existing opt-outs are respected. Turning it off stops new events, disables collection and resets the analytics identifier. It does not delete events already sent, and queued or in-flight events may still arrive. This switch controls Flex product analytics; it does not control purchase processing or Google Cast SDK data.

Earlier builds use Aptabase for app-install, app-open and upgrade-prompt counts, with a temporary session identifier rather than a persistent installation identifier. Those builds retain their existing usage-statistics switch. Historical Aptabase data is not migrated to PostHog.

PostHog privacy policy

Casting and local network

When you choose a Google Cast or Sonos device, Flex sends that receiver the track details and playback or artwork URLs needed to play your selection. These URLs can include a Plex access token. The receiver connects to your selected Plex server; lyric casting also sends the displayed lyrics. Only cast to devices and networks you trust.

Google Cast's SDK separately sends SDK usage information to Google, including discovery and session events and app/device information. The iOS SDK also declares device identifiers and diagnostic information. Google uses this data for Cast functionality and analytics. This processing is separate from Flex's optional PostHog analytics and is not disabled by the Usage statistics switch. Google states that Android Cast SDK collection cannot be opted out of or deleted by the developer or user; it retains logs briefly and aggregates them for product metrics.

Google privacy policy and Cast SDK data disclosure.

Device permissions

Internet access: connects to Plex, the selected Plex Media Server, selected Cast/Sonos receivers, Google Cast services, LRCLIB, Google Play or the Apple App Store, RevenueCat and the analytics provider when usage statistics is enabled.
Notifications: provides playback controls and playback information where permitted by the user.
Foreground media service and wake lock: support reliable background audio playback.

The current app does not request access to location, contacts, text messages, microphone or camera.

Data sharing

Data is disclosed only where necessary to provide the requested functionality, including to Plex, the user-selected Plex Media Server, selected casting devices and Google Cast services, LRCLIB, Google Play or the Apple App Store, RevenueCat and, when usage statistics is enabled, PostHog (Aptabase in earlier builds).

RevenueCat acts as a service provider for purchase validation and entitlement management. PostHog acts as a service provider for the product analytics described above, hosted in the European Union. Earlier builds use Aptabase in the EU. Flex does not share data with advertising networks or data brokers.

Data retention

On-device information remains until the user clears it, switches server where applicable, or uninstalls the app.
Purchase and entitlement records may be retained by Google Play, Apple and RevenueCat according to their policies and for legal, accounting, fraud-prevention and transaction-management purposes.
Product-analytics events are retained in our PostHog project for usage analysis until deleted under the project’s retention settings or by us. They can be associated with the random installation identifier, but we do not maintain a link to your Plex account. Historical Aptabase counts remain separate.
Support correspondence is retained only as long as reasonably necessary to resolve the request and meet legal obligations.
Elixir Consultancy Services Ltd deletes or anonymises data it controls when it is no longer required, subject to applicable legal-retention requirements.

Data deletion requests and user rights

Flex - Music Player does not create a separate account, so there is no account to delete.

Users can request deletion of purchase-related data controlled through RevenueCat by emailing support@elixircs.com with the subject “Flex - Music Player data deletion request”. The support team may request a Google Play order number, an Apple receipt or order ID, or other information necessary to identify the relevant anonymous purchase record. Users must not send payment-card information or their Plex password.

You can also contact us about analytics data using the address above. We may need information sufficient to locate the relevant installation’s records; a Plex account name alone will not identify them. Turning off Usage statistics stops new collection and resets the identifier, but is not a request to delete historical data. Do not send Plex passwords or access tokens.

Under the UK GDPR, users may have rights to access, correct or delete their personal information, restrict its processing, object to its processing and receive a portable copy of it, where applicable.

Users may also complain to the UK Information Commissioner’s Office.

Security

Elixir Consultancy Services Ltd uses reasonable technical and organisational safeguards. Purchase-service communications use encryption in transit. Connections to Plex and a personal Plex Media Server also depend on Plex and the server configuration selected by the user.

International processing

Third-party providers may process information outside the United Kingdom. Appropriate safeguards are relied upon where required by applicable law.

Children

Flex - Music Player is intended for users aged 18 and over and is not directed at children.

Changes to this policy

This policy may be updated when the app, its providers or legal requirements change. The revised “Last updated” date will be shown on this page.