Privacy
Last updated 8 November 2026.
This notice explains how Monterosa Productions Ltd ("Monterosa", "we") collects and uses personal data on Gamestage, and how to ask us about it. It is written under UK data protection law: the UK GDPR and the Data Protection Act 2018.
Who we are
Gamestage is a Monterosa product, run by Monterosa Productions Ltd, company number 04716325, registered in England and Wales at 3B The Plaza, Floor 3, 100 Old Hall Street, Liverpool L3 9QJ.
We are registered with the Information Commissioner's Office under reference Z9899012.
Who is responsible depends on whose data it is:
- Game data: the game's creator is the controller. That is everything about the people who play a game built on Gamestage: plays, answers, scores, leaderboards, player records and, where the creator switches it on, Signal analytics. Monterosa is the creator's processor: we host and process the data on their instructions, and use it only for the purposes the creator approves in their contract with us. Questions about a specific game go to whoever made it, and we will help them answer.
- Everything else: Monterosa is the controller. That covers Gamestage accounts, fan accounts on the gamestage.ai Hub, applications, quote requests, call bookings and visits to gamestage.ai.
Who to contact
Email dpo@monterosa.co with any question about your data, or to make any of the requests below.
Say what you are asking for. To help us find your data, give us the name of the game you played, or the email address you used with us. We reply within one month. If a request is complicated we may take up to two further months, and we will tell you inside the first month if that happens.
If you played a game
The game's creator is responsible for your data, and their own privacy notice applies to it. This section says what Gamestage does with it on their behalf.
What Signal collects
Signal is the engagement analytics Gamestage offers creators. It runs only on a paid plan, only where the game's creator has switched it on, and only if you have given consent. Without consent it records nothing.
With consent, it records:
- A random identifier stored in your browser, so repeat visits can be counted as one person rather than several. It is not linked to your name.
- The pages of the game you opened, their titles, and the page that sent you there.
- That you activated something, and enough to say what: the kind of element, its role, its label, and a stable name the game gave it.
- That a form was submitted, and when.
- When a session started and ended.
- Where a game already signs you in with a Monterosa account, the account identifier, so activity can be joined up across sessions.
What it never collects
- What you typed. Field values are never captured.
- The text on the page. Signal records the labels of buttons and links, not what the page says.
- Keystrokes, mouse movement, scrolling, or screen recording.
- Any device fingerprint.
Lawful basis
The game's creator decides the lawful basis for their game's data. Signal runs only on your consent, which the game asks for on its creator's behalf. You can withdraw it at any time in the game's own privacy or cookie controls, and the collector stops immediately. Withdrawing it does not affect anything collected before you did.
We keep a record of your IP address at our servers for 90 days, to stop one machine flooding the game. We do this as part of running the game for its creator, and it is not joined to the analytics above.
Analytics a creator connects
A creator can also send their game's events to their own PostHog or Google Analytics account. That happens only after you give consent in the game, the events go straight from your browser to the creator's account, and the creator's own privacy notice covers it. Monterosa does not receive or hold that data.
What we store on your device
Signal uses your browser's local storage, not cookies. It keeps a random identifier and, if the network fails, a short queue of unsent events so they are not lost. Clearing your browser's site data removes both.
If you have a Gamestage account
To give you an account and run your games we hold:
- Your email address and name, from however you signed in. Sign-in is handled by WorkOS, and by Google if you chose that route.
- Your GitHub username, once you link GitHub. We need it before your first deploy because your game lives in a repository, and so we can send issue reports to that repository.
- Your workspace: your games, what you deployed and when, and your usage against your plan's limits.
- A record of the actions you took: deploys, links, changes to limits, games suspended or woken. We keep this so that if something is disputed there is an account of what happened, and so we can spot one person running many accounts to get around a plan's limits. It includes the network address the action came from.
Our lawful basis is our contract with you for the account itself, and our legitimate interest in security, abuse prevention and keeping an accurate record for the rest.
Your Gamestage sign-in for the command line tool is held in your computer's secure credential store, such as the Mac Keychain. Where that is not available, or a write to it fails, it is kept in ~/.gamestage/credentials.json instead, a file only your user account can read, and the command line tool tells you when that happens. It is never stored in your project and never given to an AI coding assistant working in your repository.
If you apply, join the waiting list, ask for a quote or book a call
Applying for an account or joining the waiting list. We hold your name, work email, company, role, what you would like to build, your answer to the age question, and whether you want Gamestage news by email. One box lets us contact you about your application, and you must tick it to apply. The news box is separate and optional. We store this with your account records on Amazon Web Services, tell the Gamestage team in Slack, and send your confirmation email through Resend.
Asking for a quote. We hold your name, email, company, the plan you asked about and anything you wrote. We record it as a deal in Attio and tell the Gamestage team in Slack.
Booking a call. The booking page at gamestage.ai/call shows Cal.com's booking form. Cal.com holds what you enter there and sends the calendar invite.
Our lawful basis is our legitimate interest in answering you and assessing your application. Gamestage news by email is sent only if you tick the box, and you can unsubscribe from any of those emails.
If you have a fan account on the gamestage.ai Hub
The Hub on gamestage.ai is where fans play our own demonstration games. You can play without an account. If you create one:
- Sign-in is handled by Clerk, including Google sign-in if you choose it. We receive your name, email address and profile picture from it.
- We confirm you are 16 or older before the account is created.
- We record which games you played, your scores and the points in your Hub balance, so they are there next time you sign in.
Our lawful basis is our contract with you for the account. To delete a Hub account, email dpo@monterosa.co from the address you signed in with, and we delete it within 30 days.
Cookies and tracking on gamestage.ai
We set these cookies on gamestage.ai. None of them is used for advertising.
wos-session: keeps a creator signed in to Stage. Lasts until you sign out or the session expires.__Host-gs_returning: remembers that this browser has had a Gamestage account, so it offers Sign in rather than Sign up. It holds no identity. Lasts 1 year.gs_workspace,gs_space: remember which workspace and space you last chose in Stage. Lasts 90 days.__Host-creator_age_ok: remembers that a creator answered the age question. Lasts 30 minutes.__Host-fan_age_ok: remembers that a fan answered the age question. Lasts 180 days.__Host-fan_oidc_state,__Host-fan_oidc_return: protect a fan's sign-in from forgery, and return them to the page they started on. Lasts 10 minutes.__Host-fan_token,__Host-fan_signed_in: keep a fan signed in to the Hub. Lasts 1 hour, renewed while you use it.__Host-fan_uid: signs a fan back in on this device. Lasts 30 days, or until you sign out.__Host-fan_profile: shows a fan's own name and picture on their profile page. Lasts 1 hour.__Host-fan_games: remembers which games a fan chose to play while signed in. Lasts 1 year.__Host-fan_reselect: after a fan signs out, lets them sign in as somebody else. Lasts 10 minutes.__Host-gs_site_consent: remembers your choice in Privacy settings. Lasts 1 year.
These are needed for the site to work, so they do not ask for consent.
Snitcher identifies which company a visit to our public pages came from, using the network address of the visit. It sets its own cookie, snitcher_device_id, and keeps a few snitcher_ entries in your browser's local storage. It runs only on the public pages, and only after you allow marketing in Privacy settings, at the foot of every page. You can change that choice at any time.
We also count clicks on a few buttons, such as Sign up and the install command. That count holds the button's name, the page and the day, with no cookie, no identifier and no network address.
How long we keep things
| What | How long |
|---|---|
| Signal analytics events | 25 months from collection, or sooner if the game's creator asks |
| Account and workspace data | Until you ask us to close the account, then up to 30 days |
| Hub fan accounts | Until you ask us to delete the account, then up to 30 days |
| Applications, waiting list entries and quote requests | Until you ask us to delete them, or 2 years after we last heard from you |
| Action records and audit trail | 6 years, so a dispute can still be answered |
| Network addresses held for abuse prevention | 90 days |
Close your account
You close your account by emailing dpo@monterosa.co from the address on the account. There is no button for it in Stage. We close it within 30 days of your email.
When we close it, every game stops being playable, and we delete:
- Your games' files.
- Your datasets, including sources you switched on.
- Your workspace and its game records.
- The link between your sign-in and the workspace, so signing in again starts a new, empty account.
- Your players' plays, scores, leaderboards and player records, for every game except Mystery and Arcade games. We cannot delete a Mystery or Arcade game's player data this way yet, and we tell you in our reply what we still hold.
We keep the audit trail: the record of every change to your account and games, and who made it. It keeps your email address and the network address each change came from, and closing the account does not remove them. We keep it so that a dispute about your account or games can still be answered.
Closing the account does not remove your sign-in account at WorkOS, your address in our email service, Resend, any data-provider keys you stored with us, or your games' projects in Monterosa Interaction Cloud. If you want any of these deleted, say so in the same email.
Delete one game's player data
Archive the game, then email dpo@monterosa.co and name it. We delete its players' plays, scores, leaderboards and player records within 30 days of your email. The game's record stays in your account. This works for every game except Mystery and Arcade games, for the reason above.
Who else sees it
We use other companies to run the service. For a game's data they are sub-processors: they act on our instructions, which follow the creator's, and may not use the data for their own purposes. Each row is a service that receives something from Gamestage that can identify a person.
| Who | What for | What it receives |
|---|---|---|
| WorkOS | Creator sign-in and accounts | Name, email, sign-in events |
| Sign-in, where you choose it | What Google sign-in shares | |
| Clerk | Fan sign-in on the gamestage.ai Hub | A fan's name, email and picture, where they create a Hub account |
| GitHub | Linking a game to its repository, and issues | GitHub username, repository |
| Vercel | Hosting the Gamestage website | Every request to gamestage.ai, including network address |
| Amazon Web Services | Running games, storing their data and account records, and the email and secrets services behind them | Game plays, player identifiers, account records, applications |
| Monterosa Interaction Cloud | The content and live updates of every game | A fan's connection to a game, and a player identifier |
| Monterosa Analytics, run on Amazon Web Services and Databricks | Signal analytics, only after consent | The events described above |
| Databricks | Processing analytics, and the points ledger | Analytics events and player identifiers |
| Resend | Sending account and confirmation emails | Email address and the email's content |
| Slack | Telling the Gamestage team about new applications, quote requests and faults | Name, email, company and role you gave us |
| Attio | Keeping track of quote requests | Name, email, company and what you asked |
| Plane | Keeping track of bug reports and suggestions | What you wrote, and a name only if you chose to add one |
| Cal.com | Booking a call | Whatever you enter on the booking form |
| Snitcher | Identifying which company a visit to our public pages came from, only after you allow it | Network address and the pages visited |
Services that give us data but receive nothing personal from us are not listed: the sports data suppliers Sportmonks and Fantasy Premier League receive only our own requests for fixtures and statistics.
We do not sell personal data, and we do not share it for advertising.
Where it goes
Some of the companies above operate outside the United Kingdom, mostly in the United States. Where data leaves the UK we rely on the safeguards UK law provides for that, including the UK addendum to the standard contractual clauses and, where it applies, the UK extension to the EU-US Data Privacy Framework.
Your rights
Under UK law you can ask us to:
- Show you what we hold about you.
- Correct anything that is wrong.
- Delete it.
- Stop or limit what we do with it.
- Hand it over in a portable form, or send it to someone else.
- Object to processing we do on the basis of legitimate interests.
- Withdraw consent at any time, where consent is what we relied on.
Email dpo@monterosa.co. We do not charge for this.
If you are asking about a specific game, its creator is the one responsible, so ask them first. If you would rather, or cannot reach them, tell us and we will pass your request to the creator and help them answer it.
Children
Gamestage accounts are for adults: we ask a creator to confirm they are 18 or older before we keep their application, and before we open a quote request or show the booking calendar.
A fan must confirm they are 16 or older before they can create a Hub account, and before we keep a name they type into a feedback form. Under 16, the account is never created and nothing from the attempt is kept.
Playing a game needs no account. A player is given a random identifier and may pick a name and a picture from our own lists; they cannot type a name, give an email or upload a photo. Where a game needs a stricter age restriction it is the creator's job to declare one, which our platform then enforces. If you believe we hold data about a child and should not, email us and we will remove it.
Complaints
Complain to us first, at dpo@monterosa.co.
You can also complain to the Information Commissioner's Office, the UK's data protection regulator, at ico.org.uk or on 0303 123 1113. Complaining to us does not affect your right to go to them.
Changes
If we change how any of this works we will update this page and change the date at the top. If a change affects what we do with your data, we will also email account holders before it takes effect.