Proxy Mail QA

Test with made-up accounts, not masked copies of production

Copying production into staging feels like the quickest way to get realistic data. It also brings real people's details into an environment with weaker controls, and a staging job can email them. Accounts that never belonged to anyone avoid both.

Updated

QA teams often test against a copy of production with names and addresses swapped out. For sign-up and email flows that brings two problems.

A masked copy still holds real people

  • Some fields escape the masking. Free-text notes, addresses in an audit log, a second email column added last year: one missed field and real details are back.
  • Records can be matched back. Dates of birth, postcodes and order history together can point to one person, even with the name changed.
  • The law still counts it. Under the GDPR, data that has been pseudonymised is still personal data, so staging needs the same care as production. Other privacy laws take a similar view.

Staging can email real customers

A staging copy keeps working email addresses unless every one was replaced. Then a scheduled digest, a test of the password-reset flow or a bulk re-send goes out to real people, from an app they never used under that name. It happens often enough that many teams send nothing from staging at all, which also means they can’t test their emails there.

Made-up accounts avoid both

Test accounts that never belonged to anyone have nothing to leak and nobody to email by mistake:

  1. Each test creates its own address, with a persona (a name and username, plus a date of birth or a country when the form asks) and a password made for it.
  2. The address is on a test domain that only Proxy Mail QA receives, so whatever staging sends lands in a test inbox, never a stranger’s.
  3. Every test starts from a new account, so there’s no shared test user whose state drifts.

Staging can then send real email again: confirmation codes, reset links and receipts all arrive, and you can check them.

Keep it that way

  • Keep production exports out of development and staging, and say so in your team’s testing notes.
  • If staging needs a few seeded accounts in known states, make them with made-up details too, and tag them so they’re easy to find.
  • Never type a real person’s details into a test form, your own included. Proxy Mail QA’s ground rules on /security say the same.

Try it on your next sign-up test

Free plan, no credit card. Create an address and watch the code or link arrive.

Create a free accountOpen the app

Questions

Isn't masked data anonymous?

Usually not. Masking that replaces names but keeps the structure of the records is pseudonymisation, and under the GDPR pseudonymised data is still personal data (Recital 26). Truly anonymous data is hard to get from real records. A test aid, not legal advice.

Where do Proxy Mail QA's personas come from?

They're combined from lists of first and last names, with usernames and passwords made for each one. They aren't taken from real people, and their addresses are on our own test domains, so their mail can't reach anyone.

Do I still need some production data?

Sometimes, to reproduce a bug that only one account shows. Copy the smallest part you need, keep it out of shared environments, and delete it when the bug is fixed. For sign-up, login and reset tests, made-up accounts cover it.

What about the people already in my staging database?

If staging was ever loaded from production, check whether it can still send email. A job, a digest or a password-reset test can reach real inboxes from there.

Built your app with an AI tool? Pick yours