Varisai for Venues — Privacy Policy
This policy covers the venue app — the one a business installs at its reception desk, on its counters and on its wall screen. The app a visitor installs on their own phone is a different app with a different policy: see Varisai for Visitors.
Effective date: 9 October 2026 Published by: Plenitude Systems Contact: hello@plenitude.in
The short version
Varisai runs a queue inside one building. It has no accounts, and it keeps working with the broadband unplugged, because that is how it is built rather than a feature it offers.
By default nothing leaves the venue's own devices. Two things can change that, and both are switched on deliberately by the venue: publishing the queue so people can watch it from a phone, and sending a text message to somebody who is nearly up. Each is described below, and neither is on unless the venue turns it on.
What never changes: a visitor's name never leaves the device it was typed into. Not to the wall screen, not to us, not into the report.
What the app stores, and where
Everything below is written to the device it was entered on, and shared over the venue's own WiFi with other devices that venue has paired.
| What | Why | Where it goes |
|---|---|---|
| Token numbers, times, and queue status | To run the queue and produce the daily report | The venue's own devices |
| A visitor's name and callback number, if staff enter one | So staff can call the right person, and ring back somebody who did not turn up | The reception device only — see below |
| Venue settings: business type, counters, policy | To configure the app | The venue's own devices |
| The names of staff on duty, if the venue fills them in | So a visitor can see which doctor or which counter is serving today | The venue's devices, and published if the venue switches publishing on |
| A licence, if the venue has one | To know what the venue is entitled to run | The device it was entered on |
Entering a name is optional. The queue works without one.
Who can see a name
A visitor's name is kept apart from their queue number in the way the app is built, not merely by policy:
- The wall screen never receives names at all. Not hidden — not sent. The same applies to any device the venue has set up as a counter display.
- The exported report contains no names. It carries counts only, and says so in its own footer.
- The list of people who did not turn up, which staff use to call back, stays on the venue's reception device and is never exported.
- A printed slip carries the visitor's own name when staff entered one, because the slip is handed to the person it is about. It is paper and it goes no further.
What leaves the device
Nothing, unless the venue switches on one of the two features below. A venue that switches on neither makes no connection to the internet at all.
There is no analytics, no crash reporting, no advertising, and no third-party software development kit that transmits anything, in either case.
If the venue publishes its queue
So that a visitor can watch the queue from their own phone instead of standing in front of the board, the venue's main device sends to Varisai's service, every few seconds:
- queue numbers being served and waiting, and how many are in line;
- the names of the groups — "General Medicine", "Counter 2";
- the names of the staff on duty, if the venue filled them in;
- a rough estimate of how long a service is taking.
No visitor name is in any of that, and there is no field that could carry one.
If the venue sends text messages
A venue whose licence includes text alerts, and which has switched them on, can have the app send a message to a visitor who is nearly up. To do that, the visitor's phone number is sent to Varisai's service, which passes it straight to the message provider and does not store it. The number stays on the venue's device, which is the only place it lives.
The message identifies a queue position and never a person: "M-42 is two away", not a name.
Permissions the app asks for
| Permission | What it is for |
|---|---|
| Internet / network state | Device-to-device sync over the venue's own WiFi, and the optional features above |
| Keep the screen on | So the wall display does not go dark mid-queue |
| Bluetooth connect | To print a paper slip on a thermal printer paired with the device. It is used for nothing else, and only if a printer is set up. |
The app does not request location, camera, contacts, storage, or microphone.
Children
Varisai is a tool for businesses to run a queue. It is not directed at children, and it does not knowingly collect anything from anyone — including children.
How long anything is kept
The venue decides. The day's records live on the venue's devices until the venue deletes them or uninstalls the app. Closing the day writes a backup file to the venue's own device; where that file then goes is the venue's choice.
If the venue publishes its queue, the published numbers are replaced each time the venue's device sends new ones, and a venue that is cut off or stops publishing has its published numbers cleared.
Uninstalling the app removes everything it stored on that device.
Who is responsible for what
Each venue is the controller of whatever it records about its own visitors. Plenitude Systems supplies the software and never receives a visitor's name, so it cannot produce, correct or delete one. A visitor who wants their name removed should ask the venue that entered it.
Where a venue has switched on text alerts, we relay a phone number on that venue's instruction and do not keep it.
Changes to this policy
Material changes will be published here with a new effective date, and noted in the app's release notes.
Contact
hello@plenitude.in