Last updated: October 27, 2026
This policy explains how Alpha Rotto Private Limited (“Rotto”, “we”, “us”) handles personal data when you use rotto.one, the Rotto customer app, or our vehicle service. It covers the mechanic app where it handles your booking, vehicle, or service evidence. The mechanic app also handles workforce account and job activity described below. This policy should be read with the notice shown when a feature asks for information or permission.
Depending on the feature you use, we may handle:
Contacts access is optional and is used only if you open the address contact picker. You do not need to share your address book to use Rotto.
We share information needed for the stated purpose with mechanics and service partners assigned to your booking; payment, OTP/messaging, maps/geocoding, hosting and media-storage providers; analytics and advertising measurement providers described below; and authorities or other parties where law requires it or where needed to protect people, rights, safety or the service.
Rotto’s code and configuration use Google Tag Manager, Meta Pixel and Meta Conversions API for website measurement, and may load Microsoft Clarity when enabled for the environment. Rotto also uses Razorpay for checkout, Firebase services for push and diagnostics, Google Maps/geocoding services, and cloud object storage. A provider may process data under its own terms and privacy practices. We do not sell personal data for money.
After you enable advertising measurement in the website’s Privacy choices, Rotto loads Google Tag Manager and sends interaction and booking events to its data layer. The production website uses Meta Pixel; its server-side Meta Conversions API purchase path is used when enabled by the backend configuration. Microsoft Clarity may load only if you enable analytics and it is configured for the environment; it can collect website interaction and session data. The website also prepares Google conversion and enhanced-conversion event data; whether the active Tag Manager container forwards those events to Google Ads depends on that separate container configuration.
Events can include page path and title; service or package identifiers and labels; category or option; quantity; amount and currency; booking type; schedule selection; payment category; transaction or order reference; login method; and whether a vehicle or address was added. The code prepares hashed name, phone and account identifiers for matching; city, state, postal code and country may also be included. Hashing does not make these identifiers anonymous. Meta server-side purchase measurement can also receive browser click/browser identifiers, IP address, user-agent, order amount and service details.
You can accept or reject optional tags, choose analytics and advertising measurement separately, and change your choice later using Privacy choices in the website footer. Optional tags do not load before a choice; rejecting or withdrawing advertising measurement stops future website event pushes and purchase measurement. Essential app and booking functions do not depend on optional tracking. Analytics events must not include OTPs, full addresses, vehicle registration numbers, free-text notes, card/UPI credentials, or precise location.
For more information, see Meta’s Privacy Policy, Google’s Privacy Policy, and Microsoft’s Privacy Statement. You can manage browser cookies in your browser and advertising preferences with those providers. Those controls do not replace Rotto’s responsibility to provide an appropriate in-product choice where required.
The mechanic app is for authorized mechanics and operations staff. It handles workforce account and role information, job assignment and status, customer and vehicle details needed for a job, and location and media evidence captured during job tasks. Some evidence can be queued on the device for upload when connectivity returns. Access to customer information and evidence is limited by job and role permissions. Rotto uses workforce data to provide and verify services, support operations, investigate issues and protect service quality.
Mechanics and operations staff can read the separate Rotto Mechanic App Privacy Notice for more detail.
Rotto plans to add Meta and Google event measurement to the customer app. The recommended event set is limited to app open, service viewed, add/remove from cart, checkout started, payment method category selected, payment success/failure, coupon applied as a yes/no event, pickup or doorstep selected, instant or scheduled booking selected, booking confirmed, and support flow opened. These events should use service/package identifiers and coarse values only. They must not include contact details, account identifiers, precise location, registration numbers, free text, payment credentials or exact appointment timestamps. The app integration is not present in the code reviewed for this policy update; before it is enabled, Rotto will provide an in-app notice and choices and update the app-store disclosures. If data is linked across other companies’ apps or websites for advertising or ad measurement on iOS, Apple’s App Tracking Transparency permission will be used.
After identity verification and when no active booking, unresolved settlement, payment link or refund prevents deletion, we aim to remove or anonymize customer profile information, saved vehicles and addresses, cart data, sessions and registered push-device records within 30 calendar days. Completed service orders are unlinked from the customer account and their direct contact, address and vehicle identifiers are cleared from the service snapshot. Payment records are unlinked from the customer account. Invoices and transaction details required for accounting, legal or dispute handling may be retained. We acknowledge privacy requests within 2 business days. Identity is verified using an OTP sent to the phone number registered to the account; never send an OTP by email.
Original job-location data is retained for up to 90 days and original service photos for up to 180 days for service delivery and support. Rotto plans to use these data types for internal route optimization and model training in the future; this use is not active today. Before using data for that purpose, Rotto plans to create a separate training copy, remove customer account, contact and order links, redact visible registration plates and faces, strip photo EXIF metadata, and reduce location precision to what the model needs. If introduced, these separate copies may remain after account deletion for up to 3 years from creation, with an annual review and earlier deletion when no longer needed. The 3-year period and safeguards are subject to privacy-counsel review before training begins. A training copy may still show a vehicle or place and may not be anonymous in every context.
Test-drive video/audio, diagnostic logs and crash reports are retained for up to 90 days; and data deleted from active systems is scheduled to age out of backups within 90 days, except for any future training copies retained under the separate 3-year period. An active service, complaint, dispute, security incident or legal hold may require longer retention. Push tokens are removed when the device is unregistered or the account is deleted.
We retain a minimal record of privacy requests and their handling for 3 years to document and manage the request.
Order, invoice, voucher and accounting records are retained for their applicable legal period. The current operational schedule is 8 financial years for accounting books and vouchers, and at least 72 months from the relevant annual-return due date for GST records, or longer during proceedings. Finance/legal review must map these periods to each record class and verify applicable statutory requirements before store submission; a legal hold or longer mandatory period takes precedence.
You can request deletion of your customer account in the Rotto app. Deletion is blocked while a booking, settlement, payment link or refund is still in progress; the request can be submitted meanwhile and the 30-day period starts when it is verified and eligible. If you no longer have the app, use the account and data deletion request page.
Mechanic accounts are provisioned for workforce access. A mechanic who leaves or no longer needs access should contact Rotto to deactivate the account and request handling of associated personal data. Job, audit and financial records may need to be retained for operational or legal reasons.
You can correct information in your profile where the app provides that option, deny optional device permissions, and manage notification permissions in device settings. For access, correction, deletion, consent withdrawal, or a privacy complaint, contact support@rotto.one or call +91 75175 19292. We acknowledge requests within 2 business days and aim to complete verified and eligible deletion within 30 calendar days. We verify account requests by OTP to the registered phone number, never by asking you to email the OTP. Records subject to a legal, accounting, service or dispute hold may remain for the applicable period.
We use access controls and security measures intended to protect information. No online service can promise perfect security. Rotto’s services are intended for people aged 18 and over; please do not use them on behalf of a child or provide a child’s personal data.
Service providers may process information in locations outside your state or country. We use safeguards required by applicable law and our provider arrangements. We do not rely on blanket consent to international transfers.
We will update this policy when our data practices change and show the revised date here. For privacy requests and complaints, contact Alpha Rotto Private Limited at support@rotto.one or +91 75175 19292. Contact address: VJRQ+XGX, Kudlu Gate, Munireddy Layout, Hosapalaya, Muneshwara Nagar, Bengaluru, Karnataka 560102.
