Last Updated: 26 March, 2025

Zavika Fintech Private Ltd operating as Drivly (“Company”, “we”, “us” or “our”) values your privacy and is committed to protecting your personal information. This Customer Privacy Policy (“Privacy Policy”) explains how we collect, use, store, disclose, and safeguard your information when you use Drivly’s services. These services include our mobile applications, website, WhatsApp booking bot, and any other online or offline services we operate (collectively, the “Services”). By accessing or using our Services, you agree to the collection and use of your information in accordance with this Privacy Policy. If you do not agree with these practices, please do not use the Services.

This Privacy Policy is incorporated into and is subject to the Drivly Terms and Conditions (Customer Terms of Use). Capitalized terms used but not defined in this Privacy Policy have the meanings ascribed to them in the Terms and Conditions.

1. Scope of Policy

1.1 Services Covered: This Privacy Policy applies to all individuals who access or use our Services as customers or end-users, through any platform or channel. This includes:

• Users of our mobile app (Drivly customer app) on Android, iOS, or other platforms.

• Visitors to our website (e.g., www.drivly.in) and users of any web-based booking interfaces.

• Users interacting with our WhatsApp bot or WhatsApp booking service (by sending messages/commands to Drivly’s official WhatsApp number or chatbot).

• Users who contact Drivly through other channels such as phone support, email, or social media for inquiries or bookings.

• Any offline collection of data that Drivly may perform in connection with its services (for example, at promotional events or through feedback forms).

1.2 Personal Data: This Policy covers how we handle “Personal Data” (or “Personal Information”), which is any information that relates to an identified or identifiable individual. It may include obvious identifiers like your name and contact details, as well as information like device IDs or location data that can be linked to you. We also describe other data that we collect (such as aggregated data or non-identifiable data) and how we handle it. Please note that information about your vehicle (if you are using Drivly to hire drivers for your own car) can also be part of your Personal Data when it’s linked to you or when you provide it to us for service purposes.

1.3 Consent: By using our Services, you consent to our collection, use, and sharing of your personal information as described in this Privacy Policy. In some cases, we may ask for explicit consent for certain data practices (for example, accessing your location or sending you promotional messages), in accordance with applicable law. If you are using the WhatsApp channel or any third-party platform to interact with Drivly, you also consent to that platform’s own terms and privacy practices (e.g., WhatsApp’s privacy policy) in relation to the communication.

1.4 Minors: Our Services are not intended for children below the age of 18. Drivly does not knowingly collect personal information from individuals under 18 years of age without parental consent. If you are under 18, you should use the Drivly services only with the involvement of a parent or guardian. If we become aware that we have inadvertently collected personal data from a minor under 18 without proper consent, we will take steps to delete that information. Parents or guardians who believe that Drivly might have collected data from or about a child under 18 may contact us to request deletion.

1.5 Third-Party Services: Our Services may contain links to third-party websites or services (for example, payment gateways, mapping services, social media login integrations). This Privacy Policy does not apply to information collected by third-party websites or services that are not operated by Drivly, even if you access them through our platform. We encourage you to review the privacy policies of any third-party sites or services before providing your information to them.

2. Information We Collect

We collect information about you in several ways: (a) information you provide directly to us, (b) information we collect automatically when you use our Services, and (c) information we obtain from third parties. We only collect information that is necessary for the purposes stated in this Policy, and we handle it in compliance with relevant data protection laws.

2.1 Information You Provide to Us

You may choose to provide us with personal information in various contexts, including:

• Account Registration: When you create an account on the Drivly app or website, we will ask for certain details to set up your profile. Examples of data collected:

• Name: Your full name (first and last name).

• Contact Information: Your mobile phone number (required for sign-up and communication), email address, and potentially your postal address (for billing or verification purposes).

• Login Credentials: A username (which could be your email or phone number) and a password. (Passwords are stored in an encrypted or hashed form and not visible to us in plain text.)

• Profile Photo: Optionally, you may add a profile picture to help drivers recognize you during pickup.

• Referral or Invite Codes: If you sign up via a referral program or enter an invite code, we record that information.

• Booking Information: When you make a booking or request a service:

• Pick-up and Drop-off Details: You will provide the addresses or locations for pickup and destination (or specify a route or hourly hire details). If using our WhatsApp bot, you might send a location pin or type the address.

• Date and Time: For scheduled bookings, you may provide the date and time you want the service.

• Vehicle Information: If you are requesting a driver to operate your own vehicle, we might ask for details like your vehicle’s make, model, color, and license plate number. This helps the driver identify the vehicle and ensures they are prepared to handle that vehicle.

• Special Instructions: Any notes or instructions you provide for the driver (e.g., “gate code 1234” or “please honk on arrival”).

• Payment Information: If you pay for services through our app or website (non-cash payments), you will provide payment details. Drivly uses secure third-party payment processors to handle financial transactions. Examples of data collected:

• Card Details: If paying by credit/debit card, you will enter the cardholder name, card number, expiration date, CVV, and billing address. Note: We do not store full card numbers or CVVs on our servers; this data is typically captured by the payment gateway in a secure manner. We may store a payment token or the last four digits of your card for reference, and card type (Visa, MasterCard, etc.).

• UPI or Wallet ID: In regions where UPI (Unified Payments Interface) or mobile wallets are used, you might provide an associated ID or handle.

• Payment Preferences: Your saved payment method, transaction history, etc.

• Identity Verification (if applicable): In certain cases, especially for high-value bookings or where required by law, we might ask for identity proof. For example, we might request a copy of a government ID or proof of address. If you participate in promotions that require eligibility verification, we may collect additional personal data to verify your identity. (Note: For regular customer use, this is usually not required unless mandated by local regulations).

• Communications with Drivly: When you contact us directly for support or other inquiries, you may provide information:

• Customer Support: If you call our helpline or send an email, we will collect the content of your communication and any additional details you provide (such as screenshots, or descriptions of a technical issue, or feedback about a driver). We might ask for certain details to verify your identity as the account holder before addressing your request.

• Chat and Chatbot Interactions: If our app or website offers live chat with support, those chat logs are saved. Similarly, if you interact with our automated WhatsApp chatbot, the messages you send and our bot’s replies are logged.

• Surveys and Feedback: If you take a survey or provide feedback/rating within the app, we record your responses. This could include written comments and ratings for drivers or overall service satisfaction.

• Promotional Events and Campaigns: If you participate in contests, referral programs, promotions, or beta testing:

• You might provide details like your social media handle (if the promotion is run on social platforms), or additional profile information, or content (for example, a testimonial or a photo) as part of the campaign. We will inform you at the time what information is being collected and how it will be used.

Note: In all the above cases, we will ask only for information that is relevant and necessary for that interaction. You may choose not to provide certain optional information (for example, skipping adding a profile photo or not saving your payment method). However, if specific information is marked as required (such as your phone number for sign-up or a pickup address for booking), then not providing it will hinder your ability to use that part of the Service.

2.2 Information We Collect Automatically

When you use our Services (through the app, website, or even via WhatsApp), we and our third-party partners automatically collect certain information about your device and your usage of the Services. This includes:

• Device Information: We collect technical information about the device you use to access our Services. Examples include:

• Device type and model (e.g., Apple iPhone 12, Samsung Galaxy S21, or PC model if web).

• Operating system and version (e.g., Android 12, iOS 15, Windows 10).

• Unique device identifiers such as the Device’s Advertising ID, IMEI, or others (these are used for analytics or to send push notifications to the right device).

• Mobile network information (carrier name, network type) in case it affects connectivity.

• App version and build, if using the mobile app.

• Usage Data: We track how you interact with our app and website to improve user experience and fix issues. Examples include:

• Date and time of access, and the duration of use of the app (session length).

• The features or pages you click on or navigate through (for example, whether you viewed certain driver profiles, or which screens you spent the most time on).

• The actions you take (such as making a booking, cancelling a booking, adding a favorite location).

• Crash logs or error reports if the app or website encounters a problem (these reports may contain device state info or error codes).

• If booking via WhatsApp, the sequence of commands or messages you send and our bot’s interactions (though this also falls under communications, it’s automatically processed by our system).

• Location Data: Location is central to Drivly’s services (for matching you with nearby drivers and navigation). With your permission, we collect precise geolocation data from your device:

• While Using the App: If you have the Drivly app open and have granted location permission, we periodically collect your GPS location. This allows features like showing your position on the map, suggesting your current location as a pickup, and tracking your trip progress when you are in a ride.

• Background Location (if allowed): Some users may opt to allow location access even when the app is not in the foreground, to enable features like sending driver updates while you are on the way to the pickup. If you do so, we may continue to receive location info until you cancel or complete your ride or close the app.

• WhatsApp or Web: If you use WhatsApp to book, you might manually share a location pin via WhatsApp. That location is then used by us but we do not continuously track you via WhatsApp. On our website, if you allow, we may get a one-time browser location for easier booking.

• Location of Drivers and Route: Note that during an ongoing trip, we collect the driver’s location data as well. We link your account with that trip’s route (start, end, and path) for generating ride history and receipts. If you are in a vehicle with the driver (in a scenario where you ride along, like a taxi), the driver’s location essentially reveals your location during the trip as well.

• Geo-location Uses: See section 4 on how we use location, but in short: finding nearby drivers, navigating, providing real-time tracking to you (and to people you share tracking with, if feature available), safety (knowing where a trip is if an issue arises), and analytics (like demand heatmaps).

• Cookies and Similar Technologies: We use cookies, beacons, and similar technologies on our website and possibly in-app for storing preferences and tracking usage. Examples include:

