← Back to Legal

This legal document is provided in English. The same version applies on each language route.

Data Processing Agreement

Last updated: 10 October 2026

This DPA takes effect when incorporated into the applicable Services agreement. Section 11 governs existing agreements.


PARTIES

This Data Processing Agreement (“DPA”) is entered into between:

Data Controller (“Customer”): The entity agreeing to the Carrott Terms of Service

Data Processor (“Processor”):

  • Company Name: Carrott LTD
  • Registered Address: Piccadilly Business Centre, Blackett Street, Manchester, M12 6AE
  • Contact Email: admin@carrott.io

This DPA forms part of the applicable Services agreement, including the Terms of Service where applicable. Digital Loyalty and Carrott are service brands of Carrott LTD. Privacy requests, incidents and subprocessor objections should be sent to admin@carrott.io. This is a privacy contact, not a representation that a statutory data protection officer has been appointed.


1. DEFINITIONS

1.1 “Controller” means the natural or legal person which determines the purposes and means of the Processing of Personal Data.

1.2 “Data Subject” means an identified or identifiable natural person whose Personal Data is Processed.

1.3 “GDPR” means the General Data Protection Regulation (EU) 2016/679.

1.4 “Personal Data” means any information relating to an identified or identifiable natural person.

1.5 “Processing” means any operation performed on Personal Data, including collection, storage, alteration, retrieval, use, disclosure, or erasure.

1.6 “Personal Data Breach” means a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Personal Data.

1.7 “Services” means the Carrott digital loyalty platform and related services.

1.8 “Sub-processor” means any third party engaged by Processor to Process Personal Data on behalf of Customer.

1.9 “Standard Contractual Clauses” or “SCCs” means the standard contractual clauses approved by the European Commission for international data transfers.

1.10 “UK GDPR” means the GDPR as incorporated into UK law pursuant to the UK European Union (Withdrawal) Act 2018.


2. SCOPE AND PURPOSE

2.1 Scope

This DPA applies to the Processing of Personal Data by Processor on behalf of Customer in connection with the provision of the Services.

2.2 Roles

(a) Customer acts as Controller, or as a Processor authorised by its Controller, for the Personal Data processed on its behalf under this DPA (“Customer Personal Data”). Customer must identify the relevant Controllers and its authority to instruct Processor, including for franchise or agency networks, in the processing schedule described in Annex A.

(b) Processor acts as Processor or Sub-processor, as applicable, for Customer Personal Data. Network membership alone does not authorise sharing between separate Controllers.

(c) Carrott acts as an independent Controller for its own business account administration, subscription billing and legal compliance as described in the Privacy Policy. A dashboard user may be included in both roles for different activities. Programme-member data and identifiable analytics are not automatically independent-controller data merely because they are used to operate the platform.

2.3 Purpose

Processor shall Process Personal Data only for the following purposes:

  • Providing the Services as described in the Terms of Service
  • Operating and maintaining the digital loyalty platform
  • Generating and distributing digital wallet passes
  • Processing transactions and tracking loyalty activity
  • Sending communications on behalf of Customer
  • Providing customer support
  • Maintaining security and preventing fraud
  • Synchronising data with integrations enabled on Customer’s documented instructions
  • Providing service analytics and diagnostics within Customer’s documented instructions, subject to Section 4.1 and Annex A

3. CATEGORIES OF DATA AND DATA SUBJECTS

3.1 Categories of Data Subjects

  • Customer’s end-user customers enrolled in loyalty programs
  • Customer’s employees and authorized users

3.2 Categories of Personal Data

CategoryData Elements
Identity DataName, email address, phone number, date of birth
Contact DataEmail address, phone number
Transaction DataLoyalty transactions, stamps, rewards, redemptions
Technical DataIP address, browser type, device identifiers
Usage DataCard activity, scan history, timestamps
Marketing DataConsent records, preferences, communication history
Integration DataCustomer matching, receipts, refunds, POS identifiers and payment/subscription references where enabled
Wallet DataPass identifiers, displayed fields, device registration and push tokens
Custom FieldsAdditional ordinary personal data defined by Customer within the agreed processing scope

