legal/privacy
Privacy Policy
Effective date: May 13, 2026
This policy describes how Servarr Companion handles information when used to manage self-hosted media services.
Who operates Servarr Companion
Servarr Companion is operated by Petllama. Contact: [email protected].
Information Servarr Companion may process
- Service configuration, such as local service URLs and API keys entered by the operator.
- Media library metadata from configured services, such as titles, seasons, episodes, paths, status, quality, and timestamps.
- Download client status from configured Deluge or qBittorrent instances.
- Indexer and subtitle-related metadata from configured Prowlarr or Bazarr instances.
- Public title metadata returned by TMDB when metadata discovery is used.
- User-selected .torrent files opened through Android's file picker or open-with flow.
- Application logs and diagnostics needed for troubleshooting.
How information is used
- To connect to services configured by the operator.
- To display and manage library, download, subtitle, indexer, and metadata state.
- To send user-selected .torrent files to the operator's configured download client.
- To troubleshoot failures and improve reliability.
- To help protect access to configured services and app settings.
Storage and sharing
In a typical self-managed setup, Servarr Companion data remains on the device or infrastructure controlled by the operator. Servarr Companion does not sell personal information, does not use advertising data sharing, and this public website does not include tracking scripts.
Network security
Servarr Companion supports HTTPS when configured by the user. It may also support HTTP for local network or self-hosted services. Operators are responsible for configuring their own server security, reverse proxy, and network access.
Operator controls
Operators can remove local app data, delete configuration, revoke or rotate service API keys, and remove connected services from the app.
Security recommendations
Use HTTPS for exposed services, prefer LAN or VPN access, use strong credentials, and create least-privilege API keys where supported.
Contact
Questions: [email protected]