Privacy Policy

About CabNexus and this policy

CabNexus is a product of SoftDots Technologies. This policy covers this public website, the fleet management workspace and CabNexus Driver. For privacy requests and business enquiries, contact support@softdots.in and identify the website, account or fleet record concerned.

CabNexus Driver is a sign-in-only app using employer-provisioned accounts. Drivers cannot register or follow an account-creation link from the app; the employer supplies initial access. The employer determines work authorisation, assignments and many employment, passenger and financial records, and must provide appropriate notices. SoftDots product ownership does not replace the employer’s responsibilities or establish every contractual or legal processing role.

Current NANUAN’S deployment

The current CabNexus Driver deployment is for authorised employees of NANUAN’S, Mohali, Punjab, India. These drivers work for NANUAN’S only. This deployment does not support one employee account holding separate access for multiple employers.

NANUAN’S business address is Plot No. 1060, JLPL Industrial Area, Sector 82, Mohali, Punjab, 160062, India. Its business contacts are info@nanuantravels.com and +91 9216800617 / +91 9216610617; its website is www.nanuantravels.com.

For CabNexus privacy requests, including requests from former employees, use support@softdots.in. The NANUAN’S details above identify the employer’s general business contacts; they do not designate that mailbox as a privacy officer or DPO. SoftDots and NANUAN’S coordinate the records and responsibilities relevant to your request.

Account, fleet and operational information

Account and fleet records can include names, usernames, user and driver identifiers, email addresses, telephone numbers and addresses. Authorised administrators can provision accounts and maintain licence details, employment information, vehicles, shifts and assignments.

Bookings and duties can contain passenger contact details, pickup and drop-off addresses, routes, times, corporate contacts and billing information. Expenses, collections, allowances, reimbursements and settlements can include amounts, payment modes and supporting evidence. Only provide information needed for the work and that you are authorised to supply.

Absence or emergency reasons and free-text notes may reveal personal or health information if you include it. Avoid unnecessary health details or information about another person.

Location, photos and extraction

Supported attendance, odometer and duty submissions can include the location at capture, accuracy and capture time. Location is used to verify the relevant work record. The driver capture flow requests foreground location for the action you choose; continuous background tracking is not part of that capture flow. Attendance capture requires location. Odometer photo submission can proceed without coordinates when location is unavailable or declined. Earlier app versions can differ; review the access shown in device settings.

Camera or selected photos can be used for odometer readings and fuel receipts. Uploaded images, extracted readings, receipt details and review results can be stored with the relevant record. OCR can be wrong and should be checked against the original evidence. Declining a permission or upload prevents the related capture or extraction; ask the fleet about an alternative supported process.

For an odometer photo, the driver app checks the original capture evidence and prepares a separate upload image without embedded location or device metadata. Coordinates you permit for that submission are sent separately. This does not remove the original photo from your device, erase historical uploads or guarantee removal of temporary files. Other photo-upload workflows can behave differently.

Location permission and a map handoff are separate actions. When a configured map or routing feature is used, addresses or coordinates can be sent to the relevant map provider. Opening directions or calling a passenger also passes the selected destination or telephone number to the service you choose.

Devices, authentication and notifications

Authentication records support account access. Attendance records can contain device or installation identifiers, app version, platform, time zone and IP address. API and hosting systems can produce network, security and error logs containing IP addresses and request metadata.

Firebase Cloud Messaging delivers enabled work notifications using a device notification token and notification payload. In the driver app, Profile explains this purpose before you choose to enable notifications; the app then requests device permission and registers the token for the signed-in account. The app saves that choice and a cached registration on the device. Native Firebase components and, on Apple devices, Apple Push Notification service registration can initialize at startup before this app-controlled choice. The notification prompt does not mean all provider processing waits for permission.

Signing out removes the app’s saved notification choice, cached token and in-app notification history, and attempts to revoke the current registration. A local storage failure can prevent removal; the app shows a cleanup warning in that case. Network or provider failures can leave registration revocation unconfirmed. This does not delete the Firebase installation, provider-held copies or server-side work records. Other local drafts, preferences and temporary files follow their own clearing behavior. Signing out or disabling notifications is different from permanent account deletion. The Cookie Policy describes the public website and fleet browser workspace.

Processing services and recipients

The public website is served as static files and uses locally hosted website assets. Fleet records are processed by the CabNexus backend and its database. Uploaded documents use the fleet’s configured server or cloud storage; stored files are separate from the database record.

