Privacy Policy
Last updated: 7 November 2026
AudioSilo is a self-hosted audiobook player. The AudioSilo app is a client for an AudioSilo server that you (or whoever administers your server) run and control. In normal use, the app communicates only with the server address you provide, and the developer of AudioSilo operates no service that receives, stores, or processes your data, apart from the community metadata service your server can use, described below.
Who we are
AudioSilo ("the app") is published by KodeStar. Questions about this policy can be sent to [email protected].
The short version
- We do not collect, see, sell, or share your personal data.
- We use no analytics, advertising, tracking, or crash-reporting services.
- All of your content and account data lives on your own AudioSilo server and on your own device, not with us.
- The app contacts only the server you tell it to connect to.
What information the app handles
Because AudioSilo is self-hosted, almost everything stays between your device and the server you connect to.
Stored on your device
- Your session token, kept in the operating system's encrypted secure storage (Keychain on iOS, Keystore on Android) so you stay signed in.
- Downloaded audiobooks: audio files and cover art you choose to download for offline listening, stored in the app's private storage.
- App preferences: settings such as playback speed, theme, and language, plus a local cache of your listening position.
Sent to the server you choose
- When you sign in or pair, and as you listen, the app sends requests to the AudioSilo server address you provide. Your account credentials, listening progress, bookmarks, notes, and favourites are stored on that server, operated by you or your server's administrator.
- We (KodeStar) have no access to your server, your account, or any data on it.
There is no central AudioSilo account system. Your account exists only on your self-hosted server.
Device permissions
- Camera: used solely to scan a pairing QR code when connecting to your server. Images are processed on-device to read the code and are never stored or transmitted to us.
- Background audio: so playback continues when the app is backgrounded or the screen is locked.
- Network access: to communicate with your AudioSilo server.
Optional public demo
AudioSilo offers an optional, web-based public demo (at demo.audiosilo.app) so people can try the player without setting up a server. The demo server creates a temporary, throwaway guest session with sample content; no personal account is created and demo data is ephemeral. Using the demo is optional and separate from connecting to your own server.
Analytics, advertising, and tracking
AudioSilo contains no analytics, advertising, attribution, or third-party tracking software. We do not profile you and do not build advertising identifiers. Apart from the community metadata service below, nothing about your usage is reported back to us.
Community metadata
An AudioSilo server can look its books up in the community metadata database at meta.audiosilo.app (on by default; the server's administrator can turn it off). The app never talks to it; the server does. To look a book up the server sends the book's ASIN or ISBN, never a file path or who is listening. Match sends a little more (title, author, series, length, narrators, language, any ASIN or ISBN in the book's tags, anything the administrator types and up to three folder or file names), and only when an administrator opens Match or runs it on the library.
Optional community report
If the administrator of an AudioSilo server turns on the off-by-default setting Help complete the community database, that server looks up its books' Audible ASINs in the community database (up to 500 a day, each again after 30 days; with a local copy of the database these lookups stay on the server) and sends its metadata service (meta.audiosilo.app unless the administrator points it elsewhere), once a day, the ASINs the database does not know. No titles, file paths, server name or listener information are sent. The service stores each ASIN with a count and the first and last date it was reported, and stores no IP address with them. An address is held in memory for about a day after its last request to enforce a rate limit. At meta.audiosilo.app these reports are not written to the access log when they arrive over HTTPS, which is how AudioSilo servers send them. The web server's error log can still record the address of a request that goes wrong, such as a report that cannot reach the service while it is restarting. The meta.audiosilo.app privacy page has the details.
Third-party services
The app integrates no third-party data-collecting services. The only third parties involved are the app stores (Apple App Store, Google Play) that distribute the app, and the server you connect to, each governed by its own operator's terms.
Videos on this website
A video in a post on the audiosilo.app blog may be hosted on YouTube. Nothing loads from YouTube until you press play on it: until then the page shows its own preview. Once you press play, the video loads from YouTube's privacy-enhanced domain (youtube-nocookie.com), or, with JavaScript off, the button opens it on youtube.com. Either way YouTube (Google) may set cookies or use local storage on your device, under Google's Privacy Policy.
Data retention and deletion
- On your device: uninstalling the app removes its local data, including the stored session token, downloaded audiobooks, and preferences.
- On your server: your account and listening data are retained according to your server's configuration. Because the server is under your control, you can delete your account and its data there at any time.
Children's privacy
AudioSilo is a general-audience audiobook player and is not directed at children under 13. We do not knowingly collect personal information from children; indeed, the app collects personal information from no one.
Security
Communication between the app and your server uses standard transport security (HTTPS, which your server can be configured to enforce). Your session token is held in the device's encrypted secure storage. Because we hold no user data centrally, there is no central store of your information to be breached.
Changes to this policy
We may update this policy as the app evolves. Material changes will be reflected by the "Last updated" date above and published at the same URL.
Contact
Questions about this privacy policy can be sent to [email protected].