3.3 Special Categories of Data

Customer must not submit special-category data or criminal-offence data unless the parties first agree in writing on the scope, lawful conditions and additional safeguards. Configuring a custom field does not itself constitute that agreement.


4. OBLIGATIONS OF THE PROCESSOR

4.1 Processing Instructions

Processor shall: (a) Process Personal Data only on documented instructions from Customer, including instructions concerning international transfers, unless required by applicable law; (b) Inform Customer of that legal requirement before Processing unless the law prohibits this on important grounds of public interest; (c) Not Process Customer Personal Data outside the agreed instructions; (d) Immediately inform Customer if, in Processor’s opinion, an instruction infringes applicable data protection law.

The agreement, completed processing schedule and authorised service settings record the instructions. Naming an analytics supplier does not authorise unrelated profiling, advertising or reuse of programme-member data. Any additional purpose requires a documented role and lawful basis, appropriate notices and any required consent or objection controls before that Processing begins.

4.2 Confidentiality

Processor shall ensure that persons authorized to Process Personal Data: (a) Have committed to confidentiality or are under statutory confidentiality obligations; (b) Process Personal Data only as instructed and authorized.

4.3 Security Measures

Processor shall implement technical and organisational measures appropriate to the risk under GDPR and UK GDPR Article 32, taking account of the nature, scope, context and purposes of Processing. Annex B describes the service architecture and the scope of controls. Provider capabilities are not a representation that every optional control is enabled or that Carrott holds a provider’s certification.

4.4 Sub-processors

(a) Customer authorizes Processor to engage Sub-processors listed in the subprocessor register document.

(b) Processor shall:

  • Impose equivalent data protection obligations on Sub-processors;
  • Remain liable for Sub-processor compliance;
  • Notify Customer of intended additions or replacements at least 30 days in advance, by email to the designated account administrator, with the supplier, purpose and relevant location/transfer information. Updating the register alone does not replace this notice.

(c) Customer may object to a new Sub-processor within 14 days of notification. If objection cannot be resolved, Customer may terminate affected Services.

4.5 Assistance with Data Subject Rights

Processor shall: (a) Implement measures to assist Customer in responding to Data Subject requests; (b) Promptly notify Customer of any Data Subject requests received; (c) Not respond directly to Data Subjects unless authorized by Customer; (d) Provide assistance through available tools and a request process appropriate to the nature of Processing. Archiving a membership or expiring a wallet card is not erasure. Customer may request return, correction, restriction or erasure through the privacy contact; this DPA does not represent that these operations are all available as automated self-service functions. Assistance must allow Customer to meet applicable statutory deadlines.

4.6 Assistance with Compliance

Processor shall assist Customer with: (a) Data protection impact assessments; (b) Prior consultation with supervisory authorities; (c) Demonstrating compliance with GDPR obligations; (d) Security measures and breach notifications.


5. PERSONAL DATA BREACH

5.1 Notification

Processor shall notify Customer without undue delay, and in any event within 48 hours, after becoming aware of a Personal Data Breach affecting Customer Personal Data. A shorter notification deadline in separately signed customer terms applies in accordance with Section 11.1. Initial notification must not be delayed while details are gathered; missing details shall follow in phases without undue further delay.

5.2 Notification Content

Notification shall include: (a) Description of the nature of the breach; (b) Categories and approximate number of Data Subjects affected; (c) Categories and approximate number of records affected; (d) Contact point for further information; (e) Likely consequences of the breach; (f) Measures taken or proposed to address the breach.

5.3 Cooperation

Processor shall: (a) Cooperate with Customer in investigating the breach; (b) Take reasonable steps to mitigate effects; (c) Preserve evidence related to the breach; (d) Assist with regulatory notifications and communications.

5.4 No Public Disclosure

Processor shall not notify Data Subjects or make public statements about a breach without Customer’s prior written approval, unless required by law.


6. AUDITS AND INSPECTIONS

6.1 Information Provision

