CuroPark - Privacy Policies

Pentaminds Technologies (P) Ltd.

Version 1.6 | Updated 15 October 2026

Effective date: 01 October 2026

1. Scope and Company Roles


This Privacy Policy (“Policy”) explains how Pentaminds Technologies (P) Ltd. (“Pentaminds”, “we”, “us” or “our”) handles personal data in connection with CuroPark, including its parking-management platform, related mobile application, operational systems, website-related services where applicable, and associated technical support.

CuroPark enables organisations to manage employee parking enrolment, vehicle identification, RFID tag allocation and mapping, authorised parking access, and vehicle entry and exit records.

Radius Infotech (P) Ltd. (“Radius”) supplies and supports the solution under applicable customer arrangements. Pentaminds, a group or sister concern associated with Radius, develops and hosts the platform, administers databases, and provides authorised production support. Pentaminds and Radius are separate legal entities, and each is responsible for the personal data processing for which it determines the purposes and means.

The responsibilities of Pentaminds, Radius and the customer organisation depend on the actual activities and applicable contractual arrangements. The organisation responsible for employee enrolment, parking permissions and associated employment or facility-management purposes is referred to in this Policy as the “Customer Organisation”.

This Policy applies to CuroPark users, employees whose information is maintained in CuroPark, company administrators, authorised parking users and other individuals whose personal data is processed through the platform.

Unrelated corporate website browsing, recruitment, sales enquiries and other services not connected with CuroPark are outside the scope of this Policy and may be covered by separate privacy notices.

2. Customer Organisation and Data Processing Arrangements


CuroPark is deployed for organisations that manage employee parking and vehicle access at their premises. Depending on the deployment, the Customer Organisation may be an employer, tenant company, building owner, property developer, facility management company or another organisation authorised to manage the parking facility.

The Customer Organisation generally determines which employees may be enrolled, which vehicles may be authorised, the parking permissions to be assigned and the operational purposes for which parking records are maintained.

Pentaminds and Radius provide the technology, hosting, maintenance and support services under the applicable customer arrangements. Where they process personal data on the Customer Organisation's instructions, they do so for the authorised purposes and within the scope of those arrangements.

The Customer Organisation's responsibility for employee and parking administration is distinct from Pentaminds' responsibility for developing, hosting and supporting the platform and from Radius's responsibilities under its supply and support arrangements.

The entity responsible for a particular processing activity must be identified according to the actual deployment and applicable law. The fact that an organisation pays for the service, holds an administrator account or enters a record does not, by itself, determine its legal status.

Individuals may raise privacy concerns even if they do not have a direct commercial contract with Pentaminds or Radius.

3. How Employee and Vehicle Information Is Added


Employee information in CuroPark is entered and maintained by the Customer Organisation's authorised company administrator. Employees do not ordinarily create or directly enter their own employee records into the platform.

The standard onboarding process is as follows:

  • Pentaminds establishes the initial administrator account for the building or deployment, as applicable.

  • The authorised building administrator or other designated administrator creates or enables company accounts.

  • The Customer Organisation's company administrator enters and maintains employee details and associated parking information.

  • The company administrator enrols authorised vehicles, associates RFID tags with the relevant vehicle or employee records, and manages parking permissions according to the organisation's requirements.

  • The company administrator updates records when employee details, vehicle information, parking authorisations or employment status change, and initiates offboarding when an employee or vehicle no longer requires access.

The exact administrative workflow may vary according to the deployment configuration and the permissions assigned to each role.

Pentaminds and Radius do not ordinarily originate or manually enter employee and vehicle records. They may assist with authorised data imports, corrections or entry at the Customer Organisation's documented request.

However, hosting, storage, retrieval, automated collection, system maintenance and authorised support also constitute processing of personal data. The fact that Pentaminds and Radius do not routinely enter employee records does not remove their responsibilities under applicable law or contractual arrangements.

Employees should contact their employer or the designated company administrator to request corrections to employee, vehicle or parking-enrolment information.

4. Information Handled in CuroPark


CuroPark processes the following categories of personal data, as applicable to the deployment.

4.1 Employee and Account Information


  • Employee name.

  • Company name and associated company or organisational information.

  • Mobile number.

  • Email address.

  • Account identifiers and sign-in information, where applicable.

  • Account status and parking-enrolment status.

  • Relevant administrator assignments, roles and permissions.

