Arceus India

Customer app

Privacy Policy — Arceus India App

ARCEUS INDIA PRIVATE LIMITED
CIN: U32909PN2026PTC255995 · Registered Office: 22/A, Off Nagar Road, Vrundavan Nagar, Vadgaonsheri, Pune - 411014, Maharashtra, India
Effective date
20 October 2026
Last updated
20 October 2026
Applies to
the "Arceus India" application on iOS, iPadOS, macOS, Android, and Windows, and the services it connects to at app.arceusind.com.

1. Who we are

This application ("App") is owned and operated by ARCEUS INDIA PRIVATE LIMITED ("Arceus India", "we", "us", "our"), a company incorporated under the Companies Act, 2013.

For the purposes of the Digital Personal Data Protection Act, 2023 ("DPDP Act") we are the Data Fiduciary for the personal data described in this Policy, and you — the customer using the App — are the Data Principal. For the people a company adds to its account, the company and we share these roles as Section 5 explains.

Privacy contact / Grievance Officer: aditya@arceusindia.co (see Section 12).

2. Scope of this Policy

This Policy describes what personal data we collect through the App, why we collect it, how we protect it, how long we keep it, whom we share it with, and the rights you have under Indian law, including:

  • the Digital Personal Data Protection Act, 2023 and the rules made under it;
  • the Information Technology Act, 2000, including Section 43A and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 ("SPDI Rules").

This Policy covers only the Arceus India App and its backend services. It does not cover our website(s) or any offline interaction you may have with us, which may carry their own notices.

3. The App requires an account we create for you

The App is a service portal for existing customers of Arceus India. You do not create an account yourself; an account is provisioned by us when you place an order with Arceus India. On your first sign-in you verify your identity with a one-time passcode (OTP) sent to the contact details registered with your order and then choose a password. After that you sign in with your password, or with a new one-time code if you prefer.

People added to a company account. If your account belongs to a company, the company's main user (or a person they allow to manage users) can add other people to it, such as colleagues who follow the company's orders or raise complaints. To do this they enter the person's name, mobile number and e-mail address and choose what that person may see and do in the App. We then send the new person a welcome e-mail and SMS with a link to the App. From then on, even before they first sign in, they also get e-mails and SMS messages about the orders, spare-part orders and complaints the company lets them see. If you add someone, you confirm that they agree to it (our Terms, Section 3); please tell them about this Policy, which applies to them as it does to you. If the company later removes a person, they can no longer sign in, but we keep their name, mobile number, e-mail address, profile photo and the protected (hashed) form of their password on our records until the company deletes its account or the person asks us to erase them by writing to info@arceusindia.co.

Apart from these people, the App collects no personal data from anyone who is not already our customer, with two exceptions for security: when someone tries to sign in with an e-mail address or mobile number that is not one of our customers', we record the failed attempt with a partly hidden form of that address or number and the IP address it came from, and, like every request, it appears in our server logs (Section 4.3); and, from version 1.9.3, the App runs its device security check (Section 4.8) when it first starts, before anyone signs in, and what that check sends is linked to no account until someone signs in on that device.

4. Personal data we process

4.1 Data you provide directly in the App

Category Data items When collected
Sign-in identifiers E-mail address and/or mobile number (whichever you use to sign in) At sign-in
Credentials Password (chosen by you); one-time passcodes Password: when you set, change or reset it. One-time codes: at first sign-in, when you sign in with a code instead of your password, when you reset your password, when you confirm a new e-mail address or mobile number, and when you delete your account. Passwords are transmitted over encrypted channels and stored only as salted one-way cryptographic hashes — we cannot read your password.
Your profile Changes you make to your name, e-mail address or mobile number; your profile photo, if you add one (Section 4.5) When you edit your profile
People on a company account The name, mobile number, e-mail address and permissions of each person the company adds (Section 3) When a person is added or their permissions are changed
Support tickets Complaint subject and description; messages you send in ticket chat; the times at which you send them; the photos, videos, voice notes and files you attach (Section 4.5); when you last read each complaint When you raise a complaint or chat with our support/service team
Notification choices Which kinds of alert you want, your quiet hours and the language of your alerts; which alerts you have read, and which ones the App has shown on your device When you change a setting, read an alert, or the App shows one
Google review invitation (optional) The fact and time that you tapped "review us on Google" for an order whose installation is complete (a "review intent") Only if you choose to accept the invitation. The App then opens Google's review page outside the App — anything you do there happens under your own Google account and Google's own Privacy Policy and Terms.
Spare-part orders (from version 1.9.3 of the App) The machine and the part you need, the quantity and any photos you add; a delivery address, if you type one other than your usual address; whether you accept or decline our quote, and the reason, if you give one; your reason for withdrawing a request When you ask us for a spare part

4.2 Data already held in your customer record (visible in the App)

