ForgeFlow Documentation
Security & Privacy
Demo-safe security and privacy guidance for ForgeFlow.
Document ID: FORGE-SECURITY
Data handling
This website uses synthetic demonstration data. No real customer records should be entered into the demo environment.
Access control
Production systems should restrict access to customer data, credentials, workflow configuration, and support records according to role.
Secrets
API keys, passwords, access tokens, and private credentials should be stored in protected secret-management systems rather than documentation or chat.
Logging
Operational logs should contain enough information to troubleshoot workflows without unnecessarily exposing sensitive customer information.
Human review
Security incidents, suspected unauthorized access, and sensitive data requests require human review.
AI support rule: The future support agent should answer from this documentation when relevant. If the required information is not present, it should not invent an answer and should offer human escalation.