Data Processing Agreement
The terms that apply when felloh processes personal data on behalf of its customers.
Data Processing Agreement
Last updated: 18 November 2026.
This Data Processing Agreement (the “DPA”) is between Felloh Ltd, company number 12601874, registered office The Old Rectory, Main Road, Belton, Grantham, NG32 2LW (“Felloh”), and the customer that has entered into an agreement with Felloh for its payment, booking-finance and reporting platform (the “Customer”).
It forms part of that agreement (the “Agreement”) and applies whenever Felloh processes personal data on the Customer’s behalf. If the Customer and Felloh have signed a separate data processing agreement, the signed agreement applies instead of this one. Otherwise, if this DPA and the Agreement conflict on the processing of personal data, this DPA takes priority.
1. Definitions
1.1 Data Protection Laws means the UK GDPR, the Data Protection Act 2018, the Privacy and Electronic Communications Regulations 2003 and any other applicable UK data protection law, as amended or replaced from time to time.
1.2 Controller, Processor, Data Subject, Personal Data, Personal Data Breach, Processing and Supervisory Authority have the meanings given in the Data Protection Laws.
1.3 Customer Personal Data means Personal Data that Felloh processes on the Customer’s behalf to provide the Services, as described in Annex 1.
1.4 Services means the services Felloh provides to the Customer under the Agreement.
1.5 Sub-processor means any third party Felloh engages to process Customer Personal Data.
1.6 Restricted Transfer means a transfer of Customer Personal Data outside the UK that would be prohibited without appropriate safeguards under the Data Protection Laws.
1.7 IDTA means the International Data Transfer Agreement, and UK Addendum means the International Data Transfer Addendum to the EU Standard Contractual Clauses, each as issued by the Information Commissioner under section 119A of the Data Protection Act 2018.
2. Roles and scope
2.1 For Customer Personal Data, the Customer is the Controller and Felloh is the Processor.
2.2 Felloh acts as an independent Controller, under its Privacy Policy, for Personal Data it processes for its own purposes. These are: (a) setting up and administering the Customer’s account and its users; (b) fraud prevention, anti-money-laundering, sanctions and know-your-customer checks; (c) billing; (d) meeting its own legal, regulatory and card scheme obligations; and (e) creating anonymised, aggregated data where the Agreement allows it.
2.3 Acquiring banks and payment providers that the Customer contracts with directly process transaction data as independent Controllers under their own agreements with the Customer. They are not Sub-processors of Felloh.
2.4 The Customer confirms that it has a lawful basis for the processing, and has given Data Subjects all required notices, for Felloh to process Customer Personal Data under this DPA.
3. Felloh’s obligations
3.1 Felloh will:
- (a) process Customer Personal Data only on the Customer’s documented instructions. These instructions are set out in the Agreement, this DPA and the Customer’s configuration and use of the Services. The exception is where the law requires otherwise, in which case Felloh will tell the Customer before processing unless the law prohibits it;
- (b) tell the Customer promptly if, in its opinion, an instruction breaks the Data Protection Laws;
- (c) make sure everyone authorised to process Customer Personal Data is bound by confidentiality;
- (d) keep in place the technical and organisational measures described in Annex 2;
- (e) taking into account the nature of the processing, help the Customer meet its obligations under Articles 32 to 36 of the UK GDPR (security, breach notification, data protection impact assessments and prior consultation); and
- (f) keep records of processing as required by Article 30(2) of the UK GDPR.
4. Sub-processors
4.1 The Customer gives general authorisation for Felloh to engage Sub-processors. The current list is in Annex 3.
4.2 Felloh will give at least 30 days’ written notice, which may be by email, before adding or replacing a Sub-processor. The Customer may object on reasonable data protection grounds within that period. The parties will discuss the objection in good faith. If they cannot resolve it, the Customer may terminate the affected Services without penalty.
4.3 Felloh will put in place a written contract with each Sub-processor with data protection obligations that are no less protective than this DPA. Felloh stays liable to the Customer for each Sub-processor’s performance.
5. International transfers
5.1 Felloh will only make a Restricted Transfer, or allow a Sub-processor to make one, where one of the following applies:
- (a) UK adequacy regulations, including the UK Extension to the EU–US Data Privacy Framework for certified US recipients;
- (b) the IDTA or the UK Addendum; or
- (c) another safeguard permitted by the Data Protection Laws.
In each case Felloh will carry out a transfer risk assessment where one is required.
6. Personal Data Breaches
6.1 Felloh will notify the Customer without undue delay, and in any event within 48 hours, after becoming aware of a Personal Data Breach affecting Customer Personal Data. The notice will include the information required by Article 33(3) of the UK GDPR, as far as it is available, with the rest supplied in stages.
6.2 Felloh will take reasonable steps to contain and fix the breach and will cooperate with the Customer’s investigation. Felloh will not notify Data Subjects or the Supervisory Authority about Customer Personal Data unless the Customer instructs it to or the law requires it.
7. Data Subject requests
7.1 If Felloh receives a request from a Data Subject about Customer Personal Data, it will pass the request to the Customer within 5 business days and will not respond itself except on the Customer’s instruction. Felloh will help the Customer, by appropriate technical and organisational measures, to respond to such requests.
8. Audit
8.1 Felloh will make available the information reasonably needed to show compliance with this DPA. This includes its current PCI DSS attestation, external vulnerability scan results and relevant policies. Felloh will answer one reasonable security questionnaire a year.
8.2 The Customer may carry out an on-site or third-party audit only if the information under clause 8.1 is reasonably insufficient, after a Personal Data Breach, or where a Supervisory Authority requires it. The Customer must give at least 30 days’ notice, the audit must take place during business hours and under confidentiality, it may happen no more than once in any 12 months (except after a breach), and it is at the Customer’s cost.
9. Return and deletion
9.1 When the Agreement ends, Felloh will make Customer Personal Data available for export for the period set out in the Agreement. After that it will delete it, or return it if the Customer asks. Felloh may keep data where the law, card scheme rules or financial regulation require it, for up to 6 years for audit and compliance. Any data kept will stay protected under this DPA.
10. Liability
10.1 Each party’s liability under this DPA is subject to the limitations and exclusions in the Agreement.
11. General
11.1 This DPA lasts as long as Felloh processes Customer Personal Data. It is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.
11.2 Felloh may update this DPA from time to time. The date at the top of this page shows when it last changed. Changes to Sub-processors follow clause 4.2.
Annex 1: Details of processing
- Subject matter and purpose:
- Providing the Services: taking payments (payment links, card and open-banking payments, deposits and balances), managing booking and payment records, reconciliation, and regulatory and financial reporting (for example ATOL and ABTA).
- Duration:
- The term of the Agreement plus the return and deletion period in clause 9.
- Nature of processing:
- Collection, storage, structuring, retrieval, transmission to payment providers, reporting and deletion.
- Data Subjects:
- The Customer’s customers and travellers, including lead bookers, payers and members of group bookings; and the Customer’s staff who use the platform.
- Personal Data:
- Name, email address, phone number and postal address; booking details (references, travel dates, destinations and amounts); payment details (the cardholder name, card brand, issuing country and the first and last digits of the card number; full card numbers are held by a tokenisation provider and not by Felloh); bank account details for bank payments; and IP address and device data at the point of payment.
- Special category data:
- None intended. The Customer will not upload special category data (for example health or dietary information) or passport data unless agreed in writing.
- Children:
- Bookings may include travellers under 18. Where they do, the Customer is responsible for the appropriate consents and notices.
- Frequency:
- Continuous.
Annex 2: Technical and organisational measures
- Hosting: The platform’s applications run on Amazon Web Services in London, UK. The platform’s primary database is hosted by Neon in Frankfurt, Germany.
- Card data: Card details are entered into fields provided by Basis Theory, a PCI DSS Level 1 service provider, and tokenised. Felloh does not store full card numbers or card security codes.
- PCI DSS: Felloh is PCI DSS compliant as a service provider, validated with a Self-Assessment Questionnaire D (SAQ D). Internet-facing systems are scanned by Sectigo, a PCI Approved Scanning Vendor.
- Cyber Essentials: Felloh Ltd is certified against the UK government-backed Cyber Essentials scheme, assessed across the whole organisation.
- Encryption in transit: Felloh’s APIs and web applications require TLS 1.2 or higher. Connections to the database are encrypted.
- Access control: Each user has an individual login. Access is role-based and limited to the user’s own organisation. API credentials are stored encrypted, and webhooks are signed so that customers can verify them.
- Logging and monitoring: Application logging, error monitoring, a log of user activity in the platform, and automated checks of the cloud configuration.
- Secure development: Every release is built and tested automatically, and deployed to a staging environment and tested there before it reaches production.
- Incident response: Felloh notifies Customers of Personal Data Breaches as set out in clause 6.
Annex 3: Sub-processors
Last updated: 18 November 2026.
| Sub-processor | Purpose |
|---|---|
| Amazon Web Services EMEA SARL | Application hosting, file storage and email delivery |
| Neon, LLC | Database hosting |
| Basis Theory Inc | Card tokenisation |
| GoCardless Ltd | Open banking connections to bank accounts |
| NeutrinoAPI.com | IP address and card BIN lookups for fraud screening |
| Sentry | Error monitoring for the payment page and dashboard |
| PostHog | Product analytics for the payment page and dashboard |
| Honeycomb | Application performance monitoring |
| Google Cloud EMEA Limited | Email and AI processing |
| Help Scout | Customer support |
| Slack Technologies Limited | Internal communication and alerts |
| HubSpot | Customer relationship management |
| Hetzner | Server hosting for internal tools |
| Anthropic, PBC | AI-assisted engineering support |
| OpenAI OpCo, LLC | AI processing of supplier statements and automations |
| OpenRouter | Routing of AI requests for automations |
| AgentMail | Receiving reports and statements by email |
| Granola | Meeting notes |
| Zapier Inc. | Workflow automation |
See how this works around your bookings.
Bring one payment, reporting or cash-position problem. We will show how felloh connects the booking-level money trail behind it.
Book a walkthrough