Privacy Policy
株式会社RE-IDEA ("we", "us") sets out below how user information is handled in "Mono Zukan Battle" (the "Service"), a game where the things you photograph become cards.
1. Information we do not collect
We do not collect personal information such as names, email addresses, phone numbers, location, or contacts. There is no account registration. The web version shows no ads. The apps (Android and iOS) show rewarded video ads only when the user chooses to watch one. The information Google collects for ads is described in "6. Ads in the apps".
2. Camera and photos
- A card is made by capturing a single frame from the camera opened inside the app. The camera is used only when the user presses "Take".
- Identifying the object in the photo (image recognition) is done on the device. Photos are never sent to us or to any outside service.
- A reduced-size version of the photo is stored only on the device, as the card's picture.
- Only when the user presses "Save image" or a share button is the card image passed to the device's share feature. The user chooses where it goes.
- We ask users not to photograph people's faces.
3. Information stored on the device
Collected cards, encyclopedia records, the number of days played, settings, and similar data are stored only on the device. They can be deleted by deleting the app or by clearing the browser's site data.
4. Information sent to our servers
- Usage counts: To count which screens are used, we send fixed kinds of action names and a random number created on each device (used only to measure the rate of return visits). This number cannot be used to identify an individual user.
- World discovery order (optional): Only if the user chooses "View (register)", we send the card's number (a value made by reducing the photo to 8×8 colors), type, and rarity. Photos and card names are not sent. This can be turned off at any time from the home screen.
5. Challenges and online battles
- Challenges: Only when the user presses "Send a challenge" is a link created containing the card's name, the object's name, level, rarity, 8×8 colors, and similar values. Photos are not included. The user chooses whom to send the link to.
- Online battles: Only when the user creates a battle room or opens a room link does the app connect to a communication service (Supabase). On connecting, it sends only an entry signal and a single-use number; after teams are chosen and the battle begins, card values and each turn's moves are exchanged with the opponent's device. Photos and device identifiers are not sent, and nothing is stored on the server.
- Waiting for a challenge reply: When the user presses "Send a challenge", the sender's device also waits on the same communication service so it can be notified if the recipient chooses "Battle the sender online". While waiting, it sends only a signal and a single-use number; card values are sent, within the same scope as above, only after the battle begins. Device notifications are shown only if the user allows them.
6. Ads in the apps
The apps use Google LLC's advertising service (Google AdMob / Google Mobile Ads SDK) to show rewarded video ads. The web version shows no ads.
- When ads are shown: Only when the user presses a button and chooses to watch a video (for example, to keep everything picked up in the dungeon after being defeated, or to receive the once-a-day charm). There are no ads that appear automatically during play and no banner ads. Every feature can be played without watching ads.
- Information Google collects: For ad delivery, measurement, analytics, and fraud prevention, Google collects the following information directly from the device. We do not receive this information (we receive only aggregated figures, such as the number of ad views, that do not identify individuals).
- Device identifiers (advertising ID — the iOS IDFA only if the user allows tracking, and the Android advertising ID — app set ID, and similar)
- IP address (used to estimate the general region)
- Interactions with ads, such as views, taps, and video playback
- Diagnostic information such as app launch time, hangs, and crashes
- Consent: In regions where consent is required by law (such as the European Economic Area and the United Kingdom), Google's consent screen is shown at launch, and no ads are loaded until the consent check is complete. Where required, choices can be changed at any time from "Privacy choices" in the app's settings.
- Tracking permission on iOS: On iOS, Apple's tracking permission prompt (App Tracking Transparency) is shown after the consent check. Only if the user allows it is the advertising ID used for ads tailored to the user. The game can be played without allowing it, and the choice can be changed at any time in the device's Settings.
- Advertising ID on Android: The advertising ID can be reset or deleted in the device settings (Google > Ads).
- Ad content: Ads are limited to content suitable for all ages (G).
- For how Google handles information, see the Google Privacy Policy and How Google uses information from sites or apps that use our services.
7. Provision to third parties
Because we do not collect personal information, we do not provide it to third parties. The communications described above use the services of Supabase (Supabase, Inc.) and Vercel (Vercel Inc.) for storing and relaying data. For ads in the apps, Google collects information directly from the device as described in the previous section.
8. Use by children
The Service can be played by people of any age. We do not collect personal information from children either. Ads in the apps are limited to content suitable for all ages (G).
9. Changes to this policy
If we change this policy, we will announce it on this page.
10. Contact
株式会社RE-IDEA
Email: info@re-idea.jp