qanbio.Download

Privacy policy

Version 1.0 — in effect since 22 September 2026

Article 1 — Preamble

This Privacy Policy describes how ANTICIP PARTNERS SAS (the "Publisher"), acting as data controller, collects, uses, retains and protects the personal data of people using the qanbio Platform.

The qanbio Platform, for the purposes of this document, comprises:

  • the Passenger mobile application, displayed after installation under the name Qanbio;
  • the Driver mobile application, displayed after installation under the name Qanbio Driver;
  • the operations console (back office), an internal tool reserved for the Publisher’s staff;
  • the public website available at `qanbio.com`.

Distinct scope for the public website. The public website `qanbio.com` is a strictly static showcase site (home page, application downloads, driver recruitment page, legal notice). It does not create any user account, does not make any call to the application or its databases, and does not itself collect any personal data. This Privacy Policy therefore applies to it only as general information about the group’s practices; its substantive provisions concern only the Passenger application, the Driver application and the operations console, which are the only three surfaces of the Platform that process personal data tied to user accounts.

The public ride-sharing page, accessible through a unique token-based link (see Article 4.1), likewise does not create an account: for the duration of a Ride, it displays position and estimated arrival time to whoever receives the link, without collecting any data about that person.

qanbio is a technology platform operator connecting Passengers and Drivers. qanbio never collects the price of a Ride: that price is paid directly by the Passenger to the Driver, outside the application. This structural feature of the model (rule RG-04) significantly narrows the scope of data processed compared with a conventional ride-hailing platform: no Passenger payment data exists anywhere in the qanbio system. Further detail appears at Article 4.4.

Article 2 — Definitions

The terms used in this Privacy Policy follow, without redefining them, the glossary of qanbio’s Terms of Use ("CGU"), a separate document that should be consulted for the full contractual definitions. As a reminder:

  • the Publisher: ANTICIP PARTNERS SAS, controller of the data described in this document;
  • the Platform: the Qanbio (Passenger) application, the Qanbio Driver application, the operations console (back office) and the `qanbio.com` website, taken together;
  • the User: any natural person holding a Passenger or Driver account on the Platform;
  • the Passenger: a User who requests a Ride;
  • the Driver: a User, either independent or attached to a fleet, who performs Rides after identity and document verification (KYC) and subscription to a Subscription;
  • the Fleet Owner: a person to whom one or more Drivers are attached, with read-only access to a dashboard and no financial flow with the Publisher;
  • the Trusted Contact: a third party, not a Platform User, designated by a Passenger after their first Ride, notified in the event of an emergency alert;
  • the Ride: a trip requested by a Passenger and performed by a Driver;
  • the Quote: the reference amount communicated to the Passenger and the Driver before a Ride;
  • the Subscription: the Driver’s paid right of access to the Platform’s dispatch, structured as a fixed portion and a variable portion;
  • the Window: the rolling 24-hour window, strictly prepaid by the Driver, that governs their access to dispatch;
  • the Cancellation Penalty: an amount charged in the event of a Passenger’s late cancellation, carried forward to that Passenger’s next Ride, never passing through the Publisher;
  • the CGU: the Platform’s Terms of Use, a contractual document separate from this Privacy Policy;
  • the Privacy Policy: this document.

Article 3 — Data controller

The controller of the personal data described in this document is:

ANTICIP PARTNERS SAS, a simplified joint-stock company (société par actions simplifiée),

  • Registered office: Abidjan, Cocody, Angré 8th tranche, 200 metres from Mandela junction, Lot 125, Îlot 15, Republic of Côte d’Ivoire
  • RCCM registration number (trade and personal property credit register): CI-ABJ-03-2026-B16-00169 (Abidjan)
  • Share capital: 1,000,000 CFA francs
  • Legal representative / publication director: the Chairman of the Publisher
  • Taxpayer / tax identification number: 2605744Q
  • Contact address for any question relating to this Privacy Policy: +225 07 13 85 79 76; postal address: registered office above; email address: contact@qanbio.com

Data protection officer or correspondent: the Chairman of the Publisher, in their capacity as legal representative, performs this role within the meaning of Law No. 2013-450 of 19 June 2013, no separate officer being appointed as of the drafting date.

