Privacy Policy

Introduction

This Privacy Policy explains how Viviax Technologies Private Limited ("we", "us", "our"), the operator of the PikMeGo ride-hailing platform, handles personal information when you use our apps, our website and our support channels.

PikMeGo exists to connect passengers with drivers. Doing that requires knowing where you are, where you want to go, who is driving you and how the trip was paid for. This document sets out exactly what that means in practice: what is collected, why it is needed, who else sees it, how long it is kept and what you can ask us to do about it.

Please read it alongside our Terms & Conditions, which govern your use of the platform, and our Cookie Policy, which covers this website.

Who and what this covers

This policy applies to:

• Riders who use the PikMeGo app to book rides.
• Drivers who use the PikMeGo Dost app to receive and complete rides.
• Visitors to this website.
• Anyone who contacts our support channels, including people who do not hold an account — for example, someone following a shared trip link, or a person reporting an incident.

It does not cover what a driver, a fleet operator or any other third party does with information independently of us, or sites and services we link to but do not run.

Information we collect

We collect information you give us, information generated by using the service, and a small amount of technical information from your device. Each category below says what it is and why it exists.

Account information

Your mobile number is the account. You sign in by entering it and confirming a one-time password we send you, so the number is both your identifier and your authentication. We also hold your name, an email address if you provide one, and a profile photo where you add one.

Identity and eligibility information (drivers)

Drivers submit documents that let us verify who they are and that they are permitted to drive commercially: an identity proof, a driving licence, and — where the city or the operator requires it — an address proof and police verification. These are reviewed by our operations team before an account can take a ride.

Vehicle information (drivers)

The vehicle's registration details and its supporting documents: registration certificate, insurance, permit, and where required a fitness certificate, pollution certificate and photographs of the vehicle. We track their expiry dates so a lapsed document does not stay on the road.

Financial information (drivers and fleet operators)

Bank account details for paying out earnings, and the settlement records that show what was paid and for which trips.

Location information

Location is the part of this policy worth reading closely.

• Riders: your device location is used to place your pickup and to show the trip on a map. You can set a pickup by searching or by moving the pin instead.
• Drivers: while you are online, your location is collected continuously — including when the app is in the background or the screen is off — because that is what allows riders to be matched with you, to watch you approach, and for the trip route and fare to be recorded accurately. The reporting frequency changes with your state: least often when simply online, most often while a ride is being offered or is in progress. When you go offline, location collection stops.
• Trips: pickup and drop-off points, the route taken and the distance covered are stored against the ride.

Ride and trip information

Bookings and their history: the vehicle category, timings, status changes, the driver and rider involved, cancellations and their reasons, waiting time, the ride-start PIN, and the fare breakdown.

Payment information

The payment method used, the amount, the status and the reference our payment provider returns. We do not store your full card number, your UPI PIN or your banking credentials — those go directly to the payment provider. We also keep wallet balances and the ledger entries behind them, including cash collected on cash rides.

Communications

Support requests and the messages in them; notifications we send you by push, SMS, email or in the app; and records of calls placed between riders and drivers through the app. Calls are connected without either party seeing the other's number; we hold the fact that the call happened, not a recording of it, unless we tell you otherwise at the time.

Ratings and feedback

Ratings and comments riders leave for drivers and drivers leave for riders, along with any report either side makes about a trip.

Safety information

Emergency contacts you choose to add, and the details of any emergency alert raised from the app — including the trip and the location at the time it was raised.

Device and usage information

Your device platform, the app version, a device identifier and a push notification token, so that we can deliver notifications, support the app you are actually running, and require an update when an old version is no longer safe to use. We also keep server logs of requests made to our systems, which include IP address and timestamps.

Saved preferences

Saved places such as home and work, notification preferences, and your chosen payment method.

How we use information

Every use below is tied to running the service. We do not sell personal information.

