Trust and transparency
Safety at Akrid
From driver verification to in-app PIN, plus tracking, support, and incident review. Here is how we protect passengers, drivers, and data.
Passenger safety
Ride safety PIN. In app settings (Security code), you set a fixed four-digit code and can enable it for rides. That code is what the driver needs to start the trip: you share it at pickup and the ride only starts after correct validation. The same PIN applies on trips where the option is on, confirming you boarded the right vehicle. Save the PIN before enabling it for rides.
In some cases (for example when a driver requires a code and no valid PIN is stored yet), the platform may generate a one-time ride code and notify you. The general PIN rule is: your code, reused on rides where code security is enabled.
Scheduled rides and privacy. For date/time reservations, chat and shown data follow platform rules to protect identity until near pickup, aligned with what we describe in How it works.
Driver verification and approval
Only after completing registration and validations can a driver go online for rides. That includes documents, identity checks (KYC), vehicle data, and when required, biometrics with liveness to prove the driver matches the registered person.
- Personal documents. Driver license, personal data, criminal background, and proofs are reviewed; where assisted OCR is used, results are validated in onboarding to reduce fraud and errors.
- Vehicle and eligibility rules. Vehicle type (car or motorcycle), category, year, and paperwork follow platform criteria. Requirements such as inspection (ITV) and eligibility are tracked per regional policies.
- Approval before operating. Going live depends on completed steps (contract, documents, biometrics when applicable, vehicle, payments/Connect, etc.). Until onboarding is complete and approved, the driver is not an active partner on the network.
Vehicle, conduct, and rating details for drivers are in Requirements, Accepted vehicles, Ratings and penalties.
During the ride
Tracking and sharing
Follow the driver on the map in real time and share trip status with trusted contacts when you want.
Emergencies
The app offers quick help paths. In a risk situation, also use public emergency lines (190, 192).
Emergency guideMatching considers proximity, history, and ratings among other signals to balance speed and service quality. Combined with trip codes and driver verification, this forms an operational safety layer on every request.
On the platform
Ratings and reputation. Passengers and drivers rate each other after rides. Low scores and recurring issues enter review flows and may trigger usage policies per our conduct and driver documents.
Reports and review. Incidents can be reported in the app and are handled by the team. For reports and ratings, also see Ratings and reports.
Anti-fraud and compliance. Akrid uses technical and operational layers (including risk signals, reviews, and financial alignment) to reduce account, coupon, and payment abuse. The goal is a fair ecosystem for people who follow the rules.
Data, privacy, and support
Privacy and LGPD. Personal data processing follows our Privacy policy and the detailed data document.
In-app support. In Messages you can talk to Akrid support: many questions are answered by a smart assistant, with the option to continue with our human team in the same thread. You can also use Contact on the site or the FAQ.
Safety is continuous: we update processes, technology, and communication as the service evolves.
Before, during, and after
Safety Center in the app (side menu) and the shield on the map during the ride. On the site, this board summarizes good practices in plain language.
Passenger
- Before: check plate, model, color, photo; confirm PIN; wait in a well-lit place; share the ride.
- During: follow the route; use safety audio if needed; avoid unnecessary personal data; use support or emergency via the shield.
- After: rate honestly; report incidents; check the charge and receipt.
Driver
- Before accepting: review origin, destination, and modality; assess the location; confirm passenger name; do not negotiate off-app.
- During: keep the flow in the app; use support in conflicts; prioritize safe stops.
- After: rate the passenger; report damage, threats, or scams; seek support for serious cases.
How to report: in the app (Ride / Safety / Reports) or Ratings and reports. Community code: Usage rules.
Plain language
Transparency in a few questions — example of the in-app safety audio feature.
- What is it?
- Optional recording during a trip when someone in the community feels at risk or uncomfortable.
- When to use it?
- In threat, harassment, assault, or serious behavior situations, always with responsible use of the feature.
- Who hears it?
- Content is handled with strict privacy; the safety team reviews it when linked to a formal report, per current policies.
- What happens next?
- The report and follow-up flow uses app channels and may include account measures, always within platform rules.
- Is my data safe?
- We process data under LGPD and documents published in Privacy.
