Intake
Validate format, encoding, size, and content before processing.
TEST DATA MANAGEMENT
DovaTDM
Discover sensitive fields and transform real files into protected, repeatable test data without persisting the source file on disk.
- Formats
- CSV, JSON, TXT, XML, LOG
- Upload limit
- 15 MB
- Encrypted storage
- PostgreSQL + pgcrypto
- Policies
- 7 reusable profiles
PRODUCT CAPABILITIES
A controlled path from intake to audit
Each module supports one stage of the de-identification process and preserves operational traceability.
Discovery
Profile fields and detect sensitive categories through names, patterns, and validation.
Policies
Select deterministic masking, redaction, tokenization, pseudonymization, and date-shifting rules.
Masking
Generate a de-identified output while processing the source in memory.
Audit
Review execution reports without exposing original sensitive values.
Configuration
Inspect required and optional infrastructure status from one place.
DE-IDENTIFICATION WORKFLOW
Six verifiable steps
- ReceiveAccept a supported UTF-8 file up to 15 MB.
- DiscoverIdentify email, phone, payment, identity, address, date, account, IP, and free-text risks.
- ChooseApply the policy that matches the test scenario and required utility.
- TransformRun deterministic de-identification in memory.
- ProtectEncrypt jobs, reports, and outputs in PostgreSQL.
- DeliverDownload the protected file and review its audit evidence.
POLICY CATALOG
Protection profiles for different test needs
Safe Harbor DefaultGeneral deterministic protection.
Strict RedactionBroad removal when fidelity is secondary.
GDPR PseudonymizationStable relationships for repeatable tests.
PCI Payment DataReinforced payment and account protection.
Analytics High UtilityConsistent pseudonyms and shifted dates.
QA Format PreservingUseful structure for functional testing.
Irreversible TokenizationNon-reversible tokens for identifiers.
GDPR and PCI profile names describe technical controls; they are not legal certifications by themselves.
SECURITY BY DESIGN
Protection across the data lifecycle
The production architecture limits exposure at the browser, application, database, and backup layers.
- TLS through Nginx with secure session cookies, CSRF protection, CSP, and role checks.
- The application and PostgreSQL listen only on the VM loopback interface.
- The source is processed in memory; encrypted documents retain the protected output and audit report.
- Encrypted daily backups use restricted permissions and seven-day retention.
PRODUCT DOCUMENTATION
Explore the complete product scope
The Product Explorer covers capabilities, workflow, policy selection, architecture, use cases, and acceptance criteria.