Data Safety

How MUSIC 4 MEMORIES LTD protects reservation data in practice.

1. Security measures

Encryption in transit: the website and Firebase APIs are accessed over HTTPS/TLS.
Managed database: reservations are stored in Google Cloud Firestore rather than on an unmanaged private server.
Least privilege access: Firestore security rules allow guests to create a reservation and retrieve a single booking by its reservation key. Listing, editing or deleting other people’s reservations from the public site is blocked.
No public password accounts: reducing credential-stuffing risk for end users.
Input limits: forms enforce length and type checks before data is written.

2. Reservation keys

Each booking receives a unique key (format similar to M4M-XXXX-XXXX). Treat this key like a booking reference: anyone who has it can view the booking status via the lookup page. Do not post keys publicly.

3. What we do not do

We do not sell personal data.
We do not ask for payment card details on this reservation form.
We do not expose a public directory of all reservations.

4. Incident response

If we become aware of a personal data breach likely to result in a risk to your rights and freedoms, we will assess the incident and, where required by UK law, notify the ICO and affected individuals without undue delay.

5. Your role

Keep your reservation key confidential.
Use a personal email you control so we can reach you about the booking.
Contact contact@music4memories.online if you suspect misuse of your key or data.

6. Controllers & processors

Controller: MUSIC 4 MEMORIES LTD, 32A Storrs Hill Road, Ossett, England WF5 0DL.

Key processor / infrastructure: Google Firebase (Firestore and Hosting, as configured for this project).