Skip to main content

Compliance

GDPR and Data Processing

Agent workflows often process personal data. We design them around data minimisation, agreed retention and clear processing roles, documented before launch.

Conceptual data handling: selected fragments move from a document tray into a container, past a retention hourglass and a region marker, to a checked record.

What we agree with you

Recorded in the project documentation and your data processing terms.

Processing roles

Who is controller and processor, and which sub-processors are involved.

Data minimisation

Only the personal data the workflow needs is collected and passed on.

Retention

How long transcripts, documents and logs are kept, and how they are deleted.

Data protection in the project

Built into scoping rather than added at the end.

01

Map the data

Identify personal data in inputs, records and logs.

02

Agree terms

Set roles, sub-processors and transfers.

03

Configure

Apply minimisation, access and retention.

04

Support rights

Agree how access and deletion requests are handled.

Questions we answer before launch

So your data protection lead can review the workflow.

  • Which personal data is processed and why.
  • Where it is processed and by which providers.
  • How long it is kept and who can access it.

Common questions

Data processing terms are agreed as part of the engagement. Ask us for the current documentation.

This depends on the providers selected for the project, and is disclosed and agreed before launch.

Discovery call

Start with the work that slows you down.

Bring us a process, a recurring enquiry or a pile of documents. We will explore where agents fit and what a useful implementation needs.

Book a discovery call