1) Scope
This Privacy Policy explains how the App collects, uses, and shares information
when you use the mobile application.
2) Permissions, Media, and Local Files
The App requests permissions to let you record and to read/write the audio/video
files needed for conversion and playback.
Microphone permission
-
Used when you start recording your voice (Record & Convert / TTS use is separate).
-
The App uses microphone audio to create the recording you choose to process.
Storage / file access
-
Used to let you pick audio/video files from your device and to save/export the
converted results (for example: saving to Downloads via platform sharing / export).
-
The files are processed by the App so you can play and export your results.
What we do (and do not) collect from your media
-
You provide the audio/video content yourself. We use it to generate the outputs you request.
-
We do not request passwords, payment card data, or biometric identifiers.
3) Cloud AI Processing
Some features may process your content on our backend servers when on-device models
are unavailable or when cloud quality is selected. Before any upload, the App shows
an in-app permission dialog that explains what data is sent, who receives it, and requires
your agreement (a checkbox plus “I Agree — Allow”). Declining keeps processing on-device only.
Listing this information only in a privacy policy is not how permission is obtained — permission
is requested in the App itself.
What may be sent
-
Audio: recordings or files you choose to convert, or audio used to replace voice in a video.
-
Text: text you enter for Text-to-Speech.
Who processes the data
-
Our application servers (Voice Changer AI / songfinderapi backend).
-
OpenAI — speech and Text-to-Speech models, accessed via Puter.
-
ElevenLabs — optional voice style / speech-to-speech, accessed via Puter when that path is used.
These third parties receive content only to fulfill your request. We require that they provide
the same or equal protection of that content under their applicable privacy terms for this processing.
How we use it
-
Data is used solely to complete the conversion or TTS job you start.
-
We do not sell your media content. Temporary processing files are not used for
advertising profiles.
You can decline cloud processing and use offline models instead (after downloading
them). You can review this notice again from Settings → Privacy Policy.
4) Firebase (Analytics & Crash Reporting)
We may use Firebase services such as Firebase Analytics and/or Crashlytics.
These services help us understand app usage, performance, and crashes so we can improve reliability.
-
What can be collected: app usage events, device/app identifiers, crash reports, and other
technical metadata (for example device model, app version, and timestamps).
-
Why we use it: to troubleshoot crashes, improve features, and measure how users interact with the app.
Firebase is operated by Google. To learn more about Firebase and Google’s data practices,
you can refer to the official Google Privacy Policy:
https://policies.google.com/privacy.
5) Google AdMob (Advertising)
We may show advertisements using Google AdMob. AdMob helps support the app.
What data can be used for ads
-
Ad delivery / measurement identifiers: ad-related identifiers and similar technologies
used to display ads and measure performance.
-
Device information: non-sensitive technical data that helps AdMob deliver the correct ad.
Your ad-related controls
-
You can control ad personalization through your device’s advertising settings where available.
-
You can learn more and manage settings via Google ad privacy resources:
https://support.google.com/ads.
6) Your Choices
-
You can manage app permissions (microphone and file access) in your device settings.
-
You can allow or decline cloud AI processing when prompted before uploads.
-
You can download offline models and prefer on-device processing when models are ready.
-
You can limit advertising personalization using your device and ad provider settings where available.
-
If you disable recording permissions, the app can still be used for features that do not require microphone access.