Article 4 — Data collected, purposes and legal bases

This article describes, category by category, the personal data processed by the Platform, its source, purpose, the legal basis relied upon, and the recipients. Retention periods associated with each category are addressed separately in Article 5, as they depend on country-reference-data parameters not yet fixed as of the drafting date.

The legal bases relied upon are, in order of priority: performance of the contract binding the User to the Publisher (the CGU), legal obligation (in particular regarding Driver identity verification and accounting obligations), and the Publisher’s legitimate interest (in particular regarding safety). Consent is relied upon as a standalone legal basis only where none of the preceding three bases applies meaningfully — which is specifically the case for a Passenger’s designation of a Trusted Contact.

4.1 Passenger data

  • Data : Phone number — Source : Entered by the Passenger at sign-up — Purpose : Identification, one-time-code login, connection with the Driver (always masked) — Legal basis : Performance of the contract — Recipients : Publisher’s internal teams (Support, Country Manager, Administrator); Meta (WhatsApp Business Platform) for sending the one-time code via WhatsApp, Twilio for sending it as a fallback by SMS and then by voice call, and for masking calls
  • Data : First name (surname not required) — Source : Entered by the Passenger — Purpose : Personalisation, named communication with the assigned Driver — Legal basis : Performance of the contract — Recipients : Assigned Driver
  • Data : Point location: Ride pickup and destination — Source : Device GPS or manual entry — Purpose : Matching with a Driver, route and Quote calculation — Legal basis : Performance of the contract — Recipients : Assigned Driver; internal teams in the event of a dispute or incident on the Ride
  • Data : Live position during the Ride — Source : Device GPS, transmitted continuously while the Ride is under way — Purpose : Ride tracking, safety, feeding the share link — Legal basis : Performance of the contract / legitimate interest (safety) — Recipients : Assigned Driver; Trusted Contact and any person receiving the share link, if activated, only for the duration of the Ride (see Article 5)
  • Data : Trusted Contact’s identity and phone number (a third party’s data, not a User) — Source : Entered by the Passenger, offered only after their first Ride is completed, never at sign-up — Purpose : Notifying this third party if the Passenger triggers an emergency alert — Legal basis : Passenger’s consent (for the designation) / Publisher’s legitimate interest (for the notification in an emergency, which protects the Passenger’s safety) — Recipients : Twilio (SMS delivery), exclusively when an emergency alert is triggered
  • Data : Ride history (trips, displayed Quote, ratings given, reports) — Source : Generated by Platform use — Purpose : Managing the contractual relationship, evidence in the event of a dispute, computing trust indicators — Legal basis : Performance of the contract / legitimate interest — Recipients : Publisher’s internal teams, under the systematic named audit described in Article 6
  • Data : Rating given to a Driver, report of a Quote overcharge — Source : Entered by the Passenger — Purpose : Social oversight of price transparency, effect on the trust status of the Driver concerned and, where applicable, on their access to the Platform — Legal basis : Legitimate interest — Recipients : Internal teams; the Driver concerned only receives an aggregated rating, never the named detail of reports
  • Data : Language preference, technical log (crashes, usage), retained for twelve (12) months — Source : Application — Purpose : Service quality, delivering the interface in the chosen language — Legal basis : Legitimate interest — Recipients : Technical observability provider

4.2 Driver data

