luroka ← Back to Luroka

YOUR SPACE

Privacy policy.

Last updated: November 12, 2026

This policy explains how Luroka handles information when you use the Luroka app, our supporting services, and this website. Luroka is an independent media client: it connects to servers and services that you choose. Questions or privacy requests can be sent to privacy@luroka.app.

Information stored on your device

Luroka keeps settings, profiles, server connection details, authentication tokens, viewing and playback state, downloads, cached metadata and artwork, and diagnostic information on your device as needed for the features you use. Kids-profile restrictions, activity totals, screen-time settings and parent PIN settings are stored locally; they are not synchronized parental controls across every device.

Some connection credentials are encrypted in the app database, but the encryption key is also stored in the app’s local preferences. Someone with access to both may be able to recover them. Protect your device and any backups. If you export a backup, you choose where to save or share it; it can contain sensitive information.

Servers and services you connect

When you connect Plex, Jellyfin, Emby or another supported server, the app communicates with that server and, where needed, its associated account service. It sends the credentials and requests required for authentication, browsing, searching, playback, downloads and synchronizing watch progress. Server operators can receive your IP address, account information, device or session details, requested media and viewing activity, depending on the service and how you use it.

Optional connections such as MyAnimeList, AniList, SIMKL, MDBList and Seerr receive information necessary for the features you enable, such as account authorization, title identifiers, ratings or watch progress. We use a Luroka-operated authorization relay for supported tracker sign-ins. Trakt is currently disabled in the Luroka builds described here. Your connected services have their own privacy practices and retention periods.

Public discovery can contact Cinemeta and, when configured, TMDb and other metadata or artwork providers. Requests can include your IP address, search terms, title identifiers and language or region settings. Trailers and their thumbnails may use YouTube or its providers. These services may receive information directly when content is requested or opened.

Optional cloud backup and TV setup

Some test builds may offer an optional encrypted cloud backup. No Luroka account or separate registration is required. You choose the profiles to include and whether to include saved server and integration credentials. The backup may contain profile details, preferences, parental controls and viewing or screen-time data. Downloads are not included. Shared credentials may give access to information beyond the selected profiles. The app encrypts the backup on your device before upload; the Luroka backup service stores the encrypted backup and the values needed to find, expire and delete it. The service also receives ordinary connection information such as your IP address and may use it to limit abuse. Backups are intended to expire 90 days after upload, and you can request deletion in the app using the recovery code. Copies you save elsewhere and operational backups can have separate retention.

The recovery code is needed to restore or delete the cloud backup. Anyone who has it can access the backup, and Luroka cannot recover it if it is lost. Keep it private and do not send it to support. Availability, recovery and deletion may be limited during testing.

Some test builds may also offer phone-to-TV server setup. The phone authenticates with the media server you specify and sends an encrypted connection payload, including an access token and server and account identifiers, through a Luroka-operated short-lived relay to the TV. The relay processes pairing information and connection metadata, including IP addresses, and is designed to hold pairing sessions in memory for up to five minutes. Compare the code shown on both devices before proceeding. The media server receives the sign-in request and applies its own privacy practices. Camera access is used when you choose to scan a pairing or recovery QR code.

Camera and QR scanning

Camera access is optional and is used when you open the QR scanner for TV pairing or backup recovery. Camera images are processed on your device; Luroka does not upload these images to its servers. The decoded code is used for the pairing or recovery action you request, as described above. Treat QR codes containing pairing invitations or recovery codes as private. You can deny camera permission, close the scanner, or enter the code manually instead.

Android builds using Google ML Kit, including Luroka 1.0.8 build 2039, process scanner images on-device. Google states that ML Kit does not send those images or recognition results to Google, but the SDK sends performance and usage metrics and may contact Google for updates or compatibility information. This SDK processing is separate from Luroka’s optional support-log uploads. See Google’s ML Kit terms and privacy information, Android data disclosures, and Google’s privacy policy. Denying camera access prevents scanning; it is not a guarantee that an SDK already included in a build never communicates with its provider.

