Everything stays on your machine.

What it stores

One SQLite file in your user profile, holding what you copied.

• Items. The text of each unique thing you copied, its type, and when it was first and last seen.
• Events. One row per copy, with the time and, on Windows, which application owned the clipboard.
• Sessions and Revelations. Groupings RVLTION detected, and the ones you chose to keep, with the sentences explaining why.
• Settings. Your secret handling choice and whether capture is on.

There is no user profile, no identifier, and no account. The file belongs to your operating system user and nothing else reads it.

What it refuses to store

The privacy gate runs before anything reaches the disk, so a rejected fragment is never written rather than written and hidden.

1. Clipboard privacy flags. On Windows, password managers mark their copies as not for history, and RVLTION honours that.
2. Protected applications. Twenty one password managers and credential tools, matched against whatever identifier the platform provides.
3. Content shapes. Twelve published token formats including PEM private keys and provider API keys, then a general entropy check.

The default for a suspected secret is to discard it. Only a counter moves, which is the number shown as blocked in the status bar.

The third layer is best effort and will miss things. The first two carry the real guarantee.

Network behaviour

RVLTION makes no outbound connections. Not for updates, not for licensing, not for anything.

• No HTTP client, socket, or TLS library in the dependency tree.
• No fetch, XHR, WebSocket, or beacon call in the interface source.
• A content security policy of default-src 'self', which stops an outbound request at the webview even if one were introduced by accident.
• No Tauri plugins, which means no updater.

The application works with the network cable unplugged, permanently.

Telemetry

None. No analytics, no crash reporting, no usage counts, no install ping, no feature flags fetched from anywhere.

This website carries none either. It loads no fonts, scripts, or images from another origin, so visiting it tells nobody anything beyond your request reaching whatever server hosts it.

Deleting your data

Clearing history from within Settings removes every fragment, event, and detected session, and empties the search index with them, because the index is derived from the same rows rather than being a second copy.

Uninstalling RVLTION does not delete your history. The database sits outside the installation directory deliberately, so an upgrade cannot discard it. If you want the data gone, clear it from Settings first, or delete the file yourself. Its location is on the data and storage page.

What this is not

Your history is not encrypted. It is an ordinary SQLite file with ordinary file permissions. Anyone who can read your user profile can read it, exactly as with any other local application data. RVLTION keeps secrets out of that file. It does not protect the file itself, and does not claim to.

If you need encryption at rest, use full disk encryption, which your operating system already provides.

This is also not a privacy policy and makes no regulatory compliance claim. Because no data reaches RVLTION, there is no controller, no processor, no retention schedule and no subject access process to describe. Where a jurisdiction requires a formal policy before commercial release, that is a drafting job for legal counsel, and one that has not been done.