Skip to main content
Databunker Pro provides two distinct tokenization engines, each designed for a different job:
  • PII tokenization (UserCreate / UserGet) — stores a complete user profile (JSON, N fields) as one encrypted record and returns a single UUID token representing the whole profile. Builds secure hashed search indexes over email, phone, login, and a custom field for efficient lookups. This is the user-table replacement pattern; see the PII Vault page for full detail.
  • Format-preserving tokenization (TokenCreate / TokenGet) — tokenizes individual sensitive values such as credit-card numbers (Luhn-valid), uint32 / uint64 integers, and Unix timestamps. Returns both a UUID and a format-preserving token in the same response. This is the PCI / single-value pattern, covered in the rest of this page.
Both engines share the same vault, encryption, multi-tenancy, and access-control layers — so the same auditability, key management, and CRBAC policies apply to either flow. Databunker Pro was built with the latest data privacy requirements in mind, such as data minimization, and is engineered to handle millions of data tokenization requests. The API supports bulk tokenization for efficient batch operations.

What Problems Does It Solve?

  1. Data Privacy & Compliance
  • ✅ Meets GDPR data minimization requirements
  • ✅ Protects sensitive data while maintaining format
  • ✅ Ensures regulatory compliance without sacrificing functionality
  • ✅ Reduces scope of PCI DSS compliance
  1. Enterprise Scalability
  • ✅ Handles millions of records through data partitioning
  • ✅ Provides high-performance tokenization operations
  • ✅ Supports multiple data formats and types
  • ✅ Enables efficient data processing at scale
  1. Format Compatibility
  • ✅ Preserves data format for legacy system compatibility
  • ✅ Maintains data validation rules (e.g., Luhn algorithm for credit cards)
  • ✅ Enables analytics while protecting actual data
  • ✅ Supports seamless integration with existing workflows

🔄 Supported Data Types

Original Record TypeFormat PreservationGenerated Token Format
Credit Card Number✅ (with Luhn check)Format-preserving or UUID token
Uint64/Uint32 integerFormat-preserving or UUID token
Unix timestamp recordFormat-preserving or UUID token
Text stringUUID token

🛠️ Key Features

Databunker Pro has a number of unique features:

Automatic Expiration

In Databunker Pro, expiration allows you to set a lifespan for sensitive data tokens, ensuring they automatically expire after a defined period.
// Set expiration for tokenized records
{
  "record": "4532015112830366",
  "expiration": "30d" // 30 days
}

Unique Record Support

This unique flag is used for data deduplication. It ensures that each record is saved only once, and the same token value is returned for identical records. If the original record has an expiration flag set, its expiration countdown will be reset from the beginning.
// Same input generates same token when enabled
{
  "record": "4532015112830366",
  "unique": true
}

Dual Token Generation

By default, Databunker Pro generates two tokens: one in UUID format and another in a format-preserving manner.
// Example response for credit card tokenization
{
  "status": "ok",
  "tokenuuid": "550e8400-e29b-41d4-a716-446655440000",
  "tokenbase": "4532015112830366" // Format-preserving token
}

🚀 Getting Started

# Example API call for tokenization
curl -X POST https://databunker.pro/v2/TokenCreate \
  -H "X-Bunker-Token: <access-tone>" \
  -H "X-Bunker-Tenant: <tenant-name>" \
  -d '{
    "record": "4532015112830366",
    "type": "creditcard",
    "expiration": "30d"
    "unique": true,
  }'
Output:
{
  "status": "ok",
  "tokenuuid": "550e8400-e29b-41d4-a716-446655440000",
  "tokenbase": "4532015112830366" // Format-preserving token
}

📈 Benefits

  • Compliance: Built-in GDPR data minimization
  • Security: Protected sensitive data storage
  • Compatibility: Format preservation for legacy systems
  • Scalability: Enterprise-grade performance
  • Flexibility: Multiple token format support