Privacy Policy
えびです ぷりぷり〜 handles information related to Isekai Nine as follows.
1. Information stored on your device
Game progress, team and player information, settings, and images you select are stored on your device so that you can play and resume the game. Information is sent outside your device through the error reporting, Google Play Games, Web demo record submission, and App first-victory submission features described below. The developer does not collect or use this information for advertising or tracking users’ behavior.
Stored information is retained so that you can continue playing, and you can delete it.
2. Error reporting (Sentry)
The App uses Sentry to send error and crash information so that the developer can investigate and fix problems and improve the App’s stability. Reports include the time of the error, App version and build, operating system and platform, in-game year, types of scenario, screen and operation, error category, whether saving completed, save validation checks, the location of the problem in the program, and a small number of recent operation types.
Sentry reports do not include team or player names, text you enter, selected images, entire saves, complete player data, authentication information such as Google Play Games player IDs, or advertising identifiers. Sentry is not used for screen recordings, session replay, or behavioral analytics. IP addresses are not attached to error reports, and Sentry is configured not to store them. However, connection information such as the source IP address is processed when providing the service.
“Send error information” (不具合情報を送信) is enabled by default. You can turn it off under Settings (設定) → About This Game (このゲームについて) → Send error information (不具合情報を送信), and continue playing with reporting disabled. If you turn it back on, reporting resumes on the next launch, and crash information kept on your device while offline may be sent. Turning reporting off does not delete information already sent.
Error information is processed and stored in Sentry’s United States region. Individual error and crash reports are retained according to the plan in effect when Sentry receives them: 30 days on the free Developer plan, or 90 days during the trial and on Team and Business plans. Information is deleted after its retention period expires. Aggregated issue information and service backups may have different retention conditions. See Sentry’s retention periods, backup retention conditions, Privacy Policy, and service data information and legal terms for details. You can request deletion or ask about its handling through the contact form below.
3. Google Play Games (Android version)
The Android version uses Google Play Games for achievements and cloud saves. At launch, the App attempts to connect automatically according to your Google sign-in settings. When connected, the App obtains your player ID and display name from Google to show your connection status and manage records and saves for your account. You can continue playing with saves on your device if you do not connect or a connection cannot be established.
While connected, the App sends unlocked achievements to Google.
Automatic backup is enabled by default. While connected, the App saves each team’s progress, recovery saves, revealed candidates, historical records, team name, player information, and selected player images to Google Play Games Saved Games, together with unlocked scenarios, achievements, and best records. These backups also include an identifier for each installation of the App, save timestamps, and related information used to distinguish saves. Cloud saves are linked to the connected Google Account and used for backup and restoration. The App has no feature that publishes your cloud saves to other users.
You can disable automatic backup under Settings (設定) → Achievements and Saves (実績・セーブ), and manually back up or restore saves. Disabling automatic backup alone does not stop achievement submissions. Manage your Google Play Games sign-in and profile visibility through Google’s settings.
The Google Play Games SDK also collects diagnostic and usage information to improve service stability and the product. Google’s processing, storage, and deletion of information are governed by Google’s Privacy Policy and the terms of each service. See Google’s explanation of Play Games data collection for SDK details.
4. Operating system backups
Depending on your operating system and device settings, stored information may be included in Android backups, iCloud backups, device transfers, or similar services. These are operating system features. The developer does not obtain or view these backups.
5. Contact information
The email address and message you provide when contacting the developer are used to reply and address problems. Only the developer handles inquiries. Access to responses is restricted, and information is kept for as long as needed to handle the inquiry, then deleted when it is no longer needed.
Google Forms is used to receive and manage inquiries, and Google’s Privacy Policy also applies. Saves, images, and device information are not automatically added to the form.
Sentry, Google, and Cloudflare process information as needed to provide the services described in this policy. If the developer outsources handling of information, protection equivalent to this policy will be ensured. Information is otherwise provided to third parties only with your consent or where required by law.
6. Requests for deletion, disclosure, and other rights
Individual saves can be deleted within the App. To delete all information stored by the App on your device, including settings and selected images, follow these steps:
- Android: Clear the App’s storage in your device settings.
- iOS: Use Delete App to remove the App.
Manage operating system backups through your device or backup service.
Deleting a team or App data from your device does not delete achievements or cloud saves stored by Google. Follow Google’s instructions for deleting Play Games data to delete that game data. If records remain on your device and the App is connected to Play Games, they may be submitted or backed up again. To avoid this, first sign out of this game through Google’s settings and, where needed, also delete the data on your device.
Requests to access, correct, or delete inquiry information or error information sent to Sentry, and complaints about its handling, can be made through the contact form below. Select “Other” (その他) and include the email address used for your inquiry, or details such as the time of the error and App version that may help identify the information, together with the action you are requesting. Error reports do not include information that directly identifies you, so it may not be possible to identify the relevant report. Identity may be verified where necessary, and requests will be handled in accordance with applicable law.
7. Delivery of public web pages
Cloudflare Pages is used to deliver the App’s public information website. When you visit those pages, Cloudflare may process your IP address and connection information to deliver the pages and provide the service securely. See Cloudflare’s Privacy Policy for details.
8. Web demo achievement records
The Web demo keeps progress and pending records in its own browser storage. Saves cannot be transferred to the App.
At the start of play and the first victory in each of the Frontier League, Capital League and Universe Series, the demo sends a team-specific random challenge ID, event type, in-game year (one to ten), team name and predefined crest ID at that time, and schema version to the same site’s API. Cloudflare Pages Functions and D1 process and store these with the receipt time. The first Capital League and Universe Series victories also include the names of the active nine batters and twelve pitchers, abilities after stickers, blessing sticker IDs, batting order, fielding positions, pitching roles, and references to built-in portraits. Uploaded images, image files, internal player IDs, past statistics, entire saves, email addresses and account credentials are not included in these submissions. For potential future QR publication, the same 21 players also have a separate shared-team snapshot containing species, base abilities and ability caps, all sticker IDs and effects, secret technique IDs and selected pitches, and team-local numbers linking two-way registrations. It includes no uploaded images or internal player IDs. Failed submissions are retried, for example when play resumes or a connection recovers.
The purposes are team-based challenge and first-victory totals, the public achievement list on the landing page, deduplication and operation of the records service. This does not measure unique people. The public list includes first-victory year, team name and crest. Capital League and Universe Series team details also publicly display the player and lineup information described above. The shared-team snapshot is not currently served by the landing-page list or team-detail API. If a QR code is published later, readers will receive that shared-team data. Challenge IDs and receipt times are not public. Victory records are frozen and do not change with later training or roster changes. Team and player names are free text and may contain personal information; do not enter real names or contact details. These records are not treated as fully anonymous.
Challenge and achievement records are retained without a fixed expiry while the Web demo remains available. Handling after its closure will be announced at that time. Deleting a team or browser storage does not delete records already received. For removal, correction or other requests, select “Other” (その他) in the contact form below, and provide the team name, tournament, first-victory year or other details to identify the record and your request. Requests are reviewed and identity may be checked where needed.
Cloudflare also processes connection information, including source IP addresses, to deliver the site and process records. To limit repeated submissions, the API stores a short-lived identifier derived from the IP address, a secret and a time window, together with a request count. Raw IP addresses are not stored in the records database. Identifiers expire within about two minutes and are removed on a subsequent record request. Cloudflare’s own processing is subject to Cloudflare’s Privacy Policy.
9. First-victory records in the App
The Android and iOS App automatically submits a record for each team's first victory in the Frontier League, Capital League and Universe Series. It does not submit a start event or subsequent victories. The record contains a random challenge ID saved with the team, tournament, first-victory year, team name, built-in crest ID, operating-system platform, App version and build, product or test channel, scenario and revision, game-rules version, ranking-eligibility classification and schema version. The official site's App API stores it with the receipt time in Cloudflare Pages Functions and D1, separately from public Web demo totals. The Web demo's ten-year limit does not apply.
The Frontier League record includes only this basic information, without player or lineup details. Capital League and Universe Series records also contain the same frozen 21-registration display and shared-team snapshots described in the previous section. Submissions do not include uploaded images, image files, internal player IDs, statistics history, entire saves, account information or advertising identifiers. Do not enter real names or contact details in team or player names.
Records are used to prepare rankings based on the first-victory year and to operate the game. App records are not currently served on the landing page or through a public API. The information and method of publication will be explained when rankings are introduced. This is separate from error reporting settings and Google Play Games. Failed submissions do not stop play; the same saved record can be retried at launch, on connection recovery, when the App resumes or after later saves. Tournaments already won before this feature was introduced are not backfilled using the current roster.
Records are retained while the service operates, without automatic expiry. Deleting a team or the App does not delete records already received. For deletion, correction or other requests, select “Other” (その他) in the contact form below and provide the team name, scenario, tournament, first-victory year and your request. Repeated-submission protection and Cloudflare's processing of connection information are the same as in the previous section.
10. Changes and contact
Upon a request from the individual concerned through the contact form below, the developer will promptly provide their name, address, and other information that applicable law requires to be made available to individuals whose personal data the developer holds.
If this policy changes, the changes and effective date will be announced on the public website.
Developer: えびです ぷりぷり〜
Contact: Contact form
Established: October 9, 2026
Last revised: November 6, 2026
Effective from: the date this revised policy is published