Unlike the Passenger, the Driver undergoes prior identity and document verification (KYC) before activation, and holds a paid Subscription. The following data is added, consistent with Table 4.1 adapted to their profile:

  • Data : Identity document (photograph) — Source : Uploaded by the Driver at sign-up — Purpose : Identity verification prior to account activation — Legal basis : Legal obligation / performance of the contract — Recipients : Internal verification agent (Support, Country Manager); file stored on a private object storage space, accessible via a short-lived pre-signed URL, never logged (see Article 8)
  • Data : Driving licence (photograph, expiry date) — Source : Uploaded by the Driver — Purpose : Verification of fitness to drive, ongoing validity check — Legal basis : Legal obligation — Recipients : Same as above
  • Data : Vehicle registration document — Source : Uploaded by the Driver — Purpose : Verification of the vehicle used — Legal basis : Legal obligation — Recipients : Same as above
  • Data : Vehicle insurance certificate (photograph, expiry date) — Source : Uploaded by the Driver — Purpose : Verification of insurance coverage, ongoing validity check — Legal basis : Legal obligation — Recipients : Same as above
  • Data : Vehicle technical inspection (photograph, expiry date) — Source : Uploaded by the Driver — Purpose : Verification of the vehicle’s technical condition, ongoing validity check — Legal basis : Legal obligation — Recipients : Same as above
  • Data : Criminal record extract — Source : Uploaded by the Driver — Purpose : Character verification, in the interest of Passenger safety — Legal basis : Legal obligation / legitimate interest (safety) — Recipients : Same as above
  • Data : Vehicle information (make, model, licence plate) — Source : Entered by the Driver — Purpose : Visual identification of the vehicle by the Passenger before approach — Legal basis : Performance of the contract — Recipients : Passenger, for the duration of the current Ride
  • Data : Mobile money account used to pay the Subscription — Source : Entered by the Driver — Purpose : Charging the fixed and variable portions of the Subscription at each Window opening — Legal basis : Performance of the contract — Recipients : Mobile Money (Orange Money, MTN MoMo, Moov Money, Wave) ; the Publisher (financial entries, see Article 8)
  • Data : Background position while in "online" mode (outside a Ride) — Source : Device GPS, transmitted in the background on Android and iOS — Purpose : Dispatch — offering Rides to the most relevant Driver — Legal basis : Performance of the contract — Recipients : Internal dispatch processing only; this data is never transmitted to any third party and is never persisted in the transactional database outside of Ride state transitions (see Article 5)
  • Data : Financial entries: Subscription instalments (fixed and variable portions), Cancellation Penalties charged or owed — Source : Generated by Platform use — Purpose : Subscription billing, accounting evidence — Legal basis : Legal obligation (accounting) / performance of the contract — Recipients : Publisher’s internal teams (Support, Country Manager, Administrator)
  • Data : Ride acceptance rate, trust status, rolling rating — Source : Generated by Platform use — Purpose : Service quality, automatic suspension in the event of degraded trust — Legal basis : Legitimate interest — Recipients : Publisher’s internal teams
  • Data : Proof of the short training session completed at sign-up — Source : Generated by Platform use — Purpose : Evidence that the Driver completed the required training before activation — Legal basis : Performance of the contract — Recipients : Publisher’s internal teams

4.3 Fleet Owner

The Fleet Owner holds an account giving read-only access to a dashboard aggregating certain indicators of the Drivers attached to them (activity, trust status). They have no financial relationship whatsoever with the Publisher — only the Driver personally subscribes to and pays for their Subscription. The Fleet Owner’s data processed for this purpose (account identification, scope of attachment) follows the same principles of purpose, legal basis (performance of the contract) and security as the Driver’s data.

4.4 What qanbio does not collect

The Publisher emphasises, because it is a structural and deliberate feature of its model, that:

  • No Passenger payment data is collected, anywhere, in any form. Nowhere on the Platform does a Passenger bank card number, Passenger payment account identifier, or Passenger payment transaction history exist. Payment for a Ride is made directly between the Passenger and the Driver, outside the application, in accordance with the CGU. The Quote displayed before a Ride is only a reference amount communicated to both parties, never a payment transaction processed by the Publisher.
  • No password is collected or stored: authentication relies exclusively on a one-time code sent first by WhatsApp, with fallback to SMS and then to an automated voice call.
  • No position is collected outside of an ongoing Ride or the Driver’s active "online" mode.
  • No personal data is sold, rented or transferred to third parties for commercial or advertising purposes.

4.5 Masked number and one-time code

Passenger and Driver phone numbers are never exchanged with each other in the clear: their phone connection passes through a masking mechanism operated by Twilio, the Publisher’s SMS and voice provider, operating over plain GSM, without requiring a data connection. The one-time code sent during login is never logged in the clear, is limited in number of attempts by phone number, device and address, and is compared using a method protected against timing attacks.

Article 5 — Retention periods

