Brazilian voter ID in privacy-first sandboxes
A Brazilian voter ID is not just an identification number, it ties a person to the Tribunal Superior Eleitoral registry, including their voting zone and polling section. Storing someone real voter ID in a test database turns that environment into a target for electoral-data exposure, a category the LGPD treats with the same care as any other direct identifier.
The database passes the same format checks as a real one, without an accidental leak from that environment exposing a real person voting zone and section.
Accessibility audits often record the session and share it with an outside vendor; a synthetic number keeps that recording from becoming another point of electoral-data exposure.
An internal manual tends to circulate through a wiki or shared drive well beyond the original team; a synthetic number in the screenshot keeps the document from becoming a source of exposure years after it was written.
Yes. The number includes two check digits calculated from the sequence and state code.
No. The number only has a plausible format, with check digits that work out correctly; it does not exist in the Tribunal Superior Eleitoral registry, so any official lookup (electoral status, zone, section) returns that the ID was not found.
No, because the value does not correspond to any real person: LGPD consent and legal-basis requirements only apply when the data being processed identifies someone, and a formula-generated synthetic number with no registry behind it does not meet that bar.
The coincidence does not change the nature of the test: the system under test is not querying the real TSE registry, so the number is still treated as a fixture value within your environment, with no action taken against the person whose ID happened to match.
Not for the synthetic number itself, both carry zero risk since neither corresponds to a real person; the risk difference only shows up on the real-data side: a leaked real CPF hits an identifier used in nearly every registration system in the country, while a leaked real voter ID hits a more restricted set of systems, but it is still full personal-data exposure either way.
Generation happens locally in the browser. Analytics receives only action, status, type and format, never the generated voter ID.