Sensitive bid work should not require another content upload just to add final control.
REQVERA is designed around a local project boundary for normal desktop processing, explicit evidence-linked release state and human-controlled buyer-portal submission.
Local-first is an operating boundary, not a marketing adjective.
Normal desktop project processing is designed to remain on the customer device. Release state is evidence-linked, the Windows product is distributed through Microsoft Store, and final buyer-portal submission remains human-controlled.
Keep the control chain explicit from workspace to human submission.
Normal project processing stays on the customer device.
Project data and portable backups use the reviewed encryption routines.
Claims and blockers remain tied to an inspected control state.
Buyer-facing output is associated with the current release decision.
Final buyer-portal review and submission remain deliberate human actions.
State exactly what the reviewed product supports — and what it does not claim.
Desktop project processing
Security claims stay bounded
Distribution stays explicit
Read the full Security & Trust boundary before treating architecture claims as guarantees.
The trust page separates reviewed implementation evidence from claims REQVERA deliberately does not make.
Security & trust →
Keep the next control question clear.
The resource hub is organised by buyer task, not by page type. Move sideways only when the question changes.