Data Processing Agreement

Effective November 12, 2026 · Last updated November 12, 2026

This Data Processing Agreement (“DPA”) forms part of the Terms of Service between Runledge, Inc. (“Runledge”) and the Customer. It applies when Runledge processes Customer Data on the Customer’s behalf. If this DPA conflicts with the Terms, this DPA controls for Customer Data; a signed Enterprise agreement controls over both.

01Definitions

  • Customer Data means workspace policies, approval proposals, action metadata and reported outcomes the Customer submits to the Service, including any personal data in them.
  • Account Data means names, work emails, billing details and usage counts needed to run the account. Runledge is the controller of Account Data, and the Privacy Policy governs it, not this DPA.
  • Data Protection Laws means the privacy and data protection laws that apply to the processing, including the GDPR and UK GDPR where applicable.
  • Sub-processor means a third party Runledge engages to process Customer Data.

02Roles and scope

The Customer is the controller of Customer Data and Runledge is its processor. Runledge processes Customer Data only to provide the Service: evaluating proposed agent actions against the Customer’s rules, routing approvals, issuing receipts, producing reports and exports, and, if the Customer configures it, calling a provider through the credential broker.

  • Duration: the term of the Terms, plus the deletion period in “Return and deletion”.
  • Data subjects: the Customer’s users, reviewers and any individuals whose data the Customer includes in action metadata.
  • Categories of data: identifiers and work contact details of users and reviewers, and whatever fields the Customer chooses to submit in proposals. The Customer should not submit special-category data or provider secrets in action metadata.

Customer-hosted deployments the Customer operates are outside this DPA, because Runledge does not process their data.

03Customer instructions

Runledge processes Customer Data only on the Customer’s documented instructions. The Terms, this DPA and the Customer’s configuration of the Service are those instructions. Runledge will tell the Customer if it believes an instruction violates Data Protection Laws, and will not train or fine-tune a model on Customer Data.

04Personnel

Runledge gives access to Customer Data only to personnel who need it to provide or support the Service and who are bound by confidentiality obligations.

05Security measures

Runledge maintains the following technical and organisational measures:

  • encryption in transit with TLS, and at rest by the hosting provider;
  • row-level workspace isolation in the database, so each workspace can read only its own records;
  • API keys stored as hashes, and broker credentials and webhook secrets stored encrypted and restricted to service operations;
  • role-based workspace permissions and audit records of administrative changes.

Runledge does not currently hold SOC 2, ISO/IEC 27001 or HIPAA certifications.

06Sub-processors

The Customer authorises Runledge to use the sub-processors listed below. Runledge binds each one to data protection terms at least as protective as this DPA and remains responsible for their performance. Runledge will notify the Customer of a new sub-processor before it processes Customer Data; the Customer may object on reasonable data protection grounds, and if the parties cannot resolve the objection, the Customer may terminate the affected Service.

The services listed under Sub-processors are identified from the current integration; this is not an exhaustive, contract-approved subprocessor register. Legal operator names and entities, processing regions, downstream providers, provider-specific retention and deletion timelines, and change-notice terms still need confirmation.

Retention schedule
Actions, metadata, policies, approvals and receipts
Persisted; no automatic expiry is configured. Deletion requests are reviewed by Runledge.
AI guidance and saved findings
Persisted in the workspace. Dismissing a finding does not delete it.
API-key hashes and audit history
Revocation or expiry disables access; it does not delete historical records.
AI provider processing
Model requests set store: false. Provider logging, retention and training terms still require confirmation; this is not a zero-retention guarantee.
Backups, infrastructure logs, billing and email records
Provider-specific periods and deletion timelines are not yet published. Confirm requirements before submitting regulated data.

07International transfers

Where Customer Data is transferred out of the EEA, UK or Switzerland to a country without an adequacy decision, the parties rely on the European Commission’s Standard Contractual Clauses (Module 2, controller to processor) and the UK Addendum, which are incorporated by reference.

08Security incidents

Runledge will notify the Customer without undue delay after becoming aware of a breach affecting Customer Data. The notice will describe what happened, the data affected, and the steps taken, and Runledge will provide further information as it becomes available.

09Assistance

Taking into account the nature of the processing, Runledge will help the Customer respond to data subject requests, and with data protection impact assessments and regulator consultations about the Service. Authorised workspace users can export audit records and policies themselves.

10Return and deletion

During the term, the Customer can export Customer Data from the console. When the Terms end, or on written request, Runledge will delete Customer Data, except where law requires it to be kept. The Service does not yet provide automated, verified deletion within a fixed period; deletion is handled on request to contact@runledge.com, and Runledge will confirm when it is complete.

11Audits

Runledge will make available the information reasonably needed to demonstrate compliance with this DPA. Because Runledge has no third-party certification yet, the Customer may request a written questionnaire response, or, where Data Protection Laws require it, an audit on reasonable notice, during business hours, no more than once a year, and under confidentiality.

12Signing

This DPA applies automatically under the Terms. To sign a countersigned copy, email contact@runledge.com with your company name and signatory.

Ready to let your agents act safely?

Start free