Architecture
Privacy built into the architecture
We use browser security sandboxes to protect your data. See how our local-first database, client compilers, and optional authenticated cloud sync operate together.
Local browser storage
Your documents are saved inside your browser's private database (IndexedDB). No text leaves your machine by default, allowing you to use the editors, templates, and features without registering an account.
Document sandbox
Your Master Profile holds your background records. When you start a document, the editor pulls a snapshot from your profile. Changes inside templates remain sandboxed and will not overwrite your master records.
Browser compilers
When you download a resume or cover letter PDF, the compilation happens inside your browser tab using WebAssembly. Your personal facts are never processed on external servers.
Secure cloud backups
If you register and log in, your Master Profile and sandbox documents are backed up and synchronized in the cloud. Your account is secured using passwordless OTP credentials.
Subdomain routing
Publishing a portfolio pushes metadata to our edge router. The system dynamically maps visitors (e.g. name.veriworkly.com) and displays your web portfolio page without cookies.
Open and auditable codebase
A privacy statement is only as good as the code that executes it. Because VeriWorkly is open-source, developers, job seekers, and security engineers can audit our database settings, compile parameters, and routing scripts. You can run the entire platform locally, inspect the configuration, or self-host your own database endpoints.