TLU Apps Privacy Policy

1. Scope and app use

This policy applies to the following TLU apps intended for Google Play:

• TLU WEB KIOSK (트러유 웹, kr.rebooter.kioskbrowser), 1.4.3 (13)
• TLU PLAYER KIOSK (트러유 플레이어, kr.rebooter.nasplayer), 1.4.2 (11), one package for tablets and TVs

No REBOOTER app account, login or provider activation key is required. An administrator configures a web address or media source during initial setup. The web app requires an admin PIN. The player requires a PIN when kiosk lock is enabled; with lock disabled, it can be skipped after a notice. A selected website or media server may separately require an account or login.

2. Information stored on the device

• Web: start addresses, display, security, language and remote configuration settings, and the admin PIN hash are stored in app storage. The PIN itself is not stored. Separately configured HTTP authentication details are encrypted using Android Keystore. WebView may keep website cookies, site storage and cache on the device.
• Player: WebDAV addresses and user names, local/USB folder locations, HTTPS playlist and HLS addresses, playback, schedule, language and remote configuration settings, and the settings PIN hash are stored locally. Server passwords are encrypted using Android Keystore. On Android 5.x, an AES key protected by a Keystore RSA key is used.
• The player may cache media lists and files according to its settings. Local and USB sources read folders and files selected by the user.

3. Information sent to selected websites and servers

• Websites: the web app opens configured pages, followed links and redirects, and may request embedded images, scripts and external resources. The host allow-list is empty by default, so HTTPS navigation is not restricted to a particular site. A navigation host restriction does not restrict every external resource request made by a page.
• Logins, input and cookies: website logins, form input, cookies and required HTTP authentication details may be sent to the website or resource server involved in a request. JavaScript and cookies are used; the third-party cookie option is enabled by default. File uploads and downloads are disabled by default. If the administrator enables them, selected files or download requests can be processed. Connection tests also make server requests and can follow redirects.
• Media playback: the player requests lists and files from the selected WebDAV server and plays media addresses from a user-supplied HTTPS playlist or an HLS stream. Public internet and local-network sources are supported. Requests may contain required authentication details. Resources linked through media addresses, playlists, streams or redirects can be on other hosts.
• Remote configuration: if an administrator specifies a configuration address, either app requests configuration documents from that server. The default address is empty, so this feature is disabled. Request headers may be used to check for changes; web configuration requests can include the app version.
• Web status access: if the administrator enables the status feature and sets an explicit host allow-list, an allowed page can read the app version, network connection status and current time. Whether the page sends those values elsewhere depends on the website's features.

Receiving websites and servers may obtain connection information such as the IP address, requested address, headers and time. Selecting a REBOOTER website also sends the corresponding requests to REBOOTER. Processing and retention by external websites, content providers and configuration servers are governed by their respective operators' privacy policies.

4. Connections and encryption

HTTPS encrypts data in transit. Allowed HTTP connections or HTTP WebDAV do not. Enabling the player's self-signed certificate option relaxes normal certificate checks for the specified host. Encryption of server passwords stored on the device is separate from encryption of the connection used to send requests.

5. Permissions and purposes

The apps do not request location, camera, microphone, contacts or broad storage access permissions. Android's file picker provides access to local/USB folders and settings files within the scope authorized by the user. The Google Play versions do not use device admin, accessibility or overlay features, or install their own APK updates.

6. Settings export, retention and deletion

Automatic app backup is configured as disabled. Exporting a settings file or QR code can disclose included addresses, user names and operating settings to its recipient. Web exports exclude the admin PIN and the separate HTTP authentication store. Player exports include the PIN hash only when selected. A server password is included only if an export passphrase is set, encrypted with AES-256-GCM; without a passphrase it is omitted.

Settings and internal app data remain on the device during use. Clearing relevant settings, clearing app data through Android, or uninstalling can delete the corresponding app data and cache on the device. Exported files, QR codes, downloads in shared locations and external server records may remain separately. Deleting app data does not delete external website accounts or server records. Retention and deletion on external servers follow the respective operator's policy.

7. Support and policy changes

For app or privacy support: rebooter.inc@gmail.com

An email inquiry sends the sender's email address and message to REBOOTER. Settings stored in the app are not automatically attached to a support email.

If the app's information handling changes, this page and its effective date will be updated.