Privacy policy

This page describes the personal data processing WAYLISS actually carries out today, the providers used and the countries involved.

Data controller

Processing and data

WAYLISS processes the data needed to organize transfers between hotels, transport companies, drivers and travelers:

  • Professional accounts: email address, login sessions and authentication factors.
  • Hotels and transport companies: business contact details, company identifiers, vehicles and vehicle documents. A vehicle photo is shown to the hotel only if the transport company allows it.
  • Partner applications (Join WAYLISS page): type of organization, property or company name, city, professional name, email and phone number of the contact person, history of the application.
  • Drivers: identity, phone, photo, languages, driver’s license, training results. During the pilot, no identity document and no medical certificate is collected.
  • Travelers: name and contact details provided by the hotel, addresses, times, flight number and date or train number, practical trip information (passengers, luggage). During the pilot, no health or accessibility data is collected, and free-text notes must not contain any.
  • Ride execution: driver position during the ride, traveler tracking link, messages between traveler and driver.
  • Billing: company identifiers, amounts, payment references.
  • FRENCH KEYS bank statements: to match payments, we keep credits that may correspond to a commission (date, amount, reference, description with account numbers masked). The description may contain the name of the person who made the transfer, including a third party. A line that was never matched is deleted no later than 180 days after import; the statement file is not kept.
  • Security: audit and login logs.
  • Acceptance of the Terms of use (partners): the version accepted, the language in which it was shown to you, the date and time at which you ticked the box in your space (opened from the link received by email, or from your partner space), and the property or company the acceptance is attached to. Neither your IP address nor your browser information is recorded.
  • Website contact form: category, organization, name, role (optional), email and message, sent by email to the team and not stored in the website’s database.

Purposes

  • Create and manage professional accounts.
  • Organize transport requests, offers and driver and vehicle assignment.
  • Carry out and track rides, and inform the traveler.
  • Send operational communications.
  • Provide support, billing and commissions.
  • Ensure platform security and traceability.
  • Keep proof of acceptance of the Terms of use.
  • Answer requests received through the contact form.

Recipients

Each party only sees the information needed for its role: the hotel follows its requests, the transport company organizes the ride entrusted to it, the driver sees the assigned mission and the traveler views their tracking link. The WAYLISS team accesses the data needed for operations and support.

Before a ride is entrusted, the transport companies offered the request only see the pickup and drop-off areas, never the exact addresses, together with the time, the number of passengers and pieces of luggage, the vehicle category and the requested equipment. The exact addresses are shared only with the selected transport company and the assigned driver.

Providers and countries

  • OVH: data hosting is provided by OVH HOSTING SARLAU (contract concluded in Morocco); the server is located in Beauharnois (Quebec), Canada.
  • Vercel: running of the web applications; functions run in Montreal (Canada), main processing and sub-processors in the United States.
  • Resend: sending of the platform’s automatic emails from notify.wayliss.com; sent from Ireland, with the account, logs and metadata in the United States.
  • Hostinger: incoming mailboxes for @wayliss.com addresses (company established in Cyprus; actual storage country not disclosed by the provider).
  • WhatsApp (Meta): if you choose “Send via WhatsApp”, your message is sent from your device through the WhatsApp app to WAYLISS’s official number.

Third-party service opened at your initiative

FlightStats: on a ride with a flight number, the “View flight” button opens the FlightStats website, which only receives the flight number and date and, as with any website you visit, your IP address and technical information about your browser. FlightStats is not a WAYLISS provider: it is an independent service, which may be located outside Morocco and is subject to its own privacy policy; no other data is sent to it.

Push notifications

The hotel, transport company and driver apps can show alerts on your device (“New mission”, “New request”…) if you turn them on with the “Turn on notifications” button and then allow them in your browser. You can turn them off at any time in the app or in your browser settings; signing out turns them off on that device. The same information remains available in the app’s notifications.

Data: the device identifier assigned by the browser’s notification service, the encryption keys provided by the browser, the type of device and browser (for example “Android · Chrome”) and the dates of activation, last opening of the app and deactivation.

Content: alerts contain a generic title and text, with no traveller information (no name, phone number, address, time, flight or ride reference). The screen opened from an alert requires your usual sign-in. A transport company only sees whether notifications are on for each of its drivers (yes / no), never the device or the content of the alerts.

Delivery: alerts go through the notification service of your browser’s publisher (Google, Apple, Mozilla or Microsoft), located outside Morocco, mainly in the United States. Their content is encrypted and this service cannot read it; it receives the device identifier, the time and the size of the message.

Mission order and verification QR code

For an assigned ride, WAYLISS generates a “mission order” from the recorded mission. It is used to present the mission and to let the person it is shown to check its current state. The driver can display or download it; their transport company can download it. The ordering establishment can download a reduced version (driver: first name and last-name initial). This operating document is not an administrative authorisation, a licence or an official document.