• Cookies on Website: Small text files (cookies) may be stored on your browser when you visit our site. These might be session cookies (lasting until you close the browser) or persistent cookies (lasting until they expire or you delete them). They help with things like keeping you logged in, remembering your language preferences, and generally providing a smoother experience.

• Analytics and Ads: We may use third-party analytics tools (like Google Analytics) that set their own cookies to collect information on how visitors use our site (pages visited, time spent, traffic source, etc.). If we run advertisements, cookies might be used to measure ad impressions or to personalize ads (though at present Drivly’s focus is service, not ads, so this may be limited).

• Mobile App Analytics: In the app, instead of cookies, we might use SDKs and device identifiers to achieve similar ends – e.g., Firebase Analytics or similar tools might automatically log events in the app.

• WhatsApp Data: WhatsApp itself may collect information about messages (like metadata) but our system will log the content of your conversation with our bot for service purposes. We do not install cookies in WhatsApp – it’s a third-party platform – but WhatsApp might use data for its own analytics.

• Do Not Track: Note that browsers offer a DNT: Do Not Track signal. Our website’s behavior with respect to DNT signals is: [provide relevant info, e.g., “currently we do not act on DNT signals and treat all user data as per this policy; no personalized ads are served that would necessitate tracking across sites”].

• Call and Text Records: If you contact a driver or our support through the app, the calls or SMS may be routed through third-party telephony services that log the occurrence of the call/SMS (time, date, your number, driver’s number). We do this to protect privacy (so drivers and riders don’t see each other’s personal numbers) and for safety. For example, if you call a driver via the masked number we provide, we know a call happened and its duration, but the call content is not recorded by us (unless announced otherwise for quality purposes, but typically two-way calls between customer and driver are private except for meta data). If you call our customer support, those calls may be recorded for training and quality assurance – we will inform you via an IVR message if a support call is being recorded.

• Camera and Microphone (App Permissions): The mobile app may request access to your camera or microphone for specific features: e.g., scanning your card or QR code, or if you want to upload a photo (like a profile picture or to report an issue). Similarly, microphone access might be needed if we implement voice commands or audio messages. Granting these permissions is optional and you will be prompted at the time. Any media or audio captured is treated as user-provided info. We do not access your camera or mic in the background; it’s only active when you are using a feature that requires it.

2.3 Information from Third Parties

We may receive information about you from third-party sources in certain situations, such as:

• Social Media or Single-Sign-On: If you choose to register or log in via a third-party account (like Google, Facebook, or Apple Sign-in), we receive information from that account (after you grant permission). This typically includes your name, email address, and profile photo from that service. We use this to create your Drivly profile. These services might also confirm your identity or whether your email is verified. We do not get your social media login credentials. Any additional info we get (like your friend list or birthdate) will only be what you explicitly allow the third-party to share with us.

• Referral Programs: If someone refers you to Drivly (or you use a promo code), the person who referred you might give us your basic contact info or a referral code might be linked to your account creation. Conversely, if you refer someone else, we may tie your identity to that referral for reward purposes.

• Business or Corporate Accounts: If your employer or another organization signs you up for a corporate travel account or provides you access to our services, they might share your name, contact, and corporate email with us to set up your access under their account. They may also later receive information about your usage under that account (like trip invoices for reimbursement). Corporate usage will be subject to agreements between Drivly and the organization, in addition to this policy for individual privacy.

• Third-Party Booking Platforms: We might partner with other platforms or aggregators where our service is listed. If you make a booking through one of these partners (for instance, a travel app that offers multiple transport options including Drivly), the partner may send us the booking details and your relevant info so we can fulfill the service. That can include your name, contact, and booking specifics. We treat this information per this policy, but the initial collection by the partner is governed by their privacy terms.

• Background Checks / Identity Verification Services: (Primarily applicable to drivers, but in some cases might apply to customers – e.g., verifying identity for a big transaction). If we ever need to verify identity or perform due diligence (for instance, if there’s suspicion of fraud), we might receive data from verification services, credit bureaus, or public record databases. For example, verifying your driving license if you’re renting a vehicle, or checking a government watchlist if required by regulation (this is uncommon for typical customers, more relevant for drivers or certain jurisdictions).

• Marketing and Advertising Partners: We could receive information from marketing agencies or ad partners about the effectiveness of our campaigns. For instance, if we run a Facebook ad and you click it, we might get info that a certain user (you) installed the app as a result of that campaign, so we can measure ad conversion. This may involve the partner using cookies or identifiers to attribute your activity to an ad, which results in a report to us (often aggregated).

• Public Sources: We might collect information from publicly available sources for certain uses. For example, if you post a public review or testimonial about Drivly on social media and tag us, we may view or use that content (with attribution) in our marketing. Or if a government site lists publicly some transportation data, etc., we may use such data to complement our own (but that usually won’t be personal data, just service planning data).

• Driver’s Information about Customers: Our drivers and chauffeur partners could provide feedback or notes about you after a ride (e.g., “Customer was not present at location” or rating you as a passenger). We treat that as part of your user profile on our system. Negative feedback from drivers might lead to an investigation or impact your ability to pay by certain methods (for example, if multiple drivers report non-payment in cash, we might require card payments from you only). We keep such information internal and do not share your rider ratings publicly at this time.

We will treat any third-party sourced information according to the practices described in this Policy, plus any additional restrictions imposed by the source (for instance, if they only allow use for a certain purpose, we will honor that).

3. How We Use Your Information

Drivly uses the collected information for various legitimate purposes related to our provision of services and our business operations. We strive to use your data in ways that are transparent and beneficial to your experience. The key purposes for which we process your personal data are:

3.1 To Provide and Personalize Our Services

• Processing Bookings: The primary use of your information is to enable you to book driver services and for us to allocate a suitable driver. For example, we use your provided pickup and drop-off location to find drivers near you and to calculate the route and estimated fare. We use your name so drivers can confirm they have the right customer, and we share your phone number (in masked form) so you and the driver can communicate about the ride. If you’ve saved favorite locations (like “Home” or “Office”), we will recognize those and make booking faster for you.

• Account Management: We use your email or phone number as your account identifier to log you in and secure your account. We may send verification codes to your phone or email to authenticate your login or actions (two-factor authentication). We use your profile information to populate your account in the app (e.g., showing your name and profile pic to the driver that’s picking you up, so they can greet you properly).

• Personalized Features: The data collected helps personalize your experience. For instance, if we notice you frequently book in a particular area or at a particular time, the app might start showing quick suggestions like “Book your evening ride from [Work Address]”. We might show relevant messages like “Good morning [Name], ready to go to [Saved Location]?” – using your name and known preferences.

• Navigation and Real-Time Updates: We use GPS data from you and your driver to provide real-time tracking on the map. This allows you to see the driver approaching and also for us to give you accurate ETAs (Estimated Time of Arrival). Your location (if you allow background tracking) can help update the driver if you move from the requested pickup (for example, you started walking down the street).

• Multi-Modal or Additional Services: If Drivly offers additional services (like car maintenance, or delivery, etc.), we use your data in similar ways to facilitate those. E.g., if you use a car wash booking feature, we use your location and vehicle info to match you with a service provider.

3.2 To Communicate with You

• Service Communications: We will use your contact information to send you communications essential for the use of our services. This includes:

• Booking Confirmations: After you request a booking, we send details like driver name, vehicle info, ETA via push notification or SMS.

• Driver Arrival Alerts: Updates when the driver is about to arrive or if there’s any delay.

• Trip Completion and Invoice: After a ride, we send you a summary or receipt of the trip fare, distance, etc., to your app and/or email.

• Support Responses: If you contacted us for help, we’ll use your email or number to respond to your query.

• Policy Updates: If we update our terms of service or this privacy policy, we may notify you via email or app notification.

• Security Alerts: We might contact you to verify activity if we detect something suspicious (like a new login from an unrecognized device), or to verify if you made a password change.

• Transactional Messages: When you make payments, you might get confirmations or OTPs (one-time passwords) via SMS or email from our payment processor, which we facilitate by sharing the necessary data. Also, if you use WhatsApp for notifications, we might send your booking updates through WhatsApp messages (with your consent to opt-in to WhatsApp notifications).

• Promotional Communications: If you have agreed or as permitted by applicable law, we may send you promotional emails, SMS, push notifications, or WhatsApp messages about:

• Special Offers: Coupons, discounts, referral bonuses, or promotions (e.g., “Get 20% off on your next ride” or holiday promotions).

• New Services or Features: Information about new offerings by Drivly, such as expansion to a new city, a new type of service (like outstation drivers, monthly driver subscriptions, etc.).

• Customer Surveys and Feedback Requests: e.g., “Rate your experience” or surveys that help us improve our service.

• Contests or Loyalty Programs: If we have a loyalty program or contest, we’ll reach out with related info.

You can opt out of marketing/promotional communications at any time (see Section 6 on Your Choices). We will not spam you; typically, such messages will be occasional and you will have control over frequency to some extent via preferences.

• In-App and Web Messaging: Within our app or website, we might show contextual messages. For example, an in-app banner could say “Complete 5 rides this week to earn a bonus” or a web pop-up might announce a new feature. These are part of delivering the service and often tailored to your usage.

• WhatsApp Bot Interactions: If you use our WhatsApp channel to chat with the Drivly bot for bookings, that in itself is a form of communication where the bot uses your input to provide responses (like available drivers, fare estimates, etc.). We program the bot to use your information (like if it knows your default location or last booking) to simplify the chat experience.

3.3 For Customer Support and Service Improvement

