Data Processing Agreement (controller–processor) — Caravel Imo
Version: imo-dpa-1.0 · 14/11/2026
The Portuguese version is the reference text; this English version is provided for information.
Parties: the real estate agency that accepts this agreement at Caravel Imo sign-up, as controller, and Jardim Idílico Unipessoal Lda (brand Caravel Suite), VAT number PT518764532, Rua da Póvoa, n.º 775, Fração L, Zona Industrial de Amorim, 4495-121 Póvoa de Varzim, Portugal, as processor. Contact: caravel@caravelsuite.com.
Subject matter: the processing of personal data that the processor carries out on behalf of the agency when providing the Caravel Imo service (Article 28 of Regulation (EU) 2016/679, GDPR). Data that Caravel Suite processes as controller (account, invoicing and payment of the subscription) is outside this agreement and is governed by the Caravel Suite Privacy Policy.
Template used (official text, Clauses unmodified): Commission Implementing Decision (EU) 2021/915 of 4 June 2021 on standard contractual clauses between controllers and processors under Article 28(7) of Regulation (EU) 2016/679 (OJ L 199, 7.6.2021, p. 18).
- EUR-Lex (ELI): https://eur-lex.europa.eu/eli/dec_impl/2021/915/oj
- EUR-Lex (EN): https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32021D0915
Options chosen: Clause 1(a) for the GDPR; Clause 5 (docking) not used; Clause 7.7, Option 2 (general written authorisation) with 30 days' prior notice. The agreement has three parts: A (additional clauses, allowed by Clause 2(b)), B (standard contractual clauses) and Annexes I to IV.
Part A — Conclusion and performance (additional clauses, Clause 2(b))
A.1 Conclusion. This agreement is concluded by electronic acceptance at Caravel Imo sign-up. Caravel Imo records the URL and version of the accepted text, its SHA-256 fingerprint, the date and time (UTC) and the email of the person accepting. From that moment the agency is a Party as controller, and Annex I is completed with the details given at sign-up and in the account Settings. The agency may request by email a counterpart signed by both Parties, with the same text.
A.2 Main contract. This agreement forms part of the Caravel Suite Terms of Service applicable to Caravel Imo (the "Contract"). In case of contradiction the Clauses prevail (Clause 4).
A.3 Duration. This agreement applies for as long as the Contract lasts and, after that, until the return or deletion of the data under Part A.6 and Clause 10(d).
A.4 Documented instructions (Clause 7.1). The agency's documented instructions are: (i) this agreement and the Contract; (ii) the agency's and its users' configuration and use of Caravel Imo features, such as creating, editing, publishing, importing, exporting and deleting records, enabling portal feeds, and sending property sheets, documents for signature or owner summaries by email; (iii) written requests sent from an agency email address to caravel@caravelsuite.com.
A.5 Breach notification (Clause 9.2). Without prejudice to the obligation to notify "without undue delay", the processor aims to send the initial notification within 48 hours of becoming aware of the breach. It is sent to the account owner's email (role "owner") and to the agency email in Settings.
A.6 End of processing (Clause 10(d)).
- While the account is suspended, or after the subscription ends, the account owner can download all data as a ZIP (Account → Export). The ZIP contains one JSON file per table and the photos.
- The agency chooses, by email to caravel@caravelsuite.com, between return (the ZIP) and deletion.
- If the agency does not choose, the processor deletes the agency's data from the production database 90 days after the subscription ends. Backups then expire through the 14-day rotation.
- The processor confirms the deletion in writing, unless Union or Member State law requires storage.
A.7 Assistance (Clause 8). Caravel Imo gives the agency tools for data subject rights:
- view and correct contacts;
- export one contact or all data;
- delete a contact, with its consents, searches and activities;
- consent records per purpose, with the policy version;
- turn off at any time the email summary sent to an owner (the owner can also stop it through the link in every email);
- revoke an owner's access link to the owner area;
- a configurable retention period, which is informational: it does not delete anything automatically.
If a data subject's request reaches Caravel directly, it is forwarded to the agency email (Clause 8(a)).
A.8 Changes to this agreement. A new version of this agreement is notified by email to the account owner at least 30 days in advance. Changes to the list of sub-processors follow Clause 7.7. The version accepted by each agency is recorded (Part A.1).
A.9 Governing law. Portuguese law, without prejudice to the GDPR.
Part B — Standard contractual clauses (official text of Implementing Decision (EU) 2021/915)
SECTION I
Clause 1
Purpose and scope
(a) The purpose of these Standard Contractual Clauses (the Clauses) is to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation).
(b) The controllers and processors listed in Annex I have agreed to these Clauses in order to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 and/or Article 29(3) and (4) of Regulation (EU) 2018/1725.
(c) These Clauses apply to the processing of personal data as specified in Annex II.
(d) Annexes I to IV are an integral part of the Clauses.
(e) These Clauses are without prejudice to obligations to which the controller is subject by virtue of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
(f) These Clauses do not by themselves ensure compliance with obligations related to international transfers in accordance with Chapter V of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
Clause 2
Invariability of the Clauses
(a) The Parties undertake not to modify the Clauses, except for adding information to the Annexes or updating information in them.
(b) This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a broader contract, or from adding other clauses or additional safeguards provided that they do not directly or indirectly contradict the Clauses or detract from the fundamental rights or freedoms of data subjects.
Clause 3
Interpretation
(a) Where these Clauses use the terms defined in Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively, those terms shall have the same meaning as in that Regulation.
(b) These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively.
(c) These Clauses shall not be interpreted in a way that runs counter to the rights and obligations provided for in Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or in a way that prejudices the fundamental rights or freedoms of the data subjects.
Clause 4
Hierarchy
In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties existing at the time when these Clauses are agreed or entered into thereafter, these Clauses shall prevail.
Clause 5 - Optional
Not used by the Parties.
SECTION II
OBLIGATIONS OF THE PARTIES
Clause 6
Description of processing(s)
The details of the processing operations, in particular the categories of personal data and the purposes of processing for which the personal data is processed on behalf of the controller, are specified in Annex II.
Clause7
Obligations of the Parties
7.1. Instructions
(a) The processor shall process personal data only on documented instructions from the controller, unless required to do so by Union or Member State law to which the processor is subject. In this case, the processor shall inform the controller of that legal requirement before processing, unless the law prohibits this on important grounds of public interest. Subsequent instructions may also be given by the controller throughout the duration of the processing of personal data. These instructions shall always be documented.
(b) The processor shall immediately inform the controller if, in the processor’s opinion, instructions given by the controller infringe Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or the applicable Union or Member State data protection provisions.
7.2. Purpose limitation The processor shall process the personal data only for the specific purpose(s) of the processing, as set out in Annex II, unless it receives further instructions from the controller.
7.3. Duration of the processing of personal data Processing by the processor shall only take place for the duration specified in Annex II.
7.4. Security of processing
(a) The processor shall at least implement the technical and organisational measures specified in Annex III to ensure the security of the personal data. This includes protecting the data against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to the data (personal data breach). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risks involved for the data subjects.
(b) The processor shall grant access to the personal data undergoing processing to members of its personnel only to the extent strictly necessary for implementing, managing and monitoring of the contract. The processor shall ensure that persons authorised to process the personal data received have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
7.5. Sensitive data If the processing involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (“sensitive data”), the processor shall apply specific restrictions and/or additional safeguards.
7.6. Documentation and compliance
(a) The Parties shall be able to demonstrate compliance with these Clauses.
(b) The processor shall deal promptly and adequately with inquiries from the controller about the processing of data in accordance with these Clauses.
(c) The processor shall make available to the controller all information necessary to demonstrate compliance with the obligations that are set out in these Clauses and stem directly from Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725. At the controller’s request, the processor shall also permit and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or an audit, the controller may take into account relevant certifications held by the processor.
(d) The controller may choose to conduct the audit by itself or mandate an independent auditor. Audits may also include inspections at the premises or physical facilities of the processor and shall, where appropriate, be carried out with reasonable notice.
(e) The Parties shall make the information referred to in this Clause, including the results of any audits, available to the competent supervisory authority/ies on request.
7.7. Use of sub-processors
(a) OPTION 2: GENERAL WRITTEN AUTHORISATION: The processor has the controller’s general authorisation for the engagement of sub-processors from an agreed list. The processor shall specifically inform in writing the controller of any intended changes of that list through the addition or replacement of sub-processors at least 30 (thirty) days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the concerned sub-processor(s). The processor shall provide the controller with the information necessary to enable the controller to exercise the right to object.
(b) Where the processor engages a sub-processor for carrying out specific processing activities (on behalf of the controller), it shall do so by way of a contract which imposes on the sub-processor, in substance, the same data protection obligations as the ones imposed on the data processor in accordance with these Clauses. The processor shall ensure that the sub-processor complies with the obligations to which the processor is subject pursuant to these Clauses and to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
(c) At the controller’s request, the processor shall provide a copy of such a sub-processor agreement and any subsequent amendments to the controller. To the extent necessary to protect business secret or other confidential information, including personal data, the processor may redact the text of the agreement prior to sharing the copy.
(d) The processor shall remain fully responsible to the controller for the performance of the sub-processor’s obligations in accordance with its contract with the processor. The processor shall notify the controller of any failure by the subprocessor to fulfil its contractual obligations.
(e) The processor shall agree a third party beneficiary clause with the sub-processor whereby - in the event the processor has factually disappeared, ceased to exist in law or has become insolvent - the controller shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
7.8. International transfers
(a) Any transfer of data to a third country or an international organisation by the processor shall be done only on the basis of documented instructions from the controller or in order to fulfil a specific requirement under Union or Member State law to which the processor is subject and shall take place in compliance with Chapter V of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725.
(b) The controller agrees that where the processor engages a sub-processor in accordance with Clause 7.7. for carrying out specific processing activities (on behalf of the controller) and those processing activities involve a transfer of personal data within the meaning of Chapter V of Regulation (EU) 2016/679, the processor and the sub-processor can ensure compliance with Chapter V of Regulation (EU) 2016/679 by using standard contractual clauses adopted by the Commission in accordance with of Article 46(2) of Regulation (EU) 2016/679, provided the conditions for the use of those standard contractual clauses are met.
Clause 8
Assistance to the controller
(a) The processor shall promptly notify the controller of any request it has received from the data subject. It shall not respond to the request itself, unless authorised to do so by the controller.
(b) The processor shall assist the controller in fulfilling its obligations to respond to data subjects’ requests to exercise their rights, taking into account the nature of the processing. In fulfilling its obligations in accordance with (a) and (b), the processor shall comply with the controller’s instructions
(c) In addition to the processor’s obligation to assist the controller pursuant to Clause 8(b), the processor shall furthermore assist the controller in ensuring compliance with the following obligations, taking into account the nature of the data processing and the information available to the processor:
(1) the obligation to carry out an assessment of the impact of the envisaged processing operations on the protection of personal data (a ‘data protection impact assessment’) where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons;
(2) the obligation to consult the competent supervisory authority/ies prior to processing where a data protection impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk;
(3) the obligation to ensure that personal data is accurate and up to date, by informing the controller without delay if the processor becomes aware that the personal data it is processing is inaccurate or has become outdated;
(4) the obligations in Article 32 of Regulation (EU) 2016/679.
(d) The Parties shall set out in Annex III the appropriate technical and organisational measures by which the processor is required to assist the controller in the application of this Clause as well as the scope and the extent of the assistance required.
Clause 9
Notification of personal data breach
In the event of a personal data breach, the processor shall cooperate with and assist the controller for the controller to comply with its obligations under Articles 33 and 34 of Regulation (EU) 2016/679 or under Articles 34 and 35 of Regulation (EU) 2018/1725, where applicable, taking into account the nature of processing and the information available to the processor.
9.1 Data breach concerning data processed by the controller
In the event of a personal data breach concerning data processed by the controller, the processor shall assist the controller:
(a) in notifying the personal data breach to the competent supervisory authority/ies, without undue delay after the controller has become aware of it, (unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons);
(b) in obtaining the following information which, pursuant to Article 33(3) of Regulation (EU) 2016/679, shall be stated in the controller’s notification, and must at least include:
(1) the nature of the personal data including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
(2) the likely consequences of the personal data breach;
(3) the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.
Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
(c) in complying, pursuant to Article 34 of Regulation (EU) 2016/679, with the obligation to communicate without undue delay the personal data breach to the data subject, when the personal data breach is likely to result in a high risk to the rights and freedoms of natural persons.
9.2 Data breach concerning data processed by the processor
In the event of a personal data breach concerning data processed by the processor, the processor shall notify the controller without undue delay after the processor having become aware of the breach. Such notification shall contain, at least:
(a) a description of the nature of the breach (including, where possible, the categories and approximate number of data subjects and data records concerned);
(b) the details of a contact point where more information concerning the personal data breach can be obtained;
(c) its likely consequences and the measures taken or proposed to be taken to address the breach, including to mitigate its possible adverse effects.
Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
The Parties shall set out in Annex III all other elements to be provided by the processor when assisting the controller in the compliance with the controller’s obligations under Articles 33 and 34 of Regulation (EU) 2016/679.
SECTION III
FINAL PROVISIONS
Clause 10
Non-compliance with the Clauses and termination
(a) Without prejudice to any provisions of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725, in the event that the processor is in breach of its obligations under these Clauses, the controller may instruct the processor to suspend the processing of personal data until the latter complies with these Clauses or the contract is terminated. The processor shall promptly inform the controller in case it is unable to comply with these Clauses, for whatever reason.
(b) The controller shall be entitled to terminate the contract insofar as it concerns processing of personal data in accordance with these Clauses if:
(1) the processing of personal data by the processor has been suspended by the controller pursuant to point (a) and if compliance with these Clauses is not restored within a reasonable time and in any event within one month following suspension;
(2) the processor is in substantial or persistent breach of these Clauses or its obligations under Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725;
(3) the processor fails to comply with a binding decision of a competent court or the competent supervisory authority/ies regarding its obligations pursuant to these Clauses or to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
(c) The processor shall be entitled to terminate the contract insofar as it concerns processing of personal data under these Clauses where, after having informed the controller that its instructions infringe applicable legal requirements in accordance with Clause 7.1 (b), the controller insists on compliance with the instructions.
(d) Following termination of the contract, the processor shall, at the choice of the controller, delete all personal data processed on behalf of the controller and certify to the controller that it has done so, or, return all the personal data to the controller and delete existing copies unless Union or Member State law requires storage of the personal data. Until the data is deleted or returned, the processor shall continue to ensure compliance with these Clauses.
ANNEX I — List of parties
Controller(s): 1. Name: the real estate agency that accepts this agreement at Caravel Imo sign-up, with the legal name, tax number and AMI licence number given in the account Settings. Address: the address given in the account Settings. Contact person's name, position and contact details: the account owner (role "owner"), at the sign-up email; and the agency email in Settings. Signature and accession date: electronic acceptance at sign-up (Part A.1). The date and time are recorded in Caravel Imo.
Processor(s): 1. Name: Jardim Idílico Unipessoal Lda, brand Caravel Suite, VAT number PT518764532. Address: Rua da Póvoa, n.º 775, Fração L, Zona Industrial de Amorim, 4495-121 Póvoa de Varzim, Portugal. Contact person's name, position and contact details: the management of Jardim Idílico Unipessoal Lda, caravel@caravelsuite.com. No data protection officer has been designated. Signature and accession date: the agency's acceptance at sign-up applies to both Parties from that date (Part A.1).
ANNEX II — Description of the processing
Categories of data subjects whose personal data is processed
- The agency's clients and prospective clients: buyers, sellers, owners and landlords, and tenants.
- People who send contact requests through the agency's public website.
- Parties to and participants in documents prepared in Caravel Imo, and their signatories: clients, co-owners, usufructuaries, attorneys, spouses, prospective buyers and the agency's representative.
- The agency's users in Caravel Imo: owner, managers, agents and read-only users.
- People identified in free text written by the agency, for example in notes or descriptions.
Categories of personal data processed
- Contacts: name, email, phone, tax number, address, type (buyer, seller, tenant), source, responsible agent and creation date.
- Consents: purpose (contact, marketing), granted or not, source, policy version and date.
- Client searches: area, minimum and maximum price, bedrooms, purchase or rental.
- Activities and history: notes, tasks and viewings (free text, date, linked property) and the contact's event log.
- Offers and deals: amount, status, description, stage, deal value and commission.
- Properties: exact address (visible only in the dashboard), postcode, parish, municipality, district, coordinates, features, descriptions, energy certificate, virtual tour and floor plan links, linked owner (CRM contact) and photos. EXIF metadata is removed on upload. Photos may show people or interiors.
- Documents and electronic signature: the text and fields of documents (brokerage agreement, reservation, draft promissory contract or other), which may include name or company name, tax number, identity document number and expiry, marital status, matrimonial property regime and spouse's name, residence or registered office, land and tax registry details of the property, price, deposit and payment method; the original and final PDFs with their SHA-256 fingerprint; for signatories, the name, email, capacity, language, the name typed when signing, date and time, IP address and browser (user agent), any refusal and its reason; the hash-chained event trail. The personal link and the one-time code are stored only as hashes.
- Owner area and summaries: personal access link (stored only as a hash), expiry, revocation and last access date; choice of the email summary (weekly or every four weeks), language, last sent date and the key of the stop link. The summary contains the property's status and price, number of views, number of interested people, viewings and offers (dates, statuses and amounts), never the name, contact details or message of anyone who views or makes an offer.
- Import from another program: the content of the CSV or XML file uploaded by the agency, kept only for review before saving; it is deleted when the import is saved or cancelled and can no longer be used after 24 hours.
- Agency users: email, role and permissions. Sessions and sign-in links are stored only as hashes.
- Technical data: outside electronic signatures, the IP address of people using the public website or the dashboard is used only as a hash, to limit abuse (expiring rate limits). The Caravel Imo application and its nginx proxy keep no HTTP access log. The nginx error log, which may contain the IP, rotates in 14 days.
Sensitive data processed (if applicable) and applied restrictions or safeguards
- Caravel Imo is not intended for sensitive data and does not ask for it.
- The agency undertakes not to enter it in free text, documents or photos, unless strictly necessary and lawful.
- If it does, the Annex III measures apply: access limited to agency users with permission, and the record can be deleted.
Nature of the processing
- Hosting, storage, organisation, consultation, alteration and erasure.
- Publication on the agency's public website and in the feeds the agency enables: Kyero XML, Imovirtual (OLX format), own XML/JSON and sitemap. Only property data is published: the exact address is always left out and coordinates are rounded (about 100 m) unless the agency chooses to show the exact location. The portals that read these feeds are recipients chosen by the agency, which contracts with them directly; they are not sub-processors under this agreement.
- Import of properties from CSV or Kyero XML files uploaded by the agency.
- Preparation of documents and collection of simple electronic signatures, sending the link and the code to each signatory's email.
- Sending emails requested by the agency: property sheets to its clients, signature requests, access links and periodic summaries to owners, and reminders to its users.
- CSV/ZIP export, backups and erasure.
Purpose(s) for which the personal data is processed on behalf of the controller Providing the agency with the Caravel Imo service: property portfolio management, CRM, calendar and deal pipeline, documents and electronic signature, owner area and summaries, the agency's public website with contact form, feeds to portals chosen by the agency, import, emails requested by the agency, export and backups. Caravel does not use the agency's data for its own purposes, for advertising or for model training.
Duration of the processing For the duration of the Caravel Imo subscription and, after it ends or is suspended, until return or deletion under Part A.6 and Clause 10(d). Backups rotate in 14 days.
For processing by (sub-)processors, also specify subject matter, nature and duration of the processing
- Contabo GmbH: hosting of the virtual machine running the application, the database, the photos and the backups. All the data above, for the whole processing.
- Hostinger International Ltd: SMTP delivery of Caravel Imo emails: sign-in links to agency users; property sheets sent by the agency to its clients (recipient email, agency name, property title and link); signature requests (signatory's name and email, document title, link and one-time code); access links and summaries to owners (owner's name and email and the summary content described above); reminders to users (contact name, property title, date). Caravel Imo keeps no copy of the messages in a mailbox; Hostinger's processing lasts for the delivery and for the retention of technical delivery logs under Hostinger's data processing agreement.
ANNEX III — Technical and organisational measures including technical and organisational measures to ensure the security of the data
Concrete description of the measures in place on the production server (verified on 13 and 14/11/2026).
Pseudonymisation and encryption
- In transit: mandatory HTTPS (TLS 1.2 and 1.3, Let's Encrypt certificate), with HSTS (max-age 1 year) sent by the application. The application refuses to start without HTTPS outside development mode.
- Email: SMTP with STARTTLS and certificate verification (port 587).
- Billing events between the Caravel Checkout and Imo: signed with HMAC-SHA256 with a ±300 s window.
- Sessions, sign-in links, signature links, one-time codes and owner links: stored only as SHA-256 hashes. There are no passwords: sign-in is by a personal link valid for 15 minutes.
- At rest: the server disk is not encrypted. The SQLite database and the photos are in a folder accessible only to the service user (permissions 0700). The database overwrites deleted content (secure_delete).
Confidentiality, integrity, availability and resilience
- The service runs as its own system user (caravel-imo) and listens only on 127.0.0.1, behind nginx.
- systemd hardening: ProtectSystem=strict, ProtectHome, PrivateTmp, PrivateDevices, NoNewPrivileges, no capabilities, write access only to the data folder, memory limit.
- Secrets (Checkout key, SMTP password) are passed to the process as systemd credentials, from files with mode 600 readable only by root. They are never in environment variables or in the code.
- Firewall (ufw): only SSH, HTTP and HTTPS open to the outside.
- SSH by key only: password login disabled; root by key only.
- Isolation between agencies: every record carries the agency identifier and every query filters by it.
- Signed documents: SHA-256 fingerprint of the original and final PDF; each trail event stores the previous event's hash, so a change in the middle invalidates the chain.
Restoring availability (backups)
- Daily backup at 03:40 UTC: SQLite database through the backup API, checked with quick_check, plus the photos as tar.gz and SHA-256 sums.
- Kept for 14 days in a folder accessible only to the service user, on the same server. At the date of this version there is no copy of Caravel Imo outside that server.
Testing and regular evaluation
- Automated test suite run before every deployment.
- End-to-end product audit on 13/11/2026 and test-mode rehearsal of the payment chain on the same date.
- The processor reviews these measures at least once a year and whenever there is a relevant change to the service or the hosting.
User identification and authorisation
- Sign-in by a personal link sent to the user's email, valid for 15 minutes and single-use. Sessions last 12 hours.
- HttpOnly, Secure and SameSite=Lax cookies. CSRF protection on every form.
- Attempt limits per address and per email.
- Per-user roles (owner, manager, agent, read-only) and fine-grained permissions: edit portfolio, manage CRM, export, see only own records.
- The owner deactivates users.
- Signatories: personal link valid for 14 days and a code sent to the same email, valid for 10 minutes, with at most 5 attempts.
- Owners: personal link valid for 90 days, which the agency can revoke.
Protection during transmission and storage. See "Pseudonymisation and encryption".
- On the public website: restrictive Content-Security-Policy, X-Frame-Options DENY and Referrer-Policy same-origin.
- The exact property address is never published on the public website or in feeds; coordinates are rounded (about 100 m) unless the agency chooses otherwise.
- Portal feeds are protected by a key specific to each agency, which the agency can replace.
Physical security. Contabo GmbH data centre in the EU (Lauterbourg, France). Physical security is the provider's responsibility under its contract and its data processing agreement.
Event logging
- The Caravel Imo application and its nginx proxy keep no HTTP access log, so that personal data is not kept in logs.
- Billing events received are logged (identifier, type, result).
- The contact history, consent dates and the trail of each document sent for signature are recorded.
Default configuration
- New contacts from the public website only with explicit contact consent. Marketing consent is separate and optional.
- Properties start as drafts; imported properties are saved as drafts without photos.
- The email summary to an owner is off until the agency turns it on for that owner.
- EXIF metadata is removed from photos.
- Demo mode is always off in production (enforced in the systemd unit).
Internal governance. Administrative access to the server is limited to the processor's management and the people it authorises, who are bound by confidentiality (Clause 7.4(b)). The content of the agency's data is only accessed when needed to provide or maintain the service, on the agency's instruction or to comply with the law.
Data minimisation and quality. Fields are those needed for the service; outside electronic signatures, the IP is only used as a hash and expires. The agency corrects data in the dashboard.
Storage limitation
- Configurable retention period per agency (365 days by default): informational; it does not delete anything automatically.
- Manual deletion of contacts with related data.
- 14-day backup rotation.
- Deletion at the end of the contract: Part A.6.
Portability and erasure
- Export of all data (ZIP with one JSON file per table and photos), available even while the account is suspended.
- CSV export of properties.
- Deletion of contacts in the dashboard. Deletion of the agency on request (Part A.6).
Measures to assist the controller (Clauses 8 and 9). The tools in Part A.7. Contact caravel@caravelsuite.com. Breach notification under Clause 9.2 and Part A.5, with the information under Article 33(3) GDPR that is available.
ANNEX IV — List of sub-processors
(Clause 7.7(a), Option 2: agreed list; changes with 30 days' notice by email to the account owner.)
1. Name: Contabo GmbH. Address: Welfenstrasse 22, 81541 Munich, Germany. Contact: the data protection officer named in Contabo's privacy policy (https://contabo.com/en/legal/privacy/). Description of the processing: hosting of the production virtual machine (application, database, photos and backups). Location: data centre in Lauterbourg, France (EU). No transfer outside the EEA. 2. Name: Hostinger International Ltd. Address: 61 Lordou Vironos str., 6023 Larnaca, Cyprus. Contact: gdpr@hostinger.com. Description of the processing: email service (SMTP server smtp.hostinger.com, sender caravel@caravelsuite.com) used by Caravel Imo to send the emails described in Annex II. EU entity (Cyprus). Hostinger does not publicly state the country of its email servers and uses its own sub-processors; any transfer outside the EEA it makes is covered by the standard contractual clauses of Implementing Decision (EU) 2021/914 (Modules 2 and 3), under its data processing agreement (https://www.hostinger.com/legal/dpa) and Clause 7.8.