Compliance Framework

Data Processing Agreement

Last Updated: May 15, 2026

This Data Processing Agreement ("DPA") forms part of the Terms of Service between ENROUTEESSENTIALS LTD ("Processor") and the Customer ("Controller").

It reflects our agreement regarding the processing of Personal Data under the General Data Protection Regulation (GDPR) and UK GDPR, in compliance with Article 28 of the GDPR.

Preamble Context

This DPA governs all processing activities by the Processor on behalf of the Controller. The full legal entity names must be clearly defined in the underlying Terms of Service to avoid ambiguity.

Article 1

Scope of Processing

We will only process Personal Data based on your documented instructions, including those specified in the Terms of Service and any configuration settings within the Raptoriods Dashboard.

Details of Processing

Categories of Subjects

Controller's employees, end-users, and authorized representatives.

Types of Data

Names, business emails, user IDs, job titles, and integration metadata.

Compliance Note (GDPR Art. 28)

The Controller is legally responsible for ensuring that its instructions to the Processor are lawful. Documented instructions can be provided through API calls, dashboard configurations, or written requests.

Article 2

Sub-processors

To deliver our high-availability service, we utilize secure, industry-leading sub-processors:

Microsoft Azure

Cloud infrastructure and application hosting.

Supabase

Secure database hosting.

2.2 Changes to Sub-processors

The Processor shall maintain a list of all Sub-processors and shall notify the Controller of any intended changes at least thirty (30) days in advance. The Controller has the right to object on reasonable written grounds related to data protection.
Legal Liability

The Processor remains fully liable to the Controller for the performance of the Sub-processor's obligations. A public, up-to-date list of all Sub-processors is maintained for transparency.

Article 3

Security Measures

We implement robust technical and organizational measures (TOMs) as required by Article 32 of the GDPR:

  • AES-256 Encryption

    Encryption at rest and TLS 1.3 in transit.

  • PostgreSQL RLS

    Mathematical tenant data isolation.

  • Pseudonymisation

    Automated data minimization controls.

  • System Resilience

    Ongoing integrity and availability monitoring.

3.1 Audits and Certifications

The Processor shall make available all information necessary to demonstrate compliance and allow for audits or inspections conducted by the Controller or a mandated auditor, subject to reasonable notice and confidentiality.
Audit Procedure

Common practice includes a limit on audit frequency (typically once per year) and 30 days' notice using a mutually agreed-upon independent auditor.

Article 4

Incident Response

In the highly unlikely event of a Personal Data Breach, we will notify the Controller without undue delay after becoming aware of the incident.

Target: Notification within 48 hours

We provide the nature of the breach, contact points, likely consequences, and proposed mitigation measures to help you meet your regulatory obligations under Articles 33 and 34 of the GDPR.

Regulatory Speed

Since the Controller must notify the Supervisory Authority within 72 hours, the Processor's 48-hour target is critical for overall compliance success.