# Tuck privacy record

Version 0.1.0-rc.2 · 9 September 2026

Tuck runs locally. It has no account system, analytics, advertising, update service, remote classification, or file uploads. The native backend examines filenames and filesystem metadata; it does not open file contents for classification. Fonts and interface assets are bundled.

Tuck stores preferences, named rule presets, exclusions, recent locations, and recovery journals under `%LOCALAPPDATA%\app.riverandrail.tuck` by default. A test-only environment override, `TUCK_DATA_DIR`, may choose another directory. The portable application also uses this local application-data location; it is not a zero-trace or fully self-contained portable profile.

Recovery journals contain full original and destination file paths, names, sizes, volume/file identities, modification timestamps, categories, matched-rule explanations, the preset snapshot, session time, created-directory identities, and operation outcomes. This information may reveal personal or confidential filenames. It is not encrypted separately from Windows account and disk protection. Other software with access to your Windows account can read it.

History is retained until you choose to forget individual sessions. Forgetting a session removes its journal and permanently removes Tuck's undo ability for that session. Recent locations can be cleared separately in preferences. Settings and journals are retained on uninstall by default. Selecting the application-data removal checkbox in the uninstaller also erases these recovery records. To remove all local records after you no longer need recovery, close Tuck and remove its application-data directory.

The application does not automatically download cloud placeholders. It rejects unavailable/offline/recall/reparse items and unsupported linked locations. Windows or security software can perform its own network activity independently. If WebView2 is missing, the installer may download Microsoft's runtime; an already installed runtime may update according to Microsoft's policies. Development dependency installation and license collection also use network access; those steps are not application runtime features.