Privacy Policy

This English text is a translation of the Japanese original. If the two differ, the Japanese version prevails.

This page shows the same text as the Legal section in the app.

1. Operator and Scope

This Policy applies to information handled through the Service by its operator, Izaya Kajimoto, an individual (the "Operator"). Inquiries and complaints about the handling of personal information, and the requests described in section 10, are accepted at ketsuinrpg@gmail.com. The Operator's address will be disclosed without delay upon request.

2. Information We Handle and How We Obtain It

Through your input, game operations, storage on your device, and communication with the server, the Service handles the following information.

(1) Player ID, display name, birth year and month, authentication token, transfer ID, and a hash of the transfer password.

(2) Progress information such as level, inventory, equipment, quests, settings, play time, and co-op status.

(3) The versions of the Terms of Service and Privacy Policy you agreed to, the date and time of agreement, and the app version at that time.

(4) The content of inquiries (what you entered in the in-app contact form and, if you contact us by email, your email address and the content of the email).

(5) Records kept for server operation and security, such as IP addresses, dates and times, and response results of communications.

(6) Diagnostic logs for investigating problems, including the app version, platform, device model name, a temporary identifier created for each launch, and records of app activity. See section 14 for details.

(7) Recognition records, which are numerical statistics of seal recognition results (such as the number of times each seal registered or timed out, the average time, and practice statistics). See section 5 for details.

(8) Play statistics: in-game events such as progress through the introduction and sorties, level, the number of seal casts and quick casts, the number of gacha draws (amounts are not included), settings such as graphics quality, and performance (fps), together with device information added automatically by the analytics service, an identifier unique to the device, the IP address of the communication, and the approximate country or region estimated from it. See section 15 for details.

(9) The type and message of errors (exceptions) that occur in the app, which are sent as part of the diagnostic log in section 14. In addition, the Operator may receive from Apple or Google records of app crashes (such as the device model name, OS version, and where the crash occurred) and beta feedback sent through TestFlight (such as comments, screenshots, and device and app information). See section 6 for details.

(10) Magatama balances and changes, records of shop purchases and receipt, records of the purchase, validity period, and receipt of monthly passes, and records of gacha use. For purchases through the App Store or Google Play, the transaction information used to verify the purchase (such as the transaction number, the product, the purchase token and other information identifying the transaction, the dates and times of purchase and refund, and whether the test environment was used). The Operator does not receive the payment method information itself.

