Privacy Policy

01Who this policy covers

Zaqnet is provided by RDS Corp, India. This policy explains the handling of personal information through our website and business services, including ControlRoom, GroundLink and enabled integrations. ZaqOS Levante describes the shared experience layer; it is not a separate operating system or a separate permission to collect information.

RetailPort, Satchel and other capabilities described as in development are not represented as generally available. A product name, plan entitlement or marketing example does not mean a feature is enabled for every organisation or device.

For account administration, service security, billing and enquiries, RDS Corp determines the relevant service purposes. For customer, employee and operational records entered by an organisation, that organisation generally determines why the records are processed and who can access them, and Zaqnet processes them to provide the configured service. Responsibilities depend on applicable law and the customer agreement.

02Information and why it is used

Account and organisation information includes names, contact details, user identifiers, company membership, roles and permissions. It supports sign-in, access management, support and account administration.

Business records may include customer and supplier details, orders, sales, payment records, stock assignments and movements, visits, duty and closure records, documents, notes, attachments and reports. These support the workflows your organisation uses. Do not upload personal information unrelated to that work.

Device and service information may include device identifiers, operating system, app version, IP address, push-notification tokens, connection state, request timestamps, errors and security or activity events. It supports device registration, notifications, troubleshooting and misuse prevention. Such information can identify or be linked to a user; it is not necessarily anonymous.

Location, microphone access and other device permissions are described separately below. Their use depends on the enabled feature, the platform and the relevant permissions.

03Trackboard: active and passive trail detection

Location-enabled work can process coordinates, timestamps, accuracy and available movement information, associated with the user, device, organisation and tracking session. Trackboard uses this information to display location updates, routes, visits, travel and possible halts for authorised operational review.

Active tracking obtains updates during an enabled tracking session. In the current Android implementation, the active location watch operates while the app is running in the foreground. Platform support, settings and app lifecycle affect when updates are available.

Passive trail detection uses periodic or background location collection on supported devices. On Android, an authorised native tracking session can continue when the app is not open and can resume following an app restart or device restart. Closing the app alone is not a reliable way to end passive tracking. Background collection needs the relevant device permissions and enabled tracking configuration.

Trail collection is subject to the work-duty state, organisation tracking policy, feature access and applicable consent. The service checks whether the user is on duty and whether tracking remains enabled. Ending duty, changing policy or withdrawing permission may take time to reach an offline device; a displayed location may also be the last recorded point rather than the current location.

Location samples may be temporarily queued on the device when connectivity is unavailable and sent later. A later upload time does not necessarily mean the location was collected at that time. Permission withdrawal does not itself erase previously collected records.

Routes, halts and proximity are estimates. GPS conditions, battery restrictions, network availability and operating-system behaviour can produce gaps or errors. They must not be treated as conclusive evidence of attendance, misconduct or an exact physical location without checking the underlying context.

04Location choices and organisation responsibilities

GroundLink provides a trail-detection consent flow where required, separate from the operating system’s location permission. An administrator granting access to a tracking feature is not a substitute for informing the person being tracked or obtaining any consent required by law or the feature.

You can review or revoke GroundLink’s location permission in your device settings. Use available duty and tracking controls to end an authorised work session, and contact your organisation to withdraw recorded consent or resolve a tracking concern. Contact RDS Corp using the details below if you cannot resolve a privacy request through your organisation.

Your organisation must explain the work purpose, tracking mode, applicable hours, who can view the trail and its retention arrangements before enabling tracking. It must keep access proportionate to the task. Turning off a permission can prevent location-dependent functions; it does not authorise an employer to use tracking for an unrelated purpose.

Authorised location viewing or live-follow functionality is separate from LiveLink voice calling. Access to one does not by itself authorise the other.

05X-Ray: restricted enterprise scope

X-Ray is described in the enterprise plan catalogue as consent-only and restricted to enterprise-owned devices. This policy does not authorise covert monitoring, use on personal devices, or unrestricted access to a person’s screen, files, camera or microphone.

Before any X-Ray capability is supplied or enabled, the organisation must receive and provide a feature-specific explanation of the exact information accessed, its purpose, the authorised viewers, session controls and retention. The necessary consent and device eligibility must be established separately. A general acceptance of these policies or purchase of the Eternal plan does not replace that process.

Only the capabilities actually supplied and described for the deployment may be used. No unverified X-Ray capture, recording or remote-control capability is promised by this notice.

06LiveLink voice calls

LiveLink connects authorised teammates by voice. Call setup and routing use account, organisation and device identifiers, call identifiers, participants, timestamps, call state and network connection information. Push-notification services may deliver incoming-call alerts to registered devices. Multi-device handling can indicate where a call was answered.