When document extraction is enabled, processing may take place on the server or through an external extraction service, which receives the relevant image content. Firebase Cloud Messaging and, on Apple devices, Apple Push Notification service support work notifications. These services receive the information needed for their feature.

Address search and routing can use Ola Maps; browser route views can request OpenStreetMap tiles. When the employer enables email, SMS or WhatsApp messages, the selected delivery service processes the contact and message information needed for delivery. Configuration varies by fleet deployment; contact support@softdots.in for the storage, extraction and delivery services that apply to your records. Naming a supported feature does not mean that every optional service is active.

The driver app uses Google Fonts to load its interface font when it is not available locally. This can send a font request and ordinary network information to Google. Following an external website, maps or phone link invokes that service’s own practices. Data may also be disclosed where a valid legal obligation requires it. Provider names do not establish a storage region, backup expiry or permission to use information for advertising.

Retention of account and work records

When an employee leaves, the employer retains the employee record and linked historical trips, duties, attendance, allowances, expenses, reimbursements and settlements to maintain accurate operational and financial history. These links support reconciliation, reporting, audits and dispute handling. Removing an employee record could detach employment details from that history; retention must still have a relevant accounting, employment, legal or documented operational purpose.

GST-covered invoices and supporting records may need to remain after departure or account closure. The Data Policy explains the 72-month rule measured from the relevant annual-return due date and the extensions for specified proceedings. This applies to covered records and does not require an active login account.

Employment status, operational availability and application login are separate controls. Active means currently employed; inactive means a former employee, with leaving date and reason recording departure. Marking the employee inactive, recording leaving details or changing operational availability does not automatically enable, disable or reset the linked login.

Operational availability is recorded as “Record enabled for operational use”. In the assignment workflows, a disabled employee record blocks creation of a driver profile and new taxi assignments or booking allocations, including replacements and reallocations. The current employee state is checked when an assignment is submitted. Enabling the setting does not grant application login or bypass other driver, vehicle and scheduling checks.

Changing operational availability does not automatically cancel or reassign existing or scheduled work. The employer must review that work and arrange any necessary reassignment. Authorised users can release work, reassign it away from the employee or complete existing work under the usual permissions and work controls. These actions do not delete the employee record or historical transactions.

An authorised administrator must separately disable application login when access is no longer permitted. In the workflow, explicit offboarding rejects sign-in and protected requests on their next server check, invalidates existing credentials and recorded sessions, and clears the current push registration. Offline devices learn about the restriction when they reconnect. Rehire requires separate authorisation and fresh credentials; changing an HR field does not restore old sessions.

Historical transactions and their supporting personal data require separate necessity reviews. Photos, receipts, OCR results, precise coordinates, device identifiers, authentication tokens and unrelated personal details are not automatically kept indefinitely because an employment or financial record remains. Review considers unresolved verification, corrections, settlement, specific disputes and any documented obligation for the particular information.

There is no single automatic purge period for all categories. Retention needs a documented reason and an end date or measurable review criterion. A minimal protected request record can document the outcome and help prevent restoration of information approved for removal. Automatic erasure is not enabled as part of the current request service. Changing employment status, disabling operational use or login, signing out and uninstalling do not delete historical records or establish permanent deletion.

Your choices, requests and security

Current and former employees can request access, correction, retention information, deletion or anonymisation where applicable, and review of a refusal or retention exception at support@softdots.in. Use proportionate identity verification; do not send credentials, private status codes or unnecessary documents. SoftDots and the employer coordinate record ownership and specific obligations without giving an administrator a blanket veto over lawful requests. The Employee Accounts & Privacy Requests page explains employer provisioning, offboarding, permanent-deletion controls, external requests, timing limits and status after sign-in ends.

Protected features use authentication and permissions. Their protection also depends on the deployment’s server, document-storage and device configuration; no online service guarantees absolute security. Report suspected misuse or disclosure to support@softdots.in without sending passwords or unrelated personal documents.

Children and updates

CabNexus Driver is intended for authorised employees carrying out fleet work. It is not open to public driver registration or intended for children. Administrators should provide appropriate access and avoid uploading unnecessary information about children.

The date on this page identifies the version you are reading. Review changes alongside your fleet’s notices and the app’s permission disclosures. A change in providers or collection practices needs corresponding notices and, where required, permission before that processing begins.