Operating policy
Privacy by construction
For every built-in utility, input and output stay in browser memory. The site has no account system, analytics, advertising scripts, remote uploads, or server-side tool processing.
- Input / output
- Held in the current browser tab only while you work.
- Network transfer
- None for built-in tool operations.
- Persistence
- Theme override plus favorite and recent tool IDs. Never content.
What is not collected
Tool input and generated output are not sent to Recica servers or third parties, added to page URLs, stored in local storage or IndexedDB, written to application logs, or included in error telemetry. Only your theme override and the identifiers of favorite and recently opened tools are stored, so the interface can remember your preferences. No text you paste or generate is ever persisted.
Sending output to another tool
The “Send to” menu passes output to the next tool in memory during the page transition. Nothing is written to the address bar, storage, or the offline cache, and the payload is discarded as soon as the destination reads it.
Files and clipboard
Loading a file reads it inside your browser with the File API. It is never uploaded. The Paste button reads the clipboard only when you click it, and Copy writes to it only when you click it. Downloads are generated locally from the current output.
Smart paste on the homepage
Detection runs entirely in this tab against a fixed set of patterns. The pasted text is handed to the tool you choose and is not retained anywhere afterward.
External links
Links to other Recica publications and curated external resources leave this site and are governed by the destination’s policies. Recica Tools does not load those destinations in the background.
Responsiveness limits
Each utility publishes its processing limit. Limits are checked before expensive work, including before a dropped file is read, and never cause silent truncation. They do not change the local-processing guarantee.