FlowSyncSecurity and trust
Agree the controls before the work goes live.
Suitability depends on the information, the workflow and the controls configured for the proposed solution. This page is not a certification or a regulatory-compliance assurance.
What the website workspace implements
The onboarding workspace uses Supabase authentication and database row-level access policies for invited team members. Administrator checks govern team management. These are implementation details in the website code, not an independent assessment of a customer deployment.
Human decisions and evidence
Workflow design can identify the responsible reviewer, approval steps, required documents and exceptions. Agree which actions must be recorded and how evidence is retained before relying on them for an audit.
Hosting, encryption and recovery
Request the deployment-specific hosting location, encryption settings, backup schedule and recovery arrangements from the FlowSync team. AWS infrastructure on its own does not establish security or compliance. No unverified infrastructure control is promised here.
Access, retention and incident handling
Confirm who can access information, how access is removed, how long records are kept and how incidents are reported and escalated. Retention and recovery commitments must be set in the applicable agreement.
AI providers and subprocessors
The website Flo assistant sends chat content to an AI service and stores messages in Supabase. The current implementation uses Anthropic for replies. Confirm the provider list, data locations and applicable processing terms for your solution; do not assume a particular training or retention setting.
POPIA considerations
Assess the personal information involved, the purpose of processing, access and retention before implementation. FlowSync does not make an organisation POPIA-compliant simply by being used. Obtain appropriate advice and agree responsibilities for the specific process.