The App displays information from your existing customer and order records with Arceus India, including: your name and contact details; order identifiers, machine/product details and specifications; order status (confirmation, parts, trial, delivery, installation); and delivery/installation dates. For a company account, the people who manage its users also see each person's name, mobile number, e-mail address and photo, whether they have confirmed that number and address, and what each of them may do. This data originates from your commercial relationship with us, not from the App itself.

Details our staff record about you: when our sales team sets up your customer record, they also record your date of birth (for an organisation, its contact person's), your gender if you choose to give it, for a company its date of incorporation and GSTIN, a billing e-mail address and a billing address, and, for each order, the name and mobile number of the person to contact at the delivery site. Section 7 says which of our staff can see each of these.

Order feedback: when our team follows up after an installation, they may record the rating (1 to 5 stars) and the comment you give them. The App shows it to you, read-only. The App itself has no way to submit feedback.

Greeting dates: your customer record may also hold your date of birth (for an organisation, the contact person's date of birth) and, for an organisation, the company's date of incorporation. We use these dates for one purpose only: to send you a birthday greeting and, for organisations, a company-anniversary greeting once a year, by e-mail, as a notification in the App and — where the message template is registered with our SMS provider — by SMS. On the same day, the member of our sales team who set up your account gets a reminder in their app. The greetings contain no offers or requests; the SMS contains no link, and the e-mail has none apart from the usual footer links to this Policy, our Terms and Support. Opting out: if you would rather not receive them, write to info@arceusindia.co (or raise a support ticket in the App) and we will remove the date(s) from your record; no date, no greeting. The dates are erased with the rest of your personal data on account deletion (Section 9A).

Payment information: order payment records (amounts, status) are maintained by Arceus India in connection with your order. The App itself does not collect card numbers, bank details, UPI credentials or any other payment instrument from you, and contains no payment or checkout functionality. When you order a spare part (from version 1.9.3 of the App), the App shows you our quote and lets you accept or decline it; you then pay us outside the App, as for any order.

From our staff: the App also shows you who from our team is working for you, the contact details of the technician who comes to you and, from version 1.9.3 of the App, the name and work mobile number of your Sales contact and the photos and videos of your machines at dispatch. Section 4.6 explains these.

4.3 Data collected automatically (technical data)

Category Data items Purpose
Connection data Your IP address, the time of each request and what it asked for, and the technical description the App sends with every request: the App's version, your device's platform, model and operating-system version, on Android the date of its last security update, and on Windows its edition and the name you gave your computer Server request logs kept for security, abuse prevention and troubleshooting; checking that your App version and device are still supported
Session tokens Cryptographically signed access and refresh tokens Keeping you signed in securely
Sign-in records For each sign-in: when it happened, the IP address, the device's name and model, and the device identifier below Showing you "Where you are signed in" in your profile, so you can see and sign out your other devices; security
Device identifier A random value the App creates on its first launch and keeps in your device's own protected storage (Section 8) Naming a device in "Where you are signed in", 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 our device security checks tell one installed copy of the App from another (Section 4.8). It is not your device's serial number and not an advertising identifier (we never touch those), and it means nothing outside this 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). On a Mac it remains in the App's private folder after you delete the App, and is used again if you reinstall it (Section 8)
Notification data Your device's push token (from Apple on iPhone, iPad and Mac; from Google's Firebase service on Android); a random installation key; the device's language and operating-system version and the App's build; whether notifications are switched on for the App on that device; for each alert, whether your device showed it or could not show it; on iPhone and iPad, the tokens for Live Activities (Section 4.7) Delivering notifications to the right device and keeping live cards up to date; sending an important alert again by e-mail or SMS when no device of yours has shown it
Security records For a request our security checks flag: the part of your IP address that names your network (never the whole address), a one-way coded (hashed) form of the whole address and of the device identifier, your account, the kind of device and the App version, what was asked for, and short reason codes Detecting and investigating attacks on our service, and reporting them as India's cyber-security rules (the CERT-In directions) require. Kept for 400 days (Section 9)

4.4 Data the App does not collect

The App deliberately contains no:

  • analytics, advertising or tracking software of any kind (the only outside software in the App that handles your data is Google's Firebase Cloud Messaging, which the Android App needs to receive notifications, and, from version 1.9.3 of the App, Google's Play Integrity check on Android — Sections 4.8 and 7);
  • collection of advertising identifiers (IDFA / AAID);
  • crash-reporting service: errors are kept only in the App's memory on your device and are never sent to us;
  • location collection: the App never asks for or reads your device's location (no GPS, no coarse location). A photo or video you attach can, however, carry the place where it was taken, if your camera saved it; our server removes it from photos and from MP4 and MOV videos before storing the file (Section 4.5);
  • access to your contacts or calendar;
  • reading of your clipboard, with one exception: on a Mac or Windows computer, while a box asks you for a one-time code, the App checks whether the clipboard holds a code (4 to 8 digits) and, if it does, offers a "Paste code" button. Nothing is pasted unless you tap it, and nothing from the clipboard is kept or sent to us. The App puts something on your clipboard only when you tap Copy (an order number or your account ID);
  • fingerprint or face data (the App has no biometric sign-in);
  • cookies or cross-site tracking (the App has no embedded web browser);
  • third-party social log-ins.

