AbraidInformation used to provide rides
Abraid processes information you provide and information generated when you use its features.
- Account details: email, name, account role, authentication records, optional phone number and profile photo.
- Ride details: pickup and destination addresses and coordinates, driver location, trip status and times, fares, cash-payment records, receipts and ratings.
- Communications: ride chat, cancellation reasons, rating comments, safety reports and blocks, and information you send when requesting support.
- Driver applications: driving-licence details, uploaded documents, vehicle information and application-review decisions.
- Technical information: notification tokens, device or installation identifiers, service activity and diagnostic information handled by the app or its providers.
Location and permissions
Location supports pickup selection, matching and trip progress. When a driver goes online or is on a trip, Abraid sends the driver's location to its service and shares relevant trip location with the assigned passenger. This can continue while navigation is open or the phone is locked. Going offline outside an active trip stops driver location sharing.
You can change location, camera, photo and notification permissions in your device settings. Restricting permission can prevent the corresponding feature from working. Notification permission controls are not a guarantee that all provider identifier collection stops.
Who receives information
Eligible drivers receive request and route information for matching. Assigned passengers and drivers receive the information needed for their trip, including names, profile photos, vehicle details and chat. Verified phone contact is available only during an active trip. Profile photos are served through public image URLs; driver documents are restricted to their owner and authorized administrators.
Google Maps, Places and Routes process map activity, destination searches, selected places and route coordinates. Google and Firebase SDKs also process identifiers, usage and diagnostic information for service operation and their own analytics purposes. Firebase Cloud Messaging and Apple's push service support notifications, which can contain trip information. This processing is separate from whether a notification successfully reaches your phone.
Verification, password-reset and account-deletion codes are emailed through Zoho Mail, which processes the destination address and message content. When SMS phone verification is enabled, Twilio processes the phone number and message. Hosting and storage services process information needed to run Abraid. Provider processing and retention are also governed by their own applicable policies.
Security and access
Connections between the app and Abraid are encrypted in transit. Account sessions use secure device storage, and access controls restrict ride conversations and private driver documents. These measures do not guarantee that every risk is eliminated.
You can update available profile fields in the app and delete your account yourself under Account & help. For access or correction requests, use the contact address above. We may need information that verifies ownership of the account. Do not send your password or verification codes.
Retention and deletion
Account information is kept while your account is active. You can delete your account at any time in the app under Account & help → Delete account; you confirm with a code sent to your account email. If you no longer have the app, email elmoctarsalemabeye09@gmail.com from your account’s address. An active ride must be finished or cancelled first.
Deletion immediately removes your sign-in, name, phone number, profile photo, driver documents, vehicle details, notification devices and blocks. Trip addresses, chat messages, rating comments and report descriptions are kept for 30 days so we can handle cash fare disputes and safety reports, then they are permanently erased. Fare amounts, trip dates, star ratings and internal identifiers remain only in anonymous accounting and safety records.
Backups and provider records, such as emails already delivered, are not necessarily removed at the same moment; they expire under the providers’ and our own backup schedules.