Security

How VISIBLE ONLINE handles access and data

What is true today, without certifications we do not have.

Read-only by design

VISIBLE ONLINE reads public Sui and Walrus data. It holds no keys, signs nothing and moves no funds.
Repairs that move money are planned only through an on-chain policy with hard limits and human approval; none is live.

No passwords. Sign-in links are single-use and expire after 15 minutes; VISIBLE ONLINE stores only their SHA-256 hash.
Sessions are random 32-byte values in an HttpOnly, SameSite cookie; only their hash is stored. They last 14 days.
Every change in a workspace needs a per-session token (CSRF protection). Sign-in requests are rate-limited per address and per client.
Every query for workspace data is filtered by workspace; a member of one workspace cannot read or change another's agents, runs, incidents or channels. This is covered by automated tests.

No third-party scripts, trackers or fonts. The pages send a strict Content-Security-Policy; only the homepage runs two small inline scripts, allowed by their exact hashes.
Logs carry ids, states and durations — never addresses, emails, tokens or webhook URLs.

No external security audit or penetration test has been performed.
Webhook targets are restricted to public https host names; a host name that resolves to a private address is not yet detected.
A security contact address will be published before the monitoring service opens.