Get 20% off your first 6 months on all agency plans · Code: LAUNCH20
arrow_back Back to Legal

Data Processors and Sub-Processors

Last Updated: 29th January 2026

1. Introduction

This document lists all third-party service providers (“sub-processors”) that Carrott uses to process personal data. As required by GDPR Article 28 and other applicable data protection laws, we maintain transparency about who handles data on our behalf.

Data Controller:

2. Categories of Data Processors

Our sub-processors fall into the following categories:

  • Payment Processing
  • Email Services
  • SMS Services
  • Mobile Wallet Services
  • Cloud Infrastructure
  • Storage Services
  • Domain Services
  • Authentication Services
  • Analytics (if applicable)

3. List of Sub-Processors

3.1 Payment Processing

ProcessorServiceData ProcessedLocationPrivacy Policy
Stripe, Inc.Payment processing, subscription billing, Connect payoutsName, email, payment method details, billing address, transaction history, subscription dataUnited States, with EU data processingstripe.com/privacy

Purpose: Process subscription payments for Business Users, handle agency payouts via Stripe Connect, manage billing events and invoicing.

Data Transferred:

  • Customer name and email
  • Payment method information
  • Billing address
  • Subscription plan details
  • Usage-based billing data

3.2 Email Services

ProcessorServiceData ProcessedLocationPrivacy Policy
Resend, Inc.Transactional and marketing email deliveryEmail addresses, email content, delivery metadataUnited Statesresend.com/legal/privacy-policy

Purpose: Deliver authentication emails (magic links, password resets), transactional notifications, subscription alerts, and marketing communications.

Data Transferred:

  • Recipient email addresses
  • Email content (subject, body)
  • Sender information
  • Delivery status and events

3.3 SMS Services

ProcessorServiceData ProcessedLocationPrivacy Policy
Twilio, Inc.SMS delivery for OTP verificationPhone numbers, SMS contentUnited Statestwilio.com/legal/privacy

Purpose: Send OTP verification codes during customer enrollment, phone number verification.

Data Transferred:

  • Recipient phone numbers (E.164 format)
  • SMS message content (verification codes)
  • Delivery status

3.4 Mobile Wallet Services

ProcessorServiceData ProcessedLocationPrivacy Policy
Apple Inc.Apple Wallet pass distribution, push notificationsPass data, device identifiers, push tokens, card serial numbersUnited Statesapple.com/legal/privacy
Google LLCGoogle Wallet pass distributionPass data, object/class identifiers, loyalty card contentUnited Statespolicies.google.com/privacy

Purpose: Generate, distribute, and update digital loyalty cards in Apple Wallet and Google Wallet.

Data Transferred to Apple:

  • Pass content (card design, text fields, barcodes)
  • Device library identifiers
  • Push notification tokens
  • Pass serial numbers
  • Authentication tokens

Data Transferred to Google:

  • Loyalty object data (card content, balances)
  • Class identifiers
  • Object identifiers
  • Callback events (saves, deletions)

3.5 Cloud Infrastructure & Database

ProcessorServiceData ProcessedLocationPrivacy Policy
Convex, Inc.Backend-as-a-Service, reactive database, serverless functionsAll application data (users, agencies, customers, cards, transactions)United Statesconvex.dev/privacy

Purpose: Host and process all application data, execute backend logic, provide real-time data synchronization.

Data Transferred:

  • User account data
  • Business configuration
  • Customer loyalty data
  • Transaction records
  • All platform data

3.6 Storage Services

ProcessorServiceData ProcessedLocationPrivacy Policy
Cloudflare, Inc. (R2)Object storage for images and assetsCard template images, logos, branding assets, wallet pass imagesGlobal (edge locations)cloudflare.com/privacypolicy

Purpose: Store and serve card template images, business logos, wallet pass assets, and other media files.

Data Transferred:

  • Image files
  • Asset metadata
  • Storage keys/references

3.7 Domain & Routing Services

ProcessorServiceData ProcessedLocationPrivacy Policy
ApproximatedCustom domain hosting, SSL provisioningDomain names, DNS configuration, routing dataUnited StatesContact provider for details

Purpose: Enable white-label custom domains for agencies, manage SSL certificates, route traffic.

Data Transferred:

  • Domain names
  • DNS records
  • Virtual host configuration

3.8 Authentication Services

