Data processing terms
In short: when you keep personal data about tenants and others in Rentalets, you are the controller and we are your processor. These terms set out what we may do with that data, how we protect it and what happens when you leave, as Article 28 of the GDPR requires. They form part of the terms of use and apply automatically to every account.
1. Parties and roles
These terms are between the account holder (the “controller”) and Daniel Cutajar, trading as Rentalets (the “processor”). They apply to personal data that users of the controller’s account enter or upload into the app, or that tenants submit through pages the controller shares (the “controller data”). Terms not defined here have the meaning given in the GDPR.
2. Details of the processing
| Subject matter | Providing the Rentalets app: storing, organising, displaying and reporting on the controller’s property and letting records. |
|---|---|
| Duration | While the controller’s account exists, and afterwards as in section 9. |
| Nature and purpose | Hosting, storage, retrieval, calculation, reporting, document generation, electronic signing, backup, and reading of documents and answering of requests by the AI assistant when a user asks it to. |
| Data subjects | Tenants and occupants, prospective tenants, guarantors, previous tenants, estate agents, contractors and suppliers, and the controller’s own staff and helpers. |
| Categories of data | Names and contact details; identity card or passport numbers; addresses; lease terms; rent, deposits, payments and bank transaction details including IBANs; utility accounts, meter readings and bills; inventories, condition reports and photos; signed documents, drawn signatures with the time, IP address and device of signing; maintenance reports and photos; notes and messages. |
| Special categories | None are intended. The controller should not upload health or other special category data unless it is necessary and lawful, and it is then responsible for doing so. |
3. Instructions
The processor processes controller data only on the controller’s documented instructions, which are these terms, the terms of use and the controller’s use of the app’s features, including transfers described in section 7, unless EU or Maltese law requires otherwise (in which case the processor informs the controller first, unless the law forbids it). The processor will tell the controller if it believes an instruction breaks data protection law.
4. Confidentiality
Everyone the processor authorises to process controller data is bound by confidentiality, and accesses controller data only where needed to provide, support or secure the service, or where the controller asks.
5. Security
Taking into account the state of the art, costs and risks, the processor maintains appropriate technical and organisational measures (GDPR Article 32), including:
- encryption of data in transit (HTTPS) and storage on infrastructure that encrypts data at rest;
- passwords stored only as salted PBKDF2 hashes; secure, HTTP-only session cookies; limits on repeated sign-in attempts;
- access levels for users, files available only to signed-in users or to the tenant whose page lists them, and a record of who changed what;
- the AI assistant can only use the app’s defined actions, and changes it proposes are saved only after a user confirms them; and
- a full backup download for the controller, and review of the measures as the service develops.
6. Sub-processors
The controller gives general authorisation for the processor to use sub-processors. The current sub-processors are:
| Sub-processor | Service | Location |
|---|---|---|
| Cloudflare, Inc. | Hosting, database, file storage, network and security | Global, including the United States |
| Anthropic, PBC | AI model for the assistant and document reading (only for content a user sends to it) | United States |
The processor imposes data protection obligations on each sub-processor that are in substance no less protective than these terms, and remains responsible for them. It will tell account holders by email or in the app at least 14 days before adding or replacing a sub-processor. The controller may object on reasonable data protection grounds within that period; if the parties cannot resolve the objection, the controller may close its account.
7. International transfers
Where controller data is transferred outside the European Economic Area, the processor ensures a valid transfer mechanism is in place, such as an adequacy decision (including the EU-U.S. Data Privacy Framework for certified recipients) or the European Commission’s standard contractual clauses.
8. Assistance
- Data subject requests: the app lets the controller find, export, correct and delete controller data. The processor passes on any request it receives directly and, taking into account the nature of the processing, helps the controller respond.
- Personal data breaches: the processor notifies the controller without undue delay, and where possible within 48 hours, after becoming aware of a breach affecting controller data, with the information then available, and helps the controller meet its obligations under GDPR Articles 33 and 34.
- Impact assessments and consultation: the processor provides reasonable information to help with data protection impact assessments and prior consultation with the supervisory authority.
9. End of processing
When the account closes, the controller can download a full backup for 30 days. The processor then deletes controller data from the live service, and from backups within a further 35 days, unless EU or Maltese law requires it to keep it. Data sent to the AI provider is deleted by that provider within its retention period (currently 30 days).
10. Information and audits
The processor makes available the information reasonably needed to demonstrate compliance with Article 28 GDPR, and allows audits by the controller or an auditor it appoints, on at least 30 days’ written notice, during business hours, no more than once a year (unless a supervisory authority requires otherwise or after a breach), subject to confidentiality and at the controller’s cost. Audits of sub-processors are satisfied by their published certifications and reports where possible.
11. The controller’s responsibilities
The controller is responsible for the lawfulness of the controller data and of its instructions, for having a legal basis for the processing, for giving data subjects the information they are entitled to (including that it uses Rentalets), for deciding who in its account may see what, and for sharing tenant page and signing links only with the intended people.
12. Liability and order of precedence
Each party’s liability under these terms is subject to the limitations in the terms of use, except where the GDPR does not allow it. If these terms conflict with the terms of use on the processing of personal data, these terms prevail. Maltese law applies.