Quiet Tiles: privacy

Quiet Tiles privacy
Updated 7 November 2026

Moola operates Quiet Tiles. Contact Moola through https://project-moola-401d0.web.app/support. This policy covers the app and its optional account services.

Play is processed on your device. Saved play data consists of table seeds and layouts, legal tile-pair moves, unfinished and cleared tables, daily dates, tutorial progress and recovery choices. Preferences and a small device preview-use record are kept locally. The preview-use record prevents restarting the free preview and remains after account deletion; we remove its reference to the deleted account. We do not ask for your photos, contacts, microphone, precise location or advertising identifier. There is no advertising, chat, public profile, third-party analytics SDK or crash-reporting SDK.

If you create an account, Firebase Authentication processes your account identifier and the sign-in method you choose: Apple, Google or phone verification. Apple or Google may provide a name and real or relay email; phone verification processes the number and security information needed to confirm it. We use identity for account access, recovery, purchase ownership and deletion. We do not use it for advertising. Signing in with another method does not automatically transfer a different account's purchase.

Your account can back up saved play records to Google Firestore in the Moola project, named database moola. App records are isolated by app and account. The app keeps an offline device copy and retries interrupted saves. Conflicting play is preserved for recovery rather than silently replacing a table. Other devices must connect to receive changes or deletion. Do not treat a device-only preview as a cloud backup.

Apple or Google processes payment. We receive verified transaction references, product, platform, purchase environment and entitlement information to confirm, restore and reconcile the permanent unlock. We do not receive payment-card details. Store analytics and server-verified purchase records can provide aggregate product and purchase totals; we do not collect a behavioural advertising profile or send play events to an advertising service.

Firebase App Check, Firebase Authentication, Google Cloud and the stores process technical information needed for delivery and security, including app or installation identifiers, attestation results, IP addresses, request times and error information. These services may process data internationally under their published terms. Firestore application records are hosted in europe-west4; identity, store and infrastructure services can use other locations. Our app does not intentionally log sign-in codes, tokens or saved game contents.

Sharing is optional and opens the system share sheet. A game card or link contains only the generated table or print information shown in its preview and a destination link. It does not include your account identity or private history. Temporary share images are removed after sharing where the platform permits and on later cache cleanup. The recipient and chosen destination control their copies. Opening a shared web page also sends ordinary technical request information to Firebase Hosting. No contacts are uploaded and nothing is posted automatically.

Live account records remain until deletion or another applicable retention decision communicated to you. The app-specific deletion worker removes live play records, sync operations and account mappings. Save-operation deduplication records expire after 7 days. Completed deletion and membership markers expire after 30 days. Detached store references needed for payment reconciliation or disputes expire after 90 days. Expiry cleanup is asynchronous. Operational logs use the configured 30-day retention; support correspondence is retained for 12 months after closure unless an unresolved dispute or obligation requires longer.

Deletion completion confirms removal of live application records, not instant erasure of provider backups. Firebase describes removal of authentication data from live and backup systems within up to 180 days after its customer initiates deletion. Other infrastructure backups follow configured or provider periods. Restores must respect deletion markers. Exports, recipient copies and offline devices cannot be remotely erased immediately. A shared Firebase identity can remain when it still belongs to another Moola app; deleting Quiet Tiles does not delete another app's data.

Settings includes export, purchase recovery and account deletion without another purchase. To delete without the app, contact Moola support at https://project-moola-401d0.web.app/support using the email or phone linked to the account. We confirm ownership without asking for a password or sign-in code. Support aims to resolve verified requests within 30 days. You can use the same route for access, correction, removal or a privacy question; applicable statutory rights remain available.

Quiet Tiles is designed for adults and is not directed to children under 13. If you believe a child supplied personal information, contact support for removal.

Provider information: https://firebase.google.com/support/privacy, https://www.apple.com/legal/privacy/ and https://policies.google.com/privacy. Material changes to collection or purpose will be reflected here before release.