Dust and Deal Privacy Policy

Effective date: 24 October 2026

Small Rest Studio (작은쉼 스튜디오, the “Developer”) explains below what information is processed in Dust and Deal and the choices available to you.

1. Game Records and On-Device Storage

The app stores information needed to play the game in its dedicated storage area on your device. This includes game progress, battle and journey state, decks, cards, relics, consumable items, in-game currency and health, character progression and unlocks, recent journey history, and settings.

You do not need a separate game account for your game records. The Developer does not automatically upload game saves to its servers or link them to an account. You do not need to provide your name, date of birth or phone number to play.

The password encryption described below applies to new standard portable backup files you export from builds that support this feature. Standard backups already exported, or still being exported, from older builds that do not support the feature may be unencrypted. This does not mean that the app's on-device storage itself is encrypted with that password.

2. Optional Rewarded Ads and Google Services

Builds that include advertising features may use the Google Mobile Ads SDK (AdMob) and Google User Messaging Platform (UMP) for rewarded ads that you choose to watch. You can continue with basic gameplay without choosing to watch ads.

UMP may refresh consent information when the app starts to check consent status in regions where this is needed. As a result, the app may communicate with Google services over the network even if you do not tap the rewarded ad button. Before requesting ads, the app checks the applicable consent process and whether UMP permits ad requests. Where UMP requires it, you can reopen the ad privacy choices screen from Settings.

According to Google's public Mobile Ads SDK documentation, information that may be processed for ad delivery, service analytics, diagnostics and fraud prevention includes IP addresses (which may be used to estimate approximate location), app and ad interactions, diagnostic information, and device or other identifiers. The information actually processed may vary with the SDK version, device, region, consent status and Google service settings.

From version 0.5.3, the app includes the Android advertising ID (AD_ID) permission. Depending on device settings and consent status, Google’s advertising SDK may use this ID to deliver ads, limit frequency, measure performance and prevent fraud. The Developer does not store it in game saves. Non-personalized ads do not eliminate all identifier processing. You can delete or reset your advertising ID in Android’s Google ad settings, where available. Earlier versions may have this permission removed.

Google Privacy Policy: https://policies.google.com/privacy?hl=ko

Google advertising privacy information: https://policies.google.com/technologies/ads?hl=ko

Google Mobile Ads SDK data disclosure: https://developers.google.com/admob/android/privacy/play-data-disclosure?hl=ko

2.1 Automatic Error Reporting (from version 0.5.3)

Production builds use Google Firebase Crashlytics automatically to investigate crashes and improve stability, independently of whether you watch ads. Reports can include crash/error stacks, app and OS versions, device information, installation identifiers, and session-start timing used for stability metrics. There is currently no in-app switch to disable this reporting.

We do not attach game saves or backup passwords. Custom JavaScript reports contain bundled file locations and error categories, not original error messages or user-entered text. This release does not include the Google Analytics SDK.

Reports are processed by Google as a service provider and encrypted in transit. Google states that Crashlytics retains crash traces and associated identifiers for 90 days before starting removal from live and backup systems. Contact the privacy email below for enquiries or deletion requests; because we do not link reports to a named game account, identifying a particular report may be limited.

Firebase privacy information: https://firebase.google.com/support/privacy

3. Google Play Update Checks

Apps distributed through Google Play may use Google Play's native in-app update feature to check whether an update is available. These checks use Google Play services, not a separate update server operated by the Developer.

The app is designed to show an update prompt only after Google Play has reliably confirmed that an update is available. It does not treat being offline, a failed check or an unknown status as evidence that an update is available and force the app to close on that basis. Information processed as part of the Google Play update process is governed by Google's policies for the relevant services.

4. Backup and Restore

4.1 New Standard Backups

In builds that support password-encrypted backups, selecting the standard “Export Save Backup” option lets you create a portable backup file that encrypts your game save with a password. Standard exports from older builds that do not support this feature may be in plaintext. The encrypted format is designed to derive a key from the password using PBKDF2-SHA-256 and to use AES-GCM authenticated encryption. Encrypted backups help protect the confidentiality of the file's contents and verify whether they have been altered.

The password is not saved separately by the app or in device storage, and the Developer cannot recover it. If you forget the password, you will not be able to open that encrypted backup.

Leading and trailing spaces are not automatically removed from passwords. Spaces are part of the password, so you must enter them in the same way when restoring a backup. NFC normalization is applied to handle visually identical Unicode input, such as Korean combining characters, consistently.

With a compatible Dust and Deal app and the same password, you can restore an encrypted backup on another device. If you select cloud storage in the Android file picker, the relevant document provider's or cloud service's policies also apply to the file's storage and synchronization. This is not a feature that automatically uploads backups to the Developer's servers.

4.2 Older Standard Backups and Recovery Originals

You can still import older, unencrypted standard backups for compatibility. The new feature does not retroactively encrypt existing plaintext backup files. Delete older files you no longer need from the locations where you saved them, or store them securely.

Saves that the current app cannot read safely, such as those created by a newer app, are preserved through a lock and recovery process rather than overwritten. The “Export Recovery Original” option provided in these cases is a separate feature intended to preserve unreadable original data as closely as possible to its original form. It is different from a standard encrypted backup. A recovery original may contain unencrypted data and may not be a file that can be restored directly using the standard “Import Backup” option. Avoid sharing it publicly and manage access to it yourself.

5. Retention and Deletion

Game records are kept in the app's dedicated storage area on your device while you use the app. Clearing the app's data in Android Settings or uninstalling the app may delete its internal records.

Encrypted backups, older plaintext backups and recovery original files that you have exported separately may not be deleted automatically when you uninstall the app. You must delete those files yourself from the storage locations you selected.

The Developer cannot remotely access or delete game records on your device or backup files in storage you have chosen. Retention and deletion of information processed by Google for advertising, consent and Play services, and your rights concerning that information, are governed by Google's policies and the tools it provides.

6. Information You Send with Enquiries

When you contact the Developer by email, your email address, any name shown in the email or provided by you, the contents of your enquiry and any attachments may be used to respond to it. You do not need to send personal information that is unnecessary for your enquiry.

Enquiries are received through Gmail. Related materials are deleted once the enquiry has been resolved and there is no longer a reason to retain them. Where the law requires retention, the applicable retention period is followed. You can send requests to access, correct or delete your enquiry information to the contact listed below.

7. Security and Limitations

Authenticated encryption for new standard portable backups is intended to make the file's contents difficult to read without the correct password and to detect altered ciphertext. However, no security feature can eliminate every risk or guarantee absolute protection against cheating or tampering.

The app does not claim to fully prevent risks in situations where the device itself is controlled through rooting or debugging, you replace data with another valid backup file, your password is exposed, or an external storage account you have chosen is compromised. Older plaintext backups and recovery originals do not have the same level of protection as new standard encrypted backups and must be managed securely and separately.

8. Policy Changes and Contact Details

If the information processed, SDKs used or services change, this policy will be updated and an effective date shown. Where new collection or a change in purpose requires separate consent, the necessary information and consent process will be provided before the change takes effect.

Service: Dust and Deal

Developer: 작은쉼 스튜디오(Small Rest Studio)

Privacy contact: 김종현

Email: srs260303@gmail.com