Privacy Policy
Last updated November 2, 2026. Starline Media Inc. ("Starline Media", "we", "us") runs RoMirror.
RoMirror helps Roblox game studios run their games: bug reports, tickets and appeals, moderation, analytics and their economy. This policy explains what we collect, why, where it is kept, and the choices studios and players have.
Who this covers
- Studios: the people and companies who sign up for RoMirror and connect a game.
- Players: people who play a studio's game and send a report, a request for help or an appeal from inside it.
For player information, the studio decides what RoMirror is used for in its game, and we process that information on the studio's behalf and on its instructions. Players with questions about a game should also contact that game's studio.
What we collect from studios
- Account details: your Roblox user id, username and display name, from signing in with Roblox, and the team members a studio adds. If you pay, or email us, also your email address.
- Your game's scripts and the layout of its places, but only if you let RoMirror read your code. The RoMirror Studio plugin sends them when someone on your team opens the place in Studio. You choose what it may read and can leave folders out.
- If you connect your Roblox account: the permissions you approve on Roblox's own consent screen, and the information those permissions allow, such as your game's details, its analytics, and its list of bans. If you choose to add a Roblox API key instead, it is stored encrypted. We never ask for your Roblox password.
- What your team does in RoMirror: bug cards, notes, replies, bans and their reasons, settings, and a log of who did what and who opened what.
- Billing: your plan and what Stripe tells us about your payments. Stripe handles card details, and we never see or store them.
- Basic technical information to keep the service working and secure, such as IP addresses and request logs.
What we collect from players
Only when a player sends a report, a request for help or an appeal from a game that has RoMirror installed, or when the game reports an error:
- The player's Roblox user id, username and display name, and how old their Roblox account is.
- What they write in a bug report, a request for help, or a ban appeal, and the account an appeal is about.
- The kind of device (computer, phone, tablet, console, VR), the place and version of the game, and the server it came from.
- Errors the game's servers and players' devices throw, grouped by message and script. These are about the game's code, not the player.
- Only if the studio has switched it on: the saved game data of a player who reported a bug, read for that bug only. We only ever read it, never change it, and delete what we read after 7 days.
We do not collect players' real names, email addresses, contact details, location, or payment information. We never ask players for a password.
How we use it
- To give the studio its tools: use AI to group reports into one card per bug and name them, always, as this is how the board works; show tickets and appeals with the player's history in that game, carry out bans the studio makes, and deliver the studio's replies and "it's fixed" messages back to the player inside the game.
- When the studio's team uses them: AI answers to questions about the game, and AI drafts of replies for a person on the team to review. These work from the game's reports, tickets, errors and numbers.
- Only if the studio lets RoMirror read its code: to work out why a bug happens from the game's own code and errors (and, when the studio allows it, the save of a player who reported it), to answer questions about the code, and to review updates. Nothing is sent to a player or banned without a person on the team choosing to.
- To keep RoMirror secure, fix problems, and count use against the studio's plan.
What we never do
- We never use a studio's code or its players' information to train any model, ours or anyone else's.
- We never share one studio's information with another studio. What RoMirror learns about a game stays with that game.
- We never link a player across different games, and never send player information to social, chat or advertising platforms.
- We never sell personal information.
Who else handles it
We use a small number of service providers, each only to run RoMirror:
- Amazon Web Services, in the United States, for hosting, storage and key management.
- Anthropic and OpenAI, to process player reports and tickets, the team's questions, and the game's code if the studio lets RoMirror read it. They receive only what a task needs, under terms that do not allow them to train on it.
- Roblox, for signing in, when a studio connects its account, and to deliver bans and messages inside the game.
- Stripe, in the United States, to take payments and manage subscriptions.
We may disclose information if the law requires it, to protect someone's safety, or as part of a sale or merger of our business, in which case this policy continues to apply.
Where it is kept and how it is protected
Everything is stored encrypted, on AWS in the United States. Each game has its own encryption key. By default nobody at Starline Media can open a studio's data, and every access is logged. A studio can see its own log of who opened what.
How long we keep it
- Game errors: 14 days.
- Messages waiting for a player in the game: 30 days.
- Bug reports, tickets, bans and the log: while the studio keeps its game in RoMirror, up to the limits of its plan.
- When a studio deletes a game in RoMirror, everything for that game is deleted. When a studio deletes its workspace, all its games are deleted. Backup copies are gone within 30 days.
Your choices
- Studios can change what the plugin reads, stop RoMirror reading their code, disconnect Roblox, and delete a game's data or their whole workspace at any time.
- Players can ask the game's studio, or us, to see or delete what RoMirror holds about them. We honor erasure requests, including the ones Roblox passes on to developers.
- Depending on where you live, you may have more rights, such as correcting your information or objecting to how it is used. Contact us and we will help.
Children
Many Roblox players are under 13. RoMirror only collects what a player chooses to send from inside the game and what is listed above, never contact details, and the studio controls how it is used.
Changes
If we change this policy in a way that matters, we will tell studios in RoMirror before it takes effect.
Contact
Starline Media Inc. Email david@starlinemedia.com.