Privacy Policy
Shrevin Global Technologies Private Limited, operating under the brand name ManaMeter ("we," "us," "our"), operates the ManaMeter Rider mobile application, the ManaMeter Partner (Driver) mobile application, and the ManaMeter Ops dashboard (collectively, the "Platform"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Platform.
Before creating an account, and again when this Policy changes materially, you will be shown a concise notice describing the personal data we process and why. You must take an affirmative action to accept the applicable Terms and consent to the processing described in this Policy. Existing users are also asked to review the current version. You may withdraw consent from the privacy controls in the app or contact us as described in Section 6.6. If you do not consent, you cannot continue using features that require that processing.
1. Information We Collect
1.1 Information You Provide Directly
Rider Account Information:
- Phone number (used for account creation and authentication via OTP)
- Full name
- An affirmation that you are at least 18 years old; we do not require your date of birth
Driver Account Information:
- Phone number (used for account creation and authentication via OTP)
- Full name
- City of operation
- Vehicle type (Bike or Auto)
- Vehicle registration number
- Driving license number
- Vehicle registration certificate (RC) number
- Insurance expiry date
- Photographs/scans of driving license, RC, and insurance documents (captured via camera or selected from photo library, uploaded to our servers)
- Portrait photograph (partner photo) for identity verification, displayed to Riders during active rides
- Vehicle front photograph showing the vehicle and registration plate
Emergency Contacts (Riders only):
- Name and phone number of persons you designate as emergency contacts
Referral Information:
- Referral codes you generate or enter
- Referral credit balances
Ratings and Feedback:
- Star ratings (1-5) you provide for rides
- Text feedback you submit after rides
WhatsApp Booking and Support Information:
- Your WhatsApp phone number, selected language, conversation state, and messages or button selections
- Pickup and drop-off locations or Google Maps links you submit through WhatsApp
- For parcel bookings, sender and receiver names and phone numbers, payment responsibility, and parcel notes
- Support requests and associated ride, vehicle, timestamp, role, and issue information
1.2 Information Collected Automatically
Location Information:
- Riders: We collect your precise location when you use the app to set a pickup point. Location is collected only when you actively use the app (foreground). We do not track rider location in the background.
- Drivers: We collect and update your precise location while you choose to remain online and while you have an active ride, including when the Partner app is in the background or the phone is locked. Update frequency varies based on ride state, movement, device conditions, and dispatch configuration. We use this data for availability, ride matching, pickup distance, navigation and route display, live tracking, arrival/completion checks, safety, support, and fraud prevention. Going offline stops dispatch-related background location processing, subject to an active ride or a short technical shutdown period.
Device Information:
- Firebase Cloud Messaging (FCM) device token for push notifications
- Device operating system (Android or iOS)
- App version, build number, selected language, and permission/notification state used for compatibility and reliability
Crash and Diagnostics Data:
- App crash logs, stack traces, and device state at the time of a crash, collected via Firebase Crashlytics (a Google LLC product). This data may include device model, operating system version, and app version. It is used solely for identifying and fixing bugs.
Ride Information (created automatically during each ride):
- Pickup and drop-off addresses and coordinates
- Ride status and timestamps (requested, assigned, in-progress, completed, cancelled)
- Fare estimate and final fare
- Payment method chosen (Cash or UPI)
- Route polyline (encoded map route)
- One-time passwords (OTPs) generated for ride start verification and parcel drop-off verification (temporary, cleared after use)
- Quick messages exchanged between Rider and Driver during the ride (message content, sender, timestamp)
- Rider cancellation reason, if provided
- Driver cancellation reason and rolling cancellation/block status
- Optional rider-selected priority amount, waiting charges, night fare, parcel charges, platform fee, referral credit, incentives, and fare breakdown components where applicable
- Live tracking link token and expiry, and SOS activation records when those safety features are used
Service Balance and Incentive Data (Drivers only):
- Service balance amount and top-up transaction history
- Razorpay order, payment-link, payment, reference, signature-verification, and status metadata for Partner service-balance top-ups; ManaMeter does not receive your card number, UPI PIN, or banking credentials
- Incentive program progress (ride counts toward targets, qualification status, reward amounts, settlement records)
Usage Data:
- Active ride IDs stored locally on your device for session continuity
- Authentication request, provider, delivery status, verification attempt, rate-limit, and security logs
- Versioned Terms and Privacy acceptance or withdrawal evidence, including time, role, language, app/build version, document hashes, and authentication metadata
1.3 Information We Do NOT Collect
- Credit card, debit card, or bank account numbers entered into Razorpay or a payment app; those providers process payment credentials under their own terms
- UPI PINs
- Biometric data
- Contacts or address book (beyond emergency contacts you voluntarily add)
- Call logs, SMS content, or browsing history
- Photos, videos, or media from your device (beyond documents, portrait, and vehicle photographs drivers voluntarily upload during onboarding)
2. How We Use Your Information
We use the information we collect for the following purposes:
| Purpose | Data Used |
|---|---|
| Account creation and authentication | Phone number, WhatsApp or SMS OTP delivery, Firebase identity, verification and abuse-prevention logs |
| Ride matching and dispatch | Rider location, driver location, vehicle type, driver availability |
| Live ride tracking and safety | Driver real-time location, ride details, expiring tracking link, SOS activation and support records |
| Fare calculation | Pickup/drop coordinates, route distance, pricing configuration, ride state, waiting time, applicable charges and optional priority amount |
| Ride payment facilitation | Payment method preference (Cash/UPI). Ride fare is paid to the Driver; ManaMeter does not receive your UPI PIN or payment-account credentials |
| Partner service-balance top-ups | Top-up amount and Razorpay order/payment metadata used to create, verify, reconcile, and credit a top-up |
| Push notifications | FCM device token; ride status updates, driver assignment alerts |
| Safety and verification | Ride start OTP, parcel drop OTP, driver document verification |
| Quality and trust | Ratings and feedback to compute aggregate scores for riders and drivers |
| Emergency contacts | Stored for your use; we do not contact them proactively |
| Referral program | Referral codes and credit tracking |
| In-ride messaging | Quick message content, used for ride coordination between Rider and Driver |
| Service balance management | Balance amounts, top-up transactions, platform fee deductions |
| Incentive programs | Ride counts, qualification tracking, reward settlement |
| Customer support | Ride history, status logs, messages, and user information to resolve disputes |
| WhatsApp booking and communication | Phone number, language, conversation state, booking details, locations, parcel contacts, ride status, and support messages |
| Consent management | Document versions and hashes, acceptance/withdrawal action, timestamp, role, language, platform and app/build metadata |
| Legal compliance | Audit logs, ride records as required by applicable law |
| Bug fixes and stability | Crash logs and diagnostics via Firebase Crashlytics |
We do not use your information for:
- Selling to third-party advertisers
- Behavioural profiling or targeted advertising
- Automated decision-making that produces legal effects without human review
3. How We Share Your Information
3.1 Between Riders and Drivers
During an active ride, we share limited information between riders and drivers to facilitate the service:
| Data | Shared With Rider | Shared With Driver |
|---|---|---|
| Name | Driver's name | Rider's name (via ride record) |
| Phone number | Driver's phone number | Rider's phone number |
| Vehicle details | Driver's vehicle type and number | N/A |
| Location | Driver's real-time location during ride | Pickup and drop-off locations |
| Aggregate rating | Driver's average rating | Rider's average rating |
| Payment method | N/A | Rider's chosen payment method |
| Quick messages | Driver's messages | Rider's messages |
3.2 With Service Providers
We use the following third-party services to operate the Platform:
| Service Provider | Purpose | Data Shared |
|---|---|---|
| Google Firebase (Google LLC) | Authentication, database (Cloud Firestore), cloud functions, push notifications (FCM) | Phone number, user profile data, ride data, FCM tokens |
| Google Cloud Storage / Firebase Storage (Google LLC) | Storage of driver onboarding documents (photographs of license, RC, insurance) | Driver document images, accessible only to the uploading driver and ManaMeter operations staff |
| Firebase Crashlytics (Google LLC) | Crash reporting and app diagnostics | Crash logs, device model, OS version, app version, stack traces |
| Google Maps Platform (Google LLC) | Map display, geocoding, route rendering | Location coordinates, addresses |
| Meta WhatsApp Cloud API (Meta Platforms, Inc.) | Login OTP delivery, ride/parcel booking, interactive messages, status updates, location exchange, and support | Phone number, language, OTP template variables, messages and selections, booking and ride details, locations, parcel contact details, and support content |
| MSG91 / Walkover | SMS OTP fallback and, where configured, messaging delivery | Phone number, OTP/template variables, delivery identifiers and status |
| Razorpay | Partner service-balance top-up checkout and payment verification | Top-up amount, phone/contact details where provided, order/payment/reference identifiers, and transaction status. Payment credentials are collected by Razorpay, not ManaMeter. |
These providers process data under their own privacy terms and the contracts or platform terms applicable to our use of their services. Our primary Firestore and Cloud Storage resources are configured in India where stated below, but Meta, MSG91, Razorpay, Google, device manufacturers, and telecommunications networks may process data in India or other locations where they operate. We assess and apply contractual, security, and legal safeguards appropriate to each provider and applicable law.
3.3 With Authorities
We may disclose your information if required to do so by law or in response to valid requests by public authorities (e.g., a court order, government agency, or law enforcement request).
3.4 In Business Transfers
If we are involved in a merger, acquisition, or sale of all or a portion of our assets, your information may be transferred as part of that transaction. We will notify you of any such change.
3.5 We Do NOT
- Sell your personal information to any third party
- Share your information with advertisers
- Provide your information to data brokers
4. Data Storage and Security
4.1 Where We Store Data
Our primary application database and driver-document storage use Google Firebase and Google Cloud resources configured in Asia South 1 (Mumbai, India). Some supporting services, including authentication, messaging, maps, crash reporting, payment processing, telecommunications, and provider logs, may process or retain data in other regions according to the provider's infrastructure and legal requirements. Data is protected in transit using TLS where supported and at rest using the safeguards supplied by the relevant provider.
4.2 Local Device Storage
We store minimal data on your device:
- Active and recent ride IDs (for session continuity)
- App language preference
- Online intent, permission-prompt state, notification preferences, and limited cached ride/offer information needed for continuity
- Authentication session tokens managed by the operating system and Firebase SDK
4.3 Security Measures
- All data transmitted between the app and our servers is encrypted using TLS (Transport Layer Security)
- Data at rest is encrypted by Google Firebase and Google Cloud Storage
- Access to user data is restricted through Firebase Security Rules
- Driver documents in Cloud Storage are accessible only to the uploading driver and authorized ManaMeter operations personnel
- Administrative access (Ops) is limited to authorized personnel; sensitive administrative actions and legal acceptance records are logged and protected from ordinary client modification
- OTPs for ride verification are single-use and cleared after verification
- FCM tokens are cleared on user sign-out to prevent misdirected notifications
4.4 What We Cannot Guarantee
While we implement industry-standard security measures, no method of electronic storage or transmission over the Internet is 100% secure. We cannot guarantee absolute security of your data.
5. Data Retention
| Data Type | Retention Period |
|---|---|
| Account information (name, phone, age affirmation) | While the applicable Rider or Partner account remains active, then deleted or restricted when you delete the role profile, withdraw consent, or request erasure, except data retained for a documented legal, safety, fraud, dispute, or transaction-record purpose |
| Ride and parcel records (participants, pickup, drop, fare, status, timestamps) | Up to 7 years where reasonably necessary for transaction, tax, accounting, safety, fraud, complaint, or legal-record purposes; identifiers are removed or access restricted when they are no longer necessary |
| Driver location and route data associated with a ride | Retained with the related ride record where necessary for live tracking, fare verification, safety, support, dispute, fraud, or legal purposes |
| Driver idle location (driver_state) | Overwritten continuously; only latest location retained |
| Ratings and feedback | 3 years from the date of the ride, or until account deletion, whichever is later |
| Emergency contacts | Until you remove them or delete your account |
| Driver onboarding documents | For the active Partner relationship and thereafter only as long as needed for verification, regulatory, safety, fraud, dispute, or legal obligations; deletion requests are applied subject to those obligations |
| FCM tokens | Overwritten on each new session; cleared on sign-out |
| Quick messages | Retained as part of ride records (7 years) |
| Service balance and top-up records | 7 years from the transaction date, as required for financial and tax compliance |
| Incentive progress and reward records | 7 years from the incentive settlement date, as required for financial compliance |
| Driver portrait and vehicle photographs | Retained for the duration of the driver's active account plus 3 years after account closure |
| Referral data | 3 years from the referral event or account closure, whichever is later |
| Audit logs (Ops actions) | 7 years, as required for regulatory and legal compliance |
| OTP and authentication security logs | For the shortest operational period required for delivery, rate limiting, fraud prevention, troubleshooting, and security investigations, then deleted or aggregated unless a longer legal or security hold applies |
| WhatsApp booking sessions and message logs | For booking continuity, support, fraud prevention, and dispute handling; ride/parcel details incorporated into a completed booking may follow the ride-record period |
| Support tickets and safety/SOS records | For the duration needed to resolve the matter and for subsequent safety, fraud, dispute, or legal obligations |
| Razorpay top-up and payment metadata | Up to 7 years where required for reconciliation, accounting, tax, dispute, fraud, or legal obligations |
| Terms, Privacy and consent evidence | For the account relationship and thereafter for the period reasonably necessary to establish notice, consent, withdrawal, contractual, complaint, and legal compliance history |
| Crash logs (Crashlytics) | 90 days (managed by Firebase Crashlytics) |
After the applicable retention period, personal data is either deleted or anonymized so that it can no longer be associated with you.
6. Your Rights and Choices
As a Data Principal under the Digital Personal Data Protection Act, 2023, you have the following rights:
6.1 Right to Access
You may request a summary of the personal data we hold about you and the processing activities associated with it by contacting us at support@manameter.com. We will respond within 30 days of receiving a verified request.
6.2 Right to Correction
You may view and update supported profile information, including your name, through the app. For corrections to other data, contact us at support@manameter.com.
6.3 Right to Erasure (Account Deletion)
Riders may initiate deletion from the Rider app profile. Riders and Partners may also contact support@manameter.com. Rider and Partner are separate role profiles that may share one Firebase authentication identity when the same phone number is used. Deleting one role does not automatically delete the other role or the shared authentication identity if it remains necessary for the other role. Upon a verified deletion request:
- The applicable role profile, current state, and role-specific optional data are deleted or disabled unless retention is required for a documented purpose
- Historical ride, parcel, payment, safety, support, fraud, and legal records may retain a restricted or pseudonymous account identifier while needed for the purposes listed in Section 5
- Partner earnings, service-balance, top-up, incentive, onboarding, and regulatory records are deleted or retained according to Section 5 and applicable obligations
- Consent and withdrawal evidence is retained as a protected compliance record
6.4 Requesting a Copy of Your Data
Where available, you may request a copy of your personal data in a commonly used format by contacting support@manameter.com. This is offered subject to identity verification, the rights of other persons, technical feasibility, and applicable law.
6.5 Right to Nominate
You may nominate another individual to exercise your rights under this policy in the event of your death or incapacity, by submitting a written nomination to support@manameter.com.
6.6 Right to Withdraw Consent
You may withdraw consent using Profile > Privacy and consent > Withdraw consent in either app, or by contacting support@manameter.com. Withdrawal is blocked during an active ride so it cannot interrupt an ongoing safety or transaction flow. Upon withdrawal:
- We will cease processing your data for purposes that rely on consent
- Withdrawal does not affect the lawfulness of processing carried out before the withdrawal
- If consent is required for core Platform functionality, withdrawal may result in your inability to use the Platform
- Partners are taken offline and cannot receive new ride requests unless they later review and accept the then-current documents
- Data that must be retained for a transaction already requested, legal compliance, safety, fraud prevention, dispute resolution, or establishment of consent history may continue to be processed for that limited purpose
6.7 Location Permissions
- Riders: You may deny location permission. The app will function with reduced features (you will need to manually enter pickup locations).
- Drivers: Location permission is required to use the Partner app. You may revoke location permission at any time through your device settings, but you will be unable to go online and receive ride requests.
6.8 Push Notifications
- You may disable push notifications through your device settings. This may result in delayed awareness of ride status updates.
- The Partner app may use high-priority or full-screen notifications with a custom alert sound for incoming ride requests where Android, device settings, and permissions allow. Silent mode, Do Not Disturb, battery restrictions, manufacturer settings, or revoked permissions may suppress or delay an alert.
6.9 Emergency Contacts
You may add, edit, or remove emergency contacts at any time through the app.
6.10 Camera and Photo Library Access (Drivers Only)
The Partner app requests access to your device camera and photo library for the purpose of capturing or selecting photographs of your driving documents (license, RC, insurance), your portrait photo, and a vehicle front photo during onboarding. You may deny this permission; however, you will be unable to upload required documents and complete the onboarding process.
7. Data Breach Notification
In the event of a personal data breach that is likely to cause harm to you, we will:
- Notify the Data Protection Board of India in the form and manner prescribed under the Digital Personal Data Protection Act, 2023
- Notify affected Data Principals (users) as soon as reasonably practicable, with details of the nature of the breach and recommended protective actions
- Take immediate steps to contain and remediate the breach
8. Children's Privacy
The Platform is not intended for use by anyone under the age of 18. We do not knowingly collect personal information from children under 18. If we learn that we have collected personal information from a child under 18, we will take steps to delete that information promptly.
9. Third-Party Links and Services
When a UPI option is available, the app may launch a UPI application or Razorpay checkout. WhatsApp may be used for login OTP delivery, booking, ride updates, location exchange, and support. Google Maps links, live-tracking links, payment pages, and other external services are governed by the relevant provider's terms and privacy practices. Review those policies before using the external service.
10. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will notify you of any material changes by:
- Posting the updated policy within the app
- Updating the "Last Updated" date at the top of this policy
For a material change affecting the data or purposes described here, we may require an explicit, versioned review and affirmative acceptance before further use. An active ride will not be interrupted solely to display the review; the request will be deferred to a safe point.
11. Grievance Officer
In accordance with the Information Technology Act, 2000 and the rules made thereunder, the Grievance Officer for the purpose of this Privacy Policy is:
Name: Sandeep Nethi
Email: support@manameter.com
Address: Hyderabad, Telangana, India
The Grievance Officer shall address any complaints or concerns regarding the processing of personal data within 30 days of receipt. If you are not satisfied with the resolution, you may approach the Data Protection Board of India or the appropriate Consumer Disputes Redressal Commission.
12. Applicable Law
This Privacy Policy is governed by the laws of India, including but not limited to:
- Information Technology Act, 2000
- Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011
- Digital Personal Data Protection Act, 2023 (as applicable and notified)
13. Contact Us
If you have any questions or concerns about this Privacy Policy, please contact us at:
Email: support@manameter.com
Address: Hyderabad, Telangana, India