Skip to content

Data Processing Agreement

Joseph Methven t/a Caloreel · Last updated 22 November 2026

In plain English

When you use Caloreel to manage your clients, you control their data and we process it for you. This agreement sets out the promises UK GDPR requires us to make: we only act on your instructions, keep the data secure, use approved sub-processors, help you with requests and tell you quickly about any breach. It's part of our Terms of Service, so there's nothing extra to sign.

1. About this agreement

This Data Processing Agreement ("DPA") forms part of the Terms of Service between Joseph Methven, a sole trader trading as Caloreel ("Caloreel", "we", the "Processor"), and the customer that holds a Caloreel studio ("Customer", the "Controller"). The Customer accepts it, as part of the Terms, when its owner ticks the box to agree to the Terms, and it applies while we process Client Data for the Customer. There's nothing separate to sign.

It is intended to meet the requirements of Article 28 of the UK General Data Protection Regulation ("UK GDPR"). Terms such as "controller", "processor", "personal data", "personal data breach" and "data subject" have the meanings given in the UK GDPR. "Client Data" has the meaning given in the Terms.

If this DPA conflicts with the Terms on anything to do with the processing of Client Data, this DPA wins.

2. Roles and instructions

  1. The Customer is the controller of Client Data and Caloreel is its processor.
  2. We will process Client Data only on the Customer's documented instructions, unless UK law requires otherwise (in which case we'll tell the Customer first, unless the law prevents it). The Customer's instructions are: the Terms and this DPA; the Customer's use and configuration of the Services; and any other reasonable written instructions the Customer gives us that are consistent with them.
  3. We'll tell the Customer promptly if we believe an instruction breaks UK data protection law.
  4. The Customer is responsible for the lawfulness of the processing it instructs, including having a lawful basis, giving privacy information to its clients, and obtaining any consents it needs (for example for marketing emails or photographs of children). Where it switches on face recognition, the Customer is also responsible for its data protection impact assessment and for the explicit consent it relies on, as set out in Annex 4.

3. Details of the processing

The subject matter, duration, nature and purpose of the processing, and the types of personal data and categories of data subjects, are set out in Annex 1.

4. Confidentiality

We ensure that everyone we authorise to process Client Data is bound by a duty of confidentiality, whether by contract or by law, and has access only to the extent needed for their role.

5. Security

  1. We implement appropriate technical and organisational measures to protect Client Data, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing, as required by Article 32 UK GDPR. The current measures are described in Annex 2.
  2. We may update these measures over time, provided the overall level of security is not reduced.
  3. The Customer is responsible for using the Services securely, including managing team access, using gallery passwords or email allow-lists where appropriate, and keeping its own sign-in accounts secure.

6. Sub-processors

  1. The Customer gives general authorisation for us to engage sub-processors. Our current sub-processors are listed in Annex 3.
  2. We'll give the Customer at least 30 days' notice, by email to the account owner and by updating Annex 3, before adding or replacing a sub-processor.
  3. The Customer may object on reasonable data protection grounds by emailing hello@caloreel.com within that notice period. We'll work with the Customer in good faith to resolve the objection. If we can't, the Customer may cancel the affected Services before the change takes effect and we'll refund any prepaid fees for the unused period.
  4. We impose data protection obligations on each sub-processor that are no less protective than those in this DPA, and we remain responsible to the Customer for each sub-processor's performance of those obligations.

7. International transfers

  1. The Caloreel application runs on servers in London and its database is in London. Client Data files (photos, video and documents) are stored in Cloudflare R2 in an EU-jurisdiction bucket. Original files of galleries that haven't been opened for a year, and older galleries imported into Caloreel, move to Google Cloud Storage in London.
  2. We'll only transfer Client Data outside the UK, or allow a sub-processor to do so, where the transfer is protected by a safeguard recognised under UK data protection law. That means UK adequacy regulations (including the UK Extension to the EU-US Data Privacy Framework for certified US organisations), the International Data Transfer Agreement, or the UK Addendum to the European Commission's standard contractual clauses.
  3. The Customer authorises the transfers to the sub-processors in Annex 3 on that basis.
  4. Email providers, calendars and accounting software that the Customer connects (for example Google, Microsoft or Xero) are the Customer's own providers, not our sub-processors. We send data to them on the Customer's instruction when it uses those features.

