I’m building an anonymous incident reporting platform using Voxel.

For anti-spam and moderation reasons, users must authenticate (Google login), but their real identity must never appear publicly.

My approach is to auto-generate a system-controlled codename (e.g. Agent-4821) on registration and use that consistently as the public-facing identity. The goal is:

– WordPress display_name = generated Agent ID
– Voxel voxel:name profile field = same Agent ID
– Real name fields wiped or ignored
– Users cannot edit the name field

I want to confirm the safest and most future-proof way to keep voxel:name and display_name in sync so that:

– Voxel widgets always render the Agent ID
– No Google profile name ever leaks (even briefly)
– Updates to Voxel won’t override or cache the original name

Is there a recommended hook, filter, or internal pattern you suggest for enforcing a system-managed display name across profiles and frontend templates?