OkFlow security
Understand who can access your projects, how shared files are handled, and what integrations can access. Contact us to discuss the security requirements of your organization.
Controls around your workspace
Workspace authorization
Project and organization membership and roles scope access to workspace operations. Administrators should review membership and shared links regularly.
File access and upload limits
File routes check authorized access and apply upload and delivery limits. Files and screenshots can contain personal information; review what you capture before sharing.
Authentication
Sign-in uses Supabase authentication. Keep accounts and credentials private, and remove access when a member leaves your team.
Integration credentials
Connected services require authorization. Only enable integrations your organization has approved, and revoke connections you no longer need.
Regression checks
The codebase includes authorization, request-budget, database, and browser regression tests. These checks help detect regressions; they are not a security certification.
Privacy and data handling
Our privacy policy describes the information used by the service and its providers. Contact info@okflow.io about data-processing terms, retention, or deletion requests.
Security evidence and contractual commitments
This page does not represent OkFlow as SOC 2 or ISO 27001 certified, guarantee end-to-end encryption, or offer a published uptime SLA. Provider certifications do not certify our application. Ask us for current evidence before relying on a control, hosting location, or contractual commitment.
Report a security concern
Email info@okflow.io with a description, affected URL, and safe reproduction steps. Do not send passwords, secret keys, or customer data. Do not access another workspace or disrupt the service while investigating. We will review reports and coordinate follow-up; no fixed response-time or reward promise is made here.
info@okflow.io