DataAlias

For teams that move fast without giving up control.

Data Alias helps you use real customer, research, and operational data with AI — without exposing the identities behind it.

Protect a fileTry sample data →

Protect the identity.
Keep the information.

Data Alias flags the sensitive fields, applies one consistent rule per column, and hands back a safe copy.

Create safe copy

Drop a file to begin
CSV, TXT, XLSX, JSON, PDF, or DOCX · Up to 10 MB · Nothing is uploaded

See exactly what was protected.

Review every selected column and protection rule before exporting.
customers.csv
1,204 rows · 12 columns · reviewed just now
4 protected columns
  • customer_nameAlias
  • emailAlias
  • phoneMask
  • api_keyRemove
  • planKeep
customer_nameemailphoneplan
PERSON_001EMAIL_001+1 ••• 555 0198Team
PERSON_002EMAIL_002+1 ••• 555 0142Free
PERSON_003EMAIL_003+1 ••• 555 0217Team
PERSON_004EMAIL_004+44 ••• 442 099Pro
Ready to export · nothing has been uploadedcustomers.safe.csv
How it works

A single pass, from
detection to safe export.

Three steps that leave rows, columns, and totals exactly where they were.
Step 01

Detect

Find names, emails, phone numbers, identifiers, and credential patterns inside structured files.

18 values detected

Name, email, and phone cells flagged for review in customers.csv.

Step 02

Protect

Replace repeated values with stable aliases, mask partial identifiers, or remove fields that should not be shared.

PERSON_001

The same name gets the same alias — in every row.

Step 03

Export

Download the safe copy with the original columns, rows, and numeric relationships preserved.

customers.safe.csv

Original columns, rows, and numeric relationships intact.

The round trip

Protecting the file is half the job. Getting the answer back is the other half.

The answer comes back with real names

One-shot scrubbers stop at the safe copy. Data Alias keeps the mapping — in your browser, never on a server — so when ChatGPT, Claude, or Gemini answers, you can turn PERSON_001 back into a name. Paste the answer or drop in the whole result file; anything the mapping cannot resolve is reported, not guessed.

Same customer, same alias — always

Within a file, across a batch, and across sessions with the encrypted vault, PERSON_001 stays the same person. Joins, repeat counts, and analysis structure survive the protection.

A record you can hand to a reviewer

A processing report listing counts, rules, and the file's fingerprint. It contains no values from the file.

Measured, not promised.

Reproducible benchmarks from Data Alias running entirely in the browser.
0B
of your file contents leave the browser
0
third-party trackers on the site
≤200K
rows supported per CSV
≈100%
exact-token restore in benchmark scope
≈100%
row and column structure preserved

Benchmark results, not customer outcomes. Network-audited on the production build (verify local processing) · restore 54/54 fixtures · structure intact across 8,165 rows · 200K is the Pro ceiling, Free holds 20K.

Local by design.

Where the work happens, what is kept, and what you approve before anything leaves.

/ 01

Local processing

The file is parsed in the browser tab you have open. It is never sent to a Data Alias server.

/ 02

No file retention

Files live in tab memory only — a refresh clears the session. Presets and the encrypted vault save only when you choose.

/ 03

Review before export

Every detected column and protection rule is reviewable before the safe copy is created.

Verify it yourself →