This addendum governs the data processor relationship between Aurora and enterprise customers, ensuring your organisation's personal data is handled in accordance with GDPR Article 28 requirements.
Status: this DPA has not yet been reviewed by a qualified lawyer. Some of the sub-processor data-processing terms described in "International Transfers" below take effect only after a separate signature, opt-in, or plan change that has not yet been completed; Leangency will complete each of those steps before this DPA is signed with any customer. To discuss this DPA, email hello@leangency.com.
This Data Processing Addendum ("DPA") forms part of the Aurora Terms of Service and governs the processing of personal data by the operator of Aurora on behalf of the customer ("Controller"). Aurora is operated by Talysson da Silva Oliveira, trading as "Leangency", a sole trader based in London ("Processor", "Leangency", "we", "us"). Talysson da Silva Oliveira is not VAT registered. Notices to the Processor under this DPA should be sent to hello@leangency.com rather than to a street address.
This DPA is entered into pursuant to Article 28 of the UK General Data Protection Regulation (the retained version of Regulation (EU) 2016/679 as it forms part of the law of the United Kingdom by virtue of section 3 of the European Union (Withdrawal) Act 2018, as amended by the Data Protection, Privacy and Electronic Communications (Amendments etc) (EU Exit) Regulations 2019 and later by the Data (Use and Access) Act 2025 — "UK GDPR"), together with the Data Protection Act 2018. Where the Controller or its data subjects are also subject to the EU GDPR (Regulation (EU) 2016/679), the parties intend for the equivalent EU GDPR Article 28 obligations to apply in parallel. The Information Commissioner's Office ("ICO") is the UK supervisory authority; its guidance on this Article 28 contract is at https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/accountability-and-governance/contracts-and-liabilities-between-controllers-and-processors-multi/what-needs-to-be-included-in-the-contract/.
The subject matter of the processing is the provision of the Aurora CRM platform (lead, contact, account, opportunity, case, and ticket management, AI-assisted scoring and workflow automation, and related communications) as described in the Terms of Service. The duration of processing is coterminous with the Controller's subscription to Aurora, starting when the Controller's tenant is provisioned and continuing until the subscription ends.
Upon expiry or termination of the Terms of Service, personal data is handled as set out in "Data Return and Deletion" below.
The Processor processes personal data solely to provide Aurora's contracted functionality: capturing and qualifying leads, managing contacts, accounts, opportunities, cases and tickets, scheduling appointments, sending transactional email and SMS notifications, generating AI-assisted lead scores and predictions, maintaining an audit trail of account activity, and billing the Controller's subscription.
Processing activities include collection, storage, retrieval, consultation, use, AI-assisted analysis, disclosure to the sub-processors listed below, and erasure or destruction of personal data, each only as necessary to deliver the contracted service or to comply with a legal obligation.
The personal data processed under this DPA includes, but is not limited to: contact details (names, email addresses, phone numbers), account and company information, CRM interaction history (notes, activities, emails, calls, appointments, support tickets), AI-generated scores and predictions derived from that interaction history, and technical data such as user-agent and IP address captured for security and fraud-prevention logging.
Special categories of personal data as defined by UK GDPR Article 9 (health, biometric, racial or ethnic origin, and similar data) are not intended to be processed by Aurora. The Controller is responsible for ensuring no such data is submitted to the platform; the Processor has no mechanism to detect or filter special category data submitted in free-text fields.
The categories of data subjects whose personal data is processed include: the Controller's leads and prospective customers, the Controller's existing customers and contacts, the Controller's own employees and contractors who are given user accounts on the platform, and third-party business contacts (for example, opposing parties, vendors, or partners) that the Controller's users record in the CRM.
The Processor shall process personal data only on the Controller's documented instructions, including with regard to transfers of personal data to a third country or international organisation, unless required to do otherwise by UK law applicable to the Processor — in which case the Processor shall inform the Controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest. Unless the Controller gives further instructions, those instructions are the ones described in "Nature and Purpose of Processing" above and in the Terms of Service; any further or different instruction from the Controller should be given in writing, including by email to hello@leangency.com, so that it is documented.
In line with the final paragraph of UK GDPR Article 28(3), the Processor shall immediately inform the Controller if, in the Processor's opinion, an instruction given by the Controller infringes UK GDPR, the Data Protection Act 2018, or other applicable data protection law. The ICO's guidance on what a controller-processor contract must include, cited in "Introduction and Parties" above, confirms both limbs of this obligation.
The Processor shall ensure that each of its employees, contractors, and other personnel who are authorised to process personal data under this DPA has committed themselves to confidentiality in respect of that personal data — whether under a written confidentiality or non-disclosure obligation in their contract of employment or engagement, or because they are already subject to an appropriate statutory obligation of confidentiality — before they are given that access. Access is limited to personnel who need it to provide the contracted functionality described in "Nature and Purpose of Processing" above, consistent with the role-based access control described in "Security Measures" below. This personnel-confidentiality duty is separate from, and in addition to, the confidentiality obligations owed by sub-processors described in "Sub-processors" below and in "Audit and Compliance" below. See the ICO's guidance cited in "Introduction and Parties" above for the equivalent requirement at UK GDPR Article 28(3)(b).
The Controller shall ensure that personal data submitted to Aurora has a lawful basis for processing under applicable data protection law, that any required privacy notices have been given to the relevant data subjects, and that it has authority to instruct the Processor on the processing of that data. The Controller is responsible for responding to data subject rights requests it receives directly and for notifying the Processor of any instruction that would change how personal data is processed.
The Controller retains all rights to the personal data processed on its behalf and may instruct the Processor to correct, delete, or export that data at any time through the product or by emailing hello@leangency.com.
The Controller grants Leangency general authorisation to engage the sub-processors listed below, each of which is given access only to the personal data necessary to perform its function. Leangency will notify the Controller of any intended addition or replacement of a sub-processor by email to the Controller's registered account contact, giving the Controller a reasonable opportunity to object on reasonable data-protection grounds before the change takes effect.
Leangency shall engage each sub-processor only under a written contract that imposes on it the same data-protection obligations that this DPA imposes on Leangency, in particular the obligations described in "Confidentiality of Personnel", "Security Measures", "Personal Data Breach Notification by the Processor", "Data Subject Rights Assistance", and "Data Return and Deletion" above, to the extent relevant to that sub-processor's function. Where a sub-processor fails to fulfil its data-protection obligations, Leangency remains fully liable to the Controller for the performance of that sub-processor's obligations, in accordance with UK GDPR Article 28(4). See the ICO's guidance cited in "Introduction and Parties" above for the equivalent requirement.
As checked on 12 October 2026, the sub-processors used to provide Aurora in production are the following.
Vercel Inc. hosts the Aurora web application.
Railway Corporation hosts the API, AI, and background-job services, including a Redis instance used for caching and job queues.
Supabase, Inc. provides the managed PostgreSQL database, authentication, and file storage.
Upstash, Inc. provides managed Redis used for rate limiting on the web application.
Resend, Inc. delivers transactional email.
Twilio Inc. delivers SMS notifications.
Functional Software, Inc., trading as Sentry, provides error tracking and performance monitoring.
Google LLC generates vector embeddings of CRM text content, used for AI-assisted scoring, qualification, and semantic search, through the Gemini Developer API.
OpenRouter, Inc. receives the prompts for AI-assisted lead scoring, qualification, email drafting, and reasoning, and routes each request to the underlying large-language-model provider for the model configured for that request. That onward routing is OpenRouter's own sub-processing relationship, not a direct relationship between Leangency and the underlying provider.
Raintank Inc., trading as Grafana Labs, provides the Grafana Cloud monitoring service, which receives logs, traces, and metrics from Aurora's production services, including any personal data that appears in them. Added on 3 November 2026.
Zoho Corporation provides the mailboxes that receive email sent to Leangency's own addresses, including hello@leangency.com, and so holds any personal data sent to those addresses. Added on 3 November 2026.
Twilio SendGrid Inc., OpenAI, L.L.C., Anthropic, PBC, and Amazon Web Services, Inc. (S3 storage) are supported by Aurora's codebase as configurable providers but are not enabled in production. This DPA will be updated, and the Controller notified as described above, before any of them is switched on.
Stripe, Inc. is not a sub-processor under this DPA. It receives only the Controller's own billing details (the billing contact's name and email, tax ID, and invoice contact) so that Leangency can bill the Controller for its Aurora subscription. For that data Leangency is itself the controller, and Leangency's privacy notice, not this DPA, covers that billing relationship.
The Processor shall provide reasonable technical assistance to the Controller in responding to requests from data subjects exercising their rights under UK GDPR, including the rights of access, rectification, erasure, restriction, portability, and objection, and will not respond directly to a data subject request unless instructed to do so by the Controller or required to do so by law.
The Processor implements technical and organisational measures appropriate to the risk, in line with UK GDPR Article 32 and the ICO's guidance on security (https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/accountability-and-governance/guide-to-accountability-and-governance/). These measures include encryption in transit (TLS) and at rest for the primary database, role-based access control and tenant isolation enforced through row-level security, authenticated and audited administrative access, and logging of security-relevant events.
Aurora does not currently hold an independent security certification such as SOC 2 or ISO/IEC 27001; references to such standards elsewhere in Aurora's documentation describe internal controls modelled on those frameworks, not an externally certified status. Detailed technical and organisational measures are available to a Controller on request to hello@leangency.com, and the Processor will assist the Controller with its own Article 32 obligations, breach notifications under Article 33/34, and any data protection impact assessment that depends on how the Processor handles the Controller's data.
Where the Processor becomes aware of a personal data breach affecting personal data processed under this DPA, it shall notify the Controller without undue delay, in accordance with UK GDPR Article 33(2). This duty is separate from, and precedes, the assistance described in "Security Measures" above with the Controller's own obligations under Articles 32 to 34, and it is owed regardless of whether the breach was caused by the Processor, a sub-processor, or a third party. The ICO's guidance on personal data breaches confirms that where a controller uses a processor, and that processor suffers a breach, the processor "must inform [the controller] without undue delay as soon as it becomes aware" of it ("What role do processors have?", https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breaches-a-guide/). The notification shall include the information available to the Processor at the time, so that the Controller can assess the breach and, where required, notify the ICO within the Controller's own 72-hour deadline under Article 33(1); the Processor shall provide further information as it becomes available.
Upon termination of the Terms of Service, or on the Controller's written request, the Processor shall delete or return all personal data processed on the Controller's behalf, and delete existing copies, within 30 days, unless retention of specific data is required by UK law (for example, billing records kept for tax purposes). The Controller may choose return, deletion, or export through the product's export tooling or by emailing hello@leangency.com.
The Processor shall make available to the Controller the information reasonably necessary to demonstrate compliance with this DPA, and shall allow for and contribute to audits, including inspections, conducted by the Controller or an auditor mandated by the Controller, subject to reasonable advance notice, a reasonable frequency, and the Processor's and its sub-processors' confidentiality obligations to other customers.
Several of the sub-processors listed above are based outside the United Kingdom, principally in the United States, so using them involves a restricted transfer of personal data under UK GDPR Chapter V. Any such transfer relies on one of the safeguards recognised by the ICO: a UK adequacy regulation for the destination, the International Data Transfer Agreement ("IDTA") or the International Data Transfer Addendum to the EU Standard Contractual Clauses, or UK Binding Corporate Rules, together with a transfer risk assessment confirming that the data is not materially less protected after the transfer. The ICO's current (2026) guidance, including its three-step test for identifying a restricted transfer, is at https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/international-transfers/a-brief-guide-to-international-transfers/ and https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2026/01/updated-guidance-on-international-transfers-published/.
For each sub-processor listed in "Sub-processors" above, Leangency relies on the transfer safeguard named in that sub-processor's own published data-processing terms, as read on 12 October 2026 unless a later date is given below.
Vercel Inc.: Data Processing Addendum, https://vercel.com/legal/dpa, which incorporates the UK International Data Transfer Agreement for customers on Vercel's Pro and Enterprise plans.
Railway Corporation: Data Processing Addendum, https://railway.com/legal/dpa, using the UK Addendum to the EU Standard Contractual Clauses. It becomes binding once the customer submits Railway's signature form and Railway countersigns it.
Supabase, Inc.: Data Processing Addendum, https://supabase.com/legal/dpa, using the ICO's UK Addendum (version B1.0), incorporated on accepting the Supabase Terms of Service.
Resend, Inc.: Data Processing Addendum, https://resend.com/legal/dpa, using the EU Standard Contractual Clauses as amended by the UK Addendum, binding on entering the Resend agreement.
Twilio Inc.: Data Protection Addendum, https://www.twilio.com/en-us/legal/data-protection-addendum, using the UK International Data Transfer Agreement (version B1.0), forming part of the Twilio agreement.
Functional Software, Inc., trading as Sentry: Data Processing Addendum, https://sentry.io/legal/dpa/, relying on Sentry's certification to the UK Extension to the EU-U.S. Data Privacy Framework, with the UK International Data Transfer Addendum (version B1.0) as a fallback. It is entered into by electronic acceptance.
Upstash, Inc.: Data Processing Addendum, https://upstash.com/trust/dpa.pdf, using the ICO's UK Addendum (version B1.0), incorporated into the Upstash Terms of Service.
Google LLC: Data Processing Addendum for Products Where Google is a Data Processor, https://business.safety.google/processorterms/, relying on Google LLC's certification to the UK Extension to the EU-U.S. Data Privacy Framework. Google's Gemini API terms apply its paid-service data-use terms to accounts in the United Kingdom, so prompts and responses are not used to improve Google's products.
OpenRouter, Inc.: OpenRouter offers a Data Processing Addendum, naming the EU Standard Contractual Clauses and the UK Addendum, as part of its Enterprise Access Agreement, https://openrouter.ai/terms-of-service-enterprise.
Raintank Inc., trading as Grafana Labs: Data Processing Agreement, https://grafana.com/legal/data-processing-agreement/, version dated 2 April 2026 and read on 3 November 2026, using the EU Standard Contractual Clauses with the UK transfer terms it calls the UK International Data Transfer Agreement (version B1.0). It takes effect once the customer completes, signs, and submits it to Grafana Labs.
Zoho Corporation: Zoho provides its Data Processing Addendum for signature on request. Its privacy policy, https://www.zoho.com/privacy.html, read on 3 November 2026, names agreements based on the EU Commission's Model Contractual Clauses and no UK-specific instrument, so the UK safeguard will be confirmed from the addendum itself before this DPA is signed with any customer.
Where a sub-processor's data-processing terms take effect only after a separate signature or opt-in, or apply only on a particular plan, Leangency will complete that step before this DPA is signed with any customer. If Twilio SendGrid, OpenAI, Anthropic, or Amazon Web Services is enabled later, its transfer safeguard will be checked and added here first.
Contact our legal team at hello@leangency.com for enterprise DPA enquiries, countersigned copies, or audit requests. You may also review our Privacy Policy and Security Overview for additional data governance information.