Pab Music player Privacy Policy

Version française

Effective date and last updated: October 14, 2026

This English version is provided for convenience. The French version is the reference version.

1. Overview and scope

Pab Music player is an Android app for playing and managing local music files. On the device, it is displayed under the name "Music". Its Android identifier is com.pab.music.

It lets you:

• build a music library from the audio files on your device;
• listen to music, including in the background;
• create playlists and mark favorites;
• view listening statistics;
• import audio files;
• manually edit track information (tags) and cover art.

This policy explains what data is used, where it is processed, who may receive it and what your rights are. It applies to the Pab Music player app distributed on Google Play.

Key point: your music files and their information are processed on your device. The developer has no server that receives your tracks, your library or your statistics. However, the app includes Google services for advertising, consent and purchases. These services process certain data, described below.

2. Data controller and contact

The data controller is:

Paul Abensour, sole trader (entrepreneur individuel, micro-entrepreneur), France
SIRET: 851 579 847 00027
Address: 4 Mail des Catalpas, 78180 Montigny-le-Bretonneux, France
Email for privacy questions: paulabnsr@gmail.com

No data protection officer has been appointed. For any question or request, write to the address above.

3. Data processed

3.1 Data processed only on your device

To work, the app reads and stores information on your device. The developer has no access to it: it is not sent to the developer.

Audio files and track information:

• the audio files on the device that you give access to;
• their information: title, artist, album, track and disc number, year, duration, file name and location, cover art.

Data created by the app, in its private storage:

• the music library and the changes you make to it;
• playlists and favorites;
• listening statistics: play count and last played date of each track, date added;
• copies of the files you import into the app;
• cached cover art, to speed up display;
• temporary backup copies, created while editing tags so that a file can be restored if something fails;
• information used to recognize the ad-free purchase (see section 8);
• app preferences.

Listening statistics are used only for app features, for example showing your most played tracks. They are not sent to the developer or to advertising services.

Background playback: during playback, the app passes the current track's information (title, artist, cover art) to Android. It is used to display the playback notification and media controls, for example on the lock screen or a connected Bluetooth device, depending on your Android settings.

3.2 Data processed by the integrated Google services

The app includes three components provided by Google:

• the Google Mobile Ads SDK (Google AdMob), to display banner ads;
• Google's User Messaging Platform ("UMP"), to manage advertising privacy choices;
• the Google Play Billing Library, for the purchase that removes ads.

These components communicate with Google's servers. The data they process is described in sections 6, 7 and 8.

3.3 Messages you send by email

If you write to the developer, the developer receives your email address, the content of your message and any attachments. These messages are received in a Gmail mailbox, provided by Google.

3.4 What the app does not do

• It has no user account of its own and does not ask you to sign in.
• It does not send your music files, library, playlists or statistics to the developer.
• The developer does not use any server of its own for the app.
• It does not include separate audience measurement or crash reporting tools such as Firebase Analytics or Firebase Crashlytics. The diagnostic and measurement processing carried out by the advertising services is described in section 6.

4. Android permissions

The app requests or uses the following permissions.

Access to audio files (READ_MEDIA_AUDIO from Android 13, READ_EXTERNAL_STORAGE up to Android 12):

• Purpose: show and play the device's audio files in the library.
• If refused or revoked: the device's tracks are not shown. You can still import files with the Android file picker, which does not need this permission. You can grant or revoke this permission at any time in Android settings.

Write access to storage (WRITE_EXTERNAL_STORAGE, only up to Android 9):

• Purpose: save your tag or cover art changes to a file on the device, or delete a file at your request.
• If refused: these changes or deletions are not possible. Playback keeps working.
• From Android 10, these operations no longer use this permission. Depending on the file, Android may show its own confirmation window before the app changes or deletes it.

Foreground service and wake lock (FOREGROUND_SERVICE, FOREGROUND_SERVICE_MEDIA_PLAYBACK, WAKE_LOCK):

• Purpose: keep playing when the app is in the background or the screen is off, with a playback notification.

Internet and network state (INTERNET, ACCESS_NETWORK_STATE):

