Updated and effective: October 17, 2026
Privacy Policy
This policy covers the Games We Played iPhone and iPad app and its support and game-request services. Core gameplay runs on your device. Optional support features and Apple purchases involve network services and the data described below.
1. Provider and contact
The developer identified as the app provider on the App Store product page provides this app (“we”). Contact us about privacy or support at ckf@live.com. This policy covers Games We Played, not the data practices of other apps.
2. Game data on your device
Game rules, local AI and board interactions are processed on your device. Games and unfinished saves, favorites, recent activity, statistics, daily game-trial usage and appearance, board, sound, haptic and game preferences are stored locally. They are not automatically uploaded to our servers.
There is no developer account or login, advertising, third-party analytics SDK, behavioral telemetry, online matchmaking, leaderboard or developer-operated cloud-save sync. Installed games work offline, subject to the free-access limits and purchase entitlements shown in the app.
If you enable iCloud or computer backups, Apple’s system backup may include and restore app data. Your device and Apple manage that backup; it is not our cloud-sync service and does not give us access to your backups.
3. Opening feedback or a game request
Support and game requests are optional online features. Opening them from the app sends the app name and identifier, entry point and platform, version and build, device type, iOS/iPadOS version and app language to Feedback Center to identify the product and environment.
When available, Apple’s identifierForVendor (IDFV) is included as a device lookup identifier. It is not the advertising identifier IDFA and is not used for advertising tracking. The support page stores an app-specific lookup identifier in browser local storage. Direct browser visits without an app-provided identifier use a randomly generated browser identifier. Support records can therefore be linked to an identifier even though the app has no account system.
These context parameters are sent in the URL when you open a support page. Requests and infrastructure logs may include the URL, time, IP address and User-Agent. Links used to read legal and help pages pass only the language, without the app’s device lookup identifier.
Submitting creates a ticket containing your title, text, category, status, messages and technical context. A game request also stores your game description and rules so we can assess development, clarify rules and communicate with you. We do not automatically read or upload local saves, game statistics or full device logs.
4. Attachments and contact information
Attachments are optional. Without selecting an attachment, the support page does not access your photos or files. Selecting an image or video immediately uploads that file for a preview, before ticket submission. Closing the page or clearing the form does not retract an uploaded file. We do not strip metadata such as embedded photo locations; review files and remove unnecessary personal information first.
Attachments are stored at links containing a random component. There is no public attachment directory, but anyone holding a file’s link may access it. Do not upload identity documents, passwords, full payment evidence, other people’s personal information or material you do not wish to provide through support. Avoid sharing attachment links.
You do not need to provide a phone number or email address to create a ticket. If you include contact details in your message or email us, we process the address, message and attachments you provide only to address the related support or privacy request.
5. Apple purchases and transactions
Monthly and yearly subscriptions, a one-time lifetime unlock and repeatable tips use Apple In-App Purchase and StoreKit. The app verifies Apple-provided transactions and current entitlements on the device to unlock features, receive transaction updates and restore purchases. The current app does not automatically send purchase history or receipts to our Feedback Center.
Apple may connect to its services to load products, update transactions or restore entitlements, including outside an active checkout. Apple handles Apple Account, payment and purchase information under its own policies. We do not receive your card number, payment password or Apple Account password. See Apple’s Privacy Policy.
6. Permissions and tracking
The native app currently requests no photo-library, camera, microphone, location, contacts, health, motion-sensor or notification permissions and has no advertising-tracking authorization request. The browser’s file picker is for attachments you choose, not background scanning of your library. We do not use IDFA, data brokers or cross-company advertising profiles.
8. Retention and deletion
Local data remains until you clear the relevant records or delete the app. System backups may retain separate copies and can restore records; manage those copies through your backup settings.
Tickets, conversations, attachments and associated context are retained while needed for support, follow-up and necessary security purposes. The current service does not automatically expire data based on ticket closure or upload time. Closing a ticket, clearing browser data or uninstalling the app does not delete server records. You may request deletion at any time, including files uploaded without submitting a ticket.
After verifying control of the information, we handle access, correction and deletion requests under applicable law. Information that must be retained for legal obligations, disputes or necessary security is retained only for those purposes.
9. Your choices and rights
You can continue offline without opening support, omit attachments, edit text before submission and supplement or correct a ticket. Contact ckf@live.com or use the privacy-request form to request access, correction, deletion, restriction of processing or withdrawal of optional processing.
Include a ticket number where available. Otherwise, an approximate date, title or attachment filename/link can help locate the information. We may verify control of a ticket or email address; we do not routinely request Apple passwords or full identity documents. See Privacy Choices for practical steps.
10. Security
The operating system’s app sandbox isolates local app storage. Public support pages use HTTPS and administration requires authorization. Protect your device, ticket lookup identifiers and attachment links. No storage or transmission method is absolutely secure. Contact the support email if you upload information by mistake or suspect an incident.
11. Children and younger users
This app offers childhood games and is not intended to collect children’s personal information. A parent or guardian should assist younger users with purchases, online feedback and attachments and avoid providing unnecessary identity, location or school details. Guardians can email us about information submitted by a child. The App Store age rating and applicable local law govern age suitability.
12. Policy updates
We publish revisions and their effective date here. We will communicate material changes to purposes or recipients appropriately and seek consent where required. Simplified Chinese and English describe the same practices. Contact ckf@live.com if you have a question about either version.