Skip to contentRunlog 2.4: parallel tool calls and step replays
runlog_
Theme
Log inStart building ->

All systems normal

[legal] dpa

Data Processing Addendum

How Runlog processes personal data inside your runs on your behalf, as required by the GDPR and similar laws.

Last updated

Template text. This page is sample content for the Runlog theme. Replace it with a DPA written or reviewed by your own lawyer before you launch.

Scope and roles

This Data Processing Addendum (“DPA”) is part of the Terms of Service. It applies when Runlog processes personal data inside Customer Content on your behalf. You are the controller of that data, and Runlog is the processor.

Processing details

Item Details
Subject matter Hosting and running AI agent steps, storing run logs and replays
Duration For as long as you use the Service, plus the deletion period below
Nature and purpose Storage, retrieval, transmission to the model and tool providers you configure, display in the dashboard
Types of personal data Any personal data you include in prompts, tool calls, outputs and logs
Data subjects Your users, employees and other people whose data you send through the Service

Our obligations

Runlog will:

  1. Process personal data only on your documented instructions, including these terms and your settings in the dashboard.
  2. Make sure staff with access are bound by confidentiality.
  3. Help you answer requests from data subjects and carry out impact assessments, where it relates to the Service.
  4. Tell you if we believe an instruction breaks data protection law.

Subprocessors

You give general authorization for Runlog to use the subprocessors below. We will announce new subprocessors on this page and by email 30 days in advance. You can object on reasonable grounds; if we cannot resolve the objection, you may end the affected part of the Service.

Subprocessor Purpose Location
Example Cloud Hosting and storage EU, US
Example Payments Billing US
Example Mail Transactional email EU
Example Support Support inbox US

Security measures

  • Encryption in transit (TLS 1.2+) and at rest (AES-256).
  • Single sign-on and hardware keys for all production access, with access logs kept for one year.
  • Separate environments for development and production, and code review for every change.
  • Daily encrypted backups, tested every quarter.
  • Yearly penetration test by an independent firm.

Personal data breaches

We will tell you without undue delay, and in any case within 48 hours, after we become aware of a breach affecting your personal data. We will share what we know, what we are doing about it and who you can contact.

International transfers

Where personal data moves outside the EEA or the UK, the Standard Contractual Clauses (module two, controller to processor) apply and are made part of this DPA by reference.

Audits

Once a year, or after a breach, you may ask for an audit. We will first answer with our latest security report and questionnaire. If that is not enough, an independent auditor bound by confidentiality may run an audit with 30 days notice, at your cost.

Deletion and return

When the agreement ends, you can export your data for 30 days. After that we delete Customer Content within 30 days, unless the law requires us to keep it.

Contact

Data protection questions: privacy@example.com.

Buy this template$79Theme by Pavlo Zhydkykh