This policy explains what personal data we handle through this website, through our Android app Attendance & Field Tracker, and through the attendance and job-work service behind both, why we handle it, and what rights you have. Our registered name and address are on our Contact Us page.

Two different roles

• This website. We decide what is collected here, which is very little — see below.
• The service and the app. When your employer subscribes, they decide what staff data is recorded and for how long. We process it on their instructions. Requests about your own attendance records should go to your employer first; we will assist them.

What we collect on this website

• Nothing but what you send us. This site has no analytics, no advertising pixels and no third-party trackers.
• Server logs — IP address, browser type, the page requested and the time, kept for security and abuse investigation.
• Local storage — your cookie-notice choice, and, once you sign in, your session token. Both are stored in your own browser and are strictly necessary for the site to work.

What the service records

To do its job the service records, for staff of a subscribing organisation: name, email address, employee ID, role and department; punch times; the location of a punch and a place name derived from it, where the organisation has enabled that (that derivation uses an outside service — see Sharing); and photos or video captured at a punch, where the organisation has enabled that. Administrators of that organisation can see these records. We can see them only as needed to operate and support the service.

The Android app

The app is a way of using the same service from a phone. It records nothing the web console does not, and it shows you only your own organisation's data. In particular:

• Location — only when you punch. The app reads your location at the moment you tap Arrive, Sign off, Start break, End break, Start task or Stop task, and at no other time. It is sent with that punch so your employer has a record of where it was made, and, where your organisation has set up a site boundary, so the distance from that boundary can be recorded. The app does not track you in the background. It asks for no background-location permission and contains no code that could read your location while you are not using it.
• Camera. Where your organisation requires a photo to arrive or to sign off, and whenever you attach evidence to a job-work task, the app opens your camera. The photograph or video — and, for a video, the sound recorded with it — is uploaded and attached to that punch. You are shown what was captured and can discard it before it is sent. The app never reads your photo gallery or any file you did not just take for it.
• What is kept on your phone. So that you can punch on a site with no signal, punches and captures you make are stored on your own device until they reach us, and then removed from it. Your sign-in token and the few settings the app needs are held in your device's encrypted storage.
• What signing out does, and does not, remove. Signing out clears your session and everything the app was showing you — your day, your job works, anything half-captured — so that the next person to sign in on that phone sees nothing of yours. A punch you made that has not reached us yet is deliberately kept, because deleting it would throw away a record of work you really did; the app tells you so when you sign out. Until those punches have been sent, the phone also keeps what is needed to send them as yours — so they are filed against you and never against whoever signs in next. Both are removed as soon as the last of your punches has reached us, and uninstalling the app removes everything it holds immediately.
• Signing in with Google. If you choose to, Google tells us your name, your email address and an identifier for your Google account. We use those only to find the membership your administrator already created for you. We never receive your Google password, and the app cannot create an account for you.
• No advertising, no analytics, no tracking. The app carries no advertising, no analytics and no third-party tracking of any kind. It does not read your advertising identifier. Nothing it collects is used to profile you or is sold to anyone.

Payment data

Payments are handled by our payment gateway, on this website only — the app takes no payments and offers no purchases. We never see or store your card number, CVV, UPI PIN or any other payment credential. We keep the gateway's transaction reference, the amount and the status, because we must, in order to issue invoices and handle refunds.

Sharing

We do not sell personal data, and we share none of it for advertising. We share it only with service providers who help us run the service — hosting and object storage, email delivery, and payment processing — each bound to use it solely for that purpose, and where the law requires disclosure.

There is one exception, and it is set out here rather than left inside that sentence, because it is not a service provider working under contract for us. Where your organisation has enabled place names, turning a punch's coordinates into a place name uses an outside mapping service — at present OpenStreetMap's Nominatim, and it may be a different provider in future. Our server sends it a coordinate and receives a name for it. Nothing that identifies you is sent with it.

Such a service is independent of us and handles those requests under its own terms, not ours. If your organisation would rather no coordinate left our systems at all, place names can be switched off for it, and the app then shows coordinates as it did before.

Where data is stored, and how it travels

Everything the app and the website send to us travels over an encrypted connection (HTTPS/TLS). Service data is stored on infrastructure in the region matching the customer organisation's country where one is available, and otherwise in a default region. Photos and video are stored in object storage that is not publicly readable; they are served only through short-lived links to signed-in users of the owning organisation.

How long we keep it

Service data is kept for as long as the organisation subscribes, and is deleted when the organisation is deleted, save for invoices, credit notes and payment records, which we are required to retain for statutory accounting and tax periods. Website server logs are kept for a limited period for security purposes.

Deleting your data

Your employer holds your attendance records, so deletion normally starts with them:

• If you are an employee, ask your organisation's administrator. They can deactivate your account, which stops it being used, and they can ask us to erase records held for it.
• If you are an administrator, or your employer will not act, write to us at the email address on our Contact Us page, from the address your account uses, saying what you want deleted. We will confirm who you are, act within thirty days, and tell you when it is done.
• Deleting the app from your phone removes everything stored on the phone, including anything still waiting to be sent. It does not by itself delete records already held by your employer.

Some records we must keep even after a deletion request: invoices, credit notes and payment records, for the statutory accounting and tax periods. We keep nothing else.

Your rights

Under India's Digital Personal Data Protection Act, and under the GDPR where it applies to you, you may ask us to give you access to your personal data, correct it, delete it, or withdraw consent you previously gave. Write to the email address on our Contact Us page. If your data is held on behalf of your employer we will direct the request to them and help them answer it.

Changes

If we change this policy materially we will update the date below and, where the change affects consent, ask for it again.