Security

This page describes security measures that are actually present in the Visirush application. It does not claim certifications or controls that are not implemented in the code.

Transport and headers

When the public site address is served over HTTPS, responses include HTTP Strict Transport Security. Every response also sends X-Content-Type-Options: nosniff, X-Frame-Options: DENY, Referrer-Policy: strict-origin-when-cross-origin, and a Content Security Policy that forbids being embedded in a third-party frame (frame-ancestors 'none').

Passwords and sign-in

Account passwords are stored as scrypt hashes, not in plain text. Optional two-factor authentication uses TOTP. Backup codes are stored as hashes and can be used if the authenticator is unavailable. Sessions use hashed tokens.

Organization isolation

Each customer organization has its own workspace and its own secret store on disk. OAuth tokens and site or provider credentials are encrypted at rest with AES-256-GCM, with a key kept outside the source repository and the data directory; the files are readable only by the application (Unix permissions 0600) and are never sent to the browser. Data travels over HTTPS. API and workspace access are scoped to the current organization and to the member’s role (owner, admin, editor, or reader).

Rate limits

Sensitive actions (including sign-in, password reset, email confirmation, public API calls, and certain generation features) are rate-limited and may return HTTP 429 when a limit is reached.

Backups

Authorized members can export and, where their role allows, restore a workspace backup from the product. Application data is also kept in rolling operational backups for 30 days, as stated in the privacy policy.

Reports

To report a security issue, write to contact@visirush.com.

Language

These pages are provided in English and French. If there is any conflict between the two versions, the English version prevails.

Last updated: November 21, 2026.