DRAFT — NOT PUBLISHED OR EFFECTIVE
Idle Hero Legends Privacy Policy
Status
This is a review draft. It is not an effective privacy policy, public deletion channel, or published legal URL. The effective date will be the actual first public publication date after owner and legal approval.
Operator
株式会社大銭
Corporate number: 1120001248939
Registered address: 〒542-0066 大阪府大阪市中央区瓦屋町１丁目１０番１０号２０１号室
Contact candidate pending approval: ccjiao30@gmail.com
Product scope
Idle Hero Legends does not require a developer account, username, password, social login, cloud save, multiplayer profile, chat, location sharing, user-generated content, or push-notification backend. The app creates a random local player ID and stores progression, inventory, currencies, settings, entitlements, fulfilled transaction IDs, and notification preferences in app-private local storage. Android backup and device-transfer extraction are disabled. Local gameplay and UI event names with timestamps are held only in memory by the project-owned analytics abstraction and are not sent to a developer analytics backend.
Data processed by release SDKs
The production design includes Google Mobile Ads, Google User Messaging Platform, Unity In-App Purchasing, Google Play Billing, and a dedicated receipt-validation service. Depending on use and provider behavior, these components may process or share approximate location derived from IP address; advertising ID, app-set ID, installation, session, device, account or other identifiers; app launches, taps and ad-video interactions; consent status; diagnostics and advertising performance; transient email address reported by the store/IAP provider; purchase history; transaction and product identifiers; crash logs; and other app-performance data.
Purchases
Google Play processes payment. 株式会社大銭 does not receive full payment-card or bank details. The planned validator sends contract version, product ID, transaction ID, Unity receipt, platform and package ID over HTTPS to verify entitlement with Google Play. Raw purchase tokens, receipts, signatures, credentials and private keys must not appear in application logs. Only a stable hashed validation ID and minimal result metadata may be logged.
Purposes
Purposes are gameplay and entitlement delivery, optional advertising, consent management, subscription and purchase verification, fraud prevention, security, diagnostics, legal compliance and support. Personalized advertising will use consent where required. Core gameplay remains available without purchasing the optional products.
Providers and transfers
Relevant providers may include Google Mobile Ads, Google User Messaging Platform, Google Play, Unity IAP and the approved Google Cloud processor for receipt validation. The final processor list, Cloud region, subprocessor terms and international-transfer safeguards require approval before publication. Cloud Run asia-northeast1 (Tokyo) is only the current hosting proposal and is not deployed.
Retention proposal pending approval
Local saves remain until in-app reset, clearing app data or uninstall. Raw purchase tokens and receipts are transient and never logged. Proposed retention is 30 days for operational request logs, 24 months for minimal validation/refund metadata, and 3 years for privacy-request correspondence. Third-party-provision and financial/tax records are retained only for the applicable statutory period.
Choices and deletion
Players may use available consent/privacy controls, reset the device advertising identifier, avoid optional rewarded ads, manage purchases and subscriptions through Google Play, reset local progress, clear app data or uninstall. A public operator deletion-request channel and backend deletion procedure do not yet exist. The separate Data Deletion page remains a draft until an approved monitored contact and procedure are published.
Children
The working audience recommendation is ages 13-15, 16-17 and 18+. The game is not designed as child-directed and is not proposed for the Families program. Final audience and IARC answers require owner/legal approval.
Security
Off-device project traffic is designed for HTTPS. The app disables cleartext traffic, Android backup and transfer extraction. Receipt validation is fail-closed and uses bounded request sizes and timeouts. No safeguard eliminates all risk.
Approval boundary
Owner approval, legal approval, final SDK/version re-audit, processor review, public HTTPS publication and Play Console readback are all required before this draft may become effective.