Regional Tenant Database

Data Residency: What Stays Where

Choose the region of your tenant database (Türkiye or EU; US planned). Today only the tenant database is region-bound — queues, logs and platform metadata are processed on the platform.

🇹🇷Turkey Region (TR)

Turkey Region (TR)

Tenant database hosted in Türkiye, intended to support KVKK data-localisation needs.

🇩🇪Europe Region (EU)

Europe Region (EU)

Tenant database hosted in the European Union, intended to support GDPR requirements.

🇺🇸United States Region (planned)

United States Region (planned)

A US-hosted tenant database is planned and not yet available.

Storage location is selectable

What You Can Choose Today

You choose where consent records are stored: a HashEntry-managed tenant database in a region, or your own PostgreSQL (BYOD). Request processing itself runs on the HashEntry platform; a full per-region platform deployment is planned but not yet available.

1. Processing

Where requests are received and processed

  • Requests, queues and logs: processed on the HashEntry platform
  • Platform metadata (accounts, plans, billing): platform database
  • Per-region processing: planned, not yet available

2. Storage / Database Model

Where consent records & documents live

  • Managed PostgreSQL: region-bound tenant database (shared database with tenant scoping by default; dedicated schema or database on eligible plans)
  • BYOD (your PostgreSQL): consent records are stored in your database; requests transit the platform
  • Signature files: stored encrypted on platform storage unless configured otherwise

How a Consent Record Travels

The steps a consent goes through and where each one takes place.

TSA receives the hash only
StepActor / ComponentProcessing ActionDestination
1Visitor Browser / AppConsent granted or contract approvedHashEntry platform (API)
2HashEntry application serversRequest queued; canonical JSON built and SHA-256 digest calculatedPlatform queue and application servers
3Timestamp Authority (TSA)RFC 3161 request containing the SHA-256 digest only (if timestamping is enabled)Configured RFC 3161 timestamp authority
4Database PersistenceRecord, digest and timestamp token saved to the selected databaseRegion-bound tenant database or your BYOD PostgreSQL

Strengthen Your Compliance Evidence Today

Start with the free plan. No credit card required.