Purpose	What it involves
Ride matching	Finding drivers near your pickup who are online, available and eligible for the category you booked, and offering the ride to them.
Location services	Placing your pickup, showing the vehicle approaching, tracking the trip in progress and recording the route for the fare.
Pricing and payments	Calculating fares, applying coupons and taxes, taking payment, issuing receipts and processing refunds.
Driver verification	Reviewing identity, licence and vehicle documents before a driver takes rides, and re-checking them as they approach expiry.
Earnings and settlements	Calculating what a driver or fleet has earned, deducting commission, and paying out to the registered bank account.
Customer support	Investigating and resolving what you report to us, using the trip record rather than only the two accounts of it.
Safety and fraud prevention	Responding to emergency alerts, reviewing reports and low ratings, detecting fraudulent bookings or payments, and suspending accounts where necessary.
Notifications	Telling you that a driver accepted, arrived, that a payment went through, or that a document is expiring.
Service improvement	Understanding, in aggregate, where the service fails — cancelled rides, failed payments, long waits — so it can be fixed.
Legal and regulatory	Meeting tax, accounting and transport obligations, and responding to lawful requests.

Where the law that applies to you requires a legal basis for processing, we rely on: performing the contract with you (providing rides), our legitimate interests (safety, fraud prevention, improving the service), your consent (for example, precise location permission and marketing messages, which you can withdraw), and compliance with legal obligations.

Who we share information with

Between riders and drivers

A ride cannot happen without each side knowing something about the other. When you are matched:

• The rider sees the driver's first name, profile photo, rating, vehicle and number plate, and the vehicle's live position.
• The driver sees the rider's first name, rating, pickup point and destination.

Phone numbers are not exchanged. Calls between you are connected through the app.

People you share a trip with

If you share a live trip link, whoever you send it to can see the vehicle's position and the trip status, without an account. The link stops working when the trip ends. You choose whether to share it and with whom.

Fleet operators

If a driver drives for a fleet, that fleet operator can see the driver's trips, earnings and settlements — the information they need to run their business and pay their drivers.

Service providers

We use third parties to run parts of the platform. Each is given only what its function requires, and is bound to use it only for that purpose:

• Payment processing — to take payments and issue refunds.
• Maps, routing and address search — to display maps, convert addresses to coordinates and calculate routes.
• SMS, email and push notification delivery — to send one-time passwords, receipts and ride updates.
• Cloud hosting, storage and infrastructure — where the platform and its data run.

The current list of providers is available on request: privacy@pikmego.com.

Legal and safety disclosures

We may disclose information where we are legally required to, or where it is necessary to: respond to a lawful request from a court, regulator or law-enforcement authority; investigate a safety incident or suspected fraud; establish, exercise or defend a legal claim; or protect the rights, property or safety of any person. Where we are permitted to tell you about such a request, we will.

Business transfers

If the business or part of it is sold, merged or reorganised, information may transfer as part of that transaction. It remains subject to this policy until you are told otherwise.

How long we keep information

We keep personal information for as long as your account is open, and afterwards only for as long as we have a reason to.

• Account information — for the life of the account, then deleted or anonymised in line with the periods below.
• Ride and payment records — retained after an account closes, because tax, accounting and dispute-resolution obligations require it.
• Driver verification documents — retained for the period required by the regulations that apply to commercial driving in the relevant market.
• Support and safety records — retained while a matter is open and for a period afterwards, so a repeat report can be seen in context.
• Server logs — retained for a short operational period and then discarded.

Our standard retention period once an account is closed is 7 years. Where a longer period is required by law, or a matter is under investigation, we keep the relevant records until that ends.

How we protect information

The measures below are the ones that materially reduce risk, rather than a list of reassuring words:

• Traffic between the apps, this website and our servers is encrypted in transit.
• Authentication is server-side. Signing in requires a one-time password sent to your mobile number; sessions are issued as short-lived tokens that can be revoked.
• Every protected request is authorised on the server. What an app hides is also what the server refuses — hiding a control is never the only protection.
• Driver documents are stored in private storage and reached only through short-lived, signed links, not public URLs.
• Sensitive actions are recorded. Administrative changes to accounts, payments and settlements are written to an audit log.
• Payment credentials never reach us. Card and UPI details go to the payment provider directly.