The retention periods for the data described in Article 4 are not values fixed in this document: they are governed by parameters of the Platform’s country reference data, configurable from the operations console, country by country, without requiring a new application release. This Privacy Policy therefore refers, for the exact numeric value applicable to a given country, to the corresponding country reference-data settings screen or to an annex to be published separately.

Three parameters govern retention periods:

  • `conformite.retention_comptes` — retention period for account data (Passenger and Driver) after account deletion or the end of the contractual relationship. Value adopted for Côte d’Ivoire: thirty (30) days from the deletion request, after which account data is permanently purged.
  • `conformite.retention_pieces` — retention period for the Driver’s KYC supporting documents (the six documents described in Article 4.2) after account deletion. Value adopted for Côte d’Ivoire: three (3) years from account deletion.
  • `conformite.retention_positions` — retention period for the position history logged at Ride state transitions (see Articles 4.1 and 4.2). Value adopted for Côte d’Ivoire: twelve (12) months from the logging of each transition.

Particular point of attention — position history. The retention period for position history is not an ordinary parameter: it pits two legitimate and hard-to-reconcile requirements against each other. On one hand, detecting disintermediation or fraud on the Subscription’s variable-portion base, and reconstructing a disputed Ride, require a sufficient history. On the other, the data-minimisation principle requires that this history — particularly sensitive because it can reconstruct a person’s movements — be kept only for as long as strictly necessary. The Publisher currently adopts a period of twelve (12) months. This value nonetheless remains provisional and subject to confirmation: the declaration formality with ARTCI (Côte d’Ivoire’s Telecommunications/ICT Regulatory Authority) covering the Platform’s processing activities has not yet been initiated as of the drafting date (see Article 7), and the resulting guidance may lead to a revision of this period. This Privacy Policy will be updated should this period change following that process (see Article 14).

As a reminder, the continuous tracking of a Driver’s position in "online" mode or during a Ride is, technically, never persisted in the transactional database: it passes through a non-durable in-memory index. Only Ride state transitions (pickup, arrival, end of Ride, for example) are logged in the database, precisely because this is what makes a disputed Ride reconstructible after the fact — it is this logging, and this logging only, that falls under the `conformite.retention_positions` parameter.

Financial entries (Subscription, Cancellation Penalties). Financial entries relating to the Driver’s Subscription (fixed and variable portions) and to Cancellation Penalties are, by technical construction, immutable and append-only: they are never modified or deleted, only a reversing entry can correct an error. These entries are retained for as long as the applicable accounting obligation requires, including after the deletion of the Driver’s account, for a period of ten (10) years from their creation.

Article 6 — Data recipients

Internally, the personal data described in Article 4 is accessible to Publisher staff operating the operations console, according to their role: Support (handling requests and reports), Country Manager (overseeing the Ivorian market), Administrator (account and parameter management). Every consultation of personal data from the operations console is logged with a systematic named audit trail, within the very same operation as the read itself: the identity of the staff member, the data consulted and the timestamp of the consultation are recorded systematically and cannot be bypassed. This audit trail is a verifiable security commitment, not a mere statement of intent: a personal-data read that would not produce a corresponding audit entry is, by technical design, refused.

Externally, data may be transmitted to the following technical providers, strictly to the extent necessary to perform their assignment and never for their own commercial purposes:

  • Provider : Mapping and place-search provider (Google Places, Google Routes) — Role : Landmark search, route and arrival-time calculation — Data involved : Search queries, approximate coordinates — never the User’s identity
  • Provider : Displayed map provider (Apple Maps on iOS, Google Maps on Android) — Role : On-screen mapping in the application — Data involved : Position displayed on screen
  • Provider : Push notification provider (Firebase Cloud Messaging) — Role : Sending the application’s notifications — Data involved : Technical device identifier (push token)
  • Provider : Meta (WhatsApp Business Platform, Cloud API) — Role : Sending the one-time code via WhatsApp, the first channel used at login — Data involved : Phone number, one-time code — Location of processing : outside the territory of Côte d’Ivoire (see Article 7)
  • Provider : Twilio (SMS and voice call) — Role : Sending the one-time code by SMS and then by automated voice call as a fallback to WhatsApp, masking calls between Passenger and Driver, sending the alert SMS to the Trusted Contact in an emergency — Data involved : Phone number, message content — Location of processing : outside the territory of Côte d’Ivoire (see Article 7)
  • Provider : Mobile Money — Role : Collecting the Driver’s Subscription (Orange Money, MTN MoMo, Moov Money, Wave) — Data involved : Driver’s phone number, amount, transaction reference
  • Provider : Technical observability provider — Role : Diagnosing application incidents — Data involved : Technical data, systematically redacted before any export
  • Provider : Infrastructure hosts (Render, Neon, Cloudflare R2/Pages/Workers/Access, EAS/Expo) — Role : Hosting the API, database, document storage and application builds — Data involved : All data described in Article 4, acting as technical processors on behalf of the Publisher

