pairmoni

Last updated: October 3, 2026

This Privacy Policy (the "Policy") describes how "Rosenzu Wars" (the "App") handles user information. The operator handles user information appropriately in accordance with this Policy.

1. No account

The App does not use account registration or login. We never ask you to enter personal information such as your name, email address, phone number, or date of birth.

The only things the App asks you to enter are a "display name" (free text, optional), a challenge name (free text, optional), and your answer to each question (a hiragana string).

Subscription payment is made through Apple's App Store, and the operator never receives credit card numbers or other payment details (see 2.9).

2. Information we collect

2.1 Information stored on your device

Your display name (the name shown on the leaderboard and challenge screens)
Your play records (number of correct answers, time taken, question conditions, date and time played, and the characters you typed for each question)
Stations you have correctly answered, and your rating and rank (a number that rises and falls with your rated-match results, and the rank derived from it)
The number of times you've played that day, the number of times you've increased that count by watching an ad, and the usage counts described in 2.10 (used to enforce the daily limit)
An identifier key: a random identifier (UUID) the App generates per device. It contains no information that identifies you personally, such as your name or email address, and it is not your device's advertising identifier or hardware identifier. Section 2.5 explains in detail how this key is used.

※ All of the above is stored only on your device, and uninstalling the App deletes it all together, including the identifier key. Because this information is included in whole-device backups (such as iCloud backups), it carries over to a device restored wholesale from a backup. If you are moving to a new device other than by restoring from a backup, please use the "transfer code" described in 2.5.

2.2 Information sent to the operator's server (rated matches)

Every time you finish a set of ten questions, the App sends the result to the operator's server. The information sent and stored is as follows.

