Compliance

Data protection, in practice

Last updated 1 September 2026

Before you launch: the postal address and the grievance officer’s name and email below are placeholders. They are legally required to be real and reachable. Replace them, and have a lawyer read this page — it describes the system accurately, which is not the same as being legal advice.

The privacy policy says what we collect. This page says how the system actually enforces it, because a policy nothing implements is a sentence, not a protection.

Who is responsible for what

RoleWho
Data Fiduciary — for guest dataThe resort. They decide what to collect and why.
Data ProcessorMyBills Technologies. We act on the resort’s instructions.
Data Fiduciary — for account dataMyBills Technologies, for the details of the staff who hold accounts with us.

Consent, where it is actually required

An identity document cannot be stored without the guest agreeing at the moment of capture. The consent is recorded with the document, not buried in terms accepted elsewhere, and an upload without it is refused by the server rather than the screen.

Purpose limitation

Storage limitation

Identity documents carry an expiry stamped on each one and are swept automatically. Deletion removes the stored file, not just the row pointing at it.

Rights, and how they are served

RightHow
AccessA resort can export its data at any time. A guest asks the resort, or us.
CorrectionEditable in the app; write to us for account details.
ErasureDocuments are deleted on request, with a reason recorded. Records law requires us to keep are named in the privacy policy.
GrievanceOur Grievance Officer, named on the privacy page, answering within 30 days.

Breach

If personal data is exposed we notify the Data Protection Board and the people affected as the Act requires. Monitoring runs every five minutes and alerts on state change; a monitor that has stopped reporting is itself treated as a failure.