• Issue Resolution: When you reach out with a problem (for instance, “I was charged the wrong amount” or “I can’t log in”), we use the data we have (trip records, account info, technical logs) to troubleshoot and resolve the issue. We may also guide you through steps and follow up to ensure the solution worked.

• Dispute Handling: If there’s a dispute between you and a driver (e.g., regarding fare, route taken, or conduct), we will review data like GPS route, chat or call logs, and statements from both sides to mediate or decide the outcome. This may involve sharing limited info between the parties (for instance, telling you if a driver provided a reason for cancellation, or telling a driver if you reported damage).

• Improving Reliability: We analyze usage and error data to improve app stability and performance. For instance, if many users’ app crashes on a certain phone model, our engineers will investigate using the crash logs and device info to fix compatibility. If users often drop off at a certain step in booking, we analyze that funnel to see if there’s a UX issue.

• Training and Quality Assurance: We might use recordings of customer support calls or the content of support tickets to train our staff or the AI that assists them, aiming for better service. For example, support agents might review a set of past resolved queries to learn how to better address future ones. Any recordings used for training are internally protected and only accessible to authorized personnel.

• Feedback and Surveys: If you provide feedback in-app (like rating a ride or providing suggestions), we actively use that to improve drivers’ performance (aggregated ratings may affect driver incentives and we also educate drivers on issues raised). Survey results help us understand customer satisfaction and areas of improvement (e.g., if many people request a feature, we prioritize it).

• Research and Analysis: We may perform broader analysis on usage data: for example, analyzing demand patterns (which times of day are busiest, which areas have a shortage of drivers) to optimize our operations. This analysis might involve algorithms and data science to forecast and plan (often this is done on aggregated data that is not identifying individuals, but individual data might be looked at in a bug/issue context).

3.4 For Safety and Security

• Safety Monitoring: We use your data to help keep the platform safe. For instance, tracking trip GPS data in real time allows us to detect anomalies (like an unexpected long stop or detour) which might indicate a safety issue – in future, such features might trigger an automatic check-in or alert. We also allow you to share your live trip status with trusted contacts – when you do that, we use your location and trip info to send real-time updates to those you designate.

• User Verification: Data like your device info and patterns of usage can help us verify that it’s really you using your account (and not an imposter). If a new device logs in, we may ask for re-verification. If we suspect fraudulent behavior (multiple accounts, abuse of promo codes), we may use personal identifiers to cross-reference and detect fraud rings.

• Enforcing Terms and Policies: We utilize data to enforce our customer terms of service and driver-partner terms. For example, if a user is reported for misconduct (like disrespecting a driver or damaging property), we investigate using trip data and possibly suspend or ban the user. Similarly, we keep records of serious incidents to prevent misuse of our service.

• Fraud Prevention: The information we collect, especially around payments and referrals, is used to spot and prevent fraud. For example, if multiple accounts use the same credit card or device, it might indicate a scam to take advantage of referral bonuses – we analyze such patterns. We might also verify your payment details with our payment processor to ensure the card isn’t stolen (this could involve, e.g., address verification or card token checks). When necessary, we decline transactions or flag accounts that appear fraudulent or linked to illicit activities.

• Network and Information Security: We use technical data (like IP addresses, device identifiers, logs) to guard against and debug security breaches. For instance, monitoring failed login attempts can alert us to a possible brute-force attack, so we can act (block the IP, alert you to change password, etc.). We also deploy anti-virus and anti-malware measures on our systems that might analyze content (such as file attachments you send to support) to ensure they are safe.

3.5 For Legal and Regulatory Compliance

• Regulatory Requirements: We might be required by law to collect or retain certain information. For example, local transport regulations might require us to keep a log of all rides for a certain period, including details of drivers and passengers, in case of audits. Similarly, tax laws require us to maintain records of transactions and payments.

• Responding to Legal Process: If we receive a subpoena, court order, or lawful request from government authorities, we will use your information to the extent needed to respond. For instance, law enforcement might request data during an investigation (like confirming if you took a ride on a certain date and where). If such disclosures are necessary, we handle them as described in Section 5 (Sharing) under “Legal Requirements”.

• Enforcing Legal Claims: We may process and retain data to establish or exercise our legal rights or defend against legal claims. For instance, if there’s a dispute or lawsuit involving you (maybe an accident occurred and you sue Drivlyor vice versa), we will use relevant data (trip history, communications, account info) as evidence.

• Agreement Enforcement: As part of compliance, we also use data to enforce agreements such as investigating breaches of our terms. For drivers, we check compliance with their agreements too (though that’s separate from customer data usage, sometimes overlapping if a customer complains about a driver or vice versa).

• Grievance Redressal: In jurisdictions with specific data or consumer protection regulations (for example, certain countries require a Grievance Officer for user complaints about data), we use your info to address those grievances in the legally prescribed manner and timelines.

3.6 For Business Operations and Improvement

• Data Analytics: We combine data from many users to understand trends and preferences. For example, we might analyze what percentage of our customer base uses WhatsApp vs the main app for bookings, and at what times. This helps us allocate resources and decide future strategy (maybe improving the WhatsApp bot if usage is high). These analytics often use aggregated data that is not directly identifying you personally, but they originate from personal data.

• Developing New Features: Information on how you use current features (which ones are popular, which ones are confusing) guides us in developing new features or improving existing ones. If we see lots of customers manually retyping addresses, we might develop a “saved places” feature. If some use cases (like multi-stop trips) are common, we design a feature for that. We may also pilot new offerings to small sets of users and use their data to refine those features before full release.

• Marketing and Advertising: We might use certain information to plan our marketing strategy. For example, understanding our typical user demographics (from profile data or surveys) helps us target our advertising better. We might create custom (non-identifiable) audiences for ads, like “users who haven’t ridden in 3 months” to send a comeback offer. If we have testimonials or high ratings, we might anonymize them or use first name + last initial and city (e.g., “– John D., New Delhi” in a marketing material) with your permission when needed.

• Merger or Acquisition: If we engage in a business transaction like a merger, acquisition by another company, or sale of all or part of our assets, user information (including your personal data) is usually one of the assets transferred or reviewed. We use data internally to evaluate the business value and, if the transaction proceeds, to ensure continuity of service under new ownership (as detailed in Section 5 if sharing in such cases).

• Internal Audits and Analysis: We use data internally for financial reporting and audits (making sure all rides are accounted for, drivers paid, etc.), which might involve referencing user transactions. Also, to measure performance of business goals (like hitting a target number of rides or active users), we generate reports using collected data.

Whenever we use your information, we ensure that we have a valid legal basis to do so. In most cases, the legal bases are: performance of a contract (providing you the service you asked for), our legitimate interests (improving our services, preventing fraud, etc.), compliance with legal obligations, or your consent (for certain marketing or sensitive data). We strive to maintain transparency and allow you control over your data. Below, we explain how we share data and your choices which further detail our usage boundaries.

4. How We Share Your Information

Drivly is careful to share personal information only in ways that respect your privacy and are necessary to provide our Services or as described in this Policy. We do not sell your personal data to third parties for their own marketing purposes. However, we do share information in various scenarios with different parties, as outlined below:

4.1 Sharing with Service Providers (Third-Party Vendors)

We employ third-party companies and individuals to facilitate our Services or to perform services on our behalf. These service providers have access to certain personal information needed to perform their functions but are contractually obligated not to use it for other purposes. Examples of such providers include:

• Payment Processors: When you make electronic payments, your payment details are handled by companies that process payments (e.g., Stripe, PayU, Razorpay, or banking partners). They receive your card info or UPI ID to process transactions. We share the necessary transaction data with them (amount, order ID, etc.), and they confirm payment status which we then record. These processors are PCI-DSS compliant (a security standard for handling payment info) and are authorized to process your data strictly for payments and compliance (like fraud checks, regulatory reporting).

• SMS, Email, and Communication Providers: We use third-party services to send out communications:

• SMS Gateways: If we send you SMS alerts or OTPs, those are transmitted through telecom providers or aggregators. They see the recipient number and the content of the SMS (which might include your name or booking details). They are generally not permitted to use this data beyond delivering the message.

• Email Service Providers: For sending bulk or transactional emails (like SendGrid, MailChimp, or similar), we share your email and the content to be sent (receipt, newsletter, etc.). They store this data to deliver emails and track open rates or bounces.

• Push Notification Services: For mobile notifications, platform providers like Apple (APNs) and Google (Firebase Cloud Messaging) get device tokens and message payloads (which may include limited personal content like a first name or ride detail) to push to your device. These are typically encrypted and not seen by humans at those companies.

• WhatsApp Business API Provider: If we integrate with WhatsApp’s Business API (or through a partner like Twilio or Infobip), the messages we send or receive via WhatsApp are processed by them. They obviously see your WhatsApp number and message content to deliver it, but are bound by WhatsApp’s terms which limit use of data.

• Mapping and Navigation Tools: We may use third-party map services (like Google Maps, Mapbox, etc.) to provide location search, maps, or routing. When you enter a location or track a ride on our app, these services might process that request. For example, when you search for an address in the app, the query might go to Google Maps API which returns coordinates; Google might log that query along with an anonymous token. Or when calculating ETA, driver and rider coordinates are sent to a routing service. We try to anonymize or limit data (for instance, we might not send your name, just coordinates), but location itself is being handled by them. They are not supposed to use our data except to provide results, but aggregated usage might influence their traffic data etc.

• Cloud Storage and Infrastructure: Our application and data typically reside on third-party cloud servers (like Amazon Web Services, Google Cloud, Azure, etc.). That means your personal data is stored and processed on their data centers. They technically have the ability to access data, but contractually they do not and the data is protected by encryption and strict access controls. We rely on them for data backup, redundancy, and efficient content delivery. Similarly, if we use a Content Delivery Network (CDN) to load images faster (like your profile pic or map tiles), your data could pass through their nodes but only to serve you.