The microphone is used for voice media with the required permission during call setup and the call. You can decline or end a call, mute through the available controls, or revoke microphone permission in device or browser settings. Revocation can prevent calling.

Voice media uses WebRTC. A direct connection is used where available; a relay may carry media where direct connectivity fails. Connection establishment can expose network addressing information to the other endpoint and the connection infrastructure. We do not represent all calls as using a direct-only path.

The calling implementation reviewed for this notice does not include a call-recording feature. This is not a guarantee against recording by another participant or an external tool. Any future recording or transcription feature requires a separate notice, lawful basis and any required participant consent.

07Automations, reports and connected services

Automations can evaluate event data and conditions and perform supported actions, including changing business records, stock-related actions, notifications, reports or configured webhooks. Workflow definitions, execution status and related operational records may be processed to carry out and review those actions.

Your organisation chooses the workflow, its recipients and any external destinations. Reports, exports and messages can contain customer, employee or financial information. Administrators must check recipient access and minimise the information sent before enabling a flow.

Integrations and communications can involve hosting, storage, maps, payment, email, messaging, push-notification or other service providers. Those providers process the information needed for the requested service under the relevant arrangements. External services and recipient organisations may have their own policies. Do not place passwords or unnecessary sensitive information in webhook payloads or shared reports.

Where suggestions, search or Knowledge features are enabled, inputs and accessible business content may be used to generate results. Feature-specific provider and processing details must be reviewed before using sensitive material. Generated suggestions require human review and do not expand a user’s authorised access.

08Access, sharing and transfers

Organisation administrators and authorised users may access the records their roles and workspace configuration permit. Support and service personnel may handle relevant information to operate the service, investigate a problem or respond to a request. Access is not made public merely because a record exists in Zaqnet.

Information may be disclosed to service providers supporting the configured service, to recipients selected by your organisation, or where required by applicable law or necessary to address a legitimate security incident. Any business restructuring involving personal information must remain subject to applicable privacy obligations.

Hosting and third-party services can involve processing outside your country. Do not assume India-only storage or a particular residency commitment unless confirmed in your agreement. Applicable transfer restrictions and agreed safeguards govern such processing.

09Retention, deletion and security

Retention depends on the record type, the work purpose, customer instructions, the service agreement and applicable legal requirements. Business and accounting records, trails, call metadata, logs and backups may have different retention needs. There is no single retention period promised for every feature.

Ask your organisation or RDS Corp for the arrangements applying to your workspace, especially for tracking and enterprise monitoring. Deleting an account, removing a permission or ending a subscription does not automatically delete records your organisation must lawfully keep. Deletion requests may require identity checks and an assessment of those obligations.

Deleted information may remain in restricted backup or recovery systems until the relevant lifecycle completes, and copies previously exported by your organisation are outside the application’s deletion controls. We do not promise immediate erasure from every backup or recipient system.

Service safeguards include authentication, authorisation and security controls appropriate to the deployment. No system is risk-free. Report suspected unauthorised access promptly. Incident investigation and notifications are handled in accordance with the applicable obligations and customer arrangements; this notice is not a security certification.

10Your requests and choices

Contact your organisation about access to work records, correction, retention, tracking settings or a work-related privacy complaint. You can also contact RDS Corp directly to request information, correction or deletion, withdraw consent where processing relies on it, or raise a grievance. We may need enough information to verify the request and identify the relevant workspace; never send your password.

We handle requests in accordance with applicable law, including any rights of access, correction, erasure, grievance redressal or nomination as and when applicable. Some records may need to be retained for a lawful purpose. We will explain relevant limitations rather than promise unrestricted self-service deletion.

If a complaint remains unresolved, you may use the remedies available under applicable law. Indian data-protection provisions have phased commencement dates; this policy does not represent that every future statutory procedure is already available.

11Website storage, children and updates

The website and apps may use cookies, browser storage and device storage for sign-in, preferences, drafts, cached work and service operation. Clearing storage can sign you out or remove local drafts. Third-party pages or embedded services may use their own storage practices. The website includes Vercel Web Analytics and Speed Insights to measure page visits and performance when enabled in the deployment. This can involve page and referrer information, browser or device characteristics and performance measurements. Vercel describes Web Analytics as cookie-free; this does not mean the website or its hosting infrastructure processes no technical information. Additional marketing technologies require appropriate disclosure and choices.

The services are intended for authorised adult business users, not children under 18. Do not create a child’s account or use the services to monitor children. Contact us if such information has been supplied in error.

We will update this page when practices or features change and provide additional notice where required. A revised policy does not retroactively authorise a new monitoring purpose or replace a required feature-specific consent.

12Contact RDS Corp

For privacy requests, grievances or questions about the service, contact our support team and identify the relevant organisation and feature. Do not include passwords or unnecessary sensitive information.

Read the Terms of Use