The Publisher does not transmit any of this data to third parties for marketing or resale purposes.

Article 7 — Transfers outside Côte d’Ivoire and safeguards

The Platform’s technical operation requires hosting personal data outside Ivorian territory:

  • the application API, real-time layer (WebSocket) and deferred processing are hosted by Render, in the Frankfurt region (Germany, European Union);
  • the PostgreSQL database and the Redis geospatial index are hosted respectively by Neon and Render Key Value, also in the Frankfurt region;
  • KYC documents, incident photos, exports and billing archives are stored on Cloudflare R2, in a private space subject to European Union jurisdiction;
  • delivery of the public website, the operations console and the Ride share page passes through Cloudflare’s global edge network;
  • compilation and distribution of the mobile applications pass through EAS (Expo);
  • sending the one-time code via WhatsApp goes through the Cloud API of Meta (WhatsApp Business Platform), whose processing takes place outside the territory of Côte d’Ivoire, under that provider’s conditions;
  • sending the fallback one-time code (SMS, voice call), masking calls and sending emergency alerts by SMS go through Twilio, whose processing takes place outside the territory of Côte d’Ivoire, under that provider’s conditions.

This arrangement constitutes, within the meaning of Law No. 2013-450 of 19 June 2013, an international transfer of personal data outside the territory of Côte d’Ivoire, to the European Union and to providers, some of which are headquartered in the United States. In this respect:

  • Safeguard mechanism adopted for this transfer: standard contractual clauses, concluded with each of the providers concerned to govern this transfer in accordance with Law No. 2013-450.
  • Status of the declaration or prior-authorisation formality with ARTCI: still to be initiated. The Publisher confirms that, as of the drafting date of this document, this formality has not yet been completed; it remains to be carried out with Côte d’Ivoire’s Telecommunications/ICT Regulatory Authority, with a target completion date of 30 October 2026, before the Platform’s commercial launch.

Article 8 — Data security

The Publisher implements the following technical measures to protect personal data processed on the Platform:

  • Strict country segregation, enforced at the database level (row-level security): a query that does not explicitly carry a country scope returns no rows for that country, preventing any leak of data from one country to another as the Platform expands into new markets.
  • Driver KYC documents accessible exclusively via a short-lived pre-signed URL: this URL is never persistently stored nor logged in the Platform’s technical logs; the actual type of every uploaded file is verified from its opening bytes, not merely from the file name’s extension, to prevent the upload of a malicious file disguised as an image.
  • Immutable financial entries (see Article 5): the Platform’s application role does not technically have the right to modify or delete an entry once created; only a reversing entry can correct it.
  • Ride share tokens composed of 128 bits of cryptographic randomness, never derived from an existing identifier nor predictable, with validity re-checked on every request and automatic expiry at the end of the Ride concerned.
  • Protection against one-time-code abuse: limits on the number of attempts per phone number, device and address, with comparison performed in constant time so as not to expose information through response timing.
  • Systematic absence of sensitive data in technical logs: no one-time code, phone number, authentication token, pre-signed URL or geographic position appears in the clear in the Platform’s operational logs.

Article 9 — Cookies and trackers

The public website `qanbio.com` sets no cookie or tracker whatsoever: it is a strictly static site, without user accounts and without any collection of personal data, consistent with Article 1 above.

As of the drafting date, the Qanbio (Passenger) and Qanbio Driver (Driver) mobile applications include no identified advertising software development kit (SDK) and no identified cross-application tracking. No data is transmitted for targeted advertising or advertising audience measurement purposes. This description reflects the state of the product as of the drafting date and does not constitute a fixed commitment for the future: should this state change, this Privacy Policy would be updated beforehand, following the procedure described in Article 14.

