What this game knows about you
Shootar has to tell you apart from the other players on a field, which means it takes photographs of you. This page says what happens to them. It is written in the second person because you are the person it is about.
The game is not released. Nobody outside the project has played it and no public session has taken place. What follows describes how it is built to behave and how development sessions are run.
The photographs
Before a session, the game takes reference images of each player, at the venue, so it can recognise you during the round. Under European data protection law this is biometric data and the lawful basis is your explicit consent — you are asked, in words, and you can say no.
- Per session. The photographs are taken for one game and are not carried over to the next one.
- They stay on the phone. The reference gallery is held on the device that captured it. It is not uploaded, not backed up to a server, and not sent to other players.
- They are deleted at the end of the session. Not archived, not retained for improvement, not kept "in case".
- Your face is a separate question. Capturing your face is consented to separately from capturing your outfit and build, and you can agree to one without the other.
- Refusing is a supported answer. Kit and enrolment buy the game confidence at longer range. They are not the price of being allowed to play.
Position, and who can see it
While a round is running, your phone sends your position to the match server so it can judge shots and enforce the boundary. That data lives in the server's memory for the length of the match and is gone when the process restarts — there is no database behind it.
Other players do not receive your position except as the mode allows. In battle royale, players outside your squad are not sent your position at all until you fire, and then only for two seconds. That filtering happens on the server, before the data is transmitted, rather than in the app that draws it.
Recorded sessions
The project is being measured before it is built, and some development sessions are recorded: camera frames, positions and sensor readings, kept so the same footage can be replayed against different approaches.
- Participants are told before recording starts, and recording is what the session is for rather than a side effect of it.
- Recordings capture members of the public who are in the park and did not agree to anything. Venue notice, and a defined role for anyone reviewing the footage, are prerequisites for a session rather than follow-ups to one.
- Extracts of people are reviewed by a small named group under instruction, on a private system, and are not published, redistributed or used for any purpose other than measuring whether the game can work.
- A data protection impact assessment comes first. It is a prerequisite for the first field session. It is not yet complete, and until it is, no field session happens.
No accounts, no tracking, no list
- This website sets no cookies for visitors and runs no analytics. There is no third-party script on this page — no fonts, no tag manager, no embedded video.
- There is no mailing list and no "notify me" field, deliberately. A waiting list is personal data, and this project's own rule is that the assessment comes before the processing. When there is something worth announcing, there will be a lawful way to ask to hear about it.
- There are no accounts. Nothing on this site asks who you are.
Your rights, and who to ask
If you have taken part in a session, you can ask what is held about you, ask for it to be deleted, or withdraw consent — including during a session, in which case enrolment data is deleted immediately and you can keep playing without it.
Bitquid Srl is responsible for this project. Write to privacy@bitquid.com.
Last updated 14 August 2026.