ProcessorServiceData ProcessedLocationPrivacy Policy
Better AuthAuthentication library (self-hosted)Email, password hash, session tokensSelf-hosted (Convex)N/A (library, not SaaS)

Purpose: Handle user authentication, session management, magic link verification.

Note: Better Auth is a library running within our Convex backend, not an external service. Authentication data is processed within our infrastructure.


3.9 Customer Support & Feedback

ProcessorServiceData ProcessedLocationPrivacy Policy
FeaturebaseCustomer support, feedback, and feature requestsUser name, email, support tickets, feedback submissions, feature requestsUnited States / EUfeaturebase.app/privacy

Purpose: Provide in-app customer support, collect user feedback, manage feature requests and bug reports.

Data Transferred:

  • User name and email address
  • Support ticket content and attachments
  • Feature request and feedback submissions
  • User interaction metadata

3.10 Location Services

ProcessorServiceData ProcessedLocationPrivacy Policy
Google LLC (Maps/Places API)Address autocomplete, place detailsSearch queries, place IDs, geographic coordinatesUnited Statespolicies.google.com/privacy

Purpose: Provide address autocomplete for business location entry, validate addresses.

Data Transferred:

  • Address search queries
  • Selected place IDs
  • Geographic coordinates

4. Data Flow Summary

User Input


┌─────────────────────────────────────────────────────┐
│                 Carrott                      │
│              (Convex Backend)                        │
│                                                      │
│  ┌─────────┐  ┌─────────┐  ┌─────────┐             │
│  │ Users   │  │Agencies │  │Customers│             │
│  └────┬────┘  └────┬────┘  └────┬────┘             │
└───────┼────────────┼────────────┼───────────────────┘
        │            │            │
        ▼            ▼            ▼
   ┌─────────────────────────────────────────────┐
   │           Third-Party Processors            │
   │                                             │
   │  ┌────────┐  ┌────────┐  ┌────────┐        │
   │  │ Stripe │  │ Resend │  │ Twilio │        │
   │  │Payment │  │ Email  │  │  SMS   │        │
   │  └────────┘  └────────┘  └────────┘        │
   │                                             │
   │  ┌────────┐  ┌────────┐  ┌────────┐        │
   │  │ Apple  │  │ Google │  │Cloud-  │        │
   │  │ Wallet │  │ Wallet │  │ flare  │        │
   │  └────────┘  └────────┘  └────────┘        │
   └─────────────────────────────────────────────┘

5. Security and Compliance

5.1 Processor Requirements

All sub-processors are required to:

  • Implement appropriate technical and organizational security measures
  • Process data only according to our documented instructions
  • Ensure personnel are bound by confidentiality obligations
  • Assist with data subject requests
  • Delete or return data upon termination
  • Make available information for compliance audits
  • Notify us of data breaches without undue delay

5.2 Data Processing Agreements

We maintain Data Processing Agreements (DPAs) or equivalent contractual protections with all sub-processors, including:

  • Standard Contractual Clauses (SCCs) for international transfers
  • Security requirements and audit rights
  • Sub-processor notification procedures
  • Breach notification obligations

5.3 Certifications and Compliance

ProcessorCertifications/Compliance
StripePCI DSS Level 1, SOC 1 & 2, GDPR
ResendSOC 2, GDPR
TwilioSOC 2, ISO 27001, GDPR
AppleISO 27001, SOC 2
GoogleISO 27001, SOC 2, GDPR
ConvexSOC 2 Type II
CloudflareSOC 2, ISO 27001, PCI DSS
FeaturebaseGDPR

6. Changes to Sub-Processors

6.1 Notification

We will notify Business Users of any intended changes to sub-processors at least 30 days before the change takes effect, via:

  • Email notification to account administrators
  • Update to this document

6.2 Objection Process

Business Users may object to a new sub-processor by contacting us at admin@carrott.io within 14 days of notification. We will work to address concerns or provide alternatives where possible.

6.3 Change Log

DateChangeDetails
23rd January 2026Initial publicationDocument created
29th January 2026Added FeaturebaseCustomer support and feedback processor added

7. Contact Information

For questions about our sub-processors or to request Data Processing Agreements:

Carrott LTD

  • Email: admin@carrott.io
  • Address: Piccadilly Business Centre, Blackett Street, Manchester, M12 6AE

This Sub-Processors list is effective as of 29th January 2026.