Processor shall make available to Customer all information necessary to demonstrate compliance with this DPA and GDPR Article 28 obligations.

6.2 Audit Rights

(a) Customer may conduct audits, including inspections, to verify Processor’s compliance with this DPA.

(b) Audits shall be conducted:

  • During normal business hours;
  • With reasonable advance notice (minimum 30 days);
  • Ordinarily no more than once per year; additional audits remain available where necessary to demonstrate compliance, following a breach, or as required by law or a supervisory authority;
  • At Customer’s expense unless otherwise agreed or required by law.

These arrangements shall not prevent an urgent audit or restrict mandatory statutory or transfer-clause rights. The parties shall agree proportionate safeguards for other customers’ data.

6.3 Third-Party Audits

Processor may provide available provider reports and other relevant evidence to support an audit. Provider reports cover the provider’s controls; they do not certify Carrott or replace Customer’s inspection rights where further verification is necessary. Carrott does not claim its own SOC 2 attestation under this DPA.

6.4 Confidentiality

Audit findings shall be treated as confidential information of Processor and used solely for compliance verification.


7. INTERNATIONAL DATA TRANSFERS

7.1 Transfer Mechanisms

Processor shall only make restricted international transfers under a lawful mechanism applicable to the actual exporter, importer and activity. This includes onward transfers and remote access where applicable. An adequacy decision may be relied on only where its conditions cover the transfer.

Where contractual safeguards are required, the parties shall complete and enter into the applicable EU SCCs under Decision 2021/914 and, for UK transfers, the UK Addendum or IDTA before the transfer. Module Two applies to a Controller-to-Processor transfer and Module Three to a Processor-to-Processor transfer where applicable. The parties, transfer description, competent authority, clause options and security annexes must be completed for that transfer. A link to vendor terms or this general DPA is not a substitute for those completed arrangements. Mandatory transfer terms prevail over inconsistent commercial terms.

7.2 Transfer assessment and information

Processor shall assess restricted transfers as required by applicable law, document the relevant assessment and implement necessary supplementary measures before relying on the transfer mechanism. Processor shall make relevant location and safeguard information available to Customer. This is an obligation to perform and evidence that work, not a statement that every assessment has already been completed. The register describes recipients and supplier location information; customer-specific hosting and transfer arrangements belong in the processing schedule.

7.3 Alternative Mechanisms

If transfer mechanisms become invalid or inadequate, parties shall cooperate to implement alternative lawful mechanisms.


8. TERM AND TERMINATION

8.1 Duration

This DPA remains in effect for the duration of Customer’s use of the Services.

8.2 Termination

Obligations concerning retained Personal Data, confidentiality, return/deletion, assistance and audit survive termination for as long as relevant Personal Data remains in Processor’s possession or control.

8.3 Data Return and Deletion

Upon termination, Processor shall, at Customer’s choice, return Customer Personal Data in a structured, commonly used format or delete it, and delete existing copies unless applicable law requires storage. Processor shall complete return or deletion within 90 days of termination and certify deletion in writing. Return does not permit Processor to retain its remaining copies indefinitely. Earlier statutory deadlines for rights requests remain applicable.

Any legally required retention must be limited to the required data and period, protected and restricted to that legal purpose. Truly anonymised information is outside this DPA only if individuals can no longer be identified.

Where immediate deletion from backups is technically impracticable, Processor shall isolate the retained copies from ordinary use, protect them under this DPA and erase them within the documented backup expiry period agreed with Customer. Processor shall record deletion requests and reapply them before restored data is returned to ordinary use. The backup expiry and any outstanding copies must be disclosed in the deletion confirmation; an open-ended backup exception is not permitted.

Archiving a customer membership and later expiring its cards are service lifecycle operations, not proof that profiles, transactions, logs, analytics or stored passes have been erased. Erasure instructions must cover relevant Sub-processors and stored copies, while respecting separately controlled records held for other Controllers. A pass already saved to a person’s device may remain subject to that person’s and wallet provider’s controls.


9. OBLIGATIONS OF THE CUSTOMER

