Privacy Policy
Rostructure is an analytics service for Roblox developers. It has two groups of people whose data it touches: developers, who sign in to the dashboard, and players, who play games where a developer has installed the Rostructure module. This policy covers both.
Developers (dashboard accounts)
We collect what you give us to run your account:
- Account details: your name and email address, or, if you sign in with Roblox, your Roblox account identifier and display name. Roblox does not share your email address with us, so we store a placeholder.
- Sign-in data: a salted hash of your password (never the password itself), and session records so you stay signed in.
- Project data: project names, and ingestion keys, which are stored only as one-way hashes.
We use this to provide the dashboard, keep your account secure and contact you about the service. We do not sell it.
Players (data collected by a developer's game)
When a developer installs the Rostructure module, their game servers send us gameplay events. For each event the module can send:
- a pseudonymous player ID, a one-way hash of a secret value, the project and the Roblox user ID. It lets the developer count unique players and follow one session, but it is not a Roblox user ID or username and cannot be reversed without the developer's secret;
- a session ID, the event name (for example a death or a checkpoint), the time, and the game server and build identifiers;
- the player's position in the game world when the developer asks for it, a stage identifier, and a device type (touch, keyboard, gamepad);
- any extra fields the developer chooses to attach to a custom event.
The module does not send Roblox usernames, display names, chat messages, or players' IP addresses. Pseudonymous IDs are still personal data in some laws, so we treat them that way.
The developer decides what is collected and why. We process this data on the developer's behalf to show it to them in their dashboard, and we do not use it for advertising or sell it. Developers are responsible for telling their players what they collect and for following the Roblox Terms of Use and Community Standards.
Map geometry
If a developer chooses to publish a simplified copy of their map so deaths can be drawn on it, we store that geometry for them, including a coarse height-and-material map of any terrain. Map publishing is off unless the developer turns it on.
Cookies
We use two essential cookies: a sign-in session cookie, and a cookie that remembers which of your projects is open. We do not use advertising or third-party analytics cookies.
Who else handles data
- Railway hosts the website, the API and the database, in the United States.
- Roblox verifies your identity if you choose "Continue with Roblox"; we receive only the basic profile you approve.
We share data with nobody else unless the law requires it.
How long we keep it
Developer accounts and project data are kept until you ask us to delete them. Event data is kept for as long as the project exists. We do not yet delete events automatically on a schedule, so if you want data removed sooner, ask us.
Your choices
Developers can ask to access, correct or delete their account and projects. Players whose data a game sent to us can ask us, or the developer of that game, to delete data linked to their pseudonymous ID; because we cannot tell which player an ID belongs to, we may need the developer's help to find it. Questions or requests: contact us through rostructure.com.
Security
Passwords and ingestion keys are stored as hashes, connections use HTTPS, and ingestion keys never leave a game's server. No online service is perfectly secure, and we cannot guarantee absolute security.
Children
The dashboard is for developers aged 13 or older. Players of Roblox games may be children; we collect only the pseudonymous gameplay data described above and nothing that directly identifies a player.
Changes
If we make a material change we will update the date above and, for dashboard users, tell you in the product.