What the App does use on your device: network access to reach our servers; your camera, photo library, microphone and files, each only when you choose to attach something or set a profile photo (Section 4.5); notifications (only if you allow them) and a little background activity to deliver them, which also runs when notifications are switched off, so that we can send an important alert by e-mail or SMS instead (Section 4.7); and, for the device security checks, a few facts about the device, its operating system and the App's own files (Section 4.8).

4.5 Photos, videos, voice notes and files you attach

In a complaint's chat you can attach a photo, a video, a voice note or a file, and in your profile you can add a profile photo. All of this is optional. You choose each item, and nothing is taken or recorded unless you start it.

What you do What the App uses How permission works
Take a photo (complaint chat or profile photo) The camera, for one photo iPhone and iPad: the system asks your permission the first time. Android: the App has no camera permission; it opens your phone's own camera app, and only the photo you take comes back to the App. The Mac and Windows apps do not use a camera.
Choose a photo (complaint chat or profile photo) The photo you pick You pick it in your device's own photo picker. On iPhone and iPad (iOS 14 and later) the App receives only the photos you pick and cannot see the rest of your library, so no permission prompt is needed. On Mac and Windows it is a normal file window.
Record a voice note (complaint chat, every platform) The microphone, while the recorder is open Your device asks your permission the first time. Recording starts as soon as the recorder opens (if you use a screen reader such as VoiceOver or TalkBack, it starts only when you tap Record). When you tap Stop, or after 5 minutes, the voice note is attached and starts uploading straight away, like any file (see below). If you tap Cancel, the recording is discarded and nothing is sent.
Attach a file (complaint chat) The file you pick You pick it in your device's own file browser, and the App can read only that file. Accepted: PDF documents, photos, videos (MP4, MOV, WebM) and audio files. A video can be attached only this way.

You can withdraw any of these permissions at any time in your device's settings. The rest of the App keeps working; only that feature stops until you allow it again.

What we receive and keep:

  • On a phone, a photo is saved again at slightly lower quality before it is sent, and a profile photo is also reduced to at most 512 pixels on its longer side. Videos, voice notes and other files are sent as they are.
  • We remove the place where it was taken from every photo and every MP4 or MOV video you send, before we store it. Our server does this as the file arrives, whichever version of the App sent it: from a photo (JPEG, PNG, WebP or HEIC) it removes every detail your camera stored in it, and from a video (MP4 or MOV) the place where it was taken. Other files (for example WebM videos, WAV and MP3 audio and PDF documents) 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; copies in our backups keep the old details until those backups expire in the normal way.
  • Every file is checked for malware on our servers before anyone can open it, and a file found to be infected is deleted.
  • A file starts uploading as soon as you pick it, before you tap Send, so that it is ready when you send your message. If you remove it before sending, it is not added to the conversation, but the copy already uploaded stays on our servers with that complaint.

Who can see them: attachments in a complaint can be seen by you, by our staff who handle that complaint (Section 7) and, for a company account, by the other people on the account who are allowed to see complaints. Your profile photo can be shown with your name to your Sales contact and our administrators (Section 7) and to the other people on your company account. It is not public: nobody else can open it.

How long we keep them: attachments are kept with the complaint they belong to (Section 9). You cannot delete them yourself, and they stay with the complaint if you delete your account (Section 9A). Your profile photo is deleted when you remove or replace it, or delete your account.

4.6 What our staff share with you

The technician who comes to you. When a technician is assigned to your complaint, your client trial or your installation, we give you their full name, their mobile number and, once they have confirmed it, their e-mail address:

  • in the App: on your complaint while it is assigned to them, and, from version 1.9.3 of the App, on the order screen while your client trial is scheduled and from delivery until your installation is complete;
  • in the e-mails and text messages we send you about that visit or complaint. A text message includes the technician's mobile number only once that message is registered with the mobile networks; until then the e-mail carries it.

Call and Email open your device's own phone or e-mail app; the App does not see the call or the e-mail. We stop showing a technician's details when they are no longer assigned to that visit or complaint, when they no longer work for us as a technician, and once your complaint is finished (resolved, marked unresolved or closed).

Use these details for your visit only. We give you a technician's contact details only so you can reach them about that visit or complaint. Please use them only for that, and do not pass them on to others.

Your Sales contact (from version 1.9.3 of the App). Your Profile in the App shows the name and work mobile number of the member of our team who set up your account. On a company account, everyone on the account sees the company's Sales contact. Call support opens your device's own phone app; the App does not see the call. We show these details only while that person works for us and looks after customer accounts. Otherwise the App shows no Call support button, and you can still raise a complaint in the App or write to info@arceusindia.co. Please use the number only to reach us about your account, your orders and your complaints, and do not pass it on to others.

