Privacy policy

1. Data controller

The data controller under the General Data Protection Regulation (GDPR) is:

Company

Mallorcation Events & Adventure, S.L.

Address

Calle Joaquim Verdaguer 4, 07600 Palma de Mallorca, Illes Balears, Spain

Email

hello@memply.app

Phone

+34 664 13 40 43

Tax number (NIF)

B57888497

We are not required to appoint a data protection officer and have not done so. Please direct data protection inquiries to the email address above.

2. Principles

We collect only the data we need for each purpose. We do not sell data. We do not use third-party analytics, tracking, or advertising services and do not integrate advertising networks. We measure how the app is used exclusively on our own server (see “Usage measurement in the app”).

Our servers, database, file storage, and routing service for travel time calculations run on our own infrastructure, which we operate ourselves. Travel times between stations on a day plan are calculated on our own server — no data is sent to map providers for this purpose.

3. Individual processing activities

Below are the individual processing activities with their purpose and legal basis under Art. 6 GDPR.

User account

Email address, phone number, password (stored exclusively as a cryptographic hash, never in plain text), language preference, and the confirmation status of email and phone number. Purpose: providing the account, login, and protection against misuse. Legal basis: contract performance (Art. 6(1)(b) GDPR).

Bookings and day plans

Booked services, dates, number of guests, special requests in free text, planned stations for a day, and the version of accepted terms you acknowledged. Purpose: processing the booking and providing proof of contract contents. Legal basis: contract performance (Art. 6(1)(b) GDPR).

Date of birth for age restrictions

For categories with statutory or contractual age restrictions, we collect and verify your date of birth before booking. For offers without age restrictions, we do not collect it. Legal basis: legal obligation and contract performance (Art. 6(1)(c) and (b) GDPR).

Residency verification

To unlock resident pricing we check your NIE number. The number is validated in memory only and discarded immediately afterwards — we do not store it. Only the result of the check is stored, as a yes/no value. Legal basis: contract performance (Art. 6(1)(b) GDPR).

View mode and travel dates

Whether you use the platform as a visitor or as a resident and, in visitor mode, the travel dates you have entered. Purpose: tailoring the listings to your situation. Legal basis: contract performance (Art. 6(1)(b) GDPR).

Payment processing

Amount, currency, booking reference, and payment status. Card data are processed exclusively by our payment service provider and never reach our servers. Legal basis: contract performance (Art. 6(1)(b) GDPR).

Booking notifications

Emails for registration, confirmation, reminder, change, and cancellation, along with a transmission log. Purpose: performance of the contract. Legal basis: contract performance (Art. 6(1)(b) GDPR).

Booking through a provider's website

If an activity provider embeds our booking form on its own website or uses its booking page on memply.app, you book without a MEMPLY account. We process your name, email address, phone number, language, the booked offer with date and number of people, and a booking code. Payment goes through the provider's payment account; card data is processed by the payment service provider. The confirmation and reminder are sent in the provider's name from our address, and replies go to the provider. The seller is the provider, who is the controller for this data; we provide the booking system and process the data on the provider's behalf (Art. 28 GDPR). The website on which the form is embedded does not receive your details. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).

Location data

When you add a location to a station or photo in the app, we primarily use the coordinates embedded in the image metadata, and otherwise — after explicit permission in your operating system — your current location. We request permission only at the moment you use the feature and do not track your location in the background at any time. Legal basis: consent (Art. 6(1)(a) GDPR), withdrawable at any time via system settings.

Photos, videos, and notes in your travel journal

Media you upload, together with optional location data, rating, and personal notes. Purpose: providing your travel journal. Legal basis: contract performance (Art. 6(1)(b) GDPR).

Reviews

Rating and text for a completed booking. Reviews are publicly visible; please do not publish information there that you do not wish to be public. Legal basis: contract performance and legitimate interest in comprehensible offer ratings (Art. 6(1)(b) and (f) GDPR).

Points, badges, and membership

Points collected, badges earned, and membership tier with expiry date. Purpose: providing the loyalty program. Legal basis: contract performance (Art. 6(1)(b) GDPR).

Marketing communications

If you have consented, we send notifications about offers. Consent is given separately for email and push notifications and is withdrawable at any time individually — via settings or the unsubscribe link in each message. Our newsletters contain a tracking pixel and route links through our server; this lets us record whether a message was opened and whether a link in it was clicked. If you do not load images in emails, you are not counted as having opened it. Legal basis: consent (Art. 6(1)(a) GDPR).

