Security & Trust

Last updated: August 22, 2026

raiseit.dev captures screen, DOM, network, and console context to produce reproduction-ready bug reports. Because that data can be sensitive, security is built into the product — not bolted on afterward.

Encryption

All captures are encrypted in transit using TLS 1.2 or higher and encrypted at rest. Each workspace’s data is logically isolated with role-based access controls.

Redaction at capture

Passwords, API tokens, and known PII patterns are masked at the point of capture — before data leaves the reporter’s browser. This reduces the risk of accidental secret exposure in bug reports.

Data residency & retention

Workspace data can be pinned to your preferred region. Administrators control retention windows and can purge captures on demand. See our Privacy Policy for data subject requests.

Access controls & audit

Access follows least-privilege principles by role. We maintain audit logging of administrative actions and are building toward SOC 2 Type II certification with a documented incident-response process.

Compliance status

SOC 2 Type II: in progress. We will update this page when audit milestones are reached. For security questionnaires or a DPA, contact dhiraj@raiseit.dev.

Reporting issues

If you discover a security vulnerability, please report it responsibly to dhiraj@raiseit.dev with sufficient detail to reproduce. We aim to acknowledge reports within two business days.