(11) About me text, friend code, friend requests and relationships, block settings, guild membership, guild names and notices, records of reports (who reported, where the report was made [friends, guild, party, or co-op], the reported content, and the Operator's response), and records of account suspensions (when an account was suspended and reinstated, and the reason noted by the Operator). A report record includes a copy of the reported user's name and About me text at the time of the report (content entered by another user).

(12) Invite codes, invitation relationships (which invite code was entered), milestones reached, and records of gift codes and of items received from the gift box.

(13) Account deletion requests and copies of deleted characters.

3. Camera Video and Hand Recognition Data

The live video from the front camera is processed in real time in temporary memory on your device for seal recognition. Live video and still images are not stored in permanent storage on your device and are not sent to the servers of the Operator or any third party. They are not used for face recognition, personal identification, or advertising. The recognition results, namely the type of seal and whether it registered, are used as game operations and may be sent to the server to the extent needed to save progress, check hidden techniques, or synchronize co-op play. Recognition records (section 5), which are numerical statistics of the recognition results, are also sent to the server. Hand positions and shapes (landmark coordinates) and the features calculated from them are not sent outside your device. The sequence of seals you form is never sent to or shown to other players.

4. Purposes of Use

We use information to: confirm your identity and register your device; check age requirements; provide, save, and restore game progress; transfer data; synchronize co-op play; check hidden techniques on the server; provide magatama, paid items, and gacha and confirm transactions; grant bonuses and invite rewards; provide friends, guilds, and player-versus-player battles; review content entered by users, respond to reports, and suspend accounts; prevent misuse; investigate failures and security issues; respond to inquiries; comply with the law; adjust game balance and improve seal recognition accuracy using recognition records (section 5); understand drop-off and difficulty in the introduction and each stage, adjust game balance, and improve graphics quality and performance using play statistics (section 15); and investigate problems using diagnostic logs (section 14) and records of app crashes. We do not use information for advertising or targeted advertising. If a character name or display name contains prohibited words, we may refuse it or replace it with a default name ("Tabibito", Japanese for "traveler"). A character name that contains prohibited words is not accepted, and you will be asked to enter another name. The display name registered before you create a character is replaced with the default name without being refused.

5. Recognition Records

For game balance adjustment, improving seal recognition accuracy, investigating problems, and responding to inquiries, the Service sends numerical statistics of seal recognition results ("recognition records") to the server together with game records, and stores them on the Operator's server linked to your account. Recognition records consist of: for each basic seal, the number of attempts and of successful registrations, the number of registrations near the confidence threshold, the number of times a seal timed out without registering, the average time until registration, and the average time until moving to the next seal; for seal practice, the number of attempts and successes, the longest streak, and the average time per seal; and, in practice, the number of times a different seal registered instead of the target seal, for each combination. Camera video, still images, audio, hand positions and shapes (landmark coordinates), and the features calculated from them are not included in recognition records and are neither sent nor stored. Recognition records are not used as the basis for rewards, in-game transactions, or battle results. They are sent only for users whose registered birth year and month confirm that they are 18 or older; for other users, recognition records are kept only on the device. In addition, in the beta (pre-release) version, seal recognition scores and normalized features may be written to records on the device to investigate misrecognition. These detailed recognition records on the device are not sent outside the device and are not included in the diagnostic log described in section 14.

6. Outsourcing, Provision to Third Parties, and Display to Other Participants

When the Operator outsources server operation, data storage, delivery, handling of inquiries, or similar work, it has the contractor handle information only to the extent necessary and supervises it appropriately. Currently, we use Amazon Web Services for the game server and database, Amazon S3 and CloudFront for delivering notices and downloadable content, and Google LLC's email service (Gmail) for receiving and storing email inquiries. In co-op and player-versus-player battles, information such as your display name, equipment and appearance, position, actions, and battle status is shown to the participants in the same session. In friends and guilds, your display name, level, and similar information are shown to the other users of that feature. Your About me text is shown only to users who are mutual friends with you. Users who invite others are shown only the number of people who entered their invite code and the number who reached each milestone; the names and account identifiers of those people are not shown. We do not provide personal data to third parties except with your consent, where required by law, where necessary to protect a person's life, body, or property and it is difficult to obtain your consent, or where otherwise permitted by law. The current build does not include any external advertising SDK. As an external analytics SDK, we include Unity Technologies' analytics service (Unity Analytics) for play statistics (section 15), and we entrust Unity Technologies with handling that information. Unity Technologies handles the information under its contract with the Operator and within the scope of the Operator's instructions. The Operator does not give Unity Technologies your player ID or display name. The app does not include any mechanism that sends crash reports to an external service. If you have allowed sharing with app developers in your device settings, records of app crashes are sent by your device's OS to Apple (iOS) or Google (Android), and those companies provide them to the Operator. Beta feedback sent through TestFlight also reaches the Operator through Apple. Purchases through the App Store and Google Play are processed by Apple and Google respectively, and the Operator receives transaction information from each company to verify purchases, grant items, and handle refunds. Apple's and Google's handling of this information follows their own terms and privacy policies.

7. Handling Outside Japan

The Operator's game server and database are currently located in Amazon Web Services facilities in Australia (Sydney). If the location changes, this section will be revised. Australia has a federal privacy law (the Privacy Act 1988). When notices and downloadable content are delivered, communication information such as your device's IP address may be processed at delivery locations in countries or regions near you. No player identifier of the Operator is sent when downloading content or notices. When personal data is handled outside Japan, the Operator follows the applicable laws, provides necessary information such as the destination country, its system, and protective measures, and obtains consent or ensures appropriate contracts and supervision. Play statistics (section 15) are provided to Unity Technologies, which is headquartered in the United States, and are stored mainly in data centers in the Netherlands (European Union). They may be handled in the United States and other countries by Unity Technologies and its subprocessors (such as Google LLC and Snowflake Inc.). Email inquiries may be stored on the facilities of Google LLC, which is headquartered in the United States, in the United States and other countries. The European Union has the General Data Protection Regulation (GDPR), and Japan's Personal Information Protection Commission has designated it as a region with a system equivalent to Japan's. The United States has no comprehensive federal privacy law, but has state laws such as the California Consumer Privacy Act. As a processor under its contract with the Operator (a data processing addendum), Unity Technologies takes measures such as limiting the purposes of use, security safeguards, and supervision of subprocessors. Information on each country's system is available on the website of the Personal Information Protection Commission.

8. Retention and Deletion

Progress and settings are saved and synchronized automatically by the app; the app does not provide manual save, import, or a reset of device data. This does not prevent you from deleting the app or clearing its data through the OS. Progress and authentication information and recognition records (section 5) on the server are kept while you use the Service and for as long as needed to process deletion, and are deleted when your account is deleted. Account deletion is carried out after a 7-day grace period from the request, during which you can cancel it. When an account is deleted, its About me text, friend relationships, blocks, invite codes and invitation relationships, records of bonuses received, and records of inquiries are also deleted. Reports sent by that user and reports about that user are also deleted. However, to enforce the limit on the number of invite rewards, the inviting user's records keep the fact that a reward was given, in a form that does not identify the invited person. Used individual gift codes keep their used status to prevent reuse. Records of purchase and gacha transactions are kept for 3,650 days from receipt to confirm transactions, prevent misuse, and handle disputes; when an account is deleted, they continue to be kept with the account identifier replaced by a different identifier. Guild fund ledgers and audit records are likewise kept with identifiers replaced. Records of the in-app contact form are kept for 1,095 days from creation. Email inquiries are deleted once they are no longer needed after being handled. Report records are deleted once 180 days have passed since the Operator finished handling them. Records of account suspensions are deleted together with the account when the account is deleted. If you delete only a character, a copy of that character is kept for 30 days to respond to inquiries and is then deleted. Diagnostic logs are kept for 14 days and are deleted on the server after that period. Unsent diagnostic logs on the device are kept in limited temporary memory and may be lost when the app ends or in similar cases. Records of communications with the server (access logs) are kept within a storage limit to investigate failures and misuse, and are deleted starting with the oldest. Database backups are kept only for recovery from failures and are deleted starting with the oldest. In Unity's analytics service, records of individual events in play statistics (section 15) are kept for 13 months (Unity's default) and then deleted automatically. The metrics aggregated from them and the per-device records are kept until deletion is requested. When an account is deleted, the app asks Unity to delete the play statistics. If the app cannot make that request, the Operator will ask Unity to delete them if you request it through the procedure in section 10. Retention of crash records and beta feedback provided by Apple and Google follows each company's rules.

9. Security Measures

The Operator takes measures appropriate to the nature of the information and the risks, such as restricting access rights, hashing credentials, protecting communications, rate limiting, minimizing logs, backups, and supervising contractors. Upon request, the Operator will explain its security measures to the extent that doing so does not compromise security.

10. Disclosure, Correction, Suspension of Use, Deletion, and Other Requests

You or your agent may, in accordance with the applicable laws, request notification of the purposes of use of retained personal data, disclosure, correction, addition, deletion, suspension of use, erasure, suspension of provision to third parties, and disclosure of records of provision to third parties. Requests are accepted at ketsuinrpg@gmail.com. After confirming, by necessary and reasonable means, that the request comes from you or your agent, the Operator will respond in accordance with the law. To confirm your identity, the Operator may ask for information that identifies your account, such as your player ID or transfer ID. Disclosure is made by the method you request, such as providing electronic records or delivering a document. If that method is difficult, the Operator will tell you so and make the disclosure in writing. If the Operator does not comply with all or part of a request, it will tell you so and try to explain the reason.

11. Consent and Changing Permissions

You can change camera permission in the OS settings. Even if you deny it, you can play with quick cast, which casts techniques without forming seals. Collection and upload of diagnostic logs, collection of recognition records (section 5), and sending of play statistics (section 15) are managed by the operator as a whole, and there is no switch for each user. You can request disclosure, deletion, and similar actions for recognition records and play statistics through the procedure in section 10. If you withdraw your required agreement to the Terms of Service or this Policy, you can no longer use the Service, but this does not affect your right to request deletion of saved data and similar actions. Requests about the handling of information or for deletion are accepted at ketsuinrpg@gmail.com.

12. Minors

The Service is not intended for people under 13. People under 13 cannot start using the Service. If you are under 18, review this Policy with your parent or legal guardian and obtain their consent. If, because of your age or region of residence, you cannot give valid consent on your own, use the Service only after your parent or legal guardian has agreed to this Policy. Recognition records (section 5) and play statistics (section 15) are sent only for users whose registered birth year and month confirm that they are 18 or older.

13. Data Breaches, Revisions, Language, and Contact

If the Operator becomes aware of a leak, loss, or damage of personal data, or the risk of such an event, it will investigate the facts and the extent of the impact and take measures to prevent it from spreading and recurring. Where the law requires a report or notification, the Operator will report to the Personal Information Protection Commission, notify the affected persons, and take other required actions. When this Policy changes, the Operator will announce the changes and the effective date, and where agreement is required again, such as for a change in the purposes of use, you will be asked to agree again the next time you start the app. This Policy is written in Japanese. Translations into English or other languages are provided for reference, and if a translation differs from the Japanese version, the Japanese version prevails. Inquiries about this Policy are accepted at ketsuinrpg@gmail.com.

14. Diagnostic Logs

To investigate problems and improve quality, the Service automatically collects system, battle, and network records and the app's diagnostic logs, and sends them to the server over an authenticated connection. In the beta (pre-release) version, information, warning, and error records are collected; in the public version, mainly warning and error records. The type and message of errors (exceptions) that occur in the app are also included. The amount collected and the sending interval are managed by the operator, and there is no setting for users to switch this. The items sent are the diagnostic message, the app version, the platform, the device model name, a temporary identifier created for each launch, and the time elapsed since launch. Camera video, hand positions and shapes, recognition scores, and the seal sequences of hidden techniques are not included in diagnostic logs. Credentials and similar information are removed or masked before sending, and detailed records of where an error occurred (stack traces) are not sent. Sending requires authentication, but the only identifier in the records stored on the server is the temporary per-launch identifier, and the records are not linked to your account. The player ID identified through authentication is used only to limit the number of sends and is not recorded. Your display name and those of co-op participants are replaced with masked text before sending, and any line containing a name too short to mask is not sent at all. Collection and sending of diagnostic logs do not begin before you agree to the Terms of Service and this Policy. If communication is not possible, logs are held in a limited queue and sent again later; records may be lost when the limit is exceeded or when the app ends. Diagnostic logs on the server are deleted after the retention period (14 days). For the detailed recognition records on the device, see section 5. Diagnostic logs are sent to the Operator's server and are separate from play statistics (section 15), which are sent to Unity's analytics service.

15. Play Statistics

To understand drop-off and difficulty in the introduction and each stage, adjust game balance, and improve graphics quality and performance, the Service sends information on how the game is played to Unity Technologies' analytics service (Unity Analytics) ("play statistics"). What is sent: passing each step of the introduction and whether you continued without the camera; accepting story quests and receiving their rewards; whether you finished reading or skipped scenes; the start and result of stages (cleared, knocked out, timed out, or returned; time taken; number of enemies defeated; number of seal casts and quick casts; recommended level and your level; and whether it was co-op); level-ups; the number of gacha draws and whether they were free; settings for graphics quality, frame rate, hub display, and whether the recognition camera is on; and the average and minimum fps for every 5 minutes of play. In addition, Unity's SDK automatically adds the SDK and app versions and identifiers, the device model name, the OS version, language and region, the CPU and GPU names, the number of cores, memory size, screen size, battery level, an identifier unique to the device, an identifier Unity creates for each device, and the IP address of the communication and the approximate country or region estimated from it. Camera video, still images, audio, hand positions and shapes, seal sequences, hidden techniques, display names, the Operator's player ID, credentials, and payment amounts are not sent. Play statistics are sent only for users who have agreed to consent version 5 or later of this Policy and whose registered birth year and month confirm that they are 18 or older, and are not sent for any other users. Play statistics are not used as the basis for advertising, rewards, in-game transactions, or battle results. Handling by Unity Technologies is described in section 6, handling outside Japan in section 7, and retention and deletion in section 8.

16. List of Information Sent Outside Your Device

The main information the app sends outside your device, the recipients, and the purposes are as follows.

(1) Game, authentication, and saving: sent to the Operator. Authentication information, progress, results of operations, transaction information for App Store or Google Play purchases, communication information, and so on. To provide and save the game, verify purchases, grant items, and prevent misuse.

(2) Diagnostic logs: sent to the Operator. Diagnostic messages (including errors that occur in the app), the device model name, the app version, a per-launch identifier, and so on (section 14). To investigate problems.

(3) Downloading notices and content: sent to a delivery provider (Amazon CloudFront). Communication information such as the IP address. To deliver content and operate the delivery facilities.

(4) Play statistics: sent to Unity Technologies (Unity Analytics). In-game events, identifiers, device information, the IP address, and so on (section 15). To analyze how the game is played and how well it performs.

(5) In-app contact form: sent to the Operator. What you entered, your player ID, the app version, and the device type. To investigate problems and improve quality. Diagnostic logs, recognition records (section 5), and play statistics are not sent before you agree to the Terms of Service and this Policy. The app itself does not send records of app crashes. Records that your device's OS sends to Apple or Google, the purchase process in the App Store and Google Play, and feedback sent through TestFlight are handled through those companies' own systems and follow their terms and privacy policies (section 6). Handling by the companies that receive the information is described in sections 6 and 7, and retention periods in section 8.