Where things actually stand.

Ownership

RVLTION is proprietary software. The RVLTION brand owns and controls the intellectual property comprising the RVLTION product and its associated materials: the source code, the user interface and product design, the documentation, this website's content, and the RVLTION name and branding.

Third-party components are not owned by RVLTION and are covered by their own licences. They are listed on the licences page.

All source code written for RVLTION is owned by RVLTION. That covers every file in the repository authored for this product, in every language, together with the interface, the documentation and this website.

RVLTION is identified here as the IP and brand owner. No personal identity or operational contact detail is published, and that is deliberate rather than an omission.

Governing law

RVLTION is an Israeli work and its copyright is governed by Israeli law.

Under Israeli copyright law, copyright arises automatically on creation and requires no registration or filing. The notice on this site and in the repository records that position; it does not create it, and nothing is lost by the absence of a registration certificate.

Jurisdiction-specific commercial drafting, meaning venue, liability limits, consumer warranty terms and the wording of an end user licence, still requires legal counsel before public commercial release. Naming the governing law settles which law applies. It does not substitute for terms written under it.

Licensing position

RVLTION is not distributed under a public licence. The repository carries a proprietary notice, copyright 2026 RVLTION, all rights reserved. No permission to use, copy, modify, distribute, sublicense or sell the software is granted by it.

Reproduction, modification and distribution each require prior written authorisation from RVLTION. No open source licence is granted to RVLTION's own code. Third-party components keep their own licences and are unaffected by this.

Terms of use

The terms below apply to RVLTION as it stands. There is no public release, so no one has yet obtained a copy to which they could apply.

• RVLTION is proprietary software. Use is subject to authorisation by RVLTION as the IP and brand owner.
• No ownership passes to a user. Nothing on this site, and no act of downloading, installing or running the software, grants ownership of RVLTION, of its source code, or of its branding.
• The software is provided as documented, with no warranty of any kind, express or implied, and with no support commitment or service level offered or implied by anything on this site.
• Third-party components remain subject to their own licences, which are unaffected by these terms and are listed on the licences page.
• The privacy statements on this site describe the product's current architecture, verified against the source. They are a description of behaviour, not a regulatory compliance claim.
• The RVLTION name and branding may not be used without prior written authorisation.

Jurisdiction-specific provisions, including governing law, venue, liability limits and consumer warranty terms, require legal counsel before public commercial release. They are absent here rather than guessed at, because inventing a jurisdiction would be worse than naming none.

Your data

RVLTION stores what you copy in one file on your own machine. It transmits nothing, collects nothing centrally, and has no account system.

Because no data ever reaches the project, there is no controller, no processor, no retention schedule and no subject access process to describe. The data is yours, in your file system, under your operating system account. Deleting it is a matter of clearing history from Settings or deleting the file.

This is a statement about how the software behaves. It is not a privacy policy, and it does not attempt to be one. The technical detail is on the privacy page.

Third-party components

RVLTION is built on open source components under permissive licences, predominantly MIT and Apache-2.0, together with five MPL-2.0 components used unmodified. Their attribution is on the licences page.

The MPL-2.0 obligation is file level: it attaches to those files, not to the program that links them, and is discharged by attribution and a pointer to upstream source as long as the files are unmodified. They are unmodified; the project vendors nothing and patches nothing.

Whether the current attribution wording is sufficient for distribution in a given jurisdiction is a question for a lawyer and has not been answered.

Open questions

Stated here rather than quietly omitted, because an acquirer will ask and a user deserves to know what is settled. Each of these is a legal-review item. None of them is an unresolved ownership question: RVLTION is the IP and brand owner.

• Contributor rights. No contributor agreements exist, and the repository's history begins with a single baseline commit rather than an authored record. Not established by repository evidence; requires owner confirmation.
• Trademark. No registration, application or clearance search is on record for the name.
• Commercial terms drafted under Israeli law. The governing law is settled, as above. Venue, liability limits and consumer warranty wording are not drafted, and need counsel before public commercial release.
• Icon provenance. The application icon set carries no attribution or origin note. Asset provenance requires confirmation before commercial redistribution.

None of these blocks use of the software as it stands. All of them would need answering before it is sold or distributed at scale.