• Analytics and Usage Monitoring: We use analytics tools (e.g., Google Analytics for web, Firebase for mobile, Mixpanel, etc.) that integrate into our app/website. These tools set cookies or collect usage data and device identifiers as described in section 2.2. They compile reports for us about app usage, user demographics, etc. Typically, these providers use the data only to provide us insights and maintain their service, not to contact you or identify you individually (they see you as a pseudonymous ID). However, they might have the right to use aggregated data to improve their services or for industry benchmarking. We ensure any analytics provider we use has a privacy policy and commitments to data protection.

• Customer Support Tools: We may use third-party platforms for customer support management (like Zendesk for tickets, or a CRM system). When you email us or chat, those communications might reside in those platforms. The support agents use that platform to track and respond to your inquiries. Such platforms have access to whatever info is in the ticket (which could include your name, email, and issue details). They also typically maintain strict confidentiality and only use the data to facilitate support.

• Marketing and Advertising Partners: If we run targeted marketing campaigns, we might share hashed identifiers or minimal info with advertising partners to better reach you or similar users. For example, we might upload a list of user emails (hashed) to a social media ad platform to create a “custom audience” (so that we can show an ad to our existing users on that platform). Or we might use a “lookalike audience” where we provide a data signature of our user base to find similar potential customers. These partners don’t get plain personal info in these cases (the data is anonymized or hashed such that they can’t reverse-engineer it to an email or phone). Also, if we engage third-party marketing agencies to help with campaigns, they may need access to certain data (e.g., to know which users got what promo, or general stats to craft messages). They are bound by confidentiality and can’t use your data beyond our instructions.

• Other Vendors: There are various other specialized vendors we might utilize, such as:

• Identity Verification Services: If we need to verify customer identity for some reason, we might send your information (like ID documents) to a service that checks authenticity or performs KYC (Know Your Customer) checks.

• Survey or Feedback Tools: If we send out a survey via a service like SurveyMonkey or Google Forms, your responses go to those services and then to us.

• Logistics Providers: In scenarios where we send you physical items (maybe a promotional gift, or printed invoice), we’d share your address with a shipping/courier company.

In all cases, we share only the information that the service provider needs to perform their specific function. They are contractually prohibited from using your data for any other purpose and are required to maintain its confidentiality and security.

4.2 Sharing with Driver-Partners (Service Providers you book)

A core aspect of our service is connecting you with driver partners (the people who will actually drive you or your vehicle). When you request a service, certain information about you needs to be shared with the driver who accepts your booking so that they can effectively provide the service:

• Ride Details to Drivers: When a driver is searching for rides, they may see an incoming request that includes your pickup location, drop-off (if specified), and perhaps your first name and ride type. Once a driver accepts the booking, we share more details with that driver:

• Your First Name (e.g., “Passenger: Rahul”) so they can confirm identity at pickup. We typically do not share your full name or last name for privacy, unless needed.

• Your Pickup and Drop-off Address or Location. This is essential so they know where to go. If you set a destination, they see it to plan the route and estimate fare/time. If it’s an hourly service, they see the duration.

• Your Contact Number: We provide a way for the driver to contact you (and vice versa). Usually, this is done via a masked phone number or through the app’s call function which relays calls. However, drivers may end up seeing your phone number in some cases if local telephony doesn’t support masking. Also, if you directly call a driver’s number or vice versa outside the system, the real numbers get exposed. We instruct drivers to use this info only for coordination of the current service.

• Profile Photo: If you have a profile picture and our system uses it, the driver might see it to help recognize you in a crowd (this is a feature in some systems; if we implement it, you’ll be informed).

• Other Notes: Any notes you’ve provided for pickup (like “I’m wearing a red shirt” or “Pick me up at Gate 3 of the mall”) will be shown to the driver. If you’re a member of a corporate account or special program, a marker might indicate that (e.g., a tag saying “VIP” or “Corp Account” so they give any required extra service).

• Location Sharing During Trip: While the trip is ongoing, the driver’s app receives continuous updates of your location relative to theirs (especially relevant if you move or if they have to meet you in a large area). Conversely, the driver’s location is shared with you (and potentially with your emergency contact if you use safety features). This mutual sharing ensures proper meeting and safe journey. We don’t explicitly send your live location to the driver beyond the initial pickup point, but if you move, you might update them by calling or our system might update if you requested from a moving pin.

• In-Trip Communication: If you message the driver through our app (like “I’m at the side entrance”), those messages are obviously shared with the driver. Similarly, their messages to you go to you. We may retain a log of these communications for support (as mentioned).

• Driver’s Copy of Receipt: After completing the trip, the driver typically gets a summary (distance, time, fare) on their device. They might also get a portion of the receipt that shows fare breakdown which you also see. This usually wouldn’t include your personal details beyond maybe your first name or an order ID, but if required for them (like if a driver needs to provide proof of trip for their records, it might include pickup/drop info).

• Carpooling or Shared Rides (if applicable): If Drivly offers a carpool option where multiple riders share a vehicle, certain info is shared among co-riders and driver. For instance, if two passengers are matched in one car, each might see the other’s first name and drop location (to know order of drops), or at least be aware that another rider will be present. In such scenarios, minimal personal data is shared (we wouldn’t share phone numbers between co-riders, but the driver has contact for both).

• Drivers’ Handling of Info: We contractually bind our driver partners via their own agreement and training to respect riders’ privacy. They are only allowed to use your information for performing that ride and are not allowed to store it, misuse it, or contact you afterwards for anything unrelated to the ride. However, keep in mind drivers are not our employees but independent providers; while we enforce policies (and can suspend drivers who misuse info), we cannot absolutely control their actions. If a driver were to misuse your phone number (e.g., contacting you after the ride for personal reasons), we urge you to report it so we can take action. We do not share more info than necessary to complete the service safely.

Apart from the trip context, we do not share your personal data with drivers for other purposes. Drivers do not have access to our full customer database; they only get info pertaining to the bookings they accept.

4.3 Sharing with Other Users and the Public

• Ride Sharing & Emergency Contacts: If you use any features that allow you to share your trip details with others (for example, a “Share Trip Status” feature where you send a live tracking link to a friend or family member), then the recipients of that share will see certain information. Typically, a shared status link will show your first name, the driver’s first name and vehicle info, the ride route in progress, and real-time location on map. This is designed for safety so someone you trust can follow along. Those recipients are usually people you choose to share with (via a link or through the app’s share mechanism). They might not even need a Drivly account to view that info. Once the trip ends, that link usually expires and stops updating location. We consider this sharing under your control. We don’t send your trip info to your emergency contacts unless you actively trigger a share or safety feature. However, if there is a safety incident, our safety team may reach out to your listed emergency contact if we believe it’s in your vital interest (e.g., if you are unresponsive and potentially in danger).

• Social Media (User-Driven): If our app allows or you choose to do so, you might share content to social media (like posting a referral code or a screenshot of a completed trip). That is initiated by you, and whatever information you include (like a referral link that might identify you as inviting people) is shared as per your action. We would not post to your social media without your explicit request/consent. If you tag us or communicate with us on social media (like tweeting @Drivly for help), those communications are public (or at least visible to followers) and we might respond publicly (e.g., “Sorry to hear that, please DM us your account info”). We try to take detailed issues to private messages.

• Testimonials and Reviews: With your permission, we might publish your testimonial or review of Drivly on our website or promotional materials. This could include your first name, initial of last name, city, and any feedback you gave. For example, on our homepage we might show: “Great service and very reliable – drivers are professional. – Amit P., Mumbai”. We will not fully identify you (e.g., full last name or contact) without consent. If you post a review on an app store or third-party site, that is already public; we might quote it (again usually anonymized or attributed by whatever public name you used). If at any time you want us to stop showing your testimonial, you can contact us.

• Aggregate or Anonymized Info: We may share aggregated, anonymized information publicly and with third parties. For example, sharing statistics on how many rides happen per month, average time of use, popular destinations, etc. This data will not personally identify you. We could also share anonymized trip data for research (like collaborating with a city on traffic planning – providing heatmaps of rides with all personal details stripped out).

• Leaderboards or Gamification (if any): Some platforms have features like showing top riders (by number of rides, etc.) in a non-identifying manner (like a city leaderboard that might show an anonymized username). If we ever implement something like a referral leaderboard, we would ensure not to reveal sensitive personal info without consent.

We do not publicly display your personal information except in the limited ways above that are either controlled by you or presented with care (like testimonials). We do not show your trip history or future plans to other users. If there is any scenario in which your personal info might be visible to others not already covered, we will clarify at the time (for instance, if we had a forum or community, which we currently do not, but hypothetically if, your profile might be visible if you post there – governed by those platform rules).

4.4 Business Transfers

If Drivly undertakes or is involved in a merger, acquisition, reorganization, sale of company assets, or bankruptcy or insolvency proceedings, then we may need to share or transfer your personal data to the successor or affiliate as part of that transaction. In such events:

• Transfer to New Owner: If another company acquires Drivly or its assets, that company will possess the personal information collected by Drivly and will assume the rights and obligations regarding your information as described in this Privacy Policy. We will ensure that any new owner has at least the same standards of data protection, or we will seek your consent if required by law for the data transfer.

• Due Diligence: In the negotiation phase of a potential business deal, it is possible that a limited set of data needs to be reviewed under confidentiality by potential investors or acquirers for due diligence (to assess the business value, user base, etc.). In most cases, this data would be aggregated or anonymized (like total users, usage stats). If any personal data is involved, it would be shared in a secure environment and only as needed for evaluation, with strict confidentiality obligations.