Referral information at registration

If you arrive through a referral or campaign link, we store the identifier contained in it to credit the referral and assess the effectiveness of our own outreach. Legal basis: legitimate interest (Art. 6(1)(f) GDPR); you may object at any time.

Partner accounts and documentation

For partner businesses, we process company and contact details, tax number, address, and uploaded business and license documentation. These documents are stored in a non-publicly accessible area and are intended exclusively for review by our team. Legal basis: contract performance and legal obligation (Art. 6(1)(b) and (c) GDPR).

Partnership requests to businesses

We contact businesses we would like to win as partners once by email. For this we process the business name, category, business email address, phone number, website, address and, where available, the name of a contact person. The data comes from publicly accessible sources such as the business’s own website; we record the source for each contact. To find out whether the message arrived, we record whether it was opened (via a counting pixel, which is imprecise because many email programs preload or block images), whether a link in it was clicked, which pages of memply.app were visited through that link, and whether a meeting was booked or a partner account was created. Nothing is stored on the device for this, and we do not record IP addresses. Anyone who objects via the unsubscribe link will receive no further messages of this kind; to ensure this, the address stays blocked as a checksum. Purpose: acquiring partner businesses. Legal basis: legitimate interest (Art. 6(1)(f) GDPR); for a booked meeting, steps prior to entering into a contract (Art. 6(1)(b) GDPR). If a business books a meeting through our booking page, we process the details entered there: name of the business, contact person and position, phone number, email address, the address for a visit and an optional message. The same applies to meetings booked without a personal invitation through the general booking link. The same applies to our other emails to businesses: the acknowledgement of a partnership request, our personal replies to it and the emails about a meeting. There, too, we record opening, clicked links, the pages of memply.app visited through such a link and whether this led to a request, an account or a meeting. Links to the legal notice and the privacy policy are not counted. We store the text of our replies with the request. If we write a reply in German and send it in another language, it is translated by our translation service (see recipients). We do not measure emails to guests, such as booking confirmations.

Location for restaurant search

If you search for restaurants near you, the app sends your current location to our server along with the search, once you have allowed it in your operating system. We use it only to calculate distances and sort the results and do not store it, not even in our server logs. Legal basis: consent (Art. 6(1)(a) GDPR), which you can withdraw at any time in your system settings.

Spots

If you publish a spot, the photo or video, the exact place where it was taken (coordinates and place name), your text, your display name and your profile picture are visible to everyone who uses the app. The location comes from the file itself or from a recording made directly in the app; a spot cannot be published without it. You can delete your spots at any time. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).

Comments and voice messages

Comments on spots and shared routes are visible to other users, together with your display name. On spots you can also leave a voice message; for this the app records once you have allowed microphone access, and the recording is stored and played back like a comment. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).

Push notifications

If you allow notifications, we store the device identifier your operating system assigns for this purpose, together with platform and language. Purpose: reminders of upcoming reservations and bookings. Push notifications are delivered through your operating system’s service (Apple Push Notification Service or Google’s Firebase Cloud Messaging); as long as this service is not yet connected on our side, we do not send push notifications. Legal basis: consent (Art. 6(1)(a) GDPR), which you can withdraw at any time in your system settings.

Usage measurement in the app

On our own server we record which areas and features of the app are used, for example which offer was viewed or whether a search was started; for searches only the length of the search term, not the term itself. This includes platform, language, a session identifier that exists only in the app’s memory and is not stored on your device, and, if you are signed in, your account identifier. We do not store IP addresses for this, and no data is passed to third parties. Purpose: finding errors and improving the app. Legal basis: legitimate interest (Art. 6(1)(f) GDPR); you can object at any time by email.

Memy, the assistant in the partner portal

In the partner portal, businesses can ask Memy questions and hand over tasks. For this we process the messages, attached photos and PDFs, the business data Memy retrieves to answer (such as offers, time slots or booking figures) and the account identifier. Messages, attachments and retrieved data are sent to Anthropic to generate the answer (see "Recipients of your data"). Memy only makes changes after the account has confirmed a proposal with a click. Anthropic also reads uploaded restaurant menus; the result is a draft that the business reviews. If a message to Memy is dictated, we convert the recording into text on our own server in Germany; it is not passed to any third party and is discarded after conversion, not stored. The text first appears in the input field and only becomes a message once it is sent. Purpose: helping to set up and maintain the business. Legal basis: contract with the business (Art. 6(1)(b) GDPR).

Creator profile (Creator Corner)

