Aero Call Taxi & Aero Driver

Delete your Aero account

Delete an Aero Call Taxi Customer account (listed on Google Play as Aero Call Taxi - Karur) or an Aero Driver account (listed on Google Play as Aero Taxi Driver) and associated personal data. Both apps are published on Google Play by Enthiraa Softwares; the taxi service itself is operated by AERO CALL TAXI & TAXI SERVICE.

Effective: 17 November 2026

Start your request without the app

No app installation or sign-in is required.

Customer account

Aero Call Taxi

Email a Customer deletion request
Driver account

Aero Driver

Email a Driver deletion request

The buttons open an email composer. Send the email to initiate your request; opening the composer does not delete an account.

If a button does not open an email app, write to aerocalltaxi@gmail.com from any email service. Include:

Customer and Driver accounts are separate. A request applies only to the app account identified in it. Deleting one does not delete the other; submit a separate request for each if you want both deleted.

Keep your credentials private. Do not send OTPs, passwords, payment-card details or identity-document scans in the initial request. Support will explain an appropriate ownership-verification process. A legitimate support request does not ask you to forward a login OTP.

Customer: delete through the app

  1. Open Aero Call Taxi → Profile → Privacy & Legal → Delete account.
  2. Review eligibility, any outstanding ride/payment blockers and the retention information.
  3. Tap Delete account and confirm the popup. Cancel keeps your account. No OTP is required.
  4. Wait for a confirmed completed result. A pending/failed request or uncertain connection is not proof of deletion; use the app’s retry/recovery flow or contact support.

Driver: request support-assisted deletion

  1. Open Aero Driver → Profile → Privacy & Legal → Request account deletion.
  2. Choose the email request option or copy the support email.
  3. Identify your Driver account and send the request. Support verifies ownership and processes it. The email button does not instantly delete the account.

Verification, timing and blockers

Customer accounts are deleted immediately when the confirmed in-app deletion completes successfully. Email deletion requests are completed within one week, following account-ownership verification. The current Driver in-app option initiates an email request, so the email timeframe applies to that route. A pending or failed response is not confirmation of completed deletion.

If an active ride, unsettled payment or dispute prevents immediate in-app completion, you can still initiate a request through the email route above. Support will explain the steps and any retained records. Uninstalling, logging out or temporarily disabling an account does not request permanent deletion.

What deletion changes

When Customer deletion completes, account-profile names, phone numbers, email, date of birth, address and emergency-contact fields are removed or replaced. Saved-address rows remain, but their labels, address text and coordinates are cleared and they are disabled. Notification tokens are cleared and registrations are disabled. Raw device identifiers are replaced; active sessions are revoked. Internal record and relationship IDs remain. Deletion applies to the identified Customer account, not a separate Driver account or another tenant.

Linked login/device and Customer messaging identifiers are also redacted while their history rows remain. The deleted Customer’s copied trip-contact details are redacted without erasing a different passenger’s or Driver’s details. Driver support-assisted processing separately handles the verification/document and emergency-contact information described below. The request applies to the named app account, not automatically to both.

What may remain and for how long

Customer account deletion preserves history rows and redacts identifying fields as described below. Trip/GPS, financial, login/security and linked messaging history have no automatic expiry. Internal account/trip links, locations, timestamps, statuses, amounts and delivery references remain. These records are not fully anonymous. Provider copies, incoming/unlinked messages, support emails and backups have separate handling; contact us about a specific request.

Account and profile
When Customer deletion completes, account-profile names, phone numbers, email, date of birth, address and emergency-contact fields are removed or replaced. Saved-address rows remain, but their labels, address text and coordinates are cleared and they are disabled. Notification tokens are cleared and registrations are disabled. Raw device identifiers are replaced; active sessions are revoked. Internal record and relationship IDs remain. Deletion applies to the identified Customer account, not a separate Driver account or another tenant.
Driver verification documents
For a completed Driver deletion request, support also processes deletion of the submitted Aadhaar/licence details, uploaded verification images and emergency-contact details. Driver deletion is support-assisted; sending an email is not confirmation that this work has finished.
Trips, fares, payments and earnings
Trip, fare, payment-status, earnings and accounting history remain without automatic expiry for service records, reporting and dispute handling. Record IDs, relationships, timestamps, statuses and amounts remain. The deleted Customer’s name and phone copied into self-trip contact fields, or passenger contact fields identifying that Customer, are redacted. Another passenger’s or Driver’s details are not automatically erased by that Customer’s deletion. Retained records can still be identifiable through locations, internal links and other information; they are not fully anonymous.
Trip GPS and routes
Pickup/drop locations and recorded trip GPS/routes remain with trip history without automatic expiry. They are not cleared by Customer account deletion and may still identify a person. Access remains subject to account, role and tenant controls; removing profile/contact details does not make location history anonymous.
Login messages and security records
Linked Customer login OTP rows, session/device records, messaging outbox rows and delivery-attempt history remain without automatic expiry. On completed Customer deletion, login phone/device identifiers and code-verification material are redacted, messaging recipient numbers and encrypted queued OTP content are cleared or replaced, and unsent linked messages are stopped. History retains internal IDs and relationships, purposes, timestamps, statuses and delivery references. One-way session-device proofs preserve completed-deletion response retries only while the original signed access token is valid. Correlated WhatsApp delivery events have recipient identifiers redacted; incoming or unlinked provider events can require separate verified support handling. This does not erase a Driver login using the same phone, another tenant’s records, or messages already received on a phone.
Support and deletion emails
Support and account-deletion emails sent to aerocalltaxi@gmail.com are deleted after the request has been handled.
Crash reports
Firebase Crashlytics retains crash stack traces, extracted crash data and associated installation identifiers for 90 days before starting removal from its live and backup systems, according to Firebase’s published privacy information. This provider retention is separate from deletion of the Aero account profile.
Performance diagnostics
Performance and other technical diagnostics are handled under the relevant service provider retention settings and policies. The Crashlytics period below is not a retention promise for every performance or messaging record.
Database backups
Database backups are retained for 30 days and then deleted. Historical copies of personal details removed from the live database may remain in those backups until the relevant backup is deleted, for up to 30 days.
Provider and recipient copies
Account deletion does not recall WhatsApp/SMS already received on a phone or erase a person’s own email copies. Providers process and retain service data under their policies. Contact us about provider-held data associated with our service so we can handle or coordinate the request where applicable.

Messages and service-provider data

WhatsApp/Meta delivers login and enabled trip messages; SMSGatewayHub and telecom networks deliver SMS OTPs. Deleting an Aero account does not recall a delivered message or erase copies you or another recipient keep. Contact us about service-provider data associated with your request so we can handle or coordinate it where applicable. Crash/Performance retention is separate from profile deletion.

Follow up or raise a concern

We confirm the outcome and explain applicable retention exceptions. If you have not received a response, reply to your request or email aerocalltaxi@gmail.com with the app account type and original request date. Do not include a login OTP. Read the privacy policy for both apps for collection, permissions and provider information.

Contact

Aero Call Taxi and Aero Driver are published on Google Play by Enthiraa Softwares. The taxi service is operated by AERO CALL TAXI & TAXI SERVICE
168/4, Anna Nagar 2nd Cross, Thanthonimalai, Karur, Tamil Nadu 639005
Privacy and deletion contact: aerocalltaxi@gmail.com