Customer warrants and undertakes that:

9.1 Lawful Basis

Customer has and will maintain a lawful basis for Processing, including valid consent where required.

9.2 Data Subject Information

Customer has provided and will provide adequate privacy notices to Data Subjects.

9.3 Instructions

Customer’s Processing instructions comply with applicable law.

9.4 Data Accuracy

Customer is responsible for ensuring the accuracy of Personal Data provided.

9.5 Security

Customer will implement appropriate security measures within its own systems.

9.6 Sensitive Data

Customer shall comply with Section 3.3. A lawful basis alone does not enable a processing activity outside the agreed service scope.


10. LIABILITY

10.1 Allocation

Liability under this DPA is governed by the applicable Services agreement. Where separately signed customer terms expressly govern liability across the Services agreement and this DPA, those terms apply instead of inconsistent public website limitations. Nothing limits data subjects’ statutory rights or liability that cannot lawfully be limited, or overrides mandatory transfer protections.

10.2 Regulatory Fines

Each party shall be responsible for administrative fines imposed on it by supervisory authorities.

10.3 Data Subject Claims

If either party receives a claim from a Data Subject regarding Processing under this DPA, it shall promptly notify the other party.


11. GENERAL PROVISIONS

11.1 Conflict

Mandatory law and applicable mandatory transfer terms prevail. Subject to those requirements, separately signed customer terms expressly addressing the same subject take precedence over inconsistent provisions of this public DPA, including agreed breach notification and liability provisions. Otherwise this DPA prevails over the public Terms of Service on data protection matters.

11.2 Amendments

This DPA may be amended: (a) By mutual written agreement; (b) By Processor to reflect legal or regulatory changes, with 30 days’ notice, only to the extent permitted by the applicable agreement.

A website edit does not silently replace a dated version incorporated into an existing signed agreement. The parties shall retain the agreed version and annexes. Subprocessor changes remain subject to Section 4.4 and any applicable signed terms.

11.3 Severability

If any provision is found invalid, the remaining provisions remain in effect.

11.4 Governing Law

This DPA is governed by: (a) For EU data: Laws of Ireland; (b) For UK data: Laws of England and Wales; (c) For other data: Laws of United Kingdom.

11.5 Entire Agreement

This DPA and its agreed schedules form the processing terms of the applicable Services agreement, subject to Section 11.1. The Privacy Policy describes Controller activities and does not expand Customer instructions.


ANNEX A: DETAILS OF PROCESSING

A.1 Subject Matter

Processing of Personal Data in connection with the Carrott digital loyalty platform.

A.2 Duration

For the term of the Services and the limited return/deletion period under Section 8.3, subject to applicable statutory deadlines.

A.3 Nature and Purpose

ActivityPurpose
CollectionEnroll customers in loyalty programs
StorageMaintain customer profiles and card data
OrganizationCategorize and segment customers
RetrievalDisplay customer information to authorized users
UseTrack loyalty transactions and rewards
DisclosureGenerate wallet passes via Apple/Google
CombinationLink customers across locations/cards only within the authorised Controller scope and sharing instructions
Integration synchronisationCustomer-authorised POS matching, loyalty updates, receipts/refunds and optional membership-payment references
Service analytics and diagnosticsJoin and dashboard activity, identified events, errors and service logs within agreed instructions
Return and erasureFulfil documented requests under Sections 4.5 and 8.3; archival and pass expiry are separate operations

A.4 Types of Personal Data

As described in Section 3.2 above.

A.5 Categories of Data Subjects

As described in Section 3.1 above.


A.6 Customer-specific processing schedule

The order or a separately agreed schedule shall identify the Controller legal entities and contacts, any network representative and its authority, covered locations/accounts, permitted cross-location sharing, enabled integrations, data fields, purposes and retention instructions. It shall also record applicable hosting locations, onward access, transfer safeguards, backup expiry and any additional security requirements before the relevant Processing begins. Changes require documented instructions. Optional services in the register apply only when enabled for that Customer.

A.7 Analytics and integrations

