Legal · Draft for review

Privacy policy

This policy is written to match what the platform actually does, and it is labelled as a draft because it has not yet had legal review for the jurisdictions the community will operate in.

Who is responsible

Project Vice City (“we”) is an independent community project, not affiliated with Rockstar Games or Take-Two Interactive. The community is the data controller for the account and character records described here.

What we collect and why

We collect what the community needs to operate: your account, your characters, your applications, and a record of security-relevant actions. We do not run advertising, we do not sell data, and we do not embed third-party analytics or tracking scripts on this website.

CategoryWhat it includesWhyRetention
Account detailsDisplay name, email address, account status, roles.Identifying you, verifying your email, and controlling what you can access.For as long as the account exists, plus a short period for appeals and legal obligations.
Character and application contentCharacter names and descriptors, application answers, review notes and decisions.Reviewing applications, operating the setting, and keeping decisions accountable.For as long as the community holds the record; review notes are retained with the decision.
Security and audit recordsSign-in events, sensitive account actions, request references, IP address at the time of an action.Detecting abuse, investigating incidents, and attributing administrative actions.Limited, and shorter than account data: audit records are kept for the period needed to investigate and appeal.
Game session dataSession lease, character state (position, routing bucket), connection timestamps.Running the game server authoritatively and restoring your character exactly where they were.Session records are short lived; character state is retained as part of the character.

Cookies and browser storage

The website sets one cookie: a session cookie that identifies your signed-in session. It is httpOnly — JavaScript running in the page cannot read it — and it is never stored in browser local storage. Two interface conveniences are kept in your browser’s local storage: your theme choice (light or dark), and an unfinished character application draft so you can return to it. Neither is sent to us, neither is used for tracking, and the draft is deleted from your browser when you submit it or discard it.

Where data lives and who can see it

  • Account, character, application and audit records live in the community’s PostgreSQL database.
  • Staff see only what their role permits. Administrative interfaces are role-scoped, and sensitive actions are recorded with the staff member responsible.
  • Confidential in-character information is not exposed because someone can view a profile: visibility rules are decided by the backend, not by the interface.

Your choices

  • Access: you can ask for a copy of the data held about your account.
  • Correction: you can ask for corrections to account details and characters.
  • Deletion: you can ask for your account to be closed. Some records may be retained where an open investigation, an appeal window, or a legal obligation requires it, and we will say which and why.
  • Privacy settings: character visibility and out-of-character message preferences are yours to set.

Security

Passwords are stored as hashes rather than plaintext, sessions are opaque and revocable, and authorization is decided by the backend on every request. No system is perfect: if we suffer a breach affecting your data, we will tell affected members what happened and what changed as a result.

Age

The community is intended for adults. The precise minimum age is still under review for the jurisdictions we will operate in; it will be stated in the terms of service before public registration opens, and children below that age will not be admitted.

Changes to this policy

Changes are dated and announced. Where a change materially affects how data is used, we will say so plainly rather than relying on members to notice.

Contact

A support address is configured per deployment and is not published yet. Until one exists, this page will not invent a contact route.

Last updated

Draft 1 — published with the website foundation, before public registration opens.