Security practices

Tenant isolation

Every piece of data in Web Preview belongs to an organisation, and access is enforced in the database itself — not just in the interface. Row-level security policies scope every query to your organisation's members, so queries from one tenant physically cannot return another tenant's feedback, projects, or attachments.

Roles within an organisation (owner, admin, manager, developer, reviewer) map to explicit policies. Guests never gain membership: they act only through signed, scoped review links.

Data handling

Data is encrypted in transit and at rest. Web Preview records no session replay, no keystroke logging, and no always-on screen capture — recordings are explicit, per-project, consent-gated features if and when they ship. Password and payment fields are masked in screenshots before upload, and customers can add their own privacy selectors.

Integration credentials are stored encrypted and never exposed to the browser. Secrets live in server-side configuration, never in client code.

Operational practices

Security-relevant actions — sign-ins, role changes, key rotation, exports — are recorded in an audit log your admins can review. Access to production data is limited to operations that require it, and the principle of least privilege applies to our own infrastructure.

Plan limits and rate limits are enforced server-side to protect against abuse of public endpoints.

Vulnerability disclosure

We do not run a slash-and-bash bounty program, but responsive disclosure is welcome. If you believe you have found a vulnerability in Web Preview, report it to the project's support channel once launch infrastructure is online — include reproduction details, keep findings confidential, and give us reasonable time to fix before publishing. We credit researchers who ask for it.