Skip to main content

Data Processing Agreement

Last Updated: October 14, 2026

DPA Overview

This Data Processing Agreement ("DPA") forms part of the Terms of Service between Attention Keeper LLC and each customer. It applies whenever we process personal data on a customer's behalf through our platform, its client and supplier portals or Done-For-You Services. It sets out our commitments under the GDPR, the UK GDPR, Swiss data protection law and US state privacy laws, explains how the shared login works and how customers' data is kept apart, lists our sub-processors, and incorporates the Standard Contractual Clauses for international transfers.

1. Definitions

For the purposes of this DPA, the following terms shall have the meanings set out below:

  • "Controller" refers to you, the customer (the travel advisor or agency that owns a workspace), who determines the purposes and means of the processing of personal data through your use of the Service.
  • "Processor" refers to Attention Keeper LLC, which processes personal data on behalf of the Controller.
  • "Personal Data" means any information relating to an identified or identifiable natural person that the Processor processes on behalf of the Controller through the Service, including information about the Controller's staff, clients, travellers, leads, suppliers and their contacts.
  • "Sub-Processor" means any third party appointed by the Processor to process Personal Data on behalf of the Controller.
  • "Data Subject" means the identified or identifiable natural person to whom the Personal Data relates.
  • "Processing" means any operation performed on Personal Data, including collection, storage, use, disclosure, or deletion.
  • "Data Protection Laws" means all laws that apply to the processing of Personal Data under this DPA, including the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection and the California Consumer Privacy Act.
  • "Standard Contractual Clauses" means the standard contractual clauses approved by European Commission Implementing Decision (EU) 2021/914.
  • "Platform Account Data" means the data the Processor needs to run user logins across the Service: login email, password hash, two-step sign-in settings, sessions, sign-in and security logs, and the list of workspaces a login is linked to with the consent record for each link. Platform Account Data is not Personal Data under this DPA; the Processor is its independent controller, subject to section 3.

2. Scope & Purpose

This DPA applies to all Personal Data that the Processor processes on behalf of the Controller in connection with the provision of the Attention Keeper platform and services.