Who you see from our team. In a complaint's chat you see the full name of each member of our staff who writes to you. Elsewhere (order notes we share with you, your spare-part orders, notifications and your order history) you see the first name of the person who acted. Apart from the technician who comes to you and your Sales contact's work mobile number, we never give you the phone number or e-mail address of any member of our staff, and we never give you a photo of any member of our staff; to reach us otherwise, write to info@arceusindia.co.

Dispatch photos and videos of your machines (from version 1.9.3 of the App). Before an order leaves our workshop, our staff take a photo or a short video of each machine. Once the order is dispatched, you, and the people on your company account who can see that order, can view and save them in the App. Like every photo and every MP4 or MOV video, they are stored without the place where they were taken (Section 4.5).

People you name. When you add a colleague to your company account, or give us the name and mobile number of a person to contact at your delivery site, please make sure they agree to us using their details for that purpose (our Terms, Section 3).

4.7 Notifications and background activity

Notifications. The App asks for permission to show notifications through your device's own prompt: on iPhone, iPad and Mac it first explains why, and on Android 13 and later the prompt appears after you sign in. You can say no, and you can turn notifications off at any time in your device's settings. If you do, the App still registers your device and tells us it cannot show alerts, so that important ones reach you by e-mail or SMS. Once you are signed in on a phone, tablet or Mac, the App registers that device with us (the notification data in Section 4.3) so that alerts about your orders and complaints reach it. On iPhone and iPad models that support them, the App can also show Live Activities, a card on your Lock Screen that follows an order or a complaint, and on recent Android phones a similar live notification.

Background activity. The App does a little work when you are not using it, and only for notifications:

  • on every device, when an alert arrives, the App tells our server whether it was shown (on iPhone, iPad and Android even while the App is closed; on Mac and Windows while the App is running, including in the menu bar or notification area). If no device of yours has shown an important alert after a while, we send it again by e-mail or SMS;
  • on Mac and Windows, closing the window keeps the App running in the menu bar or notification area, connected to our server, so that alerts still arrive. Quit it from its icon to stop it. On Windows the App starts when you sign in to your computer unless you turn this off in the App or in Windows Settings; on a Mac it does so only if you turn it on.

The App collects nothing else in the background.

If you installed the App on a Windows computer 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 a request to our server, so it is kept in our server request logs with your IP address and the time (Section 9).

Rating the App. After you have used the App for a while, it may ask you to rate it, using the app store's own rating window. The App counts how often you open it on your device only, and sends us nothing about this. A rating you give goes to Apple, Google or Microsoft under their own terms.

4.8 Device security checks

Our servers can check that a request really comes from our genuine App on a device that has not been tampered with, using the checks built into your device's operating system: Google Play Integrity and the phone's hardware key attestation on Android, and Apple App Attest on iPhone, iPad and Mac. From version 1.9.3 the App runs these checks automatically. It creates a security key on your device, signs every request it sends us with that key, and checks that it is talking to our real server. This is how the checks work:

  • What is checked: that the App is our genuine, unmodified App; on Android, whether the device passes Google's integrity checks, whether the App's security key is held in the device's secure hardware, whether the device's software is locked and verified, and its Android version and security-update date; on Apple devices, that Apple vouches for the App and the device. On every device, Windows computers included, the App also asks the operating system whether the App is signed by us and, on Windows computers and Macs, whether its files are unchanged. It looks for signs that the device or its software has been modified (for example rooted or jailbroken), that the device has tools able to change how the App runs, that it is an emulator or a virtual machine, or that the App is being debugged. It notes a few plain facts too, 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. The App runs its first check when it first starts, before you sign in, and then about once a day.
  • What we keep: the public part of a security key the App creates on your device (the secret part never leaves the device), the device's platform and the kind of key storage, the App version, and the result of each check with short reason codes (the last 8 results). On Android we also keep 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. We keep short codes for what the App found on the device (the kind of device, any of the signs above and the plain facts it noted), never a serial number or the name of any of your files. We keep a report about your copy of the App, signed with its 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 result of the operating system's check above, and fingerprints of the App's own files. The App sends a list of its own files only when the operating system's check above fails, when its files have changed without an update, while the device is being checked more closely, or when a changed copy is cut off; the list never includes your files. We keep one record for each installed copy of the App, under a one-way coded (hashed) form of its device identifier (Section 4.3), 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. On Windows the report also carries a one-way fingerprint of the computer's security chip (TPM); we keep it only if a changed copy of one of our apps is proven on that computer. If a changed copy of the App is proven and cut off, we keep a record of it: coded forms of its security key and device identifier (and, on Windows, of 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. The records of installed copies and of cut-off copies, like the rest of the check results, are not deleted automatically yet (Section 9). To tell a fault at Google or Apple, or in an operating-system update, from a real attack, we also count which accounts and devices a failed check paused or signed out, or would have, including devices nobody is signed in on; each count is deleted two days after it is made (for operating-system updates, four days after it was last added to). On Apple devices we also keep the App Attest key, its counter and Apple's receipt. We do not keep Google's integrity token, the one-time Apple DeviceCheck token the App sends from iPhone, iPad and Mac, or your device's certificates.
  • What Google may add: on Android, if Google includes them in its answer, we also keep short codes saying whether apps that can capture the screen or control the device were running, and the state of Google Play Protect. We never receive or keep the names of those apps.
  • Who is involved: your device asks Google (Android) or Apple for the check, and on Android our server then asks Google to read Google's answer. Once we switch them on, Apple's DeviceCheck (iPhone, iPad and Mac) and Google Play's device recall (Android) let us leave a mark with Apple or Google on a device where a changed copy of one of our apps was proven, and read that mark when the App is checked on that device later. The mark names nobody and never cuts a device off: it only means the App there is checked more closely, and we act on it only in the month it was set and the following month.
  • What it is for: security only, to spot fake or tampered copies of the App and sign-ins copied to another device. Until version 1.9.3 is the oldest version of the App we support, a failed check is only recorded; it does not block you. 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. The signs the App looks for on the device never count on their own. Once a failure is proven this way, accepting or declining a quote, changing the people on your company account and changing your e-mail address or mobile number are paused on that device until it passes again. Everything else, including reading your data, contacting support and deleting your account, stays open, unless that copy of the App is cut off as described below. The same steps are also paused 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: 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 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 our 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 customers on one platform and App version are paused 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, our server by itself stops these pauses, cut-offs and sign-outs 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, Macs or Windows computers of more than two customers (each company counts once) with the same operating-system version, which points to a fault in an operating-system update, our server stops these pauses, cut-offs and sign-outs on that operating-system version, and lets back in the copies it cut off in that time. On Windows computers, and on iPhones, iPads and Macs 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. We never use these results for advertising, marketing or profiling. They are kept as security records (Section 9).

