Security model

Read-only by design.

The portal receives a small, deliberately approved copy of selected Raven City data. It is not connected to the game server and has no facility to issue commands, call server events, update the game database, or alter player data.

What leaves the city

Character identity, job and custom-business summaries, balances, owned vehicles, property summaries, progression, licences, unpaid bills and selected civilian-career statistics. No website username or password is read from or sent to the game server.

What never leaves

Passwords, IP addresses, Rockstar/FiveM licence identifiers, inventories, item storage, private messages, phone contents, precise positions, gang data, medical records, police reports, evidence, staff notes and full transaction histories are excluded from the publisher.

How the boundary is enforced

• The FiveM resource only makes outbound HTTPS requests.
• It exposes no HTTP handler, callback, export or network event for the website. The local /ucp [code] player command only initiates an outbound claim and snapshot.
• The portal uses a separate database containing only published snapshots.
• Local passwords are stored only as PHP password hashes in the isolated portal database.
• The website generates a short-lived code tied to the signed-in portal account. Ownership is created only when the authenticated publisher submits that code with the character currently being played.
• The ingest endpoint has write access only to portal tables and returns an empty response body with a success or failure status.