If you create a creator profile, we process your display name, your description, the categories you chose and, if you upload one, your profile photo. Approved partner businesses see these details in the marketplace of the partner portal for as long as your profile is set to visible. The profile photo is stored on our own server and can be retrieved via its address. Purpose: partners should be able to find and assess you for collaborations. Legal basis: performance of a contract (Art. 6(1)(b) GDPR). You can replace or remove the photo and hide your profile at any time; we delete a replaced or removed photo from storage, and also when you delete your account.

Connecting Instagram (Creator Corner)

If you connect your Instagram account as a creator, MEMPLY sends you to Instagram to log in. We receive only your username, account ID and follower count; we do not access posts, messages or comments. We also store the access token Instagram issues to us, encrypted only. Each token is valid for about 60 days; while the connection exists, we renew it automatically and fetch the follower count again about once a day. If the token can no longer be renewed, the connection counts as expired until you reconnect. Purpose: to confirm the account is yours, to show your reach as verified and to check proof of collaborations. Legal basis: consent (Art. 6(1)(a) GDPR). You can disconnect the account at any time in MEMPLY or remove the app in your Instagram settings under "Apps and websites"; in both cases we delete the Instagram data we hold. You can also request deletion through Instagram.

Connecting Facebook, TikTok or YouTube (Creator Corner)

If you connect a Facebook Page, a TikTok account or a YouTube channel as a creator, MEMPLY sends you to that provider to log in. From this we store only the name or username, the ID of the account, Page or channel and the number of followers or subscribers, where the provider shares it; we do not access posts, videos, messages or comments. On Facebook you connect a Page you manage, not your personal profile. We store the access and refresh tokens the provider issues to us encrypted only. While the connection exists, we renew the TikTok and YouTube tokens automatically and fetch the count again about once a day. If a token can no longer be renewed, the connection counts as expired until you reconnect. Purpose and legal basis are the same as for Instagram (consent, Art. 6(1)(a) GDPR). You can disconnect at any time in MEMPLY; we then delete the stored details and tokens. You can also withdraw MEMPLY's access in the settings of the provider concerned. For YouTube we use the YouTube API Services; the Google Privacy Policy (https://policies.google.com/privacy) applies, and you can revoke access at https://myaccount.google.com/permissions.

Logs and security

We log security and billing-relevant changes to records with timestamp and triggering account, and also log login attempts to prevent automated attacks. Purpose: auditability, abuse prevention, and troubleshooting. Legal basis: legitimate interest in secure operations (Art. 6(1)(f) GDPR).

4. Restaurant reservations

In the app you can reserve a table at a restaurant. We provide the same platform to restaurants as a reservation book, in which they also manage reservations that do not come through the app. There are therefore two roles:

We as controller

We are responsible for your MEMPLY account, your reservations through the app, the reservation fee and its receipt, loyalty points, the platform-wide no-show count, the reservation block, and the risk assessment (all described below).

The restaurant as controller

Each restaurant keeps its own guest book with us. It contains guests who reserved by phone, in person on site, through the restaurant's own system, or via a guest list imported by the restaurant, as well as the profile created when you reserve at that restaurant through the app. The restaurant is responsible for its guest book; we provide the software and process the data on the restaurant's behalf (Art. 28 GDPR).

In detail:

Reservation through the app

Restaurant, date, time, number of guests including children, preferred area, occasion, your free-text notes, language, and your phone number, which is mandatory for a reservation. The restaurant receives these details together with your name and email address and adds them to its guest book. We take the name from your display name; if you have not set one, we use the part of your email address before the @. If the restaurant already knows you under the same phone number or email address, the details are merged with the existing entry. Legal basis: contract performance (Art. 6(1)(b) GDPR).

Reservation through the restaurant's widget

A restaurant can embed our reservation form on its own website. There you reserve without a MEMPLY account, giving your first name, last name, phone number, email address, date, time, number of people, an optional note and your language. The reservation goes into the restaurant's guest book; the restaurant is the controller, and we process the data on its behalf (Art. 28 GDPR). We send the confirmation and reminders by email, with a link that lets you view, confirm or cancel the reservation for 30 days. No fee is charged; if the restaurant requires a deposit, the form refers you to the app. To prevent mass reservations with other people's details, we limit the number of reservations per phone number or email address per day. The website on which the form is embedded does not receive your details. Matching to an existing guest book entry works the same way as for reservations the restaurant enters itself. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).

Messages about the reservation

