How REVORY protects evidence.

Authenticated server-side context authorizes active workspace reads, writes, exports and finding changes. Password access uses email verification, durable throttling and session-version revocation; Google OAuth is available when configured.

CSV/XLSX upload policies limit file, row and batch volume, inspect file signatures and XLSX expansion, and reject workbook formulas. Canonical records preserve source IDs and provenance. Ambiguous or conflicting links remain visible and suppress unsupported financial output. Persistence uses transactions and idempotency boundaries.

Managed providers encrypt network traffic in transit and managed database storage at rest. Production secrets are held in managed environment variables. Stripe webhook signatures and a persistent replay ledger protect billing-event processing.

Scheduled retention, monitoring and operational checks are documented. Managed database backup/restore capabilities are used, and an isolated restore exercise has been recorded internally; this does not create a zero-loss or fixed-recovery guarantee. Incident response and escalation remain under Ametrine Labs operational control.

REVORY does not claim SOC 2, ISO 27001, PCI DSS certification or any independent certification not actually obtained. Stripe handles hosted payment-card collection; REVORY does not store full card numbers. Independent application-security review remains a release gate for advanced paid scope.

Send suspected vulnerabilities privately to security@revory.app. Do not send customer exports, passwords, recovery codes or exploit other users. See the Responsible Disclosure Policy for scope and safe-harbor conditions.