Re:T-UI is local-first. The launcher should not need a server to be useful.

Configuration, presets, aliases, command history, modules, notification filters, and local files live on the device unless the user chooses to export or share them.

What may stay on device

• Launcher settings: theme, UI, aliases, app visibility, presets, modules, and command preferences.
• Android permissions: notifications, contacts, calendar, files, or music only when the feature needs them.
• Backups: user-initiated exports can contain private launcher configuration. Share them carefully.
• Termux: shell scripts and commands run through Termux-owned surfaces, not a hosted Re:T-UI backend.

Companion surfaces

Re:TUI-FM owns broad file-management work. Re-TUI-Keys is local-first and does not need a hosted model. The website ASCII tool processes images in the browser.

Links