Security controls for the workflows your customers depend on.

Fluenta applies security controls to the workspace, credentials, integrations, and operational data used by a workflow. Technical implementation details are maintained in the security documentation for developers and security reviewers.

Connections to Fluenta use HTTPS in transit. Credentials used for WhatsApp and connected services are encrypted before storage and are not shown as plain text in the product interface.

Workspaces use explicit owner, editor, agent, and viewer roles. Product routes enforce the minimum role required for an action, and secret values are masked in the interface.

Workspaces are isolated so members access only the resources their workspace authorizes. Fluenta avoids revealing whether a resource exists outside a member’s workspace.

Fluenta verifies inbound webhooks and applies safeguards to outbound HTTP requests. Review webhook verification, request guard behavior, token scopes, redirect handling, runtime isolation, response limits, and audit events in the technical security documentation.

Fluenta automatically purges expired conversation data after 90 days. For deletion requests and the data classes involved, read how data deletion works.

Scheduled database backups run on a timer. Restore testing and formal recovery objectives are not yet documented.

Report a security concern through the vulnerability reporting path below. Fluenta will acknowledge receipt and use the report details to investigate the affected service.

Fluenta does not claim SOC 2, ISO 27001, HIPAA, PCI, or any other certification or audit.

Fluenta is preparing a subprocessor list that identifies each provider by legal entity and purpose. Until that list is published, contact the team for a current review request.

Please report a potential vulnerability to [email protected].

Include a concise description, steps to reproduce or an affected URL, the potential impact, and a safe way to contact you. We will acknowledge receipt.