Replacement builds that use ZXing on Android do not include the Google ML Kit scanner SDK or its models. Their scanner does not include a scanner analytics service. On iPhone and iPad, scanning uses Apple’s on-device camera APIs. These statements about the scanner do not change the diagnostics or connected-service processing described elsewhere in this policy.

Watch Together and companion remote

Watch Together uses public Open Watch Party relays by default, or a relay you configure. Room participants and the relay may receive your chosen display name, room and connection information, media identifiers and playback synchronization events. Each participant needs their own access to the media; the feature is designed to synchronize playback rather than send the host’s video stream. Treat room codes as private invitations. Relay operators have their own privacy practices.

If you enable the companion remote, devices on your network exchange pairing, connection and remote-control information. Local-network access and discovery may expose the device to other devices on that network.

Diagnostics and support

If you choose to upload logs from the app, the upload can include app and device details, error messages, timestamps, media titles and information about the actions that led to a problem. The app attempts to redact credentials and other sensitive details, but redaction is not guaranteed to remove everything. Uploaded logs are intended to expire after three days and may be removed sooner; operational backups or logs may persist under the applicable backup schedule. Anyone who knows the log ID can read that upload while it remains available, so share it only with someone you trust.

Some builds may enable automatic crash and error reporting to a Luroka-operated diagnostics service using the Sentry SDK. Reports can include app version, device and operating-system information, crash details, stack traces and diagnostic context. Whether reporting is enabled depends on the build; the app attempts to remove sensitive information before reports are sent. Apple, Google or their testing services may also collect diagnostics under their own terms—for example, TestFlight collects beta testing data.

If you email us, we receive your email address and the contents and attachments of your message. We use this information to respond, provide support, maintain security and comply with applicable obligations.

Children and household profiles

A parent or guardian can create a local Kids profile, set restrictions and manage viewing controls on the device. A child’s viewing can still be processed by the connected media server and any features or integrations used; profiles that use the same server account may share server-side watch progress. Parents and guardians can contact us to ask about or request deletion of information submitted to our services. Please do not upload children’s personal information in support logs unless it is necessary and you are authorized to share it.

Purchases

If you make a purchase through Apple or Google, that provider handles payment and applies its own privacy policy. Luroka receives purchase or entitlement information needed to provide and restore the feature; we do not receive your full payment-card details from the store.

This website

The website does not use an account system, advertising scripts or analytics scripts. Its hosting, security and network providers may process technical information such as IP address, request time, requested path, browser information and security logs to serve and protect the site. Links to external sites are governed by those sites’ policies.

Why we use information and how long we keep it

We use information to operate the features you request, authenticate connections, synchronize playback, respond to support requests, diagnose faults, protect the service and meet legal obligations. Where applicable law requires a legal basis, this can include providing requested services, legitimate interests in security and support, consent where required, and compliance with legal obligations.

Local app data generally remains until you remove it, clear app storage, uninstall the app, or restore or replace a backup, subject to your operating system’s behavior. Data held by a server or third-party integration is controlled by that provider. Support correspondence, service logs and backups are kept for as long as reasonably needed for their purpose, security, legal obligations and backup rotation; retention can vary by system. Uploaded diagnostic logs have the expiry described above.

Your choices and rights

You can disconnect integrations, manage profiles and downloads, clear available app data, stop using optional features and uninstall the app. Uninstalling or disconnecting may not remove information already held by a connected service or in a backup; contact that provider for its data. Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction or objection to processing, and to complain to a data-protection authority. To make a request about information we control, contact privacy@luroka.app. We may need to verify the request and identify the relevant data before responding. See our data deletion request page for instructions.

Security, transfers and updates

We use reasonable technical and organizational measures, but no system or transmission is completely secure. Connected services, our hosting providers and other providers may process data in countries different from yours; their locations and safeguards depend on the service. We may update this policy as features or practices change and will update the date on this page.

Contact: privacy@luroka.app