SeerrSense

Privacy

What SeerrSense does with your data

Last updated 6 November 2026

SeerrSense sits between an AI assistant and your own Overseerr or Jellyseerr. It holds as little as it can, and this page says plainly what that is. When it changes, the date above moves and the history is public in the repository.

What is stored

DataWhyKept until
Your Google account identifier and email address To know whose request this is and whether you are allowed to use the server You disconnect, or your tokens expire
The address and API key of the Seerr you attached To search and request on your instance rather than a shared one You press Disconnect
Refresh tokens, stored as a hash To keep an assistant connected without asking you to sign in daily 30 days, or until revoked
Pending sign-in state: the handoff between Google, this server and the client To carry one login from Google back to the client that started it 10 minutes
A daily count of language-model lookups, per account To cap what one account can spend on the model each day 7 days
Page views: page address, referrer, browser, operating system, device type, screen size, language, and country, region and city derived from the IP address To count visits via self-hosted Umami at stats.mctl.ai. It sets no cookies and does not store the IP address itself; the visitor identifier is computed from the IP address and browser details with a salt that rotates monthly 2 years

Your Seerr API key is encrypted with AES-256-GCM before it is written down, and it is never returned by the interface, not even partially masked. No password of yours is ever seen by this service: signing in happens on Google's own pages.

What is not stored

Where data goes

What the operator can see

This is a self-operated service, not an anonymous one, and it is honest to say what that means. The person running this server administers the database and holds the key that encrypts stored credentials, so they are technically able to read what is stored, including your Seerr API key. They do not do so as a matter of course, and nothing here is designed to make it convenient, but the encryption protects the data at rest and from anyone else, not from the operator. If that is not an acceptable arrangement for you, run your own copy: the server is open source.

Removing your data

Contact

Questions about any of this go to [email protected].