This Privacy Policy explains how TechServices LLC collects, uses, retains, protects and shares
personal data through DriverX and DriverX Conductor, as well as the rights of users. By
creating an account or using the services, the user acknowledges having read this Policy and,
where applicable, gives consent freely, specifically and on an informed basis.
Article 1.Identity of the controller and scope
DriverX is a technology mobility platform created by TechServices LLC. For the purposes of
this Policy, TechServices LLC acts as the controller of the personal data processed through
the DriverX application for passengers and DriverX Conductor, unless a specific notice
identifies another controller.
Legal name: TechServices LLC
Registered address: 504 Pinto Pony Dr, Ashland, Missouri 65010, United States
Privacy email: support@technoservicesdigital.com
Support WhatsApp: +1 573 797 6612
This Policy covers the use of the applications, the trip services, the support and safety
features, and the official websites that expressly link to this document.
Article 2.Protection framework and principles
Processing is carried out in accordance with applicable law, including Law No. 787, the
Personal Data Protection Law of Nicaragua, and its Regulation, Decree No. 36-2012.
TechServices LLC will seek to apply the principles of information, consent, purpose,
proportionality, quality, confidentiality, security and accountability.
Data will be used only for determined, explicit and legitimate purposes. We will not request
data that is not reasonably necessary to provide the service, protect users, comply with
legal obligations or handle claims.
Article 3.Personal data we collect
Registration and contact data: first and last name, phone number, email
address where provided, protected credentials, verification status and data associated
with account recovery.
Driver and vehicle data: vehicle type, license plate, make, model, year,
color, driver's license number, approval status, availability, rating, operational rates
and other data needed to assign trips.
Verification documents and images: the passenger's identity document
where they voluntarily request verification; and, for drivers, identity document, driver's
license, facial photograph, license plate, registration, insurance and vehicle photographs,
together with expiry dates and review outcomes.
Location data: approximate or precise device location, origin and
destination coordinates, addresses, the driver's current location, proximity and arrival
events, and periodic points along the route during a trip.
Trip data: service type, origin, destination, distance, estimated
duration, suggested price, offers and counteroffers, final price, trip status, timestamps,
cancellations, reasons, penalties and ratings.
Financial and payment data: payment method, amount, payment status and
confirmations, transaction references, last four digits and payment token where applicable,
driver wallet balance, top-ups, commissions, bonuses and transactions.
Safety and support data: emergency contacts, relationship to the
contact, location of an emergency, reports, disputes, tickets, comments, voluntarily
provided evidence and incident resolutions.
Technical and anti-fraud data: IP address, basic device information,
operating system, sessions, push notification identifier, security logs, alerts, fraud
indicators and administrative audit records.
DriverX does not currently use advertising SDKs and does not sell personal data. If
advertising, external analytics or new providers that change the processing are introduced in
the future, this Policy and the Data Safety declaration will be updated before enabling them.
Article 4.How we obtain the data
Directly from the user when they register, complete their profile, upload documents,
request a trip, make a top-up, submit a rating, report an incident or contact support.
From the device, with the corresponding permissions, when location, camera, files, images
or notifications are used.
Automatically during use of the service, for example when recording a trip status, a
session, a location, an alert or a security operation.
From providers that render services on behalf of DriverX, such as maps, hosting, storage,
notifications, phone verification or payments, where such functions are enabled.
Article 5.Purposes of processing
Create, verify, authenticate, maintain and protect accounts.
Locate available drivers and connect passengers with nearby drivers.
Quote, request, negotiate, assign, track, complete, cancel and pay for trips.
Show the passenger the operational identity, vehicle, license plate, rating and location
of the assigned driver.
Enable the communication needed between the parties to a trip and with the support team.
Verify identity, driver's license, vehicle and the documentation required to operate.
Manage wallets, top-ups, commissions, bonuses, payments, refunds and disputes.
Send notifications about offers, status changes, proximity, arrival, payment, safety and
document expiry.
Handle emergencies, claims, incidents, fraud, abusive conduct and requests from competent
authorities.
Generate internal operational statistics and improve the safety, availability and
performance of the service.
Comply with contractual, accounting, tax, regulatory and legal obligations.
Article 6.Precise and background location
Passengers
DriverX may access location while the application is in use in order to set the pickup point,
display the map, search destinations and follow an active trip. The user may also enter an
address manually where the feature allows it.
Drivers
DriverX Conductor collects precise location in order to show availability, assign nearby
requests, share the position with the assigned passenger, record the route, calculate
proximity and arrival, and support safety features. When the driver is online or taking part
in a service, this collection may continue in the background, even when the application is
closed, minimized, with the screen locked or not actively in use.
Prior driver consent
Before requesting the background location permission, the application must display a
prominent notice explaining these purposes and request an affirmative act of consent. The
driver can stop operational tracking by going offline and can also revoke the permission
from the device settings, although doing so will prevent them from properly receiving or
completing certain trips.
Location is not used for advertising.
Article 7.Mandatory or optional nature of the data
The fields required to create the account, verify the driver, assign and complete a trip,
manage safety or comply with the law are mandatory for those functions. Refusing to provide
them may prevent registration, driver approval, receiving trips or the use of a specific
feature.
Optional, as applicable, are the email address, the passenger's document verification,
emergency contacts, certain comments and other data identified as voluntary. Not providing an
optional item must not prevent the use of functions that do not require it.
Article 8.Emergency contacts and third-party data
If a user adds an emergency contact, DriverX stores the name, phone number, relationship and
primary contact status. Before providing that data, the user represents that they have
informed the contact and have sufficient authorization to share it with DriverX. This data
will be used solely for safety and emergency functions, save for legal obligations.
The user may delete a contact from the application where the feature is available. DriverX
must not import the device's entire address book for this purpose.
Article 9.When and with whom we share data
TechServices LLC does not sell or rent personal data. It may share it on a limited basis with:
The other party to the trip: name, rating, necessary contact information
and, in the case of the driver, vehicle and license plate. During the service, the passenger
may receive the assigned driver's real-time location.
Infrastructure providers: Render or equivalent providers to host the
application and the database, and Cloudflare R2 or equivalent services to store documents
and files.
Map providers: Google Maps Platform for maps, address search,
coordinates, routes and estimates.
Notification providers: Expo Push Notification Service and, on Android,
Google Firebase Cloud Messaging, to deliver notices.
Verification and payment providers: SMS services, banks, gateways or
payment processors where those functions are enabled. DriverX will seek to receive only the
tokens, references or partial data required, and not to store the full card number or its
security code.
Advisers and authorities: authorized personnel, auditors, lawyers,
insurers and authorities where necessary to protect rights, respond to emergencies, comply
with the law or answer a valid request.
Corporate transactions: an acquirer, successor or investor in a
reorganization, merger or sale, subject to confidentiality obligations and applicable law.
Article 10.International transfers and retention
Some providers may process data outside Nicaragua, including the United States. TechServices
LLC will carry out such transfers only where they are necessary for the service and permitted
by applicable law, using consent, contracts, security measures or other valid mechanisms as
appropriate.
Retention periods:
Account and profile: for as long as the account remains active and
during the applicable legal or contractual blocking period following a cancellation
request.
Trip, payment, wallet, billing and audit history: up to five years from
creation of the record, or for a longer period where a law, claim, investigation or
proceeding requires it.
Detailed GPS route: up to thirty days after the trip, unless an
emergency, dispute, fraud, claim or legal duty justifies keeping it longer.
Identity and driver documents: for as long as the account or operational
relationship is active and up to one year after it ends, save for blocking or necessary
legal retention.
Sessions and technical security logs: up to twelve months, unless needed
to investigate an incident or comply with a legal obligation.
Emergency contacts: until the user deletes them or requests deletion of
their account, save for justified legal retention.
Push notifications: until the token is replaced, revoked or no longer
needed.
Support, claims, disputes and evidence: for the duration of the case and
the period necessary for legal or contractual liabilities.
Once the purpose and the applicable period have been fulfilled, data will be deleted,
anonymized or blocked. Blocked data will not be used for ordinary purposes and will be kept
solely for potential liabilities until its definitive erasure.
Article 11.Information security
Encryption of communications using HTTPS/TLS.
Passwords stored using cryptographic hash functions, not in readable text.
Protected session tokens, with expiry, renewal and revocation controls.
Role-based access controls and logging of administrative actions.
Restricted document storage and the use of authorized or signed links where appropriate.
Validation, rate limiting, monitoring and fraud prevention measures.
Access and confidentiality review for authorized personnel and providers.
No system is completely infallible. If TechServices LLC identifies an incident that
compromises personal data, it will assess its scope, limit the damage, document the measures
taken and make the notifications required by applicable law.
Article 12.User rights
Data subjects may exercise their rights of access, rectification, cancellation and objection,
and may withdraw consent where applicable. They may also request information about the
purposes, the source and the transfers of their data.
Access: to know what data is processed and how it is used.
Rectification: to correct inaccurate or incomplete information.
Cancellation: to request blocking and subsequent erasure where the data
is no longer necessary or the processing is not appropriate.
Objection: to request that processing cease on legitimate grounds, where
no obligation requires it.
Withdrawal: to withdraw consent without retroactive effect, through
simple and free mechanisms.
Requests may be sent to support@technoservicesdigital.com
or via WhatsApp at +1 573 797 6612. To protect the
account, TechServices LLC may request reasonable information to verify identity and clarify
the scope of the request. Requests will be handled within the periods established by
applicable law.
Article 13.Account and data deletion
Users may request the deletion of their account and the associated data through any of these
channels:
From the application: in DriverX, via My profile → Delete my
account; in DriverX Conductor, via the side menu → Delete my account.
TechServices LLC will acknowledge the request within five business days and may request
reasonable information to verify the identity of the requester, in order to protect the
account against fraudulent requests. Once identity has been verified, deletion will be
carried out within the following thirty days.
Deletion will not be limited to suspending or deactivating the account. Where the request is
valid, data will be deleted or anonymized, except for data that must be blocked or retained
temporarily due to legal, accounting, tax, security, fraud prevention, claim or contractual
liability obligations. TechServices LLC will inform which data it retains, the reason and the
applicable period.
Article 14.Automated operational decisions
DriverX uses rules and scores to quote trips, estimate demand, rank eligible drivers, prevent
fraud and assign offers. These rules may take into account proximity, vehicle type,
availability, documentation, rating, acceptance, cancellations, operational balance and idle
time. Their purpose is to provide and protect the service; they are not used for automated
decisions that by themselves produce legal effects unrelated to the transport relationship.
Article 15.Minors
DriverX is not directed at persons under eighteen years of age and does not seek to knowingly
collect their data in order to create accounts. If TechServices LLC detects an account
belonging to a minor, it may suspend it and delete or block their data in accordance with the
law and safety requirements.
Article 16.Device permissions and controls
Location: for maps, pickup, assignment, tracking, proximity, arrival and
safety; for drivers it may operate in the background.
Photos, camera or files: to upload documents, verification photographs
and evidence the person chooses to provide.
Notifications: for trip offers and updates, payments, safety, account
and documents.
Permissions can be managed from the device settings. Revoking them may limit the functions
that depend on them, but does not authorize DriverX to use the data for purposes that have
not been disclosed.
Article 17.Changes to this Policy
TechServices LLC may update this Policy to reflect legal, operational or technological
changes. Where the change is material, notice will be given through the application, the
website or an appropriate contact channel before it takes effect where applicable. The
current version will always indicate the date it was last updated.
Article 18.Contact
For questions, claims or requests relating to privacy and personal data: