Normal desktop project processing is designed to remain on the customer device. The reviewed package contains no automatic project-content upload endpoint.
Security & Trust
Controls you can inspect. Boundaries you can understand.
REQVERA is designed around local project control, explicit release gates and evidence-linked decisions. This page states what the reviewed product architecture supports — and what it deliberately does not claim.
Local-first project boundaryHuman-controlled releaseNo hidden compliance claims
The reviewed source contains AES-256-GCM authenticated-encryption routines for project data and Argon2id + AES-256-GCM protection for portable backups.
Named blockers can keep release closed. Buyer-portal review and final submission remain human decisions.
No product telemetry integration is configured in the reviewed package. This statement does not cover unrelated operating-system, browser, antivirus or store-client traffic.
Release integrity.
Buyer-facing output is tied to an inspected release state rather than treated as an ungoverned export.
REQVERA’s controlled release architecture links buyer-facing output to a versioned control state and integrity evidence. Once readable exports are explicitly generated, their storage, transfer and retention sit under the customer’s own controls.
Assurance boundary.
We prefer a precise boundary to an inflated trust badge.
- No SOC 2 or ISO 27001 certification is claimed.
- REQVERA does not independently certify GDPR or legal compliance.
- No claim is made that every endpoint compromise or disclosure can be detected.
- Source-level evidence is not a substitute for validating the final signed installed package.
Validation statusCONTROLLED
Security claims stay evidence-bound.
Public wording remains intentionally conservative until the signed installed release has completed its own verification cycle.