Data Processing Agreement

How Jenny AI processes your leads' and members' personal data on your behalf. It forms part of our Terms of Service. See also our sub-processors and Privacy Policy.

Version 1.0, effective 5 November 2026

This Data Processing Agreement ("DPA") forms part of the Terms of Service for the Jenny AI service (the "Main Agreement") between the gym that holds the Jenny AI account (the "Controller") and Mason Alexandra Ltd, trading as Jenny AI, registered in England and Wales with company number 10197344, registered office 172-174 Albert Road, Jarrow, England, NE32 5JA, registered with the Information Commissioner's Office under number ZA527927 (the "Processor").

It applies to the personal data the Processor processes on the Controller's behalf when providing the service, and is intended to meet Article 28(3) of the UK GDPR. Where the Controller is subject to the EU GDPR, references to the UK GDPR include the EU GDPR as applicable.

1. Definitions

Terms used in the UK GDPR ("controller", "processor", "personal data", "personal data breach", "data subject", "processing", "special category data", "supervisory authority") have the meanings given there. "Sub-processor" means a third party the Processor engages to process Controller personal data. "Commissioner" means the UK Information Commissioner.

2. Details of the processing

Subject matterProviding the Jenny AI service: AI-assisted replies to and follow-up of the Controller’s enquiries, leads and members; bookings; CRM records; reporting.
DurationThe term of the Main Agreement, plus the deletion period in clause 11.
NatureCollection (via the Controller’s connected channels and forms), storage, organisation, retrieval, use (generating AI replies, summaries and lead scoring), transmission (sending messages on the Controller’s channels, syncing to integrations the Controller connects) and erasure.
PurposeSolely to provide the service to the Controller in line with the Main Agreement and the Controller’s documented instructions.
Data subjectsThe Controller’s enquiries and leads, members and former members, website visitors who use the Controller’s chat or forms, and the Controller’s staff who use the service.
Personal dataNames; phone numbers; email addresses; social media profile names and ids; message content (text, voice notes, images) on WhatsApp, Instagram, Messenger, email and website chat; form answers; bookings, appointments and trial sessions; membership and purchase status; ad attribution (campaign, UTM, Facebook lead ids); consent and unsubscribe records; technical data (IP address, device) for website chat and forms.
Special category dataHealth data where the Controller’s sign-up forms ask for it (for example injuries, medical conditions, pregnancy, medication) or where a data subject volunteers it in conversation. The Controller is responsible for identifying a lawful basis and an Article 9 condition (usually explicit consent) and for telling data subjects. See clause 7.3.

3. Controller's obligations

3.1 The Controller is responsible for the lawfulness of the processing, including its privacy notice, its lawful basis (and Article 9 condition for health data), compliance with the Privacy and Electronic Communications Regulations for marketing messages and emails, and consent for cookies on its own website.

3.2 The Controller's instructions are the Main Agreement, this DPA and the Controller's configuration of the service (scripts, channels, integrations, retention settings). Additional instructions must be in writing.

4. Processor's obligations

The Processor shall:

  1. 4.1 process Controller personal data only on the Controller's documented instructions, including on transfers outside the UK, unless required by law (in which case it will tell the Controller first unless the law forbids it);
  2. 4.2 tell the Controller immediately if, in its opinion, an instruction infringes data protection law;
  3. 4.3 ensure that everyone authorised to process the data is bound by confidentiality;
  4. 4.4 implement the technical and organisational measures in Annex 1 (Article 32);
  5. 4.5 respect the conditions in clause 5 for engaging sub-processors;
  6. 4.6 assist the Controller, taking into account the nature of the processing, with data subject requests (clause 8), security, breach notification, data protection impact assessments and prior consultation (Articles 32 to 36);
  7. 4.7 delete or return the data at the end of the service (clause 11);
  8. 4.8 make available the information needed to demonstrate compliance with Article 28 and allow audits (clause 10);
  9. 4.9 not sell Controller personal data and not use it for any other customer or for its own purposes, except (a) anonymised and aggregated service statistics, and (b) where the Controller has switched on the optional "AI training" or "Collective learning" settings in the service, anonymised patterns derived from the Controller's conversations to improve the service for all customers. Both settings are off unless the Controller turns them on, and the Controller can turn them off at any time.

5. Sub-processors

5.1 The Controller gives general written authorisation for the Processor to use the sub-processors published at /legal/subprocessors.

5.2 The Processor will give the Controller at least 14 days' notice (by email to the account address and on the published list) before adding or replacing a sub-processor. The Controller may object on reasonable data protection grounds within that period. The parties will discuss the objection in good faith; if it is not resolved, the Controller may terminate the affected service without penalty and receive a pro-rata refund of fees prepaid for the period after termination.

5.3 The Processor will impose data protection obligations on each sub-processor that are no less protective than this DPA, and remains liable to the Controller for each sub-processor's performance.

5.4 Integrations the Controller chooses to connect (for example Kit, MailerLite, Wodify, TeamUp, Slack, Calendly, Google Calendar, GoHighLevel) are listed for transparency. Data the Controller instructs the Processor to send to its own account at those services is subject to the Controller's own contract with that provider.

6. International transfers

6.1 The primary database is hosted in the EU (Supabase, Frankfurt). Several sub-processors are in the United States or operate globally (see the published list).

