R1

R1 Privacy Policy

insubae 2026. 10. 3. 20:39

 

R1 · WOOFER-R1

Privacy Policy

Effective date: October 3, 2026
Last updated: October 3, 2026

This Privacy Policy explains how R1: Woofer Bass Booster, also displayed as WOOFER-R1 (the “App”), handles information. This policy applies to the Android app with package identifier com.neointro.audio.r1.

The App is provided by [Developer name]. For privacy questions or requests, contact [Privacy contact email].

At a glance: R1 processes playback audio on your device to animate the woofer. It does not capture microphone input or record, save, or transmit audio. No R1 account is required. Google Play handles in-app purchases.

1. Information used by the App

  • Internal playback audio: Brief waveform samples and derived bass-level measurements are processed in memory to animate the speaker. R1 does not create audio recordings or a listening history, and does not send this audio to the developer.
  • Audio connection information: R1 uses audio session identifiers and player package names announced through Android's audio-effect connection mechanism, together with output-route, volume, and playback-state information, to connect effects and adjust the animation. Recent player/session mappings are stored locally. R1 does not scan a full list of installed apps or read song titles, artists, messages, or unrelated notifications.
  • Settings and local feature state: R1 stores your knob settings, light position, daily free-use date and time used, purchase-entitlement status, and permission-request flags in app-private storage. These values restore your choices and manage the daily allowance; the developer does not receive them as usage analytics.
  • Purchase information: Google Play Billing provides product and purchase information, such as product identifiers, purchase status, purchase tokens, and transaction details, for purchase checks, acknowledgement, and restoration. R1 saves the resulting entitlement status locally.
  • Support information you provide: If you contact the developer, your email address, message, and any attachments you choose to send are used to respond to your request.

R1 does not ask for your name, email address, location, contacts, photos, or an account login to use its audio features. The current App contains no advertising SDK or developer-installed analytics or crash-reporting service.

2. Permissions and background operation

  • Microphone permission (RECORD_AUDIO): Android requires this permission for the Visualizer API used to analyze internal playback and make the woofer move with the music. R1 does not open the microphone or record conversations. You may decline or revoke this permission; bass enhancement remains available, but the music-reactive animation is unavailable without it.
  • Notification permission (POST_NOTIFICATIONS): On supported Android versions, this optional permission shows the woofer-effect status in the notification panel. It does not give R1 access to other apps' notification contents. Declining it does not disable the bass effect.
  • Audio settings and foreground service: These capabilities apply your selected bass effects and maintain them while you listen in another app. Switching apps can leave the effects running; removing R1 from the Recent apps list stops its effect service. Audio-analysis polling for the animation stops when R1 is in the background.
  • Billing and network access: Google Play Billing and its related components use connectivity for product queries, purchases, purchase-status checks, acknowledgements, and service operations. R1 does not use this access to upload playback audio to the developer.

3. Google Play and other service providers

In-app purchases are processed through Google Play. Purchase-related information is exchanged with Google Play through its billing system, including when product or ownership information is queried. R1 does not receive your full payment-card details or Google Account password.

Google Play, Google Play Billing and related Google components, and Android may process transaction, app, device, and diagnostic information to operate, secure, and maintain their services. Google may also make purchase and transaction records available to the developer through Play Console for order management. Google's handling of information is described in the Google Privacy Policy.

The developer does not operate a backend that receives playback audio, speaker measurements, or local listening-time records. The developer does not sell personal information or use it for targeted advertising. Email providers process correspondence when you choose to contact support. Information provided to support or made available through purchase administration may be disclosed where required by applicable law.

4. Storage, retention, and deletion

  • Audio analysis: Playback samples and measurements are held in temporary memory, not saved as audio files. Memory buffers are reused and are released when the analyzer shuts down.
  • Local records: Saved settings and feature state remain in app-private storage until replaced or removed. Daily allowance records are updated as the day changes. Player/session mappings are replaced by newer sessions, removed when a player announces closure, or discarded when the App detects a device reboot.
  • Local diagnostic logs: R1 may write effect status, player package names, session identifiers, output-route details, and errors to Android's diagnostic log. R1 does not automatically send these developer-written logs to a developer server. Android manages their retention. A diagnostic report that you choose to share may include them.
  • System backup and transfer: Android backup or device transfer may include saved app data, including settings and local usage or entitlement state, depending on your device and system settings. These services are controlled by Android, Google, or your device provider; manage them in the relevant system settings.
  • Support and transaction records: Correspondence and records available to the developer are kept only as needed to address the request, administer a purchase, resolve disputes, and meet applicable legal obligations. Google retains its own account and transaction records under its policies.

To delete local App data, use Android Settings → Apps → WOOFER-R1 → Storage → Clear storage / Clear data, or uninstall R1. Menu names may vary. This does not cancel a purchase, remove Google Play's transaction records, or delete existing system backups. A purchase may be restored through Google Play after reinstalling.

5. Your choices and privacy requests

You can deny or revoke microphone permission in Android's app-permission settings, manage status notifications in notification settings, and stop background effects by removing R1 from Recent apps. R1 has no developer-managed user account to delete.

Depending on applicable law, you may have rights to request access, correction, deletion, or restrictions on 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 or purchase enquiries. The developer cannot remotely retrieve or delete audio or settings that remain only on your device. For Google-held information, use Google's privacy and account controls.

6. Security

R1 uses on-device audio processing and Android's app-private storage. Purchase operations use Google Play Billing. No storage or communication system can guarantee absolute security. Send only the information needed for a support request, and avoid attaching unnecessary personal or sensitive information.

7. This policy page

This page describes the R1 Android app. If you view it on Tistory, the website's hosting and any blog services may separately process visitor information, such as connection logs or cookies, under their own settings and policies. This page does not add a tracker or collect information through a form. For the hosting platform's practices, see Kakao Privacy. Any additional analytics or advertising enabled by the blog operator is separate from R1's app functionality.

8. Changes to this policy

This policy may be updated when R1 or its information-handling practices change. The revised policy will be published on this page with an updated date. Any new permission or consent required for a feature will be requested separately where applicable.

9. Contact

Developer / operator: Insu Bae
Privacy contact email: insubae@neointro.com
App: R1: Woofer Bass Booster / WOOFER-R1 for Android
Package: com.neointro.audio.r1