Evotax Staff for iOS and Android · version 1.0.6
Evotax Staff mobile app privacy policy
- Effective date:
- Last updated:
Evotax Staff is a workforce app for employees and authorised contractors of Evotax, an Indian tax practice. An Evotax administrator creates and assigns every account, and there is no public sign-up. This policy explains what the app collects about you as a staff user, and what it does with the client data you handle through it.
Our tax clients do not use this app. Clients use a separate client portal, which is covered by our website and services privacy policy.
1. Who we are
Evotax is a tax practice based in India, trading as Evotax and registered as Evo Consulting Services Private Limited. It operates the Evotax Staff app and is the data fiduciary — the controller — for the personal data described in this policy. That includes both the data we hold about you as a staff user and the client data you handle on Evotax’s behalf.
Controller identity
| Registered legal entity | Evo Consulting Services Private Limited |
|---|---|
| Registered office address | No:11, 2nd floor, 80 feet road, Koramangala 1st block, Bangalore, Karnataka, 560034, India |
| Trading name | Evotax |
| Country of establishment | India |
| info@evotaxes.com | |
| Phone | +91 901 963 5151 |
| Governing law | The Digital Personal Data Protection Act, 2023 (India). The supervisory authority is the Data Protection Board of India. |
The app this policy covers
| App name | Evotax Staff |
|---|---|
| Version this policy describes | 1.0.6 |
| Platforms | iOS and Android |
| iOS bundle identifier | com.evotaxes.mobile |
| Android package name | com.evotax.staff |
| Built with | Expo / React Native |
| Who can use it | Employees and authorised contractors of Evotax only. Accounts are created and assigned by an Evotax administrator. There is no public sign-up. |
2. Data we collect about you, the app user
This is everything the app collects about you as an Evotax staff member. There is nothing else.
| Data | What it is | Why we have it |
|---|---|---|
| Account identity | Your name, work email address, assigned role, business unit and permission set. Our server returns these to the app after you sign in. | To identify you, apply the permissions your role allows, and attribute your actions in the audit log. |
| Sign-in credentials | The email address and password you type at the login screen. They are sent to our server over TLS and checked against a stored salted hash. The password is never written to device storage. | To authenticate you. We cannot read your password; we can only check whether it matches the stored hash. |
| Session token | A signed token held in the iOS Keychain or the Android Keystore through the operating system’s secure storage API. Cleared when you sign out. | So you stay signed in between launches without re-entering your password. |
| Push notification token | An Expo push token plus the string "ios" or "android". No device name, advertising identifier or hardware identifier is sent. Deleted from our server when you sign out. | To deliver work notifications to this device. The platform string tells us which transport to use. |
| Activity records | Actions that change a record — status changes, assignments, payment approvals, messages sent — logged with your user ID and a timestamp. | Accountability and audit. A client file must show who changed what and when. |
| Technical logs (server-side) | Your IP address, the time of the request, and which endpoint was called. | Security monitoring, abuse prevention and diagnosing faults. |
3. Client data you handle through the app
The app gives you access to personal data belonging to Evotax’s tax clients. Evotax is the controller of that data. You handle it on Evotax’s behalf, and only for genuine work purposes.
| Category | What it includes |
|---|---|
| Identity and contact | Full name, phone, alternate mobile, email, date of birth, gender, marital status, lead source, free-text remarks, and the name and phone of a referring client. |
| Government identifiers | PAN and Aadhaar number. |
| Tax and financial records | Filing status and history, tax estimates, refund status, fees and payment records. |
| Documents | Form 16, Form 26AS, AIS, filing acknowledgements, ITR forms and other supporting documents the client supplied. |
| Tax portal credentials | A client’s Income Tax e-filing portal password and e-verification codes, where the client provided them so we can file on their behalf. Access is restricted by role, and every view is recorded in the audit log. |
| Internal communications | Case notes, and staff-to-staff chat with attachments. |
Your obligations as a staff user
- Access a client record only when you have a genuine work reason to. Curiosity is not a work reason. Role-based access limits what you can reach, and the audit log records what you do reach.
- Exports, downloads, screenshots and clipboard copies you create are your responsibility until you delete them. Once a file leaves the app it is outside the app’s protections, so keep it only as long as the task needs and delete it when you are done.
- Never share a client’s tax portal credentials outside the app, and never use them for anything other than the filing work the client asked for.
4. What the app does not collect or do
Each statement below was verified against the app’s source code, not assumed from a template.
- No tracking across other companies’ apps or websites. There is no advertising identifier (IDFA), no App Tracking Transparency prompt and no advertising SDK. The iOS privacy manifest declares NSPrivacyTracking: false with no tracking domains.
- No analytics or crash-reporting SDK. No Google Analytics, Firebase Analytics, Crashlytics, Sentry, Amplitude, Mixpanel or Segment. No behavioural profiling of any kind.
- Personal data is never sold. It is never shared for advertising either.
- No location, contacts, calendar or microphone access. The app never asks for any of them.
- No biometric authentication. Face ID, Touch ID and Android biometrics are not used, so no biometric data reaches the app or our servers.
- No automated decision-making with legal effect, and no profiling. Client data is not used to train machine learning models.
5. Device permissions
The app asks for each permission only when you first use the feature that needs it, never at launch. The app stays usable if you decline any of them — only that one feature is disabled. You can change your mind at any time in your device settings.
| Permission | What it is used for | If you decline |
|---|---|---|
| Notifications | Work alerts about assignments, payments and reminders. | You will not receive alerts. Everything the alert refers to is still visible in the app. |
| Camera | Photographing a client document so it can be uploaded. | You cannot photograph a document in the app. You can still upload one from files. |
| Photo library | Selecting an existing image of a document. Only the items you pick are read — the library is never scanned. | You cannot pick an image from the library. Camera and file upload still work. |
| Files and storage | Choosing documents to upload, and saving downloads and CSV exports. | You cannot upload from files or save a download or export. Viewing in the app still works. |
6. What is stored on your device
| What | Where, and for how long |
|---|---|
| Session token and selected business unit | Held in operating-system secure storage (iOS Keychain, Android Keystore). Cleared when you sign out. |
| Documents you download and CSV exports you generate | Stored in the app’s private, sandboxed storage. These files do contain client personal data, including names, PAN and phone numbers. They remain until you delete them or remove the app. |
| Progress markers for bulk operations | Record IDs and status flags only, so an interrupted bulk action can resume. |
| Everything else | Data fetched from the server is held in memory only and is gone when the app closes. |
Downloads and exports may reach your device backups
On iOS, files saved in the app’s storage may be included in device or iCloud backups. Those files can contain client names, PAN numbers and phone numbers. Use a device passcode and encrypted backups, and delete downloads and exports once you have finished with them.
7. Why we process this data
- Authenticating you and keeping you signed in.
- Applying the permissions attached to your role and business unit, so you see only what your work requires.
- Assigning, tracking and completing client tax work.
- Sending you work notifications about assignments, payments and deadlines.
- Recording who changed what and when, so a client file has a reliable history.
- Keeping the service secure, detecting abuse and diagnosing faults.
- Meeting Evotax’s own obligations as a tax practitioner, including statutory record-keeping.
We do not process any of it for advertising, for resale, or for profiling people.
8. Legal basis for processing
| Basis | What it covers |
|---|---|
| Performance of a contract | Your employment or contractor agreement with Evotax. We cannot give you a working account without processing your identity, credentials and activity records. |
| Legal obligation | Indian tax law requires us to keep books, records and filing evidence. Audit logs and client records are retained on this basis even where a person asks for erasure. |
| Legitimate interests | Securing the service, preventing misuse of client data, and maintaining an audit trail proportionate to the sensitivity of what the app holds. |
| Consent | Device permissions — notifications, camera, photo library, files. Each is requested only when you first use the feature that needs it, and you can withdraw it at any time in your device settings. |
10. International transfers
Some of the providers listed in section 9 process data outside India, in the United States and the European Union. Where that happens, the transfer is covered by the contractual protections in our agreement with that provider, which restrict the provider to processing on our instructions and require it to protect the data. We do not transfer personal data to any country that the Central Government has restricted under the DPDP Act.
11. How long we keep data
| Data | How long we keep it |
|---|---|
| Session token | Deleted from the device when you sign out, and expires on its own when the session ends. |
| Push notification token | Deleted from our server when you sign out, and replaced if you sign in again. |
| Your account identity | Kept while you are engaged by Evotax. Deleted after that on request, following the process in section 14. |
| Activity and audit records | Kept for the life of the client file they relate to. These are the record of who did what, so they are not removed when an individual account is deleted. |
| Technical server logs | Kept only for as long as they are needed for security monitoring and diagnostics, then deleted. |
| Client personal data, including PAN, Aadhaar, documents and filing records | Kept while Evotax acts for the client, and afterwards for the period Indian tax law requires books, records and filing evidence to be retained. Where a statutory retention period applies we cannot delete the record before it expires. |
| Client tax portal credentials | Deleted when the client withdraws them or the engagement ends, whichever comes first. |
| Documents and CSV exports saved on a device | They stay on that device until the person who created them deletes them, or the app is removed. |
Statutory tax record-keeping is the one thing that overrides a deletion request. As a tax practitioner Evotax must be able to produce books, records and filing evidence for the periods Indian tax law prescribes, so those records are kept until the relevant period expires even if the person concerned asks for erasure. When we act on a deletion request we tell the person exactly which records we kept and how long we must keep them.
12. Security measures and breach notification
- TLS encryption for everything in transit between the app and our servers.
- Hardware-backed secure storage for session tokens — iOS Keychain and Android Keystore, through the operating system API.
- Passwords stored only as salted hashes. We cannot read them.
- Encryption at rest for sensitive stored credentials, including client tax portal passwords.
- Role-based access control, so a staff member sees only the records their role and business unit permit.
- Audit logging of record changes and of every view of a client tax portal credential.
- Rate limiting on login attempts, to slow credential-guessing.
- Automatic sign-out when a session expires.
If there is a breach
If personal data is breached, we notify each affected person and the Data Protection Board of India, in the form and within the time the DPDP Act requires. The notice tells the affected person what happened, what data was involved, what we are doing about it, and what they can do to protect themselves.
13. Your rights under the DPDP Act
As a data principal under the Digital Personal Data Protection Act, 2023, you have the rights below.
| Right | What it means here |
|---|---|
| Access | Ask what personal data of yours we process, and get a summary of it. |
| Correction and completion | Have inaccurate or incomplete data about you corrected or completed. |
| Erasure | Ask us to delete your personal data, except where we must keep it to meet a legal obligation. |
| Information about processing | Ask which of your data we process, what we do with it, and which other data fiduciaries we have shared it with. |
| Nominating a representative | Nominate another person to exercise these rights on your behalf if you die or become incapacitated. |
| Withdrawing consent | Withdraw any consent you gave, including a device permission. Withdrawal applies from the moment you withdraw it and does not undo processing already carried out. |
To exercise any of them, email info@evotaxes.com from your work email address. We respond within 30 days. If you are not satisfied with how we handle it, you can complain to the Data Protection Board of India.
14. Account and data deletion
Accounts in this app are provisioned by an Evotax administrator, not created by the user, so there is no in-app delete button. Deletion is handled by request, and we act on every request we receive.
How to request deletion
- Email info@evotaxes.com with the subject line Account deletion request, or call +91 901 963 5151.
- We verify that the request genuinely comes from the account holder.
- We disable the account, so it can no longer sign in.
- We delete the push notification tokens and session data associated with it.
- We delete your personal data, except for records we are legally required to retain — see section 11.
- We tell you what was deleted, what was kept, why it was kept, and for how long we must keep it.
Deleting the app
Removing the app from your device deletes the files it kept locally — the session token in secure storage, and any documents or CSV exports saved in the app’s private storage. It does not delete your account or the data held on our servers, so use the request process above for that.
15. Children
This is a workplace tool for adults. It is not directed at anyone under 18, it is not available to the general public, and accounts are issued only to Evotax staff and authorised contractors. We do not knowingly collect personal data from children through this app.
16. Changes to this policy
We update this policy when the app’s data practices change. The effective date and the last updated date are both shown at the top of this page, so you can tell at a glance whether anything has moved since you last read it. For a change that materially affects you, we notify staff users directly rather than relying on you to re-read the page. This version is effective from and was last updated on .
17. Contact us
For anything about this policy, a data request, or a privacy concern:
Email: info@evotaxes.com
Phone: +91 901 963 5151
Registered entity: Evo Consulting Services Private Limited
Registered office: No:11, 2nd floor, 80 feet road, Koramangala 1st block, Bangalore, Karnataka, 560034, India
Supervisory authority: Data Protection Board of India