6.2 For each restricted transfer the Processor relies on the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, as incorporated in the sub-processor's terms, and, where the sub-processor is certified, the UK Extension to the EU-US Data Privacy Framework. The Processor will carry out and keep a transfer risk assessment for each sub-processor in the United States.

7. Security

7.1 The Processor will implement and maintain the measures in Annex 1, and review them at least quarterly.

7.2 The Processor will not make security claims to the Controller that are not true at the time; Annex 1 separates measures in place from measures in progress.

7.3 Health data minimisation. The service has a per-gym setting that replaces health-related form answers with a neutral marker before any prompt is sent to the AI model provider. It is on by default for every gym; it is switched off only on the Controller's written instruction.

8. Data subject requests

8.1 If the Processor receives a request from a data subject relating to Controller data, it will pass it to the Controller without undue delay and not respond itself except to acknowledge receipt, unless the Controller authorises it.

8.2 The Processor provides the Controller with the means to find, export, correct and delete a data subject's data in the service. Where a request cannot be carried out in the app, the Processor will carry it out on the Controller's written instruction within 10 working days, so the Controller can meet the one-month deadline.

8.3 Opt-outs ("STOP", "unsubscribe", "delete my data") received on any channel are honoured automatically by stopping messages to that person, and flagged to the Controller.

9. Personal data breaches

9.1 The Processor will notify the Controller of a personal data breach affecting Controller data without undue delay after becoming aware of it.

9.2 The notice will include, as far as known: the nature of the breach, the categories and approximate number of data subjects and records, the likely consequences, the measures taken or proposed, and a contact point. Information not available at first will be provided in phases.

9.3 The Processor will assist the Controller with its notification to the Commissioner (within 72 hours of the Controller becoming aware) and to data subjects, will not notify the Controller's data subjects itself without the Controller's agreement unless required by law, and will keep a record of every breach.

10. Audits and information

10.1 The Processor will make available, on request and not more than once a year (or after a breach, or at a supervisory authority's request), the information reasonably needed to demonstrate compliance: this DPA, the sub-processor list, the record of processing, the data protection impact assessment, summaries of security audits and the measures in Annex 1.

10.2 Where that information is not sufficient, the Controller (or an independent auditor bound by confidentiality) may carry out an audit on 30 days' notice, during business hours, at the Controller's cost, and without access to other customers' data.

11. End of the service

11.1 Until the account is deleted, the Controller may export its data using the service's export features.

11.2 When the Controller asks for its account to be deleted, the Processor holds the account for 30 days so the request can be cancelled, and then deletes Controller personal data, including from integrations it controls, within a further 30 days, unless the law requires it to be kept. The same applies at the end of the service. Backups are overwritten on the hosting provider's backup cycle and are not restored except for disaster recovery. On request, the Processor will confirm deletion in writing.

12. Liability

Each party's liability under this DPA is subject to the limitations and exclusions of liability in the Main Agreement.

13. General

If this DPA conflicts with the Main Agreement, this DPA prevails for data protection matters. The Processor may update this DPA to reflect changes in law or in the service; material changes are notified to the Controller in the service. This DPA is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.

Annex 1: Technical and organisational measures

Measures in place

  • Encryption in transit: TLS everywhere, HSTS with preload, strict security headers.
  • Hosting: primary database in the EU (Supabase, Frankfurt) with encryption at rest provided by the hosting provider; daily backups and point-in-time recovery.
  • Tenant separation: every query is scoped to the gym; row level security on every public table; the AI model only sees the conversation and gym it is working on; a WhatsApp number can only be connected to one gym.
  • Webhook integrity: signature verification, failing closed, on WhatsApp, Facebook, Instagram, Messenger, Stripe, Resend and Calendly; per-connection random secrets for other providers; verification before rate limiting.
  • Authentication: bcrypt password hashing; secure, httpOnly session cookies; single-use, hashed, 1-hour password reset tokens; sign-in throttling; optional two-factor authentication.
  • Access control: role checks on every admin route; account deletion, billing and integration changes limited to the account owner or permitted team roles; impersonation logged.
  • Secrets: no secrets in the code or its history; credentials are sent to the browser only as booleans or masked values.
  • Data minimisation and retention: raw WhatsApp webhook payloads purged after 30 days; health form answers can be kept out of AI prompts (clause 7.3); phone numbers masked and message text removed from application logs; per-gym retention settings with optional automatic deletion.
  • Data subject rights: per-person export across every channel, and full erasure across every table, storage bucket and the integrations we control.
  • Opt-out: STOP / unsubscribe honoured on every channel; one-click email unsubscribe recorded.
  • Monitoring: weekly automated dependency and secret scan; security review of changes; quarterly security audit.
  • Breach procedure: a written breach response procedure.

Measures in progress (not to be relied on until complete)

  • Application-level encryption at rest of third-party integration credentials (access tokens, API keys).
  • Audit logging of all sensitive admin actions, including actions taken while impersonating.
  • Transfer risk assessments for each US sub-processor and recorded zero-data-retention terms with the AI model provider.

Questions about this DPA: privacy@usejenny.ai

Mason Alexandra Ltd, trading as Jenny AI. Registered in England and Wales, company number 10197344. Registered office: 172-174 Albert Road, Jarrow, England, NE32 5JA.