Last updated: October 2026
The app creates a random identifier and stores it on your device: in Apple Keychain on iOS and in app-private storage on Android, where it is excluded from device backups. We use this pseudonymous identifier to authenticate app requests, associate conversions, coin balances, purchases, and subscription access with your installation, and restore access across sessions. Voix does not require your contact details to use the service.
Voix accepts EPUB, TXT, FB2, FB2.ZIP, DOCX, and PDF files. When you request a conversion, or when the app needs our servers to analyze a file to show its chapters and price, we process the uploaded file to extract its text and generate audio. The source file, conversion status, and generated audio may be stored on our service infrastructure so that the conversion can be processed and accessed from the app. We do not sell or use book contents for advertising.
If you use Scan Pages, the app uses the camera to recognize printed text on your device, on both iOS and Android. Camera images are not uploaded or stored by Voix. Recognized text remains on your device unless you explicitly continue to audiobook conversion; in that case, the recognized text is submitted and handled as Content You Provide under Section 1.2.
We collect information about how you use the app, including onboarding progress, file format selections, conversion events, paywall interactions, coin balances, and subscription status. Camera scanning analytics may include whether the feature was opened and the number of passages used, but not recognized text or camera images. We use this data to provide the service, understand product performance, and improve the app and our marketing.
We may collect basic device and app information, such as OS version, device model, app version, and pseudonymous installation identifiers, for analytics, compatibility, fraud prevention, and debugging. Firebase Analytics, Adjust, and, on iOS, Airbridge help us measure app installs and advertising performance. On iOS, if you allow tracking through Apple's App Tracking Transparency prompt, they may access Apple's advertising identifier (IDFA). Without that permission, Airbridge and Adjust may use other permitted device identifiers for measurement. On Android, Firebase Analytics and Adjust may access the Google advertising ID, and Adjust reads the Google Play Install Referrer to learn which campaign led to an install. You can reset or delete the advertising ID in your Android settings. Declining tracking or deleting the advertising ID does not limit app features.
We use Apple's AdServices attribution mechanism to understand whether an install resulted from an Apple Ads campaign. Apple can provide standard attribution without ATT permission; more detailed attribution is available only when you allow tracking. The app does not place the raw Apple attribution token in analytics events.
If you allow notifications, the app registers a push token with Apple Push Notification service on iOS or Firebase Cloud Messaging on Android. We store that token with your installation identifier and use it only to tell you when an audiobook is ready. You can turn notifications off in your device settings at any time.
We use Apple's App Store purchase services, App Tracking Transparency, and AdServices attribution. Apple's privacy policy applies to Apple's processing of this data.
On Android, purchases and subscriptions are processed through Google Play Billing, and the Google Play Install Referrer is used for install attribution. Google's privacy policy applies to Google's processing of this data.
Subscription and in-app purchase management is handled by RevenueCat. RevenueCat receives the app's pseudonymous identifier, purchase and subscription data, and Apple Ads attribution data when that integration is enabled. We may also send Airbridge and Adjust device identifiers and, on Android, the Google advertising ID to RevenueCat so subscription events can be matched to their advertising source. RevenueCat's privacy policy applies to its processing.
We use Google Firebase Analytics to measure app usage and advertising performance, Firebase Remote Config and A/B Testing to configure and compare app features, and, on Android, Firebase Cloud Messaging to deliver notifications. Firebase may process app interaction, device, installation, and diagnostic information according to Google's terms and privacy documentation.
We use Cloudflare Workers and R2 for API infrastructure and storage. Cloudflare's privacy policy applies to its processing of this data.
On iOS, we use Airbridge to measure app installs and advertising attribution. Airbridge may process device identifiers, app events, and campaign information. We may send subscription event data from RevenueCat to Airbridge when that integration is enabled. Airbridge's privacy policy applies to its processing.
We use Adjust to measure app installs and advertising attribution. Adjust may process permitted device identifiers, IP addresses, app events, and campaign information. When enabled, RevenueCat sends subscription lifecycle and revenue events to Adjust to associate purchases with their advertising source. Adjust’s privacy policy applies to its processing.
This app is not intended for children under 13. We do not knowingly collect personal information from children.
We may update this privacy policy from time to time. We will make the current version available in the app and on our published privacy page.
If you have questions or privacy requests, please contact us at support@getdimelo.app.