Privacy policy

1. Data and purposes

• Account and contact: Full name, email address, phone number if provided, user identifier, language preference, profile photo, and session/verification records. Used to create and protect accounts, provide email-code sign-in and support. Sign-in codes are sent by email.
• Membership verification: Passengers provide an identity document; drivers provide an identity document, driving licence and vehicle registration. Both roles provide three photos taken from the front, right and left. Vehicle make/model, plate and the driver's selected service regions are also processed. Documents and photos are available to authorized BinGel staff for manual membership and driver-eligibility review. This flow does not perform automated face matching or liveness testing. Trip features remain unavailable until approval.
• Location and trips: Permitted precise or approximate location, selected pickup/destination, saved addresses, route, distance, duration, trip status and history. Used to match nearby eligible drivers, arrange meeting, follow the trip and calculate trip information.
• Communications and user content: Trip chat, comments, ratings and support requests. Used for trip communications, service support and dispute review.
• Device and security: App role/version, device and operating-system information, IP address, session details, notification device identifier/token, notification preferences and security records. Used for session security, abuse prevention and notifications you allow.
• Trip and access records: Trip-fare calculations, driver-access entitlements and administrative actions are recorded. Passenger payments are not collected through the app; this version does not collect card details and in-app driver payment collection is not enabled.

2. Location, camera and notifications

With permission, the passenger app uses your location to find a pickup point while you use the app. It does not request background location permission. The driver app uses location while you are online to show suitable requests.

Driver background location: With your additional permission during an accepted trip, BinGel Driver collects precise location and sends it to the BinGel server even while the app is in the background or the screen is off. It is used to show your approach and journey to the matched passenger and to record distance and duration. Background tracking for that trip stops when it is completed or cancelled. Before enabling background tracking, the app displays an explanation and asks for device permission.

Camera permission is requested when you choose to take a document photo or selfie. Gallery and file selection upload only the content you select; broad access to your photos or files is not requested. Notification permission and the in-app notification preference are used for trip, account and general announcements. You can manage permissions in device settings; some features may be unavailable without the relevant permission.

3. Who receives data?

Profile, vehicle, meeting and location information needed for a trip is shared between the passenger and driver involved in that match. Trip messages are delivered to the other participant. Identity documents and the three verification photos are not displayed to the other passenger/driver; authorized review staff can access them.

Hosting and storage, SMTP email, Google Maps mapping/routing/address services and Google Firebase notifications may process data needed to provide their functions. Their infrastructure may be located in different countries. Necessary records may be disclosed to competent authorities for safety, disputes or legal obligations. We do not sell personal data.

4. Retention and account deletion

Account and service data is retained while the account is active and for as long as needed to provide the service. Identity documents and verification photos are associated personal data and are included in a deletion request.

You can request deletion in the app or by support email. An in-app request closes account access and ends sessions; this confirmation does not mean all personal data has been erased immediately. Support processes the request through ownership verification and review of the relevant records.

Under our published deletion process, once required ownership verification is complete, the account and associated personal data are deleted or anonymized from active systems without undue delay, generally within 30 days. Completion is communicated through the contact channel used for the request. Support will explain any delay or required retention.

Specific records required for tax, payment, fraud prevention, safety, an open dispute or another legal obligation may be kept with restricted access only for the applicable obligation period. Technical backups are removed in the ordinary backup/deletion cycle. Contact support for the retention conditions applicable to your request and its status.

Deletion removes identity documents and verification photos, contact details, location/route details, messages and reviews. The other participant keeps only a monthly summary of completed/cancelled status and journey count. It does not contain the deleted person's name, account or journey ID, location or messages.

See account and data deletion options →

5. Security and your choices

We use measures including HTTPS communications, session authentication, authorization checks and restricted document-file access. No system can guarantee absolute security. For access, correction, deletion or other personal-data requests under applicable law, contact destek@bingelapp.com. Necessary and proportionate information may be requested to verify ownership.

6. Changes

This policy is updated when the data processed or app functions change. Material changes will be communicated through the app or another appropriate channel. The date above identifies the latest update to this text.