HOW IT WORKS & ARCHITECTURE

Secure database
for PII records & files.

  • Go-powered, high-speed personal data storage
  • Built-in SQL/GraphQL injection protection
  • Simple API integration in minutes
  • Streamline DPDPA, GDPR, HIPAA, ISO 27001, and SOC2 compliance
LIVE ARCHITECTURE WALKTHROUGH
ILLUSTRATIVE EXAMPLE
Original data
Stored encrypted in vault backends
Record reference
Identifies a profile; grants no access
API credential
Authorizes your backend’s requests
  1. 01
    Your app → DatabunkerProfile + file + API credential
  2. 02
    Databunker → Vault databaseEncrypted profile
  3. 03
    Databunker → File backendEncrypted file
YOUR APPLICATION STACKBusiness logic stays here
VAULT SERVICESelf-hosted or managed
CONFIGURED STORAGEChosen for your deployment

Your application

Backend / service

Sending a profile + file
Scoped credentialProfile + file

Application database

Your existing business data

customer_id1024
user_token—

Awaiting a record reference

Databunker Pro

The controlled retrieval boundary

01
Authenticated APIProfiles + attached files
02
Access policyEvaluate the caller’s permissions
03
Encryption + retrievalOriginals returned only when allowed

Vault database

Encrypted customer records

PostgreSQLMySQLOracle

Separate from your application database

File backend

Encrypted file content

S3GCSAzure BlobLocal disk

Files linked to a customer record

01 / 04Playing

Originals go into the vault.

Your backend sends the profile and attached file through the authenticated API. Databunker encrypts their contents before writing to its configured storage.

ILLUSTRATIVE INPUT
profile: { name: "Alex Morgan" }
file: passport.pdf

The API credential authorizes the request.

READ THE MAP

Breach-proof pattern:
no PII in your app DB.

Your backend keeps business data and a token. The vault checks every request and encrypts the originals; a separate database and file store hold only ciphertext. Plan it as an integration, not a config switch.

01 / YOUR APPLICATION

Keep business logic
where it belongs.

Your backend creates records and requests the values it needs. Your database keeps separate business records, such as orders and subscriptions, and a reference to the vaulted customer profile.

Application DB ≠ vault database
02 / THE VAULT SERVICE

Put a policy boundary
around the originals.

Databunker authenticates API calls, evaluates the configured permissions, and encrypts sensitive values at rest. Use scoped credentials for application access.

API · permissions · encryption
03 / VAULT STORAGE

Store encrypted records
and ciphertext files.

A supported relational database backs the vault. Attached files use local disk or a supported object store, with access going through Databunker.

Separate storage responsibilities

Test the vault on your own data.

Spin up a vault, store your first records and get tokens back — 14 days free, no credit card required.

TWO TOKENS. DIFFERENT JOBS.

Stolen tokens?
Still no data.

Knowing a record token does not grant access to the record. The application sends a separate access credential with its API request.

The reference selects the record.
The policy controls what comes back.
AN AUTHORIZED READILLUSTRATIVE FLOW
WHICH RECORD?

Record reference

user_token: a21fa1d3…

Stored in your application database.

WHO IS CALLING?

Scoped credential

X-Bunker-Token

Kept in your application backend.

YOUR BACKEND
POST/v2/UserGet
DATABUNKER PRO

Evaluate permissions

Allowed fields

Access is defined by the configured policy, not by possession of a record reference.

RECORDS + FILES, TOGETHER

Profiles and ID scans.
One access policy.

A profile in one database. An ID scan in another bucket. Bring them under the same controls, so access follows the person and the purpose.

Share only what’s needed

Mask fields and scope access to records and documents.

Give data a lifecycle

Set retention windows and enable profile version history.

Explore access controls
Customer workspacePOLICY EXAMPLE
AM

Alex Morgan

Customer #1024
In vault
View as
Email address***MASKED
National ID***MASKED
ATTACHED DOCUMENTS 2 FILES
passport.pdfIdentity document
Restricted
address-proof.pdfSupporting document
Restricted
Support access · masked profileDocument access restricted by this example policy
POLICY APPLIED

Support gets the context to help. Identity documents stay restricted.

BEFORE YOU COMMIT

What architects
check next.

The questions that decide whether a vault belongs in production. Every answer links to the docs behind it.

Key management

AES-256 per-record encryption, FIPS 140-2 compliant. A rotatable wrapping key protects the master key, so rotation needs no data re-encryption. Backup uses Shamir’s Secret Sharing, 3 of 5.

Encryption docs

Access control

Conditional role-based policies decide which fields each caller receives, with masking on every read. Bulk export is denied by default and audited when unlocked.

Access control docs

Multi-tenancy

Tenants are isolated with PostgreSQL row-level security. The same person in two tenants gets two unrelated tokens.

Pro overview

Benchmark results

About 14 ms median per read, flat from 10M to 100M records. Bulk imports reach roughly 12,000 records per second. Storage grows linearly at about 5.7 KB per 120-field profile.

View report

Record versioning

Every create or update can keep a full snapshot of the profile, hashed for integrity checks. Review what changed, investigate an incident or restore an earlier state. Off by default; you set how many snapshots to keep and for how long.

Versioning docs

Deployment

A stateless Go service on Docker, Kubernetes with Helm, or OpenShift, backed by PostgreSQL or MySQL. Self-host it or let us run it.

Deployment options

Running the open-source Databunker? Pro adds multi-tenancy, key rotation, Shamir recovery, format-preserving tokenization, fuzzy search, record versioning and policy-based access.

Ready for implementation details?

Read the architecture docs
LESS SPRAWL. MORE CONTROL.

Give sensitive data
a proper home.

Walk through your architecture with a Databunker engineer.
Find the right place to start.

Managed trial · No credit card required