DATPROF Privacy

DATPROF Privacy is a proprietary database masking and generation tool. It can mask existing database values or generate new rows while preserving constraints; DATPROF Subset is a distinct product for database subsetting.

Sources reviewed

When should you consider it?

Best suited to database teams that need reusable masking templates, constrained synthetic rows, deterministic values and separation of project development from deployment.

Editorial fit assessment based on the sources below.

What are the limits?

Privacy should not be credited with Subset product functionality by default; Runtime is separate, runtime deployment is not available for every database, and some workflows require elevated database permissions.

Which capabilities are documented?

Synthetic generationDocumented · source

De-identification / maskingDocumented · source

Subsetting / subset planningNot verified

Data virtualizationNot verified

Seeded replay, scopedGeneration with explicit seed

Documented means a cited vendor source describes this scoped capability. Not verified means the reviewed evidence cannot establish it. Neither is a hands-on test result.

How is it deployed and licensed?

Windows GUI project authoring supports direct database deployment; runtime packages can separate development from execution, but DATPROF Runtime is separate and options vary by database.

Documentation refers to a purchased license key; no public price or edition pricing was found in the reviewed vendor sources.

Sources and scope

DATPROF Privacy Manual
Official definition as proprietary database masking and generation tool; synthetic data creation.
Source checked: 2026-10-01
Data Generation - DATPROF Privacy
Generation for existing tables with constraints; foreign-key generation; deterministic generation and reproducible output using seed value.
Source checked: 2026-10-01
Tool Overview - DATPROF Privacy
Separate development and runtime deployment; Runtime is a separate product; availability varies by database.
Source checked: 2026-10-01
Requirements - DATPROF Privacy
Database-specific requirements and permissions, demonstrating deployment/connection boundaries.
Source checked: 2026-10-01
DATPROF Subset Manual
Separate DATPROF Subset product for database subsetting; supports product-boundary correction.
Source checked: 2026-10-01

What should you verify in a proof of concept?

Your database version, schema constraints and target formats.
The exact product, edition, deployment and license entitlements.
Your business assertions and the meaning of repeatability for your output.
A failed run, cleanup and a repeat run on controlled inputs.