Your architecture, protected
Security and trust.
How Flowboard handles your diagrams, credentials and account data. This overview is not an independent audit or certification.
Data flow
- Local editing stores a browser draft. Publishing sends the model to the Flowboard application and database.
- GitHub sign-in provides account identity. Standard login is separate from optional company repository integration.
- An authorized REST or MCP client can read or change the diagrams its credential permits. What an external AI client sends to its model provider depends on that client's configuration and agreement.
- Stripe processes subscription checkout and billing management. Checkout includes billing identifiers, the selected plan and editor quantity. It does not include architecture documents or node content.
Access and security controls
- Account and diagram authorization
- Private diagrams are limited to their owners and authorized collaborators. Workspace roles control editing, commenting and administration. Personal keys inherit account permissions. Scoped MCP credentials restrict access to selected resources; OAuth requires a supported, registered client. Use a dedicated limited-permission account, not a platform-wide server key.
- Credential handling
- Personal keys are hashed for storage and shown once. Session cookies are HttpOnly and SameSite=Lax, with Secure set when the configured base URL is HTTPS.
- Revision and proposal safety
- Owned writes, restores, and proposal decisions use atomic head/history updates with stale-version checks. Restoring a revision creates a new version, preserving the intervening history.
- Keep an editable backup
- Export important architecture as JSON, Markdown or YAML. These editable formats let you keep a copy outside Flowboard. Contact us to discuss recovery requirements before relying on a contractual recovery target.
- Abuse and request privacy
- Support intake requires an active account, limits new requests, rejects cross-origin mutations, and separates requester records from administrator triage. Check request status on the support page or contact support by email. No customer request is automatically published.
Hosting, subprocessors, and residency
GitHub provides sign-in and Stripe processes billing. Contact us for hosting and subprocessor information needed for your security review. Standard plans do not include dedicated tenancy or a guaranteed data-residency location; any such requirements must be agreed in writing before purchase.
Export, deletion, and retention
Editable JSON, Markdown, and YAML exports are available to authorized readers. Owners can delete published diagrams; browser drafts must be removed separately through local controls. Database deletion is not proof of erasure from every backup or external AI provider. Contact us for account deletion, retention and backup-erasure questions before relying on a deadline. Read the data-handling notice.
Security reporting
Email support@flowboard.studio with “Security report”. Send a minimal description and a way to reach you; request a secure exchange before sending credentials, private architecture, personal data or exploit material. Do not use the public roadmap. No 24/7 response target is promised.
Terms, DPA, and questionnaire review
Enterprise contractual and data-processing requirements are reviewed individually. Only the agreement you sign defines your contractual commitments. Request a procurement review with the document name, business context and required review date, without uploading sensitive reports. Contact us to arrange review of security questionnaires, contractual requirements and access to confidential reports. Confidential reports are not publicly hosted here.