An eye-care habit your whole team keeps.

Two things: your settings, and the app. Your organisation key and configuration go into the machine registry - by Group Policy or Intune using the ADMX template we supply, so it sits alongside everything else you manage - and the app itself is a per-machine MSI installed silently. Nobody touches a machine and nobody types a licence key.

If you have neither Group Policy nor Intune, the dashboard writes you a setup script. Put it in a folder with the installer and run it on each machine: it applies your key and settings first, then installs, in that order because the app reads its settings when it starts. Or hand it to whatever your IT provider uses to push software; it is one command with administrator rights.

It is a plain text file and every line says what it does, so whoever you ask to run it can read it first. You can save more than one, if different groups need different settings.

Step by step, with the registry paths, the msiexec line and what to check when something has not worked: the deployment guide.

20-20-20 Vision LTD, a company registered in England and Wales (company no. 17357658), registered office 66 Paul Street, London EC2A 4NA.

There are two ways to pay, and you are contracting with us either way. By invoice, raised against your purchase order - annual only, since a monthly term is not something a finance team wants an invoice for twelve times a year. Or by card, for annual and monthly alike, taken through Paddle as merchant of record; card purchases appear on your statement from them rather than from us.

We're happy to complete supplier onboarding forms, security questionnaires and W-8BEN-E paperwork for buyers outside the UK. Full supplier details are at the bottom of this page.

Individual rest statistics never leave the machine, in any version. There is no per-person reporting to buy, switch on or ask for.

On Free and Pro that is the whole answer: no accounts, no telemetry, and the app works fully offline once activated.

20-20-20 Vision for Workplaces adds two things. First, a licence check-in, so the dashboard knows which licences are in use.

Second, and only if you switch it on, team-level adherence figures. Each machine sends how many break reminders it showed in a week, how many were taken and how many were skipped - three numbers and the week they belong to.

Nothing else goes with them: no licence identifier, account, machine name, installation identifier, timezone or locale, and we do not log the network address they arrive from.

They are added into a weekly total as they land, so no record of an individual submission exists to be pulled apart afterwards - by us or by anyone else. Nothing is shown at all until at least five people hold licences, so a figure cannot be attributed to one person by elimination.

(This website uses Google Analytics; the app does not.)

A locked-down estate is what the 20-20-20 Vision for Workplaces build is designed for. Smart-pause detection runs as a self-contained helper that needs no runtime scripting - nothing in it depends on PowerShell.

That matters most under Constrained Language Mode, which is where script-based tools quietly stop working. It runs under AppLocker, WDAC and ThreatLocker as well.

We have a one-page technical summary for security teams that includes details on publisher and application id, both executables and what each one is for, the single outbound host it contacts and what is sent, which registry key it reads, and what breaks if any of it is blocked. It is written to be forwarded to whoever manages your endpoints.

Two things from it worth saying here. The Workplaces build makes outbound connections to exactly one host, and nothing else - no telemetry endpoint, no analytics, no crash reporter. And if you use Ringfencing or anything like it, permit that host: an application allowed to run but not to reach its licence authority appears to work and then quietly stops reminding anybody a fortnight later, which looks like a fault in our software rather than a policy decision.

If your fleet enforces any of this, tell us how it is managed and we will make sure you get a build that fits it.

No. Nothing records how anybody works.

Rest statistics are private to each machine and visible only to the person using it. They never reach us, so there is nothing to pass on to an employer even if one asked.

The optional adherence reporting is anonymous by construction rather than by policy. Submissions carry nothing that identifies a person or a machine, and they are added into a weekly total on arrival rather than stored one by one.

That distinction is the whole answer. A policy can be changed; a missing set of records cannot be recovered. There is nothing to separate back out, which means we could not produce a per-person breakdown if you asked us for one.

It is what makes the figures something you can put in front of a works council or a safety representative.

Workstation checks, if you use them, are different on purpose: they are named records of whether each person's workstation was assessed, what was fixed and what training they completed, because the law requires you to keep them. They are compliance records rather than monitoring, and they are never joined to break data.

No. Nobody signs up, sets a password or is asked to enrol in anything. People are matched by the Windows account they are already signed in to.