• Purpose: allow Google services to work: advertising, consent and purchases. They are not used to play your files, which works offline.

Permissions added by Google components:

• The Google components included in the app may add their own technical permissions. This includes the advertising ID permission (AD_ID), used by the Google Mobile Ads SDK, and the Google Play billing permission.
• The Google Mobile Ads SDK also declares Android's ad services permissions (ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_TOPICS). On devices that support them, they let Google use the advertising features built into Android, such as interest categories ("Topics") or ad measurement. You can manage them in Android settings, for example Settings, then Privacy, then Ads.

Access to the files you import:

• When you import a file, the app tries to keep access to the original file you selected, if the file provider allows it. This allows your tag changes to be applied to that file. This access may become unavailable.

5. Purposes and legal bases

Music features (library, playback, playlists, favorites, statistics, import, tag and cover art editing):

• Purpose: provide the app features you use.
• Legal basis: performance of the service you request. This processing takes place on your device.

Advertising:

• Purpose: fund the free app with banner ads.
• Legal basis: your consent where required by law, in particular for accessing information on your device and for ad personalization. Otherwise, the developer's legitimate interest in funding the app.
• Google acts as an independent controller for its own advertising processing. It determines its own legal bases, which are presented in consent messages and in its privacy policy.

Managing your privacy choices:

• Purpose: collect, store and apply your advertising choices.
• Legal basis: compliance with the developer's legal obligations.

Ad-free purchase:

• Purpose: sell you the option that removes ads, verify the purchase and recognize it, including after reinstalling.
• Legal basis: performance of the purchase contract. Checking that the purchase is genuine also relies on the developer's legitimate interest in preventing fraud.

Replying to your messages:

• Purpose: answer your questions and handle your requests, including requests to exercise your rights.
• Legal basis: the developer's legitimate interest in replying to people who contact him. For requests to exercise your rights: compliance with a legal obligation.

6. Google AdMob ads

6.1 Placements

The app may display two banner ads: on the home screen (library) and on the now playing screen. They are provided by Google AdMob. The app does not use mediation with other ad networks.

No banner is requested:

• as long as your privacy choices do not allow ad requests (see section 7);
• when the ad-free purchase is recognized.

Loading new ads requires an Internet connection. An ad that has already loaded may remain visible after the connection is lost.

6.2 Data processed by the Google Mobile Ads SDK

According to Google's documentation for the integrated SDK version, the SDK automatically collects and shares the following data categories:

• the device's IP address, which may be used to estimate its approximate location;
• interactions with the app and ads, for example app launches, taps and ad views;
• diagnostic information, for example performance data;
• device identifiers: Android advertising ID, app set ID and, where applicable, other identifiers related to accounts signed in on the device.

According to Google, this data is encrypted in transit.

Google states that it uses this data for:

• serving ads and, where your privacy choices allow it, personalizing them;
• ad measurement, for example the number of views and clicks;
• analytics;
• fraud prevention, security and compliance.

This data is processed by Google, not by the developer. The developer only receives aggregate statistics, for example the number of ads displayed and earnings, which do not allow him to identify you.

6.3 Recipients

Advertising data is received by Google. Depending on your choices and region, Google's advertising partners (ad technology providers) may also take part in serving and measuring ads. When a consent message is shown to you, it lists these partners and lets you make your choices.

6.4 Personalization

Ads may be personalized, that is, chosen based on your interests, if your privacy choices and your region's rules allow it. Otherwise, Google may serve non-personalized or limited ads (see section 7.3).

6.5 Controlling the advertising ID

You can delete or reset your device's advertising ID in Android settings. The path varies by device, for example Settings, then Privacy, then Ads. Once the ID is deleted, apps can no longer access it.

6.6 Learn more

• How Google uses information from partner apps: https://policies.google.com/technologies/partner-sites
• Google Privacy Policy: https://policies.google.com/privacy
• Google ad settings: https://myadcenter.google.com

7. Privacy choices and consent (UMP)

7.1 Collecting your choices

If the ad-free purchase is not recognized, the app checks with Google's User Messaging Platform (UMP) before requesting an ad. UMP determines whether a consent message must be shown to you, depending on your region and the applicable rules. If so, the message is shown and you can make your choices. To do this, UMP communicates with Google's servers and stores your choices on the device.

