Your datastays yours.
Updated: August 2026
When I run a Managed Loop for you, I work with your systems and data. I take that seriously, so here is plainly how I handle it, where it flows and what never happens to it. No compliance badges on the wall, just the concrete practices of one person you can reach directly.
- Your data stays in your systems. I access only what's needed and you can revoke access anytime.
- Sensitive values are swapped for placeholders before anything goes to the cloud, so the AI vendor never sees them.
- Nothing is trained on or stored. The AI vendor runs in a zero-data-retention mode.
- I never sell your data or use it for anyone but you.
A small deliberate stack, direct accountability
I'm not a large company with layers of process, I'm one person who builds the loop, connects it and runs it. That means I know exactly where your data sits and who can reach it, while you get a single accountable human you can call at any time. The advantage isn't a badge on a wall, it's transparency and the fact that you can pull access in minutes.
Access only to what's needed
The loop gets only the permissions it genuinely needs for its job. If reading is enough it doesn't get write access, and if one folder is enough it doesn't see the whole inbox.
Your data stays yours
Data keeps living in your tools and the loop only works with it. I don't sell it, hand it to third parties or use it for anyone but you.
A small deliberate stack
The chain has only a few proven tools and I can name every one of them. Fewer parts means fewer places where something can go wrong.
Revoke access anytime
The master account for each service stays yours. When we finish, you remove access and rotate keys and it's done, I hold no data hostage.
The least privilege that gets the job done
I access each of your services through an account or token created just for that loop, never through your personal login. Where possible I use OAuth and scoped tokens limited to what's needed, which means one specific access can be revoked without affecting anything else.
I set up separate accounts and keys per client and never reuse one access across customers.
Tokens carry only the scope the loop needs, with time-limited validity where the service allows it.
The master account for each platform stays yours, I work under an invited access you can see and manage.
Access is revocable from your side at any time, you don't have to wait on me.
The loop doesn't move your data over to me. It reads only what it needs, sends it for a judgment and writes the result back where it belongs. Here's that path step by step.
Your systems
CRM, inbox, invoicing or spreadsheets. Data stays here as the source of truth.
Automation (n8n / Railway)
Through a scoped token the loop takes only the data a step needs.
Sensitive-data redaction
Before anything goes to the cloud, sensitive values like names, IBANs or amounts are swapped for placeholders.
AI model
It only gets the placeholders, never the real data. It judges the content and returns a proposal or decision.
Target system
Placeholders are swapped back to real values locally and the result is written into your tool, for approval or straight on.
None of this is a black box. These are the services that may take part in running a loop, along with what data they see and whether they train models on it. The exact set depends on what the loop does, and we go through it upfront.
| Subprocessor | Purpose | What data it sees | Location | Trains on data? | DPA |
|---|---|---|---|---|---|
| Vercel | Hosting the site and automations | Operational data passing through the loop | EU / US | No | Yes |
| Anthropic (Claude) | AI judgment inside loops | Content you send into the loop | US | No (commercial terms) | Yes |
| Railway (n8n) | Running loop workflows | Data the workflow processes | EU / US | No | Yes |
| HubSpot | CRM | Contacts and deals | EU / US | No | Yes |
| Email / IMAP | Reading and drafting messages | Messages relevant to the loop | Per provider | No | Per provider |
| Fakturoid | Invoicing | Invoices and client details | EU | No | Yes |
The table is honest about what it doesn't promise too. If a loop uses none of these services, they're not in its chain. I won't add a new service to the chain without telling you.
Encrypted in transit, protected at rest
Communication between your systems, the loop and the subprocessors runs over encrypted transport (TLS/HTTPS), so nobody reads data on the way. At rest, encryption is handled by the platforms the loop runs on, the same infrastructure your other cloud tools already rely on.
Keys belong in a vault, not an email
I keep credentials and API keys in an encrypted store and environment variables, never hardcoded in code, chat or email. Loop code lives in private repositories and keys can be rotated when needed.
- Secrets in an encrypted store and environment variables, not in code.
- I never send you keys in plain email or chat, I use a secure hand-off channel.
- The repositories holding the loops are private.
- Keys can be rotated, and on exit you rotate them anyway.
The device I run it from is secured
I operate loops from a work device with disk encryption, a password manager with unique passwords, two-factor authentication on key accounts and regular updates. It's basic hygiene, but real-world security often stands or falls on exactly this.
One person, but no single point of failure for your data
The operation runs on one person, and it's fair to spell out what that means when I'm not reachable. The key point is that my unavailability never locks you out of your data, because the source of truth and the master accounts stay with you the whole time.
The master account for each service is yours, so even if I dropped off you keep access to your systems and data without me.
The loop runs on managed infrastructure (Vercel, Railway), not on my laptop, so a short absence doesn't stop it.
For every loop I hand over documentation of how it works and where it runs, so someone else could take it over.
You can remove the invited access and rotate keys yourself at any time, without waiting on me.
Some boundaries are fixed regardless of the project.
- I never sell or share your data with third parties.
- I never train AI models on your data, and I run the AI vendor in a zero-data-retention mode.
- I never keep access or copies of your data after a project ends.
- I never store credentials in plaintext in code, chat or email.
- I never use one client's data for another.
Incident handling and responsible disclosure
If a security incident touched your data, I'd notify the affected client without undue delay, with what happened and what I'm doing about it. Where personal data under GDPR is involved, I work within the 72-hour notification framing. If you find a vulnerability or something suspicious, email me and I'll acknowledge it, typically within one business day.
I act as a processor of your data
When running a loop I process personal data on your instructions, so I act as the processor and you are the controller. A data processing agreement (DPA) is available on request and I'm happy to go through your company's specific requirements. How I handle data on this website is described on the privacy page.
01Do you send our sensitive data to the cloud?
Not in readable form. On loops that touch sensitive data a redaction layer swaps values like names, IBANs or amounts for placeholders before anything is sent. The AI vendor only gets the placeholders; real values are put back locally after the answer. On top of that the vendor runs in a zero-data-retention mode, so it doesn't even store the placeholders.
02Do you hold SOC 2 or ISO 27001?
No, and I won't pretend otherwise. I'm one person, not a large firm with an audit team, so I don't have those certifications. What I offer instead of a stamp is transparency, a small named stack and access you can revoke at any time.
03Is AI trained on or stored from our data?
No. On top of that I run the AI vendor in a zero-data-retention mode, so the content you send into the loop isn't used to train models and isn't retained by the vendor either.
04Where exactly does our data sit?
Operational data is processed on managed cloud infrastructure in the EU and US, depending on which services a given loop uses. I'll tell you the exact set for your loop upfront, and you'll also find it in the subprocessor table above.
05What happens to access when we stop working together?
You remove the invited access, rotate keys and tokens, and I keep no data or access. Your systems stay the source of truth, so once the loop is disconnected you still have everything in your CRM, inbox and invoicing.