• Notice to You: In the event of an actual transfer of ownership or assets, we will provide notice (for example, via email or prominent notice on our Services) to inform you of the change in ownership and any choices you may have regarding your personal information (for instance, if the new entity has different policies, you might choose to delete your data).

• Bankruptcy: In the unlikely scenario of Drivly entering bankruptcy or similar proceedings, your personal data might be considered an asset. We would still endeavor to protect it and any transfer in such context would be to entities bound to the same obligations or under court supervision.

Rest assured, any successor to our business will continue to be bound by this Privacy Policy (or one with comparable protections) with respect to your personal information, unless you agree otherwise.

4.5 Legal Obligations and Protection of Rights

We may disclose your information if required to do so by law or in the good faith belief that such action is necessary to:

• Comply with Legal Process: We cooperate with government and law enforcement officials and private parties to enforce and comply with the law. We will disclose any information about you to the government or law enforcement officials, courts, or other authorities if we believe it is legally required or necessary to respond to claims, legal process (like subpoenas, court orders), or to protect the rights, property, or safety of Drivly, our employees, our users, or the public. For example, if we receive a court order to provide records of all rides you took in a certain period, or if law enforcement presents a warrant or an applicable data request, we may be legally compelled to provide the requested data.

• Enforce Our Terms and Policies: We may disclose information to investigate or address violations of our terms and conditions, or to ensure your compliance with our agreements. If you are involved in activities that we suspect are fraudulent or violate Drivly policies, we might share data with investigators or lawyers to take action. Similarly, if necessary, to enforce any contractual agreements or to collect fees owed, etc., your data may be shared with collection agencies or legal counsel.

• Protect Rights and Safety: We may share information in urgent circumstances to protect personal safety, rights, or property of our customers, drivers, or any person. For example, releasing information to authorities in the event of emergencies such as incidents of violence, security threats, or to prevent imminent harm. If you send us or post content that threatens others or seems likely to cause harm, we might report it to appropriate entities including sharing your identity.

• Audits and Compliance: Occasionally, regulatory bodies or auditors may require access to certain data to ensure we’re complying with obligations (like financial audits or data protection compliance checks). They might get access to systems that include personal data, but such third parties are typically bound by confidentiality and only use data for the audit purposes.

In all cases of legal disclosure, we evaluate the request carefully, ensure it has proper authority, and only provide information that is reasonably required. Whenever permitted, we may attempt to notify you of such requests (for instance, if a government requests your data, and we are allowed to inform you, we will, unless it compromises the investigation or as prohibited by law). However, in certain cases (like urgent requests or where the law forbids notifying the user) we might not be able to provide notice.

4.6 With Your Consent

In situations other than those expressly outlined above, we will ask for your consent before sharing your personal data with third parties. For instance:

• If we ever want to share your info with a third-party partner for their own marketing (which we currently do not do), we would only do so if you opt-in to such sharing.

• If a new type of data sharing arises that is outside the scope of this Privacy Policy, we will notify you and get consent if required.

Additionally, you might direct us to share your information in specific ways: e.g., if you instruct us to connect with a third-party service (like syncing travel itineraries with your calendar, or linking an expense management app), we will share data as needed for that integration, based on your consent.

In summary, Drivly will share your personal information only for the purposes and with the parties described above, or if we have a good-faith belief that a disclosure is reasonably necessary to comply with a legal obligation or other above-mentioned exigencies. We strive to ensure that any third party that receives personal data from us is bound to protect it and use it only for the intended purpose. If you have questions about specific third parties we work with, you can contact our Grievance Officer or Support for more details.

5. Cookies and Tracking Technologies

Our website and (to a lesser extent) our mobile app use cookies and similar tracking technologies to provide and enhance our Services. This section explains how we use these technologies and your choices regarding them.

5.1 What Are Cookies and Why We Use Them

Cookies are small text files that are stored on your browser or device by websites, apps, or advertisements. They often include a unique identifier that allows the website (or third-party that set the cookie) to recognize your device upon return visits. We use cookies and similar technologies (like web beacons, pixels, local storage, and SDKs in apps) for a variety of reasons:

• Authentication & Security: To keep you logged in as you navigate our site or app (so you don’t have to log in repeatedly). Cookies help us verify your account and device, and determine when you’re logged in, so we can show you appropriate data. They also help us fight fraud – e.g., by tracking sessions and usage patterns, we might detect unusual behavior.

• Preferences: Cookies allow us to remember your preferences and settings. For instance, if you choose a preferred language on our website, a cookie stores that so next time you visit, we display content in that language. Similarly, preferences like remembering your login email (so you just input password), or saving addresses for quick selection, can be aided by cookies or local storage.

• Functionality: Certain features depend on cookies or local storage – for example, if our site has a chatbot, it might use cookies to recall your last interactions. Or if we implement a referral banner that should hide once you close it, a cookie will remember that you dismissed it.

• Performance & Analytics: We use cookies and similar tools to analyze how users use our Services. For example, Google Analytics sets cookies to collect info about site traffic and usage patterns (pages visited, time spent, etc.). These analytics help us understand user behavior, which pages or features are popular, what times of day see heavy use, and so forth. This information is generally aggregated and not intended to identify individual users. It helps us improve the design, content, and overall user experience.

• Advertising (if applicable): Currently, Drivly does not heavily rely on third-party ads on our platform, but if we do run promotional campaigns or retarget users, cookies may be used. For example, we might use Facebook Pixel or Google Ads cookies to show you Drivly ads on other sites after you visit our site (this is called retargeting). These cookies memorize that you visited or took an action on our site/app, and then an ad network uses that to serve you our ads elsewhere. Also, if we partner with advertising networks, they might set cookies to track ad impressions, clicks, and conversions relating to our campaigns.

• WhatsApp and Non-Web Platforms: While WhatsApp itself doesn’t use “cookies” in the web sense on their chat interface with you, they may use tracking for messages. Our own website’s WhatsApp integration might use something like storing that you clicked “Open WhatsApp chat” so we know that channel was initiated. The Drivly mobile app may use device storage for similar purposes as cookies — for example, saving an authentication token on the device so you remain logged in (which is conceptually similar to a cookie).

• Web Beacons/Pixels: We or our email service may use tiny graphic images or scripts (pixels) in emails or on the site to count users who have visited certain pages or opened an email. This helps gauge the effectiveness of communications (if you open our email and click a link, the beacon registers that interaction). It’s primarily for analytics and ensuring our messages reach you properly.

5.2 Your Choices Regarding Cookies

We want you to be in control of your data. You have a few options to manage or limit how we and others use cookies and similar technologies:

• Browser Settings: Most web browsers automatically accept cookies, but you can typically modify your browser settings to decline cookies or alert you when a cookie is being placed. Check your browser’s help or settings menu for how to change cookie preferences. Please note, however, that if you disable cookies entirely, our website (and others) might not function properly. For example, you may not be able to log in or use some interactive features that rely on cookies. You can usually delete existing cookies as well.

• Cookie Banner & Preferences: On our website, we may display a cookie notice or preferences panel when you first visit, especially if required by law (e.g., in the EU). This banner may allow you to opt in or out of certain categories of cookies (like analytics or marketing cookies). If so, you can make your selections there. If you dismiss or accept cookies via the banner and later change your mind, you can often find a “Cookie Settings” link on our site to adjust preferences again.

• Do Not Track (DNT): DNT is a setting in some browsers that requests that a web application disable its tracking of an individual user. However, there is no industry consensus on how DNT signals are to be interpreted. At this time, our systems may not respond to DNT: we treat all visitors the same with regard to cookies, unless they use other means to opt out. Instead of relying on DNT, using the provided cookie controls or browser settings is more effective for controlling tracking.

• Mobile App Tracking: For our mobile app, you can typically control tracking via your device settings: both Android and iOS provide options to limit ad tracking or reset your advertising ID. Also, when our app first runs certain analytics or tracking, we may ask for your consent (depending on regulations like GDPR or iOS AppTrackingTransparency). You can opt out of sharing analytics data by toggling an option in app settings if we provide one, or by uninstalling if you’re extremely concerned (though we hope to provide simpler controls).

• Opting out of Analytics: Google Analytics offers a browser add-on that allows you to opt-out of their tracking on all sites: Google Analytics Opt-out Browser Add-on. Similarly, other analytics tools might have opt-out mechanisms. On our end, if you request, we can try to exclude your visits from analytics by filtering your user ID, etc., but using the tools above is more straightforward.

• Opting out of Ads: For interest-based advertising, you can opt out of many networks via the Digital Advertising Alliance or Network Advertising Initiative websites, or for mobile, by enabling “Limit Ad Tracking” (iOS) or “Opt out of Ads Personalization” (Android). Keep in mind, even if you opt out of personalized ads, you may still see generic Drivly ads, but they wouldn’t be tailored using cookie data.

5.3 Third-Party Cookies and Tracking

We have mentioned third-party involvement in cookies. It’s important to note that third parties (like analytics companies, ad networks, and providers of external services like web traffic analysis) may use cookies, beacons, or similar technologies on our site as well. For example:

• Analytics: Google Analytics sets its own cookies to track user interactions. These might include _ga, _gid, etc., which store unique visitor IDs. We have configured GA to anonymize IP addresses where applicable. Google’s ability to use and share information collected by Google Analytics about your visits is restricted by Google’s terms and privacy policy.