Employee records are entered and maintained by the authorised company administrator. The mobile number and email address may be used for account administration, authentication, service communications and other disclosed operational purposes, depending on the configuration.

4.2 Vehicle and RFID Information


  • Vehicle registration number.

  • RFID tag identifier and associated tag details

  • Mapping between an RFID tag, vehicle, employee or parking enrolment.

  • Vehicle entry and exit records, including relevant dates and times.

  • Parking authorisation and associated operational records, where enabled.

These records support vehicle identification, parking enrolment, authorised access and parking operations.

4.3 Administrator and Operational Information


Depending on the configuration, CuroPark may process:

  • Administrator name and contact details.

  • Account roles and assigned permissions.

  • Account creation, modification, activation and deactivation records.

  • System and administrator activity logs.

  • Records of relevant access events, errors and support activities.

4.4 Support and Security Information


When a user or Customer Organisation requests technical assistance, we may process the name and contact details of the person raising the request, the issue description, relevant screenshots or diagnostic information voluntarily supplied, and the records necessary to investigate and resolve the issue.

System security logs may include IP addresses, timestamps, sign-in events, requests, errors and other technical information needed to secure, maintain and troubleshoot the platform.

Only information necessary for the relevant operational, support or security purpose should be accessed or retained.

4.5 Mobile Application Device Information


Where CuroPark is accessed through a mobile application, the application collects the following device and software details when the user signs in and when the application starts:

  • Device Unique Name.

  • System Name.

  • Device Type.

  • Brand Name.

  • Manufacturer.

  • Model Number.

  • OS Name.

  • OS Version.

  • Resolution X.

  • Resolution Y.

These fields describe the device and software environment used to access the application. A device name may include the device owner's name, and device-related information may constitute personal data when linked to an account or activity record.

In plain language:

  • Device Unique Name: The name assigned to the device, which may include the owner's name.

  • System Name and OS Name: Information identifying the operating system, such as Android or iOS.

  • Device Type, Brand Name, Manufacturer and Model Number: Information describing the hardware.

  • OS Version: The version of the device's operating system.

  • Resolution X and Resolution Y: The dimensions of the device's screen.

This information is linked to the relevant user account and is used to display screens correctly, maintain compatibility, diagnose application errors and help detect unusual sign-in activity.

Device information is accessible only to authorised Pentaminds and Radius support personnel who require it for these purposes. It is not used for advertising, profiling or cross-application tracking, and it is not sold.

These fields are collected as part of the application's operation and cannot be switched off individually. Individuals who do not wish to use the mobile application may contact their Customer Organisation to ask whether a non-app parking or access process is available.

Pentaminds determines the purposes of the device-information processing described in this subsection and is responsible for that processing. Device information is retained for six months from the date the associated user account is deactivated, subject to applicable legal retention requirements.

5. How CuroPark Displays and Protects Personal Data


The standard CuroPark operational views and reports display only the following employee and vehicle fields:

  • Employee name.

  • Company name.

  • Vehicle registration number.

Other personal information within the confirmed employee and vehicle data categories, including mobile numbers, email addresses and RFID tag details, is protected and is not displayed in these standard operational views and reports.

This limitation applies to the standard CuroPark views and reports described above. It does not mean that the underlying information is not processed or stored, nor does it override any specifically notified deployment configuration.

Authorised technical personnel may access production systems and databases when necessary for hosting, administration, maintenance, troubleshooting, security or support. Such access is restricted to authorised personnel and legitimate operational requirements.

The Customer Organisation is responsible for assigning appropriate administrator permissions and ensuring that employees and other authorised users receive access only to the information necessary for their roles.

6. Sources of Information and Purposes of Processing


CuroPark information may be obtained from the following sources:

  • Company administrators: Employee details, company information, vehicle registration numbers, RFID assignments and parking permissions.

  • Employees and authorised users: Information supplied directly for account verification, support or other permitted interactions, where applicable.

  • Parking and RFID systems: Vehicle entry and exit events, tag-related events and associated timestamps generated by configured systems.

  • System-generated records: Account activity, access events, application diagnostics, security logs and other operational information.

  • Customer Organisation and authorised service personnel: Updates, corrections, imports and administrative instructions provided through authorised processes.

A record entered by a company administrator is not, by itself, evidence that the employee has received the applicable privacy notice or given consent where consent is required. The Customer Organisation must ensure that appropriate notices and lawful processing arrangements are in place.

