Ages Untold
Privacy Policy
Effective 18 September 2026 · Updated 28 October 2026 · Applies to Ages Untold: Chronicles of Lives on iOS, iPadOS, macOS, Google Play, and the official Android build
In one sentence
Ages Untold has no account system and does not collect personal information. There is no sign-up or sign-in. We do not read your name, phone number, email address, location, contacts, or clipboard, and we do not include third-party analytics, advertising, or crash-reporting SDKs. On Google Play, portrait purchases are handled by Google Play Billing and the app reads only product and purchase status. The official Android build uses Alipay or WeChat Pay, which requires a device identifier and order information (see section 5).
1. What we do not collect
- There is no account system, so there is no account profile, phone number, or email address to collect or store.
- We do not use IDFA or advertising identifiers and do not track you across apps. Only the official Android build reads a device identifier, for Alipay or WeChat purchases (see section 5); the Google Play build does not.
- We do not include third-party analytics, advertising, or social-login SDKs.
- We do not read your photo library. Saving an image uses only the one-time permission to add the selected photo (see section 4).
2. Data that stays on this device
- Historical data: figures, periods, relationships, historical events, and quiz content are included in the app or downloaded as described below.
- Incremental updates: the app checks for and downloads updated historical data into its private application directory.
- Settings: data version numbers, skipped update versions, and similar preferences are stored locally.
- Temporary share images: files created while making a share poster live in the system temporary directory and are cleaned up by the system.
This content stays inside the app's own directories and cannot be read by other apps. Uninstalling the app deletes it. We do not keep these files on a server and cannot view them remotely.
3. Network requests the app makes
In normal use there is one purpose: checking for updates and syncing historical data. The official Android build also contacts our payment service when you buy a portrait pack with Alipay or WeChat. The Google Play build does not contact that service.
- Requests go to our content-delivery address, hosted by Volcengine Object Storage (TOS), under a domain such as
cdn-fhwca.lzqianzi.com.
- These are ordinary HTTPS file downloads with a no-cache header. They do not carry a device identifier, account information, or usage history.
- As with any web service, the CDN records the requesting IP address, time, and client type for delivery and troubleshooting. We have no account with which to associate those records and do not use them to identify individuals.
- Official Android build only: when buying a portrait pack, the app contacts
api.shanjushouji.com to create an order, query it, and restore purchases. Those requests include the device identifier and order information described in section 5. The Google Play, iOS, iPadOS, macOS, and HarmonyOS builds do not contact this service.
- The Google Play build updates through Google Play and does not download or install APKs. In-app APK updates exist only in the official Android build (see section 4).
4. Permissions
- Photos (write only): when you tap Save to device in the full-screen image viewer, the app adds the image to your photo library. On iOS the app requests add-only photo access and does not read existing photos.
- Network: used to check for updates and download historical data. Android also uses network-state permission to tell whether you are on Wi-Fi, so it can decide whether to download automatically or ask first.
- Install apps (official Android build only): in-app updates need to open the system installer. The Google Play build does not request this permission.
5. Purchases
On iOS, iPadOS, and macOS, portrait purchases are handled by the App Store. On Google Play, they are handled by Google Play. The official Android build uses Alipay or WeChat Pay. Card and payment-account details are handled by the relevant store or payment provider; we never receive them.
- Google Play build: purchases and restores use Google Play Billing. The app reads the product ID, purchase state, and restore result and stores the entitlement on the device. It does not read Android ID or upload purchase receipts to our own servers.
- Official Android build: payment is completed by Alipay or WeChat. If a channel notification contains a buyer-account field, we discard it before writing to our database. We retain only the order number, channel transaction number, amount, payment state, and payment time.
- Device identifier (official Android build): to bind purchased portrait packs to this device, the app reads Android ID. The raw identifier never leaves the device and is not written to logs. We upload and store a salted hash from which the original value cannot be recovered.
- Device model (official Android build): a value such as “Xiaomi 14 / Android 14”, used only for support and to help restore purchases.
- Order information (official Android build): merchant order number, amount, payment channel, channel transaction number, and payment state, used to grant entitlements, provide support, and reconcile refunds. We retain it until you ask us to delete it or until the retention period required for tax and after-sales records ends.
- Third-party SDKs: the Alipay SDK and WeChat OpenSDK are included only in the official Android APK. The Google Play build does not enable these payment components.
6. Images you share
Images you choose to share or save are handled by the system share sheet and photo library; they do not pass through any server of ours. To prevent misreading after an image leaves the app, images carry a product signature and necessary labels: AI illustrations are marked “AI illustration · not a historical portrait”, and historical portraits include their Wikimedia Commons source.
7. Content sources and licensing
Figure and relationship data come from Wikidata open data (CC0, available for commercial use and modification). Historical portraits come from Wikimedia Commons, and each image's licence is governed by its original file page as recorded in images_index.json. Historical events are written by hand. Character illustrations are AI-generated impressions. These are content sources; they do not involve providing user data to third parties.
8. Children
The app is rated 4+ and contains no advertising, user-generated content, or social features, and it does not collect information from children. The iOS, iPadOS, and macOS versions offer in-app purchases, and the Android versions offer paid portrait packs (see section 5). Paid content is intended for adults, not children, and is not targeted at children.
9. Changes and contact
If this policy changes, we will update this page and revise the effective date. Changes affecting your rights will be called out clearly.
For privacy questions, bug reports, or content corrections, contact us through the Support page.