Help
This policy describes information handled by the Buruh public website, the Buruh Rider app, the Buruh Driver app, and the staff admin console. It follows what those products do today.
Buruh is the name used by the ride apps and this website. The public pages are Home, About, Services, Contact, this policy, and the terms. Rides are requested in Buruh Rider and driven in Buruh Driver. Authorized staff review the same trip records in the admin console.
The products do not publish a registered company name, a postal address, or a legal jurisdiction. Those details are listed under Needs confirmation. They are not filled in here.
Rider account. A rider can register with email and password, a phone number and one-time code, or Google sign-in. The rider profile stores the account id, name, email, phone number, profile photo address when Google supplies one, the sign-in method, the date the profile was created, and a rating. The password stays with the sign-in service. The rider profile does not store it. Buruh Rider does not ask the rider to upload a photo from the camera or photo library.
Driver account. A driver registers with email and password, and the app can also verify a phone number. The driver profile stores the full name, phone number, email, home address, gender, approval status, a rejection reason when one is recorded, rating, rating count, fare rates when the driver sets them, and created and updated times. The driver chooses a profile photo and a driver-license image from the photo library. Those images are uploaded and the profile stores their addresses.
Vehicle. The driver profile stores the vehicle type, brand, model, plate number, color, year, and a vehicle photo. It can also store images of the registration, insurance, and roadworthiness documents. Photos are chosen from the photo library, not from an in-app camera capture.
Ride. A ride record stores the rider id, driver id when a driver accepts, pickup and destination coordinates and addresses, status, estimated and actual fare, distance, estimated duration, and created, started, and completed times. It also stores the driver name, photo address, rating, vehicle plate, and vehicle model shown to the rider. A ride request sent to a driver includes the rider name, phone number, and rating, the offered fare, the payment method and status, and which drivers declined. After a trip, a review can store a star rating, an optional comment, and the rider name and photo address.
Payment. A rider can pay with cash, a Buruh wallet balance, or card checkout. Card numbers and card security codes are entered on the Stripe checkout page. Buruh does not save the full card number or the security code. It does save the amount, the payment status, a Stripe session reference, the wallet balance, and references for completed wallet top-ups. A saved payment-method record, when one exists, can include a label, card brand, and last four digits. A driver payout record stores the bank name, routing number, account number, account holder name, account type, a country value of US, a currency value of USD, and a Stripe bank token. A withdrawal stores the amount, status, currency, and a copy of those bank details.
Referral and promo balance. A rider profile can store a referral code, a referral count, and a promo credit balance. Promo credit records can be read for that rider.
Device and on-device settings. The apps do not collect an advertising id, a device model, or a crash report. They do check whether the phone has a network connection so they can show an offline notice. Notification on/off choices, theme, a local signed-in flag, and the driver’s preferred navigation app are stored on the phone. They are not sent as a device profile.
Public website. Reading the public pages does not create an account. The contact page lists a phone number, email addresses, and a mailing address. It does not take or store a message. The pages load the Poppins font from Google Fonts. They do not run an analytics tag.
Admin console. An administrator signs in with an email account that carries an administrator claim. Staff can read rider profiles, driver profiles, vehicles, documents, rides, ride requests, payments, withdrawals, and disputes. Dispute and ride-investigation notes, and an append-only audit log of staff actions, are stored for that work. The console is not offered to riders or drivers, and search engines are asked not to index it.
Account details identify the rider or driver and let the person sign in again. Phone numbers and names are shown so the matched driver and rider can recognize each other. Home address and gender are collected as part of driver registration. License, vehicle, and document images are collected so staff can approve or reject a driver.
Pickup, destination, fare, distance, and time are used to price the trip, offer it to a driver, and keep a record of what happened. Driver location is used while the driver is online so nearby riders can be matched and so the rider can follow the trip. Ratings and comments record the trip review.
Wallet balances, Stripe session references, and cash or wallet payment status are used to record whether the trip was paid. Driver bank details and withdrawal records are used to request a payout. Referral codes and promo balances are used for the free-ride and credit feature in Buruh Rider.
Push messages are used to deliver ride requests and trip updates. The public website does not collect a name, email, or message. Staff use the admin console to approve drivers, review trips and payments, record disputes, and refund a wallet charge when that action is taken.
Google sign-in, maps, and fonts. Google sign-in receives the Google account the rider chooses and returns the name, email, and photo address. Place search, geocoding, and directions send the address text or the coordinates to Google so the apps can show a route. The public pages request font files from Google Fonts. Google Maps is also the default external navigation app a driver can open.
Firebase services that are actually used. The apps use Firebase Authentication for email, phone, and Google sign-in. Rider and driver records, rides, payments, reviews, and notifications are stored in Cloud Firestore. Driver location for nearby matching is also written to Firebase Realtime Database while the driver is available, and removed from the available-driver entry when the driver goes offline. Driver photos and documents are stored in Firebase Storage. Firebase Cloud Messaging delivers push notifications. The driver profile stores the messaging token used for those ride-request alerts. The rider app requests a messaging token on the device. It does not save that token on the rider profile.
Not used. The rider app, the driver app, and the public website do not include a product-analytics SDK and do not include a crash-reporting SDK. Earnings charts in Buruh Driver are calculated from that driver’s own trip records. They are not a separate analytics service.
Stripe. Card checkout for a ride or a wallet top-up sends the rider email, the amount, the currency, and a short description to Stripe. The currency value in the app is USD unless a build overrides it. Driver bank details are sent to Stripe to create a bank token. Stripe processes the card and the bank token. Buruh stores the session reference and the bank token, and also stores the bank fields described above.
Buruh Rider asks for location while you are using the app. It uses that position to place you on the map, to offer your current position as the pickup, and to look for nearby drivers. The coordinates and address you confirm are saved on the ride and on the ride request. The rider app does not keep a separate ongoing location history for the rider.
Buruh Driver asks for location while you are using the app. When you are online or on a trip, the app stores latitude, longitude, and, when the phone provides them, heading, speed, and accuracy, together with the time of the update. That location is shared so riders can see a nearby driver and follow the trip. When you go offline, the live location fields are removed from the driver profile and the available-driver location entry is removed. The pickup and destination already saved on a completed ride stay on that ride record.
The Android apps request fine and coarse location. They do not request Android background-location permission. The iOS permission text mentions location during a trip. The apps request the standard in-use location permission. They do not declare a background location mode.
Both apps ask permission to show notifications. Buruh Driver stores a messaging token on the driver profile and uses it to send a ride request. That alert can include the pickup and destination, the rider name, the fare, the payment method, the distance, and the duration.
Buruh Rider can show notification records stored for that account, including a title, a message, a category such as ride, payment, promotion, or system, and whether it was read. The rider can turn push notifications off in settings. That choice is stored on the phone. Buruh Driver stores on the phone whether ride, earnings, and promo notifications are enabled. Promo notifications start off.
Buruh can be reached at +1 (301) 442-2269, info@buruh.org, or support@buruh.org. The mailing address is 951 Upper Marlboro CT, Maryland USA. Email and phone buttons open your mail app or phone app. They do not create a support case inside Buruh. Live chat in Buruh Rider is marked coming soon and does not send a message. The rider “report an issue” control is marked coming soon and does not submit a report. The driver support screen shows short answers stored in the app. It does not save a ticket.
The contact page lists the same phone number, email addresses, and mailing address. It does not take or store a message.
The apps and the website do not set an automatic deletion date for accounts, rides, payments, documents, or messages. A ride record, a driver document, a payment, and a profile remain until they are removed outside these screens. Live driver location is the exception: it is cleared when the driver goes offline.
Buruh Rider includes a Delete Account control. That control shows a confirmation and does not delete the account, the rides, or the profile. Buruh Driver does not include an in-app delete-account action. A retention schedule is not defined in the product. That item is listed under Needs confirmation.
Sign-in is handled by Firebase Authentication. The admin console accepts only an account with an administrator claim. Staff cannot grant themselves that claim from the console. Audit records written for staff actions are append-only from the console. Rider and driver records in the admin rules are readable by administrators and are not edited directly from the console client.
Trip, profile, and document files are stored in the Firebase services named above. Card entry happens on Stripe. The driver payout record in Buruh still contains the full account number and routing number, not only the Stripe token.
You can ask for a copy of the account information Buruh holds, ask for a correction, or ask for deletion by emailing support@buruh.org. Use the email on the account so the request can be matched. The apps do not complete deletion themselves. A request is handled from that inbox. The product does not publish a response deadline.
You can sign out of either app. You can turn off location and notifications in the phone settings. You can turn off push notifications in Buruh Rider settings. Doing that does not delete past rides or documents.
The apps do not ask for a date of birth and do not check an age. They do not offer a child account. Whether the service is limited to adults, and any minimum age, is not set in the product. That decision is listed under Needs confirmation.
When this page changes, the effective date and the last updated date at the top will change. The Buruh Rider settings screen still shows “Privacy policy coming soon” and does not open this page. There is no in-app notice that a new version was published.
Privacy questions and account or data requests go to support@buruh.org. You can also call +1 (301) 442-2269, email info@buruh.org, or write to 951 Upper Marlboro CT, Maryland USA. The contact page lists the same details. That page does not store a message.
The notes in this section are open items for the Buruh business and legal owner. They are not settled policy, and they are not production legal terms.
The product does not publish a legal entity name, a registered address, a country of establishment, or a governing law. The mailing address is 951 Upper Marlboro CT, Maryland USA. A registered address still has to be supplied by the owner before it appears as a legal address on this page.
No retention period is implemented. The owner needs to set how long accounts, rides, payment records, driver documents, and support emails are kept, and who deletes them. The rider Delete Account control does not delete data.
No minimum age is implemented. The owner needs to decide whether children may use Buruh and what age rule applies.
Driver payout records store the full bank account number and routing number in Cloud Firestore, alongside a Stripe bank token. The owner needs to confirm that this storage is intended.
Fares and payouts are coded as USD, and the payout country value is US. The published support number is +1 (301) 442-2269. The owner needs to confirm the countries where Buruh operates and the currency riders and drivers should expect.
The rider Privacy Policy button still says coming soon. The owner needs to decide when the apps should open this page.