CuroPark information is processed for the following purposes, as applicable:

  • Employee and company enrolment in the parking system.

  • Vehicle registration and RFID tag mapping.

  • Verification of authorised vehicles and parking permissions.

  • Recording vehicle entry and exit events.

  • Managing and maintaining parking access records.

  • Administering user accounts, roles and permissions.

  • Providing application hosting, maintenance, troubleshooting and technical support

  • Detecting and investigating unauthorised access, misuse, system errors and security incidents.

  • Complying with applicable legal obligations and responding to lawful requests from competent authorities.

Pentaminds and Radius do not use CuroPark facility personal data for independent marketing or unrelated purposes. Any new or materially different purpose must be appropriately assessed, disclosed and supported by a lawful basis before processing begins.

7. Account Credentials, Cookies and Related Technical Processing


7.1 Account Credentials


CuroPark may process sign-in identifiers and, where applicable, passwords or other authentication information needed to establish and secure user accounts. Passwords and comparable credentials are handled in protected form, as appropriate to the authentication method.

Access to administrative functions is restricted according to assigned permissions and authentication requirements.

7.2 System and Security Logs


CuroPark may maintain logs relating to sign-ins, record access, administrator activities, application requests, errors and security events. Such logs help maintain the platform, investigate faults, protect accounts and support security reviews.

Access to these logs is restricted to authorised personnel for legitimate operational, security, legal or support purposes.

7.3 Website and Browser Storage


Where a CuroPark web interface or related service uses browser storage or strictly necessary cookies, these technologies may be used to maintain a session, preserve information required for a requested function or support secure access.

Such storage is not used for advertising or cross-site tracking under the current service arrangements described in this Policy.

Unrelated browsing of the corporate website, if any, may be covered by a separate website privacy notice.

8. Sharing and Disclosure of Personal Data


Personal data is shared only where necessary for the stated purposes, under applicable contractual arrangements, with appropriate authorisation or where disclosure is otherwise permitted or required by law.

8.1 Customer Organisation and Authorised Users


Employee, vehicle, RFID and parking information is made available to the Customer Organisation and its authorised administrators or operators according to the permissions configured for the deployment.

The Customer Organisation determines the operational access required for its parking activities and must ensure that such access is appropriate to the user's responsibilities.

8.2 Radius Infotech (P) Ltd.


Radius supplies and supports the CuroPark solution under applicable customer arrangements. Authorised Radius personnel may access information when necessary to perform contracted maintenance, troubleshooting or support activities.

The association between Radius and Pentaminds does not authorise either company to reuse personal data for unrelated purposes.

8.3 Cloud Hosting Provider


Amazon Web Services (AWS) provides cloud infrastructure for CuroPark hosting and backup. AWS processes or stores information as necessary to provide the contracted infrastructure services.

8.4 Other Service Providers


Depending on the enabled features, relevant service providers may receive the information necessary to perform their functions. These may include:

SMS gateway providers, where text-message authentication or notifications are enabled.

Email service providers, where email notifications are enabled.

Push-notification services, where mobile-app notifications are enabled, including Google Firebase Cloud Messaging for Android and Apple Push Notification service for iOS.

These integrations are subject to the deployment configuration. Providers should receive only the information necessary for their assigned function and be subject to appropriate contractual, confidentiality and security safeguards.

CuroPark does not currently use WhatsApp messaging, third-party advertising or marketing analytics, or payment processing as part of the parking-management service described in this Policy. Any future integration that materially changes the personal data processed will be assessed and disclosed as required before use.

8.5 Legal Disclosures and Business Reorganisation


Personal data may be disclosed to competent authorities where required by applicable law, a lawful court or regulatory order, or another valid legal process. Disclosure may also occur when necessary and lawful to establish, exercise or defend legal claims or address a specific security or legal incident.

In the event of a merger, acquisition, restructuring or transfer of the relevant business, personal data may be transferred to a successor or acquiring entity where lawful and necessary for the transaction. Appropriate safeguards and applicable legal requirements will be considered.

We do not sell CuroPark employee or vehicle personal data.

9. Notice, Consent and Individual Choices


The Customer Organisation must provide an appropriate privacy notice explaining its identity, the information collected, the purposes of processing, the relevant recipients, applicable retention arrangements and the route for raising privacy requests.