8. Helping with data subject requests

  1. The Services include tools that let the Customer find, export, correct and delete Client Data. Taking into account the nature of the processing, we'll provide further reasonable help so the Customer can respond to requests from data subjects exercising their rights under Chapter III UK GDPR.
  2. If we receive a request directly from one of the Customer's clients, we'll forward it to the Customer without undue delay and won't respond ourselves, other than to tell the person we've passed it on.

9. Support access

  1. We access Client Data only as needed to provide the Services, including when the Customer asks for help, to fix a problem, or to investigate a security issue or misuse.
  2. Where we sign in to the Customer's account to do this, the session ends automatically after one hour, shows a banner while active, and is recorded in an audit log. Finance records (invoices, payments, expenses, receipts, tax settings and store sales) are hidden during these sessions.

10. Helping with compliance

Taking into account the nature of the processing and the information available to us, we'll provide reasonable help to the Customer with its obligations under Articles 32 to 36 UK GDPR, including security, breach notification, data protection impact assessments (we provide an editable template for face recognition) and prior consultation with the Information Commissioner's Office.

11. Personal data breaches

  1. We'll notify the Customer without undue delay, and in any event within 48 hours of becoming aware of a personal data breach affecting Client Data.
  2. Our notice will describe, as far as we know at the time: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact for more information. Where we don't have all the information at once, we'll provide it in phases as we learn more.
  3. We'll take reasonable steps to contain and investigate the breach and reduce its effects, and we'll co-operate with the Customer so it can meet its own obligations, including any notification to the ICO or to data subjects.
  4. Notifying a breach is not an admission of fault or liability.

12. Deletion and return

  1. During the subscription, the Customer can export its Client Data at any time.
  2. When the subscription ends, the Customer has a 30-day export window, as described in the Terms. After that, we delete Client Data from our live systems, and backup copies are deleted as those backups expire, within a further 30 days.
  3. We may keep Client Data only where UK law requires us to, and then we'll protect it and use it only for that purpose.

13. Audits and information

  1. We'll make available the information reasonably necessary to demonstrate compliance with this DPA and Article 28 UK GDPR. On request (no more than once a year, unless there's been a breach or a regulator requires it), we'll answer a reasonable security questionnaire and share relevant documentation.
  2. If that information isn't enough to show compliance, or a regulator requires it, the Customer (or an independent auditor bound by confidentiality) may carry out an audit, including an inspection. The Customer must give at least 30 days' written notice and agree the scope with us in advance. Audits must take place during business hours, avoid disrupting our service, respect the confidentiality of other customers' data, and are at the Customer's cost.

14. Liability

Each party's liability under or in connection with this DPA is subject to the limitations and exclusions in the Terms of Service, except where the law does not allow it to be limited.

15. Duration and changes

  1. This DPA lasts for as long as we process Client Data for the Customer, including during the export window and deletion process.
  2. We may update this DPA to reflect changes in law, regulatory guidance or our sub-processors (under section 6). We'll notify customers of material changes in line with the Terms. Changes won't reduce the protection of Client Data.

Annex 1: Details of the processing

