Aero Call Taxi & Aero Driver

Privacy policy

One privacy policy for Aero Call Taxi (Customer app, listed on Google Play as Aero Call Taxi - Karur) and Aero Driver (Driver app, listed on Google Play as Aero Taxi Driver). Both apps are published on Google Play by Enthiraa Softwares; the taxi service itself is operated by AERO CALL TAXI & TAXI SERVICE in Karur and the service areas we support.

Effective: 17 November 2026 · Contact: aerocalltaxi@gmail.com

Need to delete an account? Both apps use the same account-deletion request page. You can request deletion by email without installing or signing in to either app.

Which app do you use?

Aero Call Taxi

Customer app. Listed on Google Play as Aero Call Taxi - Karur, published by Enthiraa Softwares. Book rides, choose pickup/drop locations and manage trips.

com.enthiraa.customer

Aero Driver

Driver app. Listed on Google Play as Aero Taxi Driver, published by Enthiraa Softwares. Complete verification, receive assignments, operate rides and view earnings.

com.enthiraa.driver

A feature or permission described for one app does not mean the other app uses it. 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.

Information used by the Customer app

Information used by the Driver app

Driver location when the app is not in use

Aero Driver collects and sends location while you are online or on a trip, including when the app is in the background or not in use, to find nearby ride requests, update passengers and record trip routes. These core ride features use background location and a visible location-service notification. We do not send precise trip coordinates to the advertising SDK through these features.

Recorded points may be saved on your device during network loss and uploaded later, including after trip completion. Going offline or revoking permission stops future access as applicable; it does not erase points already recorded. Manage on-duty status in the app and location permission in device Settings.

WhatsApp and SMS verification

We send requested signup/login OTPs to your registered phone through WhatsApp (Meta). When WhatsApp delivery fails or is not confirmed in time, the same code may be sent through SMSGatewayHub and mobile network operators as SMS fallback. A service configuration may use SMS directly when WhatsApp is unavailable. Codes are for the signup/login action you requested, not marketing.

These providers process the destination phone number, verification message containing the code, delivery identifiers, timestamps and status/error information needed to send and troubleshoot it. A send acknowledgement does not guarantee handset delivery. We do not ask you to forward the code to support.

Receiving these messages does not require either app to read your SMS inbox or call history. Enter the code in the app. Customer account deletion uses a confirmation popup with no OTP; the ride-start PIN is a separate in-app trip credential.

Where enabled, WhatsApp also sends booking confirmations and final-fare messages for staff-created bookings. These messages can include the booking reference, pickup/drop details, time or fare. Our current SMS integration is for login OTPs, not those trip messages.

Technical information and service providers

Both apps use installation/device identifiers, notification tokens, app/OS/device details, crash logs, performance measurements and relevant network/diagnostic information for notifications, account security and reliability. Support requests contain the contact details and information you choose to send. Payment-status and trip-accounting records do not mean the apps collect your card number or bank login credentials.

Firebase Crashlytics and Performance Monitoring

Both Aero Call Taxi Customer and Aero Driver use Firebase Crashlytics to diagnose crashes and reported application errors, including handled failures. Reports can contain error types, stack traces, technical app/device information and installation identifiers. Firebase Performance Monitoring helps identify slow app startup and network operations using timing measurements, response codes and technical app/device information.

Our custom diagnostic reports and measurements do not attach your name, phone number, email, ride locations, OTPs, API request bodies or authorisation headers. Custom network measurements use fixed route templates without ride IDs or query values. Firebase SDKs also process technical information under their own privacy practices. Collection defaults, available choices and retention are described below.

Driver advertising, when enabled

A Driver build with advertising enabled can request non-personalised Google AdMob banners after the applicable Google consent checks. Non-personalised ads still involve processing: the SDK may use IP address (which can indicate approximate area), advertising/app/device identifiers when available, ad interactions and diagnostic data for ad delivery, measurement and fraud prevention. This is separate from the precise location collected to operate rides. The Customer app does not use this Driver ad feature.

Where required and available, use Aero Driver → Profile → Privacy & Legal → Ad privacy choices to review the Google privacy-options form. Device advertising settings may also be available.

Why information is used

To authenticate accounts; verify Driver/vehicle eligibility; search places and provide quotes/bookings; dispatch and operate rides; notify participants; calculate/display fares and earnings; keep service and accounting records; respond to support, feedback and deletion requests; diagnose faults; and address security, misuse and disputes. Driver advertising uses the separate data and purposes described above.

Permissions and choices

Account deletion and retained records

Customer in-app: Profile → Privacy & Legal → Delete account, then review and confirm the popup. No deletion OTP is required. Driver in-app: Profile → Privacy & Legal → Request account deletion, which opens a support email request. Both accounts can also be requested through the shared deletion page without the app.

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. 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.

Customer deletion redacts personal identifiers while retaining history rows. Trip, accounting, login, security and linked messaging history remain without automatic expiry. Personal/contact identifiers are removed or replaced as described below. Internal relationships, trip locations, GPS/routes and delivery references remain, so retained data is not fully anonymous. Driver support-assisted deletion remains a separate process.

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.

Contact aerocalltaxi@gmail.com about access, correction, deletion, retention exceptions or a privacy concern. We verify ownership before disclosing or changing account information. For provider-held data associated with our service, we handle or coordinate the request where applicable; we do not promise that providers or recipients automatically erase every copy when an Aero account is deleted.

Security and provider information

Current release configurations use HTTPS for our API and WSS for live app updates. Messaging-provider calls use HTTPS. Account authentication and role/access controls limit access; queued OTP content is encrypted and login codes are stored for verification as hashes. No system guarantees absolute security.

Providers may process information in locations where their services operate. Read WhatsApp’s privacy policy, SMSGatewayHub’s privacy policy, Google’s privacy policy and Firebase privacy information for their practices.

Intended users and changes

Account holders for both Aero Call Taxi and Aero Driver must be aged 18 or over.

We update this policy when practices change. The effective date identifies this version. Material changes will be communicated as appropriate.

Privacy 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