1. General Principles
JUNNIE Games (“we,” “us,” or “our”) provides the mobile game Tiny Factory and processes personal data only to the extent necessary to operate the service. When a processing purpose is fulfilled or a retention period expires, we delete the relevant data unless applicable law requires separate retention.
Tiny Factory does not directly ask users to provide health or medical data, financial account or credit information, contacts, photos or videos, audio, files, or precise location data.
2. Data We Process
| Category | Data | When Processed |
|---|---|---|
| Account and authentication | Firebase anonymous user identifier (UID), authentication provider, and, when a Google Play Games account is linked, player identifier and display name | First launch and account linking |
| Game data and cloud save data | Game progress, currency, city, facility and manager states, mission and tutorial states, save version, modification time, and request identifier | During gameplay and when saving |
| Purchases | Product ID, order ID, purchase token hash, purchase and subscription status and timestamps, verified actual payment amount and currency where available, purchase verification results, claim status and time of mailbox rewards, delivery times and quantities, application status of immediately applied products, and refund, cancellation, expiration, recovery, shortfall review and resolution records | During in-app purchases, restorations, delivery, mail claims, and refund processing |
| Order-linked usage evidence | Time, quantity, and purpose of currency usage allocated to the delivery from that order; relevant balances before and after delivery or usage; chest type, opening results and manager types obtained; manager-type references for later activities such as upgrades and synthesis; server request identifiers and restricted account-linking identifiers or hashes | When the server processes purchased currency delivery, usage, and related activities |
| Refund and chargeback review | Google Play order and review request identifiers, review response token, request and response times, deadlines and status, submitted preferences and usage summaries, and evidence access and processing records | When Google Play review requests are received and reviewed or answered by an operator |
| Mailbox | Mail ID, purchase or reward type, reward contents, creation time, claim status and time, and scheduled deletion time | When mail is delivered, viewed, claimed, or deleted |
| Advertising | Device identifiers such as the advertising ID, approximate location based on IP address, ad impressions, taps and video views, reward transaction ID, ad unit and network information, and consent choices | When advertising consent is collected and ads are used |
| Device and diagnostics | Device model, operating system and app version, language, country, IP address, app activity, and SDK performance and diagnostic information | When the app launches and while the service is used |
| Security | App Check and Play Integrity verification information, records of abnormal requests and duplicate transactions, and server request logs | When server features are used |
| Customer support | Email address, account and purchase information, the content of the inquiry, and support records that a user voluntarily includes in a support request | When an inquiry is submitted |
Order-linked usage evidence consists of minimum records that allocate purchased currency to activities using the server’s first-in, first-out (FIFO) accounting method. Chest rewards and manager types involved in later activities may be referenced; these records do not trace an individual card’s unique lineage from acquisition through upgrades or synthesis. We do not make long-term copies of an entire game save or every action ledger for transaction evidence. A review response token is different from a purchase token and is processed on the server with restricted access.
The Google Mobile Ads, Unity Ads, and ironSource advertising SDKs may automatically collect the advertising and device information listed above or share it with advertising partners to deliver and measure ads and prevent abuse. Users can manage personalized and non-personalized advertising and exercise applicable regional privacy choices through the app’s consent flow and privacy settings.
3. Purposes of Processing
- Create game accounts, authenticate users, link accounts, and recover accounts after a device change
- Save and synchronize game progress, resolve conflicts, and restore cloud save data
- Verify in-app products and subscriptions; deliver and confirm claims of mailbox rewards; process restorations, withdrawals, refunds, cancellations, and expirations; confirm order-linked delivery and usage evidence; review necessary recovery and shortfalls; and respond to Google Play refund and chargeback review requests
- Deliver rewarded ads selected by users and prevent duplicate rewards
- Deliver personalized or non-personalized ads, measure ad performance, and manage ad frequency
- Maintain service stability, analyze errors, and prevent security threats and abuse
- Handle customer inquiries, requests to exercise privacy rights, and disputes
4. Retention Periods
| Data | Retention Standard |
|---|---|
| Firebase account and cloud save data | Until the account is deleted or an account deletion request is completed |
| Mailbox mail | Unclaimed mail is retained until claimed or the account is deleted. Claimed mail is automatically deleted 7 days after claiming and may also be deleted manually. Claim status and time, and the application status of immediately applied products, in purchase records are retained separately according to the retention standards for payment and transaction records. |
| Rewarded ad requests and duplicate-reward prevention records | Deleted after the period necessary for reward verification and fraud prevention |
| Records of contracts and cancellations | 5 years as required by applicable Korean e-commerce law |
| Payment and supply records | 5 years as required by applicable Korean e-commerce law |
| Consumer complaint and dispute records | 3 years as required by applicable Korean e-commerce law |
| Display and advertising records | 6 months as required by applicable Korean e-commerce law |
| Customer support inquiries | 3 years after the inquiry is resolved or for the period required by applicable law |
Records retained as required by law and records used to prevent payment fraud are kept separately from ordinary account data, with access restricted. When the applicable retention period expires, electronic data is deleted using methods designed to prevent recovery.
Scope of transaction evidence and calculation of retention periods
The statutory periods above follow Article 6 of the Korean Act on Consumer Protection in Electronic Commerce and Article 6 of its Enforcement Decree. We publish the following operational rules for calculating those periods. Using actual completion of dispute handling as the starting event is an operational rule stated here.
- Contract, payment, and supply records are calculated separately for five years from each verified actual event date. Records of withdrawal, cancellation, or refund are calculated separately for five years from the verified actual date of that event. Supply evidence includes minimum records of actual delivery or claim of purchased rewards or application of immediately applied benefits.
- Consumer complaint and dispute records are calculated for three years from actual completion of handling. Submitting a review preference or receiving a successful API response does not by itself mean a dispute has ended.
- Display and advertising records are calculated for six months from the verified actual event date. This period does not prescribe a single retention period for all advertising SDK activity records.
- Years and months are calculated using the calendar in Korea Standard Time (Asia/Seoul), including leap years and month ends. Records are processed for deletion by category after the final day of the retention period. Account deletion, copying or viewing evidence, and receiving the same event again do not restart an existing event’s period.
Order evidence includes only delivery, claim, usage allocation, reward result, recovery and handling records, and restricted order or account links necessary to confirm purchase or supply performance or handle an actual refund or dispute. We do not retain all game logs for a blanket five-year period. Records with different legal grounds and periods are deleted in a manner designed to prevent recovery, or reduced to necessary fields, when the applicable category’s period expires.
Deleting an account continues to delete ordinary game progress and save data. Transaction evidence subject to legal retention is stored separately with restricted access. For an actual ongoing dispute or another lawful preservation need, we manage a reason and review date for a hold on only the relevant minimum records. Submission or an unconfirmed status alone does not justify indefinite retention. When the hold is no longer needed, we check the remaining statutory period and process the records accordingly. Linkable account hashes are subject to the same access restrictions and retention and deletion controls.
Service records needed while an account remains active
Separately from copies kept for statutory transaction evidence, we retain the minimum order-to-account link, original purchase records and currency records supporting current rights and balances for the account’s lifetime, to verify purchase rights, maintain currency consistency and prevent duplicate delivery. Minimum metadata identifying the original event, its verified time, the retention calculation and event integrity may also remain for this period to prevent duplicate processing or arbitrary restarts of the retention clock. This does not mean that expired copies of transaction amounts and detailed usage evidence are retained in full.
On account deletion, ordinary service records and the original account link are deleted. Transaction evidence needed for the remaining statutory period is separately managed with the original UID link removed. Order information, restricted links and retention-control metadata retained after deletion are also processed for removal when their applicable basis and retention period end.
Separate retention of operator access records
To prevent misuse of personal data and review access and downloads, we separately manage minimum access records, including the operator identifier, access or work time, access-location information, a restricted reference identifying the affected data subject, the work performed and its result. These records are separate from transaction evidence and do not contain passwords, authentication secrets, raw review response tokens or an entire game save.
Under Article 8 of Korea’s Standards for Safeguarding Personal Information, these access records are retained for one year from the access or work event. A minimum of two years applies if the system processes personal information of at least 50,000 data subjects, processes legally defined sensitive or unique-identification information, or the Company is a facilities-based telecommunications operator covered by that Article. Years are calculated using the Korea Standard Time calendar and the final day of the period. Account deletion or expiry of order evidence does not shorten this separate security minimum. Minimum access records are also processed for deletion when their retention period and necessary security purpose end.
5. Processors and External Services
We use SDKs and services provided by the companies listed below. Depending on the service, a provider may process data independently or on our behalf as a processor.
| Provider and Service | Purpose | Main Data |
|---|---|---|
| Google Firebase (Authentication, Firestore, Cloud Functions, App Check) | Authentication, cloud save storage, server functions, and app integrity verification | UID, display name, game save data, IP address, and device and security information |
| Google Play Games Services | Sign-in, account linking, and account recovery | Player identifier and display name |
| Google Play Billing | Processing and verifying in-app purchases and subscriptions, and handling refund and chargeback reviews | Product, order, purchase and subscription status; refund review requests and responses; and summaries of the order’s currency usage times, quantities, purposes and usage percentage |
| Google AdMob / Google Mobile Ads / UMP | Ad delivery, consent management, analytics, and abuse prevention | Advertising ID, approximate location based on IP address, ad activity, and device and diagnostic information |
| Unity Ads | Ad delivery and measurement through AdMob mediation | Approximate location based on IP address, ad activity, device and app identifiers, and diagnostic information |
| ironSource Ads | Ad delivery and measurement through AdMob mediation | Approximate location based on IP address, device and app information, advertising identifiers, and ad activity |
For more information, see the Google Privacy Policy, Firebase Privacy and Security, and Unity Game Player and App User Privacy Policy. Approved partners of each advertising network may also participate in ad delivery.
6. International Transfer of Personal Data
We transfer personal data to the overseas providers listed below for processing and storage only to the extent necessary to provide the service. Processing performed by Cloud Functions in the Seoul region takes place in South Korea and is therefore not included in the international transfers listed below.
| Recipient | Country | Data Transferred | Purpose | Timing and Method | Retention and Use Period |
|---|---|---|---|---|---|
| Google LLC Contact | United States | Firebase UID and authentication provider; user agent and IP address; Google Play Games player identifier and display name; App Check and Play Integrity attestation material and tokens; product ID, order ID, purchase token, and purchase and subscription status and timestamps; and a one-way hash of the Firebase UID | Account authentication and security through Firebase Authentication; app and device integrity verification through App Check; sign-in and account linking through Google Play Games; and purchase and subscription verification, restoration, and payment fraud prevention through Google Play Billing | Transferred over encrypted networks when the app first launches, when users sign in or link an account, when the app calls server functions, and when users make or restore purchases or check subscription status | Firebase Authentication IP logs are retained for a few weeks. Other authentication data is retained until account deletion is requested, after which it is removed from live and backup systems within 180 days. App Check does not retain attestation material. App Check tokens remain valid for their time to live, up to 7 days, and replay protection tokens may be retained for up to 30 days. Google Play data is retained until the relevant purpose is fulfilled or the account or service is deleted, except where a longer period is required by law or Google policy |
| Google LLC Contact | United States | Device and account identifiers such as the advertising ID and app set ID; IP address and general location derived from it; device and app data; app launches, ad impressions, taps, and video views; SDK performance and diagnostic data; UMP consent choices; Firebase UID; ad placement; and reward session identifier | Ad delivery through AdMob and Google Mobile Ads; UMP consent management; ad performance and frequency measurement; rewarded ad verification; security; and fraud prevention | Transferred over encrypted networks when consent status is checked and when ads are requested, displayed, interacted with, or verified for rewards | For the period necessary for ad delivery, measurement, security, and compliance with legal obligations, in accordance with the Google Privacy Policy |
| Unity Technologies S.F. and affiliates, including ironSource DPO@unity3d.com | United States and Israel | Device identifiers such as the advertising ID and Android ID; IP address and country or general location derived from it; device manufacturer and model; operating system; language; screen and hardware data; app identifier and version; ad requests, impressions, taps, video views, installations, and other ad interaction data; and SDK logs and diagnostic information | Ad delivery through Unity Ads and ironSource Ads via AdMob mediation; measurement; frequency management; security; and fraud prevention | Transferred over encrypted networks when Unity Ads or ironSource Ads participates in a mediated ad request or when an ad is displayed or interacted with | For the period necessary for ad delivery, measurement, security, and compliance with legal obligations, in accordance with the retention criteria in the Unity privacy policy |
Users may refuse an international transfer by deleting their account in the app or submitting an international transfer refusal request to Support. If a user refuses an international transfer, we cannot provide features that require the transfer, including Firebase account authentication, Google Play account linking, purchase verification, and advertising. Account deletion may result in the deletion of account information, including cloud save data and unused in-game currency.
Changing your advertising consent in the app’s privacy settings allows you to choose whether your personal data is used for personalized advertising and related processing. This choice does not constitute a refusal of all international transfers. Even if you do not consent to personalized advertising, your IP address, device data, and ad interaction data may still be processed to deliver non-personalized or limited ads, maintain security, and prevent fraud.
When responding to a Google Play refund or chargeback review, we may send Google the order’s review response token, the operator’s refund preference and confirmation of whether sample content was provided, and usage percentages and summaries of usage times, quantities and purposes supported by the records, over an encrypted connection. We do not send an entire game save or the user’s full manager-card inventory as part of a review response.
7. Your Rights and How to Exercise Them
- In the app, go to Settings → Social Account Linking → Delete Account to delete your Firebase Authentication account, cloud save data, and on-device save data.
- If you cannot access the app, see the Account Deletion page for instructions on submitting a request.
- Use the privacy options in the app settings to review or change your advertising privacy choices.
- Submit requests to access, correct, or delete personal data or restrict its processing through customer support.
Game progress cannot be restored after account deletion. Purchase history managed by Google Play and transaction records that must be retained by law may remain with Google or the Company for the applicable retention period.
To view or confirm your transaction records or request an electronic copy, contact tinyfactory.support@junnie.games with the order ID and the scope of your request. We verify that you are the transaction party using existing account and order information, then explain or provide the relevant records. You do not need to send a payment password, full card number, or review response token. Information about other users and security secrets are excluded from the materials provided.
8. Children’s Privacy
Tiny Factory is not designed primarily for children. If we learn that a user who is below the age at which parental consent is required has submitted personal data without the required consent, we will take appropriate action, including deleting that data.
9. Security Measures
- Encryption in transit (HTTPS/TLS) and encryption of data stored in Firebase
- Request verification using Firebase Authentication, App Check, and Play Integrity
- Per-user access controls and Firestore security rules
- Server-side verification and duplicate prevention for purchase tokens and rewarded ad transactions
- Restricted operational access privileges and management of security logs
10. Friend Referrals
For referrals, server-verified authentication, Google account linking, and tutorial completion are used to validate registration. A referral ID is a public identifier, not an authentication credential. Friends’ email addresses, names, and account details are not disclosed.
| Data | Purpose and processing | Retention |
|---|---|---|
| SHA-256 hash of the account identifier, own referral ID, referring account hash and referral ID | Issue IDs, establish relationships, prevent self-referral and repeat registration. Raw Firebase UIDs, Google emails, names, and authentication tokens are not stored in dedicated referral records | Minimum lifetime participation records are kept separately after account deletion |
| Success count, claim records for up to 10 milestones, server creation/registration/claim times, notification acknowledgments | Show progress, grant rewards once, notify of new referrals | Minimum participation and claim facts remain after deletion. Ordinary user saves and action ledgers are deleted with the account |
| Server referral registration count and time for a one-minute window, unusual-pattern marker | Identify rapid repeated patterns; this signal alone does not automatically block normal users | The recent aggregate is separate from referral participation, expires after 24 hours by TTL, and is deleted on account deletion. Expired records may briefly remain while TTL deletion runs. No IP or device history is created |
| Referral ID in the web invitation URL | Display and copy the ID; pass it to the Google Play installation link. No web registration, reward claims, or account lookup | Processed while the page runs, without separate cookies, local storage, or a referral web database |
Referrals do not additionally collect raw IPs or IP hashes/HMACs, advertising IDs, IMEI, MAC addresses, device serial numbers, or contacts. Existing Firebase Authentication, App Check, Play Integrity, and service request logs follow the existing sections of this policy. Shared home, school, or Wi-Fi networks, and VPN use alone, do not cause referral rejection.
The minimum relationship and lifetime claim facts are separated from game saves with restricted access to prevent participation resets through deletion and rejoining. The implementation retains these minimum records while lifetime registration and duplicate-reward prevention rules remain in place. Clients cannot directly access or edit complete referral relationships or participation records; signed-in users receive only their own referral progress and reward status through the server.
11. Privacy and Support Contact
Data controller: JUNNIE Games
Representative and privacy officer: 어준성
Business registration no.: 822-72-00810
Email: tinyfactory.support@junnie.games
If we change this policy, we will announce the changes and their effective date on this page before they take effect.