Item Details
Subject matter Providing the Caloreel Services: the client CRM, inbox and email sync (Google, Microsoft, or other providers over IMAP and SMTP, if connected), calendar and meetings, bookings, quotes, contracts and e-signatures, invoices and payment plans, questionnaires, the client portal, galleries and downloads, the print store, websites and custom domains, mailing lists, finance records, and related support
Duration The term of the Customer's subscription, plus the export window and deletion periods in section 12
Nature of processing Collection, storage, organisation, structuring, retrieval, display, publication (galleries and websites the Customer publishes), transmission (including email delivery, sending print orders to labs and sending records to connected accounting software), image and video processing (resizing, watermarking, zip creation), photo analysis for album design (near-duplicates, sharpness, subject and face positions), face recognition in galleries where the Customer switches it on (Annex 4), automatic sorting of incoming email into enquiries, synchronisation with connected services, encryption, backup and deletion
Purpose To provide the Services to the Customer under the Terms and the Customer's instructions, including support and keeping the Services secure
Categories of data subjects The Customer's clients and prospective clients (including every contact in a household), people who make an enquiry or booking, gallery guests and visitors, buyers in the Customer's store, mailing list subscribers, visitors to the Customer's website, people appearing in photos and video, suppliers and venues the Customer works with, other people who correspond with the Customer, and the Customer's team members where they appear in Client Data
Types of personal data Contact details (names, email addresses, phone numbers, postal and delivery addresses); household relationships; booking and session details; contents of quotes, contracts, invoices and questionnaires; e-signature records (name, time, IP address); images and video; email content and metadata; calendar events and meeting details; gallery activity (views, favourites, comments, downloads); store order details; payment metadata (amounts, status, card brand and last four digits); expenses and receipts, which may name the people the Customer paid. Full card numbers are handled by Stripe and are never processed by Caloreel
Special category data Face fingerprints (biometric data), only in galleries where the Customer switches on face recognition, as set out in Annex 4. Otherwise not required by the Services. Photos, video or questionnaire answers may incidentally reveal special category data (for example religious belief from a ceremony, or health information). The Customer is responsible for having a condition for processing it and should only collect it where necessary
Frequency Continuous, for as long as the Customer uses the Services

Annex 2: Technical and organisational measures

Encryption

  • All connections to Caloreel use HTTPS (TLS) encryption in transit.
  • Stored data, including files and database records, is encrypted at rest.
  • Particularly sensitive values, including synced email content, connected-account tokens and email passwords, lab credentials, gallery passwords and download PINs, have an additional layer of application-level encryption (AES-256-GCM).
  • Each studio's expenses, receipts and tax profile are encrypted with a key for that studio.

Access control

  • Every record belongs to a single studio, and access is checked against that studio on every request.
  • Role-based permissions within each studio (owner, admin, staff limited to assigned jobs, read-only accountant).
  • Passwordless sign-in through single-use email links that expire after 15 minutes, or Google sign-in. Sign-in tokens are stored hashed.
  • Client access uses signed, expiring and revocable links, with optional gallery passwords, email allow-lists and download PINs.
  • Rate limiting on authentication endpoints.

Our staff

  • Multi-factor authentication for staff access to production systems and provider consoles.
  • Least-privilege access, reviewed when roles change and removed when someone leaves.
  • Support access to a customer's account lasts at most one hour, is recorded in an audit log and never shows the customer's finance records.
  • Confidentiality obligations for everyone with access to Client Data.

Logging and monitoring

  • Audit logs of important account actions and administrative access.
  • Monitoring of errors and unusual activity, with an incident response process.

Resilience and backups

  • Regular backups of databases, with restore procedures.
  • Hosting on infrastructure designed for high availability.

Data location and minimisation

  • The application and database are hosted in London. Files are stored in Cloudflare R2 in an EU-jurisdiction bucket, and original files of galleries that haven't been opened for a year, and older galleries imported into Caloreel, in Google Cloud Storage in London.
  • Receipts the Customer scans are read in the Customer's own browser, not by another company.
  • Sub-processors receive only the data they need (for example, labs receive the image, product and delivery details for an order).

Development and suppliers

  • Code review before changes reach production, and prompt patching of dependencies with known vulnerabilities.
  • Due diligence on sub-processors and written data protection terms with each of them.

Annex 3: Sub-processors

