The things worth asking first.

What it is

What is RVLTION?

A proprietary desktop application that keeps a local, searchable history of what you copy, and reveals the structure inside it. It runs on your machine, stores everything on your machine, and makes no network call.

What does RVLTION do?

It records what you copy, works out what each fragment is, and notices when a run of copies turns out to be about one thing. When it does, it offers you that grouping with the reasons it drew the line where it did.

What does it record?

The text of each unique thing you copied, its type, when it was first and last seen, one row per copy, and on Windows which application owned the clipboard. Plus the groupings it detected and the settings you chose.

What does it not record?

Anything a password manager marks as not for history. Anything copied from one of the twenty one protected credential applications. Anything matching a published token or private key format, or failing a general entropy check. Under the default setting, a suspected secret is discarded before it reaches the disk and only a counter moves.

Is it always running?

Capture runs while the application does, and you can pause it from Settings. The setting survives a restart, so a paused RVLTION stays paused.

Privacy

Does RVLTION send clipboard data to a server?

No. There is no HTTP client, socket library or TLS stack in the build, so there is no code that could send anything anywhere. The application works with the network permanently unplugged.

Is an internet connection required?

No, at no point. Not to install, not to run, not to use any feature. There is nothing for a connection to do.

Does RVLTION use AI or cloud processing?

No. No model, no embedding, no external inference, no third-party API. The engine that decides what belongs together is deterministic and runs locally. That is an architectural position, not a stage before a model.

Is there an account?

No. No sign-in, no identifier, no profile, no sync.

Is there telemetry or crash reporting?

None of either. That is also why a crash cannot report itself: see when something breaks.

Where is my data stored?

One SQLite file in your own user profile, under your operating system account. Nowhere else, and on no other machine. The exact path is shown in Settings with a button to copy it, and on the data and storage page.

Is it encrypted?

No. It is an ordinary file with ordinary permissions. Anyone who can read your user account can read it. RVLTION keeps secrets out of that file; it does not protect the file itself, and does not claim to. If you want encryption at rest, use the full disk encryption your operating system already provides.

Can my data be deleted?

Yes, entirely and at any time. Forget removes a single fragment. Clear history in Settings removes every fragment, event and detected session, and empties the search index with them, because the index is derived from those rows rather than being a second copy of them. Deleting the file removes everything at once.

Does uninstalling delete my history?

No, deliberately. The database sits outside the installation directory so that upgrading cannot discard it. If you want the data gone, clear it from Settings first, or delete the file yourself.

Reveal

What do the reasons mean?

They are the actual evidence the grouping was made from, not a summary written afterwards. Shared names, shared domains, the mix of kinds, and the span of time. If the reasons look thin, the grouping is thin, and you can decline it.

How does grouping work?

Deterministically. Fragments are compared on identity first, then subject, then structure, then where they came from, then when. There is no model, no embedding and no similarity score; the same history produces the same answer every time.

What are its limits?

It works on words that actually appear. Two fragments about the same thing in different vocabulary will not be connected, because nothing in the design knows they are related. It also holds back rather than guessing: a fragment two groups want equally is reported as held rather than assigned.

Technical

Which platforms work?

Only Windows is a platform you can actually use today.

What does it need to run?

Windows 10 or later on x64. It is a single self-contained executable; the interface is embedded at build time, so nothing needs Node, Cargo or a development server to launch it.

How do I back it up?

Copy the database file somewhere else while RVLTION is closed. It is one file and it is yours. There is no built-in backup schedule and no cloud copy, because there is no cloud.

Is there an automatic updater?

No. Nothing checks for updates, which also means there is no update channel that could be compromised. New versions are installed by downloading them.

When something breaks

RVLTION will not start. What happened?

The likeliest cause is that the history file cannot be opened, and RVLTION now says so in a dialog rather than closing silently. The message names the file and offers three things to try.

What happens to my data if the file is damaged?

Nothing, on RVLTION's part. It will not replace or delete a database it could not open, because a file that fails to open may still be recoverable and replacing it would destroy that chance. Recovery is deliberately a manual decision.

How do I recover?

1. Close RVLTION and start it again. If another copy was still running, the file may simply have been in use.
2. Restore the file from a backup if you keep one.
3. Move or rename the file, then start RVLTION again. It will begin a fresh, empty history and leave the old file alone so you can try to recover it later.

How do I see what went wrong?

Start RVLTION with the environment variable RVLTION_LOG=rvltion_lib=debug. The log records what the application did, never what you copied.

Licensing

Who owns RVLTION?

RVLTION is proprietary software owned and controlled by the RVLTION brand. The RVLTION brand owns the source code, the user interface and product design, the documentation, this website's content, and the RVLTION name and branding.

Is RVLTION open source?

No. RVLTION is not distributed under MIT, Apache-2.0, GPL, BSD, MPL or any other public licence, and no source repository is published. The components it is built on are open source and keep their own licences; RVLTION's own code does not.

What licence applies to RVLTION itself?

A proprietary notice: copyright RVLTION, all rights reserved. Reproduction, modification and distribution each require prior written authorisation. See the legal page.

What licences apply to the code it is built on?

Permissive licences throughout, mostly MIT and Apache-2.0, with five MPL-2.0 components used unmodified, plus Unicode-3.0 and BSD-3-Clause components. Those are third-party and are not owned by RVLTION. The full breakdown is on the licences page.

Support

Where do I report a problem?

There is no public contact channel, because there is no public release. Support arrangements are handled as part of the acquisition and transfer process. The support page covers what you can diagnose and fix yourself, which is most of it.

What should I include?

What you did and what happened, the version from the status bar, your operating system, and the log if you can produce one. Please do not send clipboard content or your database file: RVLTION works hard to keep that out of its own logs, and a bug report should not put it back in.