Security
Security at Vigilance
Effective October 26, 2026. Version 2.
Vigilance runs on your computers, so you must be able to trust what it does there. This page says what we do, what we do not have yet, and how to tell us about a problem.
1. Our Rules
- Your code and files never leave your computer. Vigilance reads the package lists on each computer to count packages. It sends only the names and versions of public packages.
- Reports show counts. They do not name staff. They show each computer by a two-word name, so you can see which computers are quiet.
- If our service is down or slow, installs go ahead, and Vigilance counts them as unchecked. If the program on a computer stops, installs can fail for about 2 minutes, until a watchdog puts the old settings back.
- A swap moves to the last safe version of the same package. On Done With You and Done For You, Vigilance swaps on its own. A suggestion is different. When a package has no version older than 90 days, Vigilance can suggest an established package that does the same job. A suggestion takes effect only after a yes.
2. What Leaves the Computer
The full list of fields, with samples and how long we keep each one, is on its own page: What Leaves the Computer.
3. One Host, One Port
Vigilance on each computer talks to one Vigilance host: check.vigihq.com, TCP
port 443. It needs no proxy, no root certificate, no kernel driver and no admin rights. It
opens no port to the network. Your IT provider can test the path with
netcheck. Our ready email for IT providers is on the
Email for Your IT Provider page.
4. Signed Records
- Every verdict file (the list of findings), every control file (the settings we send each computer) and every plan answer is signed with Ed25519. Vigilance checks each signature before it uses the record. A record that fails the check is not used.
- The online signing keys stay inside AWS KMS. Our code asks KMS to sign. It never sees the private key.
- A root key signs the list of online keys. It stays in AWS KMS, in a separate AWS account that runs nothing else. The Vigilance program carries the root public keys.
- Each Vigilance program release is signed. The program checks the signature and the file hash of each update before it runs it.
-
Readouts are signed. Each readout carries the hash of the one before it, so
nobody can quietly change a past month. Anyone can check a readout with our public keys
at
check.vigihq.com/v1/keys.
5. When Our Service Fails
- If our host does not answer within about 1 second, Vigilance uses its last saved list, for up to 7 days after its last signed control file expired. With no saved list, or after those 7 days, the install goes ahead and Vigilance counts it as unchecked.
- If a signature check fails, Vigilance treats it as no answer.
- If the program on a computer stops, a small watchdog puts the old package settings back within about 2 minutes. Installs can fail until then. We email you the same day.
- We can pause every change, or make every Vigilance program stop checking and let installs run, within about 6 minutes, for every company at once. A daily test of our own library pauses changes on its own when it fails.
- We can roll the verdict library back to the edition before, within about 6 minutes.
6. Where We Run
- The Vigilance service for your computers, the website and the downloads run on Amazon Web Services. Every Vigilance data store is in AWS Canada (Central).
- Data moves over HTTPS with TLS 1.2 or later.
- Data at rest is encrypted by AWS: DynamoDB tables and S3 buckets.
- Access to our AWS account and our admin console needs a sign-in for each person. Every admin action on the Vigilance service writes an audit record, kept 2 years.
- Server logs hold no IP address and no device credential. A test fails our build if one appears in a log.
7. How Long We Keep Data
| Data | Kept |
|---|---|
| Company account details | While you are a customer, then 2 years |
| Device records (one for each joined computer) | While joined, then 90 days |
| Company secret for count codes. The codes let us count different packages without naming them | Deleted on the day you leave |
| Counts, readouts and reports | 2 years |
| Plan check counts | 90 days |
| Server logs | 14 days |
| IP addresses | Never written. 5 minutes in memory for rate limits |
| Verdicts about public package versions | While the library runs. Not tied to any company |
The Privacy Policy has the full list.
8. Who Processes Data for Us
| Company | What for | Where |
|---|---|---|
| Amazon Web Services | Hosting, the lookup service, storage, signing keys | Canada for data stores. CloudFront servers worldwide |
| Stripe | Payments, and the card you save at sign-up | United States and others, as Stripe says |
| Email (Google Workspace) and website analytics | United States and others, as Google says | |
| Freeform | Forms, and the readout and receipt emails. It is our own service | Runs on Amazon Web Services |
The Privacy Policy lists the tools that the website uses.
9. What We Do Not Have Yet
- Vigilance is not SOC 2 attested, as of 21 October 2026.
- We have no outside penetration test report yet.
- We have no bug bounty with payments. We thank every reporter by name if they want it.
10. Report a Problem
Email support@vigihq.com with "Security" in the subject. A person reads it. We reply within 2 business days. Please give us 90 days to fix a problem before you publish it. We will not take legal action against a good-faith report that follows this page.
To send a file that Vigilance flagged or missed, use Send a Sample.
Our security contact file is at
vigihq.com/.well-known/security.txt.
Modul4r Solutions, 18207 61 Ave NW, Edmonton, AB T6M 1T6, Canada. Patent pending.