Your display name (sent blank if you haven't set one)
The record of that single play session (the questions asked, the characters you typed for each question, the time taken on each question, whether you pressed "I don't know" (「わからない」) or timed out, the total time, the date and time played, and the data version)
The identifier key (see 2.1 and 2.5)

We send the characters you typed so that scoring can be redone on the server side — this is an anti-cheating measure so that a score your device claims is never placed on the leaderboard as-is; it is not for analysing what you typed. The App does not send whether you were right or wrong; the server re-scores your answer from the characters you typed.

The characters used for scoring are not retained on the server after scoring. For rated matches, all that remains on the server is the question, whether you were correct, and the time taken (challenge letters in 2.4 are handled differently).

The information sent never includes your name, email address, device advertising identifier, contact details, or location.

In addition, we send usage counts related to the daily limit and to the ad and subscription screens (see 2.10).

You can play the App even when you have no connectivity. Results that couldn't be sent are kept on your device and sent together the next time a connection is available.

2.3 Aggregating question difficulty

The operator aggregates the difficulty of each question from the correct/incorrect answers that are sent. What is aggregated is a per-question figure — how many times that question was asked and how many times it was answered correctly — summed across all users. The aggregated difficulty figures are delivered to users' devices and used to adjust the difficulty of questions offered. This delivery contains only per-question figures; it never includes other users' display names, records, or identifier keys.

2.4 Leaderboard and challenge letters

Leaderboard: for top-ranked users, their display name, rating, rank, and placement are shown to other users of the App. The leaderboard can be viewed even if you haven't set a display name. Your own placement is shown on your own screen even if you are not in the top ranks.
Challenge letters: creating a six-character passphrase and giving it to someone lets you compete with them on the same ten questions. The challenge screen shows the challenge name (optional, set at creation) and, for each participant (you and your opponent), their display name, number of correct answers, the characters typed for each question, whether each question was correct, the time taken per question, and the total time.

Please note: the contents of a challenge letter are not visible only to "people who have solved it." Anyone who knows the six-character passphrase can see the challenge name and the display names, typed characters, and results of everyone who has taken part, even if they themselves haven't solved it. Only give the passphrase to people you're comfortable having see its contents.

A challenge letter becomes invalid two weeks (14 days) after it is created. Unlike rated matches, the characters you type for a challenge letter are stored on the server for the duration of its validity and continue to be shown to anyone who knows the passphrase. This differs from rated matches, whose typed characters are discarded after scoring — please keep this in mind.

2.5 Handling of the identifier key

The App issues a random identifier per device (the "identifier key") and attaches it to communications in the following cases: when sending a result, when displaying the leaderboard, when creating or displaying a challenge letter, and when sending the usage counts described in 2.10.

The identifier key is used for the following purposes.

Grouping results sent from the same device together and accumulating your rating (so that one row on the leaderboard corresponds to one consistent user)
Preventing the same result from being counted twice if it is sent twice
Preventing the same user from re-solving the same ten questions repeatedly in a challenge letter
Serving as one signal among others to curb a large volume of records being posted in a short time
Grouping the usage counts in 2.10 as belonging to the same device on the same day

The identifier key is not displayed on the App's screens and is not shown to other users (only your display name and results are shown to other users). The identifier key is never used to track you across other companies' apps or websites. We do not pass the identifier key to our advertising provider (Google) or to our subscription management service (RevenueCat).

This key is stored only on your device. The operator's server stores play records tied to the key (see 2.2), but there is nothing that links the key itself to your name or contact details.

Deleting the App deletes this key and your on-device records together. If you reinstall, a new key is issued and your rating and rank start over from the beginning.
This key is never automatically shared or synced to another device. However, because it is included in whole-device backups (such as iCloud backups), it carries over, along with your records, to a device restored wholesale from a backup. If you are changing devices other than by restoring from a backup, please use the "transfer code" described below.
This key is never synced in real time to a cloud service such as iCloud.

The App can issue a "transfer code" (「引き継ぎコード」; eight characters, valid for 24 hours from issuance, usable once) for situations such as changing phones. Using this code on a new device causes that device to be treated as having the same key — that is, the same user — as the original device, and your rating and records carry over. Please issue the code before deleting the App on your old device (once deleted, there is no way to transfer your records).

Using the code does not invalidate the key on the original device. This means that after using the code, both devices can be used in parallel as the same user.

Note: a version distributed for a short time in August 2026 (build 15) stored this key in iOS Keychain and synced it via iCloud. Later versions move that key back onto the device on launch and delete the copy in Keychain. Your rating and records are not lost, and no synced key remains.

2.6 About your display name (please note)

Your display name is shown to other users (on the leaderboard and challenge screens). Please do not enter information that could identify you or anyone else, such as your real name, school or employer, or contact details.
Setting a display name is optional. If you haven't set one, your row on the leaderboard or a challenge letter is shown without a name.
You can change your display name from within the App at any time. Changing it replaces the name shown on the leaderboard the next time results are sent. The display name already shown on past answers in a challenge letter does not change.

2.7 Technical information from communications

When communicating with our server, technical information such as the originating IP address may be processed temporarily by our server provider (Cloudflare, Inc.) to carry out the communication, prevent abuse, and maintain stable operation. The operator does not use this information in a way that links it to an individual user.

2.8 Advertising (Google AdMob)

The App uses Google LLC's advertising service "Google AdMob" to show a video advertisement (watching it to completion adds one more play for that day).

An advertisement is shown only on the screen you reach after using up your free plays for the day, and only if you choose to tap "Watch an ad to play again" (「広告を見てもう1回」). If you don't tap it, no advertisement is shown, and subscribers are not shown this prompt at all.
We request advertising only in non-personalised form (not based on your interests).
The App does not request iOS App Tracking Transparency. As a result, under iOS's own mechanism, the device advertising identifier (IDFA) is not made available to the App or to Google.
Even so, for non-personalised advertising, Google may acquire and process identifiers related to your device or the App (such as the vendor identifier, IDFV), your IP address, your device model/OS/language settings, and information about how an advertisement was shown, viewed, or interacted with, for the purposes of delivering ads, capping how often the same ad is shown, preventing fraud, and aggregating ad data. Google's handling of this information follows Google's own privacy policy.
The App does not perform ad effectiveness measurement (attribution across other companies' apps or websites).

If you are in the European Economic Area (EEA), the UK, or Switzerland, the first time you are about to see an advertisement, we ask for your consent regarding advertising through Google's consent management platform (User Messaging Platform). You can change your choice at any time from "Ad privacy settings" (「広告のプライバシー設定」) in the App's Settings screen.

Google's privacy policy: https://policies.google.com/privacy
How Google uses information from partner apps: https://policies.google.com/technologies/partner-sites

2.9 Subscriptions (in-app purchases)

The App offers an auto-renewing subscription (monthly or yearly) that removes the daily play limit and increases the number of challenge letters you can have open at once.

Payment is made through Apple's App Store. Your name, credit card number, and other payment details are handled by Apple, and the operator never receives them.
We use RevenueCat, Inc.'s service to check subscription status and restore purchases. RevenueCat receives an anonymous user ID that RevenueCat issues for the App, your purchase history/receipts (product purchased, period, expiry, etc.), and technical information such as device model, OS, app version, country/region, and IP address. This anonymous user ID is separate from the identifier key in 2.5, and the operator does not link the two.
Whether you are subscribed, and your subscription's expiry, are not sent to the operator's server. However, as described in 2.10, we do send the number of times a subscription became active on the paywall screen (successful purchase or restore), along with the identifier key and date. We do not send the product, price, or period.
You can cancel or change your plan from the subscription management screen in the App Store (iOS Settings).

RevenueCat's privacy policy: https://www.revenuecat.com/privacy
Apple's privacy policy: https://www.apple.com/legal/privacy/

2.10 Aggregation of usage counts

To confirm that the daily limit, advertising, and subscription mechanisms are working as intended, the App sends the following events' counts for that day, together with the identifier key and date, to the operator's server.

The number of times the "you've used up today's plays" screen was shown
The number of times an ad prompt was shown, the number of times an ad was started, the number of times it was watched to completion, and the number of times it failed to load
The number of times the subscription screen was opened, and the number of times a purchase or restore succeeded on that screen and a subscription became active

We only send counts — never which advertisement was shown, how you interacted with it, or the product, price, or period of any purchase.

2.11 Information we do not collect

The App does not collect your location, contacts, photos/media, microphone, or camera.
The App (the operator) does not collect the device advertising identifier (IDFA). As described in 2.8, because we do not request tracking permission, it is also not provided to our advertising provider.
The App does not use third-party analytics tools that track behaviour (such as Google Analytics or Firebase Analytics).
The App does not track you across other companies' apps or websites. It does not request iOS App Tracking Transparency.

3. Purpose of use

Providing the App's functions, such as asking questions, scoring, and displaying records
Calculating rating and rank, and displaying the leaderboard
Providing challenge letters (passphrase-based matches)
Aggregating per-question difficulty and adjusting question difficulty based on it
Showing advertisements (2.8) and granting extra plays for having watched one
Providing subscriptions, checking subscription status, and restoring purchases (2.9)
Verifying and improving the daily limit, advertising, and subscription mechanisms (2.10)
Detecting and preventing fraudulent record submissions, keeping the App stable, fixing bugs, and improving quality and features

4. Third-party disclosure and external services

The operator does not provide user information to third parties except as required by law. However, to the extent necessary to provide and operate the App, the following external services are entrusted with handling information. As a result, information may be processed overseas to the extent necessary.

Cloudflare, Inc. (provision of servers and databases)
Google LLC (advertising delivery via "Google AdMob," and management of advertising consent in Europe and elsewhere via "User Messaging Platform"; see 2.8)
RevenueCat, Inc. (management of subscription status and restoring purchases; see 2.9)
Apple Inc. (subscription payment via the App Store; see 2.9)

Google, RevenueCat, and Apple each handle information in accordance with their own privacy policies.

Note that the display name, rating, rank, and placement shown on the leaderboard are disclosed to other users of the App. Anyone who knows a challenge letter's passphrase can see the participants' display names, typed characters, results, and time taken (see 2.4).

5. Retention period

Your display name, play records, correctly-answered stations, rating and rank, and identifier key are stored on your device until you delete them or uninstall the App. Uninstalling deletes all of these from your device.

Rated-match records stored on the server are retained for as long as needed to provide the leaderboard (the characters you typed are discarded after scoring and are not retained). Even if the question data version is revised, records from a prior version are retained as that version's leaderboard.

A challenge letter (its passphrase, name, the ten questions it contains, and participants' answers) becomes invalid two weeks after creation.

The usage counts in 2.10 are retained for as long as needed to verify and improve the relevant mechanisms.

Information obtained by Google, RevenueCat, and Apple is retained according to each company's own privacy policy.

6. Security measures

The operator takes the necessary and appropriate measures to prevent the leakage, loss, or damage of the information it holds, and otherwise to keep it secure.

7. Access, correction, deletion, and so on

You may request access to, correction of, or deletion of your own information held by the operator.

You can delete all on-device data (your display name, play records, correctly-answered stations, rating and rank, and identifier key) yourself, at any time, simply by uninstalling the App. You do not need to contact the operator.

If you wish to have records stored on the server (leaderboard, challenge letters, and the usage counts in 2.10) deleted, please contact the operator. Note: records sent from the same identifier key are grouped together, but because the App has no account system, the operator has no means of linking an identifier key to a specific individual's name or contact details. The identifier key is also not shown on the App's screens, so you yourself have no way of telling us your key. If you would like your records deleted, please tell us information that can identify the record in question, such as your display name, the date you played, and approximately what your results were. We may be unable to act on a request if we cannot confirm it comes from the person concerned.

※ Because deleting the App also deletes the identifier key, if you would like records on the server deleted, please contact us before deleting the App, or note down your display name, the date played, and similar details beforehand.

※ For information obtained by Google, RevenueCat, and Apple under 2.8 and 2.9, please contact each company using the method described in its own privacy policy. If you are in the European Economic Area, the UK, or Switzerland, you can change your consent regarding advertising at any time from "Ad privacy settings" in the App's Settings screen.

※ The "per-question difficulty" described in 2.3 is a per-question figure obtained by summing correct/incorrect answers across all users, and contains no information that identifies any individual user. It is therefore excluded from the scope of deletion requests.

8. Children's use

The App may be used regardless of age, but as noted above, your display name and challenge-letter answers are shown to other users, and the App contains advertising (2.8) and subscriptions (2.9). We ask parents and guardians to make sure children do not enter their real name or similar information, and do not give a challenge letter's passphrase to strangers.

9. GDPR and other overseas law

The App respects data protection laws in various countries, including the EU's General Data Protection Regulation (GDPR).

Data minimisation: the App handles only the minimum information needed to provide its functions, and does not collect information that directly identifies you, such as your name, email address, or contact details. Characters typed during a rated match are used only for scoring and are not retained after scoring.
Handling of the identifier: the identifier key alone cannot identify a specific individual, but because it groups records sent together, we treat it as potentially constituting personal data (an online identifier) under the GDPR, and handle it within the scope of this Policy. This key is stored only on your device, is never synced to the cloud, and is deleted when the App is deleted. It is also never passed to our advertising provider or subscription management service.
Legal basis for processing: processing of information involved in providing the leaderboard, challenge letters, and subscriptions is carried out to the extent necessary for providing the service the user requests (performance of a contract) and for legitimate interests (preventing fraudulent submissions, adjusting question difficulty, and verifying our mechanisms through the usage counts in 2.10). Use of on-device information for advertising in the European Economic Area, the UK, and Switzerland is based on the consent described in 2.8, which can be withdrawn or changed at any time from "Ad privacy settings" (「広告のプライバシー設定」) in the App's Settings screen.
Data management: you can delete all on-device data, including the identifier key, by uninstalling the App. See Section 7 for deletion of records held on the server.

10. Revisions

The operator may revise this Policy in response to changes in law or in the service. Where there is a material change, we will give notice within the App or by another method the operator considers appropriate.

11. Contact

For inquiries regarding this Policy, please contact us at the address below.

Contact: support@pairmoni.com