1. Overview
Wosp ("the app", "we", "us") is an audio player for Android, developed by Borisovskiy Artem. This policy explains what information Wosp accesses on your device and through the services it connects to, why it accesses it, and what happens to it.
The short version: Wosp plays audio from your device and, if you choose to connect it, from your own Google Drive. We do not operate a backend server, we do not sell data, and we do not run advertising. The only outside parties involved are Google's own services — Firebase (crash reports and usage analytics) and Google Drive (only if you link it).
2. What we access, and why
| Category | Why Wosp accesses it | Leaves your device? |
|---|---|---|
| Audio files on your device | To scan, list, and play your local library | Stays on device |
| Google Drive files you select (optional) | To display and stream only audio files you choose in Google's file picker | Google's servers only |
| Bluetooth device list | To route playback and controls to connected headphones/speakers | Stays on device |
| Usage & interaction events | To understand which features are used, via Firebase Analytics | Google/Firebase |
| Crash & diagnostic reports | To find and fix bugs, via Firebase Crashlytics | Google/Firebase |
| Notification for playback controls | Required by Android to show the lock-screen / status-bar player | Stays on device |
2.1 Audio files stored on your device
Wosp reads audio files and their tags (title, artist, album art) using the Android permissions READ_MEDIA_AUDIO and, on older Android versions, READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE. This is used only to build your library and play tracks on your own device. Wosp does not upload your local audio files anywhere.
2.2 Google Drive (optional)
If you choose files from Google Drive, Wosp requests the drive.file scope. This grants access only to files you select through Google's file picker; Wosp cannot browse your whole Drive. Selected audio is streamed from Google Drive and is copied to your device only when you choose the download action in the app. Wosp does not operate a server or send these files to any server it controls. You can revoke access at any time from your Google Account's third-party access settings.
2.3 Bluetooth
Wosp uses BLUETOOTH / BLUETOOTH_CONNECT only to detect connected audio devices (headphones, speakers, car units) so playback and hardware media buttons work correctly. This is not used to scan for or track nearby devices for any other purpose.
2.4 Usage & diagnostics
Wosp uses Firebase Analytics and Firebase Crashlytics, both operated by Google. Analytics may collect app interaction events and device/app identifiers (such as an advertising or installation identifier); Crashlytics collects crash stack traces, device model, and OS version when the app fails unexpectedly. Both are used only to understand feature usage and fix bugs — see Section 4 for how Google handles this data.
2.5 Notifications
POST_NOTIFICATIONS is used only to show the media playback notification (required by Android for background/lock-screen controls). Wosp does not send marketing or promotional push notifications.
3. What Wosp does not do
- We do not operate a backend server that stores your files, your library, or your listening history.
- We do not require an account, username, or password — the only sign-in is Google's own, and only if you choose to link Drive.
- We do not sell or rent personal data to anyone.
- We do not run third-party advertising or ad-tracking SDKs.
4. Third-party services
Wosp relies on the following services, each governed by its own provider's privacy policy:
- Google Firebase (Analytics & Crashlytics) — see the Firebase privacy and security policy.
- Google Drive API — used only with your explicit sign-in and for files you select; see the Google Privacy Policy.
Wosp's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
5. Your choices & data retention
- Disconnect Google Drive at any time from your Google Account's third-party access page; Wosp immediately loses the ability to read your Drive files.
- Clear local data by uninstalling the app or clearing its storage in Android Settings — this removes your locally cached library data from your device.
- Limit ad personalization by resetting or opting out of your advertising identifier in your device's Google Settings; this reduces what advertising identifiers Firebase Analytics can associate with your device.
- Analytics and crash data retained by Firebase follows Google's own retention controls, which we configure but do not directly store.
6. Children's privacy
Wosp is not directed at children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us information, contact us using the details in Section 10 and we'll remove it.
7. Security
We rely on Android's app sandboxing, Google's OAuth infrastructure, and Firebase's platform security to protect the limited data described above. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.
8. Your rights
Depending on where you live, you may have the right to request access to, correction of, or deletion of personal data associated with you, to object to or restrict certain processing, or to receive your data in a portable format. Since Wosp keeps your library and files on your own device and your own Drive, most of this data is already directly in your control. For anything held by Firebase on our behalf, contact us using the details below and we will forward or fulfil the request.
9. Changes to this policy
If we change what Wosp accesses or how it's used, we'll update this page and change the effective date above. Material changes will also be reflected in the app's release notes.
10. Contact
Questions about this policy or your data can be sent to borisovskiy.dev@gmail.com.