Privacy policy

1. Your progress, inventory, and cloud saves

The game stores scores, Daily results, streaks, unfinished rounds, coins, helpers, customizations, purchase references, settings, and reminder preferences on your device. It keeps separate saves for gaming profiles used on that device, along with identifiers and records needed to keep those profiles separate and avoid granting the same purchase or reward twice.

Apple Game Center provides gaming identity and achievements. iCloud stores supported saves under the device’s main iCloud account, separated by Game Center player. The iCloud Apple Account and Game Center account can be different; cross-device saves require the appropriate Game Center profile and the same iCloud account. Google Play Games Services and Saved Games provide gaming identity, achievements, and account-based saves on Android.

For connected players, supported cloud data includes:

• Best Endless score, best streak, and dated Daily results, including scores, placement counts, and whether all pieces were placed. Monthly totals are calculated from Daily history.
• Coins, saved helper extras, and ownership of coin-unlocked palettes, accents, finishes, and clear effects.
• Grant and spending records, purchase-related grant references, helper-conversion records, and account, installation, and deletion markers used to merge saves and prevent duplicate grants or restoration of deleted data.

Settings, selected styles, weekly allowances, and unfinished rounds stay on the device. Eligible permanent purchases restore separately through the store. Apple and Android cloud saves do not transfer between platforms.

Guest progress and inventory stay local in current builds. An explicit guest-progress import can bring eligible local progress or a legacy guest cloud save into the connected profile. Switching gaming accounts changes the active save; separate local copies for other profiles may remain.

Offline changes are saved locally and can sync when the service returns. Cloud delivery can be delayed. In particular, iCloud accepting a write into its local cache is not confirmation that another device has received it. The game uses profile identifiers, display names, and account-derived markers; hashed identifiers can still be linkable information.

Achievements are sent to the gaming service. The current game does not submit new scores to public leaderboards. Apple and Google process their gaming and cloud services under the Apple Privacy Policy, Game Center & Privacy, and Google Privacy Policy.

2. Age group and privacy treatment

The app asks you to choose Under 13, 13–17, 18 or older, or Prefer not to say. It stores that choice on this device, separately from your gaming profile and cloud saves. The app does not ask for a birth date. You can change the choice in Settings → Age group.

For everyone under 18 and anyone who prefers not to say, the app requests non-personalized ads, applies Google’s child-restricted ad treatment and a general-audience ad-content filter, and tells Google’s consent tool to use under-age treatment. It does not show Apple’s tracking-permission prompt for these groups. The app supplies the corresponding privacy-treatment flags to Google; it does not put the age-group choice in your game cloud save.

Adults use the normal consent pathway. On Apple devices, the app can explain and request tracking permission at the first game-over privacy step. Apple’s permission and Google’s consent choices are separate. Changing age treatment discards ads already held by the game so they cannot be shown under the previous treatment.

Age treatment does not change puzzle access, earned-coin features, purchases, or supported saves. Store approval, account restrictions, and parental controls still apply. Restricted or non-personalized ads are not a promise of zero provider data processing; see the advertising section below.

3. Purchases and purchase support

Apple’s App Store or Google Play processes payment. RevenueCat helps verify transactions, restore purchases, and determine product ownership. This involves receipts or purchase tokens, product and transaction details, purchase history, entitlement status, and a generated customer identifier. Device, operating-system, app-version, and service information may also be processed.

The game uses RevenueCat’s generated identifier rather than supplying your Game Center or Play Games identity as a RevenueCat login. It does not ask for or send your name, email address, or payment-card details to RevenueCat. A generated identifier can still be associated with purchase records; it is not a guarantee of anonymous processing.

Purchase records support verification, fraud prevention, app functionality, purchase support, and RevenueCat dashboard analytics. The SDK can contact RevenueCat without a completed purchase. We do not receive your full payment-card details. The app and its cloud wallet retain grant and transaction references to prevent duplicate rewards, including on restore.

Deleting progress does not delete store or RevenueCat purchase records. Contact us about purchase-support information processed on our behalf. Stores and providers may retain records for ownership, billing, security, or legal purposes. See the RevenueCat Privacy Policy and the Apple and Google privacy policies linked above.

4. Advertising and consent

Quilt Bee uses Google AdMob for between-round and optional rewarded ads, and Google’s User Messaging Platform for applicable consent and privacy choices. Depending on age treatment, permissions, and the request, advertising services can process:

• IP address and general location estimated from it.
• Device, app, account, or advertising identifiers, where permitted.
• App and ad interactions, such as launches, views, and taps.
• Diagnostic and performance information and records of privacy choices.

This supports advertising, measurement, analytics, and fraud prevention. Quilt Bee does not pass its cloud-save contents or gaming-profile identity to the ad integration. It does not request location permission or perform location lookups in current v1 builds; advertising providers can still estimate general location from connection information.

The game applies its age treatment and required privacy checks before requesting an ad. Ads may be personalized, non-personalized, limited, or unavailable depending on permissions and consent. Denying tracking or using a restricted or test ad does not stop every provider connection or data transfer. See how Google uses information from apps, the Google Privacy Policy, and Google’s Android and iOS ad-data disclosures.

No Ads or Premium removes between-round ads. Optional rewarded ads, privacy controls, and some provider processing remain available. Other purchases do not remove between-round ads. Available privacy messages describe advertising partners and your choices.

We do not sell your game-save data or support messages. Advertising activity may be considered sharing or targeted advertising under some laws. Use the available privacy controls described below.

5. Daily reminders

Daily reminders are local notifications scheduled using your chosen time and Daily completion information. A Ticer Apps server does not send them. You can change the time or turn reminders off in the game, and manage notification permission in device settings. The operating system controls delivery.

