DataAlias

PostgreSQL + Data Alias: Protect a PostgreSQL export before an AI tool sees it

Data moves from PostgreSQL into Data Alias as a file you export yourself.

Why use PostgreSQL with Data Alias

A quick export from a production database is often the most accurate data a team has — and the most identifying. Protecting it first keeps real customers out of the AI conversation.

How it works

Data Alias doesn't connect to PostgreSQL. A PostgreSQL connection would need database credentials and a path for your rows that runs through something other than your own browser. So the export stays your step: export the data from PostgreSQL, drop the file into Data Alias, and everything after that happens in your browser.

What it does

  • Read a CSV export with a header row in your browser
  • Alias IDs consistently, so they still join within the file
  • Leave numeric columns untouched by default
  • Keep row order, column order and empty cells

How to use it

  1. 1

    Export the query to CSV

    In psql: \copy (SELECT …) TO 'result.csv' WITH CSV HEADER. Select only the columns the question needs.

  2. 2

    Drop the file into Data Alias

    The file is read in your browser tab. It is not uploaded anywhere.

  3. 3

    Review the identifier columns

    IDs, names and emails are suggested for aliases. Numeric measures are left as they are unless you choose otherwise.

  4. 4

    Download the safe copy

    Row order, column order and empty cells stay as they were. Use it in an AI tool, or keep the mapping to restore real values later.

What moves where

What reaches Data Alias servers
Nothing from the file.
What reaches PostgreSQL
Nothing. Data Alias never contacts it.
What stays in your browser
The original file and the alias mapping.
Permission you grant
None. There is no account link.

Limits worth knowing

  • Detection is pattern-based and suggests rather than decides. Review the columns and free text before you rely on the safe copy.
  • Files are limited by your plan's size and row limits — see pricing.

Your questions, covered

Get started today

Protect a file
Why isn't there a direct PostgreSQL connection?

A PostgreSQL connection would need database credentials and a path for your rows that runs through something other than your own browser. A file export keeps your original data out of our servers entirely.

Is anything sent to PostgreSQL?

No. Data Alias has no connection to PostgreSQL and makes no request to it.

Will the same value get the same alias everywhere?

Within one file, yes — the same email becomes the same alias in every row, so joins and counts still work. To keep aliases identical across several files, use an alias vault.

Data Alias reduces exposure risk but cannot guarantee detection of every sensitive value. Every transfer passes the same review as a download — check the result before you send it. How connected services are handled.