A car-sharing account holds a driving licence, a payment method and a trip record. The email address on the account receives booking confirmations, licence verification, fines, tolls, damage claims and password resets. The protection is one dedicated alias per car-sharing service, tied to a personal inbox and kept live while the account exists. Signup collects a name, email address, phone number, driving licence details and a payment method, and the service keeps trip dates, times and locations.
Data held by a car-sharing account#
Signup for a car-sharing service collects more identity data than a typical account signup, because the service has to check that the person can legally drive its cars. Turo's privacy policy (last revised 31 October 2025) states that account registration requires a name, email address and password, and that profile data may include addresses, phone numbers, driver's licence number, date of issuance and issuing country or state, and date of birth. Identity verification data may include a photograph or scan of a driver's licence, passport or national ID card, and a driving record. Payment data includes bank account or payment card numbers, and trip data covers the date, time and amount of each trip.
Zipcar's membership contract (effective 31 July 2026) requires members to hold a valid driver's licence and authorises Zipcar to obtain driving records from the licensing jurisdiction. Members are billed by credit or debit card, and a past-due account may be suspended. The same contract states that some vehicles contain devices tracking location, distance travelled and fuel consumption.
Car sharing differs from ride-hailing in the data collected. A ride-hailing passenger hands over a payment method and a travel record, while a car-sharing driver also hands over a driving licence, and the account stays open to mail about fines and damage claims long after the last trip. The guide to protecting email when signing up for ride-hailing apps covers the passenger side.
Car-sharing breaches#
| Service | Breach date | Accounts affected | Data exposed |
|---|---|---|---|
| Zoomcar | July 2018 | 3.6 million addresses | Names, email addresses, phone numbers, IP addresses and bcrypt-hashed passwords |
| HopSkipDrive | June 2023 | 155,394 drivers | Names, email and postal addresses, driver licence numbers |
| Zoomcar | June 2025 | About 8.4 million users | Names, phone numbers, car registration numbers, addresses and email addresses |
| Times Car | September 2026 | About 6.6 million accounts | Names, addresses, dates of birth, phone numbers, email addresses, driving licence information and licence photographs |
Zoomcar breach of 2018#
In July 2018, Zoomcar lost the data of about 3.5 million users, including names, email addresses, phone numbers, IP addresses and bcrypt-hashed passwords, and CPO Magazine's report states that the stolen data was listed for sale on an underground hacking forum. Have I Been Pwned lists the 2018 Zoomcar breach at 3.6 million affected addresses, with the breach dated July 2018. The two counts differ because CPO Magazine reports people affected and Have I Been Pwned counts affected addresses.
HopSkipDrive breach of 2023#
HopSkipDrive confirmed a breach affecting 155,394 drivers, with driver licence numbers among the stolen data (TechCrunch, 5 February 2024). The company told TechCrunch it first discovered the breach on 12 June 2023, after finding suspicious activity on third-party applications it used, and a forensic investigation dated the incident between 31 May and 10 June 2023.
Zoomcar breach of 2025#
Zoomcar is a peer-to-peer car-sharing marketplace operating in about 100 cities across India, Egypt, Indonesia and Vietnam, and other Asian countries, according to CPO Magazine. Its Form 8-K filing with the US Securities and Exchange Commission, dated 13 June 2025, states that on 9 June 2025 the company identified unauthorised access, and that a third party accessed a limited dataset containing personal information of a subset of approximately 8.4 million users, including names, phone numbers, car registration numbers, addresses and email addresses. The filing states there was no evidence at the time that financial information, plaintext passwords, or other sensitive identifiers were compromised. CPO Magazine's report confirms the same figures. This was Zoomcar's second major breach, seven years after the 2018 incident.
Times Car breach of 2026#
Times Car is a Japanese car-sharing service run by Times Mobility, part of the Park24 Group. The company announced on 25 September 2026 that a third party had accessed its systems, and blocked the access the next day. Its second report on the incident, published 28 September 2026, confirmed that about 6.6 million accounts were affected, covering current and former members, incomplete applicants, and corporate business service members. The exposed fields are names, addresses, dates of birth, phone numbers, email addresses, driving licence information, identity-verification document images including licence photographs, account passwords, and linked service IDs. The report states that credit card information was not exposed. BleepingComputer's report on the same day confirms the same figures and the same field list.
The AliasFleet article on the Times Car breach lists every exposed field. A leaked password can be changed, while a photograph of a driving licence cannot be changed in the same way, so the image carries the longest exposure. Held next to a name, home address and date of birth, it is the kind of material used for identity fraud.
The address the account holds#
The email address on a car-sharing account creates three problems when it is the same address used everywhere else. The first is correlation. The same address on a car-sharing service, a bank account, a shopping account and a social account lets any one breach connect the accounts together. A separate address for every service breaks that link. The guide to whether a second email address is needed covers the general case.
The second problem is the phishing that follows a breach like Times Car. Whoever holds that database has a real name, a real address, proof of membership, and a photograph of a licence. A message claiming that licence verification needs updating, or that a damage claim is outstanding, carries the details from the breach. When that address is an alias used only for that service, the alias names the source, and the address can be paused or replaced once the account is safe.
The third problem is volume. Every trip brings a confirmation and a receipt, plus service updates and promotions. A dedicated address keeps that mail in one place, separate from the main inbox. The guide to what to do when an alias starts getting spam covers the sequence: identify the source, create a replacement, update the account, then pause or delete the old alias.
One alias per car-sharing service#
The setup is one alias for each car-sharing service, each forwarding to the same personal inbox. Turo gets one alias and Zipcar another, each forwarding to the same inbox. If Turo is breached, the exposed address is the Turo alias, which no other service holds, so it reveals nothing about the account holder's other accounts. The alias can be paused or replaced. The recovery path stays open as long as the alias forwards to an inbox the account holder controls.
Booking confirmations, receipts, fines and damage claims arrive at the car-sharing alias, and a filter sorts them without any rule touching the main inbox. Email two-factor codes also work through an alias. The guide to receiving two-factor codes at an email alias covers the timing and the cases where a service insists on SMS. An alias does not replace a password or a second factor; it limits what a breach exposes.
Short-lived addresses#
A short-lived address is the wrong tool for a car-sharing account, because the mail that matters arrives after the trip. Licence verification, fines, tolls and damage claims all need a reachable address, and some arrive months after the trip. An address that stops working after a week or a month leaves the account with no route for those notices, and a missed damage claim typically turns into a larger bill. Account recovery runs through the same address: a forgotten password is reset by a link sent to the address on file. The guide to using an email alias for account recovery covers the general rules.
The alias should therefore be a managed, persistent address that stays live for as long as the account exists. This is not a disposable email setup: it is a permanent forwarding identity for one service, with pause and delete controls.
Moving an existing account to an alias#
A driver who already signed up with a personal or work address can change it in the service's account settings, and in most cases the service verifies the new address before the change takes effect. The new alias is created and tested before the change, so the verification code arrives somewhere the account holder can read it. Only then is the address on the car-sharing account changed, with the old address left in place until the new address is confirmed. A work address should be moved while it still works, because it is deactivated when employment ends.
AliasFleet and car sharing#
AliasFleet provides managed, persistent email aliases that forward to a verified destination inbox. A driver creates one alias per car-sharing service, for example one for Turo and one for Zipcar, each forwarding booking confirmations, fines, damage claims and password resets to the same inbox. An alias that starts receiving spam can be paused, and a breached alias can be replaced while the account moves to a fresh address. AliasFleet does not store the driver's password, does not replace two-factor authentication, and does not prevent a car-sharing service from being breached. Pricing starts with a free tier of 10 active aliases, and the docs cover setup.
An alias does not protect the rest of the account. The service still holds the phone number, payment details, licence data, location history and trip record, and none of that changes when the email address changes. A breach of the service exposes the trip data regardless of which address is on the account, as the Times Car and Zoomcar cases showed. The alias limits the exposure of the email address itself and keeps the account holder's accounts from being linked through a single shared address. It does not stop the service collecting the data, or phishing mail that uses details from a breach. The remaining controls are a unique password, two-factor authentication where the service offers it, and a check of known breaches. A driver who suspects the address on a car-sharing account has appeared in a breach can check it against Have I Been Pwned, which lists the 2018 Zoomcar breach. The guide to what to do when an email is in a data breach covers the steps that follow.