Your dashboard lists the people you have put on it, because that is what lets you take a licence back when somebody leaves. For licensing, it is an identifier, whether they hold a licence, and the machine they are currently on. If you use workstation checks, it also holds each person's checks, actions, training and eye-test dates, seen only by the assessors you name. Only your own administrators see it, you can take somebody off it yourself, and it is deleted within 90 days of your licence ending - or within 7 days if you close the account, because that is a request to erase and we treat it as one.

If you would rather we did not hold readable account names at all, a setting replaces them with an unreadable digest - at the cost of making licences harder for your own team to manage.

Nobody types a key. You deploy one organisation key to every machine, by Group Policy, Intune, or a small configuration file we generate for you.

You decide who gets a licence. Installing the software does not hand one out. In the dashboard you list your people - paste them in, or point us at one security group and a small script keeps the list in step with it - and you assign a licence to each person who needs one. Both can be done before anything is installed anywhere, which is the sensible order: you license people, then deploy to the people you licensed.

A licence belongs to a person, not to a machine, so somebody with a laptop and a desk PC uses one licence, a shared workstation gives each person their own, and a rebuilt virtual desktop does not consume a new one.

When somebody leaves, unassign their licence and give it to whoever you choose. We never unassign anybody on your behalf - not when somebody drops out of your security group, not when a machine is uninstalled, and not when a machine goes quiet. Those are flagged for you to act on, never acted on for you.

The one thing that is not a choice is the number. The app runs for as many people as you hold licences for. If a term ends or you renew for fewer, the licences you assigned first stay in force and the rest stop being reminded. Nobody is unassigned, the dashboard shows exactly who is affected, and you change which by unassigning somebody and assigning the person you would rather have.

The list is the people you put on it, and nobody else. A machine reporting an account you have not listed is told it holds no licence, and nothing about it is recorded, counted or shown to you - running the software licenses nobody and adds nobody. You can also restrict which email domains the key will license, so a copy that leaves your estate can never take a licence you have paid for.

You buy them and they join the term you already hold, charged pro rata for the months remaining. Ten licences in January and four in April is one renewal date, not two. Extra monthly licences go onto the subscription you already have rather than starting a second one.

Annual licences are paid by card or against an invoice; monthly licences are card only. One exception is worth stating before it surprises anyone: if your annual term is on an invoice, further annual licences have to be invoiced too. A card purchase starts its own twelve months, which would hand you a second renewal date to manage, so we would rather raise the invoice.

Going the other way, licences nobody is using can be given up. On an invoice they stop being assignable straight away; on a card subscription they stay available until your next billing date, because that is when the quantity actually changes. Either way the rest of the term you have paid for is not refunded, and a licence somebody holds can never be taken this way - so nobody loses their reminders because of a billing change.

Yes, with one consequence worth knowing before you buy.

The app reports the first identifier it can resolve: the work account name, else the domain account, else the machine account. On a standalone machine that last one is what it uses, so everybody is still recognised, licensed and reminded.

What you lose is the part that makes a licence belong to a person. With Active Directory or Entra ID, somebody with a laptop and a desk PC is one person on both, and a rebuilt machine does not consume a second licence. Without a directory there is nothing stable to match them on, so the same person on two machines is two entries on two licences, and per-person licensing becomes per-device in practice. The dashboard marks those people so you can see exactly where it is happening rather than discovering it on the invoice.

If that suits you, it is a supported way to run it. If it does not, and the machines are genuinely standalone, Individual Pro licences need no directory, no dashboard and no key.

If you are somewhere in between - a domain with unpopulated account attributes, say - tell us how your machines sign in and we will tell you honestly whether it will match cleanly.

Yes, and you decide which parts your people can change.

Set the interval, rest length, working hours, snooze allowance and the rest centrally, by Group Policy or Intune using the ADMX template we supply. If you have neither, the dashboard generates a small configuration file to run on each machine instead.

Then choose setting by setting what is fixed and what is theirs. You might pin the break interval your DSE assessment recommends and still let people turn the notification sound off.

Anything you fix appears in the app greyed out and marked “Set by your organisation”, rather than silently refusing to work. Somebody who wonders why they cannot change it can see that it was a decision, and whose.

Theme and language always stay adjustable, because freezing somebody's dark mode achieves nothing.

No. The 20·20·20 rule is a widely recommended habit for easing digital eye strain, and 20-20-20 Vision is a wellbeing aid that helps people keep it. It complements - and doesn't replace - professional eye care or your statutory DSE eye-test obligations.