Qinglv Puzzle — Privacy Policy

Privacy Policy

1. Scope and contact

This policy covers Qinglv Puzzle on Android, iOS and macOS. The provider is the developer listed in the app store. Contact flowergame@yeah.net for privacy enquiries, access, corrections, complaints and deletion requests. Availability depends on platform and version. Google sign-in and cloud saves are currently implemented for Android.

2. Your initial choice

We present our Terms and Privacy Policy during normal initial use, after material updates and after withdrawal. Only choosing “Accept and play” permits gameplay; declining stops play. Reading, navigating back or closing a document is not acceptance. Analytics has a separate, initially unchecked choice. The policy version, acceptance time and analytics choice stay locally, are excluded from game cloud saves and are not restored as old consent from backups.

3. Guests and local records

Guests can play offline without registering. Local records include progress, complete boards, moves, duration, collections, achievements, daily records, virtual scores and device preferences. The season ranking is a local simulation, not online competition. Android may migrate older local saves without changing the original database. System backup may retain game records; consent and login sessions are excluded. Uninstalling or clearing data may remove records that have not synchronized.

4. Optional Google sign-in

When you choose Google sign-in, Android Credential Manager and Google Firebase Authentication verify your identity and create a game account. Google/Firebase process the supplied display name, email, profile-photo URL if provided, account UID, credentials, session state, IP and device information necessary to operate authentication. We never request or record your Google password. Native SDKs handle tokens; they do not enter Unity saves or analytics events. The game does not automatically download profile pictures.

The session is stored in the app's private device storage to restore the same account. Account services initialize separately from optional analytics. Signing in does not opt you into analytics. Signing out clears the session and returns to a separate guest save. Local account records remain for the same account unless you delete it or clear app data.

5. Account cloud saves

When available and signed in, Cloud Firestore stores gameplay under the verified UID: completed puzzles, in-progress boards, moves, timing, collections, achievements, daily records and virtual scores. This supports backup and continuing on a new device. Audio, haptic and language settings and legal consent are not uploaded. Accounts are isolated. You choose whether to import guest progress; the original guest save is retained separately.

Failed synchronization retains local records, and we do not claim a cloud save without server acknowledgement. Completed progress can merge; conflicting active boards require your choice. Offline changes need a connection and synchronization before they are backed up. Confirm synchronization before uninstalling. Cloud saves are not an anti-cheat or public-ranking service.

6. Optional usage analytics

Analytics is off by default; declining or disabling it does not affect sign-in, cloud saves or gameplay. Only Android integrates Firebase Analytics; macOS and iOS do not upload analytics. After a separate opt-in, events may include screens, buttons, theme/chapter/puzzle IDs, board size, start/restore/pause/restart/completion, moves and active duration, hints/flips/merges, collections/achievements/virtual scores and save failures. Random attempt IDs and event sequences link actions within a puzzle to improve gameplay.

The SDK may also process an app-instance identifier, first opens and sessions, app/device/system details, IP and approximate location derived from IP. We request no location permission and do not set account UIDs, names, emails or sign-in tokens in analytics. Full boards and images are not analytics events. Advertising IDs and ad-related consent remain disabled; no targeted ads are provided. Settings can stop further collection and reset local Analytics data; this does not erase previously uploaded reports.

7. Recipients, security and international processing

Google/Firebase receive necessary data as authentication, cloud-storage and optional analytics service providers. Connections are encrypted. Processing may occur outside your country. Cloud retention and authorized access depend on Firebase configuration, Google service rules and applicable law. Local retention is distinct. We do not sell personal data. Material changes will be disclosed with renewed consent where required.

8. Access, export, deletion and withdrawal

Account & cloud saves lets signed-in users copy gameplay records, sign out or request account and cloud-record deletion. Deletion requires connectivity, explicit confirmation and verification with the same Google identity. Success removes the game account, its cloud records and its save on this device. It does not delete your Google account or the separate guest save. Other devices may retain offline copies until cleared, but the deleted account cannot sync. Privacy support also accepts external requests; the store listing will provide a public request entry.

To stop short-lived tokens from recreating deleted records, the server retains a minimal deletion-blocking record, normally removed by a scheduled job after a two-hour safety window. Failed cleanup keeps a retry marker until complete, blocking further account cloud access. Backups and legally required retention follow service recovery cycles and applicable requirements. Historical Analytics reports require a separate deletion request; signing out does not delete them.

Privacy & your rights provides documents, support, analytics controls and withdrawal. Withdrawal signs out and stops play/cloud operations, retaining local gameplay. Accept again to resume. Device settings can clear app data; uploaded records require account deletion or support.

9. Minors

Minors should review these documents with a guardian. Do not enable optional analytics if under 14. Contact privacy support for children's data requests. Actual distribution, age selections and ratings are disclosed in the store.

Google Privacy Policy · Firebase privacy and security

10. Policy changes

This website policy was revised on 17 October 2026 from the in-app source dated 15 October 2026, including optional Android accounts and cloud saves when available. Material changes to purposes, data types or recipients must be explained before affected processing, with renewed permission where required. Reading this page, signing in or continuing play is not permission for new optional processing. The app must provide the corresponding notice and controls; account and cloud availability depends on actual service configuration.

11. Email enquiries and rights requests

When you email flowergame@yeah.net, we process the email address, message, attachments and communication information you provide to answer support enquiries, verify identity where necessary, and handle privacy requests or complaints. Mail providers process information necessary to deliver and store communications. Email is not added to game analytics or used for targeted advertising. Do not send passwords, recovery credentials, identity documents or unrelated sensitive information; if additional verification is necessary, we will explain why and limit it to what is needed.

We retain communications only as needed to handle the request. If a legal duty or specific dispute requires further retention, we keep only necessary records, restrict purposes and access, and delete or lawfully anonymize them when that reason ends. We respond within applicable legal time limits. If a request cannot lawfully be fulfilled in full, we explain the reason and available complaint channels. Missing installation information may affect locating historical analytics, but does not automatically remove statutory rights or justify collecting unnecessary personal information.

12. Third-party responsibilities, security incidents and statutory rights

Third-party privacy policies explain their services; they do not transfer our legal data-protection, SDK-configuration, processor-oversight or rights-request duties to those providers. You may still contact the actual game provider at the developer email in this policy. We process or disclose data only for purposes and within limits permitted by applicable law; requests from authorities are handled with legally required and necessary disclosures.

The absence of an absolute-security guarantee is not a blanket release from responsibility for a breach, alteration or loss. When an actual or possible security incident is identified, we take appropriate investigation, corrective and harm-reduction measures and notify affected users and authorities as applicable law requires. Liability limits in the Terms do not reduce statutory privacy rights or liability that cannot legally be excluded.

Permission and withdrawal for optional analytics, and processing requiring separate consent, follow the actual in-app notice and applicable law. Reading this page, accepting Terms or continuing to play does not replace the separate choices and other safeguards legally required for new optional processing, third-party disclosures or international transfers.

13. Reading this document online

This HTML file itself contains no analytics, ads, cookie scripts, external fonts, input forms or login. Online access still sends an IP address, request path and technical information supplied by the browser to the web server. Hosting services may retain access records to deliver and protect the site; this is separate from optional Firebase game analytics. Actual hosting-log practices and retention depend on deployment configuration. You can ask about them or exercise applicable rights using the email above. Services independently provided by linked external websites follow their own notices.