26 lines
971 B
Markdown
26 lines
971 B
Markdown
# Privacy and publishing posture
|
|
|
|
AmpFire is planned as a self-hosted music client for user-controlled Subsonic/Navidrome-compatible servers.
|
|
|
|
## Data handled by the app
|
|
|
|
- Server URL supplied by the user.
|
|
- Username and password/token used to authenticate to that server.
|
|
- Music library metadata returned by the user's server.
|
|
- Playback activity if scrobbling is enabled.
|
|
|
|
## First release goals
|
|
|
|
- No ads.
|
|
- No third-party analytics.
|
|
- No credential logging.
|
|
- No trust-all TLS bypass in release builds.
|
|
- Reviewer/demo server support before Amazon Appstore submission.
|
|
|
|
## Before Appstore submission
|
|
|
|
- Replace the temporary DataStore credential persistence with Android keystore-backed encrypted storage.
|
|
- Publish a privacy policy URL.
|
|
- Create app icon, banner, screenshots, short description, full description, and support contact.
|
|
- Provide Amazon reviewers with a demo server or built-in demo mode.
|
|
- Verify remote-only navigation on physical Fire TV hardware. |