5. Purposes and lawful basis of processing

The DPDP Act allows two grounds for using personal data: your consent, or one of the legitimate uses its section 7 lists (for example data you gave us yourself for a stated purpose, section 7(a), or what a law requires). We process your personal data only for the following purposes:

Purpose Data used Lawful basis
Authenticating you and securing your account Identifiers, credentials, session tokens, sign-in records, the device identifier Consent, given when you first sign in; you can withdraw it by deleting your account (Section 9A)
Showing you your orders and their status Customer/order records Legitimate use: you gave us these details to buy from us and have your order delivered (section 7(a))
Taking your spare-part orders (from version 1.9.3) The part order, its photos, the delivery address you type, your answer to our quote Consent (you place the order)
Operating the complaints/service-ticket system Ticket content, chat messages, attachments (photos, videos, voice notes, files), when you last read each complaint Consent (you raise the complaint)
Showing your profile photo Your profile photo Consent (entirely optional)
Managing the people on a company account The name, mobile number, e-mail address and permissions of each person added; their welcome e-mail and SMS; the e-mails and SMS messages about the company's orders and complaints The company decides who is on its account and what each person may see, so for this it is the Data Fiduciary and we process the people's data on its behalf, as its Data Processor, under the company's own lawful basis. The company confirms that each person agreed (our Terms, Section 3). Until a person first signs in, we use the name, mobile number and e-mail address the company gave us to send them that welcome and, for what the company lets them see, the e-mails and SMS messages about its orders, spare-part orders and complaints. For our own purposes (keeping every account and our service secure, the rows below) we are the Data Fiduciary, and rely on the consent the person gives at their first sign-in, after the welcome message that links this Policy
Sending you notifications about your orders and complaints, keeping live cards up to date, and sending an important alert again by e-mail or SMS when no device of yours has shown it Notification data, notification choices, your name, e-mail address and mobile number Consent (you sign in and allow notifications on your device; you can turn them off). For a person on a company account, the e-mails and SMS messages about the company's orders and complaints, including those sent before the person first signs in, rest on the company's instruction: we send them on its behalf, as its Data Processor (row above)
Recording your feedback when we follow up an installation Rating, comment Consent (entirely optional)
Sending a yearly birthday / company-anniversary greeting (e-mail, SMS and in-App notification) and reminding your Sales contact of it Date of birth (contact person's, for an organisation); date of incorporation (organisations); name; e-mail address; mobile number Legitimate use: the date was given to us for this stated purpose (section 7(a)); you can tell us at any time that you do not want the greetings, and we then remove the date(s) (Section 4.2)
Running the Google review programme Review-intent records; the public reviews of our Google business listing (reviewer display name, rating, comment, timestamps) retrieved from Google's Business Profile API and matched to review intents only by time proximity (Google does not tell us who wrote a review, and we do not attempt to identify reviewers beyond this time-window correlation) Consent (the tap-through is voluntary). A review its author chose to publish on Google is public, and the DPDP Act does not apply to personal data a person makes public themselves (section 3(c)(ii))
Security, fraud and abuse prevention; diagnosing faults Connection data, sign-in records, security records, audit records, device security check results (Section 4.8) Consent, given when you first sign in (the device security check the App runs before that, Section 4.8, is linked to no account until then); and, for the records Indian law requires us to keep and give to the authorities on request (the CERT-In directions under the IT Act, and section 43A of the IT Act), that legal duty (section 7(d) of the DPDP Act)
Complying with law (tax, accounting, court/authority orders) Order and payment records What a law or a court requires of us (sections 7(d) and 7(e) of the DPDP Act), and keeping the records a law requires us to keep (section 8(7))

We do not use your personal data for advertising, marketing profiling, automated decision-making that produces legal effects, or any purpose incompatible with the above. We do not sell personal data. If we ever wish to process your data for a new purpose, we will notify you and, where required, seek fresh consent.

Where processing rests on your consent, you may withdraw it at any time by writing to info@arceusindia.co or by deleting your account (Section 9A). You can also switch off the App's access to your camera, photos, microphone or notifications at any time in your device's settings (Sections 4.5 and 4.7). Withdrawal is as easy as giving consent, does not affect the lawfulness of processing already carried out, and does not affect processing we must continue under law (e.g., retaining tax-relevant order records). If you withdraw consent required to operate your account, we may no longer be able to provide the App's services to you.

7. Sharing and disclosure

We share personal data only as follows, and never for anyone else's advertising:

Recipient What Why
Our employees and authorised service personnel On a strict need-to-know basis, by role: our technicians, dispatch and operations staff see your name and phone number and, for the orders they handle, each order's delivery address and site contact; our accounts staff see your name, GSTIN and billing details, and your orders and their payment status; your Sales contact (only for the customers they look after) and authorised administrators see your full customer record, including your e-mail address, date of birth, gender, profile photo and billing details. Staff who work on your orders and tickets also see that order and ticket data, including your attachments To process your orders, deliver and install equipment, bill you, and answer your tickets. Access is controlled by server-enforced role permissions; for example, field technicians are technically prevented from viewing your payment information, your e-mail address and your date of birth.
Other people on your company account The company's orders and complaints (with their chat and attachments) and the other details the App shows, according to the permissions the company's main user gives each person; your name and profile photo; the people who manage the company's users also see your mobile number and e-mail address, whether you have confirmed them, and what you may do in the App So that everyone the company chose can follow its orders and complaints
Data Processors — infrastructure Data stored/transmitted through our servers Hosting of our private server infrastructure (application, database, and object storage for any files, all operated by us). Processors act only on our documented instructions under contract.
Data Processors — communications Your e-mail address or phone number and the message content Microsoft (Microsoft 365 / Graph) delivers our transactional e-mails; Fast2SMS delivers our SMS messages (including OTPs) on India's DLT-registered routes. Both act as processors for delivery only — they are not permitted to use your data for their own purposes.
Notification delivery — Apple and Google Your device's push token and each notification's title and text (for example an order step or the start of a chat reply). On Android, Google's Firebase software in the App also creates an installation identifier and sends it to Google so that Google can issue the push token Apple (Apple Push Notification service) delivers notifications to iPhone, iPad and Mac, and Google (Firebase Cloud Messaging) to Android devices, on our behalf. Our notification texts never include an address or a phone number of their own; a message someone types (for example in a complaint's chat) is quoted as it was typed
Device checks — Google and Apple (from version 1.9.3 of the App) On Android, a Google Play Integrity token, which our server asks Google to read; on iPhone, iPad and Mac, Apple's App Attest. Once we switch them on: on iPhone, iPad and Mac, the one-time DeviceCheck token the App sends with its checks, which our server then passes to Apple; on Android, the same Play Integrity token, with which our server asks Google to mark the device (Google Play's device recall) Checking that 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 (Section 4.8)
Password-safety check (privacy-preserving) A 5-character partial hash prefix — never your password and never a full hash When you set a password, we check it against known breached-password lists via the Have I Been Pwned k-anonymity API. The service cannot learn your password or identify you from the prefix.
Google (independent service, not our processor) For the review programme we send Google nothing about you. If you accept a review invitation, you open Google's site/app and interact with Google directly under Google's own terms and privacy policy. Separately, we retrieve our listing's public reviews from Google's API. Operating the optional Google review programme (Section 4.1)
App stores (Apple, Google, Microsoft) Nothing from us. If you rate the App in the store's own rating window, your rating goes to that store directly The optional rating request (Section 4.7)
Government authorities, courts, regulators As legally demanded Where disclosure is required by law or valid legal process
Successors in business Relevant records In a merger, acquisition or restructuring, subject to this Policy's protections

