AMPL

AMPL Privacy Policy

insubae 2026. 10. 1. 10:52

<!doctype html>

AMPL

Privacy Policy

Effective date:

· Last updated:

This Privacy Policy explains how AMPL for Android (the “App”) handles information when you use its equalizer, tone controls, VU meter, music display, and in-app purchases.

At a glance: AMPL processes audio and music information on your device. It does not record microphone input, upload audio or song information, or include advertising or analytics SDKs. Google Play handles purchases. No AMPL account is required.

1. Information AMPL handles

The App uses the following information to provide its features. On-device processing is separate from information you choose to send when contacting the developer.

Information used by the App and its purpose
Information Purpose and handling
Playback audio levels Brief waveform samples and peak/RMS measurements from Android’s internal audio output drive the VU meter. They are processed in memory and are not saved as audio recordings or sent to the developer.
Current music information With notification access, the App reads title, artist or display subtitle, playback state, and the player’s name and package identifier from active media sessions. This information is displayed locally; the App does not build or upload a song-listening history.
Audio session and output details Player package identifiers, audio session IDs, and output-route information help attach effects and calibrate the meter. Recent session mappings are saved locally. The App does not scan your full list of installed apps.
Audio preferences EQ, bass, treble, loudness, and related effect settings are saved in private app storage to restore your choices.
Local usage and permission state The App saves daily free-use time, relevant dates, purchase entitlement, permission-request flags, and review-prompt choices and listening-time counters. These support the free allowance and optional review prompt; they are not uploaded as analytics.
Device orientation Rotation-sensor values animate the interface’s lighting while the App is in use. These values are processed in memory, without creating a stored movement history or sending them to the developer.
Purchase information Google Play supplies product and transaction information, purchase status, and purchase tokens to process, acknowledge, and restore purchases. AMPL saves the resulting entitlement locally.

The App does not request your name, email address, location, contacts, photos, or an account login for its audio features.

2. Android permissions

  • Microphone permission (RECORD_AUDIO): Android requires this permission for its audio Visualizer API. AMPL uses that API to measure internal playback for the VU meter. AMPL does not open your microphone, record conversations, save audio files, or transmit audio. You can use the audio effects without granting this optional permission.
  • Notification permission (POST_NOTIFICATIONS, Android 13 and later): This optional permission displays the audio-effects service status in your notification list. AMPL asks after you finish adjusting an effect. If you decline, audio effects continue to work; AMPL does not repeatedly ask. This is separate from the notification access used for song information.
  • Notification access: This optional access enables the current-song display through Android’s active media sessions. Although Android grants a broad notification-listener capability, AMPL does not read or store the contents of messages, emails, or unrelated notifications.
  • Audio settings and foreground service: These allow the App to apply your selected audio effects and keep them running while you listen in another app. They are not used to send your playback information to the developer.

The App explains its optional access requests before directing you to Android’s permission or access settings.

3. Google Play purchases

Google Play processes the App’s in-app purchase and purchase restoration. The App exchanges purchase-related information with Google Play through Google Play Billing, including purchase queries and acknowledgements. AMPL does not receive your full payment-card details or Google Account password.

Google’s handling of account, payment, and transaction information is governed by the Google Privacy Policy. Google Play also handles any review you choose to submit after opening the store from the App.

4. Sharing and third-party services

AMPL does not operate a developer backend for audio, song information, sensor data, or usage tracking. The current App contains no advertising, analytics, or third-party crash-reporting SDKs, and the developer does not sell your personal information or share it for targeted advertising.

Google Play and Android may process information as part of their own services, including billing, backup, and platform diagnostics, under their respective settings and policies.

If you contact the developer, your email address, message, and any attachments you choose to provide will be used to respond to your request. Your email service and the developer’s email service process that correspondence. Information may also be disclosed where required by applicable law.

5. Storage, retention, and deletion

  • Temporary information: Audio measurements, current-song display information, and orientation values are handled in memory rather than saved as recordings or histories.
  • Saved preferences: Settings and local feature state remain in private app storage until replaced or removed. Daily free-use records are updated as the day changes. Remembered audio sessions are removed when the player announces their closure, replaced by newer sessions, or discarded after a device reboot.
  • Diagnostic logs: The App may write effect status, output-route details, player package identifiers, session IDs, and errors to Android’s local diagnostic log. It does not automatically upload these logs. Android controls their retention; a diagnostic report you choose to share may include them.
  • System backups: Some saved settings may be included in Android backup or device transfer, depending on your device and system settings. The App’s backup rules exclude free-use and purchase-entitlement state, audio-session mappings, and VU and service-notification permission-request flags. Manage system backups through your Android or Google settings.
  • Support correspondence: Messages you send to the developer are retained only as needed to respond, resolve the issue, and meet applicable legal obligations.

You can remove local App data through Android Settings → Apps → AMPL → Storage → Clear storage / Clear data, or by uninstalling the App. Menu names may vary by device. This does not cancel a purchase or delete Google Play’s transaction records or existing system backups. An eligible purchase may be restored by Google Play after you reinstall the App.

6. Your choices and privacy requests

You can stop background audio effects by removing AMPL from Android’s Recent apps list. Switching to another app keeps selected effects running. You can disable service-status notifications in Android’s notification settings without disabling the audio effects.

You can deny or revoke microphone permission in Android’s app-permission settings and revoke AMPL’s notification access in Android’s notification-access settings. Revoking access disables the related VU or music-display feature; it does not require you to create an account.

Depending on where you live, you may have rights to access, correct, delete, or restrict the processing of personal information, and to raise a concern with your local privacy authority. Contact the developer about information you have provided through support. The developer cannot retrieve audio, music-display information, or local settings that remain solely on your device.

7. Security

AMPL uses Android’s app-private storage for saved preferences and on-device processing for its audio features. Purchase operations use Google Play Billing. No method of storage or communication can guarantee absolute security; avoid including unnecessary sensitive information in support messages or diagnostic attachments.

8. Changes to this policy

This policy may be updated when the App or its data practices change. The updated version will be published on this page with a revised “Last updated” date. Any new permission or consent required for a feature will be requested separately where applicable.

9. Contact

For privacy questions or requests concerning AMPL, contact:

Developer
Insu Bae
Privacy contact email
insubae@neointro.com
App
AMPL for Android
AMPL · Privacy Policy