> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/privacy-and-security/data-processing-agreement.md).

# Data processing agreement

The Guestway Data Processing Agreement, with the details of the processing, the security measures and the list of sub-processors.

{% hint style="info" %}
**Version 2026.10**

* Effective from 28 September 2026.
* This page is a copy for reference. The legally binding version is the [Data Processing Agreement](https://guestway.io/contract-terms/dpa/) on the Guestway website.
  {% endhint %}

**Which version applies to you.** This version applies to customers whose agreement commences on or after 28 September 2026. Customers whose agreement commenced before that date remain governed by the version in force at the time their agreement was concluded (version 2026.09 or 2025.09), which remains available on request via <gdpr.support@guestway.io>. Existing customers who prefer to move to this version can arrange that with us at any time, and we are happy to execute it bilaterally.

**Effective Date:** for customers accepting these terms as part of the Agreement, the date on which the Agreement is concluded; where this DPA is signed separately, the date of the last signature.

This Data Processing Agreement (the "DPA") is entered into by and between:

**Guestway BV**, a company incorporated under the laws of Belgium, with registered offices at Soenenspark 1, 9051 Ghent, Belgium, registered with the Crossroads Bank for Enterprises under number 0798.195.974 (VAT BE 0798.195.974) ("Guestway" or "Processor");

and

**\[Client Name]**, \[legal form], with registered offices at \[address], registered under number \[number] (the "Customer" or "Controller").

Each a "Party" and together the "Parties".

This DPA forms part of and is subject to the Master Subscription Agreement or equivalent agreement between the Parties (the "Agreement"). In the event of a conflict between this DPA and the Agreement in respect of the Processing of Personal Data, this DPA prevails.

## Definitions

**1.1** "GDPR" means Regulation (EU) 2016/679, and where applicable the UK GDPR and the Data Protection Act 2018.

**1.2** The terms "Controller", "Processor", "Data Subject", "Personal Data", "Special Categories of Personal Data", "Personal Data Breach", "Processing" and "Supervisory Authority" have the meanings given to them in the GDPR.

**1.3** "Sub-processor" means any third party engaged by Guestway to Process Personal Data on behalf of the Customer.

**1.4** "Services" means the services provided by Guestway under the Agreement.

**1.5** "Standard Contractual Clauses" or "SCCs" means the standard contractual clauses adopted by the European Commission in Implementing Decision (EU) 2021/914.

## Roles of the parties

**2.1** The Customer acts as Controller and Guestway acts as Processor in respect of the Personal Data Processed under the Agreement.

**2.2** Where the Customer is itself a processor acting on behalf of a third party controller, the Customer warrants that it has the authority to enter into this DPA and to give the instructions set out in it, and Guestway acts as a sub-processor. References to the Controller are then construed accordingly.

**2.3** Guestway acts as Controller in respect of Personal Data it Processes for its own purposes, such as account administration, billing, and the security and improvement of the Services in aggregated or anonymised form. That Processing falls outside this DPA and is governed by Guestway's own [privacy notice](https://guestway.io/privacy/).

## Subject matter, duration and scope

**3.1** The subject matter, duration, nature and purpose of the Processing, the categories of Personal Data and the categories of Data Subjects are set out in Annex 1.

**3.2** This DPA applies for as long as Guestway Processes Personal Data on behalf of the Customer, and survives termination of the Agreement to the extent Guestway continues to hold Personal Data.

## Documented instructions

**4.1** Guestway shall Process Personal Data only on documented instructions from the Customer, including with regard to transfers of Personal Data to a third country, unless required to do so by Union or Member State law to which Guestway is subject. In that case Guestway shall inform the Customer of that legal requirement before Processing, unless the law prohibits such information on important grounds of public interest.

**4.2** The Agreement, this DPA including its Annexes, and the Customer's use and configuration of the Services constitute the Customer's complete documented instructions. Additional or alternative instructions must be agreed in writing and may be subject to additional charges where they require changes to the Services.

**4.3** Guestway shall immediately inform the Customer if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions.

**4.4** The Customer is responsible for ensuring that it has a valid legal basis for the Processing, that it has provided the required information to Data Subjects, and that its instructions comply with applicable data protection law.

## Special categories of personal data

**5.1** Where the Customer enables identity verification, Guestway and its Sub-processor Process biometric data for the purpose of uniquely identifying a natural person, which constitutes a Special Category of Personal Data under Article 9(1) GDPR. The categories concerned are described in Annex 1, section 5.

**5.2** The Customer is responsible for establishing and documenting an exception under Article 9(2) GDPR, in practice normally the explicit consent of the Data Subject under Article 9(2)(a), and for providing the information required under Articles 13 and 14 GDPR before the verification is carried out.

**5.3** Guestway shall apply the additional safeguards described in Annex 2 to this category of Personal Data, and shall make available to the Customer the configuration options described in Annex 1, section 5, including the ability to restrict the categories of data collected. Verification data is automatically and permanently erased at the Sub-processor no later than thirty (30) days after the verification.

## Confidentiality

**6.1** Guestway shall ensure that persons authorised to Process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality, and that access is limited to those persons who need it to provide the Services.

**6.2** Guestway shall ensure that such persons receive appropriate training on their responsibilities and are subject to the access controls described in Annex 2.

## Security of processing

**7.1** Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of Processing as well as the risk to the rights and freedoms of natural persons, Guestway shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, as required by Article 32 GDPR.

**7.2** The measures in force at the Effective Date are set out in Annex 2. Guestway may update those measures from time to time provided that the level of security is not materially reduced.

**7.3** Guestway shall not use Personal Data Processed on behalf of the Customer to train machine learning or artificial intelligence models, and shall procure that its Sub-processors do not do so, save where the Customer has expressly enabled a feature that uses the Customer's own Personal Data to improve that Customer's own use of the Services, as described in Annex 1, section 6.

## Sub-processors

**8.1** The Customer grants Guestway a general authorisation to engage Sub-processors, subject to this clause.

**8.2** The Sub-processors engaged at the Effective Date are listed in Annex 3. Guestway maintains the current list and provides it to the Customer; changes are notified in accordance with clause 8.3.

**8.3** Guestway shall inform the Customer of any intended addition or replacement of a Sub-processor at least thirty (30) days in advance, by email to the contact designated by the Customer and by updating the list referred to in clause 8.2. The Customer may object on reasonable data protection grounds within thirty (30) days of being informed. The Parties shall discuss the objection in good faith. If no solution is found, the Customer may terminate the affected part of the Services without penalty, and shall receive a pro rata refund of prepaid fees for the terminated part.

**8.4** Guestway shall impose on each Sub-processor, by written contract, data protection obligations that are no less protective than those set out in this DPA, and shall remain fully liable to the Customer for the performance of each Sub-processor's obligations.

**8.5** Guestway shall make available to the Customer, on request, the relevant provisions of its agreements with Sub-processors, which may be redacted to protect commercially confidential information.

## International transfers

**9.1** Guestway Processes and stores Personal Data within the European Economic Area, on infrastructure located in Ireland, save as set out in Annex 3.

**9.2** Where Personal Data is transferred to a Sub-processor established outside the EEA, or is accessible from outside the EEA, such transfer takes place on the basis of an adequacy decision under Article 45 GDPR or of appropriate safeguards under Article 46 GDPR, in practice the Standard Contractual Clauses. The applicable transfer mechanism per Sub-processor is stated in Annex 3.

**9.3** Where the Standard Contractual Clauses apply, Module Three (processor to processor) applies between Guestway and the relevant Sub-processor, and Module Two (controller to processor) applies between the Customer and Guestway where the Customer is established outside the EEA. In case of conflict, the Standard Contractual Clauses prevail over this DPA.

**9.4** Guestway shall carry out and document, and make available to the Customer on request, an assessment of the transfer in accordance with applicable guidance where required.

## Assistance to the Customer

**10.1 Data subject rights.** Taking into account the nature of the Processing, Guestway shall assist the Customer by appropriate technical and organisational measures, insofar as this is possible, in fulfilling the Customer's obligation to respond to requests for exercising Data Subject rights under Chapter III GDPR. The Services provide functionality allowing the Customer to access, correct, export and delete Personal Data itself. Where a Data Subject contacts Guestway directly, Guestway shall not respond substantively but shall refer the Data Subject to the Customer and inform the Customer without undue delay.

**10.2 Security, breach notification and impact assessments.** Guestway shall assist the Customer in ensuring compliance with the obligations under Articles 32 to 36 GDPR, taking into account the nature of the Processing and the information available to Guestway. This includes providing the information reasonably required for a data protection impact assessment and, where applicable, for prior consultation with a Supervisory Authority.

**10.3** Guestway may charge a reasonable fee for assistance that goes materially beyond what is required by the GDPR or that results from the Customer's own configuration choices, provided that Guestway informs the Customer in advance.

## Personal data breaches

**11.1** Guestway shall notify the Customer without undue delay, and in any event within forty-eight (48) hours, after becoming aware of a Personal Data Breach affecting Personal Data Processed on behalf of the Customer.

**11.2** The notification shall describe, to the extent known at the time and supplemented as further information becomes available: the nature of the breach including where possible the categories and approximate number of Data Subjects and records concerned, the likely consequences, the measures taken or proposed to address the breach and mitigate its effects, and the contact point for further information.

**11.3** Guestway shall document each Personal Data Breach and shall provide the Customer with reasonable assistance in relation to any notification to a Supervisory Authority or communication to Data Subjects. Guestway shall not notify any Supervisory Authority or Data Subject on the Customer's behalf unless required by law or instructed by the Customer.

## Retention, return and deletion

**12.1** Guestway retains Personal Data for the duration of the Agreement, in accordance with the retention periods set out in Annex 1, section 7.

**12.2** Upon termination or expiry of the Agreement, Guestway shall, at the Customer's choice, delete or return all Personal Data. The Customer may export its data through the Services before termination and for thirty (30) days thereafter.

**12.3** Personal Data in active production systems, including file storage, shall be deleted within seven (7) days of termination or of the expiry of the export period referred to in clause 12.2, whichever is later. Personal Data contained in backups, logs and error monitoring systems is deleted in accordance with the ordinary rotation cycle of those systems and within the periods set out in Annex 1, section 7. Until deletion, such data remains subject to the security measures set out in Annex 2 and is not Processed for any other purpose.

**12.4** Clause 12.2 does not apply to the extent that Union or Member State law requires storage of the Personal Data. In that case Guestway shall inform the Customer of the requirement.

**12.5** Guestway shall confirm deletion in writing on request.

**12.6** Clause 12.3 and the post-termination deletion periods set out in Annex 1, section 7 apply with effect from 1 November 2026. Until that date, Personal Data is deleted within ninety (90) days of termination in accordance with Guestway's current retention procedure. All other provisions of this DPA apply from the Effective Date.

## Audits and information

**13.1** Guestway shall make available to the Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 GDPR.

**13.2** Guestway shall in the first instance satisfy requests for information by providing its then current security documentation, the measures set out in Annex 2, responses to a reasonable security questionnaire, and any third party certifications or audit reports it holds.

**13.3** Where the information referred to in clause 13.2 is not sufficient, Guestway shall allow for and contribute to audits, including inspections, conducted by the Customer or another auditor mandated by the Customer, subject to the following: audits take place no more than once in any twelve month period, on at least thirty (30) days' written notice, during normal business hours, without unreasonable disruption to Guestway's operations, and subject to confidentiality undertakings. The auditor shall not be a competitor of Guestway.

**13.4** The limits in clause 13.3 do not apply where an audit is required by a Supervisory Authority, or following a Personal Data Breach affecting the Customer's Personal Data.

**13.5** Each Party bears its own costs of an audit, save that the Customer shall reimburse Guestway's reasonable costs where an audit exceeds one working day or where it is repeated within a twelve month period at the Customer's request.

## Liability

**14.1** Guestway's obligations under this DPA are obligations of means. Guestway is liable only for damage that is the direct and immediate consequence of a proven contractual fault in the performance of this DPA, and solely in the event of fraud, wilful misconduct or gross negligence on its part.

**14.2** Guestway's liability is at all times limited to compensation for direct damage. Indirect damage, consequential damage, loss of profit, loss of turnover, loss of data, reputational damage or any other form of non-direct damage is excluded, irrespective of the manner in which the claim is brought.

**14.3** Guestway's total, aggregate liability under this DPA shall never exceed the equivalent of six (6) months of the fees paid by the Customer for the Services to which the damage relates, or EUR 50,000, whichever amount is the lower.

**14.4** Guestway is in no way liable for damage arising from instructions, decisions or acts of the Customer, nor for any negligence, fault or infringement by the Customer, its employees, its appointees or any third party engaged by it, nor for shortcomings in systems, security or processes falling under the Customer's responsibility.

**14.5** Where both the Customer and Guestway are held liable for damage under applicable data protection law, Guestway is liable only for that part of the damage which results directly from its own processing activities and from a breach of this DPA attributable to it.

**14.6** If Guestway is held liable by a Data Subject, a Supervisory Authority or any third party pursuant to Article 82 GDPR or any other statutory provision, the Customer shall indemnify and hold Guestway harmless against all damage, costs and expenses (including reasonable legal fees), save where and to the extent that such damage is the direct result of a proven fault of Guestway as defined in this DPA.

**14.7** The Customer shall take all reasonable measures to mitigate its damage.

**14.8** The Customer acknowledges that, within the limits permitted by law, the compensation of damage caused by the non-performance of a contractual obligation is governed exclusively by the law of contract, even where the event giving rise to the damage also constitutes an extra-contractual fault.

**14.9** The Customer further acknowledges that, within the limits permitted by law, the non-performance of a contractual obligation by an auxiliary person gives rise only to a claim against the principal debtor and not to an extra-contractual claim against that auxiliary person, even where the event giving rise to the damage also constitutes an extra-contractual fault.

## Miscellaneous

**15.1** This DPA may be amended in writing signed by both Parties. Guestway may update the Annexes to reflect changes in the Services, its Sub-processors or its security measures, provided that the level of protection is not materially reduced and that the Customer is informed in accordance with clause 8.3 where a Sub-processor is concerned.

**15.2** Guestway may publish new versions of this DPA for agreements concluded after the date of publication. A new version does not apply to an existing Agreement unless the Parties agree to it. Guestway maintains previous versions and provides them on request.

**15.3** If any provision of this DPA is held invalid or unenforceable, the remaining provisions remain in full force and the Parties shall replace the invalid provision with a valid one reflecting its purpose as closely as possible.

**15.4** This DPA is governed by the laws of Belgium. The courts of Ghent, Belgium have exclusive jurisdiction, without prejudice to any mandatory jurisdiction under the GDPR.

**15.5** Privacy related enquiries under this DPA may be directed to <gdpr.support@guestway.io>.

## Signatures

This DPA is executed as part of the Agreement, or by separate signature. Where signed separately, the Effective Date is the date of the last signature.

**Guestway BV**

**\[Client Name]**

## Annex 1: Details of the processing

### Subject matter and nature of the processing

Provision of the Guestway property management and guest experience platform, including guest communication, booking data management, online check-in, and, where enabled by the Customer, identity verification and damage waiver services.

### Purpose of the processing

Processing is carried out solely to provide the Services to the Customer in accordance with the Agreement and the Customer's documented instructions.

### Duration

For the duration of the Agreement, plus the retention periods set out in section 7 below.

### Categories of data subjects

* Guests and prospective guests of the Customer
* Additional occupants named in a booking
* Employees, contractors and other authorised users of the Customer
* Any other individuals whose Personal Data the Customer submits to the Services

### Ordinary categories of personal data

| Category                     | Data                                                                                                                            |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Identification data**      | Name, date of birth, nationality                                                                                                |
| **Contact data**             | Email address, telephone number, postal address                                                                                 |
| **Booking data**             | Reservation details, dates of stay, property and unit, rate, number of guests                                                   |
| **Communication data**       | Messages exchanged between the Customer and the guest, attachments sent in those messages, and associated metadata              |
| **Check-in data**            | Data submitted through the online check-in flow, including arrival details and any additional fields configured by the Customer |
| **Payment related data**     | Payment status and transaction references. Card data is Processed by the payment provider and is not stored by Guestway         |
| **Usage and technical data** | IP address, device and browser information, log data relating to use of the guest facing interfaces                             |

### Special categories, identity verification (only where enabled by the customer)

Where the Customer enables identity verification, the following may be Processed by Guestway's Sub-processor Didit:

| Category                                       | Data                                                                                                                                                                                 |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Identity document images and capture video** | Depending on the workflow configuration                                                                                                                                              |
| **Data extracted from the identity document**  | Name, date of birth, document number, nationality, expiry date                                                                                                                       |
| **Selfie and liveness media**                  | Used for the comparison against the document image                                                                                                                                   |
| **Facial comparison result**                   | A mathematical vector is generated for comparison purposes. This constitutes biometric data under Article 9 GDPR. The vector cannot be reconstructed into an image of the individual |
| **Fraud and risk signals**                     | Including device and network data where that module is enabled                                                                                                                       |

**Customer controls and deletion.** The categories collected and returned are determined by the configuration of the verification workflow. Verification data, including identity document images and biometric data, is retained at the Sub-processor for no longer than the configured retention window of thirty (30) days and is then automatically and permanently erased, including the biometric template, which is deleted together with the session. The applicable retention periods are stated in section 7.

### Data not requested

The Services are not intended for the Processing of Special Categories of Personal Data other than as described in section 5.2. The Customer shall not submit health data, data revealing racial or ethnic origin, political opinions, religious beliefs, trade union membership, sex life or sexual orientation, or data relating to criminal convictions, through free text fields or attachments.

### Artificial intelligence features

**6.1** Guestway does not train artificial intelligence models on Customer Personal Data. Guestway's AI features are built through prompt and agent engineering using third party models, under terms which exclude the use of input data for the training of those models.

**6.2** Where the Customer enables AI suggested replies or Autopilot, the Customer's own guest conversations may be used to improve the quality of suggestions for that Customer only. Such data remains within the Customer's own environment, is not used to improve suggestions for any other customer, and is not used to train any underlying model. This feature is opt in and can be disabled at any time.

**6.3** In respect of identity verification, the use of verification data for model and product improvement by the Sub-processor is disabled at account level for the Guestway account, with effect from 31 July 2026. The Sub-processor has confirmed in writing that data processed before that date has been excluded.

### Retention periods

| Data                                                                       | Retention                                                                                                                                                                 | After termination                                                       |
| -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| **Guest profile data**                                                     | For the duration of the Agreement.                                                                                                                                        | Deleted within 7 days.                                                  |
| **Booking data**                                                           | For the duration of the Agreement.                                                                                                                                        | Deleted within 7 days.                                                  |
| **Communication data and attachments**                                     | For the duration of the Agreement.                                                                                                                                        | Deleted within 7 days.                                                  |
| **Check-in data**                                                          | For the duration of the Agreement.                                                                                                                                        | Deleted within 7 days.                                                  |
| **Verification results**                                                   | For the duration of the Agreement.                                                                                                                                        | Deleted within 7 days.                                                  |
| **Identity documents and biometric data**                                  | Automatically and permanently erased at the Sub-processor no later than 30 days after the verification (the shortest retention window configurable at the Sub-processor). | Not applicable, deleted at source.                                      |
| **Backups**                                                                | Database backups follow a rotation cycle of 21 days. Infrastructure snapshots are retained for 4 weeks.                                                                   | Fully deleted no later than 28 days after deletion from active systems. |
| **Application, infrastructure and security logs containing Personal Data** | Up to 90 days depending on the log type.                                                                                                                                  | Expire through the ordinary rotation cycle, no later than 90 days.      |
| **Error monitoring data**                                                  | 90 days.                                                                                                                                                                  | Expires through the ordinary rotation cycle, no later than 90 days.     |
| **AI processing logs**                                                     | 90 days maximum.                                                                                                                                                          | Expire through the ordinary rotation cycle.                             |

## Annex 2: Technical and organisational measures

### Organisation of information security

* A set of adopted information security policies covering access control, asset management, cryptography, operations security, data management, secure development, human resource security, physical security, risk management, third party management, incident response, GDPR compliance and business continuity.
* Policies are reviewed at least annually and communicated to personnel.
* Compliance is monitored through a compliance management platform.

### Access control and authentication

* Access is granted on the principle of least privilege. Permissions not expressly granted are prohibited by default.
* Role based access control is the primary method of assigning access rights.
* Multi-factor authentication is required for all privileged access to production infrastructure.
* Unique user identifiers per person. Credentials are not shared. Administrative accounts are separated from ordinary accounts where feasible. User identifiers are not reused.
* Access provisioning requires documented approval and is not granted before onboarding is complete, including a signed employment agreement, an intellectual property agreement and acknowledgement of the information security policy.
* Records of permission and privilege changes are retained for at least one year.
* Access rights of user, administrator and service accounts are reviewed quarterly, and additionally on any job role change.
* Access is revoked on termination within a maximum of 24 business hours.
* Remote connections to production systems are encrypted.
* Vendor default credentials are changed before deployment and unnecessary default accounts are removed.
* Password requirements: minimum eight characters including upper case and a number, reuse of the last eight passwords prohibited, lockout after six failed attempts, unique initial passwords changed at first login, identity verification before manual resets, and storage in hashed and salted form.

### Encryption

* Encryption is performed in accordance with industry standards including NIST SP 800-57.
* Personal Data is encrypted at rest using AES-256.
* Personal Data is encrypted in transit using TLS 1.3.
* Passwords are stored using a one way hash with a unique salt.
* Laptops and mobile devices containing confidential data use full disk encryption.
* Backups are encrypted.
* Encryption keys are managed centrally and rotated on demand.

### Network and infrastructure security

* Production infrastructure is hosted on Amazon Web Services in the Ireland region (eu-west-1), across multiple availability zones.
* Firewalls and network access controls govern traffic to and from the production environment. Network access configuration rules are reviewed at least annually.
* Development and staging environments are strictly segregated from production. Confidential production customer data is not used in development or test environments without documented approval, and is scrubbed of sensitive information where feasible.
* Anti-malware and threat detection software is deployed on company issued endpoints and company email.
* An annual network security assessment is performed, including a review of major changes to the environment.

### Logging and monitoring

* Logging of user log-in and log-out, create, read, update and delete operations on users and objects, changes to security settings including changes to logging itself, and administrator access to customer data.
* Logs include user identifier, IP address, timestamp, type of action and object of the action, and do not contain sensitive payloads.
* Log retention is bounded per log type, with a maximum of 90 days for application and infrastructure logs containing Personal Data and 90 days for error monitoring data. The cloud provider audit trail, which records administrative activity by Guestway personnel and contains no Customer Personal Data, is retained for 365 days for security monitoring and incident investigation.
* Logging facilities are protected against tampering and unauthorised access.
* Alerts are configured for events representing a significant threat to the confidentiality, availability or integrity of production systems or confidential data.
* Restoration of production data containing personal data from backup is logged in auditable tickets.

### Secure development

* Production, staging and development environments are logically or physically segregated.
* Change control ensures that development, testing and deployment of changes are not performed by a single individual without approval and oversight.
* Code is not deployed to production without documented successful test results and evidence of security remediation.
* Significant code changes are reviewed and approved before merging to a production branch.
* Dependencies are scanned for known vulnerabilities during the build process.
* All software is version controlled and repository access is restricted by role.
* Customer data is not used for testing without explicit permission.
* Personnel involved in development receive secure development training at least annually.

### Vulnerability and patch management

* Application code and dependencies are tested for vulnerabilities as part of the development and build process.
* Vulnerability scans of public facing production systems are performed at least quarterly.
* Remediation targets: critical and high within 30 days, medium within 60 days, low within 90 days. Vulnerabilities that cannot be remediated within the standard timeline require a documented risk treatment plan.
* An independent penetration test of the platform is performed at least annually, and findings are remediated within the timeframes set out above.

### Backup and resilience

* Database backups run continuously (incremental) with full snapshots daily, are encrypted, and follow a rotation cycle of 21 days. Infrastructure snapshots are taken weekly and retained for 4 weeks. Ad hoc snapshots are subject to a mandatory expiry.
* Backups are stored separately from the production data location, within the EU.
* Backup and restore capability is tested at least annually.
* A disaster recovery test including restoration from backup is performed annually.
* Recovery objectives are defined per asset in the business continuity and disaster recovery plan.

### Personnel measures

* Background verification checks are carried out in accordance with applicable law and proportionate to the role and the classification of information accessed, including criminal history checks where permitted.
* All personnel and third parties with access to company or customer information sign confidentiality and non-disclosure agreements and a code of conduct.
* Security awareness training at the time of hire and annually thereafter, with completion monitored.
* On termination, physical and logical access is revoked and company issued equipment is returned.
* Disciplinary process up to and including termination applies to policy violations.

### Physical security

* Production infrastructure is hosted in data centres operated by Amazon Web Services. Physical security of those facilities is provided by the hosting provider under its certifications, including ISO/IEC 27001 and SOC 2. Guestway personnel have no physical access to that infrastructure.
* Guestway's own offices apply entry controls to secure areas, visitor sign in and escorting of third parties, and screen locking on devices after five minutes of inactivity.

### Incident response

* A documented incident response plan with a severity classification, defined response lifecycle covering triage, investigation, containment, recovery and remediation, and a documented root cause analysis for every incident.
* Personal Data Breaches are notified to affected customers without undue delay and in any event within the period stated in clause 11.1 of the DPA.
* Guestway cooperates with customers, controllers and supervisory authorities in the event of an incident.
* The incident response plan is reviewed at least annually.

### Supplier management

* Due diligence is performed before a service provider is given access to confidential data, systems or networks.
* Confidential data is not shared with a third party without a completed risk assessment and a fully executed written agreement setting out information security requirements.
* Supplier security and service delivery performance is reviewed at least annually.
* Records are maintained of the certifications held by each provider.

### Data minimisation and separation

* Customer environments are logically separated so that each customer can access only its own data.
* Personal Data is collected and retained only for as long as there is a legitimate business purpose, in accordance with the retention periods in Annex 1.

## Annex 3: Sub-processors

### Infrastructure and core processing

| Sub-processor                     | Role                                                 | Location                                       | Transfer basis                                                                                                   |
| --------------------------------- | ---------------------------------------------------- | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Amazon Web Services EMEA SARL** | Hosting of the platform and storage of customer data | Luxembourg, data hosted in Ireland (eu-west-1) | Processing within the EEA. SCCs in place under the AWS GDPR addendum for any support access from outside the EEA |

### Identity verification

| Sub-processor                  | Role                                                           | Location                             | Transfer basis            |
| ------------------------------ | -------------------------------------------------------------- | ------------------------------------ | ------------------------- |
| **Didit Identity Spain, S.L.** | Identity document verification, liveness and facial comparison | Spain, data hosted on AWS in Ireland | Processing within the EEA |

**Data minimisation:** Guestway transmits no name, email address or telephone number to Didit. The Data Subject uploads the identity document and selfie directly to Didit, and Guestway provides only a workflow identifier and internal reference identifiers. Use of verification data for model or product improvement by Didit is disabled at account level (see Annex 1, section 6.3).

Didit's own sub-processors: Amazon Web Services EMEA SARL (Luxembourg, hosting in Ireland) and Google Maps Platform, the latter used solely for geocoding of an address string within the Proof of Address feature and receiving no document images, biometric data or verification results. Where the Customer's workflow does not include Proof of Address, Google Maps Platform is not involved.

### Communication and messaging

| Sub-processor                          | Role                                   | Location           | Transfer basis |
| -------------------------------------- | -------------------------------------- | ------------------ | -------------- |
| **Twilio SendGrid**                    | Transactional and guest email delivery | United States      | SCCs           |
| **Meta Platforms (WhatsApp Business)** | WhatsApp messaging with guests         | United States / EU | SCCs           |

SMS delivery via Sinch MessageMedia or Twilio uses the Customer's own account with that provider, connected with the Customer's own credentials. These providers are engaged by the Customer and are not Guestway Sub-processors. For Sinch MessageMedia an EU-hosted variant is available.

### Integrations operated at the customer's instruction

Where the Customer connects its own property management system, smart lock or other third party service to Guestway, Guestway transmits Personal Data to that service at the Customer's instruction. These parties are engaged by the Customer and are not Guestway Sub-processors.

**Property management and booking platforms:** Airbnb, Apaleo, Guesty, Hostaway, Hostfully, Mews, Smoobu

**Smart locks, access and building systems** (receive guest name and access window, no communication content): Brivo, Honeywell, Keynest, Nest, Nuki, ProDataKey, Salto, Seam (including Yale), Zennio

### Artificial intelligence providers

| Sub-processor                             | Role                                                                                              | Location                            | Transfer basis                                                                                                                               |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------- | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **OpenAI**                                | Generation of AI suggested replies and agent features                                             | United States                       | SCCs. Training on customer data excluded under the API terms                                                                                 |
| **Anthropic**                             | Generation of AI suggested replies and agent features                                             | United States                       | SCCs. Training on customer data excluded under the API terms                                                                                 |
| **Google (Gemini API, Google Translate)** | Message translation and AI features                                                               | United States, EU regions available | SCCs. Gemini is used under the paid API tier (pay per request), under which Google does not use input or output data to improve its products |
| **Google Firebase**                       | Staff authentication and push notifications. Notification payloads can contain guest message text | United States, EU regions available | SCCs                                                                                                                                         |

### Payments

| Sub-processor | Role               | Location                  | Transfer basis                                                          |
| ------------- | ------------------ | ------------------------- | ----------------------------------------------------------------------- |
| **Stripe**    | Payment processing | Ireland and United States | SCCs. Stripe acts as an independent controller for certain payment data |

### Independent controllers connected to the services

The following party is not a Sub-processor but an independent controller. It is listed here for transparency.

| Party                      | Role                                                                                                                                                                | Location                                                                                                                                                                                                                       | Notes                                                                                                                                                         |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Truvi Technologies Ltd** | Guest screening and damage waiver (Screen & Protect). Truvi determines the means and criteria of the screening and acts as independent controller for the screening | United Kingdom (3rd Floor, 1 Ashley Road, Altrincham, Cheshire, WA14 2DT). Processing in the UK and EEA via Microsoft Azure and SEON; storage in the USA can occur where the property is US based, with appropriate safeguards | UK benefits from an EU adequacy decision. Truvi's Screen & Protect Data Processing & Handling Agreement applies, published at [truvi.com](https://truvi.com/) |

### Operational and support tooling

| Sub-processor  | Role                                                                                                                                          | Location                                  | Transfer basis |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | -------------- |
| **Cloudflare** | Content delivery, DNS, protection against attacks, and gateway logging of AI requests including message content                               | United States, with EU processing options | SCCs           |
| **Sentry**     | Application error monitoring. No user identity is attached to events; payload fragments can occur in exception messages                       | United States (US region)                 | SCCs           |
| **Pylon**      | Customer support ticketing. Guest data appears incidentally, for example in screenshots shared during support conversations, not structurally | United States                             | SCCs           |

### Tooling without access to guest personal data

The following are used by Guestway and are not expected to Process guest Personal Data.

Cursor, GitHub, Hetzner.

### Guestway BV

Soenenspark 1, 9051 Ghent, Belgium

KBO/BCE 0798.195.974 · VAT BE 0798.195.974

GDPR contact: <gdpr.support@guestway.io>

## Related

* [Organization details](https://docs.guestway.io/account-and-administration/organization-details.md)
* [How to set up ID verification](https://docs.guestway.io/guest-experience/guest-journey/how-to-set-up-id-verification.md)
* [About how the AI answers guests](https://docs.guestway.io/ai/ai-center/about-how-the-ai-answers-guests.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guestway.io/privacy-and-security/data-processing-agreement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
