Game information stored on your device
Your current game and move history, completed games, settings such as difficulty and theme, attendance, puzzle progress and cumulative score are stored on your device. This storage feature does not synchronise full game records to a server. Results and feature-use analytics are sent separately as described below.
Clearing app data or removing the app can cause you to lose local information. Backups and restoration depend on your operating system or host settings. Removing the app does not by itself delete server identifiers or analytics already sent.
Service identifiers and analytics
The app has no registration screen asking for your name, email or password. The service server issues an identifier for app use and uses Firebase authentication. The device stores the identifier and authentication refresh information. The information processed is therefore not limited to anonymous statistics.
We analyse feature use, including game starts, finishes and abandonment, puzzles, hints, attendance and ads. Events can include a game record identifier, difficulty, language, game mode, result and settings relevant to that action. Native apps also send a defined set of key events to our service server; the AppsInToss version uses the server event relay.
Android and iOS use Firebase Analytics and Crashlytics to understand usage, errors and crashes. These SDKs may process installation identifiers, device and operating system details, usage events and crash diagnostics. Android uses Firebase Remote Config to receive feature settings; the iOS version does not link that SDK.
Optional collection in iOS 3.0.28 and later
In iOS 3.0.28 and later, “Send usage and diagnostics” in Game settings is off by default. Firebase Analytics, Crashlytics and optional service-server analytics do not start until you turn it on. This setting does not apply to Android or AppsInToss. Earlier iOS versions use the existing collection paths described above.
Turning the setting off stops new usage and diagnostic collection and requests that pending uploads be cleared. It does not reverse requests that have already started or automatically delete data stored on servers. The retention and deletion procedures below apply to data already sent.
You can still save games and receive non-personalised ads when the setting is off. Existing service identifiers and authentication refresh information remain on the device so you can turn it on again. Opting in does not permit ad storage, ad user data or ad personalisation signals, and does not request ATT permission. iOS 3.0.28 and later do not call the UMP consent form. The Privacy policy button in Game settings opens this notice.
Advertising and your choices
The native apps show Google AdMob interstitial ads between games. The current public versions do not connect banner ads, rewarded ads or in-app purchases. To deliver and measure ads and prevent fraud, Google and advertising partners may process permitted device or advertising identifiers, IP addresses and approximate location inferred from them, ad impressions and clicks, and diagnostics.
Android checks consent using Google UMP and requests ads once ad requests are permitted. It does not force all requests to be non-personalised, so personalisation may depend on consent, region and provider settings. The iOS version requests non-personalised ads and is configured not to request ATT tracking permission. Non-personalised ads can still involve identifiers for frequency capping, measurement and fraud prevention.
When UMP requires a privacy choices form on Android, you can revisit it through the advertising privacy choice in app settings. You can also use your device advertising privacy settings. AppsInToss ads use the Toss host advertising features and notices, separately from the native AdMob settings.
Optional AppsInToss features and sharing
The AppsInToss version sends cumulative scores to Toss Game Center for rankings. Return reminders use the Toss host consent request feature. Toss notices also apply to information processed by the host and its consent settings.
When you choose to share, a game result message or image is passed to the operating system or Toss sharing feature, or copied to the clipboard. You choose the recipient and destination, whose privacy policy applies.
Purposes and providers
Game information and service identifiers support game progress, feature state and authentication of service requests. Analytics and crash information help us understand usage and stability and improve features. Advertising information supports ad delivery, measurement and fraud prevention.
Google Firebase, Google Analytics and AdMob are involved in analytics, authentication, error reporting and advertising. Toss is involved in AppsInToss ads, Game Center, reminders and sharing. Depending on provider server locations, information may be processed outside your country. Our app server and server-event storage use the Seoul, South Korea region. Firebase authentication is processed in the United States; other Google services may process information at Google facilities worldwide. Transfers occur through SDKs and server APIs during app use, under the relevant service data-processing terms and international-transfer safeguards.
Retention periods
Google Analytics user and event retention are each set to 14 months. New activity resets the retention period of the user identifier. Standard aggregated reports are not subject to that setting.
BigQuery app-analytics export tables expire 60 days after creation. Our server retains raw events and audit records in daily partitions for 400 days. General service logs are kept for 30 days; required security and administrative audit logs are kept for 400 days.
App-specific server identifiers and Firebase authentication records have no automatic expiry. We delete relevant records when processing a verified deletion request. Firebase states that authentication records are removed from live and backup systems within 180 days after deletion is requested.
Crashlytics starts removal after retaining crash data and associated identifiers for 90 days. Remote Config installation identifiers remain until deletion is requested; Google states removal from its copies takes up to 180 days after that request. Information independently processed by advertising providers and the Toss host follows their retention policies.
Access, correction and deletion requests
Contact cs@seorilabs.com. Tell us the app name and market you used, and we will explain the minimum information needed to identify the relevant installation or records. Do not send passwords or authentication tokens.
The app does not currently provide an automated deletion-request feature. An operator verifies the target and processes deletion of linked service identifiers, authentication records and analytics copies. For records we cannot identify, such as SDK data not linked to that installation, or records we must retain by law, we explain the available scope, reasons and retention period.
Deletion is applied to operational records and provider copies in stages. BigQuery separately retains time-travel and fail-safe recovery copies after deletion, so deleting operational records does not immediately erase all recovery copies. The provider removal periods above apply to Firebase authentication and Remote Config copies.
Children and policy changes
Lucid Chess is not designed primarily for children. If you have concerns about a child’s information, contact cs@seorilabs.com. The absence of a registration form does not mean no information is collected: SDKs and service identifiers are still involved.
When this policy changes, this page will show the effective date and changes.
