Privacy Policy

DailySudoku is a Sudoku game available on the web and on iOS and Android apps. It works without an account, and your data is stored on your device or in your browser. This policy applies to all platforms.

The following applies to single-player play. For what is sent to our servers during 1-on-1 matches, see section 6. The iOS and Android apps store your game progress, settings, completion and failure records, and daily completion status locally on your device. Starting with version 2.2.0, to send the daily-puzzle reminder once a day around the time you usually play, the apps store on your device, even if you have not turned reminders on, the start times from your 7 most recent days of daily-puzzle play (one per day) and when you last opened the app; if you turn reminders on, they also store a record of scheduled and sent reminders (entries older than 30 days are deleted when the app next reschedules reminders). To check that this record was created on this device, the iOS app also stores the device's identifier for vendor (IDFV) with it. The service provider does not access this data, but if your device's OS backup (Google or Apple) is enabled, this data may be included in the backup and stored in the provider's cloud (however, the record of scheduled and sent reminders is excluded from backups on Android). The web stores your in-progress game (resume), completion and failure records, daily completion status, and gameplay and appearance settings (theme, accent color, etc.) in your browser's localStorage; this data stays only in your browser and is not sent anywhere. The web currently uses Coupang Partners (affiliate advertising) and Firebase / Google Analytics (GA4). The web pages contain only a Google AdSense site-verification meta tag (our publisher ID) and do not load the AdSense script; no AdSense ads are currently displayed (details in section 4). The web also uses Kakao's advertising platform, Kakao AdFit. Kakao may automatically collect and use, from your browser, an advertising identifier, cookies and similar tracking technologies (including browser storage), device and browser information (device type, OS, browser version, IP address, etc.), and behavioral data such as ad impressions and clicks — for ad serving, improving ad quality, and providing personalized ads — and, under Kakao's policy, Kakao does not serve personalized ads to children under 14. Kakao states that it retains behavioral data that cannot identify a user for up to one year, after which the data is destroyed or stored separately (see section 4 for details). While a Coupang ad is shown, the ad frame sends your IP address, browser and device information (User-Agent), and the referring page address to Coupang, and Coupang's domain may store cookies in your browser (shown only to visitors in Korea — see section 4 below). Firebase / GA4 anonymously collects usage-analytics events such as puzzle start, completion, and hint use and sends them to Google (no personally identifiable information or advertising identifier included). You can turn off usage-analytics collection at any time in Settings. Starting with iOS app version 2.0.0, the iOS app uses Coupang Partners and Google AdMob advertising, Firebase usage analytics (Analytics), Firebase crash and performance diagnostics (Crashlytics), and an ad-removal in-app purchase. It also uses Game Center leaderboards, and on iPad recognizes Apple Pencil handwriting input entirely on-device using Core ML — no stroke or image data is collected or sent anywhere. Coupang Partners ads appear only in select regions within Korea, shown in a separate in-app web view (WKWebView), and this frame sends your IP address, device information (User-Agent), and the referring page address to Coupang. AdMob ads collect device and app information, IP-based coarse location, ad-interaction data, and SDK performance and diagnostic data to serve ads, control frequency, and measure performance; if you have allowed App Tracking Transparency (ATT), AdMob additionally uses your advertising identifier (IDFA) to serve personalized ads, and if you have not, it serves non-personalized ads without an advertising identifier. Firebase usage analytics collects events such as puzzle start, completion, and hint use under an anonymous app-instance ID that does not include an advertising identifier, and Firebase crash and performance diagnostics continuously collects crash and performance data to keep the app working correctly (neither is linked to your identity). The ad-removal in-app purchase is processed by Apple's StoreKit — we do not have access to your card information, and only store whether the purchase was completed on your device. If you are signed into Game Center, the app submits your daily-puzzle score to a Game Center leaderboard so you can compare results with other players; if you are not signed in, nothing is submitted. Starting with iOS app version 2.1.0, the iOS app includes the Kakao AdFit SDK. Kakao collects device and app information and behavioral data such as ad impressions and clicks to serve ads, control frequency, and measure performance; if you have allowed App Tracking Transparency (ATT), Kakao additionally uses your advertising identifier (IDFA). The SDK also collects performance and crash data to keep the app working correctly. Under Kakao's policy, Kakao does not serve personalized ads to children under 14. Starting with version 2.2.0, the iOS app includes the Unity Ads SDK (Unity Technologies) as a bidding mediation partner of Google AdMob. To take part in the ad auctions AdMob runs and to serve and measure ads, Unity Ads collects and processes device and app information (such as device language, make, model, screen size, and connection type), your IP address and IP-based coarse location (country level), ad-interaction data such as impressions and clicks, and SDK performance diagnostics; if you have allowed App Tracking Transparency (ATT), it additionally uses your advertising identifier (IDFA). In its SDK disclosures, Unity also states that it may collect a user or installation identifier that Unity assigns (for app functionality), your in-app purchase history (for advertising and analytics), and app activity such as app launches and usage times (for advertising, analytics, and fraud prevention, collected depending on Unity's settings), and that it also uses the information above for ad-fraud prevention, security, and compliance. If you report a Unity ad, the content of your report is sent to Unity so it can be handled (customer support). Depending on Unity's server-side settings, motion-sensor (accelerometer) readings, ad-quality verification data, and common attributes gathered by Unity's coherence library may also be collected. Unity ads are requested only through AdMob — the app never requests ads from Unity directly (see section 4 for how your consent choices are passed on). Starting with version 2.2.0, the iOS app also includes the Meta Audience Network SDK (Meta Platforms) as a bidding mediation partner of Google AdMob. To take part in the ad auctions AdMob runs and to serve and measure ads, Meta Audience Network collects and processes device identifiers (your advertising identifier (IDFA) if you have allowed App Tracking Transparency (ATT)), device attributes (such as device model, screen size, operating system, and SDK versions), your IP address, ad-performance information such as impressions, clicks, and viewability, and crash and other diagnostic information. In its SDK disclosures, Meta states that it may use advertising data and device identifiers to track you across other companies' apps and websites. Meta ads are likewise requested only through AdMob — the app never requests ads from Meta directly (see section 4 for how your consent choices and the Limited Data Use signal are passed on). Starting with Android app version 2.0.0, the Android app uses Coupang Partners and Google AdMob advertising, Firebase usage analytics (Analytics), and an ad-removal in-app purchase. It also uses Google Play Games Services leaderboards. The ad provider receives your IP address, browser and device information (User-Agent), and the referring page address as part of loading an ad; AdMob additionally collects and processes your device's advertising identifier, IP-based coarse location, device and app information, and ad-interaction data to serve ads, control frequency, and measure performance; the advertising and Play Games SDKs also collect diagnostic information about how the app and the SDKs are performing, such as app launch time. Starting with Android app version 2.0.1, the Android app includes the Kakao AdFit SDK. This SDK is active from that version onward; Kakao automatically collects and uses, for the same purposes, an advertising identifier (such as AAID), device and browser information (device type, OS, browser version, IP address, etc.), and behavioral data such as ad impressions and clicks (see section 4 for details). Under Kakao's policy, Kakao does not serve personalized ads to children under 14. Starting with Android app version 2.1.0, the Android app includes Firebase crash and performance diagnostics (Crashlytics), which continuously collects crash and performance data to keep the app working correctly (not linked to your identity). Coupang Partners ads are shown only in select regions within Korea; to determine the region, the app makes a single request to our own endpoint (dailysudoku.app), which derives your approximate city from that request's IP address and returns only the city name — no third-party location lookup service is used, and the city name is used only to choose which ad to show. The ad-removal in-app purchase is processed by Google Play Billing — we do not have access to your card information, and only store whether the purchase was completed on your device. If you are signed in to Google Play Games, the app submits your daily-puzzle score — tagged with the puzzle's date — to a Play Games leaderboard so you can compare results with other players; signing in is your choice, and if you are not signed in, nothing is submitted. Starting with version 2.2.0, the Android app includes the Unity Ads SDK (Unity Technologies) as a bidding mediation partner of Google AdMob. To take part in the ad auctions AdMob runs and to serve and measure ads, Unity Ads collects and processes your advertising identifier (AAID), device and app information (such as device language, make, model, screen size, and connection type), your IP address and IP-based coarse location (country level), ad-interaction data such as impressions and clicks, and SDK performance diagnostics. In its SDK disclosures, Unity also states that it may collect a user or installation identifier that Unity assigns (for app functionality), your in-app purchase history (for advertising and analytics), and app activity such as app launches and usage times (for advertising, analytics, and fraud prevention, collected depending on Unity's settings), and that it also uses the information above for ad-fraud prevention, security, and compliance. If you report a Unity ad, the content of your report is sent to Unity so it can be handled (customer support). Depending on Unity's server-side settings, motion-sensor (accelerometer) readings, ad-quality verification data, and common attributes gathered by Unity's coherence library may also be collected. On Android, whether app-store apps are installed on your device (such as the Google Play Store and Galaxy Store; Unity's servers can add to the list checked) is also sent to Unity for ad serving and analytics. Unity ads are requested only through AdMob — the app never requests ads from Unity directly (see section 4 for how your consent choices are passed on). Starting with version 2.2.0, the Android app also includes the Meta Audience Network SDK (Meta Platforms) as a bidding mediation partner of Google AdMob. To take part in the ad auctions AdMob runs and to serve and measure ads, Meta Audience Network collects and processes device identifiers such as your advertising identifier (AAID), device attributes (such as device model, screen size, operating system, and SDK versions), your IP address, and ad-performance information such as impressions, clicks, and viewability; if the SDK runs into an error, crash information may also be sent to Meta. Meta ads are likewise requested only through AdMob — the app never requests ads from Meta directly (see section 4 for how your consent choices and the Limited Data Use signal are passed on).

We use it to save game progress, retain settings, compile completion records and statistics (app), diagnose errors, and improve the service. From version 2.2.0, the apps use daily-puzzle start times and the reminder record only to choose the reminder time and to send the reminder no more than once a day. Coupang Partners ads on the web are affiliate ads: if you purchase a product through an ad, we receive a commission from Coupang. Web usage-analytics data from Firebase / GA4 (puzzle start, completion, hint use, etc.) is used to analyze usage and improve the service. The web's Google AdSense meta tag is used only to verify site ownership; no AdSense ads are currently displayed. Kakao AdFit is used to serve ads, control frequency, and measure performance. On iOS (starting with version 2.0.0), ad data is used to serve ads, control frequency, and measure performance, and Coupang Partners ads work the same affiliate way as on the web. iOS Firebase usage analytics is used to analyze usage and improve the service, and Firebase crash and performance diagnostics is used to diagnose errors and keep the app stable. The ad-removal in-app purchase removes banner, interstitial, app-open, and native ads; rewarded ads are shown only when offered by the app and you choose to watch them. Game Center leaderboard integration lets you compare your daily-puzzle results with other players. Kakao AdFit on iOS is likewise used to serve ads, control frequency, and measure performance. Unity Ads on iOS (starting with version 2.2.0) is used to serve and measure ads through AdMob mediation, for analytics, for ad-fraud prevention, security, and compliance, and to provide SDK functions such as handling ad reports. Meta Audience Network on iOS (starting with version 2.2.0) is used to serve and measure ads through AdMob mediation, for analytics, and to diagnose SDK errors. On Android (starting with version 2.0.0), ad data is used to serve ads, control frequency, and measure performance, Coupang Partners ads work the same affiliate way as on the web, and Android Firebase usage analytics is used to analyze usage and improve the service. Kakao AdFit on Android is likewise used to serve ads, control frequency, and measure performance. Unity Ads on Android (starting with version 2.2.0) is used to serve and measure ads through AdMob mediation, for analytics, for ad-fraud prevention, security, and compliance, and to provide SDK functions such as handling ad reports. Meta Audience Network on Android (starting with version 2.2.0) is used to serve and measure ads through AdMob mediation, for analytics, and to diagnose SDK errors. Android Firebase crash and performance diagnostics (starting with version 2.1.0) is used to diagnose errors and keep the app stable. The Android Play Games leaderboard lets you compare your daily-puzzle results with other players.

Data related to Coupang Partners ads on the web is sent to Coupang (subject to Coupang's privacy policy). Coupang ads on the web run only inside a frame on an isolated domain (ads.dailysudoku.app) separated from this site, and cannot access data this site has stored. Kakao AdFit banners, by contrast, run directly inside the page — the AdFit script operates in the same execution context as the page itself, because Kakao AdFit's operating policy does not allow calls made from an isolated frame. AdFit-related data is sent to Kakao (subject to Kakao's privacy policy). Third-party web ads are shown regardless of your cookie setting; that setting controls whether your data may be used for advertising, not whether ads appear. Visitors in Seoul, Busan, or Jeju are shown Coupang Partners ads; visitors in all other regions are shown Kakao AdFit banners. If the selected third-party ad fails to load, only our own (Object) house ad is shown. The web pages contain only a site-verification meta tag and do not load Google's AdSense script, so no data is sent to Google through AdSense. No AdSense ads are currently displayed. Web usage-analytics events from Firebase / GA4 are sent to Google (no personally identifiable information, no advertising identifier (IDFA); subject to Google's privacy policy). Firebase Remote Config, which we use to switch between ad providers, uses a Firebase installation ID to distinguish app installations when it delivers configuration values. Web usage-analytics collection does not use a separate consent flow — it operates under this policy's notice and the service provider's release approval, and you can turn off collection at any time in Settings (turning it off stops any new data from being sent from this device immediately). On iOS (starting with version 2.0.0), ad-related data is sent to Coupang and Google (AdMob) respectively, and starting with version 2.2.0 also to Unity Technologies (Unity Ads) through AdMob mediation (subject to each company's privacy policy). The fallback ad shown when no ad can be loaded is our own (Object) asset and sends no data to third parties. In regions where consent is required (such as the European Economic Area and the UK), we first gather consent for ad personalization through Google's User Messaging Platform (UMP). Ads are shown whether or not you consent: without consent, AdMob serves ads without using your data for personalization, while Kakao AdFit has no way to receive that choice — you can opt out directly in Kakao's own advertising settings (see section 6). Your consent choice in regions where consent is required (such as the European Economic Area, the UK, and Switzerland) is also passed on to Unity Ads in the industry-standard format (IAB TCF), so the same choice applies there. In regions where US state privacy laws apply, as soon as Google UMP has recorded on your device that they apply, the app sends Unity Ads a 'do not sell or share my personal information' (no-consent) signal regardless of your choice, so Unity does not use your personal information for personalized ads (if the consent message cannot be loaded on first launch, this signal may be briefly absent until that record exists). Starting with version 2.2.0, ad-related data is also sent to Meta Platforms (Meta Audience Network) through AdMob mediation (subject to Meta's privacy policy). Because Meta Audience Network is not registered in the industry-standard format (IAB TCF), your consent choice in regions where consent is required is passed on to Meta through Google's Additional Consent mechanism, so the same choice applies there. In addition, the app always sets a Limited Data Use (LDU) signal for Meta before starting the ad SDKs; if your location falls within a US state where this signal applies, Meta processes your data under Limited Data Use (Meta determines this from your location). Firebase usage-analytics events are sent to Google (no personally identifiable information, no advertising identifier; subject to Google's privacy policy) — this collection does not use a separate consent flow and operates under this policy's notice and the service provider's release approval, and iOS currently has no separate setting to turn it off. The iOS app uses Firebase Remote Config to deliver ad-unit IDs, frequency settings, format-specific disable switches, and provider-forcing values; a Firebase installation ID distinguishes app installations when those configuration values are delivered. On iOS, users who have purchased ad removal also fetch Remote Config and go through the consent and ad-SDK startup flow, because rewarded ads are shown only when offered by the app and they choose to watch them. Firebase crash and performance diagnostics data is also sent to Google (Firebase) and is collected continuously without separate consent, on the basis of our legitimate interest in keeping the app working correctly (not linked to your identity). Payment for the ad-removal in-app purchase is processed by Apple (StoreKit) — we do not receive or store your payment card information. Game Center leaderboard data — your Game Center player identity and daily-puzzle score — is sent to Apple, governed by Apple's Game Center privacy policy; this requires you to be signed into Game Center, and nothing is sent if you are not. Data related to Kakao AdFit on iOS is sent to Kakao (subject to Kakao's privacy policy). On Android (starting with version 2.0.0), the ad-related data above is sent to Coupang and Google (AdMob) respectively, and starting with version 2.2.0 also to Unity Technologies (Unity Ads) through AdMob mediation (subject to each company's privacy policy). Kakao AdFit-related data is sent to Kakao (subject to Kakao's privacy policy). The Android app uses Firebase Remote Config to deliver ad-unit IDs, frequency settings, format-specific disable switches, and provider-forcing values; a Firebase installation ID distinguishes app installations when those configuration values are delivered. On Android, users who have purchased ad removal also fetch Remote Config and go through the consent and ad-SDK startup flow, because rewarded ads are shown only when offered by the app and they choose to watch them. The fallback ad shown when no ad can be loaded is our own (Object) asset and sends no data to third parties. The approximate city used to decide whether a Coupang ad can be shown is determined by our own endpoint (dailysudoku.app), which returns only the city name — your IP address is not sent to a third-party location lookup service for this purpose. On Android, in regions where consent is required (such as the European Economic Area and the UK), we first gather consent for ad personalization through Google's User Messaging Platform (UMP). Ads are shown whether or not you consent: without consent, AdMob serves ads without using your data for personalization, while Kakao AdFit has no way to receive that choice — you can opt out directly in Kakao's own advertising settings (see section 6). Your consent choice in regions where consent is required (such as the European Economic Area, the UK, and Switzerland) is also passed on to Unity Ads in the industry-standard format (IAB TCF), so the same choice applies there. In regions where US state privacy laws apply, as soon as Google UMP has recorded on your device that they apply, the app sends Unity Ads a 'do not sell or share my personal information' (no-consent) signal regardless of your choice, so Unity does not use your personal information for personalized ads (if the consent message cannot be loaded on first launch, this signal may be briefly absent until that record exists). Starting with version 2.2.0, ad-related data is also sent to Meta Platforms (Meta Audience Network) through AdMob mediation (subject to Meta's privacy policy). Because Meta Audience Network is not registered in the industry-standard format (IAB TCF), your consent choice in regions where consent is required is passed on to Meta through Google's Additional Consent mechanism, so the same choice applies there. In addition, the app always sets a Limited Data Use (LDU) signal for Meta before starting the ad SDKs; if your location falls within a US state where this signal applies, Meta processes your data under Limited Data Use (Meta determines this from your location). On Android, the usage-analytics events above are sent to Google (no personally identifiable information, no advertising identifier; subject to Google's privacy policy). Firebase crash and performance diagnostics data is also sent to Google (Firebase) and is collected continuously without separate consent, on the basis of our legitimate interest in keeping the app working correctly (not linked to your identity). Payment for the ad-removal in-app purchase on Android is processed by Google (Play Billing) — we do not receive or store your payment card information. Play Games leaderboard data — your Play Games player identity and your daily-puzzle score, tagged with the puzzle's date — is sent to Google (Play Games Services), governed by Google's privacy policy; this requires you to be signed in to Play Games, and nothing is sent if you are not. That leaderboard is a public one, so a submitted score and the Play Games profile it belongs to can be visible to other players. We will also note any other features introduced in this document, and we do not otherwise share or sell your data to third parties.

The apps store data in your device's local storage (Android DataStore/Room and an app-only file excluded from backups, iOS local storage), and the web stores data in your browser's localStorage. Clearing storage or removing the app deletes the local data. Our site does not use server session cookies, as it is a static site with no server sessions. However, while a Coupang ad is shown, the ad frame may store cookies from Coupang's domain in your browser, subject to Coupang's policies. Kakao AdFit's script runs directly inside the page, so the cookies and similar technology it stores (including browser storage) may also be saved under this site's own domain, unlike Coupang's. Cookies from Kakao's and Daum's domains may likewise be stored in your browser while AdFit ads are loaded. Kakao's policy applies to how that information is handled. Clearing your browser's site data removes them. Third-party vendors, including Google, may use cookies to serve ads based on a user's prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads to users based on their visits to this site and/or other sites on the Internet. You can opt out of personalized advertising in Google's Ads Settings (https://www.google.com/settings/ads), or opt out of third-party vendors' use of cookies for personalized advertising at https://www.aboutads.info/choices/.

This section applies only when you use the versus feature. Single-player play stays on your device exactly as described in sections 2 and 5. A match has two people filling one board in turns, so that board must be shared between two devices. While a match is running, the following is sent to and stored on our servers. Anonymous identifier — an anonymous account created per device the first time you start a match, identified by a random string. The account holds no identifying profile: we do not ask for your name, email, or phone number. It is used only to tell the two seats apart. Match name — an adjective-and-noun pair our server picks at random for each match; you never type it. Match content — the puzzle and the board in progress, a record of each move (cell, digit, whether it was correct, timestamp), each player's mistake and correct counts, difficulty, start and end times, and the outcome. Invite code — a six-character code created when you open a room. Connection signal — the time your app last checked in, sent periodically while you play a match. It is used only so the server can tell whether a player has left. A match cannot work if the device knows the solution, so the server decides whether each move is correct. That is why the match content cannot stay on the device alone. Processing. The above is stored in Google Firebase and Google Cloud, in the Seoul region (asia-northeast3). Google's privacy policy applies in addition to this one. Retention. Invite codes are deleted after 10 minutes, matchmaking entries as soon as you are paired or cancel, finished match records 7 days after they end, and connection signals 7 days after they were last recorded. The anonymous identifier disappears when you clear the app's data or your browser storage, which also severs the link to those matches. If you do not use the versus feature, none of the above is sent.

Deleting the app or clearing the app's data and storage in your device settings removes the local data. On the web, clearing the browser's site data (storage) removes the local information. The web also lets you delete your data inside the app: Settings › Data can delete the game in progress, reset your stats, or delete all local data (game in progress, stats, and settings). That in-app deletion deliberately keeps your cookie setting and your analytics setting — erasing them would silently undo choices you made — so clearing the browser's site data remains the way to remove those as well. On the web, you can change your ad-cookie setting at any time in Settings, and you can turn usage-analytics collection off at any time with its own switch (turning it off stops any new data from being sent from this device immediately). You can also block cookies directly in your browser settings. You can separately block Kakao's ad cookies from the 'Ad Cookie Setting' control on Kakao's personalized advertising notice page (https://info.ds.kakao.com/optout.do). On the web, third-party ads are shown regardless of that setting; turning it off signals Google not to use your data for advertising, while Coupang Partners and Kakao AdFit cannot receive that signal — use their own opt-out paths (Kakao's is linked above). Clearing your browser's site data also erases the setting. There is no ad-removal purchase on the web. On iOS (starting with version 2.0.0), you can change ad personalization at any time in your device's Tracking settings (App Tracking Transparency, ATT), and in regions where consent is required, you can reopen the UMP consent form from the Privacy Options in Settings to change your ad-personalization consent. This App Tracking Transparency (ATT) setting applies to Kakao AdFit as well — if you do not allow it, Kakao does not use your advertising identifier (IDFA) either. The same ATT setting applies to Unity Ads (starting with version 2.2.0) as well. In regions where consent is required (such as the EEA, the UK, and Switzerland), any UMP consent change you make in the Privacy Options is passed on to Unity Ads too, while in regions where US state privacy laws apply the no-consent signal remains in place regardless of your choice (see section 4). You can also opt out of Unity's personalized ads directly from the Data Privacy icon inside a Unity ad. The same ATT setting applies to Meta Audience Network (starting with version 2.2.0) as well, and any UMP choice you change in regions where consent is required is passed on to Meta through Google's Additional Consent mechanism. The Limited Data Use (LDU) signal is always set before the ad SDKs start, regardless of your choice (see section 4). However, iOS has no separate setting to turn off usage analytics (Analytics) or crash diagnostics (Crashlytics) collection — the only way to stop it is to delete the app. You can use the ad-removal in-app purchase in Settings to remove banner, interstitial, app-open, and native ads; rewarded ads are shown only when offered by the app and you choose to watch them (this purchase is not available on the web). You can control Game Center participation in your device's Game Center settings — signing out stops score submissions. On Android (starting with version 2.0.0), you can delete or reset your advertising identifier in your device settings, and where consent is required, you can change your ad-personalization consent through the in-app consent management (UMP). This same advertising-identifier deletion and reset also applies to Kakao AdFit (Kakao's guidance: Home > Settings > Google > Ads > Delete advertising ID). It applies to Unity Ads (starting with version 2.2.0) as well. In regions where consent is required (such as the EEA, the UK, and Switzerland), any consent change you make in the in-app consent management (UMP) is passed on to Unity Ads too, while in regions where US state privacy laws apply the no-consent signal remains in place regardless of your choice (see section 4). You can also opt out of Unity's personalized ads directly from the Data Privacy icon inside a Unity ad. Deleting or resetting this advertising identifier applies to Meta Audience Network (starting with version 2.2.0) as well, and any UMP choice you change in regions where consent is required is passed on to Meta through Google's Additional Consent mechanism. The Limited Data Use (LDU) signal is always set before the ad SDKs start, regardless of your choice (see section 4). For more on opting out of Kakao's personalized-ad collection and use, see Kakao's personalized advertising notice (https://info.ds.kakao.com/optout.do). However, Android has no separate setting to turn off usage analytics (Analytics) or crash diagnostics (Crashlytics) collection — the only way to stop it is to delete the app. On Android, you can also use the ad-removal in-app purchase in Settings to remove banner, interstitial, app-open, and native ads; rewarded ads are shown only when offered by the app and you choose to watch them (this purchase is not available on the web). Taking part in Play Games is your choice — the app works without signing in — and you can delete the games data Google has collected, including leaderboard scores, from your Play Games profile or your Google Account. Contact: contact@object.so — to request deletion of any data we hold, please write to this address. Match records are deleted automatically 7 days after they end. Clearing the app's data or your browser storage removes the anonymous identifier, which also severs the link to those records.

Business name: Object · Representative: Jaemyeong Jin · Business registration number: 113-59-00420 · Mail order sales registration: 2019-Busanbukgu-0492 · Address: 86 Sangni-ro, Buk-gu, Busan, Republic of Korea · Phone: +82 10-3614-3752 · Fax: +82 504-334-3752 · Email: contact@object.so · Hosting provider: Amazon Web Services (AWS)