CAMSTRIKE Privacy Policy

Effective: November 6, 2026 · Android package: net.breyes.camstrike · Web version: www.breyes.net/camstrike/play/

BREYES (“the operator”) processes information as described below to provide the features of CAMSTRIKE. This policy applies to the CAMSTRIKE Android app and web version. There is no account sign-up and no ad-serving SDK. The Android app includes Firebase Analytics for app launch statistics and ad performance measurement (section 1); the web version has no analytics SDK. The play records stored on a server are the weekly ranking in section 4-2 and the usage statistics in section 4-3. In versions that support Google Play in-app purchases, users may choose to buy weapons and restore their purchases.

1. What we process and why

• Android app usage analytics (Firebase Analytics): used to count first launches and app launches, and to measure the performance of install ads (whether people who installed from an ad actually opened the app). First-open, session, app-update and in-app purchase events (product and amount), the app instance ID, advertising ID, install source (install referrer), app version, device model, OS version, language and approximate country and region are sent to Google. Game scores, nicknames, photos, camera video and face feature values are not sent. Ad personalization signals are turned off.
• The front-facing photo you choose: used on your device to calculate face feature values and to display your own registered photo. The app does not send the original photo to the operator’s servers or to other participants.
• Camera video, face and body positions: analyzed in real time on your device during camera matches to find registered opponents and to judge aiming and hits. Video and photos are not broadcast to other people or stored on a server.
• Face feature values: a 1024-dimensional set of numbers extracted from a face, used to identify participants in the same room. After you consent to sharing, they are exchanged in encrypted form between participants’ devices. There are two ways to register. (1) Photo registration: extracted from your own photo. (2) Tag registration (room-code matches): when a user who has consented aims at a friend and shoots, that user’s device extracts the face feature values of the person aimed at from live camera video. At that moment the person in view has not yet confirmed. The values are held as a candidate in the memory of the device that extracted them. If another participant confirms by tapping “It’s me” on their own screen, the values are sent to that participant’s device and then shared among the session’s participants. If nobody confirms within 10 seconds, they are discarded. Register only your own photo, and aim only at people who have agreed to take part. Do not aim at anyone who is not a participant.
• Callsign (nickname), temporary participant identifier, room code: used to connect to a room and to show participants. You do not need to enter your real name.
• Ready status, selected weapon, shots and hits, health, score, takedowns and deaths: shared among participants to keep game progress and rankings in the same room in sync.
• Connection information: while connecting over the internet, network information such as your IP address, connection time and temporary connection identifiers may be passed to the operator’s connection servers (signaling, STUN and TURN), to Google’s STUN service and to the peers you connect with. The app does not request GPS location, contacts, phone number or advertising identifiers.

2. Retention and deletion

To request deletion, send a CAMSTRIKE data deletion request to contact@breyes.net. You can delete photos and face feature values on your device yourself as described below. You do not need to attach a face photo or feature values to your request.

• The registered photo preview and your own face feature values are held in the app screen’s memory. If you unregister with the delete-photo button in the lobby, or fully close the app, the registration is no longer used. The original photo stays in the photo storage you chose it from; the app does not delete it.
• Feature values and game state exchanged in a room are used during the game in the running memory of the legitimate client. When you leave or end the room, the connection is closed and the room state is released. Tag registration candidates are discarded within 10 seconds if nobody confirms them. The app has no feature that permanently stores this information on the operator’s servers, in files, in localStorage or elsewhere.
• Ordinary WebView cache and website data that may remain on your device can be deleted from CAMSTRIKE’s storage in Android settings, or by uninstalling the app.
• The operator keeps no face database. The operator cannot remotely delete information that another participant has kept separately, or copies made by a modified app. Share room codes only with the people you will play with.
• Names and records in the weekly ranking are kept on the server until they are deleted. See section 4-2 for how.
• Inquiry emails are kept as long as needed to respond, and content no longer needed is deleted once the inquiry is resolved. Where the law requires separate retention, information is kept within the scope of that requirement.

3. Third-party connections and processing outside Korea

In room-code matches, game data and face feature values are sent over encrypted WebRTC data channels.

Room-code matches connect through connection servers (signaling, STUN and TURN) that the operator runs on cloud infrastructure (Vultr). The signaling server passes only connection identifiers and connection information, and does not receive face feature values. If devices cannot connect directly (for example on mobile data), game data and face feature values may pass through the operator’s TURN server in encrypted form. The TURN server holds no decryption key, so it relays the data without decrypting it, and it is configured not to log the relayed content or IP addresses. If the app cannot get the settings from the connection servers, it tries to connect using Google’s STUN service, in which case connection metadata may be processed on Google’s overseas infrastructure. The app does not upload original photos or camera video to these servers or services.

The app may connect to Google Fonts to display fonts, which may send your IP address and browser request information. Installation and device information that Google Play and Android process on their own is governed by those services’ policies. The operator cannot set or delete the retention periods of external services.

The web version downloads pictures, sounds and detection model files from the Cloudflare CDN (cdn.breyes.net). Your IP address and browser request information are passed to Cloudflare and may be processed on overseas infrastructure. No photos, camera video or face feature values are sent to download these files.

Usage analytics in the Android app are entrusted to Google LLC (Firebase Analytics). The information in section 1 is sent over the internet while the app runs to Google servers overseas, including in the United States, and event data is kept for 2 months.

• Cloudflare Privacy Policy
• Google Privacy Policy
• Google Fonts privacy information

