Agreements

Data processing addendum

The terms on which we process personal data on the Customer’s behalf. It forms part of the terms of service and meets Article 28 of the GDPR and UK GDPR.

Version
1.4
Effective
30 October 2026
Last updated
8 November 2026
  1. 1.Scope and roles

    1.1

    This data processing addendum ("DPA") applies when Rykon Technologies Inc. ("Processor") processes Personal Data in Customer Data on behalf of the Customer ("Controller") in providing Rykon AI. Terms defined in the terms of service have the same meaning here.

    1.2

    For Account Data, we act as an independent Controller under our privacy policy, and this DPA does not apply to it.

    1.3

    Where the CCPA applies, we act as the Customer’s service provider: we do not sell or share Customer Data, retain, use or disclose it outside the direct business relationship with the Customer or for any purpose other than providing the service, or combine it with personal information from other sources except as the CCPA permits.

  2. 2.Details of the processing

    Subject matter and nature
    Running AI agents on tasks the Customer gives: sending the task and its material to AI models, executing approved tool calls, and storing transcripts, results, approvals and the record.
    Purpose
    Providing, securing and supporting the service as the Customer configures and uses it.
    Categories of Data Subjects
    The Customer’s staff and Users, and any person whose data the Customer puts into a task, a brief or material an agent works on.
    Categories of Personal Data
    Whatever the Customer chooses to put into tasks and briefs, and what runs produce from it; names and email addresses of Users in approvals and the record.
    Special categories
    None intended. The Customer should not put special category data into tasks unless it has a lawful basis and has assessed the risk.
    Duration
    The term of the Customer’s account, then deletion under clause 10.
  3. 3.Processing on instructions

    3.1

    We process Customer Data only on the Customer’s documented instructions, which are the Terms, this DPA and the Customer’s use and configuration of the service (its tasks, agents, levels and approvals), unless the law requires otherwise, in which case we tell the Customer first unless the law prohibits it. We tell the Customer if we believe an instruction infringes data protection law.

    3.2

    We do not use Customer Data for advertising or to train artificial intelligence models.

  4. 4.Confidentiality

    4.1

    We limit access to Customer Data to personnel who need it to run and support the service and who are bound by confidentiality.

  5. 5.Security measures

    5.1

    We maintain technical and organisational measures appropriate to the risk, as described on our security page, including:

    • runs answered directly in our control plane, which runs no code the model provides, and any work that needs code, a shell, files or packages in a fresh sandbox of its own, removed after it: read-only root, no capabilities, resource limits, a deadline, and a network that reaches only our relay;
    • for sandbox work, a run credential that works only for that run, while it runs, from its own sandbox address;
    • the account’s AI gateway key sealed with AES-256-GCM and opened only for one model call at a time, by the relay or the control plane, never placed in a sandbox; API keys stored only as SHA-256 hashes;
    • every request scoped to one account, with attempts to reach another account’s data refused and recorded;
    • actions above an agent’s level held for a person, and the highest risk class always held;
    • append-only records of what agents did and of changes to the account, with keys and tokens redacted;
    • encrypted offsite database backups, and a monthly restore test of the database cluster.
    5.2

    We may update these measures, provided we do not lower the overall level of protection.

  6. 6.Subprocessors

    6.1

    The Customer gives general authorisation for the subprocessors listed on our subprocessors page. We impose on each, by written contract, data protection obligations no less protective than this DPA, and remain responsible for their performance.

    6.2

    We give at least 30 days’ notice of a new or replacement subprocessor on that page and by email. The Customer may object on reasonable data protection grounds within that period; if we cannot address the objection, the Customer may end the affected service and receive a refund of prepaid fees for the unused period.

  7. 7.International transfers

    7.1

    Customer Data is currently stored in Germany, and in any further region listed on the subprocessors page before it holds Customer Data. Model calls are processed by Anthropic, or OpenAI as a fallback, in the United States; the voice of Mission Control, which an owner or admin may turn off, is processed by OpenAI in the United States. Transfers of Personal Data from the EEA, the United Kingdom or Switzerland to a country without an adequacy decision are made under the European Commission’s Standard Contractual Clauses (Module 3, processor to processor, with each subprocessor), with the UK International Data Transfer Addendum where UK data is concerned, or under the EU-US Data Privacy Framework where the recipient is certified.

  8. 8.Assistance

    8.1

    Taking into account the nature of the processing, we help the Customer respond to Data Subject requests, through the console and the API, which show the Customer its runs, transcripts and approvals, and on request. If we receive a request directly, we pass it to the Customer without undue delay and do not answer it ourselves except to say we have done so.

    8.2

    We give reasonable help with data protection impact assessments, prior consultations and the Customer’s security obligations.

  9. 9.Personal data breaches

    9.1

    We notify the Customer without undue delay, and in any event within 72 hours, after becoming aware of a Personal Data Breach affecting Customer Data. The notice describes, as far as then known, the nature of the breach, the categories and approximate number of Data Subjects and records concerned, the likely consequences, and the measures taken or proposed; we supplement it as we learn more. We take reasonable steps to contain and remedy the breach.

  10. 10.Deletion and return

    10.1

    While the account is open, the Customer can read its Customer Data in the console and through the API, and its owners and admins can download all of it in one archive (Settings, Your data, or GET /v1/tenant/export).

    10.2

    When an owner closes the account, nothing is deleted for 7 days and the closing can be withdrawn. Then every credential the account holds is revoked and Customer Data is deleted from the live service. The audit log and the record keep their entries, reduced to what happened and when, with no personal data or content, so their integrity can still be proven. Customer Data leaves our encrypted backups as they rotate out, within four months, unless the law requires us to keep it. The periods are in our privacy policy.

  11. 11.Information and audits

    11.1

    We make available the information reasonably needed to demonstrate compliance with this DPA, including written answers to security questionnaires. Where that is not sufficient, the Customer may audit our compliance once a year, on 30 days’ notice, during business hours, under confidentiality, and at its own cost, or by an independent auditor bound by confidentiality.

  12. 12.Contact

    12.1

    Data protection questions: support@rykon.ai, subject "Privacy request".

Change log

  1. Version 1.4
    8 November 2026

    The voice of Mission Control is processed by OpenAI, a listed subprocessor, unless an owner or admin turns it off.

  2. Version 1.3
    5 November 2026

    Deletion and return: the export, the 7 day closing and what the logs keep.

  3. Version 1.2
    1 November 2026

    Security measures now describe direct answers in our control plane, sandboxes for code, shell and file work, and the gateway key opened for one call at a time by the relay or the control plane.

  4. Version 1.1
    31 October 2026

    Customer Data location stated as the current region, with any further region listed on the subprocessors page before it holds Customer Data.

  5. Version 1.0
    30 October 2026

    First published.

Data processing addendum · Rykon AI