Partners & Provider Notice
This page explains key transport partners, provider categories and partner-onboarding disclosures. It complements the Privacy Policy and Terms.
Last updated: 2026-05-18
Key providers and systems
Provider regions, DPA status, SCCs and subprocessors must be verified in provider dashboards and contracts before formal due diligence. This public list does not state unverified regions as confirmed.
| Name | Role | Scope | Status / caveat | Website |
|---|---|---|---|---|
| Hosting platform (likely Vercel) | Hosting, deployment, CDN/logs | Runs the application and public website. | Production host and region still need dashboard verification. | vercel.com |
| PostgreSQL database provider | Database hosting technology | Stores users, bookings, payments, invoices, partner records, dispatch and admin records. | Technology confirmed; production provider and region not confirmed in repository. | - |
| Cloudflare R2-compatible storage | File/object storage | Partner document uploads, vehicle photos and related stored files. | R2-style code confirmed; bucket region, lifecycle, encryption and access settings require dashboard verification. | cloudflare.com |
| Brevo | Email sending | Transactional account, booking, verification, reset, partner and operational emails. | Confirmed email provider. | brevo.com |
| Google Workspace | Business mailbox | Business email handling for support, booking, billing, privacy and partner messages. | Owner-confirmed business mailbox provider. | workspace.google.com |
| Stripe | Payment provider | Online checkout, payment references, refunds and payment status. | Confirmed in code; payment-provider role and transfer safeguards require contract review. | stripe.com |
| myPOS | Payment provider | Online checkout, payment notifications, refund handling and payment status. | Confirmed in code; payment-provider role and transfer safeguards require contract review. | mypos.com |
| Google Maps Platform | Maps, Places, route services | Address autocomplete, maps, geocoding and route support. | Confirmed; Google terms and transfer safeguards apply as relevant. | maps.google.com |
| Google Analytics | Consent-gated analytics | Sanitized page path/location and usage measurement if NEXT_PUBLIC_GA_ID is configured. | Code-supported and blocked before consent; production status and dashboard settings not confirmed. | analytics.google.com |
| Google OAuth / Apple OAuth | Account sign-in | OAuth account identifiers and sign-in data where the user chooses that login method. | Confirmed in auth code. | accounts.google.com |
| EU VIES | VAT validation | Partner VAT number checks for onboarding. | Confirmed in code. | ec.europa.eu |
| GitHub Actions | CI/CD | Build and test automation for the codebase. | Confirmed in repository workflow; production data exposure should remain limited by CI configuration. | github.com |
1) Transport partners and assigned operators
- ODDO TRANSFER may assign a confirmed ride to ODDO TRANSFER or to licensed partners/operators.
- Assigned partners/drivers receive only the ride details needed to perform the transfer: pickup/drop-off, timing, passenger count, contact details, flight details, luggage/add-ons and relevant notes.
- Partners and drivers must use customer data only for ride performance, required service communication, legal obligations and dispute handling.
- Contact details exchanged through the platform must not be used for marketing or off-platform solicitation without a separate lawful basis.
2) Partner onboarding and documents
- Partner applicants submit company, VAT, contact, service-area, vehicle and payout information.
- Documents and photos may include licences, insurance, vehicle documents, vehicle photos and other required eligibility records.
- The authorised-representative confirmation is required and persisted as evidence that the applicant can submit the application for the company.
- The service/onboarding email acknowledgement is required and persisted for application, onboarding, assignment and service-related communications. It is not marketing consent.
- Uploaded documents should be limited to documents requested by ODDO TRANSFER.
3) Provider roles and transfers
Some providers may act as processors, while payment providers, OAuth providers, card schemes or transport partners may also have independent legal obligations. Exact role splits and DPAs should be confirmed in contracts.
Provider regions and transfer safeguards are not all visible in repository code. They must be verified in provider dashboards and contracts before a formal processor/transfer inventory is treated as complete.
4) Dispatch priority and quality-linked fees
Partners may set a Platform Visibility percentage in their dashboard. A higher percentage can affect dispatch visibility or priority compared with peers.
Quality, rider ratings, penalties, cancellation behaviour, no-shows, cash reporting, service reliability and safety issues may influence dispatch handling, partner review and platform fees.
ODDO TRANSFER may adjust dispatch inputs to preserve fairness, availability and service quality. Manipulation attempts may lead to suspension, penalties or termination.
5) No marketing consent
Partner service/onboarding communication acknowledgement is not newsletter or marketing consent. No partner marketing subscription is created by this acknowledgement.
6) Contacts
For partner applications and updates, contact partners@oddotransfer.com. For data protection questions, contact privacy@oddotransfer.com.