8. Storage, security and where your data lives

  • All traffic between the App and our servers is encrypted in transit using TLS (HTTPS/WSS). The App will not talk to our servers over unencrypted connections.
  • 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 (Section 4.8).
  • On your device, from version 1.9.3 of the App, everything the App keeps (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) — your sign-in tokens, your name, the e-mail address or mobile number you signed in with, the device identifier, the notification installation key and your App settings — is encrypted with a key that your device's own security chip protects (the Secure Enclave on iPhone, iPad and Mac, the Android Keystore, the TPM on Windows; an older Mac or PC without such a chip uses a software key kept on the device instead) and is checked every time it is read. If even one byte has been changed, the App does not use it: you sign in again, or, if only your App settings were changed, they are reset. It is kept only in the App's own storage on your device. Signing out removes the tokens, your name and your sign-in details, and the App's temporary files; the device identifier and the installation key stay (Section 4.3). A file you open from a complaint, or a voice note you play, is checked against our server's own fingerprint of the file before it is shown, once our 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 the file itself, the App keeps one copy in its own temporary storage and deletes it soon after. 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). When you uninstall the App, your device deletes the App's storage; on iPhone, iPad and Windows, a few protected items the system keeps after uninstall are deleted by the App when it is installed again. A Mac keeps the App's private folder until you delete it. We do not store your password on the device.
  • Server-side, passwords are stored only as salted one-way hashes (Argon2id) — we cannot recover them. OTPs are stored only as keyed hashes, expire within 5 minutes, are single-use, and are rate-limited against guessing.
  • Every file uploaded to us is checked for malware before anyone can open it.
  • Access is governed by role-based access control enforced on the server, and administrative and sensitive actions are recorded in tamper-proof audit logs (the log store is technically immutable). The audit log also records your own sensitive actions, such as signing in (and failed attempts), setting or resetting your password, raising or reopening a complaint, uploading a file, and changing your profile or your company's users, with the time and IP address.
  • Personal data is stored on Arceus India's own server infrastructure hosted in India (Section 13 explains the messages that pass through delivery services).
  • We follow reasonable security practices and procedures as required by Section 43A of the IT Act and the SPDI Rules, and the security-safeguard obligations of the DPDP Act.