Content of the document: mission reference, transport company, driver’s first and last name, vehicle and registration, ordering establishment, first name of the main traveller and number of passengers, date, time, pickup place, destination, type of service and, where applicable, flight or train number. It contains no phone number, email address, identity document or price.

The document’s QR code opens a public page, accessible without an account to anyone who holds the document. While the mission is upcoming or in progress, this page shows the current state of the mission: reference, status, transport company, driver’s first name and last-name initial, vehicle, registration, date, time, pickup and destination. It never shows the traveller. If the driver or the vehicle has changed since the document was generated, the page says so and shows the current assignment.

After the mission is completed, cancelled or closed, the page only shows the reference and the status for 24 hours, then nothing. QR code openings are not recorded. Each generation of the document leaves a record (mission, author, date and time, screen or PDF), deleted 90 days after the end of the mission.

Transfer documents: traveller voucher and execution attestation

From the page of a ride, the establishment or agency that requested the transfer can generate a “transfer summary” and then, once a driver and a vehicle are assigned, a “traveller transfer voucher” to give to its client. Content: service, date, time, pickup, destination, establishment name, references, the price invoiced by the establishment to its client if it entered one, the driver’s first name and last-name initial, vehicle and registration, and a QR code to a tracking link created for this voucher. The traveller’s first name only appears if the establishment types it; never their surname. The document does not print the pickup code, but its QR code opens the tracking page, which shows that code once the driver is assigned: the voucher must be given to the traveller only. The price never appears on the tracking link. WAYLISS is neither the seller of the service nor the issuer of the invoice.

For a completed ride, the establishment can generate a “transfer execution attestation”: reference, establishment, transport company, the driver’s first name and last-name initial, vehicle, route and the times recorded in WAYLISS (driver arrived, pickup, ride started, transfer completed). It contains no traveller name and no location, and its content is frozen at the first generation. Its QR code opens a public page that only states that the document is authentic (type, reference, issue date), for 90 days after the end of the transfer, then nothing. This document is neither a mission order nor a regulatory manifest.

Transfers outside Morocco

Today, platform data is not hosted in Morocco: it is stored in Canada, and some processing takes place in the United States, by providers established outside Morocco, listed above.

Push notifications also go through your browser’s notification service, located outside Morocco (see “Push notifications”).

Hosting in Morocco is WAYLISS’s target; it will be put in place after evaluating suitable Moroccan providers.

Retention periods

Partner applications: an application never confirmed is deleted after 7 days; an application with no follow-up, 90 days after the last activity; a rejected application, 90 days after the decision; the copy of an approved application, 30 days after approval. The contact details of an approved organisation remain in its partner space for as long as it exists.

Push notifications: a subscription is revoked after 90 days without the app being opened. As soon as a subscription is revoked (turned off, sign-out, inactivity or end of access), the device identifier and keys are erased immediately; a minimal technical record (dates, reason, device type) is deleted 30 days later. Delivery records (status and timestamps, no content) are deleted 30 days after they are created. Deleting an account immediately deletes its subscriptions.

Mission order: the record of each generation of the document (mission, author, date and time, screen or PDF) is deleted 90 days after the mission is completed, cancelled or closed. The public QR code page shows nothing 24 hours after that end.

Transfer execution attestation: its frozen content and its generation record are deleted 90 days after the end of the transfer; the public page of its QR code shows nothing after that date.

Driver position tracking: a tracking gap of 10 minutes or more during a ride is reported to the driver’s transport company and to the WAYLISS team (ride reference and length of the gap, never the position). These reports are kept for 90 days, then deleted.

Acceptance of the Terms of use: if your application never led to the creation of a partner space, it is deleted with the application, unless it must be kept because of an ongoing dispute or proceeding; once a partner space has been created, even if the application is later rejected, it is kept for the whole relationship with WAYLISS and then for five years after the final closure of your space, including if your account is deleted, and longer if a dispute or proceeding is ongoing, solely as proof of that acceptance.

Retention periods depend on the nature of the data and its purpose. WAYLISS applies specific periods to certain categories and is continuing to put in place retention and deletion rules suited to each processing activity.

Your rights

You may request access to your data, its rectification or erasure, or object to its processing, under the conditions set by Moroccan law No. 09-08.

How to exercise your rights

Write to the data protection contact address above. State your name, your capacity (hotel, transport company, driver, traveler, partner applicant or other), the purpose of your request and the address for our reply.

Handling of requests and complaints

WAYLISS confirms that your request has been received. To check that it comes from you, the team may ask you to confirm it from your account or through the property that organized your transfer; no copy of an identity document is requested by default.

You may also refer the matter to Morocco’s data protection authority, the CNDP (Commission nationale de contrôle de la protection des données à caractère personnel).

Cookies

Cookie details are on the Cookies page.

Formalities with the CNDP

Formalities with the CNDP are being prepared. No reference is available yet; it will be shown here once obtained.