Skip to content
Nawati Flow

Information security

Practical safeguards for account access, business information and responsible incident reporting.

Access and accountability

Workspace actions are subject to identity, permissions and organisational scope. Reading, editing and administration are different responsibilities. Give each person the access needed for their role and review it when duties change.

Use two-step verification where enabled. Keep recovery material safe and never share passwords or one-time codes in support messages.

Everyday handling

Check recipients before sharing a link or attachment. Protect exported files, screenshots and devices as carefully as the records inside the service. Do not place integration secrets in customer notes.

Shared user accounts weaken accountability. Lock unattended devices and report unexpected access or actions to your business administrator.

Operations and recovery

Audit information available for each authorised function helps establish what happened. Do not erase evidence or attribute an action to another person.

Backup, integration and recovery arrangements depend on the service configuration and agreement. This notice does not assert a security certification, unrestricted availability or immunity from incidents.

Report responsibly

Send an initial description, approximate time and safe reproduction steps to office@nawati.io. Do not attach a complete database, credentials or another person’s records.

Stop if a test could affect a real account or cause harm. Further testing needs an agreed scope. This page is not permission for unrestricted penetration testing or a promise of a bounty.

We store your privacy choice. You may also allow this browser to remember how you display help guides. This public site uses no external advertising or analytics tools.