No system is perfectly secure. In the event of a personal data breach affecting you, we will notify the Data Protection Board of India and affected Data Principals in the form and manner required by the DPDP Act and its rules.

9. Retention

We keep personal data only as long as needed for the purposes above or as law requires, whichever is longer:

Data Retention
Account identifiers and credentials While your account is active; erased immediately when you delete your account (Section 9A)
People removed from a company account Until the company deletes its account or the person asks us to erase them (Section 3); no automatic time limit is applied yet (see below)
Order, delivery, installation and payment records Duration of the commercial relationship plus 8 years, in line with record-keeping obligations under the Companies Act, 2013 and tax laws
Spare-part orders, with their quotes and photos The same period as order records
The billing party recorded against each order The same period as the order it belongs to (Section 9A)
Support tickets and chat, with their attachments (including files uploaded and then removed before sending) 3 years from ticket closure (to handle recurring faults, warranty and disputes)
Profile photo Until you remove or replace it, or delete your account
Feedback Life of the related order record
Notifications Alerts you have read: 180 days after they were sent. Alerts you have not read: until you read them, unless you lose access to what they are about (for example, when a company account changes what you may see), in which case 30 days after that. Records of whether your device showed an alert: 30 days. Live Activity tokens: a card's token is deleted when the card ends and in any case after 12 hours; the token that lets us start a card on your device is kept until you sign out. All Live Activity tokens are deleted when you sign out
Sign-in records and device registrations for notifications Kept as security records. Signing out, or deleting your account, ends them but does not delete them; no time limit is applied yet (see below)
Device security check results (Section 4.8) Kept as security records; not deleted automatically yet (see below), apart from the counts described in Section 4.8, each deleted two days after it is made (for operating-system updates, four days after it was last added to)
Security records (Section 4.3) 400 days, then deleted automatically
Audit log Kept indefinitely: the log is built so that its entries cannot be changed or deleted
Server request logs 180 days, then deleted. India's cyber-security rules (the CERT-In directions) ask us to keep them for that long
OTPs Minutes — expire on use or shortly after issuance

When retention ends, data is deleted or anonymised. Support tickets, with their chat and attachments, are deleted automatically once their 3 years have passed. We are still setting up the automatic deletion that enforces the periods for orders. Under the DPDP Act we will also erase personal data when you withdraw consent or when the purpose is exhausted, unless retention is required by law.

Records with no time limit yet. By 13 May 2027, when the DPDP Act's rules on how long personal data may be kept take effect, we will delete automatically: sign-in records 13 months after the sign-in; a device's notification registration one year after it was last used (we stop using it as soon as Apple or Google tells us it no longer works); device security check results one year after the device was last seen or its key was removed; and the details of a person removed from a company account one year after the removal, unless the company tells us otherwise. From then the audit log is kept for a fixed period of at least one year, after which the names of people who are no longer on an account are replaced with internal references.

9A. Deleting your account, and what survives it

You can delete your account yourself, at any time, without asking us. There are two ways, and both do exactly the same thing:

