Vocal Booth — Privacy Policy
Last updated: 2026-10-17
This privacy policy applies to the mobile app "Vocal Booth" for Android:
- Google Play: package com.simonj.vocalstudio, developer "Global Utility App Maker"
The app is developed and operated by Kyu-Hee Jang (Google Play developer name: Global Utility App Maker).
Contact: wkdrb2100@gmail.com
OVERVIEW
Vocal Booth does not require an account, and we do not sell personal information. You import a beat, record vocal takes over it, apply pitch correction after recording, and export the mix as an audio file. Your songs and recordings are kept in the app's storage on your device. The app also uses Google services and an advertising mediation partner for analytics, crash reporting, remote configuration, and advertising.
MICROPHONE AND RECORDINGS
The app asks for microphone permission when you first start recording or the timing calibration. It uses the microphone only while you record a take or run the timing calibration, and only while the app is in the foreground; a take ends when the app leaves the foreground. While you record, the take is written to a file in the app's storage so that it can be recovered after a crash; when the take is finished it is copied into the song's audio, and the recorder's copy is then removed. Calibration records a short clip in the app's cache to estimate a timing offset; the app keeps the resulting offset and deletes the clip afterwards (if a calibration is interrupted, its clip may remain in the cache). Pitch detection, pitch correction, mixing and export run on your device; the app does not upload your recordings. If you deny the permission, recording is off and the rest of the app keeps working; you can allow it later in Android settings.
BEATS AND FILES YOU PICK
The app does not ask for access to your music, photos or storage. When you tap to start a new song or "Restore backup", the Android file picker opens and only the files you choose are given to the app. A beat you pick is copied into the app's storage; the picker may also leave a temporary copy in the app's cache. The demo song is generated on your device.
INFORMATION STORED ON YOUR DEVICE
For each song the app keeps its name, the copied beat, your takes (audio files, take number, recording time, length, the audio route used such as wired headphones or Bluetooth, timing alignment and why the take ended), the selected key and scale, pitch-correction and mix settings, and analysis and pitch-corrected versions of takes. The app also keeps a list of IDs of deleted songs so that restoring an older backup does not bring them back; this list is kept without a limit. There is no fixed limit on the number of songs or takes; a single take can be up to 10 minutes and a beat up to 15 minutes. If a saved song cannot be read, the app leaves it untouched and shows that it could not be read.
The app may also store basic operating information such as timing calibration offsets for each audio route, whether the introduction screens were shown, cached advertising settings and a cached More Apps list.
The developer does not run a server that receives your songs. The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore, but it does not upload your recordings, beats or song names. When you open the developer's other apps in the menu, app icons are loaded from the web addresses in that list.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as screen views; beat import results (sample-rate range and channel count); microphone permission results; record start and stop (audio route, whether it was calibrated, why it stopped and a length range); recovered takes (count and length range); calibration results (result, offset range and audio route); pitch-correction results (scale and ranges for strength, speed, voiced share and processing time); key and scale changes; export results (format, content, render, share or save, and a length range); cancelled steps; review requests from the menu or exit dialog; ad revenue events (ad format, value, currency and precision); app version, device type, and app-instance identifiers. These events do not include audio, song names or file names.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
The app shows ads through Google AdMob. A banner may appear at the bottom of the song list, and an ad may appear in the exit dialog. Full-screen ads may appear when the app returns to the foreground, and occasionally on the result screen after an export (never after your first export in a session). The app does not start a full-screen ad while a take is recording. AdMob may also request ads from the InMobi mediation network. Google and InMobi may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location even though the app has no location permission.
PERMISSIONS AND ADVERTISING CHOICES
Apart from the microphone described above, the app does not request camera, location, contacts, photos and videos, Bluetooth, health data, or notification permissions. It uses internet access and the Android advertising ID permission for the services above, and vibration for short haptic feedback.
When the app starts, Google's consent message (UMP) is checked first. Where consent is required (for example in the EEA and UK), personalized advertising stays off unless your choice allows it, and if the consent result does not allow ad requests, or the consent check has not completed, the app does not request ads. If the consent message cannot be loaded, the app still requests non-personalized ads, personalized advertising stays off, and "Privacy choices" is not shown until the app is started again. Where Google requires it, the app's menu shows "Privacy choices", which reopens the consent message so you can change your advertising choice. The app works whatever you choose.
STORAGE AND YOUR CONTROL
You can delete a take in the studio (after a confirmation; "Undo" is offered briefly) and delete a song from the song list (after a confirmation). After you delete a song, "Undo" is available until you tap "Done", delete another song, or the app is restarted; then the song's record, its analysis and pitch-corrected files, and its audio files are removed, except audio that another song still uses. While any saved song cannot be read, the app keeps audio files it cannot match to a song. You can also clear the app's data in Android settings or delete the app.
The app is configured to opt out of Android cloud backup and device-to-device transfer for its data, so songs and recordings are not included in Android's automatic backup of this app.
Exported audio files (M4A or WAV) are written to the app's cache. "Share" sends the file through the system share sheet, and "Save to device" lets you pick a location and copies the file there; the app does not delete copies kept elsewhere. When the app starts, it removes exported files from its cache once they are more than 24 hours old; files whose age it cannot check may be kept. "Create backup" writes a set of backup files to the app's storage with your readable songs, their beats and takes, and the deleted-ID list, and you share or save each part yourself. Backup sets made in the app, and backup parts you restore, are kept in the app's storage; when you delete a song, the app removes it from those sets and removes a set once none of its songs remain (sets it cannot verify may be kept). Restoring adds or updates songs from the backup, and songs on the backup's deleted-ID list are not restored.
Because we do not receive your songs or recordings, we cannot delete them for you; the controls above remove them from the app. For questions about data processed by Google or InMobi, or to ask us for help with a privacy request, contact us at the address below.
Data processed by third parties is retained according to their service settings and policies. We use these services under their applicable terms, and we ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy.
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
- InMobi Privacy Policy: https://www.inmobi.com/privacy-policy
SECURITY
Your songs, recordings, backup sets and exported files are kept in the app's private storage on your device, which the operating system protects from other apps; they are not separately encrypted by the app, so protect your device with a screen lock. Apart from the limited analytics events described above, the app does not upload your saved data. Communication between the app and Google services and the ad mediation partner uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app collects to what is described in this policy.
IMPORTANT NOTICE
Timing alignment and calibration are estimates, and pitch correction changes your recording; check the result before you share it. Use headphones at a safe volume. Only import, record and share audio you have the right to use.
CHILDREN
The app is not directed to children under 13, and we do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Kyu-Hee Jang (Google Play developer: Global Utility App Maker)
Email: wkdrb2100@gmail.com