• Advertising: If we run Google Ads (AdWords) or Facebook Ads, those platforms may install cookies (like the Google Ads conversion cookie or Facebook Pixel cookie) to measure ad performance and attribution. These cookies allow us to know if you clicked an ad and then did something on our site. It doesn’t reveal personal info to us, just that an anonymous user took an action, which we correlate with our campaign.

• Social Media Widgets: If our site includes social media plug-ins (like a Facebook “Like” button, Twitter “Tweet” button), those plugins might set cookies or use other tracking (they may see that your browser visited a certain page, possibly linking it to your social account if you’re logged in). These interactions are governed by the privacy policies of the respective social media companies.

We do not have direct control over the cookies placed by third parties, other than choosing whether to incorporate their services into our site. However, we ensure any such third-party is reputable and we try to limit what they can collect (for example, we might not include third-party scripts that we deem overly intrusive). Where required, we will list the categories of third-party cookies in our cookie consent tool, so you can opt out of them if desired.

5.4 Local Storage and Other Technologies

In addition to cookies, our site/app may use local storage (including HTML5 local storage) to store content information and preferences (e.g., a list of your past search locations stored on your device for quick reuse). Local storage is similar to cookies but can hold more data and is stored in your browser’s database rather than as small files. You can usually clear local storage via your browser settings (often clearing cache will do this).

Our emails may contain a small snippet of code (a beacon) that tells us if an email was opened or if certain links were clicked. We use this info primarily to figure out which communications are useful to users (for instance, if few people open a certain type of email, we may stop sending it).

By using our Services, you agree to our use of cookies and similar technologies as described, unless you opt out through one of the means described above. We will update you of any material changes in how we use these technologies in our Privacy Policy or via cookie notices.

6. Data Security

We understand that the security of your personal information is important. Drivlytakes a number of precautions to protect your data from unauthorized access, alteration, disclosure, or destruction. However, no method of transmission over the internet or electronic storage is 100% secure, so while we strive to use commercially acceptable means to protect your personal data, we cannot guarantee absolute security. Below are key measures and practices we follow:

6.1 Technical Safeguards

• Encryption in Transit: We enforce secure communications by using encryption protocols. All data exchanged between your app/browser and our servers is transmitted over HTTPS (TLS encryption). This means that personal information (like login credentials, booking details, payment info) is encrypted while it’s traveling over the internet, making it much harder for anyone to intercept or eavesdrop on it. Similarly, our mobile apps communicate with the backend using encrypted channels. For WhatsApp communication, WhatsApp itself provides end-to-end encryption for messages which covers that channel’s transit security.

• Encryption at Rest: We encrypt sensitive data at rest in our databases and storage. For example, passwords are never stored in plain text; they are hashed (using strong one-way hashing algorithms with salt) so that even our team cannot retrieve your actual password. Other particularly sensitive fields (like payment tokens, identity numbers, etc.) may be encrypted in the database, meaning that even if someone gained unauthorized access to the storage, they couldn’t read that data without the encryption keys. Those keys are stored separately with strong security.

• Access Controls: We restrict access to personal information within our organization strictly on a need-to-know basis. Only authorized Drivly employees, contractors, or agents who require your information to perform specific job duties (for example, customer support resolving an issue, or a developer debugging a specific problem) are granted access to personal data. We employ multi-factor authentication, unique user IDs, and robust password policies for our internal systems to prevent unauthorized login. Administrative access to servers and databases is logged and audited.

• Network Security: Our servers and network infrastructure are protected by firewalls, intrusion detection systems, and other monitoring tools. We regularly update our systems with security patches to guard against vulnerabilities. We segment our network such that critical systems are isolated and additional authentication is needed to access them. We also run periodic penetration tests and security assessments (often via third-party security experts) to identify and fix vulnerabilities.

• Data Backups: We keep backups of critical data in secure, encrypted form. This ensures that in case of a hardware failure or other issue, we can restore your information. Backup data is protected with similar encryption and access controls and is stored separately (often in secure cloud storage or offsite).

6.2 Organizational and Operational Security

• Employee Training and Policies: All Drivly employees and contractors are trained on the importance of privacy and security. We have internal policies governing how personal data must be handled and kept confidential. Employees with access to personal data sign confidentiality agreements and undergo background checks as permitted by law. We make sure they are aware of security best practices (like recognizing phishing attempts, secure handling of user data, etc.).

• Third-Party Vendor Security: When we engage third-party service providers (as mentioned in sharing section), we vet their security practices. We choose reputable providers and include data protection clauses in our contracts with them. For critical services like payment processing or cloud hosting, we rely on industry-leading companies with high security standards and compliance certifications (like ISO 27001, SOC 2, PCI DSS for payment, etc.). We monitor their compliance and require timely patching of any vulnerabilities that could affect us.

• Physical Security: For any physical offices or data centers we maintain, we enforce access controls (badges, biometric access, surveillance cameras) to prevent unauthorized physical access to systems where personal data is stored. Our critical servers are usually in secure data centers run by cloud providers with stringent physical security protocols.

6.3 Data Retention and Minimization

Though not directly “security,” our approach to retaining data impacts risk. We implement retention schedules (see Data Retention section) to ensure we don’t keep personal data longer than necessary. Old data, if no longer needed, is securely deleted or anonymized, reducing the amount of information at risk in case of a breach.

We also minimize the personal data we collect to what is relevant. For example, we don’t store full payment card numbers on our servers, reducing exposure of that sensitive info.

6.4 Incident Response

Despite strong security measures, if a data breach or security incident were to occur, Drivly has an incident response plan in place. Steps we will take include:

• Immediately working to contain the breach (e.g., shutting down compromised systems, revoking credentials, etc.).

• Launching an investigation (often with third-party security experts) to determine the scope, root cause, and data affected.

• Notifying affected users and authorities as required by law. We comply with applicable breach notification laws, which might require us to inform you within a certain timeframe if your data was involved in a serious breach. We will contact you via email, app notification, or other direct communication with information about what happened, what data was involved, and advice on what you should do (like changing passwords, watching for suspicious activity).

• Taking steps to prevent future incidents (patching, improving systems, additional training, etc.).

We also provide ways for you to help keep your data secure: for instance, you must keep your account password confidential and we encourage using unique passwords. We also provide options like two-factor authentication when possibleto add another layer of protection.

6.5 No Absolute Guarantee

While we put in significant effort to safeguard data, we want to remind you that no system is impenetrable. Advanced cyber attacks or unforeseen vulnerabilities could lead to compromises. We cannot guarantee absolute security of any information.

However, we are continuously improving our security measures to meet or exceed industry standards and will make any required disclosures if an unlikely event affects your information.

If you have reason to believe that your data or account with us is no longer secure (for example, you feel your account has been hacked), please contact us immediately through our Grievance Officer or Support Contact listed at the end of this policy so we can assist and take appropriate measures.

7. Data Retention and Deletion

Drivly retains personal information for as long as necessary to fulfill the purposes outlined in this Privacy Policy, unless a longer retention period is required or permitted by law. The length of time we keep your data can vary based on the type of data and the context of how it was collected. Below, we outline our general retention practices and your options regarding deletion:

7.1 Retention Periods

• Account Information: We retain your basic account information (like name, contact details, login credentials, etc.) for as long as your account is active and for a certain period after you discontinue using the service. Even if you stop using the Drivly app or delete it from your device, unless you specifically delete your account or request deletion, we will keep your account on file in case you return, and also for the reasons below (legal obligations, etc.).

• Ride History and Transaction Data: We maintain a history of your rides, payments, and related transaction details for at least the duration necessary for customer support, accounting, and legal compliance. For example, ride receipts and payment records may be kept for several years as required by tax regulations or for auditing purposes (often 5-7 years is a typical period to retain financial transaction data). Even if you delete your Drivly account, we might be required to keep certain data (like invoices or basic identification tied to transactions) for the legally mandated period.

• Communications and Support Tickets: If you contacted support or if there were disputes, those communications might be retained until the issue is resolved, and then archived for a period in case of follow-up. Typical retention for support logs might be 2-3 years, but could be longer if they contain info relevant to a legal dispute or recurring issue. Recorded calls (if any) are usually retained for a limited time (few months) unless flagged for training or dispute evidence, in which case they might be kept longer.

• Usage Data & Analytics: Aggregated usage data that is not directly identifiable may be retained indefinitely to help us improve our services (this data might not be considered personal data legally if it’s fully anonymized). Raw logs and app event data linking to user IDs are often rotated or deleted after a shorter period (maybe 6-12 months) once we’ve extracted useful analytics, unless needed to investigate fraud or technical issues.

• Geo-location Data: Detailed GPS traces of rides are retained for as long as ride history (for receipts and safety). If we collect continuous location when the app is in use, that might be kept with trip records. Off-trip location pings (if any) we usually do not store long-term except maybe the last known location to suggest pickups. In summary, location data gets tied to ride records and persists with them.

• Marketing Data: If we have records of consents (for example, opt-ins to newsletters) or suppression lists (opt-outs), we keep those as long as necessary to honor your preferences (e.g., if you opt out of emails, we keep your email on a do-not-contact list to ensure we don’t email you again inadvertently). If you entered a contest or promotion, data around that might be kept through the promotion’s duration and any required post-promotion period (like winner lists might be kept per legal requirements for a year or two).

• CCTV/Security (if applicable): If you visit a Drivly office or if vehicles had dashcams (not presently the case, but hypothetically), any video recordings would be retained per our security policy (often overwritten after a set time unless flagged for an incident).

7.2 Legal Obligations for Retention

Certain laws and regulations compel us to retain data for specific periods. For example:

• Financial/Tax Laws: As mentioned, transaction records and invoices need to be kept typically for 5 to 7 years (depending on local laws) for auditing and tax purposes.

