Customers and GDPR

Where: Operations → Customers. Who: cashiers, managers and owners edit; everyone views.

/admin/e/…/clienti

Searching

Search by name, phone or email (no need to worry about accents) and filter by Tag. Anonymised customers are hidden: Show anonymised to see them. The Marketing column says whether the customer gave consent.

New customer

New customer has one required field: the Last name. Phone and Email are optional (used to contact the customer and to spot duplicates, only when given). Then, also optional:

Field	Notes
First name, Language	The language of emails to the customer.
Tags	Comma separated, e.g. vip, family, regular (up to 20, 30 characters each). The vip tag shows the VIP indicator on the map; tags are also used in price rules (Customer tags).
Internal notes	Never shown to the customer. Do not write health data.
Marketing consent	Optional and separate: date, source and text version are recorded.

Arenile avoids duplicates: if the email or phone already belongs to a customer, it suggests them (Possibly already registered → Use this one).

The customer record

/admin/e/…/clienti/…

• Profile with the data and the consent (“Consent given on… (source)”).
• Statistics: Bookings, Total spent, Balance due, Available credit.
• Recent bookings, Season passes (with the released half-days), Credits with their movements (source: Cancellation, Season pass release, Bad weather, Manual, Redemption) and any expiry.
• New booking for this customer.

Customers booking online are created when they enter their details at the “Details and payment” step; the public page never links them to an existing customer with the same email or phone (whoever knows a contact detail could read their data): when the same person books again, the customer card flags the duplicate. Marketing consent given online has source “online”.

The «Walk-in customer»

Quick sales without a name (ADR 0020) are recorded on a single system customer, Cliente al banco (tag walk-in), created on first use: it will carry hundreds of bookings. It is not a person: it stays out of the top customers ranking and of the renewal campaigns, asks for no consent and is never anonymised or deleted. The optional name of a ticket stays on the ticket and never becomes a customer.

GDPR rights

Export

Export data (GDPR) downloads a JSON file with all the customer’s data: a ready answer to an access or portability request.

Anonymisation

1. In the record press Anonymise.
2. Read the warning: name, contacts, notes and consents are replaced for good; bookings and payments stay for accounting, without personal data.
3. To confirm, type the customer’s last name.
4. Anonymise permanently.

This cannot be undone

There is no way back, not even for the server administrator. Export the data first if the customer requested it.

Cancellation reasons and notes on payments and credits are deleted too. For the full picture (roles, privacy notice, response times) see Privacy and GDPR.