Account security and privacy controls

In production, one email should normally have one main role: Gentleman, Lady, Agency, Club or Admin. Mixing roles creates workspace confusion and can expose the wrong navigation or permissions.

Admin access should use the dedicated operator login and must stay separated from normal client/provider login. Admin routes should never redirect operators to a public password form by mistake.

For QA, yes. A single Gmail inbox can receive mail for aliases like name+lady1@gmail.com or name+club1@gmail.com. For production users, use real account emails and a clear role.

Yes. Privacy controls should support correction, export or deletion requests according to platform policy and applicable law. Some safety, billing or legal records may have retention rules.

Only authorised operator or review roles should access verification documents. Public users, clients and normal business accounts should not see private verification files.

Use a private email, strong password where applicable, avoid sharing login links, keep role access separate and report suspicious account activity quickly.