How the TV app and account website use your information, and the controls available to you.
Limefire operates this deployment and is the contact for its account data. Contact support@limefire.tv.
LimeFire uses Supabase for email sign-in and account storage. Account records include your email, profiles, watchlists, preferences, viewing history and resume positions. File progress can include a provider file identifier, filename, episode details, playback-session identifier and timestamps. Paired-TV records link a device name and profile to your account.
The app server also keeps file-to-catalog associations so different files for the same movie or episode can share useful artwork and resume information. We use these records to run your account, pair TVs, organize your library and save your place.
Supabase processes application customer data for its customers. Its own notice explains that role separately from data about users of Supabase’s website. See Supabase’s privacy notice.
When paid signup is enabled, Stripe processes checkout, payment methods and subscription management. LimeFire stores billing customer and subscription identifiers, plan status, renewal periods and trial eligibility to manage access. LimeFire does not receive or store your full card number or card security code.
Stripe maintains its own payment and transaction records. Deleting a LimeFire account does not erase Stripe’s records or cancel a provider subscription. Resolve an active LimeFire subscription through Plans & billing before deleting your account. See Stripe’s privacy notice.
Provider API keys are encrypted in LimeFire’s server storage. A key grants account access; encryption does not prevent its approved use by the application.
Video travels directly from the provider to the TV or chosen player. LimeFire does not relay the video through its application server. Disconnecting a provider stops future credential delivery or link requests. Reset the key with the provider to revoke credentials or links already shared with a TV or player.
Catalog queries, title and episode identifiers, and artwork requests may be sent to TMDB and the configured source-discovery service. Your connected provider receives the file, hash or link requests needed for your selections. These services process requests under their own policies.
Trakt is optional. If you connect it, LimeFire stores encrypted authorization tokens, basic Trakt account information and your selected permissions. Imports can bring history and watchlist entries into the chosen LimeFire profile. Sending completed watches or list changes back to Trakt requires enabling those sync choices. Disconnecting Trakt stops future synchronization; previously imported items remain in LimeFire until removed or the account is deleted.
A separate TV discovery permission lets LimeFire read your personal Trakt recommendations and private Trakt watchlist for the chosen profile’s Home screen. LimeFire uses exact TMDB title identifiers from those results to request current catalog cards from TMDB. Private feed results are cached briefly for that profile; enabling discovery does not import history or lists, or enable sending viewing and list changes to Trakt. Turning this permission off stops future discovery access.
Sign-in uses necessary session cookies. Your browser or TV can keep local preferences, profile state and progress needed for its interface. Network addresses and request information are processed when you reach the website, Supabase and connected services.
When signup verification is enabled, Cloudflare Turnstile processes a challenge and its result is sent to Supabase Auth. See Cloudflare’s privacy notice, including its Turnstile addendum.
Optional browser diagnostics are off unless monitoring is configured and you opt in. When enabled, limited error counts and page timings can be sent to the configured monitoring services. Watch history, searches, recordings and playback links are excluded from those optional diagnostic events. You can turn diagnostics off in Account settings.
Where account data controls are enabled, open Account → Your account data to download your LimeFire records or delete your account. The JSON export excludes provider keys and playback links. Deletion requires a recent sign-in and typed confirmation.
Confirmed account deletion removes the active LimeFire server account and its related account records. File-to-catalog cleanup is attempted separately; the confirmation tells you if operator cleanup is still needed. Contact support with that cleanup reference if one is shown.
LimeFire deletion does not delete your provider or Trakt accounts, their files or history, or cancel their subscriptions. Local app state and previously downloaded exports can remain on devices you control. Clear that storage separately and reset provider keys to revoke previously delivered copies.
Account records remain available for the account features described above until you remove them or delete the account. Deletion applies to active LimeFire stores; restricted backup copies have a separate rotation cycle.
The weekly server-backup plan retains host copies for 28 days when enabled. This does not establish a Supabase database backup retention or immediate-erasure deadline. Supabase storage and backups follow the project’s actual configuration and provider policies; see Supabase’s backup documentation.
Provider systems and copies already delivered to devices have their own lifecycles. Deleting a LimeFire account does not erase every backup, provider record or device copy immediately.
Use the verified contact listed above for account access, correction, deletion or privacy questions. If self-service controls are unavailable in private staging, ask the operator for help.Support guidance explains what to include without sharing keys or private links.
