Last updated November 14, 2026
Security
Your API keys and payment secrets are encrypted and never shown again after you save them. Every workspace is isolated from every other, access is role-based, and significant actions are logged. If you find a security issue, please email security@getflowbiz.com and we will work with you to fix it.
1. Encryption
- In transit. All traffic to GetFlowBiz is served over TLS, using certificates issued automatically by Let’s Encrypt.
- Secrets at rest. API keys for connected platforms and payment-provider secrets are encrypted with AES-256-GCM before they are stored. They are never displayed again after saving; to change one, you replace it.
- Passwords. Passwords are hashed with argon2id. We never store them in plain text and cannot see them.
2. Accounts and sessions
- Sessions are stored server-side, and only a hash of each session token is kept in the database.
- Sessions use a 30-day sliding expiry and an httpOnly cookie that page scripts cannot read.
- Email verification, password reset and magic sign-in links use time-limited tokens, and expired tokens are purged.
3. Tenant isolation and access control
- Each agency is a separate tenant. Tenant isolation is enforced on every database query, so one workspace cannot read another’s data.
- Role-based access control limits what team members and clients can see and do.
- Clients see only the portal content their agency chooses to share.
- Audit logs record significant actions taken in each workspace.
4. Integrations and webhooks
- Outbound requests to connected platforms and custom endpoints are protected against server-side request forgery (SSRF), including blocking requests to internal networks.
- Incoming webhooks are verified using signatures where the provider supports them.
- GetFlowBiz reads data from connected platforms and only changes workflows when you use actions such as activate, deactivate, run or retry.
- We never store full card numbers or bank credentials. Card payments are handled by your own payment provider.
5. Data retention and deletion
Execution history is deleted automatically at the end of your plan’s retention period, and logs and resolved alerts follow a fixed retention schedule. Deleting a workspace deletes its data; backups expire on our hosting provider’s backup cycle, up to 30 days. See our Privacy Policy for details.
6. Incident response
If we become aware of a security incident affecting your data, we will investigate, contain it, and notify affected agencies without undue delay and, where required, within 72 hours, as described in our Data Processing Addendum.
7. Responsible disclosure
If you believe you have found a vulnerability in GetFlowBiz, please email security@getflowbiz.com. Include a description of the issue, steps to reproduce it, the affected URL or feature, and its potential impact. We will acknowledge your report, keep you updated, and let you know when it is fixed.
When researching, please:
- test only against accounts and workspaces you own or have permission to use;
- not access, modify or delete other customers’ data, and stop and tell us if you encounter it;
- not run denial-of-service, spam, social engineering or physical attacks, or automated scans that degrade the Service;
- give us reasonable time to fix the issue before disclosing it publicly.
We will not pursue legal action against researchers who act in good faith and follow these guidelines. We do not currently run a paid bug bounty program.
8. Security information for customers
Customers can request more information about our security practices, including answers to security questionnaires, by emailing security@getflowbiz.com. You are responsible for securing your own accounts, devices and the credentials you connect, and for revoking keys at the provider if they may have been exposed.
Questions about this document? Email support@getflowbiz.com.