The app only requests ads when UMP indicates that it may. This is the case once you have made your choices, or when no choice is required in your region.

If UMP cannot be reached, for example offline, the app relies on the choices already stored on the device.

7.2 Changing or withdrawing your choices

Where required by law, the app's menu offers an "Ad privacy choices" option. It reopens Google's form and lets you change or withdraw your choices at any time. Current banners are removed while the form is open. New ad requests take your new choices into account.

Withdrawing consent does not affect processing carried out before the withdrawal.

7.3 Effect of refusing

Refusing consent does not necessarily prevent ads from being displayed. After you make your choice, the app may keep requesting banners from Google.

In that case, according to Google's documentation, when the consent needed to access information on the device is not given, Google tries to serve "limited ads". These ads do not use the advertising ID or local storage for advertising purposes. However, Google states that it uses the IP address for basic ad serving. Depending on the applicable AdMob settings, in particular whether programmatic limited ads are enabled, Google may also use local storage reserved for detecting invalid traffic. It is also possible that no ad is displayed.

To stop seeing ads, you can buy the ad-free option (section 8).

8. Ad-free purchase (Google Play)

8.1 How it works

The app offers a one-time, permanent purchase that removes ads. Payment is handled entirely by Google Play, with your Google Play account. No account specific to the app is created.

8.2 Data held by Google

Google processes the information needed for the purchase: Google account, payment method, purchase history, country, etc. The developer has no access to your payment details. This processing is governed by Google's privacy policy: https://policies.google.com/privacy

The developer can view in the Google Play Console the order information that Google makes available to developers. He uses it to manage sales, refunds and his accounting obligations.

8.3 Data received by the app

During a purchase or a check, the app receives from Google Play, on your device, a signed purchase receipt. This receipt includes in particular:

• the order ID;
• the purchased product;
• the purchase date;
• the purchase state;
• a purchase token;
• the app name.

The app verifies the receipt's signature and confirms the purchase with Google Play. It then stores the verified receipt in its private storage, on your device. This receipt allows your purchase to be recognized when you open the app offline.

This information is not sent to any developer server: the app does not use one.

8.4 Restoring and revoking

Each time you open or return to the app, it asks Google Play for the purchases associated with the account in use. This makes it possible to restore the purchase after reinstalling, or on another device using the same Google Play account. A connection to Google Play is then required.

If Google Play replies that no valid purchase exists, for example after a refund or an account change, the receipt stored on the device is deleted and ads come back. Being offline does not delete the receipt.

9. Data sharing and international transfers

The developer does not sell your data. The developer does not receive your music files, library or statistics.

The only external recipients are:

• Google, for advertising, privacy choices, Google Play purchases and the Gmail mailbox;
• Google's advertising partners, depending on your choices and region (section 6.3).

Google states that it maintains servers around the world. Your data may therefore be processed outside your country, including in the United States. For transfers of data outside the European Economic Area, Google states that it relies on European Commission adequacy decisions, the EU–U.S. Data Privacy Framework and standard contractual clauses. More information: https://policies.google.com/privacy/frameworks

The developer may also disclose information when required by law, for example at the request of an authority.

10. Retention and deletion

10.1 The app's private data

The library, playlists, favorites, statistics, preferences, imported copies and purchase receipt are stored on your device, in the app's private storage. They remain there until you delete them. Caches may be refreshed or deleted automatically. Temporary backups created while editing tags are normally deleted at the end of the operation; they may be kept if restoring the file fails.

You can delete them:

• partly within the app, for example by deleting a playlist or a track;
• entirely in Android settings, with the option that clears the app's data or storage;
• by uninstalling the app: Android then deletes its private storage.

The app does not offer a button to delete all its data or reset statistics.

Android automatic backup of the app's data is disabled. Depending on the device, manufacturer and Android version, some phone-to-phone transfer tools may still copy app data.

10.2 Original music files and imported files

Your original music files stay where they are on your device or in the storage service from which you selected them.