Sub-processor Service Data involved Location Transfer safeguard
Vercel Application hosting, websites and custom domains All Client Data in transit; served from London Application servers in London; global delivery network UK Extension to the EU-US Data Privacy Framework, the IDTA or UK Addendum where data is processed outside the UK
Neon Database hosting All Client Data held in the database London UK-hosted; the IDTA or UK Addendum for any support access from outside the UK
Cloudflare File storage (R2) and DNS Photos, video, documents and other files Files stored in an EU-jurisdiction bucket UK adequacy regulations (EU); the IDTA or UK Addendum where data is processed elsewhere
Google Cloud Long-term storage (Archive) of original files for galleries that haven't been opened for a year, and older galleries imported into Caloreel Original photo and video files London UK-hosted; the IDTA or UK Addendum for any support access from outside the UK
Stripe Payments for invoices and store orders, payouts Buyer and payer names, emails, payment metadata UK, EU and US UK adequacy regulations, the IDTA or UK Addendum
Resend Email delivery Recipient names and email addresses, email content US and EU UK adequacy regulations, the IDTA or UK Addendum
Google Gmail sync, Calendar and Meet (only where the Customer connects them) Email content and metadata, calendar events, guest email addresses Global UK adequacy regulations, the IDTA or UK Addendum
Microsoft Outlook mail and calendar sync (only where the Customer connects them) Email content and metadata, calendar events, guest email addresses Global UK adequacy regulations, the IDTA or UK Addendum
Prodigi Print fulfilment (UK and worldwide) Image files, product details, buyer delivery name and address UK and international lab network UK-based; the IDTA or UK Addendum for onward transfers
WHCC Print fulfilment (US), only for Customers who connect their own WHCC account Image files, product details, buyer delivery name and address US UK adequacy regulations (where certified), the IDTA or UK Addendum
Browser push services (Apple, Google, Mozilla) Delivering notifications to the Customer's team on devices where they turned them on Notification text, which can include a client's name Global UK adequacy regulations (where certified), the IDTA or UK Addendum

To object to a new sub-processor, or to ask for more detail about any of them, email hello@caloreel.com with "DPA" in the subject line.

Annex 4: Face recognition

  1. Off by default. Face recognition is available on the Unlimited plan. The Customer switches it on per gallery, or as a default for new galleries, and only after the Customer's owner has signed the Customer's data protection impact assessment in Settings. We provide an editable template for that assessment.
  2. The Customer's responsibilities. Face fingerprints used to tell people apart are biometric data under Article 9 UK GDPR. The Customer is responsible for its Article 9 condition (normally the couple's explicit consent, for example in its booking contract), for telling the people photographed, and for keeping its assessment up to date.
  3. What we process. For each face found: its position in the photo and a face fingerprint (128 numbers). For people the Customer or its client names: a name and a role. For guest selfie searches: a record of the search (email, time, consent wording version, number of matches). Selfies are fingerprinted in memory and never stored.
  4. How and where. Open-source models running on our own application servers in London (Vercel) find faces and make fingerprints; the results are stored in our database in London (Neon). No other sub-processor receives face data, and no photo or face is sent to an outside AI service.
  5. Limits. Fingerprints are compared only within the gallery they came from, never across galleries, studios or outside sources. We don't use face data for any other purpose or to train models. Fingerprints are never sent to browsers and are hidden during support sessions.
  6. Deletion. Fingerprints and names are deleted automatically when the gallery is archived, deleted or expires, when face recognition is switched off for it, and at the end of the retention period the Customer chooses (at most 12 months after the event). The Customer can remove a person at any time, which deletes their fingerprints and name straight away. Face data is deleted with all other Client Data when the subscription ends.
  7. Security. The measures in Annex 2 apply. In addition, fingerprints are stored separately from face positions so they can be deleted on their own, and guest searches are rate-limited and logged.
  8. Changes. We'll tell the Customer when the feature changes in a way that affects its assessment.

Questions about this policy? Email hello@caloreel.com.