How we confirm it is you. 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. We ask for both because account deletion cannot be undone, and because a single compromised channel should not be enough to destroy someone's account.

What is erased. Your account is closed permanently and cannot be recovered or reopened. We erase your name, e-mail address, phone number, date of birth, gender, password, profile photo and billing address and, for a company, the company name and GSTIN on the account; any outstanding one-time codes; our record of which birthday and anniversary messages were sent to you; the delivery log of text messages we sent to your number; your alerts, your notification choices and the language you chose; and the other contact people recorded on your account. We sign out every device and stop every device from receiving notifications; the records of past sign-ins, device registrations and device security checks are kept as security records (Section 9). Your customer record itself is retired and is no longer visible to our staff. If you delete a company account, every person on it is erased in the same way.

What is kept, and why. For each order you placed, we keep one separate record of the party that order was for. That record holds:

  • the company name and trading name, where the order was placed by a business;
  • the GSTIN / tax identification number the invoice was raised against;
  • the billing e-mail address;
  • the name, phone number and e-mail address of the contact person for the order, and of any additional contacts recorded against it, such as an accounts or site contact.

We keep this because we are legally required to. The Companies Act, 2013 and India's tax rules oblige us to retain our books of account and tax invoices, and a tax invoice is not a valid record unless it names the person or business it was issued to. An order history we could not attribute to anyone would not satisfy that obligation.

The lawful basis for keeping it is therefore compliance with a legal obligation, not your consent — which is why it survives the deletion request that removes your account. It is kept for the same period as the order it belongs to (Section 9), and is then deleted with it.

One record per order. If you placed three orders, three separate records are created, one for each. They are never merged, and each is deleted when its own order's retention period ends, so an older order's record goes before a newer one's.

Your complaints are kept too. Your support tickets, with their chat messages and attachments, stay with the service history of the machines they are about, for the period in Section 9 (to handle recurring faults, warranty and disputes). After deletion they are no longer linked to your account, but they stay linked to the order they are about, so the record we keep for that order (above) still names its contact person; what you wrote or attached in them stays as it is. The audit log entries about your actions are also kept (Section 8).

What we do NOT do with it. These records exist to satisfy our accounting and tax obligations and to answer questions about a past order — a warranty claim, a dispute, a tax audit. We do not use them to market to you, we do not use them to rebuild your account, and deleting your account unsubscribes you from every message we send.

10. Your rights (DPDP Act)

You have the right to:

  1. Access — obtain a summary of the personal data we process about you and the processing activities;
  2. Correction and completion — have inaccurate or incomplete data corrected or updated;
  3. Erasure — have personal data erased when it is no longer necessary and no legal duty requires retention. You do not have to ask us for this: you can delete your account yourself, in the app or on the web, and Section 9A sets out exactly what that erases and what we keep: the records the law requires, your complaints, and our security records;
  4. Grievance redressal — a readily available means of registering a grievance (Section 12);
  5. Nomination — nominate another individual to exercise your rights in the event of your death or incapacity;
  6. Withdraw consent at any time (Section 6);
  7. Complain to the Data Protection Board of India if you are not satisfied with our response.

To exercise any right, write to info@arceusindia.co from your registered e-mail address, or raise a ticket in the App. We may need to verify your identity before acting. We respond within the timelines prescribed under the DPDP Act and its rules.

Account deletion does not require writing to us at all — it is self-service, immediate, and described in Section 9A.

Your duties as a Data Principal: the DPDP Act also requires that you not impersonate another person, not suppress material information, and not register false or frivolous grievances.

11. Children

The App is a business/after-sales tool intended for adult customers of Arceus India. It is not directed at, and must not be used by, persons under 18 years of age, and we do not knowingly process children's personal data. If you believe a child's data has been provided to us, contact us and we will delete it.

12. Grievance Officer and contact

In accordance with the DPDP Act, the SPDI Rules and applicable IT rules, the following officer addresses privacy questions, requests and grievances:

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

We acknowledge grievances promptly and resolve them within the period prescribed under applicable rules. If you remain dissatisfied, you may approach the Data Protection Board of India.

13. Cross-border transfers

Your personal data is stored in India, on our own servers. 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's and Google's notification services, Section 7), the e-mails we send you (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, Section 4.8). 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 4.8). If we ever store your personal data outside India, this Policy will be updated first.

14. Changes to this Policy

We may update this Policy from time to time. Material changes will be notified in the App and/or to your registered contact details, with the new effective date shown at the top. Each notice says plainly what changed, and whether it is something new or a correction of how we described something we already did. Where fresh consent is legally required, we will seek it.

15. Governing law

This Policy is governed by the laws of India. Subject to applicable law, courts at Pune, Maharashtra, India shall have jurisdiction.


A copy of this Policy is available at any time from within the App and on our website. For the machine-readable summaries filed with app stores (Apple App Privacy details, Google Play Data safety), see our published store listings — they are prepared from Section 4 of this Policy.