Privacy in the Runfabric dev release.
What the product stores and where work executes, to help you decide what to connect to a development workflow.
Account and access records
Runfabric stores product account identifiers, optional display names, passkey public credentials, project memberships, session and authorization records. Passkey private keys remain with your authenticator. Recovery codes and opaque access credentials are stored as hashes where verification permits.
Workflow and integration data
Definitions, inputs, outputs, attempts, approval decisions and execution history persist for the project. Hosted integration credentials are encrypted. Tool results and model responses can form part of the execution evidence.
Configured integrations receive the data needed by their operations. Your model broker receives prompts and permitted tool results. Consult the provider's privacy and retention information when deciding what to send.
Browser storage
The app uses a secure session cookie for login. Project selection and interface preferences can be stored locally. The separate playground stores its simulated project in the browser and labels it as local; it is not the durable hosted project.
Development use
CognitionHub hosts this release on Cloudflare and Google Cloud development infrastructure. Avoid production-sensitive data. Revoke machine grants and integration access through the product. Contact your Runfabric development administrator for account or data requests.