Skip to content
DVSentry
Code Web & Network Cloud Infrastructure AI Resilience DPDP Burnwatch Vault & Share Plans Docs
Log in Start free

Trust

Architecture and data flow

Last updated: November 19, 2026

This page follows your code, your findings and your secrets through DVSentry: which part of the platform touches them, what is kept, and what DVSentry never receives. It describes the platform as it runs today. The Trust Center covers isolation, backups and sub-processors in more detail.

The parts of the platform

  • Web app and API. Where you sign in and where every request is checked against your organization's membership. It holds no scanner and cannot start containers.
  • Repository fetcher. A separate service that clones a repository for a scan. It has no database access and no platform secrets.
  • Workers. Repository, web, cloud and AI workers run the scans. They hold no database credential: they take work from, and return results to, an internal job service over mutual TLS, which checks every result as untrusted input before storing it.
  • Scanner runtime. The only service that starts scanner containers. Each scanner runs in its own short-lived, sandboxed container with no network, as a non-root user, on a read-only file system, from an image whose signature is checked first.
  • Database. PostgreSQL in Google Cloud's Mumbai region. Row-level security adds a second check on sensitive tables, so a request admitted to one organization sees only that organization's rows.
  • Agent (optional). A read-only agent you install on your own Linux hosts or Kubernetes clusters. It connects out to DVSentry; DVSentry does not connect in.

Your code

  1. You start a scan. You give a repository address and, for a private repository, a token, or the GitHub App provides a short-lived token for that one repository. A token you give for one scan stays in memory for that scan and is never written to the database, unless you choose to keep it encrypted in Scan credentials.
  2. The fetcher clones it. A shallow copy is written to a workspace the scanners can read. The web app can only read that workspace.
  3. Scanners read it, offline. Each scanner container sees your code read-only and has no network, so it cannot send your code anywhere.
  4. The copy is deleted. When the scan's jobs finish, the copy of your repository is removed. DVSentry does not keep your source code.

Your findings

  • What is stored. Each finding's rule, title, severity, file path and line, the scanner's description and fix advice, and the software bill of materials. For code, infrastructure-as-code and secret findings, DVSentry keeps the one flagged line, encrypted, with credential-shaped values masked to their shape.
  • Who can see it. Members of your organization, by role. Every lookup is filtered by organization, and row-level security checks it again.
  • How long. Reports and their findings for the period your organization sets (default 90 days, 30 to 365). See the Data Retention Disclosure.
  • Where else they go. Only where you send them: exports you download, a Trust Center you publish, tickets and webhooks your Admin connects, and chat apps your Admin installs.

Your secrets

  • Secrets found in your code. Secret scanners report where a secret is, with its value redacted. Checking whether a secret is still live is a separate step that runs only when an Admin of your organization turns it on.
  • Credentials you save. Scan credentials and provider keys you choose to keep are stored encrypted and opened only for the job that uses them.
  • Cloud accounts. AWS, Azure and Google Cloud are connected without a stored key: your account trusts DVSentry's own identity issuer, and each scan gets a short-lived, read-only token.
  • Password vault and Secure share. Encrypted in your browser before upload. The keys never reach DVSentry, so we cannot read or recover them.

AI features

Repository scanning sends no source code to an AI service. AI features run only when you use them, and send only what each needs, with secrets removed:

  • Report summaries send the finding details needed to answer, with secrets removed.
  • Triage sends each finding's rule, title, severity and file type, never the code or the file path.
  • Ask DVSentry sends finding titles, severities and dates, never asset or owner names.
  • Code review runs only after an Admin opts the organization in. It sends up to 13 lines around each new code or infrastructure-as-code finding, never the file path, the repository name or a secret value.
  • Platform-managed AI uses Google Gemini, as listed in the sub-processors, or your own provider key if you set one.

What DVSentry never receives

  • The contents of your password vault, your vault passphrase and recovery words.
  • The key to a Secure share link: it stays after the "#" in the link, which browsers do not send.
  • A long-lived key to your cloud accounts.
  • The values of personal data in your code: PII Radar records field names, places and counts, never the data itself.
  • Your cloud identity policy documents: the cloud scanner evaluates them inside its container and sends only the access they grant.
  • A password you check against known breaches: only the first five characters of its hash go to the breach service, from your browser.

Web, network and cloud scans

  • Web and network. DVSentry tests only domains you prove you own with a DNS record, and refuses private and internal addresses. What a scan reads from your site is reduced to findings and evidence.
  • Cloud. The cloud scanner reads your account's configuration with the read-only token, inside its own container, and returns findings and a resource inventory. It does not change anything in your account.
  • Agent. The agent sends check results, package names and versions, and the facts the checks need. It acts only on commands signed by DVSentry and checked against its own trust file.

Questions

Write to security@dvsentry.com. To report a vulnerability, see Report a security issue.

DVSentry
Password generator Security Trust Center Documentation Terms Acceptable use Privacy Data sources Architecture and data flow Changelog Security disclosure Hall of fame Legal Built for DPDP compliance Log in
Created by Aslam Jabri