The join application’s analytics integration sends name, email, phone and marketing preference, where supplied, with card/programme context to PostHog as both person properties and event data. This is identifiable Processing. Dashboard-user analytics and service error/log data are distinct activities. Autocapture and session replay are configuration-dependent capabilities; this annex does not assert that replay is enabled for every production session or that captured content is anonymous. Customer instructions must specify the permitted purpose and scope; Processor must minimise collection and implement any required privacy controls. Marketing permission is not by itself permission for every analytics activity.

Customer-connected POS systems receive and supply the configured customer, receipt and loyalty fields. Payment and wallet providers have activity-specific roles described in the register. Customer must authorise the integration and the affected Controller scope; enabling an integration does not authorise unrelated data sharing.


ANNEX B: TECHNICAL AND ORGANISATIONAL MEASURES

B.1 Hosting and access

The service uses Convex for backend functions, database and application authentication, Cloudflare Workers/R2/KV for pass generation and storage, and Vercel for application hosting. Backend membership and role checks restrict access within the agency, subaccount and franchise structure. Authentication uses account credentials and sessions. This annex does not promise customer-login MFA. Staff access to vendor consoles is a separate control from customer login and must be managed on a least-privilege basis.

B.2 Encryption and provider assurance

Application connections use HTTPS. Convex describes AES-256 encryption at rest and encrypted transport in its security documentation. Cloudflare describes provider-managed encryption of R2 objects in its R2 security documentation. These descriptions apply to those provider services, not every copy on an end-user device or every external integration. Provider attestations apply to their stated scope and do not constitute Carrott certification.

B.3 Application protection and monitoring

Backend functions apply authentication, authorisation and input validation. Turnstile is used in the join flow for anti-abuse checks. The backend exposes a health endpoint. The service also supports a conditional synthetic Apple-pass generation and R2 verification monitor that reports a heartbeat to Better Stack without programme-customer records. Coverage depends on deployment configuration. Automated health checks do not imply continuous human security response, and no 24/7 staffed response is promised by this annex. Section 5 notification duties apply independently of routine support hours.

B.4 Backup and recovery scope

Convex database backups are enabled. The Professional plan supports configurable periodic backups. Its backup documentation explains the scope and exclusions, including deployment code, environment variables and scheduled functions. Separate Cloudflare R2 objects and KV configuration require separate recovery arrangements. Enabled database backups do not by themselves establish backup frequency, retention, geographical redundancy, coverage of separate services or a successful restore test. Applicable backup frequency, retention, coverage and recovery arrangements shall be recorded in the customer-specific schedule. This annex makes no representation of daily backups, geographical redundancy or completed recovery tests.

B.5 Organisational obligations

Processor shall restrict authorised access, maintain confidentiality under Section 4.2, assess security risks, and maintain measures for incident handling and restoration of availability appropriate to Article 32. The parties may agree additional evidenced controls in writing. This annex does not represent that background checks, a particular staff training programme, penetration tests or transfer assessments have already been completed. Those statements require their own supporting records.


ANNEX C: APPROVED SUB-PROCESSORS

The current approved Sub-processors are listed in the subprocessor register.


SIGNATURES

This DPA is agreed through the applicable Services agreement. An existing incorporated version changes only as provided in Section 11.

Carrott LTD

Effective when incorporated into the applicable Services agreement, subject to Section 11.

개인정보 보호

기본적으로 쿠키 없는 익명 이용 통계를 사용합니다. 개인정보 설정에서 끌 수 있습니다.

익명 통계는 기본적으로 켜져 있으며 쿠키나 기기 내 다른 저장소를 사용하지 않습니다. 방문자 ID나 프로필 없이 페이지 조회와 클릭을 집계하며 광고에 절대 사용하지 않습니다. 여기에서 끌 수 있으며 Global Privacy Control 신호로도 꺼집니다. 선택적 분석은 동의한 후에만 쿠키를 사용하며 광고나 세션 녹화를 활성화하지 않습니다. 선택은 180일간 유지됩니다.

개인정보 설정