Security & data handling
How FlowState Studio treats your data, what it connects to, how every run is evidenced, how your administrators control it, and the limits we know about. Written so your security review can be done from this page.
1Network access
FlowState sends no telemetry and has no server of ours to talk to. The product contains exactly one module that connects off the PC, the optional AI connector, and the test suite fails the build if any other networking code appears.
| Connection | When | To where |
|---|---|---|
| Telemetry, updates, licence checks | Never. Licence keys are verified offline with a public key built into the program. | — |
| AI assistant / Ask AI steps | Only if a user adds an API key (their own, or the OpenRouter key with included credits that we supply) and uses them; can be forbidden by policy. | The provider the user names (Anthropic, OpenRouter, OpenAI, or an address of your own such as Azure or an internal model), over HTTPS only. Policy can restrict the allowed addresses. |
| Browser steps | Only in flows that use them; can be forbidden by policy. | 127.0.0.1 only: FlowState controls the Edge or Chrome it started on the same PC. |
Programs FlowState drives keep their own connections. When a flow works in a browser, Outlook, SAP GUI, a terminal emulator or a database (through ODBC), those programs use the network exactly as they do when a person uses them. FlowState doesn't add connections of its own. CyberArk passwords are read through CyberArk's Credential Provider on the PC; FlowState opens no connection to the vault itself.
2What stays on the PC, and where
Everything FlowState creates is stored on the PC (or a folder you choose). Nothing is uploaded.
| What | Where |
|---|---|
| The program | %LOCALAPPDATA%\Programs\Automater, for the signed-in user |
| Flows and their pictures | Wherever the user saves the flow (.json), with an assets folder beside it |
| Run logs, screenshots, evidence | A dated folder under runs beside the flow |
| Approvals and decisions | decisions.jsonl beside the flows (append-only, hash-chained) |
| Stored passwords | Windows Credential Manager, encrypted by Windows for the signed-in user |
| Machine policy | %PROGRAMDATA%\Automater\policy.json, set by an administrator |
| Preferences, licence key | %APPDATA%\Automater |
| AI conversation record (if AI is used) | An assistant_log folder beside the flow: everything sent and received, hash-chained |
| AI "lessons" (if AI is used) | %APPDATA%\Automater\lessons; long numbers, email addresses and the user folder are masked first; can be turned off |
| Browser profile for browser steps | Temporary and deleted when the browser closes, unless a flow asks to keep logins (%LOCALAPPDATA%\Automater\browser-profile) |
Screen reading (OCR), PDF pages and pictures are handled by the engines built into Windows, on the device. Optional extra OCR engines (Tesseract, RapidOCR) are installed as packs whose every file is checked against a SHA-256 list.
3Audit trail and evidence
Every run writes a tamper-evident log
- Each run gets its own folder with
run.jsonl(one record per event), a seal and the screenshots taken as evidence. - The first record states who ran which version of the flow (its SHA-256) on which machine, under which policy and approval state. Every step records its arguments, result, duration and outcome.
- Records are hash-chained and screenshots are pinned by hash, so
automater verifydetects an edited, removed, inserted or reordered record, a cut-off log, and an altered or missing screenshot. - Keyed mode: with
AUTOMATER_AUDIT_KEYset, the chain is an HMAC, so only a key holder can produce or verify a valid log. - Wherever a password or other secret would appear in a log, it is written as
***.
Evidence packs for auditors
One .zip per run, made with automater evidence <run folder>. It contains the run log, seal and screenshots, the flow and its code files, the approvals ledger, and a manifest. The manifest gives the outcome, the policy in force, the approval state and the SHA-256 of every input document the run read. It can be signed with your organisation's certificate (standard CMS/PKCS #7, SHA-256), which verifies with OpenSSL or Windows.
Each pack includes verify_evidence.py, a short checker that uses only Python's standard library, so an auditor can verify it without installing FlowState. Altering any screenshot, log line, ledger record or the manifest, or adding or removing a file, makes it fail.
Maker-checker approval
A flow version can be submitted by its author and approved or rejected by a different Windows user. Approval covers the flow's fingerprint: the flow, every code file it can run, the flows it uses and the pictures it searches for. Any change withdraws the approval. The approver is identified by asking Windows, not by a user-editable variable. With "require_maker_checker": true in the machine policy, an unapproved version does not run.
4Administrator control (machine policy)
An administrator places one file, %PROGRAMDATA%\Automater\policy.json. Every run log records the rules in force. A policy file that cannot be understood stops everything until it is fixed, and environment variables can only tighten the policy, never loosen it.
{
"allow_python": false,
"allow_commands": false,
"allow_email": false,
"allow_browser": false,
"allow_ai": false,
"allow_recording": false,
"require_log": true,
"require_approved_flows": true,
"require_maker_checker": true,
"approved_flows": {"951fdf45…a63": "Month-end posting v3, approved 2026-11-02"}
}
| Setting | Effect |
|---|---|
allow_python: false | No Python steps, custom actions or exported scripts; flows using them are refused when loaded |
allow_commands: false | No running commands, PowerShell or Excel macros |
allow_email: false | No sending email through Outlook |
allow_browser: false | No browser steps |
allow_ai: false | The AI assistant is off and nothing is sent; ai_in_flows: false stops only Ask AI steps in running flows; ai_endpoints limits where AI may connect; ai_may_see caps what it may be shown |
ocr_engines | Only the listed OCR engines may be used |
allow_recording: false | The task recorder is unavailable |
require_log: true | Every run must write its tamper-evident log |
require_approved_flows: true | Only flows whose fingerprint is listed may run |
require_maker_checker: true | A flow version must be approved by a second person before it runs |
automater policy shows the rules in force on a PC, and automater fingerprint flow.json prints a flow's fingerprint for the approved list.
5Passwords and credentials
- Flows never contain passwords. They name a secret, and its value comes at run time from Windows Credential Manager (encrypted by Windows for the signed-in user), an environment variable, or a prompt that doesn't echo.
- Anything typed into a password box while recording is never stored; that step becomes "type a secret", supplied at run time.
- FlowState never reads the contents of password boxes when inspecting the screen.
- An unattended (scheduled) run with a missing secret fails immediately rather than waiting.
- CyberArk credentials can be fetched through CyberArk's own Credential Provider on the PC.
6The AI assistant
FlowState works fully without AI. The assistant only runs if a user adds an API key (stored in Windows Credential Manager), and an administrator can forbid it on a PC with allow_ai: false.
- What it does: it writes or repairs a flow from a plain-language description. It cannot run anything; every proposed change must be accepted by the user.
- What is sent by default: only what the user types, the list of available actions and the flow being written. No screen contents, no file contents, no secret values.
- Ask AI steps (a running flow asking a model a question) are off by default at three levels: per flow, per assistant conversation, and by policy. Secrets are masked before anything is sent, and each exchange is recorded in the run folder.
- Every conversation is recorded on the PC (
assistant_log), hash-chained, so you can review exactly what was sent. The API key is never in the record. - The included AI credits ($100 (about ₹9,500) with every licence) come as an OpenRouter key on our OpenRouter account. Requests still go straight from your PC to OpenRouter, never through us, but the usage on that key (which model, how many tokens, the cost) shows in our account. To keep even that private, use your own key instead, or forbid AI by policy.
| "The assistant may see" | What leaves the PC |
|---|---|
| Nothing (default) | Only what the user types |
| Window titles and control names | Titles of open windows and the labels of their controls. Never what is typed in them. Note: a label can itself contain data (e.g. "Balance: 1,250,000") |
| Also pictures of a window | As above, plus a picture of one window, only after the user has seen it and pressed OK |
7Installation, components and integrity
- Per-user install, no administrator rights. The setup program installs to
%LOCALAPPDATA%\Programs\Automaterwith Start menu shortcuts; nothing system-wide changes. Scheduled runs are ordinary Task Scheduler tasks in an\Automaterfolder that run only while the user is logged on. - Few components. The official python.org runtime (unmodified, still carrying the Python Software Foundation's signatures), NumPy, and FlowState's own code. Screen capture, input, OCR, PDF and UI Automation use Windows' own APIs.
automater licenceslists every component with its licence. - Integrity checks. Every installed file is listed with its SHA-256 in a manifest; the installer verifies it, and
automater verify-installre-checks it at any time. The setup program's own SHA-256 is published on the download page. - Licence keys are Ed25519 signatures over the customer's name, a key id and the dates. They are checked offline against a public key built into the program.
- Safety stops. A global hotkey (
Ctrl+Alt+Q) stops any run within a fraction of a second, and moving the mouse to the screen's top-left corner aborts.
8Known limitations
We list these so your review doesn't have to find them.
AUTOMATER_AUDIT_KEY), keep the seal elsewhere, restrict folder permissions, and export evidence packs.9What our website collects
The product sends us nothing. The website (solutionandnetwork.com) handles only:
- Free trial keys: the name and the phone number or email the visitor enters, the key issued and its dates. To limit abuse we keep a keyed hash of the visitor's IP address, never the address itself. The key is shown once on screen and not emailed.
- Downloads: served as ordinary files by our hosting provider (Vercel).
- Email you send us at sales@solutionandnetwork.com.
The website uses no analytics or advertising trackers.
Security questionnaire or a vulnerability to report?
We'll complete your vendor or security questionnaire, join a call with your IT team, or walk through any section of this page. To report a security issue, please write with "Security" in the subject; we'll acknowledge it and keep you informed while we fix it.
sales@solutionandnetwork.com