AZIT STUDIO Privacy Policy
This policy explains what personal data AZIT STUDIO Inc. processes, why, how long it is kept, when it is transferred abroad, and how you can exercise your rights.
> This English version is provided for convenience. If it conflicts with the Korean version, the Korean version prevails.
1. General
AZIT STUDIO Inc. (the "Company") complies with the Personal Information Protection Act of Korea and processes personal information only to the minimum extent necessary to provide its services. This Privacy Policy applies to the following services operated by the Company.
| Service | Address / form | Service-specific notice |
|---|---|---|
| AZIT official website (inquiries, idea submissions, Q&A, privacy requests) | azit.studio | — |
| AZIT Account (integrated account) | accounts.azit.studio — a single login account shared by the Company's web services | — |
| Mochi: Merge Master | Google Play and App Store app | Mochi Data Handling and Deletion Notice |
| Tikkle (service ended) | Removed from the stores on 2026-08-26. Apps already installed continue to use the ranking and progress servers and ads | Tikkle data notice |
| CouchTrader (service ended) | App removed from the stores. Account database destroyed on 2026-11-04 | — (the "CouchTrader account deletion notice" is no longer published now that destruction is complete) |
- The authoritative versions of this policy and the service-specific notices are published at azit.studio/en/policies.
- Processing that differs by service is described in detail in the service-specific notice above. If this policy and a service-specific notice differ, the one more favorable to the data subject applies.
- Apps whose service has ended (Tikkle, CouchTrader): No new sign-ups or installs are accepted. The CouchTrader account database was destroyed on 2026-11-04. For Tikkle, data remaining on the servers is retained under the notice above and will be destroyed. Once the destruction schedule is set, we will announce it through this policy and a notice, and once destruction is complete, the corresponding row and notice will be removed. You may request deletion before then using the methods in Section 10.
- What this policy does not cover: The Bigdandy online store follows its own privacy policy. Services not offered to the general public or not yet launched (AZIT Blackjack, etc.) will be added to this policy when they launch. Personal information of the Company's officers and employees is described in a separate "Notice on Processing of Employee Personal Information".
2. Purposes and Items of Processing
The Company processes only the items needed for the purposes below. If a purpose changes, the Company obtains consent in advance or gives notice as required by law. For items processed without consent, the legal basis is stated.
2-1. Official website
The items below are exactly the fields on each input screen. Consent to collection and use is obtained on each screen.
| Purpose | Items | Legal basis |
|---|---|---|
| Receiving and replying to inquiries (including privacy requests) | Required: email address, inquiry type, subject, inquiry content / Optional: related service, reference link | Consent (Art. 15(1)1) |
| Reviewing idea submissions, replying, and using them for service planning and improvement | Required: email address, idea type, title, description / Optional: nickname, expected effect, reference link | Consent (Art. 15(1)1) |
| Receiving Q&A questions and replying | Required: email address, category, title, question / Optional: nickname | Consent (Art. 15(1)1) |
| Partnership, investment, press, and recruiting inquiries (business inquiry form) | Name, email address, purpose, content — stored on the website server | Consent (Art. 15(1)1) |
| Business inquiries sent directly to the Company's email address | Sender's email address and name, email content | Measures at the data subject's request (Art. 15(1)4) |
- The Company replies to inquiries from its company email (Google Workspace). Email received at the company address passes through AI summarization (Anthropic) and notification (Telegram) so that important messages can be flagged to the representative (Sections 5 and 6).
2-2. Mochi: Merge Master
| Purpose | Items | Legal basis |
|---|---|---|
| Weekly ranking (game feature) | Anonymous player identifier, nickname (if set), country (device region setting), score — submitted automatically when you finish a game with a score | Performance of contract (Art. 15(1)4) |
| In-app purchase processing | Store order number, purchase token, product, payment date and time, delivery record, failed payment verification records, recovery records following refunds | Performance of contract (Art. 15(1)4); statutory retention (Section 3) |
| Sending notifications | Push notification token, notification language, platform (Android/iOS) | Consent (when notifications are allowed, Art. 15(1)1) |
| Managing in-game currency and items (kept across reinstalls) | Marble balance, owned skins, collection progress, fragments and items, Mochi Premium subscription status | Performance of contract (Art. 15(1)4) |
| Preserving and restoring progress | Cumulative records and achievement claims, snapshots of saved games (latest 5), save/continue records (including app version and platform) | Performance of contract (Art. 15(1)4) |
| Reward mail and friend referral | Reward mail claim records, referral code and referral relationship | Performance of contract (Art. 15(1)4) |
| Preventing ranking abuse | Hash of the connecting IP address (transformed so it cannot be reversed to the original address) | Legitimate interest (Art. 15(1)6) |
| Delivering app updates (code patches) | App and release version, platform and CPU architecture, applied patch number, random per-install identifier, connecting IP address, patch download/install results (error message on failure) | Performance of contract (Art. 15(1)4) |
- This information is stored on the Company's server tied to an anonymous player identifier, without any name or email (app update information is sent to Shorebird, not to the Company's server — Section 5). On Android the identifier is a hash of the device's unique value (ANDROID_ID) combined with an app-specific value; on iOS it is a random value created at first launch and kept in the device keychain. Either way, it stays the same if you delete and reinstall the app. The server hashes it once more before storing it. Game settings are stored only on the device.
- The app has no error-report feature; inquiries from the app settings are sent from the user's own email program to the Company's email (Section 2-1).
- Details follow the app's service-specific notice (Mochi Data Handling and Deletion Notice).
2-3. AZIT Account (integrated account)
| Purpose | Items | Legal basis |
|---|---|---|
| Sign-up, login, and identity verification | Login identifier (email address), password (stored irreversibly transformed), name (optional) | Performance of contract (Art. 15(1)4) |
| Logging in with a Google account (if linked) | Google account unique ID, Google account email address | Performance of contract (Art. 15(1)4) |
| Two-step verification and passkeys (if used) | Two-step verification secret (stored encrypted), recovery codes, passkey public key | Performance of contract (Art. 15(1)4) |
| Keeping you logged in and preventing unauthorized logins | Login session token (stored irreversibly transformed), login records (irreversibly transformed value of the login identifier entered, result, IP address, browser information, date and time) | Legitimate interest (Art. 15(1)6) |
- For accounts to which the Company has granted work permissions, the services granted and the records of granting, changing, and revoking those permissions are also kept (Sections 3 and 13).
- How to delete the account is described in Section 10.
2-4. Information generated or collected automatically in all services
| Purpose | Items | Legal basis |
|---|---|---|
| Operating the services; preventing and investigating security incidents | Connecting IP address, access date and time, service usage records, device and browser information, error logs | Legitimate interest (Art. 15(1)6); Protection of Communications Secrets Act Art. 15-2 |
2-5. App advertising and ad conversion measurement (sent to Google)
- Personalized ads (if you consent): The advertising identifier (Android Advertising ID, iOS IDFA), device information (model, operating system, language), approximate location (country or region), and ad impression and click records are provided to Google (Section 4; Section 5 A).
- Non-personalized ads (if you do not consent): Ads continue to be served to keep the app free, and the information needed to request them (connecting IP address, device information, approximate location, ad impression and click records, and the advertising identifier used for frequency capping and invalid-traffic prevention) is still sent to Google. This information is not used for interest-based ads (Section 4; Section 5 B).
- Ad conversion measurement (Google Analytics): Mochi app versions 1.6.0 and earlier (Android build 52 and earlier, iOS build 30 and earlier) send sign-up completion events (when a new user is shown the welcome bonus), Mochi Premium subscription purchase events, automatically collected events such as app launches, and device information to Google for ad conversion measurement. On Android this is sent regardless of the result of the advertising consent at first launch; on iOS it is sent only if you allow tracking under App Tracking Transparency (ATT). This transmission has been removed from later builds; devices that do not update may continue to send it (Section 4; Section 5 B). The Company currently runs no Google Ads campaigns.
- You can use the app without consenting to ads.
2-6. Information not processed
The Company does not process sensitive information under Article 23 of the Personal Information Protection Act. The services covered by this policy do not process unique identification information such as resident registration numbers.
3. Retention Period
Personal information is destroyed without delay once its purpose is achieved. Information that must be retained by law, and information needed to handle disputes, is kept separately from other information, limited to those items, for the periods below. For Mochi server records, "on deletion request" means when deletion is carried out after the 7-day grace period in Section 10.
| Information | Period | Basis |
|---|---|---|
| Ranking information (anonymous identifier, nickname, country, score, IP hash) | Until a deletion request or the end of the app service | Terms of use |
| In-game currency, items, progress, reward mail, referral information | Until a deletion request or the end of the app service | Terms of use |
| Snapshots of saved games | Only the latest 5 are kept; older ones are deleted when you save (a snapshot awaiting a restore you requested is kept until restored). Deleted on request | Terms of use |
| In-app purchase and subscription records (store order number, purchase token, product, items delivered, date and time; subscription verification result and expiry; failed payment verification records; recovery records following refunds) | 5 years from March 31 of the year following the payment. After a deletion request, kept in pseudonymized form so the person cannot be identified | Enforcement Decree of the E-Commerce Act Art. 6(1)2·3; Framework Act on National Taxes Art. 85-3 |
| Non-payment records kept pseudonymized after a deletion request (wallet balance, reward mail, collection progress, weekly rewards and lottery wins, bonus marble grants, fragment migration records, referral relationships) | 1 year after deletion is carried out, then destroyed | Handling refund and payment-cancellation disputes and preventing abuse (legitimate interest, Art. 15(1)6) |
| Business inquiries (business inquiry form) | 1 year after handling is completed (closed), then name, email, and content are irreversibly de-identified | Consent |
| Records of handling inquiries and privacy requests (including website inquiries and inquiries received by Company email) | 3 years after handling is completed | Enforcement Decree of the E-Commerce Act Art. 6(1)4 (records of consumer complaints and dispute handling) |
| Idea submissions and Q&A questions (including the asker's email address and nickname) | 1 year after handling is completed (closed) (deleted without delay if deletion is requested earlier) | Consent |
| Unprocessed submissions (website inquiries, business inquiries, idea submissions, Q&A) | 3 years from submission (for shortlisted or selected idea submissions, 3 years from the last update), then name, email, and content are irreversibly de-identified | Consent |
| Push notification token (including notification language and platform) | Until the token becomes invalid because notifications are turned off or the app is deleted (deleted when notified that it is invalid). Deleted on request | Consent |
| AZIT Account information (login identifier, password, name, Google link, two-step verification and recovery codes, passkeys, login session tokens) | Until the account is deleted; deleted immediately on account deletion | Terms of use |
| AZIT Account login records | 1 year (deleted when this period ends, even after the account is deleted) | Preventing and investigating unauthorized logins (legitimate interest, Art. 15(1)6) |
| Access records of administrators (personal information handlers) to personal information processing systems (account, access date and time, IP address, data subjects processed, tasks performed) | 2 years; protected against forgery and alteration and reviewed monthly | Standards for Personal Information Security Measures Art. 8 (at least 1 year; at least 2 years for systems processing unique identification information, etc.) — the Company applies 2 years to all systems |
| Records of granting, changing, and revoking access rights to personal information processing systems (including work permission records of AZIT Accounts) | 3 years | Standards for Personal Information Security Measures Art. 5(3) |
| Access logs such as connecting IP address and access time | 3 months | Protection of Communications Secrets Act Art. 15-2; its Enforcement Decree Art. 41(2) |
| Information contained in server backups | Up to 21 days after the backup is created (14 days of retention + 7 days pending deletion) | Disaster recovery |
- The CouchTrader account database was destroyed on 2026-11-04. Paid purchase records (42 purchases, July–August 2026) are kept separately as required by the Act on the Consumer Protection in Electronic Commerce, limited to purchase date, product, purchase status, member identifier, and nickname, and will be destroyed in August 2031. Retention and destruction of Tikkle server data follow Section 1 and its notice.
4. Provision of Personal Information to Third Parties
The Company does not provide personal information to third parties beyond the scope stated in this policy, except where the data subject has consented or where the law specifically provides otherwise. Current provisions are as follows; for provisions made without consent, the basis is stated.
| Recipient | Purpose | Items | Retention and use period | Legal basis |
|---|---|---|---|---|
| Google LLC (Google AdMob) — personalized ads | Serving personalized ads, measuring ad performance, preventing invalid ad traffic | Advertising identifier, device information, approximate location, ad impression and click records | As set out in Google's privacy policy | Consent (Art. 17(1)1) |
| Google LLC (Google AdMob) — non-personalized ads (if you do not consent) | Serving non-personalized ads to keep the app free, frequency capping and aggregate reporting, preventing invalid ad traffic | Connecting IP address, device information, approximate location, ad impression and click records, advertising identifier (for frequency capping and fraud prevention) | As set out in Google's privacy policy | Sent to the extent necessary to serve ads so the app can be used free of charge (provision of the service) — performance of contract (Art. 15(1)4) and legitimate interest (Art. 15(1)6) |
| Google LLC (Google Analytics for Firebase) — Mochi 1.6.0 and earlier | Ad conversion measurement (counting sign-ups and subscription purchases) | App instance identifier, sign-up and subscription purchase events (product, amount, currency), automatically collected events such as app launches and sessions, device information, approximate location, Android Advertising ID (if use of the advertising ID is allowed in the device settings) | Event-level data for 2 months (Google Analytics retention setting) | Android (build 52 and earlier): sent without separate consent; removed in later builds / iOS (build 30 and earlier): sent only if tracking is allowed under App Tracking Transparency (ATT) |
- The provision to Google Play Games Services (leaderboards and achievements) listed in the previous version (effective 2026-07-14) has been removed because the app no longer uses that feature.
5. Cross-Border Transfer of Personal Information
A. Cross-border transfer by provision to a third party — separate consent (Art. 28-8(1)1)
| Item | Details |
|---|---|
| Recipient | Google LLC (contact: as published at policies.google.com/privacy) |
| Country of transfer | The United States and other countries where Google operates data centers |
| Time and method | Encrypted transmission over the network at app launch and when an ad is requested |
| Items transferred | Advertising identifier, device information, approximate location, ad impression and click records |
| Purpose and retention | Same as the personalized-ads row of the table in Section 4 |
| How to refuse, and effect | Refuse on the consent screen at first launch, or withdraw at any time in the app settings or via the contact in Section 12. If you refuse, non-personalized ads unrelated to your interests are shown instead of personalized ads, and use of the app is not restricted. The information in B below is still sent for non-personalized ads |
B. Information sent to Google without consent
| Recipient | Country | Time and method | Items | Purpose | Retention | Basis |
|---|---|---|---|---|---|---|
| Google LLC — Google AdMob (non-personalized ads) | The United States and other countries where Google operates data centers | Encrypted transmission when an ad is requested | Same as the non-personalized-ads row in Section 4 | Serving non-personalized ads to keep the app free, frequency capping and aggregate reporting, preventing invalid ad traffic | As set out in Google's privacy policy | Sent to the extent necessary to serve ads so the app can be used free of charge (provision of the service) |
| Google LLC — Google Analytics for Firebase (Mochi 1.6.0 and earlier) | United States and others | Encrypted transmission while the app is used | Same as the Google Analytics row in Section 4 | Ad conversion measurement | Event-level data for 2 months (Google Analytics retention setting) | Android (build 52 and earlier): sent without separate consent; removed in later builds / iOS (build 30 and earlier): only if tracking is allowed under ATT |
- If you do not want the non-personalized ad transmission, stop using and delete the app. The Google Analytics transmission in Android 1.6.0 and earlier cannot be turned off in the app; it stops when you update to the latest version.
C. Cross-border transfer by outsourcing or storage — disclosed through this policy (Art. 28-8(1)3)
| Recipient (contact) | Country | Time and method | Items | Purpose | Retention |
|---|---|---|---|---|---|
| Vercel Inc. (privacy@vercel.com) | United States | Encrypted transmission when the web service is used | Web access logs such as connecting IP and request records; user information shown on admin screens (nickname, player ID, payment history) | Hosting web pages and admin screens | 1 day (Vercel runtime log retention) |
| Google LLC — Firebase Cloud Messaging | United States and others | Encrypted transmission when a notification is sent | Push notification token, notification content | Sending app notifications | Per Google's policy after delivery |
| Google LLC — Google Play payment verification | United States and others | Encrypted transmission right after payment and during daily subscription status re-checks and refund lookups | Store order number, purchase token | Verifying payment authenticity | Until verified (the Company's own retention follows Section 3) |
| Apple Inc. — App Store payment verification | United States | Encrypted transmission right after payment and during daily subscription status re-checks and refund lookups | Transaction identifier | Verifying payment authenticity | Until verified |
| Google LLC — Google Workspace (company email) | United States and others | Encrypted transmission when sending and receiving inquiry replies and business inquiry emails | Email address, name (business inquiries), email body | Replying to inquiries, receiving business inquiries | 3 years after handling is completed |
| Anthropic PBC (privacy@anthropic.com) | United States | Encrypted transmission within minutes after an email arrives at the company address | Sender, recipient, and CC addresses and names, subject, time received, and body of emails received at the company address | Selecting and summarizing important emails (AI analysis) | Anthropic deletes within 30 days and does not use the data for model training. Summaries are not stored on the Company's server (only identifiers of processed emails are kept for 90 days) |
| Telegram Messenger Inc. (telegram.org/privacy) | Countries where Telegram data centers are located (multiple) | Encrypted transmission right after summarization | Sender, subject, summary | Notifying the representative of important emails | 1 month (auto-deleted in the representative's chat) |
| Code Town, Inc. (Shorebird, privacy@shorebird.dev) | United States | Encrypted transmission when checking for and downloading updates at app launch | App and release version, platform and CPU architecture, applied patch number, random per-install identifier, connecting IP address, patch download/install results (error message on failure) | Delivering Mochi app updates (code patches) | The period set in Shorebird's privacy policy |
- How to refuse, and effect: Because these transfers are necessary to provide the services, you may refuse by stopping use of the relevant service and requesting deletion (Section 10).
- The servers and databases (AWS) are located in the Seoul region, so they do not constitute a cross-border transfer. (The previous version incorrectly stated "the United States, etc.")
6. Outsourcing of Personal Information Processing
| Processor | Outsourced task |
|---|---|
| Amazon Web Services Korea LLC (service provided by Amazon Web Services, Inc.) | Hosting servers, databases, file storage, and backups (Seoul region) |
| Vercel Inc. | Hosting web pages and admin screens |
| Google LLC | Sending app notifications (Firebase Cloud Messaging), Google Play payment verification, company email (Google Workspace — replying to inquiries) |
| Apple Inc. | App Store payment verification |
| Anthropic PBC | Summarizing important emails received at the company address (AI analysis) |
| Telegram Messenger Inc. | Delivering email summary notifications to the representative |
| Code Town, Inc. (Shorebird) | Delivering Mochi app updates (code patches) |
- Outsourcing contracts (each provider's data processing addendum) prohibit processing beyond the purpose and set out safeguards, limits on sub-processing, incident notification, and liability for damages, and the Company reviews its processors once a year. If a processor changes, the Company updates this policy and gives notice.
7. Destruction Procedure and Method
- Procedure: Information whose retention period has ended or whose purpose has been achieved is identified and destroyed with the approval of the privacy officer. Automated destruction jobs run according to defined rules, and their results are recorded.
- Method: Electronic files are erased in a way that cannot be recovered (deleting database rows or irreversible de-identification, and deleting objects in file storage), and paper is shredded.
- Information retained by law is kept separately from other information and destroyed without delay when its period ends.
8. Processing of Pseudonymized Information
For Mochi users who have requested deletion, the server records below are not deleted but kept in pseudonymized form, with the user identifier replaced by another value.
| Records | Purpose | Period |
|---|---|---|
| In-app purchase and subscription records | Statutory retention; handling refund and payment-cancellation disputes | The statutory period in Section 3 (5 years from March 31 of the year following the payment) |
| Wallet balance, reward mail, collection progress, weekly rewards and lottery wins, bonus marble grants, fragment migration records, referral relationships | Handling refund and payment-cancellation disputes and preventing abuse | 1 year after deletion is carried out, then destroyed |
The Company does not provide pseudonymized information to third parties or use it for other purposes, and does not keep any information linking the replacement value back to the original identifier.
9. Cookies, Advertising Identifiers, and Other Automatic Collection Tools
- Web: The official website does not use cookies for visitors and do not use tracking tags for advertising or analytics (the Company's administrator login cookies are unrelated to users).
- The AZIT Account (accounts.azit.studio) uses a login session cookie only for people who log in, and not for advertising or analytics.
- Apps: The advertising identifier is used to serve ads.
- Android: Settings > Google > Ads > "Reset advertising ID" or "Delete advertising ID"
- iOS: Settings > Privacy & Security > Tracking > turn off "Allow Apps to Request to Track", or decline the tracking request at the app's first launch
- The third-party collection tools included in the app are as follows.
| Tool (provider) | App | Items collected | Purpose | How to refuse |
|---|---|---|---|---|
| Google Mobile Ads SDK (Google LLC) | Mochi | Advertising identifier, device information, ad interactions | Serving and measuring ads | Declining on the consent screen or withdrawing in the app settings stops personalized ads (non-personalized ads and their transmission continue — Section 2-5); device advertising ID settings |
| Google Analytics for Firebase (Google LLC) | Mochi 1.6.0 and earlier | App instance identifier, event records such as sign-up and subscription purchase, device information | Ad conversion measurement | iOS: decline tracking under App Tracking Transparency (ATT). Android (build 52 and earlier): cannot be turned off in the app — removed in later builds (stops when you update) |
| Shorebird updater (Code Town, Inc.) | Mochi | App and release version, platform and CPU architecture, patch number, random per-install identifier | Delivering app updates | Cannot be turned off in the app (delete the app) |
| Firebase Cloud Messaging (Google LLC) | Mochi | Push notification token | Sending notifications | Turn off in the device notification settings |
- In regions that require separate consent, such as the European Economic Area (EEA) and the United Kingdom, a separate advertising consent flow is provided at the app's first launch.
10. Rights of Data Subjects and Legal Representatives and How to Exercise Them
- Data subjects may at any time request access to, correction or deletion of, or suspension of processing of their personal information, withdraw consent, and refuse cross-border transfer.
- How: (1) the privacy request page on the official website (azit.studio/en/trust/privacy-requests), or (2) the email in Section 12. Only the minimum procedure necessary to verify identity is required, and it is no more difficult than signing up for or using the service.
- The Company notifies the result within 10 days of receiving a request. If a request is refused or delayed, the Company gives the reason and explains how to object.
- Deleting Mochi server records: Mochi has no accounts, so please include your nickname (or your referral code shown in the app settings) so we can find your records. The app currently has no in-app deletion request screen, so please use (1) or (2) above. Once the Company registers the deletion request, you can cancel it for 7 days; after 7 days, deletion is carried out in the daily early-morning run. The records in Section 8 are then pseudonymized and kept only for the stated period, and the rest is deleted. Deleting the app alone does not delete server records.
- Deleting an AZIT Account: after logging in, you can delete the account yourself once you confirm your identity again with your password (plus a verification code or recovery code if two-step verification is turned on). Accounts to which the Company has granted work permissions cannot be deleted by the user; the person in charge (the Company) removes the permissions and then deletes the account. On deletion, the account and authentication information (password, Google link, two-step verification, passkeys, login session tokens) are deleted immediately, and login records are deleted after the retention period in Section 3 (1 year). You may also request deletion through (1) or (2) above.
- Requests may be made through an agent, in which case a power of attorney is required. The rights of children under 14 are exercised by their legal representative.
11. Children Under 14
The Company's services are not primarily directed at children under 14, and the Company does not knowingly collect personal information of children. If the Company learns that a child's information has been collected, it destroys it without delay. Mochi is not an app subject to Google Play's Families policy (directed at children under 13).
12. Privacy Officer
| Role | Details |
|---|---|
| Privacy officer | Ryunkwang Kim, Inside Director (with representative authority) |
| haru@azit.studio |
You may contact the above for privacy inquiries, complaints, and remedies for damage, and the Company will respond without delay.
13. Measures to Ensure the Security of Personal Information
In accordance with Article 29 of the Personal Information Protection Act and its internal management plan, the Company takes the following measures.
- Administrative: establishing and implementing an internal management plan (with an annual implementation review), minimizing the number of personal information handlers, and regular training
- Technical: access rights management, limits on administrator login attempts, encrypted storage of passwords and important information, HTTPS for all transmission, retention of administrator access records (account, access date and time, IP address, data subjects processed, tasks performed) for 2 years with protection against forgery and alteration and monthly review, retention of records of granting, changing, and revoking access rights for 3 years, and security updates
- Physical: servers operated in a cloud data center (AWS Seoul region), and locked management of work devices and auxiliary storage media
14. Automated Decisions
The Company does not make decisions that significantly affect individuals by fully automated means without human involvement.
15. Remedies for Infringement of Rights
| Organization | Contact |
|---|---|
| Personal Information Dispute Mediation Committee | 1833-6972 / www.kopico.go.kr |
| Personal Information Infringement Report Center (KISA) | 118 / privacy.kisa.or.kr |
| Supreme Prosecutors' Office, Cyber Investigation Division | 1301 / www.spo.go.kr |
| Korean National Police Agency, Cyber Bureau | 182 / ecrm.police.go.kr |
16. Changes to This Policy
- Effective date: 2026-11-11
- Previous version: version effective 2026-07-14 (2026-07-14 to 2026-11-10) — previous versions remain available on the policy page.
- This revision rewrites the whole policy to match actual processing, together with the change of company name. It does not reduce users' rights or start any new collection; it describes processing that was already taking place as it actually is. The main changes are listed in the table below.
Summary of Changes
| Section | Previous version (2026-07-14) | This version (2026-11-11) | Reason |
|---|---|---|---|
| Controller | Synub Inc. | AZIT STUDIO Inc. | Change of company name |
| Services covered | "Apps, web, and games operated by Synub" | Lists services and links to service-specific notices; states that Bigdandy and employees are covered separately | Clarify scope |
| Items processed | Common items only, "technical logs, etc." | Tables by service with legal bases. Adds Mochi payments, currency, progress, saved-game snapshots, referrals, reward mail, and app update delivery, and the official website's business inquiry form. The ranking's legal basis is stated as a game feature (performance of contract). Adds the AZIT Account. Services not yet launched (AZIT Blackjack) are not included; Tikkle, which has ended, is shown with a notice on retained data, and CouchTrader is shown as account database destroyed on 2026-11-04 | Match actual processing; no "etc." |
| Retention | "A reasonable period" | Specific period per item (payments 5 years, inquiries 3 years, business inquiries, idea submissions, and Q&A 1 year, pseudonymized non-payment records after a deletion request 1 year, access logs 3 months, administrator access records 2 years, access-rights records 3 years, etc.) | No abstract periods |
| Retention (idea submissions, Q&A, business inquiries) | "A reasonable period" | 1 year after handling is completed (closed). Website inquiries and inquiries received by Company email remain 3 years. Unprocessed submissions are capped at 3 years from submission | Shortened to the period needed for review and reply; inquiries are records of consumer complaints and dispute handling, so 3 years |
| Cross-border transfer (AWS) | United States, etc. | Seoul region — not a cross-border transfer | Correction of fact |
| Outsourcing and cross-border transfer | AWS, Vercel / Google ads and games services | Adds Google (notifications, payment verification, company email), Apple (payment verification), Anthropic (email summarization), Telegram (email notifications), Shorebird (app update delivery); removes Play Games Services. Separates personalized ads (consent) from non-personalized ads (sent without consent) and discloses the Google Analytics ad conversion measurement in Mochi 1.6.0 and earlier | Match actual SDKs and code |
| Pseudonymized information | None | New: after a deletion request, payment and subscription records (statutory 5 years) and non-payment reward and wallet records (1 year) kept pseudonymized | Match actual processing |
| Privacy officer | Co-representatives, two emails | Ryunkwang Kim designated among the two inside directors with representative authority; haru@azit.studio | Art. 31 and Enforcement Decree Art. 32 (designated among representatives and officers); matches registered title |
| Security measures | General wording | Lists measures actually in place (limits on administrator login attempts, 2-year administrator access records with forgery protection and monthly review, 3-year records of granting, changing, and revoking access rights, etc.) | Only measures actually implemented |
| AZIT Account | None | New: items processed, retention, and how to delete the account (self-deletion after re-confirming identity; work accounts deleted by the Company after removing permissions; login records 1 year) | Match actual processing |
| Automated decisions | None | New | Art. 37-2 |