Privacy Policy

1. Who this policy covers

Codejera Company operates the Jera Taxi customer and driver apps and their supporting services. This policy explains how we handle information about customers, drivers, and people who contact us. It also covers this public policy website.

The information collected depends on your role, the features you use, the app version, and the permissions you grant.

2. Information we handle

• Account and profile: name, phone number, username, email if provided, profile photo, account identifiers, verification status, and login information. Passwords are stored as hashes.
• Driver and vehicle: driving licence number, verification documents you submit, vehicle details, registration or plate number, photos, approval status, availability, ratings, and completed trips.
• Location and journeys: pickup and destination coordinates and addresses, saved places, driver GPS positions and route points, and related movement information such as speed, bearing, accuracy, and timestamps when supplied.
• Ride and communication records: requests, offers, fares, trip status and history, cancellations, receipts, in-app messages, ratings, feedback, and safety or SOS reports.
• Wallet and payment records: balances, top-ups, charges, commissions, transaction references, payment status, and refunds or adjustments where available. Payment information submitted directly to a payment provider is also handled under that provider’s policy.
• Technical and support information: notification tokens, device platform, IP addresses and request or security logs, information you send to support, and crash diagnostics where crash reporting is enabled.

3. How we use information

We use this information to create and secure accounts, verify drivers, find nearby drivers, arrange and track rides, enable communication, maintain wallets and receipts, send service notifications, respond to support and safety reports, prevent misuse, resolve disputes, and meet applicable obligations. Crash diagnostics help us investigate failures and improve reliability.

Jera Taxi does not display in-app advertisements. We do not use the information described in this policy to serve targeted advertising.

4. Location and background access

Customers: location helps select a pickup point, show nearby drivers, and support an active journey. Pickup and destination information you enter is stored with your ride records.

Drivers: precise location is used while you are online or carrying out a ride to match requests, estimate arrival, show trip progress, and support safety and trip records. In app versions with background location enabled, updates may continue while the app is in the background or the screen is off during these activities, subject to device permissions and operating-system restrictions.

Assigned ride participants and authorised operations staff may see location relevant to a journey. Customers viewing nearby available drivers receive approximate discovery positions; assigned-ride tracking can use precise positions.

You can change location access in device settings. Drivers can also go offline to stop offering availability. Restricting location access may prevent matching or trip tracking. Going offline or revoking permission does not erase previously stored trip locations.

5. When information is shared

• To provide a ride: relevant customer and driver details, pickup and destination information, vehicle information, messages, ratings, and trip location may be shared with the other participants as needed.
• For service operations: authorised support, dispatch, verification, and administration personnel can access records needed for their work.
• With service providers: hosting and storage providers, including Oracle Cloud; mapping services; Google Firebase for enabled diagnostics or push delivery; Apple for enabled push delivery; and authentication, SMS, or payment providers when you use those features. They process the information needed to deliver those services.
• For protection or legal obligations: information may be disclosed when needed to investigate misuse, handle safety incidents or disputes, protect rights, or respond to a valid legal requirement.

Profile and vehicle photos are intended for display in the service and may be viewable by anyone who has their direct image link. Do not upload identity documents as a profile or vehicle photo.

Cloud and service-provider processing may take place outside your country. Their services may also have their own privacy notices.

6. Firebase Crashlytics

App versions that enable Google Firebase Crashlytics send crash reports to Google to help diagnose faults. Reports can include stack traces, app state and version, device and operating-system details, crash times, and installation identifiers. This is reliability reporting, not advertising.

Google states that Crashlytics keeps crash traces and associated identifiers for 90 days before beginning removal from live and backup systems. See Firebase’s privacy information and Crashlytics data-collection details. Contact us with questions about diagnostic information relating to your app installation.

7. Permissions and your choices

Where used, location permissions support maps and rides; camera or photo access lets you submit profile, vehicle, or verification images; and notifications deliver trip and account updates. Device settings let you change permissions. Some features will be unavailable when their required permission is denied.

Optional account details can be left blank where the app permits. You may ask us for access to or correction of information, or request deletion, using the contact below. Available rights and any exceptions depend on applicable law. We may verify that a request comes from the account holder.

This website uses browser storage or cookies for language and appearance preferences. Visiting the website also sends normal request information, including your IP address, to hosting and font-delivery services. It does not use advertising cookies.

8. Storage and retention

Account, profile, driver, journey, communication, wallet, and safety records are stored to operate the service and handle support, accounting, security, and disputes. Live availability information and temporary location buffers are distinct from saved journey records; the expiry of a live update does not erase recorded trip history.

Deactivating an account does not automatically erase these records. Verified deletion through our public account-deletion page removes the account and personal profile data and de-identifies retained historical records. Information may need to be retained for applicable legal, accounting, fraud-prevention, safety, or dispute-resolution reasons. We can explain which categories must be retained when responding to a request.

Copies can remain in existing backups until those backups are deleted or replaced. Crashlytics has the separate retention process described above.

10. Security

We use measures such as HTTPS connections, hashed passwords, authenticated access, and role-based controls to protect information. No online service can guarantee absolute security. Keep your login credentials and verification codes private, and contact us if you suspect unauthorised access.

11. Children and young people

Jera Taxi’s account-based customer and driver services are not directed at children. Drivers must meet the applicable licensing requirements. If you believe a child has supplied personal information inappropriately, contact us so we can investigate and address the information.

12. Changes and contact

We may update this policy as the apps or data practices change. The date above identifies the current version. Material changes may also be communicated through the app where appropriate.

For privacy questions, requests to access or correct information, account and data deletion, or concerns about this policy, contact: