This version has not yet been reviewed by legal counsel. It accurately describes how the platform currently works, but its wording may change before launch.
1. Controller
Valtransfer, Nkerabigwi, sole proprietorship, Rue du Scex 49B, 1950 Sion, Switzerland, UID CHE-307.804.188. Data protection questions: support@valtransfer.ch, with "data protection" in the subject line.
This document is governed by the Swiss Federal Act on Data Protection (revised FADP, in force since 1 September 2023). Where the data subject is in the European Union, the GDPR may apply in parallel.
2. Passenger data
| Data | Why it is collected |
|---|---|
| Name | So the driver can identify the passenger |
| Phone number | Contact before and during the ride |
| Email address | Booking confirmation and receipt |
| Pickup and destination addresses, and their coordinates | Price calculation, ride assignment, execution |
| Date and time of the ride, estimated distance and duration | Pricing and scheduling |
| Amount, commission and Stripe transaction identifiers | Payment and accounting |
| Rating and comment, if given | Service quality and driver eligibility |
| The partner who recommended ValTransfer to you, if you arrive through their link or QR code | Paying their commission, or giving you their discount. The code is kept for 30 days in your browser (for the visit only for a taxi company; no cookie, can be cleared in Cookie settings), then recorded with your ride; the partner sees neither your name nor your trips, only the number of rides and their total |
| Your consent to receive our news by text message, if you tick the box when booking: number, date and accepted wording | Sending you our news and offers by text message, at most twice a month, based on your consent. You can withdraw it at any time at valtransfer.ch/stop |
Card details are never stored by ValTransfer. They go directly to Stripe, which holds them. ValTransfer keeps only technical transaction identifiers, which cannot be used to charge a card.
3. Driver data
This data is supplied by the driver when signing up, or by the partner company that engages the driver. Some of it is sensitive personal data under the FADP and is protected accordingly.
| Data | Why it is collected |
|---|---|
| First name, last name, date of birth | Identification |
| Email address and phone number | Ride coordination |
| OASI (AVS) number | Identity verification and legal obligations — sensitive data |
| Driving licence, B121 professional licence, cantonal authorisation | To verify the right to carry passengers professionally |
| Date the criminal record extract was checked | Passenger safety — sensitive data |
| Date the debt collection extract was checked | Partner reliability |
| Professional liability insurance | Cover in case of loss |
| Vehicle: make, model, year, plate | So the passenger can identify the vehicle |
| Vehicle location and its timestamp | Assigning the nearest ride and tracking execution. Shown to the passenger of the ride during the approach and the ride only (see "Location data") |
| Average rating, number of ratings, completed rides | Service quality and commission reduction calculation |
Only the dates on which the criminal record and debt collection extracts were checked are kept — never the contents of those documents.
Documents scanned at sign-up. Photos or PDFs sent by the driver are encrypted on receipt and can only be viewed by the company the driver chose and by ValTransfer. They are deleted as soon as the company approves or rejects the file, and at the latest 30 days after submission without a decision. A rejected file is itself deleted 30 days after the decision. For an approved driver, only numbers, expiry dates and verification dates remain.
Partners and ambassadors
For establishments and individuals who recommend ValTransfer: name, address, contact details, IBAN and account holder, and commission statements. This data is used to pay commissions, keep the accounts and, where applicable, meet legal obligations (social security, tax). It is kept for ten years as accounting records (art. 958f CO) and is only passed to the bank for transfers, and to the compensation fund or tax authorities where the law requires.
4. Location data
Vehicle position is recorded to assign rides and track their execution. It concerns the driver's vehicle, not the passenger's phone. No position is kept after the ride beyond what is needed to settle a possible dispute.
Only the last known position of each vehicle is kept: it is overwritten at every update, and no trip history is recorded.
Live tracking by the passenger. Once the ride is accepted, the tracking page shows the passenger the position of the vehicle coming to pick them up, and its estimated arrival time: during the approach and during the ride only, never before acceptance nor after the ride ends or is cancelled. The page shows the last known position; no history of it is kept, neither on our servers nor in the browser. To estimate the arrival time, this position and the pickup or drop-off point are sent to Google Distance Matrix.
5. Recipients
- The partner company and its driver receive the name, phone number, addresses and time, without which the ride cannot happen.
- Stripe processes the payment and receives the data needed for the transaction.
- Cal.com is used for scheduling and receives what is entered in the booking widget.
- Google Maps / Distance Matrix is queried to compute distances and durations from the addresses and, during live tracking, from the vehicle's position.
- swisstopo (Federal Office of Topography, Wabern) provides the base maps for live tracking. Your browser requests them directly from its servers, which deliver them through the Amazon CloudFront network: they receive your IP address and the map area displayed, nothing else. These servers set no cookie (checked on 11 October 2026).
- Twilio (Twilio Ireland Limited, part of the Twilio group in the United States) delivers text messages: it receives the number and the message text.
- Authorities, where the law requires it.
No data is sold or shared for advertising purposes.
Our servers are hosted by Hostinger in France, a country the Swiss Federal Council recognises as providing adequate protection. Providers based in the United States (payments, maps, telephony, artificial intelligence) receive data under the Swiss-U.S. Data Privacy Framework where they are certified, otherwise under standard contractual clauses recognised by the FDPIC.
6. Retention
Ride data is kept for the statutory retention period for accounting records in Switzerland, namely ten years for anything touching invoicing and payment. Data not covered by that obligation is deleted earlier — see Account & data deletion.
Your consent to our text messages, and its withdrawal, are kept as proof while the consent lasts; after a withdrawal, a record of it is kept so that no further news or offers are sent to you.
7. Your rights
- Access: obtain a copy of the data concerning you.
- Rectification: correct inaccurate data.
- Erasure: request deletion, within the limits of statutory retention.
- Objection: object to a specific processing activity.
- Portability: receive your data in a usable format.
To exercise these rights see Account & data deletion. You may also contact the Swiss Federal Data Protection and Information Commissioner (FDPIC).
8. Security
Passwords are never stored in clear text. API keys are kept as a non-reversible hash. Traffic to the site is encrypted (HTTPS). Incoming webhooks are cryptographically signature-verified before processing: an unsigned request is rejected.
9. Changes
Any substantial change to this document will be flagged on this page with a new update date.