• Regulatory Compliance: Transportation regulations might require that we keep a log of all rides and driver details for a minimum time in case of investigations.

• Litigation Holds: If we are involved in a legal proceeding or receive a legal notice relevant to your data, we will preserve the data relevant to that matter until it is resolved (which could be longer than our standard retention).

• Grievance/Complaint Data: If you lodge a formal grievance, we might need to document the process and outcome and retain that evidence to demonstrate compliance with consumer protection laws, typically for a couple of years after resolution.

7.3 Account Deletion and Your Rights

• Deleting Your Account: You have the right to request deletion of your personal data. You can typically delete your Drivly account by contacting us through the app or support channels (some platforms may also allow a self-serve delete in the account settings). Upon receiving a verifiable deletion request, we will proceed to deactivate your account and remove personal information that we are not required to keep. Deletion generally takes effect within a reasonable time after verification and processing (we’ll communicate expected timeline, often within 30 days).

• Data We May Retain After Deletion: Even after you delete your account, we may retain certain information for the purposes mentioned above. This includes:

• Transactional records (ride history, payments) kept for legal/tax reasons.

• Any data necessary to resolve disputes or defend against future legal claims (for instance, if you were banned for misconduct, we might keep a record to prevent re-registration; or if there’s a chance of litigation, we preserve relevant evidence).

• Logs and records that are stored in backup archives which will be deleted according to our backup rotation schedule (meaning if your data is on a backup tape, it will eventually be overwritten or destroyed per routine, but not immediately upon account deletion).

• Anonymized data: We may convert your data to an anonymized form (removing identifiers) and keep that for analysis. For example, after account deletion, your rides might still count in aggregated city statistics but no longer tied to your identity.

• Service Limitation during Deletion: Once you request deletion, you will not be able to log in or use the account (we might lock it during processing). If you just uninstall the app without formal deletion, your account stays, as described, and you can reinstall and use it anytime.

• Retention for Users with No Activity: If you have registered but not used the service for a long time, we might eventually classify the account as dormant and remove some of your data (especially if required by law or storage optimization). For example, if an account hasn’t been accessed in 3 years, we may purge certain personal data while possibly retaining minimal info (like email with a flag that it’s deactivated) to prevent fraud. We’ll try to notify you at your last provided email/phone before such archival deletion, giving you a chance to keep the account active.

• Backups and Delays: Please note that deletion from active systems is prompt, but complete removal from all systems (like caches, backups) might take additional time. We have processes to eventually clean those up or render data unreachable.

• Exercising Your Rights: Depending on jurisdiction, you might have a right to request erasure of your data. Section 9 (Your Rights) covers how to exercise these rights. We honor legitimate deletion requests consistent with our legal obligations and the above-described retention policy. If we must retain some data, we will inform you of that and the reasons.

7.4 Data Anonymization

In cases where full deletion is not feasible or required, we may opt to anonymize the data. For instance, rather than deleting a trip record entirely (which might conflict with obligations), we could strip it of personal identifiers (your name replaced with a random code, etc.). This way, the record can be kept for analytics or legal reasons without being linked to you. Anonymized data is no longer personal data as it’s not re-identifiable.

We will update our retention and deletion policies as needed to comply with new laws or changes in business needs, and reflect those in this Privacy Policy. We aim not to keep your personal data longer than necessary and to dispose of it in a secure manner when it’s no longer needed.

8. International Data Transfers

Drivly operates primarily in India (and possibly other jurisdictions) – please adjust if Drivly is global – and the data we collect may be transferred to and stored on servers located in different countries. If you are using our Services from outside the country where our servers or offices are located, please be aware that your information may be transferred across international borders. This section explains how we handle cross-border data transfers and what measures we take to ensure your data is protected when moved to another jurisdiction.

8.1 Data Storage Locations

Currently, the personal data we collect is stored on servers located in India. However, some of our service providers (cloud hosting, analytics, etc.) might store data in multiple locations globally for redundancy and speed. This means your data could be processed in [list likely regions, e.g., the United States, European Economic Area (EEA), India] or other places where those providers have infrastructure.

For example, if we use cloud services from AWS or Google Cloud, they may store data in data centers in the U.S., Europe, or Asia Pacific. Our primary database might reside in one country, while backups could reside in another.

8.2 Transfer Mechanisms

Whenever we transfer personal information from one country to another, we take steps to ensure that the transfer is lawful and that adequate safeguards are in place:

• Standard Contractual Clauses (SCCs): For transfers out of regions with strict data laws (like the European Union) to countries not deemed to have “adequate” privacy laws, we rely on EU-approved Standard Contractual Clauses or equivalent legal mechanisms in contracts with the data receiver. These clauses commit the receiving party to protect the personal data to EU standards regardless of local law differences. If you are an EU user (though likely Drivly is Indian focusing Indian customers, if any EU data is involved), we ensure any U.S. or Indian providers handling your data have these clauses or another lawful basis.

• Adequacy Decisions: Some countries are recognized by certain jurisdictions as having adequate data protection (e.g., EU to countries like Japan or Canada). If we transfer data to such a place, it’s considered automatically in line with EU law due to that adequacy decision.

• Consent for International Transfer: In cases where legal mechanisms are complex or not in place, we may seek your explicit consent for transferring your data across borders when you sign up or via acceptance of this policy. By using Drivly services, you are consenting to the transfer of your information to countries which may have different data protection regimes than in your country (though we still protect it as described).

• Intra-Group Agreements: If Drivly has affiliated entities in other countries (for example, if we have a subsidiary or parent company abroad), we have internal data transfer agreements ensuring all entities uphold consistent privacy and security practices.

8.3 Jurisdiction-Specific Considerations

• India: Since Drivly is likely an Indian-based service (given references like DriveU, etc.), Indian laws apply to data processing. India as of [2025] is in the process of implementing new data protection law (the DPDP Act 2022). We comply with applicable sections (like appointing a Grievance Officer in India, local storage requirements if any sensitive data require it, etc.). There’s currently no restriction on transferring data out of India, but we ensure equivalent protection standards.

• Europe (EEA/UK): If we have users or operations in the EEA or UK, we adhere to GDPR/UK GDPR requirements. This means any transfer outside EEA/UK will either go to a country with adequacy or be under SCCs, as said. EU individuals also have rights which we respect (see Section 9).

• Other Countries: We aim to comply with any local data regulations where we provide services. For example, if in future Drivly operates in or has users from e.g., Singapore, we would adhere to PDPA guidelines, etc.

• WhatsApp Data: Note that when using WhatsApp, your data is subject to international transfer by WhatsApp (which stores data in the US and elsewhere under its privacy policy). By using that channel, you agree to WhatsApp’s transfer terms as well. We primarily process WhatsApp interactions on our systems as per above protections.

8.4 Security and Privacy Safeguards

Regardless of where your data is stored or processed, we apply the safeguards described in the Security section (Section 6). Our security team manages and monitors all locations similarly, and service providers must meet our security requirements globally.

Additionally, any third parties handling data must align with our privacy values. For example, our customer support vendor or marketing email service might be US-based but they sign commitments to confidentiality, use data only for our instructed purpose, and (if applicable for EU data) incorporate SCCs or similar.

8.5 Your Acknowledgment

By using our Services, you acknowledge and consent that your information may be transferred to, processed, and maintained on servers or databases located outside of your state, province, country, or other governmental jurisdiction, where privacy laws may not be as protective as those in your jurisdiction. We will take all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy.

If you have questions or need more information about cross-border data transfer or the safeguards in place, you can contact our Grievance Officer or the privacy support contact given in this policy.

9. Your Rights and Choices

Drivly respects your privacy rights and provides you with reasonable access and control over your personal data. Depending on applicable law and our policies, you as a user have the following rights regarding the personal information we hold about you:

9.1 Access and Portability

You have the right to request access to the personal data we hold about you. This means you can ask us to confirm if we’re processing your information and request a copy of that information.

• How to Access: You can typically see a lot of your data through the Drivly app itself (for example, your profile info, ride history, payment history). If you need a comprehensive export, you can contact us (see Contact section) with an access request. To protect your privacy, we may ask you to verify your identity before providing any data (to ensure the person requesting is actually you).

• Data Portability: In certain jurisdictions (e.g., under GDPR), you may have a right to request your personal data in a structured, commonly used, and machine-readable format, and to have that data transmitted to another data controller. We will provide an electronic file of your basic account data and ride history upon request, where it’s feasible. Note, data portability doesn’t require including our proprietary analytics or anything, just the data you provided or that was collected from you.

9.2 Rectification (Correction)

If you believe that any personal information we have about you is inaccurate or incomplete, you have the right to request us to correct or update it.

• Self-Service Edits: Through your account settings, you can edit certain information directly (like your name, contact, saved addresses). We encourage you to keep your info up-to-date (e.g., new phone number or email).

• Requesting Corrections: If there’s something you cannot change (like an official ID number or something in our records), contact us with what needs rectification and why. We’ll verify and make appropriate updates. For example, if your name was misspelled during signup and it’s locked, we can fix that.

We will also proactively correct data if we become aware of errors (like a bounce from an email might prompt us to confirm and update your email address).

9.3 Deletion (Right to be Forgotten)

As detailed in the Retention section, you have the right to request deletion of your personal data in certain circumstances:

• Account Deletion: You may request that we delete your account and associated personal information. You can do this typically via contacting support or possibly an account deletion option in-app.

• Scope of Deletion: Upon such request, we will remove or anonymize personal information that we are not required to retain. However, as noted, we will retain what we must for legal or legitimate business purposes (e.g., past transaction records, etc.). If we cannot fully delete, we will inform you what we are keeping and why (unless we’re legally prevented from disclosing that).

