WhatsApp 查詢

Trust centre

How SharkFlows earns operational trust

信任中心

A transparent view of product status, security boundaries, privacy responsibilities and third-party dependencies.

01

Security

Server-enforced roles, tenant scoping, private files, signed public links, webhook verification and audit trails protect normal workflows. Security controls are tested in the application, but SharkFlows does not currently claim SOC 2 or ISO 27001 certification.

02

Privacy

DONOW LIMITED publishes its operator identity, contact channel, privacy notice, deletion route and data-processing explanation. Customer businesses remain responsible for notices and lawful use relating to their own employees and end customers.

03

Availability

The public status page performs a current health check. It is not a promise of uninterrupted service or a fabricated historical uptime percentage. Third-party services such as Meta, Stripe, Supabase and Vercel can affect individual capabilities.

04

Integration control

Meta messaging is connected only through customer action and requested permissions. A connection is bound to the correct tenant, tokens are protected, and a customer can disconnect. App Review and Tech Provider verification remain Meta-controlled processes.

05

Responsible product claims

Demo data is labelled. Planned or testing functions are distinguished from available functions. Customer names, partnerships, funding, certifications and awards are not displayed unless they are real and authorised.

How SharkFlows earns operational trust | SharkFlows