1. Purpose of this Notice
This Notice tells you — as a member of Arceus India's workforce — what personal data the Arceus Employee App ("App") collects about you, what work activity it records, how that data is used and protected, and your rights under the Digital Personal Data Protection Act, 2023 ("DPDP Act"), the Information Technology Act, 2000 and the SPDI Rules, 2011.
ARCEUS INDIA PRIVATE LIMITED is the Data Fiduciary. The App is an internal business tool: your use of it is a condition of performing your role, and the data it processes is primarily employment and business-operations data.
Privacy contact / Grievance Officer: aditya@arceusindia.co (Section 13).
2. Account provisioning
You cannot self-register. An administrator invites you; you activate your account with a one-time code and set a password. Your account carries a role (Admin, Operations, Sales, Technician, Dispatch or Accountant) and, where applicable, individually granted permissions, which together determine exactly which data and actions the server allows you.
Your consent to customers seeing your contact details. When you set up your account, the App asks you, in your language and with one tap, to agree that "Customers you visit or serve see your name, work mobile number and confirmed e-mail." Section 7 says when and how they see them. If your account already existed, the App asks you once, the first time you open version 1.9.3 or later. The customers you serve include the customers whose accounts you look after: if you added a customer, they see your name and work mobile number in their app so they can call you (Section 7). Customers get your e-mail address only while you are the technician assigned to their visit; for the accounts you look after, they see only your name and work mobile number. Until you agree, the customers you visit or serve are still shown these details as part of your work (Section 5). We record when you agreed and which wording you agreed to, and your Profile in the App shows the date. There is no switch to turn this off: to withdraw your consent, ask your administrator to delete your account; you can also delete it yourself (Section 9A). Withdrawing does not undo what customers were shown before.
3. Personal data we process about you
3.1 Identity and account data
| Category | Items |
|---|---|
| Identity | Full name, work e-mail address, phone number |
| Employment attributes | Role, individually granted permissions, account status (invited / active / disabled) |
| Credentials | Password (stored only as a salted one-way hash), one-time activation/sign-in codes, session tokens |
| Profile photo | Optional; replaced each time you upload a new one |
| Account history | When your e-mail address and phone number were confirmed; when you last signed in; when you agreed to customers seeing your contact details, and to which wording (Section 2) |
3.2 Work-activity records
Because the App is the system of record for orders, service and installation work, it necessarily records what you do in it:
| Category | Items |
|---|---|
| Order actions | Orders you create, edit, progress, dispatch, deliver, or mark installed; procurement/parts confirmations; delivery-date settings; notes you add |
| Payment records | Payments you record against orders (amount, currency, type) and payment-proof screenshots you upload |
| Task records | Tasks assigned to you, completions, completion notes, dates |
| Tickets & service | Tickets you handle, assignment history, resolution/unresolution actions, chat messages you send |
| Feedback capture | Customer feedback you record on completed orders |
| Google review asks | When you open the "ask for a Google review" link on an order whose installation is complete, a tracked review-intent record (your account, the order, timestamp) is created; the review page itself opens externally in Google |
| Note receipts | When a colleague adds a note to an order you are working on, the App records when that note was shown to you and, separately, when you opened it. Both timestamps, with your name, are shown to the colleague who wrote the note. This applies only to orders you are a party to — the ones you created, are assigned to as a technician, or have written a note on yourself |
| Audit trail | Administrative and sensitive actions are logged with your user ID, the action, and a timestamp |
| Connection data | IP address, the time of each request and what it asked for, the App's version and build, your device's model and operating-system version, on Android its security-update date and on Windows its edition and computer name, and real-time (WebSocket) connection events. On a Windows computer where the App was installed from our download page (app.arceusind.com/download/windows), Windows itself also asks our server for a newer version of the App when the App opens (at most every 4 hours); each check is kept in our server request logs with the IP address and the time |
| Device identifier | A random value the App creates on its first launch and keeps in the device's own secure storage. It names a device in your session list, so signing in again on the same device updates that entry instead of adding another. From version 1.9.3, in a one-way coded (hashed) form, it also lets the device security checks tell one installed copy of the App from another (Device security checks, below). Not a hardware serial, not an advertising identifier (never accessed), and meaningless outside that installation. The App sends it with every request, so it also appears in our request logs. On Android and Windows it is deleted when you uninstall the App, and from version 1.9.3 on iPhone and iPad too (a copy an earlier version left on an iPhone or iPad is deleted when version 1.9.3 or later is installed), so a reinstalled App gets a new one |
| Notification data | Your device's push token (from Apple; on Android from Google Firebase, which also creates an installation identifier), a random installation key, the device's language and operating-system version, whether alerts are switched on, and on iPhone and iPad the Live Activity tokens |
| Device security checks (from version 1.9.3 of the App) | The App runs its first check when it first starts, before you sign in, and then about once a day. A security key the App makes on your device (only its public half reaches us), which signs every request; the result of Google Play Integrity and the phone's hardware key attestation (Android) or Apple App Attest (iPhone and iPad), with short reason codes. On Android, if Google includes them in its answer, short codes saying whether apps that can capture the screen or control the device were running and the state of Google Play Protect; and two yes/no answers the phone's hardware gave when the key was made (whether the device's software was unlocked or unverified, and whether the App was signed by someone other than us). Short codes for what the App finds on the device: the kind of device (for example a phone, an emulator or a virtual machine); signs that the device or its software has been modified (for example rooted or jailbroken), that it has tools able to change how the App runs, or that the App is being debugged; and a few plain facts, such as where the App was installed from, whether the device has a security chip and, on Windows, whether Windows is genuine and Secure Boot is on. A report about the App's installed copy, signed with the security key: its version and build, when it was installed or last updated, where it was installed from (on Android, the name of the app that installed it, usually Google Play), the operating system's answer on whether the App is signed by us (on Windows, also whether its files are unchanged), and fingerprints of the App's own files. A list of the App's own files only when the operating system's check fails, when the App's files have changed without an update, while the device is being checked more closely, or when a changed copy is cut off. On Windows the report also carries a one-way fingerprint of the computer's security chip (TPM), kept only if a changed copy of one of our apps is proven on that computer. On iPhone and iPad, a one-time Apple DeviceCheck token, which we do not keep. A record of each installed copy under a one-way coded form of the device identifier, with its version, where it was installed from, its latest result, when it was first and last seen, and the last file list it sent; if a changed copy is proven and cut off, a record of it (coded forms of its security key, its device identifier and, on Windows, the security chip's fingerprint; the kind of proof; the App's build and where it was installed from; a coded form of its report; how many accounts and sessions were signed out; and when it was cut off and let back in). Both records are kept like the other device security records (Section 9). Which accounts and devices a failed check stopped or signed out, or would have, including devices nobody is signed in on, as a count deleted two days after it is made (for operating-system updates, four days after it was last added to). Once we switch them on, a mark that Apple (DeviceCheck) or Google (Play device recall) keeps for us on a device where a changed copy of one of our apps was proven (Section 7). Never your files, the names of your other apps (apart from the one that installed the App, and the codes above that name rooting tools, emulators or tools that can change how the App runs) or your device's serial number |
| Security log | For requests our security checks flag: the part of your IP address that names your network, a one-way coded (hashed) form of the whole address and of the device identifier, your account, the route asked for and short reason codes; kept 400 days |
3.3 Media you capture or attach
With your in-context permission, the App can use the camera, photo library, microphone and file picker solely so you can attach evidence to work records:
- photos/screenshots attached to tickets, order notes, or as payment proof;
- dispatch photos and videos: a photo or a short video (with its sound) of each machine of an order, taken or chosen before the order is dispatched;
- voice notes recorded and attached to ticket messages or order notes;
- documents/files attached to work records.
Media is captured only when you actively choose to attach something; there is no background capture, and the App never accesses these device features on its own. Media you attach becomes part of the business record it is attached to.
Dispatch photos and videos are shown to the customer. Once the order is dispatched, the customer (and the people on the customer's company account who can see that order) can view and save them in the customer app, as a record of how the machines left our workshop. The App tells you this on that screen. Photograph the machine, not people: if a person (you included) or the wrong machine is in a photo or video, it can be removed from the order, and the removal is recorded in the audit trail. Before storing a photo or an MP4 or MOV video you attach, our server removes the place where it was taken (and, from a photo, every other detail the camera stored in it), so the customer never receives that location; other files, such as WebM videos, are stored as you sent them. Files stored before we started doing this, during the 1.9.3 update of our service, are cleaned the same way by a one-off job.
3.4 What the App does not collect
- No location tracking — the App requests no GPS/location permission on any platform;
- No analytics, advertising or behavioural-tracking SDKs;
- No biometrics collected by us (if you unlock your device or Keychain with Face ID/fingerprint, that stays on your device and never reaches us);
- No personal communications — the App cannot read your e-mail, SMS, contacts, calendar or other apps;
- No keystroke, screen or off-app monitoring. The App never watches what you do outside it. To protect company and customer data it checks the device it runs on and its own installed copy, and sends us only what Section 3.2 lists under Device security checks. iOS Live Activities (lock-screen task status) and the App's icon in the Windows notification area are drawn on your device from your own work data and collect nothing more.
4. Customer personal data you handle — your obligations
Through the App you will process customers' personal data (names, contact details, addresses, order and payment information, complaint content). In doing so you act for Arceus India, and you must:
- access customer data only as needed for your assigned work (the server enforces role-based limits — e.g., payment amounts and status are hidden from Technician accounts and from Operations accounts without the payment-visibility permission, and payment-proof files are blocked server-side for technicians). Depending on your role you may see customers' dates of birth, gender, GSTIN, billing details and the mobile numbers of their site contacts: use them only for the order in hand, and call a customer's site contact only about that delivery or installation;
- never copy customer data out of the App except as your role requires;
- never disclose customer data to unauthorised persons, inside or outside the company;
- report any suspected misuse, loss or breach immediately to
info@arceusindia.co; - keep your device passcode-protected and your account credentials secret. Your account actions are attributable to you.
Violations may attract disciplinary action and, where applicable, liability under the IT Act and the DPDP Act.
5. Purposes and lawful basis
Arceus India is your employer, so for the work below it relies on the legitimate use the DPDP Act allows for employment, section 7(i): processing for the purposes of employment, and to safeguard the employer from loss or liability. Where something goes beyond that, it asks for your consent.
| Purpose | Lawful basis under the DPDP Act |
|---|---|
| Giving you authenticated, role-appropriate access to business systems | Employment (section 7(i)) |
| Running orders, service, installation, payments and support operations | Employment (section 7(i)) |
| Maintaining audit trails, preventing fraud, securing systems, and checking the devices the App runs on (Section 3.2) | Employment (section 7(i): safeguarding the company from loss or liability); our duty to keep reasonable security practices (section 43A of the IT Act) and the logs the CERT-In directions require |
| Workforce coordination (tasks, notifications, real-time updates, reports) | Employment (section 7(i)) |
| Showing your name, work mobile number and confirmed e-mail address to the customers you visit or serve (Section 7) | Employment (section 7(i)): a customer needs to know and reach the person who is coming to them, and the person who looks after their account. From when you agree in the App (Section 2), also your consent; withdrawn by having your account deleted |
| Meeting legal obligations (tax, accounting, statutory records, lawful orders) | What a law or a court requires of us (sections 7(d) and 7(e)), and keeping the records a law requires us to keep (section 8(7)) |
We do not use workforce data for advertising, we do not sell it, and we do not use it for automated decisions producing legal effects about you without human involvement.
6. Transparency about workplace monitoring
The App records the business actions you take in it (Section 3.2), standard connection metadata, and — on orders you are a party to — when a colleague's note was shown to you and when you opened it (the "Note receipts" row in Section 3.2), which that colleague can see. That is the full extent of monitoring. The App does not track your location, does not monitor your device outside the App (apart from the device checks below, which look only at the App's own installed copy and at the device's security state, and are used only for security), and does not record audio or images except when you actively attach them. Reports and dashboards aggregate work data (e.g., technician workload) for operations management; they are derived from the same records listed above.
Device checks (from version 1.9.3 of the App). The App also checks that the device it runs on, and the App itself, have not been tampered with (Section 3.2). Until version 1.9.3 is the oldest version of the App the company supports, a failed check is only recorded. From that day, with no waiting period, a failed check leads to more than a warning only when Google's or Apple's signed answer, or the operating system's own check of the App's signature, proves the failure and at least one more check, ten minutes or more later, confirms it. A single check is enough when Google's or Apple's signed answer shows that the App is not ours. What the App notices on the device never counts on its own. Once a failure is proven this way, that device stops working with the App, apart from your own profile, your sessions, signing out and deleting your account, until it passes again; ask your administrator for help. Its requests are also stopped in the same way if a proven failure is still waiting for its confirming check after more than eight days, until the App checks again, which it does by itself. If your copy of the App is proven to have been changed, that copy stops working altogether: it asks you to install the App again from the official app store (on Windows, from app.arceusind.com), and removes your sign-in, its security key, the device identifier, the fingerprints of its own files, and its settings and temporary files from the device. Everyone who was signed in on it is signed out on all their devices and gets our usual message saying so. You can still delete your account on the website (Section 9A) or get help at app.arceusind.com. A genuine copy installed again from the official app store (on Windows, from app.arceusind.com) works normally; if it still carries the changed copy's security key, it works again as soon as it passes its checks, and where it cannot pass them, it asks you once more to install the App, removes that key, and works normally from its next start. Where the server can still recognise the device (for example a Windows computer, by its security chip), the App there is checked more closely, at every start, until it passes its checks and for 30 days after. If, within an hour, unusually many members of staff on one platform and App version are stopped or signed out (or would be) because of a failed check, which points to a fault at Google or Apple rather than at the devices, the server by itself stops blocking devices, cutting off copies and signing people out on that platform and version for at least a day. If, within three days, the operating system's check of the App fails on the iPhones, iPads or Windows computers of more than two members of staff with the same operating-system version, which points to a fault in an operating-system update, the server stops blocking devices, cutting off copies of the App and signing people out on that operating-system version, and lets back in the copies it cut off in that time. On Windows, and on iPhones and iPads when Apple's App Attest gives no answer, only the operating system's own check of the App can count against a device, and only where the App's security key is held in the device's security chip.
7. Sharing and disclosure
| Recipient | What | Why |
|---|---|---|
| Your colleagues | Your full name on the work you do, to every colleague who can open that order, part order, task or complaint; if you add a customer, your name as the person who added them, shown only to Sales staff and Administrators. If you are a technician: your mobile number and confirmed e-mail address to Sales (their own orders and complaints), Operations, Administrators and the other technicians on the same job, with Call and Email buttons; Operations and Administrators also see every technician's mobile number and confirmed e-mail address when they assign work. Administrators see every employee's name, mobile number, e-mail address, role and permissions. Dispatch and Accountant staff never see a technician's contact details | Operations management, scheduling, supervision |
| Customers (the account holder, and the people on the customer's company account who may see that order or complaint) | The first name of the person who acted on their order, part order or a note shared with them, in the customer app, notifications, e-mails and SMS; the full name of everyone who writes in a complaint's chat. If you are the technician assigned to a customer's complaint, client trial or installation: also your full name, your mobile number and, once you have verified it, your e-mail address, shown in the customer app with Call and Email buttons and sent to the customer by SMS and e-mail while you are assigned to that visit. If you look after customer accounts (you added the customer): from version 1.9.3 of the customer app, your full name and your work mobile number, shown to the account holder and the people on their company account in the customer app's Profile with a Call support button, for as long as you are active and in a Sales or Admin role (never your e-mail address or your photo). The dispatch photos and videos of their machines (Section 3.3), after the order is dispatched, with no name attached. Customers never receive your profile photo, or the phone number or e-mail address of any other member of staff | So customers know who is handling their order or complaint, can reach the technician who is coming and the person who looks after their account (there is no company support number), and can see how their machines left our workshop |
| Data Processors — infrastructure | Data stored/transmitted through our servers | Hosting of our application, database and object storage (attachments, payment proofs, voice notes, dispatch photos and videos are stored in company-operated object storage and are malware-scanned on upload) |
| Data Processors — communications | Your e-mail address, phone number and message content, which can include colleagues' and customers' names; if you are an assigned technician, your name, mobile number and verified e-mail address inside the messages we send to that customer; your device's push token and each notification's title and text | Microsoft (Microsoft 365 / Graph) delivers transactional e-mail (e.g., invites, and customer updates that name the technician coming and how to reach them); Fast2SMS delivers SMS (e.g., activation codes, and the same customer updates); Apple (iPhone and iPad) and Google Firebase (Android) deliver notifications — delivery only, on our instructions. Notification texts never include an address or a phone number of their own |
| Device checks — Google and Apple (from version 1.9.3 of the App) | A Google Play Integrity token, which our server asks Google to read (Android); Apple App Attest (iPhone and iPad). Once we switch them on: the one-time DeviceCheck token your iPhone or iPad sends with its checks, which our server then passes to Apple, and, on Android, the same Play Integrity token, with which our server asks Google to mark the device (Google Play's device recall) | Checking the App is genuine and the device has not been tampered with; marking a device where a changed copy of one of our apps was proven, which only means closer checks there (Sections 3.2 and 6) |
| Password-safety check | A 5-character partial hash prefix (never the password, never a full hash) | Breached-password screening via the Have I Been Pwned k-anonymity API when you set a password |
| Government authorities, courts, regulators | As legally demanded | Compliance with law |
| Professional advisers / successors in business | Relevant records | Audits, legal advice, corporate transactions — under confidentiality |
8. Storage and security
- All App–server traffic is encrypted in transit (TLS, including the real-time WebSocket channel).
- From version 1.9.3, everything the App keeps on your device (session tokens, the device identifier, settings and temporary files), apart from the fingerprints of its own installed files and the result of their last check, a few technical notes about its security key, what the system needs to show its notifications and live cards without opening the app, and two kinds of file copy described below, is encrypted with a key protected by the device's security chip (Secure Enclave, Android Keystore, TPM; an older PC without such a chip uses a software key kept on the device), checked every time it is read (a changed byte is never used: you sign in again, or, if only settings were changed, they are reset), and kept only in the App's own storage, which uninstalling removes (on iPhone, iPad and Windows the App deletes the few protected items the system keeps after uninstall when it is installed again). Files are checked against the server's fingerprint before they are shown, once the server has one for that file (for a file sent before these checks began, from its first complete download). When another app, or your device's own viewer or player, needs a file or voice note itself, the App keeps one copy in its own temporary storage and deletes it soon after, or at the latest at the next start. This copy is not encrypted by the App. Nor is a photo, video or file you add, until the App has taken it in (at the latest, the next start). Passwords are never stored on devices and are held server-side only as salted one-way hashes (Argon2id). Activation/sign-in codes are stored as keyed hashes, expire within 5 minutes, are single-use and rate-limited.
- Role-based access control is enforced on the server, not just in the interface; permission changes take effect on your next token refresh and sensitive routes re-validate permissions.
- Administrative and sensitive actions are audit-logged to a technically immutable store (records cannot be edited or deleted), including the acting account, action, target, IP address and timestamp.
- From version 1.9.3 the App keeps its security key in your device's secure hardware where the device has it, so the key cannot be copied off the device, and it accepts only our own server's certificate.
- Data resides on Arceus India's server infrastructure hosted in India.
- We maintain reasonable security practices under section 43A of the IT Act and the SPDI Rules, and meet the DPDP Act's security-safeguard obligations. Personal data breaches will be notified to the Data Protection Board of India and affected individuals as the DPDP rules require.
9. Retention
| Data | Retention |
|---|---|
| Identity/account data | Duration of engagement + 3 years, except where longer statutory periods apply |
| Business records you created (orders, payments, installations, notes, attachments) | Retained as company business records — commercial relationship + 8 years (Companies Act, 2013 / tax laws). These are records of the business, not of you personally, but they remain attributed to your account |
| Sign-in records and notification registrations | No time limit is applied yet. By 13 May 2027: sign-in records deleted 13 months after the sign-in; a notification registration one year after it was last used |
| Device security records | Not deleted automatically yet, apart from the counts in Section 3.2, each deleted two days after it is made (for operating-system updates, four days after it was last added to). By 13 May 2027: one year after the device was last seen or its key was removed |
| Security log | 400 days, then deleted automatically |
| Profile photo | Until you replace or remove it, or your account is deleted |
| Audit logs | Kept with no end date for now: the log is built so that its entries cannot be changed or deleted. By 13 May 2027 it gets a fixed period of at least one year, after which the names of people who have left are replaced with internal references |
| Tickets/chat/voice notes | 3 years from ticket closure |
| Server request logs | 180 days, then deleted. India's cyber-security rules (the CERT-In directions) ask us to keep them for that long |
| Disabled accounts | Deactivated immediately on exit; personal identifiers minimised after the periods above |
9A. Deleting your own account
You can delete your own account, at any time, without going through an administrator. There are two ways, and both do the same thing:
- in the Arceus Employee app, under your profile;
- on the web, from the employee section of
/account-deletion.
We send a separate one-time code to your registered e-mail address and another to your registered phone number, and both must be entered. Account deletion cannot be undone.
An administrator account cannot be deleted this way. Removing the last administrator would leave the business unable to manage its own users, so an administrator must first have their role changed by another administrator.
What is erased: your credentials, your active sessions, any outstanding one-time codes, and your personal identity data on the account.
What remains: the business records you created — orders, payments, installations, notes and attachments — and the audit log of administrative actions. These are records of the business, not of you personally, and Section 9 sets out how long they are kept. They stay attributed to your account so the business can answer questions about who did what. That attribution is a legal and audit requirement and is not removed by deleting your account. The device security records (Section 3.2) also remain; Section 9 sets out how long they are kept.
10. Your rights
Subject to the DPDP Act's provisions applicable to employment-related processing, you may: access a summary of your personal data; seek correction of inaccurate identity data (name, contact details — via your administrator or the contact below); seek erasure where data is no longer necessary and no law or legitimate business/audit purpose requires it; nominate a person to exercise rights on your behalf; and raise grievances (Section 13). You may withdraw your consent to customers seeing your contact details (Section 2) by asking your administrator to delete your account, or by deleting it yourself (Section 9A). Note that work records and audit trails generally must be retained for the periods in Section 9 notwithstanding an erasure request — the DPDP Act permits retention required for compliance with law and for employment-related legitimate uses.
11. Consequences of not providing data
The App and an account on it are required tools for the roles that use them. Declining to provide the identity data in Section 3.1, or revoking the in-context device permissions needed for a specific task (e.g., camera for payment proof), may mean you cannot perform those parts of your role; it has no other consequence.
12. Children
Accounts are issued only to persons legally competent to be employed or engaged by Arceus India; the App is not for use by anyone under 18.
13. Grievance Officer and contact
Grievance Officer, ARCEUS INDIA PRIVATE LIMITED
Name: Aditya Upadhyay
E-mail: aditya@arceusindia.co
Address: 22/A, Off Nagar Road, Vrundavan Nagar, Vadgaonsheri, Pune - 411014, Maharashtra, India
Grievances are acknowledged promptly and resolved within the prescribed statutory period. If unsatisfied, you may approach the Data Protection Board of India. This channel is in addition to, and does not replace, internal HR grievance procedures.
14. Cross-border transfers
Workforce and business data is stored in India. We use Apple, Google and Microsoft to deliver notifications and e-mail, so your data may be processed outside India. Indian law permits this, subject to any restrictions the Central Government notifies under section 16 of the DPDP Act.
What passes through them: your device's push token and each notification's title and text (Apple and Google), e-mail (Microsoft 365) and, from version 1.9.3 of the App, the device checks (Google Play Integrity and Apple App Attest and, once we switch them on, Apple's DeviceCheck and Google Play's device recall). They act on our behalf, we remain responsible for what they do with your data, and we keep no records with them, apart from the device mark that DeviceCheck and device recall keep, which names nobody (Section 7).
15. Changes
We may update this Notice as the App or the law evolves. Material changes will be notified in the App and/or by e-mail, with the effective date updated above. Each notice says plainly what changed, and whether it is something new or a correction of how we described something we already did.
16. Governing law
This Notice is governed by the laws of India. Subject to applicable law, courts at Pune, Maharashtra, India shall have jurisdiction.