Your workflows run
on your computer.
FlowForge executes workflows on your Mac. Workflow definitions and run history stay local, while credentials use the macOS Keychain. Connected email, APIs and hosted AI send the data needed by those services. Licence activation and periodic validation also require network access.
Know where your automation runs
Private workflow automation starts with knowing where your work happens. FlowForge runs your emails, files and task workflows on the computer where you install it, with local history you can review.
Local workflow files
Your workflow configuration remains on your machine rather than being stored in a FlowForge cloud account.
macOS Keychain
Credentials are stored using the operating system’s protected credential facility.
No usage telemetry
The published privacy model states that FlowForge does not collect workflow usage analytics or telemetry.
Explicit network actions
Email, webhooks, APIs, hosted AI, and third-party connectors use the network only because you configured those steps.
Human approvals
Pause sensitive runs and require a person to approve the next action.
Audit and versions
Review local execution history and restore earlier workflow versions when a change needs to be reversed.
Keep sensitive context close to the work
Local execution is useful when automating internal files, operational inboxes, client processes, development tasks, or other workflows where unnecessary data replication creates risk.