Trust CenterSecurity
Security and access control in FlowDule
This page describes the security mechanisms that protect data across chains, locations and roles, from encryption and separation between businesses to logging and multi-factor authentication.
Security is part of the architecture, not an add-on
FlowDule has been built with separation between businesses from day one, with chains, locations and users kept apart. Security is not an extra layer. It is part of the way data is stored, accessed and logged.
This page describes the most important mechanisms in outline. The binding level of security is set out in the accepted data processing agreement and the version-bound TOMs annex, and the security description gives the complete overview.
Read the security descriptionSecurity
The most important security layers in the platform
Encryption, isolation, access and traceability.
- Encryption
Encryption at rest and in transit
Communication with FlowDule is protected with modern transport encryption. Production uses encryption at rest for relevant databases, files and sensitive fields, and journal data is field-encrypted with AES-256 and chain-specific keys in AWS KMS.
- Isolation
Data separation between chains and locations
Data per business and location is kept separate, so the platform is designed to prevent access to data across different organisations or departments.
- Access
Personal accounts and multi-factor authentication
The security model requires personal accounts rather than shared login details. Multi-factor authentication is required for FlowDule's own platform users, and the chain's users can switch it on for their own account.
- Control
Role and permission management
Decide who can see, edit or administer which data, so only authorised users get access to sensitive information.
- GDPR
Consent and logged export
FlowDule logs consent at sign-up. The full export of the chain's data can only be ordered by an administrator, and the order is logged.
- Traceability
Audit logs and backup
Relevant actions involving client and journal data must be traceable to an identified user or system component. The database is backed up daily to Cloudflare R2 with 30-day rotation, and as part of the restore procedure, restoration must be tested in an isolated environment.
Isolation
Separation between businesses as the foundation of the whole platform
Customer data is separated in several layers: the application checks chain, location, role and relationship, and the database enforces row-level security on the tables in scope. Access across chains and support access are tested with both permitted and refused scenarios.
See GDPR and policiesAccess control
Role-based access across chain, location and practitioner
FlowDule's role model cascades from chain to location to practitioner. Access is checked on every API call. Support access to the customer's content may only take place in a specific, documented case, after the necessary approval, with a personal identity, for the shortest possible duration and with relevant logging.
Read the security descriptionContact
Security enquiries
If you have found a vulnerability, or if you have a security question about the platform, write to security@flowdule.com. We handle security enquiries as quickly as possible. General support questions should be sent to support@flowdule.com.
Write to security@flowdule.comSee it for yourself.
Create a free account and try FlowDule for 30 days. No credit card, no commitment.