We send confirmations, reminders, requests to reconfirm, and notices of changes and cancellations by email — for reservations from the guest book on behalf of the restaurant. Messages you exchange with the restaurant in the app are stored so that both sides can see the conversation. Legal basis: contract performance (Art. 6(1)(b) GDPR).

Fee, deposit, and paying at the table

If a restaurant requires the MEMPLY reservation fee for app reservations, you pay it to us and we issue you a simplified receipt. A deposit, card guarantee, or prepayment required by the restaurant, and a payment at the table via the QR code, go to the restaurant. In all cases our payment service provider processes the card data; it never reaches our servers. Legal basis: contract performance and the legal obligation to invoice and retain records (Art. 6(1)(b) and (c) GDPR).

Waiting list, freed-up tables, and group requests

If you join the waiting list for a fully booked day, ask to be notified when a table becomes free, or send a request for a larger group, we store the details you provide and pass them on to the restaurant. Legal basis: contract performance (Art. 6(1)(b) GDPR).

“On my way”

If you tell the restaurant that you are on your way, we pass on the estimated arrival time in minutes that you selected — not your location. Legal basis: contract performance (Art. 6(1)(b) GDPR).

Reviews and private feedback

After a visit you can review the restaurant. The review is public unless you deselect this. It shows your display name in shortened form (first name and initial of the surname); if you have not set a display name, the part of your email address before the @ appears instead. The restaurant can reply publicly. Private feedback is seen only by the restaurant. Legal basis: contract performance and legitimate interest in transparent reviews (Art. 6(1)(b) and (f) GDPR).

Loyalty points

You receive 100 points for every completed reservation through the app and 20 for a review; if a restaurant does not honour a guaranteed reservation, we credit you compensation points. Points expire twelve months after they are credited. You can exchange 1,000 points for a voucher that waives the reservation fee of a later app reservation. Legal basis: contract performance (Art. 6(1)(b) GDPR).

No-shows and reservation block

If a restaurant marks an app reservation as a no-show, or if you cancel at short notice, we count this for your account across all restaurants; only the last twelve months are taken into account, and the count is recalculated daily. We inform you of every no-show marking. Within 48 hours you can object via the link in that message, and the restaurant can withdraw the marking during that time. If the number of no-shows reaches the limit, we automatically block your account from making reservations at all restaurants on MEMPLY. The platform-wide limit is currently four in twelve months; if the restaurant at which you were marked as a no-show has set a lower limit for itself, the block can take effect earlier. The block does not only apply to reservations through the app: if a restaurant enters a reservation itself (by phone, in person, by import or through its own connected system) and, via your phone number or email address, assigns it to an entry in its guest book that is linked to your account, that reservation is rejected as well, and the restaurant thereby learns that your account is temporarily blocked. An entry is linked as soon as you have made a reservation at that restaurant with your MEMPLY account once. The block ends after twelve months at the latest, and earlier as soon as the count for the last twelve months falls below the platform-wide limit; we check this daily. Independently of this, a restaurant can block a guest in its own guest book for itself. Legal basis: legitimate interest of the restaurants and the platform in reliable reservations (Art. 6(1)(f) GDPR).

Risk assessment for the restaurant

For each reservation we calculate, according to fixed rules, a value from 0 to 100 indicating how likely a no-show is. It takes into account whether neither visits nor no-shows are known for you so far, your number of no-shows in the last twelve months and your total number of completed visits so far, both across the whole platform, the number of guests, how far in advance you booked, whether the reservation falls on a Friday or Saturday evening, your reconfirmation, and whether a deposit was provided or a fee paid. The restaurant sees the value together with the individual reasons. If it is 60 or higher, we automatically tag your entry in the restaurant’s guest book as “risk” and highlight the reservation in the restaurant’s shift overview. The value does not trigger a block, a deposit or a different price. Legal basis: legitimate interest of the restaurants in predictable table planning (Art. 6(1)(f) GDPR).

Marketing by the restaurant

Restaurants can use our platform to send email campaigns to guests in their guest book, but only to guests for whom consent is recorded there. The restaurant is responsible for this consent. Every campaign email contains an unsubscribe link. A tracking pixel and the routing of links through our server record whether and when the email was opened or a link in it was clicked; both are recorded as an open.

The restaurant's guest book

The guest book contains name, phone number, email address, language, the number of visits, no-shows, and short-notice cancellations, the date of the last visit, tags, notes, birthday, consent to the restaurant's marketing, and — if you tell the restaurant — allergies and intolerances. Allergy information is health data; it is entered by the restaurant. The restaurant can import guest lists, export the guest book, and have reservation data transmitted to its own systems.

