What we handle and what we don't.
Data Alias is a browser-based utility. Files you drop into the workspace are parsed and transformed inside your own browser tab. File contents, detected values, and generated safe copies are not uploaded to a Data Alias server or shared with any third party.
Local processing
Parsing and anonymization run in JavaScript executed by your browser. No worker, edge function, or API endpoint receives your file. File contents are never written to localStorage or IndexedDB. The single exception is rule presets: if you explicitly save a protection-rule preset, its configuration — column types and transform choices only, never data values — is stored in your own browser's localStorage. Presets contain no cell values, and nothing is saved unless you choose to save it.
Accounts and billing data
Data Alias currently works without accounts. When accounts and paid plans are enabled, the server will store only:
- Your email address (used for magic-link sign-in).
- Your plan entitlement (free or pro).
- Payment events reported by the payment provider. Checkout and card handling happen entirely on the provider's side — your card data never touches Data Alias.
Even with an account, the following never leave your browser: your files, cell values, column names, filenames, and the actual data referenced by your transformation rules. Signing in changes what the server knows about your plan — not what it knows about your data, which remains nothing.
What we don't collect
- File names of uploaded files.
- File contents or detected cell values.
- Analytics events tied to your data.
- Session-replay recordings.
What we do use
Standard access logs at the hosting layer may record IP addresses and request paths for the purpose of operating the site. These do not include file contents.
Contact
Privacy questions: hello@dataalias.app.