Security is built around HTTPS, least privilege, explicit linking, protected infrastructure, and controlled review. Players are also expected to protect their own access and use official channels for security concerns.
Security is shared. The platform protects the stack, and players protect their own access chain.
Do not share passwords, verification codes, or recovery links. Do not trust unofficial requests for credentials or supposed shortcut verification.
Unexpected unlinks, suspicious verification prompts, unknown connected accounts, or support messages asking for secrets should be treated as red flags.
The goal is not absolute invulnerability. The goal is a layered system where identity, permissions, infrastructure, and review all reinforce each other.
The stack uses HTTPS, role-based access, protected internal routes, explicit account-linking flows, infrastructure hardening, and audit trails around high-risk actions.
No modern system can promise perfect security or zero incidents. We can promise deliberate design, review, and response paths.
If you find a real issue, we want it reported responsibly instead of exposed theatrically.
Describe what you found, how it was observed, what area it affects, and enough detail for review without causing further exposure.
Do not publicly disclose unreviewed vulnerabilities, destroy data, access another player’s information, or use the finding for leverage.
This page follows the source references captured in the Prozilli Website Legal Manual and updates as the operating systems behind the city grow.
