Zarokaa Privacy Policy
Last updated: 23 October 2026 | Version: 1.0
1. Introduction and Last Updated Date
1.1 About this Policy
This Policy explains how Enovate IT Outsourcing Pvt Ltd handles personal information in connection with Zarokaa, https://zarokaa.online, our mobile applications, customer accounts and support. It also explains the different responsibilities that apply when customers use Zarokaa to monitor vehicles, drivers, passengers, assets or school transport. Reading this Policy does not constitute consent to every processing activity. By accessing or using the software, you acknowledge and accept the practices described in this Policy.
Policy version 1.0, issued 23 October 2026.
Where an applicable regional notice or an organisation's monitoring notice supplies more specific information, read it alongside this Policy.
1.2 Our role
For account administration, our business contacts, billing records, service security, support administration and legal compliance, Enovate determines the purposes and means of processing and acts as a controller or data fiduciary where those concepts apply.
For telemetry, tracking histories, customer video, driver records, commands and other personal information processed to provide a customer's configured fleet service, the customer normally determines why monitoring takes place and Enovate acts as its processor or service provider. A reseller or school may have its own role depending on the arrangement. Roles depend on actual conduct, not merely contractual labels. We do not acquire ownership of an individual's privacy rights.
1.3 Responsibilities of monitoring organisations
The fleet operator, employer, school, rental business or other monitoring organisation should explain its identity, purposes, legal basis, monitoring hours, recipients, retention and rights. Direct a request concerning its monitoring first to that organisation where known. We will assist and route requests appropriately and will not refuse our own legal responsibilities simply because a customer is involved. On-premise deployments may keep operational data within the customer's environment; this Policy covers only information Enovate actually receives or accesses.
1.4 Changes to this Policy
We will update this Policy when practices or law change, identify the current version, and provide prominent or direct notice of material changes as appropriate. A notice update does not authorise incompatible new purposes or replace required consent. You may request the version relevant to your interaction by emailing support.
2. Interpretation and Definitions
[New section – not in the source document. Definitions are drawn from how each term is used in this Policy; please have them reviewed by legal before publishing.]
In this Policy, the following terms have the meanings given below:
- "Enovate", "we", "us" or "our": Enovate IT Outsourcing Pvt Ltd, the operator of Zarokaa.
- "Zarokaa" or "Service": the Zarokaa platform, the website https://zarokaa.online, our mobile applications, customer accounts and support.
- "Customer": an organisation that holds a Zarokaa account and configures the Service, such as a fleet operator, employer, school, rental business or reseller.
- "Monitoring organisation": the Customer or other organisation that decides why and how vehicles, drivers, passengers, assets or school transport are monitored.
- "User" or "you": any individual who accesses the Service, or whose personal information is processed through it, including account holders, authorised users, drivers and passengers.
- "Personal information" or "Personal Data": any information that relates to an identified or identifiable individual.
- "Customer Data": telemetry, tracking histories, video, driver records, commands and other personal information processed to provide a Customer's configured fleet service.
- "Controller" or "Data fiduciary": the party that determines the purposes and means of processing personal information.
- "Processor" or "Service provider": the party that processes personal information on behalf of, and under the instructions of, a controller.
- "Order": the agreement or order form between Enovate and a Customer, including the service settings selected under it.
- "Device": a vehicle tracker, camera, sensor, mobile device or other equipment connected to the Service.
- "Cookie": a small file or similar browser or app storage used to keep sessions, authentication or preferences.
3. Types of Data Collected
3.1 Information processed
The categories depend on the enabled features, devices and information supplied.
| Data Category | Specific Data Elements | Primary Purpose |
|---|---|---|
| Account & Business Records | Names, business email, phone numbers, role, organization, login credentials, billing details, transaction references, support correspondence. | Account setup, service delivery, billing, and identity verification. (Note: We never ask for payment card credentials via email). |
| System & Security Logs | IP addresses, device/app IDs, browser/OS details, timestamps, session telemetry, diagnostic logs, access records, and security audit trails. | System diagnostics, platform security, abuse prevention, and auditing. |
| Operational & Telemetry Data | Vehicle/device IDs, registration numbers, precise real-time & historical location, routes, speed, fuel/sensor metrics, driver scores, geofence alerts, and executed command logs. | Core fleet management, reporting, route optimization, and tracking functionality. |
| Video & School Transport Data | Live video streams, recorded clips, event timestamps, location links, passenger/student references (as supplied by the customer). | Safety monitoring and incident investigation. (Zarokaa does not provide facial recognition or audio recording). |
| AI-Generated Outputs | Summaries, driver behavior insights, and automated fleet recommendations derived from operational inputs. | Feature functionality. Enovate does NOT use customer operational data or video to train AI models. |
3.2 Sources of collection
Information comes from account holders and their users; connected devices and applications; monitoring organisations and authorised partners; interactions with our website and support; and service and security events. We may receive information about a driver or passenger indirectly from the customer rather than from that person.
3.3 Collection controls and permissions
- Permissions: Mobile app tracking depends on OS permissions granted at the device level.
- Continuous Tracking: Closing a desktop or mobile viewer application does not stop active tracking devices installed in a vehicle.
- Off-Duty Management: Monitoring organizations are required to provide clear procedures and technical configurations allowing drivers to disable or restrict tracking during off-duty or private hours.
3.4 Cookies and permissions
Zarokaa may require session or authentication storage to provide secure account access. Optional analytics, advertising or similar nonessential tracking must not be activated without the notices and choices required by applicable law. We do not use targeted advertising. Browser controls can remove or block storage, which may affect login and other requested functions. App permissions should be explained at the point of use; withdrawing a device permission may stop the associated app function without stopping a separate vehicle device.
4. Purpose of Data Collection and Legal Basis
4.1 Account and contact data
For our controller activities we use account and contact data to create and administer accounts, supply purchased services, respond to requests and communicate operational information. Where applicable, the ground is performance of a contract with the individual or steps requested before contracting. For an organisation's employees and representatives, legitimate interests in administering the business relationship may be relevant instead of their employer's contract being treated as their own.
4.2 Billing, security and audit data
We use billing and transaction information for invoicing, accounting, tax and payment administration; legal obligations and, where appropriate, contract performance apply. We process security and audit information to protect accounts, investigate abuse, maintain the service and establish or defend claims. Where recognised by the applicable law, this relies on proportionate legitimate interests, balanced against individuals' rights, or a specific legal duty. We do not treat legitimate interests as a universal legal ground in countries that do not recognise it.
4.3 Support data
We use support information to investigate a request and resolve faults, subject to appropriate access restrictions. If support requires access to operational data, that access is on the customer's behalf under its instructions, except for a separately applicable legal duty. We may process information for binding legal requests and required incident reporting.
4.4 Customer operational processing and consent
For customer operational processing, the monitoring organisation is responsible for selecting and documenting a lawful ground and providing required information. Employee consent is not assumed to be freely given merely because an employer obtains a signature. Where consent is legally required, it must be specific and valid and may be withdrawn through an appropriate process. Consent withdrawal does not retrospectively invalidate prior lawful processing. A contractual warranty does not replace the required legal ground or assessment.
4.5 What we do not do
We do not sell personal information, use it for targeted advertising or cross-context behavioural advertising, or train AI models on Customer Data. We do not use customer video for facial recognition. We do not send Customer Data to an external AI provider under the currently identified supplier arrangement.
4.6 AI outputs and driver scores
AI outputs and driver scores may be inaccurate and require human assessment. Zarokaa's terms do not authorise a customer to make solely automated employment or similarly significant decisions. Where a proposed use triggers additional assessment, notice, human-review or objection rights, those must be addressed before deployment. We do not represent that Zarokaa independently makes employment decisions for customers.
5. How Data is Shared and Third Parties
5.1 Service providers and support access
Hetzner supplies our current external hosting infrastructure in Germany. Self-hosted Nominatim provides geocoding within our infrastructure rather than through the public Nominatim endpoint. Limited authorised support staff in India may access information as necessary for a support or operational purpose. Audit logs, access restrictions and confidentiality duties apply to that access.
5.2 Customer-configured recipients, legal and business transfers
Authorised users, administrators, customer-selected partners and recipients of reports, video or alerts may receive information according to the customer's configuration. Customers are responsible for selecting recipients lawfully. We may disclose necessary information to legal or accounting advisers subject to appropriate duties, competent authorities where lawfully required, or a genuine business successor subject to safeguards and applicable notice obligations. These are possible legal or transactional disclosures, not a representation that additional technology vendors currently receive customer telemetry.
5.3 Maps and location services
Map display and location lookup are distinct activities. Where a map is loaded directly from an external tile service, that service may receive connection details and requested map areas, which may reveal locations being viewed. Applicable map attribution and service privacy information should be available in the interface. This Policy does not represent that self-hosting Nominatim also self-hosts every map component.
5.4 New providers and customer integrations
We will assess new providers, enter required agreements and update relevant information before materially changing processing. A customer's separate device, telecom, app-store or integration provider may process information under its own terms. Customers must assess those connections before enabling them.
5.5 Video access and disclosure
Video access and disclosure should be limited to authorised purposes and recipients. Customers must address recording notices, private spaces, passenger and workplace rules and the handling of requests involving other people in an image. Where a deployment cannot lawfully meet these conditions, the affected function should not be activated.
5.6 Hosting and international processing
Our current cloud hosting location is Germany and Enovate is established in India. Access by authorised support personnel in India forms part of the processing arrangement. Personal information is not represented as remaining exclusively in Germany. A separately agreed country deployment applies only once actually arranged; website availability is not a guarantee of a local server.
Where international-transfer restrictions apply, the relevant parties must establish a valid mechanism before the restricted transfer or access starts. Depending on the arrangement, this may involve an adequacy decision, applicable standard contractual clauses, a UK transfer instrument, Swiss adaptations or another legally available safeguard, together with required assessments and supplementary measures. This Policy is not itself a transfer instrument and does not state that one has already been executed for every customer.
Country-specific localisation, notification and supplier restrictions may require a different architecture or prevent activation. We do not rely on general acceptance of this Policy as blanket consent to routine restricted transfers. Contact support for information about the applicable arrangement and, where entitled, a copy of relevant safeguards with necessary confidential information protected.
6. Data Security and Retention
6.1 Security safeguards
Current safeguards include encryption, audit logs, tested backups and restricted support access. No ISO certification, universal country compliance, MFA availability or invulnerability is represented. No system is completely secure. Customers should restrict permissions, protect credentials, promptly revoke departing users and report suspected compromise.
6.2 Security incidents
We investigate suspected incidents, take proportionate containment and remediation steps, and notify customers, affected individuals and authorities where and within the periods required by applicable law and contract. Processor notifications are addressed in the customer-data processing schedule. Report concerns to support@zarokaa.online; do not send unnecessary live tracking data or credentials in the initial message.
6.3 Operational data retention
Operational tracking history is retained for the period selected in the customer's agreement, from one to twelve months. That period must be identified in the Order or service settings before collection. Video and other high-volume or sensitive features require an expressly disclosed feature-specific period rather than an assumption that every data type shares the longest tracking period. Shorter justified periods and mandatory limits take precedence.
6.4 After termination or expiry
After account termination or expiry, the customer has 30 days to request export of records still available under the agreed retention settings. This is not an extension of ordinary history retention or a recovery promise for already deleted data. After that window, operational data is deleted or returned under the customer-data processing schedule unless applicable law requires retention.
6.5 Backups
Protected backups are removed through the applicable documented rotation rather than necessarily at the instant of a live-system deletion. Until expiry, retained copies must be isolated from ordinary use and subject to the same protections; any restoration must reapply relevant deletion instructions. Customers can request the backup-deletion schedule before deployment. No instant or fixed global backup-erasure period is represented by this Policy.
6.6 Account, billing and other records
Account, billing, tax, support and security records are retained only as long as reasonably necessary for their stated purposes, binding retention duties and proportionate claim-handling needs. A legal hold may delay deletion of relevant records. Retention decisions consider the record type, statutory duties, incident investigation and limitation periods; they do not authorise indefinite operational-history storage. We can explain the applicable period or criteria in response to a request.
7. Your Data Protection Rights
7.1 Your rights
Depending on your location, our role and the applicable law, you may have rights to information, access, a copy or portability, correction, deletion, restriction, objection, consent withdrawal, and review of certain automated decisions. California and other US state laws may provide rights concerning sensitive information, sale or sharing, appeals and nondiscrimination where their scope and thresholds are met. We do not sell or share personal information for targeted advertising. We will honour legally applicable opt-out signals and requests if relevant processing is introduced, subject to the required notice and choice.
7.2 How to exercise your rights
Contact support@zarokaa.online with enough information to locate the account or monitoring organisation. We may request proportionate identity or authority verification, but will not request excessive identification. Authorised agents may act where permitted. We will respond within applicable statutory periods and explain lawful refusals, extensions or retention exceptions. Exercising rights will not result in unlawful discrimination. Necessary processing may still be required to provide a requested service.
7.3 Requests about customer-controlled monitoring
If your request concerns customer-controlled monitoring, we normally refer it securely to that customer and assist it. If the customer is unknown or unresponsive, contact us so we can assess our own obligations. A controller request will be handled directly by Enovate.
7.4 Complaints to authorities
You may complain to Enovate and to the competent authority without first completing our complaint process where law permits. Relevant authorities may include an EU/EEA supervisory authority, the UK Information Commissioner's Office, the Swiss Federal Data Protection and Information Commissioner, Russia's competent personal-data authority, the South African Information Regulator, US enforcement authorities, or the competent Indian authority as its relevant powers and provisions apply. This list does not assert that every regime applies to every person or that every Indian DPDP provision is already in force. You may ask for escalation or an available statutory appeal through the same contact address.
8. Children's Privacy
Purchasing accounts are for adults with legal capacity. A school or fleet customer's service may nevertheless process children's information. The customer must identify an appropriate legal ground, provide child-appropriate and parent/guardian information where required, obtain any required verifiable authorisation and avoid unnecessary collection. Enovate will assist with applicable processor duties and will not treat an adult account holder's acceptance as a child's consent.
9. Grievance Officer and Contact Information
9.1 Corporate identity and contact details
- Legal Entity: Enovate IT Outsourcing Pvt Ltd
- Registered Address: Office #429, Amanora Chambers, Hadapsar, Pune, Maharashtra 411028, India
- Corporate Identity Number (CIN): U72200PN2010PTC135682
- GSTIN: 27AACCE3814H1ZU
- Official Website: https://zarokaa.online
- Privacy & Legal Contact: support@zarokaa.online
9.2 How to contact us
You may contact our privacy team at the email above to submit data subject requests (access, correction, deletion, restriction, objection, consent withdrawal), file complaints, or handle general privacy and legal correspondence. Including "Privacy Request" in your subject line helps expedite handling, but it is not a formal requirement.