How we handle keys, guest data and incident disclosures.
A short, specific statement rather than a legalese brochure. If you want the long contract version, email [email protected] and we send a signed data processing agreement under the UK GDPR.
Credentials
Every module activates against a scoped API credential you mint inside your own PMS vendor's console — a read + write key narrowed to the endpoints the module uses. We never ask for your PMS login, we never shadow-login, and we never share one credential across customers.
Credentials live in encrypted storage on our side (AWS-managed KMS keys, UK region) and are redacted from logs. They are decrypted only in the brief window a worker needs to call your PMS API. On cancellation the credential is deleted within 30 days along with the module-side data; we e-mail a delete-confirmation when the sweep completes.
Guest data
Where a module handles guest records — SMS and email journeys, e-signed registration, parity screenshots — Clydebridge Software Ltd acts strictly as processor under a written data processing agreement signed before any guest data is sent. Our own controller-side handling of your (operator) records is described in the privacy notice under the UK GDPR, the UK GDPR and the Data Protection Act 2018, ICO registration ZA917604.
We do not sell data, we do not run advertising-side pixels on the client console and we do not use guest records for anything beyond fulfilling the module's documented function.
Breach reporting
If we identify unauthorised access to any system that holds your credentials or guest records, we notify you within 24 hours of becoming aware, with the scope we have at that point. We update at the 72-hour mark with a confirmed scope and the remediation already applied. Where guest records are involved and the risk threshold is met, we support your notification to the ICO and to data subjects under Article 33/34 UK GDPR.
Research disclosures
Good-faith security research is welcome. Report issues to [email protected]; acknowledgement within one business day. Research against your own account is always welcome; against shared infrastructure requires prior written permission from us. Findings are credited anonymously unless you ask otherwise.
Vendor conflicts
When something breaks at the interface between our module and your PMS vendor, each side can be tempted to point at the other. We agree a written triage order with every new operator at onboarding: who holds the ticket first, when it escalates, and who signs off on the fix. In practice our engineers reach out to the PMS vendor directly on your behalf rather than ask you to broker it.