Privacy Policy
Effective 2026-07-27
Draft — not yet reviewed by a lawyer.
This is a starting draft written to describe how VISION actually works. It has not been reviewed by a qualified legal professional and must be before the service is offered to a paying customer. Indian law, including the Digital Personal Data Protection Act 2023, places specific obligations on whoever holds this kind of data.
The registered legal entity has not been configured, so this document names the product rather than a company. Set NEXT_PUBLIC_LEGAL_ENTITY before publishing.
VISION records where and when you work, and takes your photograph when you do. This page says exactly what is collected, who can read it, and how long it is kept.
1. Who is responsible for your data
VISION operates VISION and stores the records it creates. Under the Digital Personal Data Protection Act 2023 we act as the Data Fiduciary for that data, and your employer — the Owner of the company account — determines who is enrolled and what rules apply.
If you are an employee and want your data corrected or erased, you may contact either your employer or us directly using the address at the end of this page.
2. What we collect
Account details: your name, email address, phone number if you provide one, your home address as entered at signup, your department and joining date, and a hashed password. We never store your password itself.
Attendance records: the time of each punch, the GPS latitude, longitude and accuracy reported by your device at that moment, the distance from your employer’s configured office location, and a photograph captured at the punch.
Compensation records: monthly salary, provident fund percentage, allowances and any custom fields your employer configures, together with the dates from which each applies.
Technical records: IP address, browser user agent, and a device fingerprint used to flag when a punch comes from an unfamiliar device. Request logs carry a request identifier and a company identifier, never a password, token or decrypted field.
Aadhaar number, if your employer asks for it and you supply it. It is optional. It is encrypted at rest, only its last four digits are ever displayed, and it is never included in any list or export of multiple people. We recommend employers do not collect it at all: it serves no attendance purpose.
3. Why we collect it
Location and photographs exist to establish that a punch was made by the right person at the right place. They are used for that, for the audit trail your employer can inspect, and for nothing else. We do not build location profiles, and we do not record your location except at the instant you press check in or check out.
We do not track your location between punches, and the Service has no background location capability.
4. Who can see it
Your employer — the Owner of your company account — can see your attendance, your punch photographs, your location readings and your compensation. That is the purpose of the product.
Other employees cannot see your records. Access is enforced in the database itself rather than only in the interface, so an employee reading any part of the system receives only their own rows.
We can technically read your records. Every customer’s data is held in one database, separated by database-level access controls rather than by physical separation. Our support console connects with a read-only account that has no permission to read attendance, punches or compensation, and we restrict ourselves further by policy — but we are not architecturally prevented from access, and we would rather say so than imply otherwise.
5. How long we keep it
Punch photographs are deleted after 90 days by an automatic job, and the reference to them removed. The attendance record itself — time, status, location — is retained for as long as your employer's account is active, because payroll and statutory records depend on it.
One-time codes are deleted shortly after use or expiry. Audit log entries are permanent by design: they are what makes the record of changes trustworthy, and the application is not permitted to delete or alter them.
When a company account is closed, its data is exported on request and then deleted.
6. How it is protected
Passwords are hashed with argon2id. Aadhaar numbers, where collected, are encrypted with AES-256-GCM using a key held outside the database. Photographs are stored in a private bucket and served only through short-lived signed links that expire in five minutes.
All traffic is encrypted in transit. Backups are encrypted, and their passphrase is stored separately from the credentials for the backup storage.
Separation between companies is enforced by row-level security in the database, verified by an automated test and by a check that refuses to start the server if that separation is not in force.
7. Your rights
You may ask for a copy of the personal data we hold about you, ask for it to be corrected, or ask for it to be erased where we are not required to retain it. Employers can export a company’s full data themselves from the Owner console.
Attendance records that have already been used to calculate a payment cannot be altered, including by us. Where a record is wrong, the correction is recorded alongside it with the reason and who made it — the original remains visible.
You may withdraw consent for optional data, such as an Aadhaar number, at any time.
8. Third parties
Photographs are stored with an object storage provider. Email is delivered through an email provider. Maps are rendered by Google Maps, which receives the coordinates being displayed. We do not use advertising or analytics trackers.
We do not sell personal data, and we do not share it with anyone except as necessary to run the Service or where required by law.
9. Changes to this policy
If we change what we collect or who can see it, we will update this page and change the effective date shown at the top. Material changes will be notified to account Owners.
10. Contact
Questions about this document, or any request concerning your personal data, should go to VISION at anup86017@gmail.com.