Privacy Policy

Effective date: 5 May 2026 Applies to: SeerrClient for iOS, and to future SeerrClient apps for Android, Apple TV, Android TV, Amazon Fire TV, Samsung Tizen, and LG webOS as they ship. Provided by: Frost Forge Labs Inc., an Ontario, Canada corporation.

Summary

SeerrClient is a thin client for media-request servers you operate yourself. It does not run any backend on our side and we do not collect any personal information about you. Everything sensitive — your credentials, your server URL, your activity — stays either on your device or on the server you configured.

• We have no analytics, no telemetry, no crash reporting, and no advertising.
• We use no third-party tracking SDKs.
• We do not have a server that talks to your device.
• Your credentials live in the iOS Keychain on your device.
• Your media requests, watchlist, and login go directly to the Jellyseerr, Overseerr, or Seerr instance you configured.

What we do not collect

Frost Forge Labs Inc. does not collect, store, transmit, sell, or share any information about you through SeerrClient. Specifically:

• No account is created with us. There is no SeerrClient account; you sign in to your own server.
• No usage analytics. We do not track which screens you open, what you search, what you request, or how long you use the app.
• No crash reports. SeerrClient does not contain a crash reporting SDK.
• No advertising or ad SDKs.
• No location data, contacts, microphone, photos, or camera access.
• No cross-app or cross-site tracking identifiers.

What stays on your device

SeerrClient stores the following locally on the device, and only on the device:

• Server credentials — your username, password, or API token for your media-request server. Stored in the iOS Keychain. Protected by the device passcode and, when enabled, Face ID.
• Server URL and connection settings — stored in UserDefaults so the app can reconnect on launch.
• Session cookies issued by your server — stored in the standard iOS HTTPCookieStorage for the app.
• Theme preference (light/dark/system) — stored in UserDefaults.
• Cached media metadata — posters, request status, watchlist entries, and similar data fetched from your server are cached locally to reduce load times.

You can clear all of this by signing out (Profile → Sign Out) and/or by deleting the app, which removes the app’s Keychain items and on-device storage.

What goes to your own server

Every action that produces network traffic in SeerrClient is directed at the media-request server you configured (Jellyseerr, Overseerr, or Seerr). That includes:

• Sign-in requests (your username/password or token)
• Searches, discover feeds, media metadata fetches
• Request creation, request approvals, and request status checks
• Watchlist reads and updates
• Profile information

Frost Forge Labs Inc. has no access to that server, and we never see, intercept, or proxy that traffic. The privacy policy of your server’s operator (which may be you yourself, in a self-hosted setup) governs what happens with that data once it arrives.

Third-party network destinations

In normal use, SeerrClient also makes network requests to a small number of third-party services. We list each one here so you know exactly what touches your device.

Plex (only when you sign in with Plex)

If you choose Sign in with Plex, SeerrClient performs the standard Plex OAuth pin flow:

• POST https://plex.tv/api/v2/pins to create an authentication pin.
• The Plex web auth page (https://app.plex.tv/auth) opens in Safari so you can sign in to Plex directly with Plex.
• GET https://plex.tv/api/v2/pins/{id} is polled until your sign-in completes.

We do not see your Plex password — it is entered in Safari on Plex’s own page. SeerrClient receives only the resulting auth token, which is then forwarded to your media-request server. If you do not use Plex sign-in, no traffic is sent to plex.tv.

Plex’s privacy policy: https://www.plex.tv/about/privacy-legal/privacy-policy/

TMDB image CDN

Posters, backdrops, and cast photos shown inside SeerrClient are loaded directly from The Movie Database’s image CDN at https://image.tmdb.org. No personally identifying information is sent — the request is for an image at a path your server (or the public TMDB catalogue) returned. As with any image load, your IP address is visible to the CDN.

TMDB’s privacy policy: https://www.themoviedb.org/privacy-policy

Apple App Store and TestFlight

When you install or update SeerrClient through the App Store or TestFlight, Apple may collect data according to Apple’s own privacy policies (App Analytics, crash data, install metrics). That data flows from your device to Apple, not to us. Frost Forge Labs Inc. has access only to the aggregate, anonymised information Apple provides through App Store Connect (e.g. counts of installs, crashes), and we cannot identify individual users from it.

Apple’s privacy policy: https://www.apple.com/legal/privacy/

Permissions SeerrClient requests

• Face ID / Touch ID — used to unlock the app and protect Keychain items, when you enable biometric protection. The biometric check happens entirely on-device through Apple’s Local Authentication framework. No biometric data leaves your device.
• Local network / arbitrary loads — SeerrClient must be able to connect to media-request servers running on your home network or a self-hosted host that may not have a publicly trusted TLS certificate. Connecting to such a server is your choice.

Children’s privacy

SeerrClient is intended for adults and a general audience managing their own home media servers. It is not directed at children under 13, and we do not knowingly collect any data from anyone — including children — through the app, because we do not collect data from anyone at all.

Your data rights (GDPR, CCPA, and similar laws)

Because SeerrClient does not collect personal data on our side, there is nothing for us to access, export, correct, or delete on your behalf.

If you want to access, correct, or delete data held by your media-request server (your Jellyseerr, Overseerr, or Seerr instance), please contact the operator of that server. In a typical self-hosted setup, that is you. Plex’s and TMDB’s data subject rights are handled by those companies under their own privacy policies linked above.

Security

• Server credentials are stored in the iOS Keychain, which is encrypted on the device using hardware-backed protection.
• Network traffic to your server uses HTTPS whenever your server provides HTTPS. SeerrClient permits HTTP because many self-hosted home setups use plain HTTP on the local network; this is your decision based on how your server is reachable.
• SeerrClient is open source under the Apache License 2.0. You can audit how data is handled at https://github.com/Frost-Forge-Labs-Inc/SeerrClient-iOS.

Changes to this policy

When this policy materially changes, we will update the Effective date at the top of this page and note the change in the SeerrClient repository changelog. Continued use of SeerrClient after a change indicates acceptance of the updated policy. We will not retroactively change how older versions of the app behave.

Contact

For privacy questions, please open an issue on the SeerrClient repository:

• https://github.com/Frost-Forge-Labs-Inc/SeerrClient-iOS/issues

You can also reach Frost Forge Labs Inc. through the company website:

• https://frostforgelabs.com

Frost Forge Labs Inc. is a corporation registered in Ontario, Canada.