Privacy Policy
Last updated: October 11, 2026
This policy describes data handled by AIOMetadata, including its optional Google Drive backup integration. AIOMetadata is self-hostable: the operator of the particular server you use controls that server and may have additional policies. This project website is informational and does not collect account data.
Information handled by an AIOMetadata server
Depending on how you use an installation, its operator may process:
- Configuration data you save, such as provider selections, preferences, and API keys you enter.
- Account identifiers and authentication data used to protect and load your configuration. Configuration passwords are stored as password hashes, not as the original password.
- Optional integration credentials and tokens for services you connect. These are stored by the server to operate those integrations.
- When you use the Jellyfin API integration, locally stored per-profile playback progress, watched/scrobble state, favorites, watchlists, dropped titles, ratings, and Jellyfin preferences.
- Technical request, error, and diagnostic information needed to operate and troubleshoot the server.
How information is used
The server uses configuration and integration data to provide metadata, catalogs, search, artwork, playback-state, and other features you enable. When you configure an external provider or connect a service, the server may send the relevant requests and information to that provider under its own terms and privacy policy. The server operator chooses the providers, deployment, logs, storage, and retention practices.
Optional Google Drive backups
If the server operator has configured Google OAuth and you connect Google Drive, AIOMetadata requests the https://www.googleapis.com/auth/drive.file permission. This scope allows the app to work with files it creates, rather than granting access to the user's entire Drive.
Each backup is associated with the saved configuration UUID and stored in the Google account you connected. A backup contains the saved configuration, including API keys and settings, as well as locally stored Jellyfin per-profile playback and watch state, favorites, watchlists, dropped titles, ratings, and preferences. Treat these files as sensitive.
Linked-service OAuth tokens, Jellyfin/API authorization tokens, and pending tracker writes are not included in Drive backups. History held only by an external tracker remains with that service and is not copied into this backup. The server separately stores the Google refresh token needed to schedule backups. Google processes Drive data under Google's Privacy Policy and Google API Services User Data Policy.
Daily backups are enabled after connecting. The default retention is 10 snapshots; the configuration owner can change the limit. When the limit is exceeded, older snapshots are deleted from Drive. Disconnecting removes the server's local Google authorization and stops future backups, but intentionally leaves existing backup files in Drive. You can remove those files from Drive yourself.
Storage, sharing, and retention
Configuration and integration data are stored by the operator of the AIOMetadata server you use. The project does not operate or control every self-hosted installation and cannot specify that installation's retention period, security measures, or access practices. Contact that server's operator for details about its data handling or to request access or deletion. Data sent to an external provider is also subject to that provider's terms.
Google Drive snapshots remain in the connected Google account until deleted by the retention process or by the account holder. Deleting an AIOMetadata configuration removes its local backup settings and Google token; it does not delete snapshots already in Drive.
Security
Use a trusted server operator, protect your account and Google account, and do not share backup files. Self-hosting operators are responsible for securing their database, server environment, backups, and any OAuth credentials they configure. No method of storage or transmission is completely secure.
Children
AIOMetadata is a metadata and media-catalog tool, not a service directed to children. The server operator determines who may use a particular installation.
Changes and contact
This policy may be updated as the project changes. For questions about a hosted installation's data, contact its operator. For questions about this project policy, use the project issue tracker.