Security & Trust

Care for people.
Control over their information.

Employee information deserves more than a promise. VaultFlare builds layered safeguards into the work itself—from access and document handling to signing evidence and recovery.

We reply with a scoped overview and the verification evidence behind it.

Application-level encryptionPrivileged-access MFARecorded signing evidenceRestore verification

Built into the work

Protection at each handoff.

Six controls. For each one: what it covers, where it stops, and what we confirm with you before the pilot.

01Document encryption

Protection within the document workflow.

New files in supported document workflows are encrypted with AES-256-GCM, with a separate key for each file. The application decrypts them only for authorized use.

Covers · Boundary · Pilot review
Covers
New files in supported document workflows. Files that cannot be encrypted are refused rather than saved as plaintext.
Boundary
This coverage excludes legacy files, imports and other attachment types. This is application-level encryption, not end-to-end: the application can decrypt files.
Pilot review
Confirm the file types and workflows in scope for your pilot.
02Identity & permissions

Access shaped by responsibility.

Workspace membership, roles and employee groups decide who can see and act. Privileged administration requires multi-factor authentication and enforced session limits.

Covers · Boundary · Pilot review
Covers
Server-side permission checks govern access to protected workflows and customer information.
Boundary
Employee multi-factor authentication is optional under the current policy. Administrator MFA is not universal employee MFA.
Pilot review
Roles, employee groups and authentication settings for your team.
03Upload safeguards

Checks before files become trusted.

Supported uploads are checked against their actual file format and screened for malware. Scan results are recorded, and infected files cannot be viewed or downloaded through the application.

Covers · Boundary · Pilot review
Covers
Format verification and malware screening on supported document uploads. Access is restricted while a scan is pending or has failed, except for the uploader.
Boundary
Generated signed PDFs follow a separate output policy and are not independently antivirus-scanned.
Pilot review
Coverage for the file types and workflows you will use.
04Signing & evidence

A signature with a record behind it.

Signing records consent and completion, preserves the exact document version signed, and files a signed copy with a completion certificate and integrity references.

Covers · Boundary · Pilot review
Covers
Consent and completion evidence, the preserved document version, the filed signed copy and its certificate. Signing links are time-limited.
Boundary
Signer verification depends on how the signer opens the request: an authenticated named signer, or an emailed code.
Pilot review
Test the signing and verification paths your team will use.
05Traceability

Accountability stays with the work.

Workflow, document and administrative events are recorded so authorized teams can review who did what, and when. Integrity references allow a downloaded signed copy to be checked against the filed one.

Covers · Boundary · Pilot review
Covers
Workflow, document and administrative events, and signed-copy integrity checks.
Boundary
Recorded events vary by workflow, and not every interaction is logged. Access to history follows permissions. Records support operational review; they are not a regulatory certification.
Pilot review
Agree which events and evidence your reviewers will need.
06Backup & recovery

Recovery that has been exercised.

An encrypted backup of the production database and uploaded files has been restored in an isolated environment and checked for integrity. Recovery planning covers data, files and encryption keys together.

Covers · Boundary · Pilot review
Covers
A post-release backup, restored in isolation and integrity-checked on November 2, 2026.
Boundary
This verifies a specific backup, not continuous recovery or a full rebuild of the hosted service.
Pilot review
Backup frequency, retention and recovery responsibilities before live operational use.

Data & hosting

Where your information lives.

Hosting
Infrastructure is provided by Vercel and Supabase. Contact us for the hosting and data-location details for your pilot.
In transit & at rest
HTTPS protects browser connections. Provider-managed encryption at rest is supplemented by application-level encryption in supported document workflows.
Workspace isolation
Access to customer records and documents is governed by workspace membership, roles and assigned employee groups.
Retention & exit
Retention periods and deletion at the end of a pilot are agreed in writing with each customer.

A considered start

Your requirements.
A defined pilot.

Before employee data is introduced, we review the intended workflows, access model, data handling and recovery expectations with your team. Pilot and service commitments are documented separately.

We can walk your reviewers through the implemented controls and the verification completed so far. Independent penetration testing and compliance certification are separate assurance steps; neither is claimed by this overview.

Start a security conversation

Questions or a security concern?

Contact support@vaultflare.ai. For a suspected issue, begin with a brief description and the affected area. Please do not email passwords, access tokens or employee records. Contact us to agree scope before conducting security testing.

Overview reviewed Privacy details Website & demo terms