Data processing agreement
1. Why this exists
When you use Sakura Trade to hold information about your guests, customers, suppliers or staff, you decide what happens to that information and we act on your instructions. In data-protection language you are the controller and we are your processor. This document is the agreement that relationship requires. Article 28 of the GDPR and section 21 of POPIA both oblige it to be in writing.
It is separate from our privacy notice, which covers the data we hold as controller: your own account and staff records.
2. What we process, and for whom
| Subject matter | Providing the Sakura Trade software and, where applicable, hosting it. |
| Duration | For as long as the Client's subscription runs, plus the deletion window in clause 9. |
| Nature and purpose | Storage, retrieval, organisation and transmission of records so the Client can trade: take bookings, ring up sales, run accounts, keep books. |
| Categories of data subject | The Client's guests, customers, suppliers and staff. |
| Categories of personal data | Names; contact details (phone, email, postal address); stay and event history; purchase history; amounts owed and paid; staff identity, role and action history; IP addresses of people signing in. |
| Special category data | None is required by the software and none should be entered. Free-text fields, such as a booking note or a ticket, could hold anything the Client's staff type into them, including a dietary or accessibility need. Clause 4 covers this. |
3. Our obligations
- We process personal data only on the Client's documented instructions, including for transfers, unless the law requires otherwise, in which case we tell the Client first unless that law forbids it.
- Everyone we allow near the data is bound to confidentiality.
- We apply the security measures in clause 5.
- We use sub-processors only under clause 6.
- We help the Client answer data-subject requests (clause 7).
- We help the Client with breach notification, impact assessments and consultations (clause 8), taking into account what we know and the Client does not.
- We delete or return the data at the end (clause 9).
- We make available the information needed to show compliance, and allow audits (clause 10).
- We tell the Client if an instruction of theirs appears to us to break the law. We are not their lawyer and this is not a guarantee that we will spot it.
4. What the Client is responsible for
The Client decides what goes into the system and warrants they have a lawful basis for it. In particular: do not type special-category information into free-text fields. A note reading "coeliac, room 4" is health data, and the software will treat it as an ordinary string because it cannot know otherwise. If the Client needs to record such things, they should tell us so we can design a field with the right handling rather than have it arrive by accident.
The Client is responsible for who they give accounts to and what access those accounts carry.
5. Security measures
Current as of the version date. We may change these where the replacement is equivalent or better; we will not weaken them silently.
- In transit: TLS 1.2 or better on every connection, HTTP redirected to HTTPS, HSTS.
- Passwords stored as PBKDF2 hashes, never recoverable. Till PINs likewise hashed.
- Access control: per-person accounts, per-dashboard permissions, and per-action grants for sensitive operations (refunds, price overrides, voids) with a supervisor PIN.
- Tenant isolation: every record is bound to its owning business at the database layer, so one client's records are not reachable from another's session.
- Audit trail: every money, sale and permission record keeps a full history of who changed what and when.
- Rate limiting on sign-in, per account and per IP address.
- Server access by SSH key only; password authentication disabled.
- Backups taken nightly and verified by restoring them, not merely written.
- Self-hosted installations: the data never leaves the Client's own machine, and the physical and network security of that machine is theirs.
6. Sub-processors
The Client gives general authorisation for the following. We will give 30 days' notice before adding or replacing one, and the Client may object on reasonable data-protection grounds; if we cannot resolve the objection the Client may terminate the affected service without penalty.
| Who | What they do | Where |
|---|---|---|
| Resend | Delivers transactional email, and sees the recipient address and the contents of a confirmation or bill | United States (standard contractual clauses) |
| 1984 Hosting | Hosts the shared instance and its database | Iceland (EEA) |
For self-hosted installations, only Resend applies, and only if the Client switches email on.
7. Data subject requests
If a guest or customer contacts us directly, we will not answer for the Client. We will tell them to contact the Client and let the Client know. If the Client needs help extracting, correcting or deleting a record, we will provide it within 10 working days, which leaves the Client time inside their own 30-day deadline.
8. Personal data breaches
We will notify the Client without undue delay and in any event within 48 hours of becoming aware of a breach affecting their data, with what we know: what happened, which categories and roughly how many records, the likely consequences, and what we are doing. We notify the Client, not the regulator. That call is theirs, on their 72-hour clock.
9. Deletion and return
On termination the Client may request a full export in an open format; we will provide it within 30 days. We then delete the data from live systems within a further 30 days, and it ages out of backups under the backup retention schedule (14 daily, 8 weekly, 12 monthly), so the last copy is gone within 13 months. We will confirm deletion in writing on request.
We keep nothing beyond that except what the law requires us to keep about our own dealings with the Client.
10. Audit
We will answer reasonable written questions about our processing, and provide a copy of any relevant certification or report we hold. The Client may audit on 30 days' notice, at most once a year unless there has been a breach, at their cost, during business hours and without disturbing other clients.
11. International transfers
The shared instance is hosted in Iceland, inside the EEA. Email is processed in the United States under the sub-processor's standard contractual clauses. We will not move personal data to another country without a lawful transfer mechanism and notice under clause 6.
12. Liability and precedence
Liability under this agreement is subject to the cap in the terms of service. Where this document and the terms conflict on a data-protection matter, this document wins.
13. Signature
This agreement takes effect when the Client starts using the service and needs no signature. A counter-signed copy is available on request through the contact form. Most auditors and larger clients will want one.