Article 10 — Rights of individuals

In accordance with Law No. 2013-450 of 19 June 2013 on the protection of personal data, any individual concerned by a processing activity described in this document has the following rights:

  • Right of access: to obtain confirmation that data concerning them is being processed, and to obtain a copy of it;
  • Right to rectification: to have inaccurate or incomplete data corrected;
  • Right to object: to object, on legitimate grounds, to processing based on the Publisher’s legitimate interest;
  • Right to erasure: to request deletion of their data, under the conditions described in Article 11;
  • Right to data portability, to the extent provided for by Law No. 2013-450, for data provided directly by the individual concerned.

These rights are exercised in writing with the Publisher, at the email address contact@qanbio.com, at +225 07 13 85 79 76, or at the postal address of the registered office set out in Article 3. A response is provided within the timeframes set by Law No. 2013-450. Proof of identity may be requested to verify the identity of the requester before acting on a request concerning sensitive data.

The Trusted Contact, although not a Platform User, holds the same rights over the data concerning them (name, phone number) processed under Article 4.1.

Article 11 — Account deletion

Any User may request deletion of their account. This request triggers, on the Platform side, the calculation of a final purge deadline ("`purge_prevue_le`"), established from the applicable retention parameters described in Article 5 (`conformite.retention_comptes` for account data, `conformite.retention_pieces` for the Driver’s KYC documents). Between the request and this deadline, the data is no longer used for the Platform’s ordinary operation; it is retained only for the residual period required by a legal or accounting obligation, before final purge.

Financial entries relating to the Subscription and to Cancellation Penalties, being immutable by construction (see Articles 5 and 8), remain retained beyond account deletion, under the applicable accounting obligation, for the ten (10) year period referred to in Article 5. When the account is purged, they undergo an irreversible dissociation between the user account and the financial entries: the user identifier is replaced with a technical reference that is not directly identifying, personal attributes that are not required are deleted, and only the data necessary for accounting, tax and legal obligations is retained, in isolation, for its regulatory period.

In accordance with the requirements of the mobile application marketplaces (Apple rule 5.1.1(v), and the equivalent Google Play requirement), the account deletion request can be initiated from within the application itself, without requiring an external channel, through the Profile → Account → Delete my account path, available in both the Qanbio and Qanbio Driver applications. A request channel accessible from the web, without prior login to an account, is also provided at `qanbio.com/delete-account`.

Article 12 — Recourse to ARTCI

Any individual concerned who believes that the processing of their personal data by the Publisher does not comply with Law No. 2013-450 of 19 June 2013 has the right to lodge a complaint with the Telecommunications/ICT Regulatory Authority of Côte d’Ivoire (ARTCI), the supervisory authority competent in matters of personal data protection in Côte d’Ivoire, independently of any other amicable or judicial remedy.

Article 13 — Minors

The Publisher set a minimum age threshold of eighteen (18) years on 22 September 2026, applicable to the creation of both a Passenger account and a Driver account, restated in Article 4.1 of the Terms. Registration by a minor, regardless of age, is not permitted.

On the Driver side, the requirement of a valid Ivorian driving licence further bounds access to legal adulthood in practice. On the Passenger side, verification of this age relies solely on the User’s declaration at registration; the Publisher does not implement any independent verification mechanism (identity document, third-party verifier).

Article 14 — Updates to this policy

This Privacy Policy may be amended to reflect changes to the Platform, to applicable regulation, or to the providers referred to in Article 6. Any substantial change — in particular a change affecting the categories of data collected, their recipients, the retention periods described in Article 5, or the introduction of an advertising-tracking mechanism that does not exist as of today — is communicated to Users in advance, through an appropriate means (in-app notification, information displayed before acceptance), prior to its taking effect. The effective date and version number appear at the top of this document.

Article 15 — Contact

For any question relating to this Privacy Policy, or for the Publisher’s full identity (registered office, RCCM number, legal representative), please refer to the Platform’s Legal Notice, a separate document maintained independently, or contact the Publisher at the address indicated in Article 3 above.