Privacy policy
MyWorld — Your own space
- Effective date
- 2026-10-21
- Operator
- 앵두별컴퍼니 / addwisdom
- Privacy contact
- MyWorld Operations Team (마이월드 운영팀)
- Privacy and support email
- addwisdom@gmail.com
- Information updated
- 2026-11-10
1. Scope
This policy covers the MyWorld iOS and Android apps’ device demo, online account features, decorating content downloads and email inquiries. The demo and online account use separate records. Demo currency and backups are not uploaded as online currency or item ownership. The online service is available through the mobile apps. The existing browser demo keeps separate records in that browser.
2. Information and purposes
| Activity | Information and purpose | Storage and management |
|---|---|---|
| Device demo | Room layout, avatar, pet, owned items, Stars, care, missions and demo guestbook. Used to save play and recover from storage errors. | Stored on the device. A last valid save and recovery copies of damaged records may remain. The existing web demo uses that browser’s storage. |
| Account authentication | Firebase anonymous account identifiers, authentication and session information, and app integrity evidence. Used for account access, authenticating requests and preventing abuse. | Processed by the authentication provider and online server. Anonymous authentication creates an identifier linked to game records. Real name, email and phone number are not required for play. |
| Online play and social features | Public player ID and nickname, room, avatar, pet, items, Stars, care, missions, rewards, friends, requests, blocks, public and private guestbook messages, reports and community consent. Used for account play, sharing controls and handling reports. | Linked to the account on the server and included in account deletion. Hiding the internal authentication ID from public screens does not remove account linkage on the server. |
| Usage and reward records | Virtual-currency item purchases, prices, balance changes, timestamps, mission dates, claims, request results and account request counts. Used to manage currency and prevent duplicate rewards, abuse and excessive use. | Linked server records included in account deletion. No real-money payment records are processed. |
| Content and connections | HTTPS requests for catalogs and images, and connection or diagnostic information such as IP addresses and user agents. Used for delivery, protection and operation. | Downloaded content is cached on the device. Provider processing, retention and server logs are described in section 3. |
| Backups you create | Local game JSON and demo guestbook content that you choose to copy. | Held in the clipboard, files or external services where you save them. The app does not automatically send them to the operator. |
| Email inquiries | Sender address, inquiry or rights request, and voluntary attachments. Used to reply and handle requests. | Received by the MyWorld Operations Team by email. Retention and deletion are described in section 5. |
3. Sharing and service providers
Online rooms and guestbooks are shown according to privacy settings, in-app friendships and blocking in both directions. Friends-of-friends visits also depend on accepted in-app relationships and public rooms. Private messages are processed by the server, and records needed to handle a report may be reviewed. The app does not read device contacts or find friends by email or phone number. Copies and screenshots saved by others can remain after the original is deleted.
MyWorld uses Google Firebase and Google Cloud for anonymous authentication, online game storage, API execution, decorating content delivery and app integrity checks. The Cloud Firestore database storing game records is configured in the Seoul region (asia-northeast3). Firebase states that Authentication processes data exclusively in the United States, while services such as Hosting and App Check may process data on Google’s and its providers’ global infrastructure.
Our billing country is South Korea. Google’s public online-terms entity table lists, for Google Cloud Platform and Firebase Paid Services, Google Cloud Korea LLC (Gangnam Finance Center, 20th floor, 152 Teheran-ro, Gangnam-gu, Seoul, South Korea) for a South Korean billing address. This entity is an authorized reseller. For an agreement with that reseller, Google means Google Asia Pacific Pte. Ltd. (70 Pasir Panjang Road, #03-71, Mapletree Business City II, Singapore 117371) and/or its affiliates, including the reseller, as the context requires.
Under the service-specific terms list, Authentication, App Check, Cloud Firestore and Cloud Functions for Firebase use the Google Cloud terms. Firebase Hosting uses the Google APIs terms, Firebase Data Processing and Security Terms and Firebase Paid Services Agreement. The Google APIs terms identify Google LLC (1600 Amphitheatre Parkway, Mountain View, California 94043, United States) by default unless additional terms provide otherwise; the Firebase Paid Services Agreement refers to the entity table above. These office addresses do not describe where all user data is stored.
Provider privacy inquiry routes are the Google Cloud Data Protection Team and Firebase Data Privacy Inquiries. For a MyWorld account or privacy-rights request, contact our operations team using the details in this policy. Opening a provider inquiry page does not submit a MyWorld account deletion request.
Required authentication and request information is transmitted over HTTPS when connecting an online account, making game or social API requests, or resuming or checking an account deletion in progress. Catalog checks, refreshes and image downloads also send HTTPS connection information to the provider. The device demo can be used without connecting an online account, but content requests in the demo can still involve processing connection information. Support inquiries are sent through the email service when you send an email.
Public terms and provider inquiries: Google’s public online-terms entity table · service-specific terms list · Google Cloud terms · Google APIs terms · Firebase Data Processing and Security Terms · Firebase Paid Services Agreement · Google Cloud Data Protection Team · Firebase Data Privacy Inquiries
Firebase privacy information · Firestore locations · Terms by service
App integrity checks are configured to use Apple App Attest on iOS and Google Play Integrity on Android, with evidence and tokens processed through Firebase App Check. App Check and the attestation provider’s processing are separate from account storage. Apple App Attest information · Android Play Integrity information
Firebase states that Authentication retains IP addresses for a few weeks for security and abuse prevention, while Hosting retains them for a few months for abuse detection and usage analysis. App Check forwards attestation material to the attestation provider and states that Firebase App Check does not retain that material itself. The Seoul database setting and the app’s deletion periods do not apply to all provider records.
Cloud Run, which runs the API, generates HTTP request logs that may include IP addresses and user agents. The verified Cloud Logging default log bucket, _Default, has a 30-day retention setting. This applies only to that bucket, not all other buckets, authentication or Hosting records, or provider backups. These logs are also separate from the server’s temporary hashed-IP request limits.
Support email uses Google Gmail. Messages you send are also processed by Google’s mail service. The operator’s deletion of inquiry records is separate from the provider’s retention and backups. Google Privacy Policy
4. SDK diagnostics, permissions and ads
The iOS Firebase Auth and App Check SDKs use default user-agent diagnostic collection, including app and SDK versions, device, operating system and development platform information, for Firebase platform and version usage analytics. Firebase describes these diagnostics as not linked to device or user identifiers. This applies to those SDK diagnostics only; it does not mean account and game records or all provider IP records are unlinked. Firebase Apple SDK collection information
On Android, Firebase Auth and App Check use Firebase user-agent data, including device and OS information, app installation source and SDK versions, to provide, maintain and improve services. Auth also processes IP addresses for security and abuse prevention, authentication user-agent strings and the Firebase app ID. App Check processes Play Integrity tokens to validate app integrity. Firebase’s statement that the Firebase user agent is not linked to user or device identifiers applies only to those diagnostics. Firebase Android SDK collection information
The app does not read your address book, location, camera, photo library or microphone. AdMob, advertising identifier collection, Google Analytics, automatic crash reporting and in-app purchase SDKs are not connected. No real ads are requested, impressions counted or ad rewards paid. Care and mission game rewards are separate.
Support and policy links open in an external browser. The app does not read browser history or attach account tokens to these links. Visited sites and your email app process connection and transmission information under their own policies.
5. Retention and deletion
Online account, game, social and reward records are held to provide the account service and removed through an in-app account deletion request. See account deletion for the scope and progress checks. Account access stops when the server accepts a deletion request, and an accepted request cannot be canceled.
Minimal records for completion and recovery verification become eligible for scheduled cleanup 30 days after completion; account hashes used to prevent recreation become eligible 7 days after completion. Actual cleanup can take additional time depending on the workload and processing status. Pending requests remain as needed to confirm completion. Separate provider log and backup retention means the app’s completion message does not confirm immediate erasure of every copy.
We use inquiry emails, messages and voluntary attachments to answer and handle requests, and delete inquiry records held by the operator within one year after the request has been resolved.
Operator-held records are removed using the relevant storage service’s deletion functions when their retention period ends or they are no longer needed. Separate copies held by the operator are also deleted. Provider security and backup processing follow the provider’s policies. You manage device demo records, caches and backups you created on the device and external services. Resetting the demo or uninstalling the app does not delete an online account.
6. Rights requests and deletion help
For access, correction, erasure, restriction of processing or help with account deletion, email addwisdom@gmail.com with your request and a reply address. We explain the minimum account ownership checks needed and do not disclose or delete another person’s records without verifying ownership.
If a legal representative makes a request, we check their authority. Do not send passwords, verification codes, session or recovery tokens, full backup JSON or national identity numbers. A public player ID alone does not prove ownership. If ownership cannot be verified, we cannot disclose or delete records; we explain available verification steps and the outcome. Opening this page or an email link does not submit a request. Send the email yourself.
7. Device storage and safe use
Server and content transfers use HTTPS, and the app checks content hashes and formats. To continue an interrupted deletion, the app keeps a request key, resume secret, account scope and progress in secure storage on the same device. iOS uses Keychain without iCloud synchronization. Android uses encrypted storage with keys protected by Android Keystore. The Android app is configured to exclude app data from automatic backups and device transfer. A hashed account scope is account-linked recovery information, not anonymous statistics. This recovery record excludes email and the raw internal authentication ID; recovery secrets are excluded from demo JSON, screens and logs.
Do not uninstall or clear device data before completion is confirmed. Changing devices, clearing storage or uninstalling the Android app can lose account access or deletion recovery information. On iOS, reinstalling does not always erase Keychain records. Completion is shown after server deletion and device recovery-data cleanup are confirmed. Files you saved, synced clipboard copies and copies held by others must be managed separately.
8. Contact and changes
Operator: 앵두별컴퍼니 / addwisdom · Privacy contact: MyWorld Operations Team (마이월드 운영팀) · addwisdom@gmail.com
Changes to information, purposes or retention practices will be announced on this page with their effective date.