Privacy Policy

Summary

vbreader does not collect, share, sell or transmit your personal data to the developer. There is no vbreader account, no sign-up, no ads, no analytics, no crash-reporting service and no in-app purchase. Nothing is sent to the developer. Optional Portable Positions writes user-controlled shared records; that is different from developer collection or a vbreader cloud service. This matches this candidate's Google Play Data safety answers: no data types are declared as collected or shared, and nothing is transmitted off this device to the developer.

You choose your audiobook folder

vbreader uses Android's Storage Access Framework. You pick a folder using Android's own system picker, and Android grants vbreader read access to that folder. vbreader reads that folder to build your local library and to notice later changes; it never picks a folder for you and never scans your whole device. vbreader does not request broad storage access, and it does not delete your audiobook files.

What stays on your device

The app keeps its database, bookmarks and preferences in private device storage. Audiobook files remain in the source you selected. Optional progress records also go to the shared folder described below. Private data includes:

• the folder access grant you chose through Android's system folder picker;
• library details read from your files, such as title, author, narrator, duration and cover art when available;
• the app's own local database of books, editions, source folders and file order;
• your listening progress, playback speed and finished state, saved every few seconds; playback speed stays a stored local field and is not promised across reinstall or devices in 1.0;
• a local Android device identifier stored with that progress so the app can tell its own device apart from another; vbreader does not transmit this identifier anywhere, and never writes that raw value into the shared folder;
• your bookmarks;
• local app preferences and dismissed-card state.

vbreader does not send any of this to the developer, because there is no vbreader server to send it to.

The app's Report an issue action

The app includes a Report an issue action, offered from Ebooks: Coming Soon and the You screen, that opens an email draft addressed to vbreader@vbondariuk.com in your device's email app. The draft may include small, non-sensitive context, such as your app version, Android release and application programming interface (API) level, and device manufacturer and model, and never a device identifier, a file or folder path, a library or source name, your listening position, a log, database content, or an attachment. vbreader itself sends nothing when you tap it; you review the draft and choose whether to send it. If you send it, your email provider's privacy policy applies to that message instead of this one.

Portable Positions

Portable Positions can store acknowledged listening position, finished state and supported playback speed in a shared folder you choose through Android's system picker. vbreader reads and reconciles recognized records using exact audio identity. It has no cloud-provider API integration and does not run or control a sync service. Selecting the folder is enough; vbreader needs no network permission or provider login. Your chosen provider or separate software makes the folder available on your devices and controls its transport and retention. Playback speed is a stored local field; vbreader 1.0 does not promise reinstall or cross-device restoration of it.

Every app-created shared document is under the selected folder's exact .vbreader subfolder: the setup manifest and checksummed journals. No audiobook files are copied there. Journals contain content/timeline evidence, duration, position, finished state, playback speed, dataset and portable-book identifiers, random installation writer identifiers, a pseudonymous stream-owner identifier and causal counters. The stream-owner identifier derives from an Android device binding and an app-scoped protected key; the raw Android device identifier and key material are not exported. Titles, paths, source grants, bookmarks, settings and layout decisions are not transported.

Only exact Edition audio with a compatible ordered timeline matches, with no path/title fallback or automatic re-encoded-copy matching. Different concurrent listening states need a choice. Records for audiobooks not on this device are preserved without creating playable entries. Provider errors leave local progress intact and retryable; checkpoints and provider copying can lag. Give shared-folder access only to software and people you trust.

A network-backed document provider can upload records when vbreader writes them, using its own network access, immediately or later. No app Internet permission does not prevent this transfer. The provider's terms and privacy policy govern its handling. The developer does not receive, collect or share these app records; that does not mean the records cannot leave your device.

Software you separately choose to point at that folder, such as a sync client, a cloud-storage app, another file provider, or your device's own backup, can still copy the bytes in that folder on its own schedule. Independent copying and provider-mediated uploads are not a vbreader sync service. The provider controls its transport and retention; vbreader does not guarantee copying.

Android system backup

vbreader 1.0 disables Android automatic app backup. Android does not back up vbreader's internal library database, listening history, progress, bookmarks or settings to your Google account, and does not restore that app data onto another installation.

The user-owned .vbreader data remains after uninstall, but app-private state and folder grants do not. After reinstalling, reselect audiobook sources and the Portable Positions folder, then choose Adopt existing. Disconnect keeps shared data and local progress. Deleting shared data is a separate confirmed action scoped to the displayed dataset and may affect other devices. The shared folder can be copied by software you choose, such as a device-transfer or cloud-storage provider. That is separate from Android app backup; a write to a network-backed provider may trigger an upload even though the app has no network permission.

Planned features are not shipped features

Some pages on this site describe a fuller edition planned for later, including server sources, an ebook reading, server sync and artificial intelligence (AI). None of that is part of the local build this policy describes; shared-folder Portable Positions is included as described above. If a later release changes what data the app collects, shares or transmits, this policy and the Google Play Data safety declaration will both be updated before that release ships.

Children

vbreader is not designed for children. It is an audiobook player for files you already own. The app does not knowingly collect personal information from children, and it does not collect personal information from anyone for the developer.

Deleting your data

You can clear vbreader's local data using Android's own app-storage settings, or by uninstalling the app. This removes private listening state but not audiobook files or shared .vbreader data. Because that shared data lives in a folder you selected, it is yours to remove: Portable Positions offers an explicit confirmed Delete shared data action in-app, or you can delete the .vbreader subfolder yourself with any file manager. Either route leaves your audiobook files untouched. Because vbreader does not hold your data on a developer server, there is no separate server-side account or profile to delete.

Contact

Data controller: vbondariuk software, the individual developer who publishes vbreader as com.vbondariuk.vbreader, is the data controller for the information this policy describes.

For support requests or privacy questions, email vbreader@vbondariuk.com, or see the Support page.