Data location and privacy

Accounts, cloud credentials and targets live on your NAS/Docker host. Leelaa STRM does not download or cache media bodies; the player reads from the 115 CDN. Software licensing uses the Leelaa platform, so storing media in the cloud does not make this an offline application.

Where data lives

Data	Location and purpose
Accounts, sessions, 115 Cookie, service address, targets, run records and playback grants	Complete application state; fnOS allocates it, Docker maps the deployment's data/
STRM and NFO	Output root under 设置 → 生成文件位置; typically deployment media/ in Docker; downstream receives read access only
Staging, backups and recovery markers	.sync-, .backup- and related items inside output; abnormal leftovers need preservation and review
Original 115 video/audio	Remains in the cloud, not inside STRM or application backups
.lltf / .llab	Separately saved license-recovery materials, not whole-library backups

Initial administrator passwords stop working after the first change. There is no web recovery of an old password. Do not expose application state as a media library.

Credentials and access

• The 115 Cookie is used for listing and direct-link exchange and is not returned after saving or written to logs. Passwords use irreversible hashes; original login tokens are not stored server-side.
• Playback grants store key digests in the database, with raw keys temporarily shown after creation. Generated STRM also contains that playback credential. Reading it grants the target's playback capability.
• A NAS system maintainer can technically access application data; database encryption cannot isolate a person controlling the host. Application administrators manage configuration/users; ordinary members only manage their own account and view the shared license.
• Licensing, purchases and recovery send required account/order, project and installation-binding information to Leelaa. They do not send 115 Cookies or media bodies to that platform. 115 requests use its endpoints; players read upstream media. This application has no usage analytics or advertising reports.
• Downstream applications have their own users and software licenses. Check their separate documentation for media probing/processing/playback behavior.

Backup and recovery

There is no user-facing whole-library export or one-click restore. A deployment maintainer should preserve complete state:

1. Wait for sync, deletion and payment checks, then stop the application through App Center or the original Docker deployment. Ensure no other instance writes to the same data.
2. Preserve all application data, original private deployment configuration and existing external keys/binding materials. Also keep complete output, including file manifests and valid STRM. Do not pick one database file or only visible STRM files.
3. In Docker, retain original data/, media/, Compose/private environment configuration and host identity mappings. On fnOS retain actual application data/private configuration. Backups contain Cookies and playback capability: restrict access and consider separate storage media.
4. Protect cloud originals separately. Missing STRM can be regenerated if the source, target configuration and license remain available; a lost original cannot be restored from STRM.

Preserve current state before recovery. Have the maintainer stop writers and check backup versions, permissions and completeness. Old and new data cannot be automatically merged. An old backup can roll back newer orders, users, credentials and playback-grant state; do not overwrite a current instance blindly.

Afterwards check original accounts/roles, targets/records, service address, real 115 browsing, generated files, the dedicated channel and downstream playback. Another device needs official license recovery. IP/port changes require playback-address updates. Restored files do not establish restored licensing/playback.

Uninstalling and erasure

The current fnOS uninstall preserves data and does not remove 115 originals. Before later erasure, keep complete backups and have the NAS maintainer check exact folders, downstream references and license-recovery materials. Do not delete shared folders still scanned elsewhere. Removing local state neither deletes cloud originals nor resets a signed trial.