Security and privacy
We take security and privacy seriously, and we would rather show you the control than talk about it.
We run a workflow your team depends on, so you need to know what we hold, how it is protected and who else is in the path. Your systems stay the system of record. Where something is still being built, the status below says so.
Compliance
We build the evidence as the platform runs, not the month before an audit.
We are working toward SOC 2 Type II, and the controls listed here are the ones in scope for it. Until the report exists we will not cite it.
- SOC 2 Type IIThe workflow engine, the run log and the hosting that carries themIn progress
- GDPRData processing agreement, with transfer terms where a workflow needs themOn request
- Penetration testAnnual test by an outside firm, summary available to your reviewerPlanned
Security practices
Every hop is encrypted, every access is named, and a run that cannot finish stops.
Encryption
Encrypted in transit and at rest, on every hop a run takes.
Every workspace has a key of its own. Credentials for your systems and the data a run produces are encrypted with it before they reach the database or the file store, and nobody sees a secret again after it is saved. The key is itself held encrypted under the application key, is rotated about every thirty days or sooner on request, for one workspace alone, and is destroyed with the workspace. How the key works, in the guide.
Each credential belongs to a group in your workspace, and the people who manage it can replace the secret at any time, with every change logged.
Network and access
The engine runs on Laravel Cloud, on managed AWS infrastructure in a private network. Nothing that carries your data is reachable from the open internet.
Least privilege, and named. The engineers on your workflow have access, nobody carries it standing, and every access is logged.
A step reaches only the systems and fields written into it. Outbound calls go to a named list, not wherever a run decides to go.
Vulnerability management
Dependencies and images are scanned on every build, and patched on a clock: critical findings first, the rest on the next release.
An annual third-party penetration test, plus a review of the workflow logic itself before anything new goes live.
Report something to security@vectorfrank.com. You get an acknowledgement from a person, not a queue.
If something goes wrong
A run that cannot finish holds and says why. It never writes half a record, and the queue keeps its place.
Your named contact hears what we know, which runs are affected and what your team should do meanwhile. Then a written account: cause, affected runs, the fix, and the control we added.
Your data
Your systems stay the system of record.
Data governance
We hold the records and fields a workflow needs to operate, and nothing it does not need.
Your data runs your workflow. It is not pooled with another customer's, and it is not used to train or build anything we sell elsewhere.
Every input, decision and write is logged in order, per run. Your team reads the same log we do, and keeps it on the way out.
Residency and retention
Run data stays in the United States. The engine runs in a US region on Laravel Cloud, and every subprocessor in the path of a run is US-based too. The one exception is OpenRouter, which passes a request on to the model's own provider, and that provider can be outside the US. A workflow that has to keep its data in the country calls Anthropic or OpenAI directly instead.
If your work needs data held outside the US, tell us before we build it rather than after. We would rather say no at the start than move a workflow later.
What we store is kept for the window we agree, then deleted. Export and deletion on request.
Subprocessors
Everyone in the path of a run, named below. Where a step in your workflow calls a service specific to your work, that one is named in your workflow record too. You get notice before either list changes.
This is the path a run takes. The providers behind this website and our booking process are a separate list, in the privacy policy.
- Laravel Cloud
Runs the workflow engine and its database: the run log and the encrypted credentials for your systems
What it can touch Run data and encrypted credentials at rest
Region United States
- Anthropic
Called by the step where judgment is hard, where a workflow has one
What it can touch Only the fields that step needs, per case
Region United States
- OpenAI
Called by the step where judgment is hard, where a workflow has one
What it can touch Only the fields that step needs, per case
Region United States
- OpenRouter
Called by the step where judgment is hard, where a workflow uses a model from another provider
What it can touch Only the fields that step needs, per case
Region United States, then the model's own provider
- TypeSafe
Called by the step that sorts cases or makes a yes-or-no call, where a workflow has one
What it can touch Only the fields that step reads, per case
Region United States
- Sentry
Alerts us when a queue stalls or a run fails
What it can touch Operational metrics and error traces, no record contents
Region United States
Notice given before this list changes
Anything your review needs that is not here, ask.
Your engagement lead can walk your team through the controls and open the log from a workflow already in production. This page covers the data inside a workflow we run for you; what we collect when you browse this site or book an audit is in the privacy policy.