This Privacy Policy explains how TrackMyRMC, published on Google Play by KBADE and operated by GOLD-e Tech, collects, uses, shares, retains, and protects information when customers, drivers, plant owners, administrators, staff, and other authorised users access the TrackMyRMC website or Android application.
This page applies only to TrackMyRMC services hosted at trackmyrmc.com and the associated TrackMyRMC Android application.
1. Information We Collect
- Account and contact data: name, mobile number, email address, account role, company or RMC plant details, address, city, GST information, and authentication records.
- Order and operational data: concrete grade, quantity, delivery address, delivery pin, customer and site contacts, order status, dispatch details, vehicle and driver assignment, challans, invoices, payment status, reports, and audit records.
- Location data: approximate or precise location used for delivery pins, nearby-plant functions, navigation, and authorised live-trip tracking.
- Photos and files selected by the user: delivery proof, site photographs, profile or verification documents, challans, and other files deliberately uploaded for a TrackMyRMC feature.
- KYC information: verification status and permitted identity details supplied through an authorised DigiLocker or KYC workflow. TrackMyRMC does not intentionally store a complete Aadhaar number in its application database.
- Technical and security data: IP address, browser or device type, operating system, app version, timestamps, diagnostic logs, authentication events, security events, and feature usage.
- Communications: support enquiries, account-deletion requests, and transactional messages delivered by email, SMS, WhatsApp, push notification, or similar channels.
2. Android Permissions and Device Access
- Precise and approximate location may be used for delivery-site selection, navigation, nearby-plant discovery, and live trip visibility.
- Background location may be used only for an authorised driver or role-based tracking session while an active trip is in progress. Tracking is intended to stop when the trip or tracking workflow ends.
- Notifications may be used for OTP, account, order, dispatch, delivery, operational, and security updates.
- User-selected photos and files are accessed only when the user chooses to capture or upload content for an available feature.
Permissions can be managed in Android settings. Disabling a required permission may prevent the related TrackMyRMC feature from operating.
3. How We Use Information
- Create, authenticate, secure, and administer accounts.
- Verify eligible customers and display verification status where applicable.
- Place, approve, schedule, dispatch, track, deliver, and document RMC orders.
- Generate challans, invoices, ledgers, reports, payroll or attendance records where enabled, and operational audit trails.
- Provide map, routing, delivery coordination, and live-trip functions.
- Send transactional and security communications.
- Respond to support, correction, privacy, and account-deletion requests.
- Detect abuse, prevent fraud, investigate incidents, and enforce role-based access.
- Meet legal, tax, accounting, safety, employment, contractual, or regulatory obligations.
4. How Information Is Shared
Information may be shared only as reasonably necessary with authorised users involved in an order or operational workflow, and with service providers supporting cloud hosting, databases, storage, authentication, email, SMS, WhatsApp, push notifications, maps, navigation, KYC, monitoring, and security.
Information may also be disclosed where required by law, a court, a regulator, or a lawful authority, or where necessary to protect users, prevent harm, or establish or defend legal rights.
TrackMyRMC does not sell personal information.
5. Data Retention
Information is retained only for as long as reasonably necessary for the purposes described in this policy. Retention depends on account status, active orders, employment or business relationships, security needs, dispute resolution, and applicable legal, tax, accounting, and audit requirements.
After a verified deletion request, account access is disabled and personal account data is deleted or de-identified, except for information that must be retained for legitimate legal, accounting, fraud-prevention, safety, dispute, or audit purposes.
6. Account and Data Deletion
Users may request deletion from the account settings available inside the TrackMyRMC application. Users who cannot sign in may use the public TrackMyRMC Account Deletion Request page.
Removing the application from a device does not itself delete the account. Identity verification may be required before an account or associated personal data is deleted.
7. Privacy Choices and Rights
Subject to applicable law and identity verification, users may request access, correction, deletion, or restriction of personal information associated with their TrackMyRMC account. Android permissions can be managed through device settings.
8. Security
TrackMyRMC uses safeguards designed to protect information, including encrypted network connections, authentication controls, role-based access, restricted administrative access, secure credential handling, logging, and monitoring. No electronic system can guarantee absolute security.
9. Children's Privacy
TrackMyRMC is intended for businesses, authorised workers, and adults. It is not directed to children under 18, and children are not knowingly permitted to create accounts.
10. Third-Party Services and International Processing
Service providers may process information on infrastructure located outside the user's city, state, or country. Third-party integrations are also governed by their own privacy notices and terms.
11. Changes to This Privacy Policy
This policy may be updated when TrackMyRMC features, permissions, service providers, data practices, or legal requirements change. The effective date at the top of this page will be updated when revisions are published.