Virata runs on your computer and works on your data there. Your data never leaves your machine. Checking that a licence key is genuine, and has not expired, happens entirely on your computer and makes no network request. What does reach our server, once per key: a request to confirm no other computer is already using it (see "When you first use a licence key" below) — never your data, and never anything read from your hardware. The other things we hold are what you give us when you ask for a key, and a count of how often the program starts.
| What | Why | Where in the code |
|---|---|---|
| Your email address | To send you the key, and tell you when it runs out | server/signup.php |
| What you said you wanted it for, if you said | To understand who uses Virata | server/signup.php |
| The kind of key and its dates | To issue and renew it | server/lib.php |
| A scrambled form of your internet address | To stop the form being abused | server/lib.php, ip_hash() |
The scrambled address is a salted one-way hash. It cannot be turned back into your address, and changing the salt makes old ones unlinkable to new ones. We do not store your actual internet address.
Every copy needs a key, and since 24 September 2026 a key works on only one computer: the first one that uses it. The first time you paste a key in, Virata asks our server whether a different computer has already claimed it.
| What | Why | Where in the code |
|---|---|---|
| The key's public identifier | To look up whether it is already claimed | virata/activation.py, server/activate.php |
| A random identifier this copy of Virata made up | To tell your computer apart from another one | virata/activation.py, function device_id() |
That random identifier reads nothing about your computer — not a MAC address, a disk serial, or anything else the operating system could report. It is a number nobody chose, made once and kept in one file, and it means nothing to anyone outside this program.
We keep the identifier, the key it was used with, and when — enough to tell two computers apart, not enough to say who they belong to unless that key is also looked up in the table above. This request happens once per key. After that, every start-up checks the key on your own computer, with no network request, exactly as before — including after the key's dates have passed: renewing means pasting in a new key, which activates once in the same way.
If this request cannot be completed — no internet, or the key is already in use elsewhere — Virata says so and does not start. This is the one condition on "your data never leaves your machine": the key has to reach us, once. Your data still never does.
Each time it starts, Virata asks our server for a short file of notices — things like "a new version is out". That request sends nothing about you or your data. It does reveal, as any request on the internet does, your internet address and a label saying it is Virata.
From that we keep the date, the same scrambled form of the address, and the label. We use it only to count roughly how many machines are running Virata.
virata/licence.py; a test fails if this ever touches the network (tests/test_licence.py, test_the_check_makes_no_network_request). Only activating a key, described above, reaches us, and only once per key.You can ask to see what we hold about you, have it corrected, or have it deleted, by writing to feedback@vira.guru.
Nobody, by intent.
On our server at vira.guru.
---
The facts above describe the code as of commit on 22 September 2026. If the code changes what it collects, this must change with it, before the change ships.
These are open, and we would rather say so than write a confident sentence over a gap. This page will be updated as each is decided.