Privacy
What Boomerplay Track stores, why it is used, who processes it, and how to ask about your data.
Last updated 9 November 2026
Boomerplay Track is operated by Kielerlabs. This page describes the data the application stores and the third parties it uses. It is not a statement that any particular law applies to you or to the operator.
Data stored in your account
The application stores the following categories of information so the tracker and its integrations can work:
- Account and sign-in: email address, username, display name, password hash, email-verification flag, account creation and update times, and session records. Session records include an expiry time and may include the IP address and browser user-agent that Better Auth records when you sign in.
- Tracking data: watch history with the watched date, action and source; playback positions; collection entries; watchlist entries; your 1–10 ratings; per-user activity timestamps; and account preferences such as hiding specials.
- Imports: the file you upload (a Trakt export ZIP or Netflix viewing-activity CSV), its file name and size, import status, counts, errors, and a Netflix review decision. Imported plays, ratings, watchlist, collection and playback entries become part of your tracking data.
- Connected Jellyfin server: the server URL, device ID, a pending Quick Connect code and secret with an expiry, the Jellyfin access token, and the Jellyfin user ID and username. These values are stored server-side and are removed when you disconnect Jellyfin or delete your account.
- Authorized apps: the OAuth client name, redirect URIs, scopes, grant metadata, access and refresh token records, and their expiry or revocation times.
- Catalog metadata: movie and TV metadata and artwork references cached from TMDB. This catalog cache is shared across the application and is not tied to your account.
Why the data is used
- To create and secure your account, keep you signed in, and let you recover access.
- To record what you watch, your progress, ratings, collection, watchlist and statistics.
- To import history you choose to upload and to show import progress and results.
- To connect to a Jellyfin server or an authorized client when you ask for it.
- To fetch movie and TV metadata and images from TMDB.
- To investigate abuse, security problems, support requests and legal obligations.
Who processes data
- Cloudflare hosts the application and provides the D1 database, R2 file storage, Workflows and network delivery. Data may be processed in countries where Cloudflare operates.
- TMDB supplies movie and TV metadata and artwork. Search terms and the titles or identifiers used for matching imports are sent to TMDB. Account email addresses, passwords and Jellyfin tokens are not sent to TMDB.
- Your Jellyfin server receives requests and the access token when you connect it. It may be operated by you or by a third party.
- Apps you authorize receive the access allowed by the scopes shown on the consent or activation screen.
- Cloudflare Email Service delivers verification and password-reset emails. Cloudflare receives your email address and the message, including its time-limited account link.
- If a support email is configured for this deployment, the operator's email provider processes messages you send to it. The provider is not identified in this deployment.
This version does not include advertising, third-party analytics, AI processing or payment services. The application does not sell personal data or use it for advertising.
How long data is kept
- Account and tracking data is kept while your account exists. Delete your account or contact the privacy contact to ask for removal.
- The original file of a finished import is kept for 30 days after the import finishes, or until you delete the import. An upload that never finishes is removed after about 2hours. Imported tracking data is not removed when the original file expires.
- An unapproved Netflix import review waits for up to 30 days. There can be at most 25 import records per account, with at most 3 running at once.
- Browser sessions expire after the configured session lifetime, which is 7 days by default. OAuth access tokens expire after 7 days and refresh tokens after 180 days unless revoked sooner. A Jellyfin token remains until you disconnect the server or delete your account.
- Shared catalog metadata, including cached TMDB data, may remain after an account is deleted because it is not personal tracking data.
Cookies and browser storage
The application sets a Better Auth session cookie, normally named better-auth.session_token; on HTTPS it may carry a __Secure- prefix. It is needed to keep you signed in.
Two functional browser-storage entries are also used:
boomerplay-track:episode-watch-datein local storage remembers whether episode actions use the current date or the release date on this device.- A session-storage value records a one-time page reload after a failed code-chunk load.
This version does not use advertising, analytics or cross-site tracking cookies, so it does not show a cookie-consent banner. That position must be reviewed if non-essential tracking is added.
Your choices and rights
Depending on where you live, you may be able to request access to, correction of, a copy of, or deletion of your data, and to object to or restrict some processing. Use privacy@boomerplay.app for a privacy request. Signed-in users may also have export and deletion controls under Settings → Data and account controls underSettings → Security.
You may also complain to the data-protection authority where you live. The operator's postal address and legal jurisdiction are not published in this deployment.
Security
Passwords are stored as hashes by Better Auth, and Jellyfin access tokens and pending secrets are kept server-side. Production traffic is served over HTTPS. No system is completely secure; report a suspected problem through the support page and do not send your password or access tokens.
Children
The service is not intended for children. The operator has not published a minimum age in this deployment. If you believe a child has created an account, contact privacy@boomerplay.app so it can be reviewed.
Changes
This page may be updated when the application or its data practices change. The date at the top shows the latest revision. Material changes should be announced in the application before they take effect.
Contact
Privacy requests: privacy@boomerplay.app. General support: support@boomerplay.app. See the support page for abuse and security reports.
TMDB is used for metadata and artwork. This product uses the TMDB API but is not endorsed or certified by TMDB.