Please address your rights regarding data in a restaurant's guest book to the restaurant; if you contact us, we support the restaurant in responding. The data access report for your MEMPLY account also contains your restaurant reservations, the guest book entries linked to your account, points, vouchers, reviews, waiting list and notification entries, and messages.

As long as a restaurant reservation is still upcoming, you cannot delete your account. If you delete it afterwards, we remove name, contact details, notes, tags, allergies, birthday, and consents from the guest book entries linked to your account, and delete loyalty points, vouchers, waiting list and notification entries, messages, and the no-show count. The reservations themselves are kept without any link to you, without your notes, and without the occasion; public reviews remain without contact details.

5. Recipients of your data

We share data only as far as necessary for the stated purposes. Recipients are:

The booked partner business

Receives the information necessary to provide the service: name, date, number of guests, special requests, and — where necessary for contact — your contact details. The partner business is independently responsible for processing this data to provide its service. For restaurant reservations, the restaurant also receives your email address and phone number, the risk assessment with its reasons, and any messages, reviews, and feedback you address to the restaurant.

Stripe

Payment service provider (Stripe Payments Europe, Ltd., Ireland, with group companies in the USA). Processes payment and card data, and for partner businesses, identity verification data required by law. Stripe acts as an independent controller for its own regulatory and anti-money laundering obligations.

Resend

Sending our emails (Resend, USA). Processes recipient address and message content.

Microsoft 365

Our mailbox hello@memply.app for correspondence with you (Microsoft 365, provided through GoDaddy; Microsoft, with group companies in the USA). Processes sender, recipients, content and attachments of the emails you exchange with us. Microsoft processes data as a processor under our instructions.

Hetzner

Hosting our servers and backups (Hetzner Online GmbH, Germany). Data centers are located in Germany. Hetzner processes data as a processor under our instructions.

Meta

Operator of Instagram and Facebook (Meta Platforms Ireland Ltd., Ireland, with group companies in the USA). Processes your Instagram or Facebook login and sends us the details listed above when you connect an Instagram account or a Facebook Page. Meta is an independent controller for processing on Instagram and Facebook themselves; Meta's data policies apply.

TikTok

Operator of TikTok (for users in the European Economic Area, TikTok Technology Limited, Ireland, with group companies outside the EU). Processes your TikTok login and sends us the account details listed above when you connect a TikTok account. TikTok is an independent controller for processing on TikTok itself; TikTok's privacy policy applies.

Google (YouTube)

