Email verification tests are usually designed around correctness: trigger the message, open it, click the link, and assert that the account is active. Privacy is often added later, after somebody finds an address in a screenshot or a token in a CI log.
That order are backwards. A test mailbox is part of the application's data boundary, even when it contains only synthetic users. A disposable address can still identify a run, expose product behavior, or be reused by the wrong test. The useful question is not whether the data is real. It is whether each system in the test path needs to see it.
The browser is part of the data boundary
Modern browser tests cross several boundaries: the page, the test runner, a mailbox API, the application logs, and CI artifact storage.…