ONE MORE · 差一格
Effective and last updated: November 3, 2026. Developer and operator: fanshxin (individual). Service domain: onemoreblocks.com. Privacy contact: fanenjoymi@gmail.com.
1. Scope
This policy describes how we handle information when providing the ONE MORE / 差一格 Android game, browser-based friend challenges, and related puzzle services. It describes the current Android 0.7.2 test version. The iOS version has not launched. Before introducing iOS, production advertising, accounts, or cloud saves, we will update this policy to reflect actual practices.
This policy explains our practices. Continued use does not replace separate consent where applicable law requires it.
2. Information stored on your device
The game generally does not require account registration. Scores and progress, boards and move history, daily and practice progress, badges and items, restart and help counters, saved and authored puzzle records, drafts, review archives, appearance, sound, and haptic settings are primarily stored on your device or in your browser.
Local storage also holds random service credentials, author management permissions, queued challenge submissions, ad reward fulfillment records, and a limited history of local playtest and timing events. Local records can include game and puzzle IDs, times, moves, scores, and help outcomes. Some operational records are sent as described below. System language selects the interface language. The current version does not provide account-based cross-device cloud saves.
3. Information sent for online features
- Publishing or adapting a puzzle sends its title, initial board, three pieces, goal, completion rule, source puzzle ID, and publication request ID. These support solvability checks, original-puzzle storage, duplicate prevention, and adaptation provenance.
- Playing an online puzzle may send a random service credential, challenge and puzzle IDs, the first move, move/undo/hint/revive traces, and completion or learning markers. These validate results, provide hints and reviews, prevent duplicate counts, and produce author feedback. Not all local practice records are uploaded.
- Identity and permissions use a server-side digest of a random service credential to distinguish authors and challengers. We do not use names, phone numbers, or your contacts to identify players. Random identifiers do not necessarily make these records legally anonymous.
- A personal invitation message is normally stored locally and sent through a system sharing option you choose. The current puzzle publication endpoint does not store that message in the puzzle itself. Recipients and your chosen sharing service process the content you send.
Anyone holding a public puzzle link may read the puzzle. Author feedback shows challenge, completion, and unassisted completion counts, rather than friends' names or contact details. Do not include sensitive information about yourself or others in titles, boards, or invitations.
4. Optional experience statistics
Experience statistics in Sound & settings are off by default. If enabled, we send limited events associated with a random installation identifier: app version, puzzle and game IDs, mode, content date or period, move counts, active time, completion/block/help status, and ad request, display, wait, and reward outcomes. They help us assess puzzle quality, reliability, and assistance.
These optional statistics do not include complete boards or complete solutions, friends' names, contacts, or author management credentials. The installation identifier is hashed for association and deduplication and should still be treated as pseudonymous. Switching statistics off stops future optional uploads and clears queued events. It does not automatically delete events already received, prevent operational challenge submissions, or control the advertising SDK's own processing.
Detailed events are retained for 30 days; daily summaries and activity records for approximately 90 days. Deduplication receipts last 90 days from receipt. Installation-linked first-activity and first-attempt indices are removed after 90 days of inactivity. Cleanup occurs during service processing rather than at the exact instant each record expires.
5. Advertising and Google services
The current Android test version integrates the Google Mobile Ads SDK (AdMob) and uses Google's test rewarded ads. Rewarded ads are displayed after you choose an advertising help option. However, the SDK may initialize and request ads in advance when you enter an eligible game screen. Not pressing Watch ad does not mean the SDK has never made a network connection.
Google's disclosure for the current SDK describes automatic collection and sharing of IP addresses (which can estimate general location), app and ad interactions, performance and diagnostic information, and Android advertising IDs, app set IDs, and applicable device/account-related identifiers for advertising, analytics, and fraud prevention. Google states that SDK data is transmitted using TLS. Test ads do not mean no data is processed. Our optional experience-statistics switch does not control Google's SDK.
You can use Android system settings to manage, reset, or delete the advertising ID, depending on the OS version. This does not guarantee that all ad requests or other necessary SDK processing stop. The current version does not implement a complete regional advertising-consent interface. Before production advertising and wider regional release, we must implement applicable consent configuration and update these disclosures.
See the Google Privacy Policy, Google's information about partner sites and apps, and Google Mobile Ads SDK data disclosure. New ad partners or an iOS advertising SDK will be disclosed when introduced.
6. Network access, device functions, and contact
Network requests expose an IP address, request time, and necessary protocol, device, or browser information to receiving servers. Puzzle-service and website hosts and their network infrastructure may process this information for delivery, security, and troubleshooting. The current application database does not use IP addresses to identify players. Our configured policy-website access log records only IP, time, request method, path, response status, and response byte count, without deliberately logging query parameters, request bodies, or identity credentials. Separate error logs support troubleshooting. Website logs rotate daily and retain the active file plus seven historical files, typically about eight days; cleanup depends on scheduled rotation. Infrastructure logs held by the cloud provider are subject to that provider's actual practices.
The game's own features do not request access to contacts, messages, call records, the camera, microphone, or precise location. Sharing uses recipients you select in the system share sheet and does not give the game your friends list. Sound and haptic settings provide local feedback. Playtest-record and collection-card exports are generated when you request them; you decide whether and where to save or share them.
If you email us, we process your email address, message, and attachments to respond to support, complaints, or privacy requests. Do not email service-management tokens, passwords, or unrelated identity documents.
7. Purposes and applicable legal bases
We process this information to provide and maintain the game, save and share puzzles, validate challenges and rewards, provide support, prevent abuse, and improve the experience. Where applicable law permits, legal bases may include performance of a contract necessary for requested services, legitimate interests in service security and reliability, legal obligations, and your valid consent for optional statistics or other consent-based activities. You may withdraw consent without affecting prior lawful processing.
8. Sharing and processing locations
We provide relevant information to necessary hosting, network, and technical service providers. Google processing is described in the advertising section. Content you publish or share is made available to link holders and your selected sharing services. We may also disclose information as required by law or as necessary to protect legal rights or address security incidents. Management credentials are not included in public sharing links.
This policy website is hosted in Tencent Cloud's Singapore region and served through play.onemoreblocks.com. The game puzzle service remains a local development/test service operated on the developer's equipment; its production cloud service has not been activated. Google and network infrastructure providers may process relevant data in multiple countries. We will update this policy for material hosting or integration changes and apply safeguards required by applicable law. We do not promise that processing takes place only in your country.
9. Retention and security
Local game data generally remains until you clear it, uninstall, or your system removes it. Server-held puzzles, identity digests, challenge records, and learning markers are retained to maintain original sharing links, verify results, and provide author feedback. They currently have no automatic expiry equivalent to the statistics limits above. You may request deletion. Limited records may need to be retained for legal obligations, disputes, or security, subject to applicable restrictions.
We use access controls, credential hashing, and storage protections appropriate to the service. Current local-network testing permits HTTP; production public services must be configured with HTTPS. Local test connections must not be described as end-to-end encrypted. Where backups are enabled, access is restricted and copies are overwritten according to the actual rotation schedule. No network or storage system can guarantee absolute security.
10. Your choices and deletion requests
- Device data: use Sound & settings to disable experience statistics, export playtest records, or clear local data; system and browser controls can also clear app data. Clearing can be irreversible and can remove author management permissions.
- Works and saved puzzles: removing a favorite or deleting a card from My Puzzles only removes local records. It does not automatically withdraw a server-published puzzle, invalidate a shared link, or delete server records.
- Server information: email fanenjoymi@gmail.com explaining the information you want to access, correct, delete, or restrict. Include relevant puzzle links and a necessary description. We may reasonably verify your relationship to records; do not send service tokens in the initial email. If original device identifiers have been cleared, we may be unable to associate all corresponding records with you.
- Advertising and sharing: use system ad controls and decide whether to trigger rewarded help or share through external services. Those services describe their processing in their own policies.
Depending on applicable law, you may also request a copy or portability, object to certain processing, withdraw consent, or complain to a competent supervisory authority. We handle reasonable requests within applicable deadlines. Legally required records and public-content copies independently saved by others may not be removed with our copies. The current version has no user-facing server-data self-service deletion button.
11. Children and younger users
This version has no age-verification or parental-authorization flow and does not actively ask you to provide a date of birth or identity documents. Younger users should use the service with guardian guidance and obtain valid authorization where required by the law in their location. If you believe a younger user's information has been handled improperly, contact us so we can investigate and take appropriate deletion or restriction measures.
12. This website and policy updates
The policy pages themselves load no game code, ad SDK, analytics scripts, or third-party fonts. Basic network processing by the website host still occurs. Both Chinese and English pages can be read directly without a game account.
When features, providers, processing locations, or purposes materially change, we will update the date and policy and provide appropriate notice, such as an in-app notice, where needed. Changes requiring separate consent take effect after that consent is obtained. Questions can be sent to our privacy email.