Privacy
Updated November 2026
What we keep when you ask us for a ride, why we need it, who else sees it and how you can have it deleted.
This covers all three ways to ask us for a ride: WhatsApp, the request form and a phone call.
What the form asks for, and why
Each detail on the form has a job:
- your name, so your driver knows who to meet at arrivals or at your hotel;
- your phone or WhatsApp number with the country code, so we can confirm the ride and reach you on the day;
- the trip itself (date, time, from and to, number of people, bags and items such as a pushchair or golf bag), so we can price it and plan the day;
- your flight number or your ship's name, so we follow the real landing or docking time;
- each child's age, so we fit the right child seat;
- the language you want us to write to you in;
- the reference code the page gives your request, and whether you came through an ad, Google Maps or a host's link, so we can find your request and see how people find us;
- notes and how you found us, only if you fill them in.
We use these details to answer your request and, if you book, to drive you and send the invoice. You asked us for the ride, and that is what allows us to use them. Please leave out anything the ride doesn't need. If you tick Wheelchair or mention someone's health, we use it only to plan the ride.
WhatsApp and phone calls
A WhatsApp button on this site opens WhatsApp with your trip summary already typed, and nothing is sent until you press send. After that the chat is handled in WhatsApp, on your phone and ours, under WhatsApp's own privacy policy. We use what you write there the same way as a form request. After the ride we send one message asking for a short review. If you call, we see your number.
Our WhatsApp assistant
An AI assistant that works for us answers our WhatsApp and our Telegram bot first, and it says so in its first message. It answers questions about prices, free dates and the tours, and it passes your booking request to us: we confirm every booking and send the payment link ourselves. Ask for a person at any time and we answer you in person.
These services handle the chat for us:
- Kapso carries the messages between WhatsApp and the assistant;
- Anthropic's Claude writes the assistant's replies, and under Anthropic's commercial terms our chats are not used to train its models;
- Cloudflare runs the assistant and keeps its copy of the chat, which is deleted 180 days after your last message unless a booking is still open;
- Telegram carries the chat when you write to our Telegram bot, under Telegram's privacy policy, and carries your request (your name, contact and the trip) to our phone, so it can be confirmed quickly;
- Google Calendar keeps your booking in our diary once it is confirmed.
Where the form goes
When you press Send request, the form goes to our booking assistant, the same system as the chat assistant above, run for us by Cloudflare. It keeps your request with your booking and passes it to us in Telegram, so it can be confirmed quickly. The confirmation page then offers our Telegram bot or WhatsApp: if you open the bot from there, the assistant carries on with the same request. Its copy of the request is deleted 180 days after your last message unless a booking is still open.
The shared rides board and its bot
- Who is responsible: Dmitriy Gerko (Extra Madeira), as below.
- What we keep: your Telegram user ID and app language, and a short code we use instead of your ID; your listings (route, pickup area, date and time, seats, price and your note); your requests to join and their status; how many messages were passed between two people on a trip, but not their text; your reports; the people you block in the bot; our moderation decisions about you. If you use the report form on the website: your name, e-mail address and report. To stop abuse of the form we count reports per connection with a scrambled code, deleted after 2 days and never stored with the report.
- What is public: the trip: route, area, date, time, seats, price and the kind of poster, and an operator's business name and registration number. Never your name, phone number or Telegram username. Notes stay in the bot.
- What the other person sees: when you ask to join, the poster sees your first name as Telegram shows it, and your short message. Your Telegram username or phone number reach the other person only if you press Share my contact; we don't store them.
- Why: to run the board for you at your request (GDPR art. 6(1)(b)); to handle reports and keep moderation records as the Digital Services Act requires (art. 6(1)(c)); to prevent abuse and keep the board working (our legitimate interest, art. 6(1)(f)).
- Messages: we pass messages on and do not store their text, except a message someone reports, which we keep with the report as the reporter saw it. Messages stay in your Telegram app until you delete them; we cannot delete them there.
- Automatic checks: filters hide links and numbers in messages and hold some listings for a person to review. A person makes every removal and ban; after some removals an automatic rule limits the account (new listings checked by a person first, lower posting and request caps), which you can contest with /appeal.
- Moderation: each new listing with its note, each report and each appeal reaches our moderator as a message in Telegram; a report sent from the website carries the reporter's name and e-mail there, and we answer it by e-mail.
- Who else: Cloudflare stores the board's data for us; Telegram carries the messages under its own privacy policy.
- How long: listings and requests: 30 days after the trip; reports, moderation decisions and blocks: 12 months; your account: 180 days after you last used the bot; daily backups of the database: up to 90 days. The copies in our moderation chat and mailbox follow the same periods: we delete them by hand each month once their period has passed.
- Your rights: see your rights. In the bot, /deletedata deletes your listings, requests and account from the board at once; their copies in our moderation chat follow the periods above. If your account was closed for breaking the rules, a minimal record of that decision (your Telegram user ID, the decision and its date) stays for 12 months so it can't be bypassed. The same minimal record keeps a limit placed after a listing of yours was removed for breaking the rules, until 180 days after you last used the bot. You can complain to the CNPD.
Who else sees your details
We don't sell your details or share them for advertising, and we don't send newsletters or offers. If another driver takes your ride, they get only what the ride needs: your name, phone number, and the pickup time and place. When you pay by our payment link, Revolut (Revolut Bank UAB) processes the payment on its own page under its privacy policy; it shows you our name and contact details, and we never see your card details. Portuguese law requires us to report each invoice to the tax authority.
How long we keep them
We keep your details only as long as your request, your ride and its invoice need them, and then we delete them. The invoice itself stays on file for as long as Portuguese tax law requires.
Cookies, analytics and web addresses
We use Google Analytics 4 (Google Ireland Limited) to see which pages people read, how they found the site and which buttons they press. It never receives your name, phone number, email or anything you type in the form or the WhatsApp message. It does see the addresses of the pages you open, and a booking page address can carry the route and the number of people. How it runs depends on where you are:
- In the EEA, the UK and Switzerland it sets no cookies and stores nothing on your device until you press Accept, or save your cookie settings with Analytics ticked. Until then Google gets only cookieless signals, such as a page view without a visitor identifier, which it may use for counted and modelled reports.
- Everywhere else it sets its cookies from your first visit, and you can switch it off at any time.
In the cookie settings, Analytics is ticked and Marketing is not; Accept turns both on. Marketing covers ad and remarketing tags. We use none today, and if we add any, they run only for visitors who have Marketing turned on. You can change your choice at any time with the Cookie settings button in the footer. If you switch Analytics off, it stops on the page you are on, isn't loaded on later pages, and its cookies (the ones whose names start with _ga) are deleted from your browser.
Your browser keeps your cookie choice, your day or night setting, a copy of the island weather figures for a few minutes and, for 30 days, the kind of place you last came to us from, such as a Google ad, a Google search or another website: one word and a date, never an identifier. While you browse, your browser tab also keeps the ride you priced, its reference code and the first page you opened, until you close it. The booking page uses them to fill in the form, and the source and the first page let a request be credited to the right source. Neither is kept if you have switched Analytics off.
We also count visits ourselves, without cookies. Each page you open and each press on the WhatsApp, Telegram or phone button sends our server the page, that kind of source and, for a WhatsApp press, the page label at the start of the message. It carries no identifier, and we keep only daily totals and the time of each press, never your IP address. If you have accepted Analytics, a press on the WhatsApp, Telegram or phone button, and the booking form, also carry the Google Analytics code of your visit (from its _ga cookies), so the request you send can be credited to that visit. We use all this to see which pages and sources bring requests, and it stops when you switch Analytics off.
When a request reaches us or a trip is paid, our server also sends Google Analytics a short note of it: the amount, that kind of source and whether it came through the form, WhatsApp or Telegram. It carries no name, phone number or email. If you accepted Analytics, it goes under the Google Analytics code of the visit you came from, so Google Analytics can tell which visit brought the request; otherwise its visitor code is scrambled with a key only we hold, so Google can't link it to you or to your browser. We send it for every request, whatever your cookie choice, and without your Analytics consent nothing in it points to you.
Your name, phone number and email never go into a web address. A link to the booking page carries at most the route, the number of people and where the link came from, such as Google Maps. The WhatsApp button's link carries only the trip summary you see before you press send. The site is served by Cloudflare, which sees your IP address when it sends you a page. The weather and sea panel on the home page loads its figures from Open-Meteo, which sees your IP address too.
Your rights
You can ask to see the details we hold about you, and have them corrected, deleted or sent to you in a form you can take elsewhere. You can also ask us to limit or stop using them, and withdraw the consent you gave on the form at any time. Message us on WhatsApp or email us (both are in the footer), with your booking reference if you have one, and we answer within one month, as the GDPR requires. We may ask you to confirm it's you before we send anything. You can also complain at any time to Portugal's data protection authority, the Comissão Nacional de Proteção de Dados (CNPD), or to the one where you live in the EU.
Who is responsible
We, the business named below, decide how your details are used, which makes us the controller under the GDPR. Questions about this page go to the WhatsApp number and email in the footer, the same ones you book through.
- Company
- Dmitriy Gerko (Extra Madeira)
- NIF
- 299863727
- Activity
- Animação turística (tourist animation)
- RNAAT
- 1070/2026
- Head office
- Caniço, Madeira
- Livro de Reclamações (complaints book)
- www.livroreclamacoes.pt/Inicio/