Engineering
·
8 min read
Where your data goes when a flow runs
A plain-language tour of what Wordloom stores, what it sends to your tools, and the controls admins get to keep it that way.
Jonas Feld
Security Engineer
Three places, nothing more
A run touches three places: your workspace, where the request and plan live; the approval step, where rules and roles are checked; and the tools an admin has connected.
In your workspace
Requests, plans and results are stored in your workspace region and kept only as long as your retention policy says. They are never shared with other customers and never used to train models.
On the way to your tools
Every call goes over TLS 1.2+ with the permissions of the person who asked. If they cannot do something by hand, Wordloom cannot do it for them.
What admins control
Which tools are connected, which steps need approval, who can build or run flows, and how long history is kept. All of it is visible in the action log.
This article describes a fictional product. Replace it with your own architecture before you publish.
Write it once. It runs.
Try Wordloom with your team for 14 days, no card needed.