Where consent is the applicable legal basis, it must be obtained through an appropriate affirmative choice for the specified purpose. A company administrator's entry of employee information, an employee's receipt of an OTP or acceptance of general terms does not, by itself, establish consent to every possible use of that information.

Where processing is permitted on another lawful basis, the responsible organisation must identify and rely on the applicable basis and meet the relevant legal requirements.

Employees and other individuals may contact the Customer Organisation to request clarification about the information maintained in CuroPark, seek correction of inaccurate records, or raise concerns about the use of their information.

Where consent-based processing applies, individuals may withdraw their consent through the applicable privacy contact. Withdrawal does not invalidate processing lawfully completed before withdrawal.

If information is necessary for an essential parking function and can no longer lawfully be processed, the corresponding feature or access permission may need to be discontinued. The Customer Organisation should explain the impact and any available alternative arrangements.

Requests to correct employee records should ordinarily be routed through the company administrator because employees do not directly maintain their own employee records in the standard CuroPark workflow.

10. Hosting and Information Security


The current CuroPark hosting architecture uses:

  • Primary environment: AWS Mumbai, India.

  • Backup and disaster recovery: AWS Hyderabad, India.

These locations describe the primary application hosting and backup architecture. They do not, by themselves, establish the processing locations of every external service provider or optional integration.

Pentaminds applies appropriate technical and organisational safeguards to protect personal data, including access restrictions, authorised account permissions, protection of applicable personal data and restricted access to production systems and databases.

Authorised access is limited to personnel who require it for hosting, administration, maintenance, support or other legitimate purposes. Customer administrators are expected to maintain appropriate user permissions and remove access when an employee or administrator no longer requires it.

No electronic system or transmission method can guarantee absolute security. If a personal data incident occurs, Pentaminds will take appropriate response measures and coordinate with the Customer Organisation and relevant service providers to support investigation, containment, remediation and any notifications required by applicable law.

Material changes to hosting, overseas access or provider processing will be assessed against applicable law and contractual requirements and disclosed where required. This Policy does not constitute blanket consent to unrestricted international transfers.

11. Retention and Deletion


CuroPark follows an operational retention policy of six months for the categories described below, subject to applicable statutory retention requirements, documented legal holds and other lawful reasons for retaining information.

Account deactivation, termination of parking access and deletion of stored records are separate actions.

Unless a longer retention period is required by law, a court or regulatory order, an open investigation, a dispute or a legal claim, the following periods apply:

  • Employee accounts and parking-user profiles: Retained while the account is active. Following employee offboarding or account deactivation, access is stopped and the associated profile is deleted six months later.

  • Vehicle and RFID details: Retained while the relevant parking enrolment is active and deleted six months after the enrolment ends.

  • Vehicle entry and exit logs: Retained for six months from the date of the event.

  • Mobile application device information: Retained for six months from the date the associated user account is deactivated.

  • Support requests: Retained for six months after the request is closed.

  • Administrator accounts: Retained while authorised and deleted six months after deactivation.

  • System, security and administrator activity logs: Retained under the operational retention policy, subject to any applicable statutory minimum, documented legal hold or other lawful retention requirement.

When an employee leaves the Customer Organisation or no longer requires parking access, the company administrator should promptly revoke the relevant access permissions and update the account and vehicle enrolment records. The subsequent deletion of the stored profile follows the applicable retention schedule.

11.1 Statutory Retention Requirements


Applicable statutory retention requirements take precedence over shorter operational retention periods.

Where Rules 6(1)(e) and 8(3) of the Digital Personal Data Protection Rules, 2025 apply, relevant personal data and logs must be retained for the applicable required period, including the minimum one-year period measured from processing under Rule 8(3), where that requirement applies.

Records required by law must remain appropriately protected and retrievable for the permitted legal purposes and must be erased when retention is no longer justified.

The applicability of particular statutory requirements depends on the relevant provisions, commencement notifications and facts of the processing. This Policy does not represent that every provision of the Digital Personal Data Protection Act, 2023 or its Rules is already in force.

11.2 Backups


Database backups are retained for 12 months from the backup date as an archive and then expire under the backup lifecycle.

As a result, deleted information may remain in backup copies for up to 12 months after deletion from the operational system. Backup access is restricted to authorised personnel and legitimate recovery or maintenance purposes.

Backup expiry alone does not determine the statutory retention period. Where records must be retained by law, the applicable retention arrangements must be followed.

