Privacy policy
Briki is a staff app for businesses that run ride-on car play zones. The business you work for (the "operator") gives you a Briki account and uses Briki to run its rides, takings, expenses and staff attendance. This policy explains what the Briki app collects and how it is used.
Briki is not for the public. You can only sign in with an account your operator created for you.
What we collect
- Account details: your username, full name, role (staff or admin), the location you work at, and a securely hashed password. Your operator may also record a phone number or email address for you.
- Work records: the rides you start and end (car, ride package, times, status), the payments you record (cash or UPI, and the amount), the expenses you record (amount, category, payment method and any note you write), and your attendance clock-in and clock-out times.
- Receipt photos: only if you choose to attach one to an expense, taken with your camera or picked from your photo library.
- Car controller data: when an installer pairs a car, the app reads the car controller's device ID and security key over Bluetooth and stores them so the car can be unlocked for rides. This identifies the car's hardware, not you.
- Change history: who corrected a payment, voided a ride or edited an expense, and when, so the operator's records can be audited.
What we do not collect
- No location or GPS data. On Android 11 and older, the system requires location permission for Bluetooth scanning; Briki uses it only to find nearby car controllers and never records your location.
- No information about the operator's customers.
- No contacts, advertising identifiers or device identifiers.
- No analytics, crash-reporting or advertising tools.
- No card or bank details. Briki records how a ride was paid; it does not process payments.
How the data is used
Only to provide the service to your operator: unlocking cars for paid rides, keeping the daily money record (daybook), recording expenses and attendance, and showing reports to the operator's admins. We do not sell your data or use it for advertising.
Who can see it
- Staff see the records for their own location and their own attendance.
- Your operator's admins see the records for all of the operator's locations.
- Brickly, which provides and hosts Briki, can access the data only to run, secure and support the service.
We do not share it with anyone else unless the law requires us to.
Storage and security
Data is sent over encrypted connections (HTTPS) and stored on our servers. Your sign-in tokens are kept in your phone's secure storage (the iOS Keychain or Android Keystore) and removed when you sign out. Car controller security keys are stored encrypted.
How long we keep it
Ride, payment and expense records are business records, so they are kept for as long as your operator uses Briki and needs them for its accounts. When you leave, your operator deactivates your account and you can no longer sign in.
Your choices and rights
You can ask to see, correct or delete your personal data. See Account deletion for how. Some records may need to be kept, with your name removed, where the operator must keep financial records by law.
Permissions the app asks for
- Bluetooth: to connect to a car's controller and unlock or lock it for a ride.
- Camera and photos: only when you add a receipt photo to an expense.
Children
Briki is a workplace app for adult staff and is not directed at children.
Changes
If we change this policy, we will update the date at the top of this page.
Contact
For questions about this policy or your data, email support@brickly.ai.