Dashboard

Privacy and security

Anonymous player IDs, server-only sending and key handling.

Last updated Oct 9, 2026

Player privacy

Player IDs are anonymous: p_ plus the first 128 bits of a salted SHA-256 of your project and the player's ID. Roblox UserIds and names are never sent.

Revenue is optional and private

  • Off by default. A project owner turns revenue tracking on in Settings → Revenue, and the game must also set revenue = true. Without both, no revenue is stored.
  • Enforced on our servers. If a game sends revenue for a project that has not enabled it, the API removes it before anything is written. A change to the setting takes effect within about 30 seconds.
  • Private. Revenue is visible only to the project's members. RoStructure uses it only to debug and fix the service. We do not sell or share it, and we do not use it to benchmark, rank or advertise.
  • Yours to remove. Turning tracking off stops new revenue from being stored. Delete stored revenue data permanently removes the amounts already stored for the project.

How data is protected

AreaWhat we do today
In transitThe website and API are served over HTTPS and send Strict-Transport-Security. The API accepts requests only with a valid ingestion key or the dashboard credential.
In the browserThe website sends a content security policy, X-Frame-Options: DENY, nosniff and a restrictive referrer and permissions policy. API responses are marked no-store.
KeysIngestion keys are 256-bit random values stored only as SHA-256 hashes. The plaintext is shown once, and keys can be revoked.
AccessEvery dashboard request is tied to a signed-in account, and project membership is checked on the server each time. A cookie cannot grant access to another project.
Database connectionThe API can verify the database certificate when DATABASE_SSL_CA is set.
Revenue at restEncrypted by the API with AES-256-GCM before it reaches the database. Each project has its own key, and every value is tied to its project and purchase, so it cannot be moved or altered without detection. If the encryption key is not configured, revenue is not stored at all.
Everything else at restEvents and accounts live in a database on our hosting provider's infrastructure. We have not added our own encryption for them, and we do not claim encryption at rest beyond what the provider documents.
RetentionData is kept until it is deleted. Automatic retention limits are planned. Revenue data can be deleted by the project owner at any time.

Keys and access

  • Keys are compared in constant time and can be rotated. Keys managed in the database are stored only as hashes and can be revoked.
  • Treat game code and traffic as inspectable. Never place a dashboard credential in a game.
  • Events are sent from the server only. The client cannot send or alter analytics.
  • The dashboard is private and requires sign-in.