• Clearing the app's data or uninstalling it does not delete your original files.
• The tag and cover art changes you save are written into the files concerned. They therefore remain after uninstalling.
• Deleting an imported track in the app deletes its private copy, not the original file.
• Deleting a device track in the app erases the file from the phone. The app asks you to confirm. Android may also ask for its own confirmation.

10.3 Purchase data held by Google Play

Uninstalling the app does not cancel your purchase and does not delete the data held by Google Play. The purchase remains linked to your Google Play account. For data that Google retains, see Google's privacy policy and your Google Account settings: https://myaccount.google.com

10.4 Data processed by Google and its advertising partners

This data is retained by Google and its partners under their own rules. Uninstalling the app does not delete it. You can manage your Google ad settings at https://myadcenter.google.com and delete your device's advertising ID (section 6.5).

How Google retains data: https://policies.google.com/technologies/retention

10.5 Messages sent by email

Messages are kept for as long as needed to handle your request and follow up on the exchange, then deleted, unless the law requires keeping them longer.

11. Security

The following measures are in place:

• The app's data is stored in its private storage, which other apps cannot read thanks to Android's app sandbox.
• The app does not allow unencrypted network connections. According to Google, data collected by the Google Mobile Ads SDK is encrypted in transit.
• Android automatic backup of the app's data is disabled.
• Before removing ads, the app checks the Google Play receipt's signature, the product, the app name and the purchase state.
• Before changing a file, the app creates a temporary backup copy so that it can be restored if something fails.
• The developer does not operate any server that would receive your data.

No security measure is foolproof. The protection of your data also depends on your device's security, for example its screen lock and updates.

12. Your rights

Depending on the applicable law, in particular the General Data Protection Regulation (GDPR) and the French Data Protection Act (loi Informatique et Libertés), you have the following rights:

• access to your data;
• rectification;
• erasure;
• restriction of processing;
• objection, in particular to processing based on legitimate interest;
• data portability;
• withdrawing your consent at any time;
• giving instructions on what happens to your data after your death.

How to exercise them:

• Data on your device: you control it directly, in the app and in Android settings (section 10.1). The developer has no access to it and therefore cannot view or delete it remotely.
• Advertising choices: use the "Ad privacy choices" option when it is offered (section 7.2), as well as the Android and Google settings listed in section 6.
• Data processed by Google: Google is responsible for this processing. You can exercise your rights directly with Google: https://policies.google.com/privacy
• Messages and any other request: write to paulabnsr@gmail.com.

The developer replies within one month. This period may be extended by two months for complex requests; you will be informed if so. Proof of identity may be requested in case of reasonable doubt.

You can lodge a complaint with the French data protection authority, the Commission nationale de l'informatique et des libertés (CNIL), 3 place de Fontenoy, 75007 Paris, France, https://www.cnil.fr, or with the data protection authority of your country.

13. Children and minors

Pab Music player is not intended for children under 13. On Google Play, its target audience is set to 13 and over.

It does not ask for the user's age, does not create accounts and does not ask you to enter a name or email address. However, the integrated advertising services may process the personal data described in section 6. The developer does not receive data that could identify a child.

Banner ads are requested from Google with the same settings for all users: the app does not apply different advertising treatment based on age. Any personalization depends on the privacy choices stored and on the rules of the region (sections 6 and 7).

In France, when processing is based on consent, a minor under 15 cannot consent alone. Consent must be given jointly by the minor and the holder of parental authority. Other ages may apply in other countries. We encourage parents to supervise their children's use of the app, in particular for privacy choices.

Purchases remain subject to the Google Play authentication and parental control settings defined for the account in use.

If you believe a child under 13 has sent personal data to the developer, for example by email, contact paulabnsr@gmail.com to request its deletion.

14. Changes to this policy

This policy may be updated, for example when features or services are added or when regulations change. The new version will be published at the same address, with a new update date. In the event of a significant change, notice will be given by appropriate means, for example on the Google Play listing or in the app.

15. Contact

For any question about this policy or your data:

Paul Abensour
4 Mail des Catalpas, 78180 Montigny-le-Bretonneux, France
paulabnsr@gmail.com