Deletion requests are assessed against legal requirements and documented needs to preserve records. Where continued retention is required, the reason and applicable period or criteria will be explained where appropriate, and access and use will be restricted accordingly.

Backup copies are removed through the documented backup lifecycle. Restoration processes should not permanently reintroduce records that are scheduled for deletion.

12. Privacy Requests and Grievances


Individuals may contact Pentaminds or the relevant Customer Organisation to ask about personal data processed through CuroPark, request access to or a summary of their information, seek correction or erasure where applicable, withdraw consent where consent is the legal basis, or raise a privacy grievance.

The available rights and the conditions for exercising them depend on the applicable law and the legal basis for the relevant processing.

For employee profile corrections, vehicle changes and parking-enrolment updates, the first point of contact is ordinarily the company administrator. For questions concerning the platform, technical processing or a privacy concern that cannot be resolved through the Customer Organisation, individuals may contact Pentaminds using the details in Section 15.

Please identify CuroPark, the relevant company or facility and the record or issue concerned. We may request proportionate verification to protect personal data, without requiring unnecessary identity documents.

Where Pentaminds or Radius processes information on the Customer Organisation's instructions, we will help route and support the request to the appropriate responsible entity.

Grievances will be acknowledged within seven days and resolved or redressed within 30 days, or within any shorter period required by applicable law. Where the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 apply, grievances will be redressed within one month of receipt.

Where applicable and in force, statutory escalation rights and prescribed grievance procedures remain available. A substantive response will explain the action taken, any lawful reason a request cannot be granted in full and the applicable escalation route.

13. Children and Individuals Requiring Representation


CuroPark is designed for organisational employee and parking management and is not intended for persons under 18 to independently register or enter into a contract through the service.

Where information relating to a child is entered into CuroPark, the Customer Organisation must ensure that the collection and use are appropriate to the stated purpose and comply with applicable child-data requirements, including obtaining verifiable parental consent where legally required, unless a specific lawful exception applies.

An administrator's entry of another person's information does not, by itself, establish parental authority or consent.

Where an individual has a lawful guardian or requires representation, applicable verification and representation requirements will be followed.

Individuals may contact the privacy contact if information concerning a child has been collected without the required process. Pentaminds will coordinate appropriate corrective action with the responsible organisation, as applicable.

14. Changes to This Policy and Applicable Law


The approved current version of this Policy will be published on the Pentaminds website at https://pentaminds.com under the title “CuroPark Privacy Policy”, together with its effective date.

Material changes will be communicated through an appropriate product, website or Customer Organisation notice where required.

If a new purpose or materially different collection of personal data is introduced, the change will be appropriately explained before the new processing begins, and fresh consent will be obtained where required by law.

Publication of an updated Policy does not retrospectively authorise new uses of personal data.

This Policy is intended to operate alongside applicable Indian privacy and information-technology laws, including the Information Technology Act, 2000, the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, and the Digital Personal Data Protection Act, 2023 and its Rules, as applicable and in force.

References to rights and obligations under the Digital Personal Data Protection Act, 2023 and its Rules are subject to their respective commencement provisions, applicable Gazette notifications and other relevant legal requirements.

15. Contact Information


Pentaminds Technologies (P) Ltd.


Registered office: E-58, Preet Vihar, Delhi – 110092, India
Corporate office: B-418, 4th Floor, I-Thum, Tower-B, Sector 62, Noida – 201301, Uttar Pradesh, India
Website: https://pentaminds.com

Data Protection and Privacy/Grievance Contact: Satyendra Kumar
Email: satyendra@pentaminds.com
Telephone: +91-9873262630

Postal privacy requests may be sent to the company office above, addressed to the Data Protection Officer.

For electronic requests, identify CuroPark, the relevant company or facility and briefly describe your concern. Please do not send unnecessary identity-document copies.

Customer Organisation: For employee details, vehicle enrolment, RFID assignments and parking permissions, contact your employer's designated company administrator or the relevant facility administrator. The Customer Organisation is responsible for providing its applicable privacy notice and contact details for matters it controls.

Radius Infotech (P) Ltd.: Where Radius supplies or supports the solution, its contact for relevant privacy matters is:

Contact: Atul Kumar Singh
Email: atul.singh@radiusinfotech.in
Telephone: +91-8130192081

Pentaminds will coordinate relevant requests with Radius and the responsible Customer Organisation, as appropriate. Individuals do not need a direct commercial contract with every party involved in the service to raise a privacy concern.