1. Who we are and what this policy covers
UpDown helps people find and offer community shared rides. This policy explains personal information processed through our public website, mobile application, ride coordination and support. The operator and privacy contacts appear in the policy information panel above. Third-party services and other travellers are responsible for their own handling of information outside UpDown.
2. Information you provide
Account access: Your phone number, country code, authentication requests, verification results, internal account identifier and session tokens support sign-in and account security. Never share an OTP or authentication token.
Profile: We process the name, date of birth, gender, city, occupation, biography, photo, language and preferences you submit. Profiles can include ratings, completed-ride information and verification statuses. Add only details you are comfortable sharing in the community.
Vehicles and rides: Vehicle descriptions, registration details, pickup and destination addresses and coordinates, journey dates, departure times, routes, available seats, cost contributions, recurring schedules, requests and cancellation information support matching and ride management.
Communications: We process in-app messages, conversation participants, delivery/read information, notifications, ratings, reports and support correspondence so users can coordinate journeys and we can investigate issues.
Verification: If an available work-email check is used, we process the email address, verification token, expiry and result. If a document-verification feature is offered, its notice must explain the requested document, purpose and visibility before submission. Do not send Aadhaar or identity documents through ordinary support messages. A badge indicates a specific check, rather than a guarantee of identity, employment, driving skill or safety.
3. Device, location and website information
The App may process device and app identifiers, notification tokens, app version, operating-system information and permission choices. Location information selected or supplied by you helps identify pickup and destination points and routes. Device location requires the permission presented by your operating system; you can revoke that permission in device settings. Selecting a journey address still supplies its location to the service.
The website is a static information site. Its current code does not set cookies, use browser local storage, run advertising pixels or collect website analytics. Hosting and network providers may nevertheless receive IP addresses, requested URLs, browser information, timestamps and security logs. Links to app stores or other external services take you to services with their own policies.
4. Mobile analytics and service providers
The mobile App integrates Google Firebase for analytics, push notifications and remote configuration. Its current analytics implementation includes screen views, login and signup activity, an internal user identifier and ride events. Search events include origin, destination and travel date; publishing events include origin, destination, fare and seats; request/cancellation events include ride identifiers and cancellation information. These fields may reveal journey patterns. Website browsing does not trigger these App analytics events.
Mapping, geocoding and routing integrations process the locations needed for the feature you request. Email delivery supports work-email verification. Database, image storage, hosting and infrastructure providers process data needed to run the service. Actual providers and deployment locations depend on the production configuration. We do not represent that all data is stored exclusively in India. Cross-border processing must follow applicable law and relevant contractual safeguards.
You can read Google's privacy policy and Firebase's privacy information. Provider policies supplement this notice; they do not replace UpDown's responsibilities for the information it controls.
5. Why we process information
We use information to create and secure accounts, display profiles, search and publish journeys, manage seat requests, enable communication, send service notifications, process verification, maintain preferences, respond to support and privacy requests, investigate misuse and meet legal obligations. App usage information helps diagnose service problems and understand feature use.
Processing must have a lawful basis under applicable law. Where consent is required, it must be requested for the specific purpose. Reading this policy or visiting the website does not by itself provide consent to unrelated processing. Withdrawal may prevent a feature that needs the withdrawn data from working, but does not invalidate earlier lawful processing.
6. What other travellers can see
Ride coordination involves sharing profile and trip information with relevant users, including names, photos, ratings, verification status, vehicle information, pickup and destination details, times, seats and cost contributions. Conversation participants receive messages you send. The information displayed depends on the feature and ride stage. Do not put private financial credentials, exact home-access instructions or identity documents in profiles or conversations.
Other users can save or copy information they receive. UpDown cannot retrieve copies they keep outside the service. Report misuse through the contact page.
7. Other disclosures
Information may be processed by vendors supporting the purposes above, authorised personnel handling support or safety issues, and authorities when disclosure is legally required. Disclosure may also be necessary to investigate fraud, protect people or defend legal claims, subject to applicable law. A business transfer may involve relevant data and must remain subject to appropriate safeguards and notice requirements.
UpDown's current service has no integrated wallet or payment-processing flow. Do not submit card details or banking credentials to UpDown support. We do not use the current website to sell personal information or serve targeted advertising.
8. Retention and deletion
Account and profile information supports the account while it is used. Ride, conversation and request records may remain necessary for coordination, support, misuse investigations and legal obligations. Verification challenges have expiry controls. Expiry of a login or verification token does not by itself delete the related account.
The current product has no complete automated account-deletion workflow or verified production retention schedule. We therefore do not promise instant erasure, a fixed deletion deadline or automatic removal from every vendor and backup. A deletion or retention enquiry can be submitted using the privacy contact when available. We must explain what can be deleted, what needs to be retained and why, and any applicable legal response deadline. This limitation is material if you are deciding whether to create an account.
When implementing deletion, active databases, stored images, analytics identifiers, vendors and backups all need to be addressed. Information required for legal obligations or claims may be retained for that purpose, with access limited appropriately. Anonymised data that cannot reasonably identify you may be retained separately.
9. Your choices and requests
You can update available profile and vehicle information in the App, manage device permissions and notification settings, and stop using the service. Uninstalling the App does not delete server-side account or ride data.
Subject to the law in force, you may request information about processing, access, correction, completion, updating, erasure, consent withdrawal and grievance redressal. Send a clear request through the privacy contact listed above or consult Data requests and account deletion. We may need proportionate information to verify that the request concerns your account. Do not send an OTP, password, PIN or full identity-document image by email.
Some rights and obligations depend on the commencement of applicable legal provisions. We will not treat a right that has not commenced as already enforceable, and we will not limit rights that do apply. If a request cannot be fulfilled, the response should explain the reason and available escalation routes.
10. Age and safety
UpDown shared-ride accounts are intended for adults aged 18 or older. Children must not create an account or independently arrange rides through UpDown. If you believe a child has submitted information, contact the privacy channel so the matter can be investigated. This intended age policy does not represent that a technical age-verification check has been implemented.
11. Security
Account authentication, access controls and appropriate technical and organisational safeguards help protect personal information. No networked service can guarantee absolute security. Keep your device secure, protect sign-in credentials and report suspected unauthorised access. Where a breach triggers legal notification duties, affected people and authorities must be notified as required.
12. Complaints and changes
Use the privacy or grievance contact in the policy panel to raise concerns. Describe the issue and the remedy sought, and retain a copy of your request. Applicable legal response periods take precedence. You may use available statutory complaint mechanisms where eligible after following any required grievance process.
Changes to data practices require an updated policy and, where required, a fresh notice or consent. The effective date appears above; material changes should be brought to users' attention through an appropriate service channel.