• When Deletion May Be Denied: We might deny deletion requests if: (a) the data is required for executing a contract (e.g., you have an ongoing ride or balance), (b) for legal compliance (like active investigations, tax records), (c) if the request is unfounded or excessive (especially repetitive), or (d) if the data is needed for free expression, public interest, or establishing/defending legal claims. We will explain any denial in compliance with applicable law.

• Effect on Service: If you request deletion, you will lose access to Drivlyservices that rely on that data. Also, note that backup copies might not be immediately deleted but will be overwritten in due course.

9.4 Objection to Processing

In certain jurisdictions (like EU residents under GDPR), you have the right to object to our processing of your personal data if that processing is based on our legitimate interests or for direct marketing purposes.

• Marketing Opt-Out: You can always opt out of direct marketing (newsletters, promotional texts, etc.). Once you opt out, we stop using your data for those marketing purposes. Every marketing email will have an unsubscribe link. For SMS/WhatsApp, you may reply with designated keywords or adjust settings in app. Push notifications can be turned off via device settings.

• Objecting to Legitimate Interest Uses: If you believe our use of your data (that we justify under “legitimate interest”) is impacting you negatively and you want us to stop, you can object. For example, if we are processing your data for a research or product improvement that you don’t agree with, you can tell us. We will then review the objection and unless we have compelling legitimate grounds that override your interests or it’s needed legally, we will cease the processing objected to. One area this could apply is if you object to profiling (say we profile you for fraud detection or service personalization) and it significantly affects you, you could object. We will either stop or explain our grounds.

9.5 Restriction of Processing

You have the right to ask us to restrict the processing of your data in some circumstances, for example:

• You contest the accuracy of the data (until we verify its accuracy or correct it, you might want it not processed).

• The processing is unlawful but you prefer restriction over deletion (maybe you want us to keep the data but not use it until an issue is resolved).

• We no longer need the data but you need it preserved for a legal claim.

• You have objected to processing (as above) and are awaiting verification of overriding grounds.

During restriction, we will store the data but not use it except for the exempt reasons (legal claims, consent, protecting others’ rights, etc.). We will inform you when the restriction is lifted.

9.6 Automated Decision-Making

Drivly might use automated decision-making or profiling in some cases (like matching drivers to riders, fraud checks, etc.). However, we do not make decisions that legally or significantly affect you without human oversight. If we ever implement significant automated decisions (e.g., automatically banning a user due to certain triggers), you have the right to:

• Request human review of that decision,

• Express your point of view, and

• Contest the decision.

For example, if an algorithm flags your account as fraudulent and disables it, you can contact us to have a person review the case. We’ll give you the opportunity to explain and we’ll re-evaluate under human judgment.

9.7 Consent Withdrawal

Where we rely on your consent to process data (like sending marketing emails, or accessing your location in background on iOS, etc.), you have the right to withdraw your consent at any time.

• This will not affect the lawfulness of processing based on consent before its withdrawal. But once withdrawn, we will stop the specific processing that was based on consent.

For example, if you gave consent for sharing data with a partner app and then withdraw, we’ll stop sharing and notify the partner to delete any new data (already shared data handling might be subject to their policy). Or if you let us use location always and then change to “while using app”, we adjust to that new setting.

9.8 Complaints

If you have concerns or complaints about how we are handling your data, we encourage you to contact us directly (see Grievance Officer) so we can address it. However, you also have the right to lodge a complaint with a data protection authority or relevant regulator. For instance, if in the EU, you can approach your local Data Protection Authority. In India, you could approach the Grievance Officer or courts under IT Act. We will work with regulatory bodies to resolve any complaints.

9.9 Verification of Identity

For any substantial request regarding personal data (access, deletion, etc.), we need to verify that you are the rightful data subject (or an authorized representative). We might do this by asking you to log into your account, or provide information that matches our records, or identification documents if necessary. We do this to prevent fraud (we don’t want to give your data to an impostor).

9.10 Response Time

We aim to respond to all legitimate requests within a reasonable timeframe: typically within 30 days. If a request is complex or we have many requests, it may take longer, and we will inform you of the extension and reason.

9.11 Limitations

Some rights may not be absolute. For example, we might not provide certain data if it includes others’ personal info or trade secrets, etc. We also might decline repetitive or harassing requests. If we deny your request, we’ll explain why (unless legal restrictions).

We do not discriminate against individuals for exercising their privacy rights. If you choose to exercise any of these rights, we will not deny you services, charge different prices, or provide different quality (subject to the functionality limitations if data needed for service is removed).

To exercise your rights, please reach out to our Grievance Officer or Customer Support as detailed in the Contact section below. We’ll guide you through the process.

10. Updates to this Privacy Policy

We may update or modify this Privacy Policy from time to time to reflect changes in our practices, technologies, legal requirements, and other factors. We encourage you to review this Policy periodically to stay informed about how we are protecting your information. Here’s how we handle updates:

10.1 Notification of Changes

• If we make material changes to this Privacy Policy, we will provide a prominent notice to users prior to the change becoming effective. This could be done by:

• Sending an email to the email address associated with your account,

• Posting a notice on our website or within the mobile application (such as a banner or pop-up notification),

• Or via other communication channels available (like a WhatsApp message if appropriate).

Material changes might include (for example) a change in the types of data we collect, a significant new purpose for processing data, changes in how we share data, or updates in your rights. Minor changes (like clarifications, grammar fixes, or changes that do not impact your privacy negatively) may not be communicated in the same way, but the latest Policy will always have the “Last Updated” date at the top.

• The notice will outline what is changing and, if applicable, the rationale behind it. We will also update the “Last Updated” date at the top of the Privacy Policy.

10.2 Acceptance of Changes

By continuing to use our Services after those changes become effective, you acknowledge and agree to the updated Privacy Policy. If you do not agree with the changes, you should discontinue use of the services and may request deletion of your data as per Section 9.

For significant changes, especially if required by law, we may explicitly seek your consent again. For instance, if in the future we decide to process existing data for a new purpose that requires consent, we might ask you to opt-in via an in-app alert or similar.

10.3 Version History

For transparency, we may keep prior versions of this Privacy Policy accessible. If requested, we can provide earlier versions and highlight what changed. In some jurisdictions, we might be required to maintain an archive of policies.

10.4 Questions about Updates

If any user has questions or concerns about a change in the Privacy Policy, they can contact our Grievance Officer or support before the change takes effect. We welcome feedback.

We take your privacy seriously and will not reduce your rights under this Privacy Policy without your explicit consent. Any changes will comply with relevant privacy laws and we will always act in good faith with respect to your privacy.

11. Contact Us and Grievance Redressal

If you have any questions, concerns, or complaints regarding this Privacy Policy or how we handle your personal information, or if you wish to exercise any of your rights as described above, please reach out to us. We are here to help and address your concerns.

11.1 Grievance Officer (Data Protection Officer):

In accordance with applicable laws (such as the Information Technology Act, 2000 and rules thereunder in India, or other global data protection laws), we have designated a Grievance Officer who is responsible for overseeing compliance with this Privacy Policy and for addressing any grievances or concerns you might have.

• Name: Zachariah Jacob

• Designation/Title: Grievance Officer

• Email: support@drivly.in

• Contact Number: +91 82200 46002 (available on 8 AM to 8 PM on all days)

• Postal Address: Zavika Fintech Private Limited, Trading as Drivly, Flat No-1082, Sector A, Pkt B, Vasant Kunj, New Delhi: 110070

Please direct any complaints or issues to the Grievance Officer via email or postal mail with the subject “Privacy Grievance – [Your Issue]”. Kindly include your contact information and as much detail as possible about your concern. The Grievance Officer (or an authorized team member) will acknowledge receipt of your complaint within [72 hours] and will work to address your issue in a timely manner. We aim to resolve all grievances within [30 days] of receipt. If an issue requires more time, we will keep you informed of the progress and reason for delay.

11.2 Customer Support:

For general inquiries or support related to our services (booking issues, account help, etc.), you can contact our customer support team:

• Support Email: support@drivly.in

• Helpline: +91 82200 46002 8 am-8 pm on all days

• In-App Support: Use the “Help & Support” section in the Drivly app to chat with a support agent or to raise a ticket.

While customer support can handle many routine requests (like account updates, trip issues), if your matter specifically concerns your privacy or personal data (for example, requesting a data copy or deletion), it may be escalated to our privacy team or Grievance Officer to ensure proper handling.

11.3 Local Data Protection Authorities:

If you are not satisfied with our response to any privacy-related concern, and depending on your jurisdiction, you may have the right to lodge a complaint with your country’s data protection authority or equivalent regulatory body. For example, EU users can contact their local Data Protection Authority; in India, you might approach agencies under the IT Act or any Data Protection Board once established. We would appreciate the chance to address your concerns directly first, but you have this right.

11.4 Update Your Info:

If you need to update your personal information (like changing your email or phone number) and are unable to do so via the app, you can also contact us through the above support channels and we will assist in making the changes after verifying your identity.

11.5 Language and Communication:

We will communicate with you in [English/Tamil/Hindi/other supported language] regarding your queries. If you prefer another language, we will try to accommodate where possible or provide translation support.

Thank you for reading our Privacy Policy. We are committed to protecting your privacy and ensuring a safe and secure experience with Drivly. Your trust is important to us, and we welcome your feedback on any aspect of our privacy practices.

By using Drivly’s Services, you confirm that you have read and understood this Privacy Policy and agree to its terms. If you do not agree, please discontinue use of our Services.