4. Permissions and your choices

• Camera: Android permission (browser permission in the web version) is requested when you try to use a camera feature. You can use the training range without allowing it, and you can revoke the permission at any time in Android or browser settings.
• Photo selection: only the files you pick with the system photo or document picker are read. The app does not request access to your whole photo library.
• Internet and vibration: used for multiplayer connections and game feedback. The app does not request microphone, location or contacts permissions.
• Advertising ID: the Android app reads the advertising ID to measure ad performance. If you delete it under Privacy › Ads in Android settings, it is no longer used. Uninstalling the app also resets the app instance ID.
• Consent to sharing: if you do not consent to sharing face feature values, you do not join camera rooms, and you can keep using the training range. To stop sharing, leave the room and delete your photo.

4-1. Optional Google Play in-app purchases

When you buy or restore a purchase, the product ID, Google Play purchase token, signed purchase receipt and a random app installation ID are sent over HTTPS to the operator’s purchase verification server. The server checks the purchase status with Google Play and issues the right to use the weapon. Card numbers and payment method details are handled by Google Play and are not collected by the app or the operator’s server. No face photos, camera video, face feature values or game scores are sent for purchase verification.

The verification server keeps a hash of the purchase token, the product ID, the purchase or cancellation status, the acknowledgement status and the time of the last update, in order to restore purchases and prevent duplicate processing. The raw purchase token, receipt and installation ID are used during verification and are not stored in the purchase database. The device stores the installation ID and the server-signed entitlement, which are deleted when you clear the app’s data or uninstall the app. On another device or after reinstalling, you can restore purchases with the same Google Play account. Google Play purchase records are kept according to Google’s policies.

You can ask to view or delete your purchase records at the contact below. The operator’s records are kept as long as needed for purchase entitlements and restore support, and records no longer needed are deleted when support ends or on a verified deletion request. Where a separate retention obligation applies, records are kept within the scope of that obligation. While connecting to the server, your IP address and request time may be processed by network infrastructure.

4-2. Weekly ranking and receiving game settings

Weekly ranking: when you finish a 60-second challenge, the run is sent automatically to the operator’s ranking server, which replays the shot log to confirm the score. The server stores the name shown in the game, a hash of a random installation ID, the run ID, mode, season, league, weapon, score, counts of takedowns, hits and shots, and the time it was saved. It does not store the raw installation ID or the shot log itself. The name, weapon, score and takedowns are visible to anyone in the ranking, so do not use your real name. No photos, camera video or face feature values are sent.

If you do not want a record in the ranking, do not play the 60-second challenge. Other modes are not sent to the ranking.

Receiving game settings: at launch, the app and web version connect to the ranking server to receive weapon balance values, sending the installation ID and a one-time encryption key. The Android app also sends a Google Play Integrity token, which the server checks with Google to confirm the app is genuine. This information is used only to answer the request and is not stored.

Connection information: to prevent excessive requests, the ranking server briefly uses your IP address in memory and does not write it to a file or database.

Deletion: tap “Delete my ranking records” on the game’s ranking screen to remove this device’s name and records for every week from the server immediately. Do this before clearing the app or website data: clearing it removes the installation ID from your device, so you can no longer delete from the game and uploaded records stay on the server. In that case, email contact@breyes.net with the name shown in the ranking, the season and the score. Reports of inappropriate names go to the same address.

4-3. Usage statistics

To improve the game, the app and web version send statistics about which features were used to the operator’s server. These statistics are not sent to Firebase or any other third-party analytics service (for Firebase Analytics in the Android app, see section 1). What is sent: a random ID used only for these statistics, the platform (Android or web), the app version, the time, the event name (app launch, camera on, start of a match connection and its type, start and end of a match, 60-second challenge or arcade stage, weapon trial, purchase offer shown and clicked, Armory opened, buy button pressed, purchase completed), and for those events the weapon, product ID, stage, win or loss, takedown and death counts, and the number of players.

The server stores only a hash of the random ID. This ID is different from the ranking’s installation ID, and the statistics are stored in a separate file from the ranking, so they are not linked to your in-game name. Names, photos, camera video, face feature values, room codes and payment details are not sent. Your IP address is briefly used in memory to prevent excessive requests and is not stored. Stored statistics are deleted after 180 days.

Turning it off and deleting: turn off “Send anonymous usage stats” on the game’s sensitivity screen to stop sending, clear the waiting records and the ID on your device, and delete this device’s statistics from the server (if you are offline, they are deleted on the next launch). This switch applies only to the statistics in this section. If you clear the app data without turning it off first, the ID is gone and those statistics can no longer be found; they are deleted automatically after 180 days.

5. Age requirement and safe use

CAMSTRIKE is intended for users aged 16 and over. Do not register or capture anyone’s photo without their consent. Do not use the app on people who have not agreed to play, such as passers-by in public places. Play in a safe place, free of obstacles and traffic hazards while you move.

6. Access, correction, deletion and contact

Send questions about the processing of personal information, and requests for access, correction, deletion, suspension of processing or withdrawal of consent, to contact@breyes.net. You can delete in-app data yourself as described in section 2. The operator will not ask you to submit on-device information it does not hold, and you do not need to attach a face photo or feature values to your request.

Privacy officer: the operator of BREYES · Email: contact@breyes.net

7. Changes to this policy

If the items processed or the purposes change, we will update the effective date and the content of this page and, where necessary, notify you again in the app and ask for your consent. This document describes how the currently released version works.