6. Earlier test builds and retained online records

Earlier internal builds included public rankings powered by Firebase Authentication, Cloud Functions, and Cloud Firestore, plus optional location lookup for country rankings. Those builds could submit a gaming identity, Firebase user identifier, display name, platform, scores, dates, monthly or weekly totals, days played, and a country code. Other players could view leaderboard entries. Raw location coordinates were not included in the game’s leaderboard records.

Those builds also used Firebase App Check with Apple App Attest or DeviceCheck, or Google Play Integrity, and service protections that processed integrity, connection, authentication, and request information. They could contact those services while running. Current v1 builds do not contain that Firebase integration, read or submit those rankings, or look up location.

Removing these features did not erase records already hosted online. Old test builds may still access the earlier service while it is available. Old Game Center or Play Games leaderboard entries may also remain with their platform provider. Current in-app Delete player data does not erase Firebase identities or old public scores.

Use our data-deletion request page to request removal of earlier Quilt Bee online records. Please identify the platform and nickname used; we may need further information to verify ownership. Platform achievements and native leaderboard records use Apple or Google’s own controls. See Firebase’s privacy information.

7. Support, diagnostics, and this website

If you email us, we receive your address, message, and attachments and use them to respond. Gmail processes messages as our email provider. Please do not send passwords, sign-in codes, or payment-card details.

Current v1 builds have no Firebase SDKs, Firebase Analytics, or Crashlytics and send no separate gameplay analytics stream to Ticer Apps. Development builds can log locally for debugging. This does not exclude store, purchase, advertising, and gaming-service providers’ own diagnostics or retained earlier-service records.

GitHub Pages hosts this website. We have added no website analytics, tracking pixels, ads, third-party fonts, or JavaScript. GitHub may process connection information, including IP addresses, under its Privacy Statement. External sites have their own practices.

8. Your choices and deletion

• Age group: change the device-local choice in Settings. The restricted treatment applies when the choice is under 18 or “Prefer not to say.”
• Ad privacy: open Settings → Privacy choices when available. Device settings also provide advertising-ID and Apple tracking controls. Declining applicable permissions does not prevent ordinary gameplay.
• Gaming profiles: use platform account controls to change or disconnect Game Center or Play Games. Disconnecting alone does not delete a saved profile, achievements, purchase records, or earlier online records.
• Reminders: turn them off or change their time in the game; manage permission in device settings.
• Restore purchases: use the store account that purchased eligible permanent products. Restore does not regrant consumable packs. Purchase ownership and gaming saves are separate.
• Delete player data: in current v1 builds, Settings → Delete player data resets the selected player’s local progress and wallet and records the reset in their supported platform cloud saves. Coins, saved helpers, and coin-unlocked customizations are included; gameplay and reminder settings reset; your age-group choice is retained. Other players’ saves, gaming accounts, achievements, and permanent purchase ownership remain. The app keeps cloud sync disconnected until you reconnect; follow any retry message if deletion is incomplete. Cloud delivery can be delayed. On iCloud, older per-device wallet copies may remain until replaced or removed; current builds ignore those older copies after receiving the deletion marker. This action does not delete earlier Firebase accounts or leaderboard entries, provider purchase or ad records, permissions, or independent backups.
• Guests: deletion clears local guest data and a legacy guest cloud save if available. It does not erase a signed-in player’s save. Sign into the relevant profile to delete its supported saved data.
• Remove app storage: deleting the app or clearing its data removes local storage according to your operating system. Offloading an iOS app retains data. Cloud and provider records can remain, and reconnecting may restore supported saves. Recovery copies of damaged saves or separate device backups may also remain.
• Access, correction, or deletion requests: visit the request page or email ticerapps@gmail.com. We address information we control or that providers process on our behalf and help identify controls for independently held provider data. We may ask for reasonable information to verify a request, never your password.

9. Retention, security, and your rights

Local and cloud progress, inventory records, account copies, and preferences remain until replaced or removed through the relevant controls. Purchase-grant and deletion markers help prevent duplicate rewards and deleted saves from returning. Platform cloud services, independent backups, and provider logs follow their own retention and deletion processes. Support and purchase-related records may be kept for support, ownership, fraud prevention, disputes, and applicable obligations.

Earlier Firebase identity and leaderboard records have no automatic expiry in the game’s service and remain until removed through a verified request or service administration. The earlier deletion system retains limited, linkable security markers: a keyed hash derived from the platform gaming identity, deletion version and state, and hashes of erased Firebase identifiers. These have no automatic expiry and do not contain gaming names or scores. An unfinished cleanup can retain the user identifier and request reference needed to complete it. Abuse-prevention counters have a two-day expiry setting with asynchronous cleanup. Provider-generated logs and backups are separate. Removing the current app integration did not remove these records.

We use platform storage protections and the safeguards of the services involved. This website uses HTTPS. No storage or transmission method is completely secure, and deletion is not a promise of immediate erasure from every provider or backup. Providers may process information outside your country under their policies and applicable safeguards.

Depending on where you live, you may have rights to access, correct, delete, or obtain information; restrict or object to processing; withdraw consent; opt out of applicable sharing or targeted advertising; or complain to a regulator or appeal a decision. We handle requests within our control as required by applicable law without penalizing you for exercising your rights.

Where a legal basis is required, processing may rely on providing requested features, consent where required, legitimate interests such as support and service security, or legal obligations. Withdrawing consent does not affect earlier lawful processing.

10. Parents, guardians, and updates

If you are a parent or guardian with a concern about a child’s information, contact us. We will investigate and address information within our control, including deletion where required. Device and store parental controls can restrict purchases and connected accounts.

We will update this policy and its date when practices change, with additional notice or consent where required. Earlier internal builds can behave differently, as described above.