dbslice — Column Mapping

## Getting Started

5 steps to generate your anonymization config

1

### Connect to your database

Enter your PostgreSQL URL and click Introspect Schema. Only metadata is read — no row data is accessed.

2

### Apply a compliance profile

Click GDPR, HIPAA, or PCI-DSS to auto-map columns matching the profile's rules. You can apply multiple and override any suggestion.

3

### Review columns

For each column, choose:

Keep — passes through unchanged
Anonymize — replaced with fake data
NULL — set to NULL (passwords, tokens)
4

### Choose providers

When you select Anonymize, pick a provider from the dropdown. Each provider generates a specific type of fake data:

`email` fake email `name` full name `phone_number` phone `ssn` SSN `ipv4` IP address `year_only` HIPAA date `hipaa_zip3` Safe Harbor ZIP `credit_card_number` PAN
5

### Generate & export

Click Generate Config to create a `dbslice.yaml`. Download and use:

dbslice extract --config dbslice.yaml --seed "table.column=value"

`Ctrl+Z` / `Cmd+Z` to undo · `Esc` to close modals

## Connect to a database

Enter your PostgreSQL connection URL in the sidebar and introspect the schema to begin mapping columns.