HostelKeep Data Processing Agreement
Version 1.0 · Effective from 11 November 2026 · hostelkeep.com/dpa
Earlier versions are available on request at privacy@kohciaostudio.com
This Data Processing Agreement ("DPA") is part of the HostelKeep Terms of Service between the business that uses HostelKeep ("the Customer", controller) and KohCiao Studio di Casasco Matteo, Via Cerruti 16, 15050 Avolasca (AL), Italy, VAT 02820820062 ("KohCiao Studio", processor). It meets article 28 of the EU General Data Protection Regulation 2016/679 ("GDPR") and, where they apply, the UK GDPR and the Swiss Federal Act on Data Protection. It is accepted together with the Terms.
#1. Subject, duration, nature and purpose
1.1 KohCiao Studio processes personal data on behalf of the Customer only to provide HostelKeep as described in the Terms: hosting, storing, showing, transmitting, backing up and deleting the data the Customer and its users put into the Service, and sending notifications when the Service needs to.
1.2 The DPA lasts as long as KohCiao Studio processes personal data for the Customer, including the export and deletion period after the end of the contract.
1.3 Details (people, data, retention) are in Annex 1.
#2. Instructions
2.1 KohCiao Studio processes personal data only on the Customer's documented instructions. The Terms, this DPA and the Customer's use of the Service's features and settings are those instructions. Other instructions must be in writing and compatible with the Service.
2.2 If KohCiao Studio believes an instruction breaks data protection law, it tells the Customer and may suspend that instruction.
2.3 If the law requires KohCiao Studio to process data in another way, it tells the Customer first, unless the law forbids it.
#3. Confidentiality
Only people who need access to provide or support the Service have it, and they are bound to confidentiality in writing. Today administrative access to the production data is held by Matteo Casasco alone, through the Google Cloud (Firebase) console.
#4. Security
KohCiao Studio applies the technical and organisational measures in Annex 2, appropriate to the risk, and keeps them up to date. It may change them as long as the overall level of protection does not go down.
#5. Sub-processors
5.1 The Customer gives general authorisation to use the sub-processors in Annex 3.
5.2 KohCiao Studio informs the Customer by email (owner and billing contact) and in the app at least 30 days before adding or replacing a sub-processor. The Customer may object on reasonable data-protection grounds within that time; if no solution is found, the Customer may terminate the affected Service and receive a refund of the unused prepaid part.
5.3 KohCiao Studio imposes on each sub-processor data-protection obligations equivalent to this DPA, and remains responsible for them towards the Customer.
#6. International transfers
6.1 Customer Data is stored in the EU (Google Cloud multi-region "eur3": Belgium and the Netherlands).
6.2 Some sub-processors in Annex 3 may access or process limited data outside the EU/EEA (for example to deliver a push notification to a phone). Each such transfer relies on an adequacy decision (such as the EU–US Data Privacy Framework for certified providers) or on the European Commission's Standard Contractual Clauses (with the UK Addendum or Swiss amendments where needed), together with the provider's supplementary measures.
#7. Helping the Customer
7.1 Requests from people. If someone asks KohCiao Studio directly to exercise their rights on Customer Data, KohCiao Studio forwards the request to the Customer without delay and does not answer on its own, except to say it has done so. The Service lets the Customer find, correct, export and delete data; for anything it cannot do in the Service, KohCiao Studio helps on request.
7.2 KohCiao Studio helps the Customer, with the information available to it, with security, breach notification, data protection impact assessments and prior consultation (articles 32–36 GDPR).
#8. Personal data breaches
KohCiao Studio notifies the Customer without undue delay, and within 48 hours of becoming aware of a personal data breach affecting Customer Data, with what is known (what happened, data and people concerned, likely consequences, measures taken or proposed, a contact), and updates as more is learned. It takes reasonable steps to contain the breach. Notifying the authority and the people concerned remains the Customer's duty as controller, with KohCiao Studio's help.
#9. End of the contract
When the account is closed, the Customer can export its data for 30 days. KohCiao Studio then deletes Customer Data within the following 60 days, and backups are overwritten within their normal cycle, unless EU or member-state law requires keeping it. On request, KohCiao Studio confirms the deletion in writing. Cancelling a paid plan alone does not delete data: the account returns to the Free plan.
#10. Audits and information
10.1 KohCiao Studio makes available the information needed to show compliance with article 28 GDPR: this DPA, its annexes, and answers to reasonable written questions (once a year, or after a breach).
10.2 If that is not enough, the Customer may carry out an audit, or have one carried out by an independent auditor bound to confidentiality, with 30 days' notice, during working hours, without access to other customers' data, and at its own cost. Audits of sub-processors rely on their certifications and reports.
#11. Liability and precedence
11.1 Liability under this DPA follows the limits of the Terms, except where article 82 GDPR or other mandatory law provides otherwise.
11.2 If this DPA and the Terms disagree on personal data, this DPA prevails.
#Annex 1 · Details of the processing
Categories of people
- The Customer's owners, managers, housekeepers and maintenance staff who use the Service, and people they mention.
- Guests are not a category: the Service is not built for guests' personal data (Terms 8.2).
Categories of personal data
- Users: name, email (owners, managers and staff) or username (housekeepers, who sign in with the hostel code and a username), role, hostel, language; optional profile photo; the hostel's logo; sign-in data (password managed by the authentication service, last sign-in date); assignments, room and bed state changes with time and author, requests for extra rooms and their photos, maintenance tasks and their photos, checklists, notes; device addresses for notifications if the user allows them.
- Error reports: technical details of app errors (Sentry), without IP address or email.
- Activity records: who changed what and when (used for the live view and reports).
Special categories (article 9 GDPR): none. The Customer must not enter them.
Retention
- Photos attached to a request for an extra room: deleted as soon as the request is approved or rejected.
- Maintenance photos: deleted 30 days after the task is finished (the app warns 7 days before).
- Error reports (Sentry): up to 90 days.
- Rooms, cleaning states, daily history and requests: as long as the Customer keeps them, until it deletes them or closes the account (section 9).
Frequency: continuous, for the length of the contract.
#Annex 2 · Technical and organisational measures
- Location: database in the EU (Google Cloud multi-region "eur3": Belgium and the Netherlands); sign-in accounts by Firebase Authentication (see Annex 3).
- Separation between customers: each hostel's data lives under its own path (
hostels/{code}); the database security rules check, on every read and write, that the person belongs to that hostel and that their role allows the action. About 150 automated tests of these rules run before each release, including "nobody can read a user of another hostel". - Access control: sign-in with email and password (housekeepers: hostel code, username and password); no shared accounts; roles and custom permissions; the owner removes a person's access at once; the password is asked again before an account is deleted.
- Encryption: HTTPS (TLS) in transit; encryption at rest by Google Cloud.
- Photos: stored inside the database documents of the hostel (no public links), protected by the same rules; size limits (profile photo under 400 KB, request photo under 700 KB); deleted as in Annex 1.
- Logging: app errors reported to Sentry (EU region) without IP address, email, screenshots or session recordings.
- Backups and recovery: the database is kept by Google Cloud in two EU locations at once; no separate backup copies are kept at present.
- Development: code reviewed and tested before release; secrets kept out of the code; real customer data never used in development.
- People: one person with administrative access (Matteo Casasco); any staff bound to confidentiality.
- Incidents: a written breach procedure (contain, assess, notify the Customer within 48 hours, document).
#Annex 3 · Sub-processors
The list in force is published at hostelkeep.com/sub-processors.