Version: 2.5
Effective date: November 13, 2026
Applies to: Face Explorer (脸型探索) for iPhone, iPad and macOS
Public URL: https://z415073783.github.io/app/FaceAnalyse/en/privacy.html
Contact: z674636160@163.com
Summary
Face Explorer does not require an account. The photo, birth information, name, MBTI type or tarot question you choose to provide is sent over an encrypted connection to our own server. The server computes deterministic facts in memory (e.g., Four Pillars/Five Elements, zodiac, tarot cards, life path number, synastry relations) and a third-party AI service (DeepSeek) turns them into an entertainment reading. We do not store your photo, birth information, name, question or report text on our servers, and we do not use them for advertising or model training. We use only a randomly generated device identifier for request verification, daily limits and abuse prevention. For two-person scenes, you must obtain the other person's consent. Completed readings are saved only on your device (up to the latest 50, including facts, full report and a compressed thumbnail; no original image). You can delete/clear them at any time; we do not upload local history or thumbnails. Optionally, you may save a local-only “My Profile” (birth information, name and MBTI type) on your device to pre-fill readings and daily content; it is never uploaded and can be edited or deleted at any time in Settings (see Section 13).
On iOS, product usage statistics and crash diagnostics are provided by Firebase (Google) — Firebase Analytics and Firebase Crashlytics — and are initialized only after you consent to this policy; before consent, the app makes no network requests. Firebase is not used for advertising or ad personalization, we do not use IDFA, and we do not track you across apps (see Section 3 and the Appendix).
1. Information We Collect
1.1 Provided by you
Photo: one photo you choose from your library or take with the camera for the face/classic-face/palm reading (a palm photo for palm reading). It is used only for this reading and released after processing (see Section 2).
Birth information: calendar type, birth date, birth time or "time unknown", birth city/longitude/timezone, and gender you enter for Bazi/horoscope/birthday/two-person scenes. Used only in memory for this reading; not stored on our servers. You may optionally keep it in your local-only profile on your device (Section 13).
Name: the name you enter for name/synastry readings. Used only for this reading; not stored on our servers (you may optionally save it in your local-only profile, Section 13).
MBTI type: the four-letter type you select. Used only for this reading; not stored on our servers (you may optionally save it in your local-only profile, Section 13).
Local profile (optional): you may save birth information, name and MBTI type in “My Profile” on your device so readings and daily content can pre-fill them. It is stored only on your device (Application Support, excluded from iCloud backup), never uploaded to our servers or the third-party AI, and can be edited or deleted at any time in Settings; deleting it does not affect saved history.
Tarot question: the optional question you enter (0–200 characters). Used only for this reading; not stored on our servers and not logged.
Two-person information (third party): partner birth information and optional name/gender for synastry/Bazi compatibility. You must have the other person's consent. Used only for this reading; not stored on our servers.
Language preference: used to choose the report language (Simplified Chinese, Traditional Chinese, English, German, French, Italian, Spanish or Japanese).
1.2 Generated automatically
Device identifier (Device ID): a random UUID generated when the app is installed and stored in the system Keychain. It is not IDFA, IDFV, a serial number or a phone number and cannot identify you personally. It is used for request signing, per-device daily limits, abuse prevention and troubleshooting.
Request metadata: time, duration, status code, image bytes and dimensions, token usage and server error codes. Used for quotas, cost accounting and service reliability.
Network logs: our server keeps access logs for security and troubleshooting (time, path, status code, duration, device identifier, IP address) for a short retention period. Logs do not contain the photo, its base64 data or the report text.
Product usage statistics and crash diagnostics (Firebase, iOS only): after you consent to this policy, Firebase Analytics records usage events, sessions, device model/OS version/app version, an app instance ID and a coarse region derived from your IP address; Firebase Crashlytics records crash stack traces, device state, OS/app version and an installation identifier when the app crashes. This data is not used for advertising or ad personalization, we do not collect IDFA, and we do not track you across apps (see Section 3).
1.3 Purchases
In-app purchases are handled by Apple (App Store / StoreKit). We do not collect or store your payment card number, Apple ID or billing information.
Analysis credits (1 free per day; +6 per in-app purchase) are stored locally on your device (Keychain) and are not uploaded to our servers.
Apple provides us with limited transaction status so credits can be added to your device.
1.4 What we do NOT collect
We do not collect account credentials, phone number, email (unless you email us), contacts, precise location, other photos in your library, IDFA/advertising identifiers, Face ID or other biometric templates, or information about people you share reports with. We do not integrate advertising SDKs, do not use IDFA or other advertising identifiers, and do not track you across apps. On iOS, product usage statistics and crash diagnostics are provided by Firebase (Google) and are initialized only after you consent to this policy (see Section 3).
Name, birth date/time/place/longitude, gender, MBTI type, tarot question and two-person information are processed only when you start the relevant reading, are not stored on our servers, not used for profiling, advertising or model training, and are not requested when you do not use those scenes. The only exception is the optional local profile you choose to save on your device (Section 13): it stays on that device and is never uploaded, and you can delete it at any time in Settings.
No network requests before consent: the app makes no network requests until you consent to this policy. On iOS, Firebase Analytics and Firebase Crashlytics are initialized only after consent and are not used for advertising or ad personalization. Firebase processes data under Google's policies (Google Privacy Policy, Firebase Privacy and Security); retention and cross-border processing of this data are governed by Google's policies. You can stop this collection by not consenting or by uninstalling the app (see Section 6).
2. How Photos Are Processed
Only the photo you select: the app does not read your library in bulk. It uses the system photo picker or camera to minimize permission scope.
Local compression and metadata removal: before upload, the photo is redrawn as JPEG (long edge about 1280 px, quality about 0.8), orientation is baked into the pixels, and EXIF, GPS location and camera-device metadata are removed.
Encrypted transfer: the photo is base64-encoded in an HTTPS request to our own server (hk.zengliangmin.cn), protected by request signatures against tampering and replay.
Forwarded to a third-party AI: our server forwards the photo to DeepSeek for visual analysis. See DeepSeek's privacy policy: Chinese / English. We forward data in a minimized form; the provider's retention, training and processing practices are governed by its own policy, and we make no commitments beyond it.
In-memory processing, no persistence: our server validates, forwards and releases the photo in memory only. We do not write photos to server disks, do not use object storage, do not log them and do not back them up. Memory is released when analysis ends or the request is closed. Report text is streamed to your device and is not stored on our servers.
Photos are not stored long-term on the device: the app keeps the photo in memory only for the current session; it is not written to your library or app cache. Local history stores result facts, the full report and one compressed thumbnail (240–320px long edge JPEG, EXIF removed, not the original); deleting history or clearing all removes thumbnails. Photos taken with the camera are processed the same way as library photos: used only for this analysis, the original is not stored on our servers; local history may keep a compressed thumbnail, which you can delete at any time.
No training or advertising: we do not use your photos to train AI models, for advertising, for sale, or for sharing with research institutions.
Report sharing: the share card/text is generated on-device only when you tap Share. It contains only the displayed report excerpt, scene, date, brand and disclaimer; it does not include birth details, names, questions, photos, two-person information or raw input. It is not uploaded or posted automatically; the destination third-party app handles it under its own privacy policy.
3. Third-Party Services
Third party
Purpose
Data involved
Notes
DeepSeek
AI entertainment reading inference (face/palm/Bazi/horoscope/birthday/tarot/name/MBTI/synastry)
Compressed photo, birth information/name/MBTI/tarot question/two-person information (as applicable), report language
Processing governed by DeepSeek's official privacy policy; servers may be located in mainland China or elsewhere, which may involve cross-border transfer
Firebase Analytics (Google)
Product usage statistics and feature improvement (iOS only)
Usage events, sessions, device model/OS version/app version, app instance ID, coarse region derived from IP
Not used for advertising or ad personalization; no IDFA and no cross-app tracking. Processing governed by Google's privacy policy and Firebase Privacy and Security; initialized only after you consent to this policy
Same processor and policies as above; initialized only after you consent to this policy
Apple (App Store / StoreKit)
In-app purchases and receipts
Transaction information
Processed by Apple under its privacy policy; we do not access payment credentials
Our own server and CDN/reverse proxy
API access, HTTPS, rate limiting
Request metadata, network logs
Used for service operation, security and abuse prevention
We do not sell your personal information or provide photos to third parties other than the services above, unless required by law or necessary to protect users or public safety. On iOS, Firebase data is not used for advertising, ad personalization or cross-app tracking.
4. Retention of Device ID and Usage Data
Device ID: stored in your device Keychain for request signing and daily limits; on our usage table, per-device detail is deleted after 30 days.
Aggregated usage without identifiers (total requests, tokens, image bytes): retained for up to 365 days for cost and capacity planning.
Server access logs: retained short-term under log rotation (typically no more than 30 days) for security and troubleshooting.
Local credit ledger: stored in your device Keychain until you uninstall the app or clear its data; after uninstall, Keychain items may remain so unused credits can be restored, depending on system behavior.
Birth information/name/MBTI/tarot question/two-person information/photos/reports: not written to server disks, not logged; released after the request ends.
Local history/thumbnails: stored only in your device's Application Support, up to 50 items; oldest removed beyond 50; deleted on individual delete/clear all; excluded from iCloud backup; never uploaded. Viewing/deleting history does not change credits or purchases.
Firebase Analytics/Crashlytics data (iOS only): processed by Google as our service provider; retention and cross-border transfer are governed by Google's policies (see Section 3). The server retention periods above do not apply to this data, and we do not set a separate retention period for it.
5. Data Security
HTTPS is used end to end; APIs use HMAC request signatures, timestamps and nonces to prevent tampering and replay.
The AI provider's real API key exists only on our server; the client holds no cloud-provider credentials.
We follow data minimization: no photos on disk, no report text in logs, and logs contain metadata only.
No internet transmission or processing can be absolutely secure. Please avoid uploading photos containing sensitive information (e.g., identity documents, addresses, or other people's private information).
6. Your Rights and Choices
Do not use analysis: you may browse the app without selecting a photo; no photo is uploaded unless you start an analysis.
Deny permissions: you may deny photo-library or camera access; the app will explain but will not force you. You can still view the privacy policy and purchase credits.
Delete local data: uninstall the app or clear its data in system settings. Since purchased credits are tracked locally, you may need "Restore Purchases" (based on transaction history, subject to the limitations in the Terms of Use).
Contact us: email z674636160@163.com to request access, correction, deletion or to file a complaint. Because there are no accounts, we may ask for your device identifier or request time to locate records; we will respond within the period required by law.
Withdraw consent: you may stop using the service. Completed processing cannot be undone, but this does not affect the lawfulness of processing before withdrawal. On iOS, Firebase Analytics and Firebase Crashlytics are initialized only after consent, so they are not initialized if you do not consent; uninstalling the app stops any further collection from that device.
7. Minors
The app is rated 12+ and is not designed for children under 12. If you are under 18, please use it with the consent and guidance of a parent or guardian. We do not actively collect age or date of birth. If a guardian believes a minor uploaded a photo without consent, contact us and we will help handle the relevant records.
8. AI-Generated Content and Disclaimer
Reports are generated by a third-party AI model based on the information you provide and traditional/entertainment rules, for entertainment and self-reflection only. They are not medical, investment, legal, psychological, marital/divorce or other professional decision advice. AI results may be inaccurate, incomplete or inconsistent with reality. Do not make medical, aesthetic, investment, legal or relationship decisions based on a report, and do not use it to evaluate other people or make decisions for them.
Bazi/astrology/tarot/birthday/name/MBTI/synastry content is traditional or pop-culture entertainment, does not predict the future and is not guaranteed to be accurate; 12+. For two-person scenes you must obtain the other person's consent. If a photo/input cannot be analyzed (e.g., no clear face or palm, content filter), the app will ask you to change it and will not deduct a credit.
9. Changes to This Policy
We may update this policy due to feature changes, legal requirements or third-party service changes. The new version will be published on this page with a new effective date; material changes will be communicated in the app in a reasonable way. Continued use means you accept the updated policy.
Terms of Use: https://z415073783.github.io/app/FaceAnalyse/en/term.html
11. Multi-Scene Entertainment Reading Data (New in v2.0)
Scenes: face, palm, Bazi/Five Elements, horoscope, birthday, tarot, name, MBTI, synastry and Bazi compatibility, plus the existing classic face score.
Server-side deterministic calculation: birth information is used to compute Four Pillars/Five Elements/true solar time in memory; tarot cards are drawn server-side; life path number/zodiac/synastry relations are computed by fixed rules. These facts and inputs exist only in memory for the request and are not written to disk or logs.
Third-party AI: the server forwards the necessary facts and inputs (photo/birth information/name/question, as applicable) to DeepSeek to generate the entertainment reading. Processing by DeepSeek is governed by its official privacy policy; we require minimization and prohibit advertising use.
Two-person information: you must confirm that you have obtained the other person's consent. We use it only for this reading, do not store it and do not use it for identification or profiling. If the other person contacts us, we will explain the processing; because we do not retain the data, it may not be possible to locate a specific request.
What we do not do: no identity verification, age verification, medical/dermatological diagnosis, investment advice, marriage/divorce decisions, psychological diagnosis, advertising profiles, or cross-app tracking; we do not store birth information, name, MBTI, tarot questions, photos, two-person information or report history on our servers; completed readings may be kept only in local history on your device (Section 12), and an optional profile may be kept only on your device (Section 13).
Age: 12+; not directed to children under 12. For third-party information you must ensure lawful permission.
App Store privacy labels: "Other User Content" (birth information/name/MBTI/question) is collected for App Functionality, not linked to identity and not used for tracking; photos remain "Photos"; device ID is used for App Functionality/abuse prevention.
12. Local History, Thumbnails and Notifications (New in v2.1; updated in v2.4)
Local history content: successful readings are saved on the device with scene, completion time, language, facts, full report and one compressed thumbnail (240–320px long edge JPEG, EXIF removed for image scenes; scene icon placeholder for text scenes). We do not store the original image, photo base64, raw input objects (birth date, name, tarot question, two-person raw input); derived display facts (e.g., solar/lunar date, Four Pillars, Five Elements) may be stored locally with the result; names/questions naturally appearing in the report are stored locally only as part of that report.
Device-only, not uploaded: history and thumbnails live in the app's Application Support, are not sent to our server or third-party AI, are not synced across devices, and are excluded from iCloud backup.
Limit and deletion: keep at most the latest 50 items; adding the 51st removes the oldest; individual delete and clear-all are supported with confirmation and are irreversible; deleting history cancels its pending local notification.
Notification permission and purpose: before the first reading we ask for notification permission to remind you when a reading completes; optionally, you can enable daily fortune reminders in Settings. Declining does not block analysis or daily content, and only in-app banners are used where applicable. Both kinds of notifications contain only generic text — completion reminders show the scene name and a generic “tap to view” message; daily reminders show only a generic “today’s fortune is ready” message — no birth information, name, question, MBTI type, report text or thumbnail; you can turn completion alerts and daily reminders off at any time in the app or in system settings.
Billing separation: saving/viewing/deleting history does not refund, recharge or consume credits; "read again" starts a new reading and is charged as a new reading.
Birth information/name/MBTI/tarot question/two-person information: still processed in server memory under this policy, not written to disk/logs and no server-side history; local history does not additionally store raw inputs.
Age: local history/notifications are also 12+ entertainment; not used for advertising, profiling or cross-app tracking.
13. Local Profile, Daily Content and Reminders, Report Cache (New in v2.4)
Local profile (optional, device only): “My Profile” lets you optionally save birth information, name and MBTI type on your device so that readings and daily content can pre-fill them. It is stored in the app’s Application Support, excluded from iCloud backup, never uploaded to our servers or the third-party AI, and not included in local history as an input record. You can edit or delete it at any time in Settings; deleting it does not affect saved history or credits. If you never create a profile, no profile data is stored.
Daily content: when you view the daily fortune card, the app sends POST /api/v1/daily to our server with either a zodiac sign or your birth month and day (derived on the device) plus the interface language. The server computes deterministic facts (e.g., sign, lucky color/number, daily tarot card) in memory and returns them. No third-party AI is called, no analysis credit or quota is consumed, and the endpoint does not create server-side history linked to you.
Daily reminders (optional, local): if you turn on daily reminders, the app schedules local notifications at 08:30 and 21:00 in your device’s time zone. Their content is generic (“today’s fortune is ready”); no birth information, name, MBTI type, question, report text or thumbnail is included. Reminders are scheduled and shown by the system on your device; you can turn them off at any time in Settings or system settings. Declining or disabling them does not affect daily content or readings.
MBTI quiz: the 12-question personality quiz is scored locally on your device. Your answers are not uploaded; only if you choose to save the resulting 4-letter type to your local profile, or start an MBTI reading, is the type stored on the device / sent as the reading input under Section 1.
Server-side generic report cache: for horoscope reports and daily tarot (single card, no question), the server may cache the generated report. The cache key contains only non-identifying parameters (sign and period/date, language, prompt version); it contains no device identifier, photo, birth date, name, MBTI type, question or other personal data, and cannot be used to build a user profile. Cached entries expire at the end of the period + 1 hour (daily tarot: next midnight + 1 hour) and the cache holds at most 500 entries, evicting the oldest. Personalized tarot readings with a question are not cached.
Rating prompt: after two consecutive days of use, the app may ask the system to show the standard App Store rating prompt at most once. The decision is made locally on your device; we do not collect or receive any data about whether the prompt was shown or what rating you gave (Apple processes it under its own policy), and the prompt can be dismissed without affecting the app.
Appendix: App Store Privacy Label Summary (for review and development alignment)
Data type
Collected
Purpose
Linked to identity
Used for tracking
Photos or videos (user content)
Yes (uploaded only when you start an analysis)
App functionality
No
No
Device ID (random UUID) and Firebase app instance ID (iOS only)
Yes
App functionality, abuse prevention; app instance ID used for usage analytics on iOS
No
No
Usage data (request/usage metadata)
Yes (server-side counters)
App functionality, analytics (cost and reliability)
No
No
Usage data (Firebase Analytics, iOS only: usage events, sessions, device and OS/app version, coarse region)
Note: the Firebase rows apply only to the iOS version; the macOS version does not integrate Firebase and does not collect this usage or diagnostics data.