Somedea LLC (hereinafter referred to as the “Provider”) establishes the following Privacy Policy (hereinafter referred to as the “Policy”) regarding the handling of users’ personal information and other user-related information in connection with the “Shinsen Memo” service (hereinafter referred to as the “Service”).
1. Personal Information
“Personal Information” in this Policy refers to information such as a name, email address, or any other information that can identify a specific individual.
2. Methods of Collecting Personal Information
The Provider may collect email addresses and other contact information when users make inquiries or contact the Provider.
In addition, for service improvement, usage analytics, advertising, and fraud prevention, the Service may automatically collect IP addresses; device, operating system, and app information; device or app identifiers; advertising identifiers when available; approximate location inferred from an IP address; usage data; ad impression, interaction, and viewing data; crash reports; and related information. The information collected varies depending on device settings, region, features used, and user choices.
When users use the following features of the Service, the Provider also collects the information described below.
- Sign-in (optional): When users sign in with Google or Apple, their email address, display name, and user ID are stored in Firebase Authentication. On iOS, while signed in, the user ID is set as the identifier for usage analytics and crash analysis.
- Cloud backup (optional; sign-in required): When users run a backup, formations, enemy templates, simulation history (including titles and notes entered by the user), settings, and an identifier generated for each device are stored and linked to the user ID.
- Battle report recording: Battle report images are recognized on the device, and the images themselves are not sent. When users record a battle report, the recognized battle report data (units, officers, tactics, troop losses, and similar data) is sent automatically with an anonymous identifier generated on the device and is used for battle report recording and to improve simulation accuracy. The battle report data sent does not include player names or alliance names.
- Sending failed recognition images (optional; off by default): Only when users allow it in the app’s settings, a screenshot of a battle report whose text recognition failed is sent to improve recognition accuracy. Such images may show player or alliance names. Users can change this setting at any time from “Send Failed Recognition Images” in the menu.
- Simulation rankings: When users run a simulation that is eligible for ranking aggregation, the simulation result, the full formation settings (officers, troop types, tactics, rank-ups, troop type aptitude, stat adjustments, military books, equipment skills, and strategist skills), the simulation time, and the submission time are sent automatically with an anonymous contributor ID generated on the device. Player and alliance names, battle report images, battle report text, notes, and account profile information are not sent.
- Battle adoption ranking: Where this feature is available, for battle reports recorded in the current month and the previous two months, the IDs of the three allied officers, whether each is the commander or a vice commander, and the time the battle report was recorded are sent automatically with a random anonymous identifier and sync IDs generated for each installation. Player names, alliance names, opponent names, coordinates, battle report images, notes, tactics, military books, equipment skills, and saved formation names and IDs are not sent.
- Game services: When users are signed in to Game Center on iOS or Google Play Games services on Android, scores and achievements are sent to those services.
- Push notifications: The Service uses Firebase Cloud Messaging to deliver announcements. The Provider does not store notification tokens.
- Purchases: Subscriptions are purchased and restored through the App Store or Google Play payment systems. To confirm purchase status, purchase information (transaction information or a purchase token) and the user ID are sent to the Provider’s servers, and the subscription is linked to the account.
- Fraud prevention: To prevent unauthorized access to the Provider’s servers, the Service uses Firebase App Check (Apple App Attest or DeviceCheck on iOS, and Google Play Integrity on Android) to verify the integrity of the app and device.
- Contact: The in-app contact form uses Google Forms or FormConcierge. While users are signed in, the user ID, OS version, device model, and app version are filled in automatically to help with support. With Google Forms, this information is included in the form URL and sent to Google when the form is opened. With FormConcierge, device information such as language and time zone is also sent.
Simulation ranking and battle adoption ranking data is used to aggregate and display rankings and is not linked to the user ID or the signed-in account. Aggregated results are visible to other users as rankings. Because sending this data and battle report data is necessary to provide these features, the app does not offer separate settings to stop it. Users who do not want this data sent can avoid using the relevant features (simulations eligible for ranking aggregation and battle report recording) or delete the app. Retention periods for data already sent are described in Section 9.
3. Purposes of Collecting and Using Personal Information
The Provider collects and uses personal information and related information for the following purposes:
- To provide and operate the Service
- To anonymously aggregate and publish the simulation rankings and the battle adoption ranking
- To respond to user inquiries
- To improve the Service, investigate issues, and enhance quality
- To analyze usage of the Service
- To deliver advertising, provide in-app functionality associated with ad impressions or views, and measure advertising effectiveness
- To assess advertising quality and safety and to detect and prevent invalid impressions or interactions
- To obtain, manage, and apply users’ choices regarding advertising and analytics
- To send maintenance notices and other important information
- To identify users who violate the Terms of Service or attempt to use the Service for improper purposes, and to take appropriate measures
- To confirm usage status related to paid services
- For purposes incidental to the above purposes
Payments are processed through Apple’s or Google Play’s payment system, depending on the platform, and the Provider does not directly obtain or retain users’ credit card or payment information.
4. Changes to the Purpose of Use
- The Provider may change the purposes of use of personal information only when reasonably deemed related to the original purposes.
- In the event of such changes, the Provider will notify users or publicly announce the updated purposes through the Service or by other appropriate means.
5. Provision to Third Parties
The Provider will not provide personal information to third parties without the user’s prior consent, except where required by applicable laws and regulations.
However, within the scope necessary to achieve the purposes of use, the Provider may outsource the handling of personal information to external service providers, including but not limited to:
- Server operation and maintenance
- Usage analytics and advertising measurement
- Crash analytics
- Advertising delivery, advertising quality assessment, and fraud prevention
- Management of privacy choices
- Payment processing
- Customer support
The Provider does not sell users’ personal information for monetary consideration. However, disclosures to advertising providers may be considered a “sale” or “sharing” under certain U.S. state privacy laws. Where applicable, users may opt out through the advertising privacy settings presented in the Service.
6. Analytics, Advertising, and External Data Transmission
The Service uses Google Firebase, including Google Analytics for Firebase and Firebase Crashlytics, for service improvement, usage analytics, and crash analysis. For advertising delivery, measurement, advertising quality assessment, and fraud prevention, the Service also uses Google AdMob and its advertising partners.
Advertising services that may process information through SDKs embedded in the Service are listed below by platform. Depending on delivery and review status, not all listed services will necessarily serve ads at all times.
- iOS: Google AdMob / User Messaging Platform, AdGeneration (Supership), Unity Ads / Unity Ad Quality, Liftoff Monetize (Vungle), Pangle, and Mintegral
- Android: Google AdMob / User Messaging Platform
These external services may collect the information described in Section 2 and use, retain, or disclose it in accordance with their respective privacy policies. This does not mean that all listed information is always transmitted to every provider.
For details, please refer to the privacy policies of Google, Supership, Unity, Liftoff, Pangle, and Mintegral.
Depending on the user’s region, the Service may present consent or opt-out controls for advertising or analytics. Where available, users can review or change their choices using “Ad privacy options” in the Service’s Settings. On iOS, users can also change tracking permission in the device’s Settings → Privacy & Security → Tracking. On Android, users can reset or delete their advertising ID in the device’s Settings → Privacy → Ads (the exact labels vary by device and OS version). Declining tracking or deleting the advertising ID does not disable all advertising or network communications.
7. Disclosure of Personal Information
If a user requests disclosure of their personal information, the Provider will respond appropriately in accordance with applicable laws and regulations.
However, the Provider may refuse to disclose all or part of the information in the following cases:
- When disclosure may harm the rights or interests of the user or a third party
- When disclosure may significantly interfere with the proper operation of the Provider’s business
- When disclosure would violate laws or regulations
8. Correction and Deletion of Personal Information
Users may request correction, addition, deletion, or suspension of use of their personal information held by the Provider.
The Provider will respond appropriately in accordance with applicable laws and regulations.
9. Retention Periods
The Provider retains personal information and related information for as long as necessary to achieve the purposes of use. The main retention periods are as follows:
- Sign-in account and cloud backup: until the account is deleted (when a backup is updated, the older backup data it replaces is deleted)
- Deleted account identifier and deletion date: 30 days after account deletion, to safely retry deletion and prevent deleted cloud data from being restored
- Battle report data: 90 days after submission
- Images sent when battle report recognition fails: 30 days after submission
- Anonymous ranking and battle adoption data: 180 days after it is stored (values already included in anonymous aggregates are not deleted individually per contributor)
- Support inquiries: as long as necessary to respond. If deletion is requested, they are deleted unless retention is required by law or for fraud prevention.
- Usage analytics, crash analysis, and advertising information: for the periods set by each external service
10. Account Deletion
Users can delete their sign-in account and cloud backup in the app under Settings → Account Management → Delete Account. For how to request deletion without the app, and which data is deleted or remains after deletion, see the Account Deletion page.
11. Children Under 13
The Service is not directed to children under the age of 13. If a parent or guardian becomes aware that a child under 13 has provided personal information, please contact us using the contact information in Section 13. We will review the request and delete the relevant information.
12. Changes to This Privacy Policy
- The Provider may revise this Policy as necessary.
- The revised Privacy Policy shall become effective when posted within the Service.
13. Contact Information
For inquiries regarding this Policy, please contact:
Email: support@somedea.com
Established: April 15, 2023
Revised: October 13, 2026