Vrge

Trust Center

Last updated: April 27, 2026

This page is the single index of Vrge's security, privacy, and compliance posture. It is built for procurement, security, and legal teams who need to evaluate Vrge before purchase. We are honest about what is in place today, what is in progress, and what is on the roadmap. We do not display certifications we have not earned.

The short version. Vrge is local-first by design — customer business data lives on customer devices. Source connections (Gmail, Calendar, Drive, banking) are read-only. Cloud AI calls are redacted by default. AI proposals never write to the database without explicit user approval. Nothing is sold, no telemetry exfiltrates customer data, and one-click export works even with an expired license. The rest of this page is the receipts.

Architectural commitments

The structural decisions that make Vrge a different category of risk than a typical cloud CRM. These are properties of the codebase, not promises in a policy.

Local-first storage

In place

Customer data lives in a SQLite database on the user's own device. Vrge does not host customer business data on its own servers.

Read-only OAuth scopes

In place

All third-party data sources (Gmail, Calendar, Drive, etc.) connect using read-only scopes. Vrge cannot send email, modify calendars, or alter source data.

Redact-by-default cloud AI

In place

Names, emails, addresses, and dollar amounts are tokenised before any cloud AI inference call. Full-content mode requires explicit per-source opt-in with a 'what gets sent' preview.

Proposal review before any write

In place

AI-detected entities never write to the customer's database directly. Every observer-generated change requires explicit user approval through the Inbox.

24-hour reversible accept

In place

Every accepted proposal can be undone within 24 hours via transactional rollback. The applied_proposals log records full snapshots for that purpose.

Provenance on every entity

In place

Each entity created via the observer carries an origin record — source event, AI model, confidence score, accept time. Auditable end-to-end.

One-click data portability

In place

Full export to portable JSON/CSV — entities, proposals, AI history, origin records. Works even with an expired license. No DRM, no lock-in.

No training on customer data

In place

Customer email, file, or business data is never submitted to any AI provider for training. Inference-only API calls, when authorised by the user.

Security posture

Concrete technical and operational measures, including what isn't in place yet.

TLS in transit

In place

All traffic between Vrge endpoints (website, license, auto-updater, Managed AI proxy) and customer devices uses TLS 1.2 or higher.

Bcrypt password hashing

In place

On the optional Team self-hosted server, user passwords are bcrypt-hashed with per-user salts. JWT for session management with rotation.

OAuth tokens stored only on-device

In place

OAuth refresh and access tokens for connected sources never leave the customer's device. Vrge servers cannot impersonate connected accounts.

Cookieless analytics

In place

The marketing site uses Cloudflare Web Analytics — aggregate page views and coarse geography only, no cookies, no fingerprinting, no personal identifiers.

Coordinated vulnerability disclosure

In place

Triage commitment within one business day of report. Public scope and rules of engagement on the Security page. Safe-harbour language for good-faith research.

Security & disclosure policy

Independent security audit

Planned

We have not yet commissioned a formal third-party penetration test. We will publish results when one is complete.

Google CASA security assessment

In progress

Required for Gmail/Calendar OAuth verification at restricted scopes. Pack drafted; assessment pending Google's verification process.

SOC 2 Type I

Planned

Targeted once Managed AI tier reaches sustained scale. We are honest that we are not certified today and will not display badges we have not earned.

Legal & regulatory

Frameworks Vrge addresses, with links to the underlying documents your legal team will want to read.

GDPR (EU/UK/Swiss)

In place

Article 28 controller–processor template available. Standard Contractual Clauses (Module 2) incorporated. Sub-processor change notification with 30-day objection window.

Data Processing Agreement (DPA)

CCPA / CPRA (California)

In place

Privacy policy details CCPA categories of information collected. We do not sell or 'share' personal information as those terms are defined under CCPA.

Privacy Policy — California section

HIPAA

In place

TRD Ventures LLC is not a HIPAA-covered entity, and Vrge is not a HIPAA-compliant system today. Customers in healthcare should not store, process, or transmit Protected Health Information through the Service.

Privacy Policy — HIPAA notice

Sub-processor disclosure

In place

Complete current list of third-party services that may process data on Vrge's behalf, with purpose, data categories, and jurisdiction for each.

Sub-processors

PCI DSS

In place

Vrge does not collect, transmit, or store payment card data. All payments are processed by Lemon Squeezy as Merchant of Record — they are PCI DSS Level 1 compliant.

Data residency

In place

Customer business data resides where the customer chooses — their device, their self-hosted server. Vrge-operated services run primarily in the United States; the marketing site is on Cloudflare's global network.

For security and procurement teams

We respond to security questionnaires (CAIQ, SIG, custom), DPA redline requests, and procurement intake forms within five business days. For most B2B engagements the published policies here are sufficient — counter-signed PDFs are available on request.

Privacy PolicyFull data handling disclosureSecurityDisclosure policy + scopeData Processing AgreementGDPR Article 28 templateSub-processorsThird parties processing dataTerms of ServiceCommercial termsAccessibilityWCAG 2.1 AA conformance target