Player data and privacy tiers

Privacy

This page explains what we collect, why we collect it, how the privacy tiers work, and what doors players can use to access, correct, unlink, or delete their data.

Read the page Back to legal hub
🪪
No silent identity mergingDiscord, FiveM, stream, and character identities stay separate until you explicitly link them.
enforced
🗂
Tiered memorySyntra stores public, community, world, operations, and restricted data under different visibility rules.
tiered
🛠
Request paths existPlayers can ask for access, correction, deletion, export, and unlinking through structured review flows.
available
No silent identity merging enforcedTiered memory tieredRequest paths exist availableNo silent identity merging enforcedTiered memory tieredRequest paths exist available
📥 What we collect

If a player uses ZO surfaces, Discord, FiveM, applications, dashboards, support forms, or LISA, the system may create records around that activity.

Identity and account records

We may store usernames, platform IDs, Discord IDs, FiveM identifiers, linked-platform status, email address where provided, and internal Prozilli account records.

  • Platform identity does not equal character identity.
  • Separate RP characters are not automatically merged.
  • Linked-account history keeps an audit trail.

Community, gameplay, and support records

We may store application state, whitelist records, public messages, support tickets, bug reports, moderation records, dashboard status, and public-safe world activity.

  • Restricted systems stay gated.
  • Staff notes do not become public just because a player used multiple surfaces.
  • LISA logs follow the privacy tier attached to the interaction.
⚙️ Why we use it

The city only works if systems can recognize the right person, show the right tools, and keep the right kind of memory without exposing everything everywhere.

Core operation

We use data to run websites, dashboards, Discord tools, FiveM-linked features, account linking, staffing, support, moderation, and player continuity.

  • Authenticating users.
  • Showing correct dashboard or staffing status.
  • Helping LISA answer within the correct privacy boundary.

Safety, quality, and review

We may use records to investigate abuse, resolve disputes, improve systems, protect infrastructure, and maintain the continuity of the city.

  • Security review.
  • Moderation and appeals.
  • Product and workflow improvement.
🛡️ Privacy tiers and restricted data

Not everything in Syntra belongs in the same room. Data is sorted by how public or sensitive it is, and surfaces only receive what matches their role.

Player-safe tiers

Public and community tiers include what can safely be shown in player-facing routes, onboarding flows, public-safe summaries, and personal dashboards.

  • Linked-account status.
  • Application status.
  • Public-safe notifications and account state.

Restricted tiers

Operations and restricted tiers cover staff notes, tactical dispatch data, private moderation history, active investigations, private crew records, private economy records, and sensitive security logs.

  • Restricted does not become public because a player asks.
  • LISA does not have blanket permission to reveal restricted data.
  • Least privilege applies to staff and automation alike.
✉️ Your choices and requests

Players should have clear doors for privacy action instead of being forced to guess who to DM.

What you can request

You can request access, correction, deletion, account unlinking, export where feasible, or review of a disputed account link.

  • Account unlinking.
  • Account deletion or closure review.
  • Privacy request escalation when identity linking is disputed.

How review works

Some requests can be handled quickly. Others need identity verification, fraud review, or records we must retain for safety, legal, or accounting reasons.

  • We may ask for enough information to verify you.
  • Some records may be retained for security or dispute handling.
  • Privacy requests can be rejected where law or safety requires retention.
References

This page follows the source references captured in the Prozilli Website Legal Manual and updates as the operating systems behind the city grow.

R1R2R3R4R5