The nature and purpose of processing is to provide the Service and any Done-For-You Services as directed by the Controller, including storing client, traveller and supplier records, trips, itineraries, bookings (including flight bookings through Duffel), quotes, contracts and e-signatures, invoices and client payments and supplier payment requests and payouts (through the Controller's own payment accounts), availability, rates and inventory, documents and communications; running the client and supplier portals; sending and receiving emails, text messages, WhatsApp and social media messages; making, recording and transcribing calls; and generating AI-assisted content with identity data removed before sending. The duration of processing is the term of the Controller's subscription or Services engagement plus the deletion periods in section 11.

Categories of data subjects include: the Controller's clients and their travel companions, including children; leads and enquirers; suppliers and their contact people; people who message the Controller through connected channels; and the Controller's employees and travel advisors. Categories of personal data include: names, email addresses, phone numbers, physical addresses, emergency contacts, passport, visa, national ID and driver's licence details and images, dates of birth, nationality, travel preferences, itineraries, flight numbers, booking references and tickets, payment amounts, status and references (never full card numbers), supplier legal names, tax IDs, rates and inventory, payout account references, messages, call recordings and transcripts, documents and photos, signature evidence, marketing consents, activity and audit logs, payroll, bank and tax identification details of staff, and other data entered by the Controller.

Sensitive data: the Controller may choose to store health-related information, such as dietary, medical, mobility or accessibility needs, and information about children. The Controller is responsible for having a lawful basis for this, including explicit or parental consent where the law requires it. The Processor restricts access to this information to personnel who need it.

3. Roles, Platform Account Data & Shared Logins

For Personal Data, the Controller is the controller (and the business under the CCPA) and the Processor is the processor (and the service provider). For Platform Account Data, and for the data the Processor needs to bill and support the Controller as its customer, the Processor is an independent controller, subject to the limits in this section.

A person (a client or a supplier) who works with more than one customer on the Service may, by their own choice, use one login for several customers. When accepting an invite from a further customer, the person is asked to add that customer to their existing login or to create a separate login. A link exists only if the person chooses it, and each link is recorded as an auditable consent event (who, when, which customer).

Personal Data of one customer is kept logically separate from that of every other customer, and every request is scoped to one workspace. The Processor will not disclose to the Controller that a person it invites already has a login or works with another customer (an invite to an already registered email gives the Controller the same result as any other invite); will not make any Personal Data, documents, messages, payment methods or payout accounts of one customer available to another; and will not combine Personal Data received from the Controller with personal data received from another customer or collected in its own interactions with the person, except to the extent the shared login itself requires it for the permitted purposes below.

The Processor uses Platform Account Data, including the existence of a link between one login and several customers, only to authenticate the person and let them switch between the customers they linked; to keep the Service and accounts secure and to detect, prevent and investigate security incidents, fraud and abuse; to comply with the law and respond to rights requests about the login; and to keep the record of the person's linking choices. The Processor will never use the cross-customer link for marketing, advertising, analytics, profiling, ranking or building a profile of the person, and will never sell or share it.

The person can remove any customer from their login at any time; this affects no other customer. The Controller can end a person's access to its own workspace at any time; this affects no other customer. When a link to the Controller is removed, the Processor keeps only what it needs for the purposes above, such as the consent record, and erases the login entirely when it no longer serves any customer and the person's account is deleted.

4. Processor Obligations

Attention Keeper as Processor shall:

  • Process Personal Data only on documented instructions from the Controller, unless required by applicable law
  • Ensure that persons authorized to process Personal Data have committed to confidentiality
  • Implement appropriate technical and organizational security measures as described in this DPA
  • Respect the conditions for engaging Sub-Processors as outlined in this DPA
  • Assist the Controller in responding to requests from Data Subjects exercising their rights
  • Assist the Controller in ensuring compliance with security, breach notification, and data protection impact assessment obligations
  • At the Controller's choice, delete or return all Personal Data after the end of the provision of services, and delete existing copies unless required by law to retain them
  • Make available to the Controller all information necessary to demonstrate compliance with these obligations
  • Inform the Controller if, in its opinion, an instruction infringes Data Protection Laws

5. Controller Obligations

The Controller shall:

  • Ensure that the processing of Personal Data through the Service has a lawful basis under applicable data protection laws
  • Provide all necessary notices and obtain all necessary consents from Data Subjects for the processing of their Personal Data
  • Ensure that documented instructions to the Processor comply with applicable data protection laws
  • Be responsible for the accuracy, quality, and legality of Personal Data provided to the Processor
  • Obtain any consent the law requires before recording or transcribing calls and before sending text messages, WhatsApp messages or other communications through the Service
  • Configure automated features, such as automatic sending, in line with Data Protection Laws
  • Give its clients and suppliers its own privacy notice, including on any branded portal domain, and ensure that children's data and health-related data (medical, dietary and accessibility notes) are stored with the lawful basis the law requires

6. Sub-Processors

The Controller authorizes the Processor to engage Sub-Processors to assist in providing the Service. Sensitive identity, travel and payment fields reach them only in encrypted form, unless a Sub-Processor's function requires the readable data. Current Sub-Processors are:

  • Convex, Inc. (database, server functions, scheduled jobs and file storage for the whole platform), United States
  • BunnyWay d.o.o. (Bunny.net: storage and delivery of uploaded files, images and video, DNS, and serving customer and portal domains; passport, ID, ticket and boarding-pass files are encrypted before upload), Slovenia
  • Resend (Plus Five Five, Inc.) (sending system, account and customer emails, sending domains and inbound mail for the mailbox feature), United States
  • Zernio Software SL (social media publishing and inbox, text messages, WhatsApp, phone numbers and calls, call recording and transcription where the Controller turns it on, Google Business Profile), Spain
  • Duffel Technology Ltd (flight search and booking through Attention Keeper's Duffel account, when the Controller books flights), United Kingdom
  • Evervault, Inc. (card data encryption for Duffel's card form, used when the Controller saves an agency payment card for Duffel bookings; the card number never reaches the Processor's servers), United States
  • Anthropic PBC (AI features, with identity fields removed before sending), United States
  • OpenAI, L.L.C. (AI features, with identity fields removed before sending), United States
  • Google LLC (Gemini API, AI features, with identity fields removed before sending), United States
  • DeepL SE (machine translation, with identity fields removed before sending), Germany
  • Intuition Machines, Inc. (hCaptcha bot protection on sign-in, sign-up, password reset, invite and public lead forms), United States
  • Zoomash Ltd, operator of WeatherAPI.com (weather forecasts for trip destinations; no personal data is sent), United Kingdom
  • Browser push services operated by Google, Mozilla, Apple or Microsoft, chosen by the user's browser (delivery of in-app notifications, encrypted end to end), location varies by vendor
  • Crisp IM SAS (live chat and customer support; the Controller's staff may share client details in support conversations), France
  • Vetted contractors (Done-For-You Services, only when an engagement requires access to Personal Data), locations available on request

The Processor keeps this list up to date on this page. It will give the Controller at least 30 days' notice of any new or replacement Sub-Processor by updating this page and emailing the workspace owner, so the Controller can object on reasonable data protection grounds. The parties will discuss any objection in good faith; if they cannot resolve it, the Controller may terminate the affected services and receive a refund of any prepaid fees for the unused period.

The Processor imposes data protection obligations on each Sub-Processor that are no less protective than those in this DPA, and remains responsible to the Controller for each Sub-Processor's performance.

Services the Controller connects with its own account are the Controller's own providers and not Sub-Processors: its own Stripe account (including Stripe Connect Express for supplier payouts) and its own PayPal account for client payments and supplier payouts, its own Duffel account for flight bookings, its own SMTP server, and its own social media accounts. The Processor sends data to them only on the Controller's instruction and never holds client payments or supplier payouts. The Processor's own Stripe account is used only to bill the Controller for subscriptions and AI credits.

7. International Data Transfers

Personal Data is stored in the United States (US East, N. Virginia) and may be processed by Sub-Processors in the countries listed in section 6. To the extent Personal Data subject to the GDPR is transferred to a country without an adequacy decision, the Standard Contractual Clauses are incorporated into this DPA by reference, with the Controller as data exporter and the Processor as data importer. Module 2 applies where the Controller is a controller, and Module 3 where the Controller is a processor. Clause 7 (docking clause) applies; under Clause 9, option 2 (general written authorization) applies with the notice period in section 6; the optional wording in Clause 11 does not apply; for Clauses 17 and 18, the law and courts of Ireland apply; and Annexes I to III are completed by sections 2, 6 and 8 of this DPA. Where a Sub-Processor is certified under the EU-U.S. Data Privacy Framework (with the UK Extension and the Swiss-U.S. DPF), the Processor may rely on that certification instead.

For transfers subject to the UK GDPR, the International Data Transfer Addendum issued by the UK Information Commissioner applies in addition to the Standard Contractual Clauses. For transfers subject to Swiss data protection law, the Standard Contractual Clauses apply with the adjustments required by the Swiss Federal Data Protection and Information Commissioner, and references to the GDPR include the Swiss Federal Act on Data Protection.

We implement supplementary measures as needed based on the destination country's data protection framework, including encryption in transit and at rest, access controls, and contractual commitments from Sub-Processors.

8. Security Measures

The Processor implements and maintains appropriate technical and organizational measures to protect Personal Data, as required by GDPR Article 32, including:

  • Encryption of all data in transit using TLS 1.2 or higher
  • AES-256 encryption at rest for sensitive categories of Personal Data, including identity and travel documents, booking references, health-related notes and payment details, with encryption keys managed separately from the data
  • Uploaded identity and travel documents encrypted before storage; other files kept in private storage and shared only through short-lived signed links
  • Access control on every request through authentication, workspace isolation and role-based permissions, with portal users limited to what the Controller shares with them
  • Strong authentication: passwords stored only as hashes, multi-factor sign-in that the Controller can require, session expiry, and protection against automated and brute-force sign-in attempts
  • Application and infrastructure protections, including rate limiting, security headers and verification of incoming provider webhooks
  • Audit logging of sensitive actions, on-screen masking of sensitive fields, exclusion of sensitive values from logs, error reports and analytics, and approval by the Controller's owner or admin for changes to supplier payout and identity details
  • Safeguards for AI features: identity data is removed before any text is sent to an AI provider, and AI models have no access to the Processor's systems or databases
  • Personnel and administrative access limited to what is needed to provide, support or secure the Service, with administrative and support access logged

The Processor may update these measures over time, provided that the overall level of protection of Personal Data is not reduced. A more detailed security overview is available to customers on request, subject to confidentiality.

9. Data Breach Notification

The Processor shall notify the Controller without undue delay, and in any event within 48 hours, after becoming aware of a Personal Data breach affecting the Controller's Personal Data. The notification shall include the nature of the breach, categories of data affected, approximate number of data subjects affected, likely consequences, and measures taken or proposed to mitigate the breach. Where not all information is available at once, the Processor will provide it in phases as it becomes available.

The Processor shall cooperate with the Controller and take reasonable steps to assist in the investigation, mitigation and remediation of the breach. Notifying a breach is not an admission of fault. For an incident affecting only Platform Account Data, the Processor, as controller, handles any notice to authorities and people, and will tell affected Controllers where the incident could affect their workspace.

10. Data Subject Rights

The Processor shall assist the Controller in fulfilling its obligations to respond to Data Subject requests, including rights of access, rectification, erasure, restriction, portability, and objection. The Processor shall promptly notify the Controller if it receives a request from a Data Subject directly and will not respond to it, except to refer the Data Subject to the Controller, unless the Controller authorizes it.

The Service lets the Controller answer most requests itself: search, view and correct records; export contact and workspace data in readable form (sensitive fields are decrypted for export after permission checks); erase or anonymize a person through the built-in erasure function, which keeps the finance records the law requires; and see and cancel pending client deletion requests. Clients and suppliers can download their own data and ask for deletion from their portal. A client's deletion request is scheduled 30 days ahead and shown to the Controller, which may cancel it in that window where it has grounds to; at the date, that client's access to the Controller is removed and the client's record is erased or anonymized, and the person's login is erased if it serves no other customer. A company supplier's tax ID may be kept as a business record after the personal account is deleted; a sole trader's is erased. The Processor will also give reasonable help with data protection impact assessments and prior consultations.

11. Data Retention & Deletion

The Processor shall process and retain Personal Data only for the duration of the Controller's subscription and the deletion periods below. The Controller can export its data at any time in readable formats. When the workspace owner deletes the workspace, it is held pending deletion for 30 days: members lose access, sending and automations stop, and the owner can restore it. At the end of the 30 days the workspace and its Personal Data are deleted, including at Sub-Processors (for example social media profiles and stored files). When the subscription otherwise ends, the Controller may export its Personal Data for 30 days, after which the Processor shall delete it, unless retention is required by applicable law. Copies held in backups are deleted as those backups are overwritten in the normal cycle and remain encrypted until then.

12. Audit Rights

The Processor will make available to the Controller all information reasonably necessary to demonstrate compliance with this DPA, including written answers to reasonable security questionnaires and any third-party certifications or audit reports it holds.

If that information is not sufficient, or if a supervisory authority requires it, or following a Personal Data breach, the Controller may conduct an audit, including an inspection, itself or through an independent auditor bound by confidentiality. Audits may take place no more than once in any 12-month period, except following a breach or at a supervisory authority's request, require at least 30 days' notice, take place during normal business hours without unreasonably interfering with the Processor's operations, and are at the Controller's cost.

13. US State Privacy Laws

To the extent the California Consumer Privacy Act or similar US state privacy laws apply to Personal Data, the Processor acts as the Controller's service provider or processor. The Processor will not sell or share the Personal Data; will not retain, use or disclose it for any purpose other than providing the Service or as those laws permit; will not retain, use or disclose it outside the direct business relationship with the Controller; and will not combine it with personal information it receives from or on behalf of another person, or collects from its own interactions with the consumer, except as those laws and their regulations permit (including for security, integrity and fraud prevention) and as described in section 3 for the shared login. The Processor will comply with those laws, provide the level of privacy protection they require, notify the Controller if it can no longer meet these obligations, allow the Controller to take reasonable steps to stop and remedy unauthorized use, and engage Sub-Processors only under written contracts with the same restrictions. The Processor certifies that it understands and will comply with these restrictions.

14. Liability

Each party's liability under this DPA is subject to the limitations of liability set forth in the Terms of Service. Nothing in this DPA limits either party's liability for breaches of data protection laws where such limitation is not permitted by applicable law.

15. Term & Termination

This DPA shall remain in effect for the duration of the Controller's subscription to the Service. The DPA shall automatically terminate when the Processor no longer processes Personal Data on behalf of the Controller, subject to the data deletion obligations described above.

If this DPA conflicts with the Terms of Service, this DPA controls. If the Standard Contractual Clauses conflict with this DPA, the Standard Contractual Clauses control.

16. Contact

For questions regarding this DPA or to exercise your rights, please contact our Data Protection team.

Email: privacy@attentionkeeper.com

We use cookies

This website uses cookies to improve your experience. By continuing to use this site, you agree to our use of cookies. See our Cookie Policy to learn more.

If you click Decline, only Necessary Cookies will always be enabled.