Operator of YouTube (Google Ireland Limited, Ireland, with group companies in the USA). Processes your Google login and sends us, through the YouTube API Services, the channel details listed above when you connect a YouTube channel. Google is an independent controller for processing on YouTube itself; the Google Privacy Policy (https://policies.google.com/privacy) applies.

Anthropic

Machine translation of texts into other languages (Anthropic, USA): offer and restaurant descriptions that partners publish, and our email templates, in which names and greetings are replaced by placeholders, and our personal replies to partnership requests from businesses, as we wrote them, including the greeting. Anthropic also answers messages to Memy, the assistant in the partner portal, and reads restaurant menus; in doing so, business details are transmitted. Memy does not retrieve guest names or contact details, only occupancy figures; they only reach Anthropic if the business writes them into a message itself. Anthropic processes the data as a processor under our instructions and does not use it to train its models.

We also share data where we are legally required to do so, such as to authorities or courts.

6. Transfers to third countries

Our servers and the vast majority of processing are located in the European Union. Stripe, Resend, Microsoft 365, Anthropic and Meta may process data in the United States.

We base these transfers on the European Commission's Standard Contractual Clauses or the recipient's participation in the EU-US Data Privacy Framework. We provide information about the safeguards in place upon request.

7. Storage duration

Account data

Until you delete your account. We then delete or anonymise it unless statutory retention obligations prevent this.

Booking and payment data

For as long as commercial and tax law retention obligations under Spanish law apply. These periods are several years and continue independently of account deletion.

Partnership requests to businesses

Until the business objects or asks for erasure, and at most two years after the last contact. After erasure we keep only a checksum of the email address and the domain so that the business is not contacted again, together with a note if it objected. The records of our replies and meeting emails (text, opening, clicks, page visits) are deleted two years after sending. For meetings that do not belong to any of our contacts, we remove the personal details two years after the meeting.

Confirmation codes and login sessions

Until the code or session expires.

Travel journal and uploaded media

Until you delete them or have your account deleted.

Security and change logs

As long as necessary for auditability and abuse prevention.

Messages about restaurant reservations

Messages exchanged in the app are deleted automatically twelve months after they were sent, as are the recipient lists of restaurant campaigns together with the record of opens.

Loyalty points and no-shows

Loyalty points expire twelve months after they are credited and are deleted together with your account. The no-show count only takes the last twelve months into account.

Restaurant guest books

Until the restaurant deletes the entries. We do not delete them on our own initiative.

Usage measurement

Individual events and sessions are deleted automatically after 90 days. After that only daily totals remain, with no link to any person.

Push identifiers

Until your account is deleted.

Spots, comments and voice messages

Until you delete them. If you delete your account without removing them first, they appear as “Deleted account”.

Conversations with Memy

We automatically delete conversations including attachments 90 days after the last message, and immediately when the account is deleted. Afterwards only the usage per call (amount of text processed and cost) remains, without content.

Backups

Deleted data may still be present in backups until the backup cycle completes and they are overwritten.

8. Storage on your device

We do not use cookies for analytics or advertising and do not integrate third-party tracking services. We store on your device only what is necessary for operation:

• Login credentials: On the website as a cookie, in the partner portal and admin interface in the browser local storage, in the app in the encrypted key store of your operating system. They keep you logged in and are removed on logout.
• Language choice: Your language selection in the partner portal, so the interface appears in the same language on your next visit.
• Cookie notice confirmation: a cookie remembering that you have seen the notice, so that it does not reappear on every page.

This storage is essential for the service you have explicitly requested and therefore requires no consent. We tell you about it on your first visit; there is nothing for you to choose, because there is nothing non-essential you could object to. As soon as that changes, we will ask beforehand — with equally prominent accept and reject buttons.

Which cookies we set in detail, with their lifetime and purpose, is set out in the cookie policy.

9. Your rights

You have the following rights against us:

• Access to information about whether and which data we process about you (Art. 15 GDPR).
• Rectification of incorrect and completion of incomplete data (Art. 16 GDPR).
• Deletion of your data where no retention obligation applies (Art. 17 GDPR).
• Restriction of processing (Art. 18 GDPR).
• Receipt of data you have provided in a standard, machine-readable format and transmission to another controller (Art. 20 GDPR).
• Objection to processing based on our legitimate interests (Art. 21 GDPR).
• Withdrawal of given consent with future effect (Art. 7(3) GDPR).

To exercise these rights, send an informal message to hello@memply.app. We respond within one month. To prevent disclosure to unauthorised persons, we may request additional information to confirm your identity.

10. Right to lodge a complaint

If you believe we are processing your data unlawfully, you may lodge a complaint with a supervisory authority. The Spanish data protection authority is responsible:

Agencia Española de Protección de Datos (AEPD)

C/ Jorge Juan 6, 28001 Madrid, Spain — www.aepd.es

You may also contact the supervisory authority in your country of habitual residence.

11. Necessity of information

To create an account, we require your email address and phone number. To make a booking, we additionally require booking-related information and, for offers with age restrictions, your date of birth. Without these, we cannot provide an account or booking. All other information is voluntary; its absence has no disadvantages except that the relevant feature is unavailable.

12. Minors

Our service is intended for adults. We do not create accounts for persons under 14 years of age. For use by minors from age 14, Spanish data protection law applies. Some categories have an additional, separately stated higher age limit.

If you notice that a child has created an account without required consent, please write to us — we will delete it.

13. Automated decisions and assessments

Our day plan suggestions are based on fixed, comprehensible rules — availability, time windows, travel time, budget, and your stated preferences — and are merely suggested to you; booking happens only through your own selection.

There is one automated decision: the reservation block after repeated no-shows (section “Restaurant reservations”). It is based on markings set by restaurant staff, and you can object to each individual marking within 48 hours. If you think a block is unjustified, write to us at the email address given above.

The risk assessment for restaurants is an evaluation of your reservation behaviour according to fixed rules. It does not trigger anything by itself; it serves the restaurant as an indication.

14. Security

Your connection to our services is encrypted throughout. We store passwords exclusively as a cryptographic hash. Access to administrative functions is tied to roles and individual permissions and is logged. Documentation uploaded by partner businesses is stored in a non-publicly accessible area.

15. Changes to this policy

We update this policy when processing changes — for example, when a feature is added or a service provider changes. This published version with the date above is authoritative. For material changes, we will notify you via the app or email.