ServicesGoverned workflow automation
Automation that moves only the data it needs
Every time an automation copies data, personal data can end up somewhere unplanned. We build automations that move only what each system needs, stay in approved systems and regions, and log every run.
- Field-level data minimisation
- Self-hosted where required
- A log of every run
How we build them
So an automation doesn't become a data leak.
Field-level minimisation
Each step receives only the fields the next system needs. The billing tool doesn't get the ID scan.
Approved systems and regions
Data moves only between systems on your approved list, in the regions they're approved for.
Secrets in a vault
API keys and passwords held in a secrets manager, not pasted into workflow tools, and rotated on a schedule.
Self-hosted when needed
Where a hosted automation platform isn't acceptable, workflows run in your own cloud, on a self-hosted orchestrator or as plain code.
No stray copies
Execution history in intermediate tools is trimmed so personal data doesn't build up where nobody looks.
Run logs and alerts
Every run recorded by step and field name, with alerts when something fails, so errors don't fail silently.
Only the fields each system needs
source
in your environment
GDPR Art. 5(1)(c)
destinations
Field-level minimisation: each destination is given a list of the fields it may receive, and the run log records field names, never values.
Typical workflows
Fixed rules, no guesswork. When an input is messy enough to need judgement, that step becomes an agent with its own limits.
Intake and onboarding
Forms, signatures and documents turned into records in the right systems, with the originals kept in one place.
Billing and payments
Invoices raised when work closes, payment links sent, and books updated, with card data handled only by the payment provider.
Reporting
Weekly and monthly numbers built from your systems, aggregated so the report doesn't carry personal data.
Deletion requests
A data subject's deletion request carried out across every connected system, with a record that it was done.
In production
An 8-truck plumbing company in Newark ran its customers out of a shared spreadsheet. Now quotes, invoices and payments move through a CRM with roles, and card payments go through hosted links.
Questions
Do you use Zapier, Make or n8n?
Yes, along with many other platforms, where they fit your data rules. If a hosted platform isn't acceptable, we self-host or write the workflow as code you own.
What happens when a step fails?
It retries where that's safe, then alerts a named person with the run details. Nothing fails silently.
Can you automate deletion and access requests?
Yes. Finding and deleting a person's data across connected systems is one of the most useful automations for a privacy team, and the run log becomes your record that it was done.