No system is perfectly secure. If a breach occurs that is likely to affect you, we will notify you and the relevant authority as required by the law that applies.

Your choices and your rights

Subject to the law that applies to you, you can ask us to:

• Access the personal information we hold about you.
• Correct anything inaccurate — much of it you can edit yourself in the app.
• Delete your account and the information attached to it, subject to the records we must keep.
• Object to or restrict certain processing.
• Withdraw consent you previously gave, such as marketing messages or a device permission.
• Receive a copy of information you provided, in a portable form.
• Complain to a data protection authority where one has jurisdiction over you.

You also control these directly:

• Device permissions. Location, notifications, camera and photo access can be changed in your phone's settings at any time. The app will tell you what stops working.
• Notification preferences. Turn off promotional messages in the app. Messages about a ride in progress, a payment or your account cannot be turned off while you hold an account — they are part of the service.
• Going offline. Drivers can stop all location collection by going offline.

To make a request, write to privacy@pikmego.com or use the contact page. We may need to verify your identity — usually by confirming control of the mobile number on the account — before acting, because handing someone else's ride history to the wrong person is the failure this step prevents.

Deleting your account

You can request deletion from the account section of the app, or by writing to privacy@pikmego.com.

When we receive a request we confirm it, close the account so it can no longer be used to book or to drive, and then delete or anonymise the personal information attached to it. We complete this within 30 days of verifying the request.

Some records survive deletion, and we would rather say so plainly than imply otherwise:

• Completed ride and payment records, which we are required to keep for tax and accounting purposes. These are retained in a form that is no longer linked to your profile where that is possible.
• Records relating to an open dispute, claim or safety investigation, until that matter concludes.
• Information we are under a legal obligation to retain.

An outstanding balance — an unpaid fare or an uncollected cancellation fee — must be settled before an account can be closed.

Children's privacy

PikMeGo is not intended for children. You must be at least 18 to hold an account. We do not knowingly collect personal information from anyone below that age; if we learn that we have, we delete it and close the account.

A minor may travel as a passenger in accordance with our Terms & Conditions and the law that applies locally, but the account used to book the ride must belong to an adult.

Where information is processed

Our platform and its data are hosted with cloud providers, and some of the services we rely on — payment processing, message delivery, mapping — may process information in a country other than the one you are in.

Where information is transferred across borders, we take the steps the applicable law requires to protect it, including contractual protections with the recipient. The primary hosting region for the platform is India.

Third-party services and links

The apps and this website contain links to services we do not operate — an app store, a payment provider's own flow, a map, or a page we reference. Once you are there, that service's privacy policy applies, not this one.

The apps use a payment provider's software to collect card and UPI details. That information goes to the provider, not to us, and is handled under their policy and the card-scheme rules.

Cookies and similar technologies

This website is a set of static pages. In its current form it sets no cookies and loads no third-party trackers. If that changes — for example, if analytics is switched on — the Cookie Policy will be updated first and, where consent is required, it will be asked for before anything is set.

The mobile apps do not use cookies. They store your session token and your preferences in your device's own secure storage, which is cleared when you sign out or uninstall the app.

Changes to this policy

We update this policy when the platform changes or the law requires it. The "last updated" date at the top always reflects the current version, and we keep every published version.

Where a change materially affects how your information is used, we will tell you before it takes effect — in the app, by email, or both — and, where your consent is needed, we will ask for it rather than assume it.

Contact us and grievances

For any question about this policy, or to exercise a right described in it:

• Privacy enquiries: privacy@pikmego.com
• General support: support@pikmego.com
• Post: Viviax Technologies Private Limited, 2-54, Mariamman Koil St, Alavaipatty, Namakkal 637505, Tamil Nadu, India

Grievance officer

If a privacy matter is not resolved to your satisfaction through support, it can be escalated:

• Name: Mr Karthikeyan
• Designation: Grievance Officer
• Email: grievance@pikmego.com
• Response time: 48 hours

This policy is governed by the laws of India.