Data encryption
All data processed by Felix is encrypted in transit and at rest.- In transit — all communication between Felix and external services uses TLS
- At rest — connector credentials and workflow data are encrypted using AES encryption
Connector credentials
Felix stores connector credentials with the following controls:- Encrypted at rest using AES encryption
- Never exposed in logs, outputs, or the code view
- Only accessed when a workflow step requires them
- OAuth tokens are automatically refreshed before expiry
- Access can be revoked at any time from Settings → Connectors
Audit trail
Every workflow run produces a full audit log. For each step you can see what input the step received, what it did, what output it produced, when it ran, how long it took, and who triggered the run. Run logs are retained in your workflow’s run history and cannot be edited or deleted. Every automated decision Felix executes is traceable.Human Checkpoints as a compliance control
When a run pauses at a checkpoint, Felix records who was notified, what information was presented, what decision they made, and when they made it. This creates a named, timestamped record of human oversight.Access controls
| Permission | What it allows |
|---|---|
| View | See the workflow and its run history |
| Run | Execute the workflow and view outputs |
| Edit | Modify steps and descriptions |
| Admin | Full control including sharing and deleting |
AI usage
Felix applies AI only at the steps that require it. Steps that fetch data, write records, or send notifications run as structured code with no AI involvement. When AI is applied, Felix uses the connectors you have explicitly connected —@Anthropic, @OpenAI, or @Gemini. Felix does not use your workflow data to train models.