1. Information kept on your device
The app keeps the following information in its device storage to provide results, continue questionnaires, maintain your archive and favorites, and support sharing.
- Your answers, scores, detailed results and creation times, questionnaires in progress, favorites, and mood entries.
- An optional nickname, language preference, your daily fortune focus, and the month and day of an optional birthday. The birth year is not stored.
- Face-story results and observation summaries, plus a photo only if you separately choose to keep it.
The current app does not require a name, age or gender profile, or an email/password sign-in. Nickname and birthday are optional, and you can use the core features without them. Detailed answers, scores, nickname, birthday, mood entries, and detailed face-story, fortune and compatibility results are not included in the Firebase type-distribution upload described below.
2. Anonymous authentication and type distribution
There is no sign-in screen, but the app uses Firebase Authentication's anonymous sign-in internally. A Firebase-issued UID distinguishes participation records across installations and authentication states. Anonymous authentication does not mean that no identifiers or personal data are processed.
When you complete an MBTI or Egen & Teto questionnaire, the app automatically sends a summary of your latest type to Firebase Realtime Database. This does not require a separate “turn on sync” choice. The transmitted information is:
- A type code, result ID, question version, scoring version, completion time and server update time, linked to an anonymous UID.
- A schema version describing the data format. The app keeps the latest record for MBTI and for Egen & Teto; it does not upload your entire archive.
These records support type-distribution counts, latest-result updates, duplicate-count prevention and deletion requests. The server uses an internal participation record linking a UID to its type; the public distribution in the app shows counts by type only. These counts are not a verified number of individual people.
If the device is offline or a transfer fails, the app keeps pending operations locally and processes them when a connection or retry is available. Latest results already kept on the device can also be included in this process.
3. Face photos and on-device analysis
If you choose the face-story feature, a photo you select or take is analyzed on your device with Google ML Kit Face Detection. It reads face position, landmarks around the eyes, nose and mouth, head angles, and probabilities used to classify a smiling expression and open eyes. It is not used to identify a person, authenticate a face or track users by their face. Face stories are entertainment, not medical diagnoses or objective assessments of personality or the future.
An analysis copy is resized and oriented, and metadata such as EXIF location information is removed. The selected original is not overwritten. Photos and analysis results are not uploaded to Firebase or Paeek's remote servers.
Temporary analysis photos are deleted during cleanup, such as when replacing a photo or leaving the screen. Old analysis cache left after an interruption or cleanup failure is cleaned again when the feature is opened later. Keeping a photo is off by default. A copy is saved in the app's private storage only if you explicitly choose to keep it. Observation summaries and results can be saved to the archive independently of that choice.
App-backup exclusion is configured on Android, and saved-photo backup exclusion is configured on iOS. This is not an absolute guarantee about every operating-system backup behavior. Your original photos and cards you export to your photo library may be kept or backed up separately under your device and photo-service settings.
ML Kit does not send input photos or analysis outputs to Google servers, but it sends API usage and performance metrics to Google and may contact servers for updates. “Photos are analyzed on-device” therefore does not mean “no information is ever sent externally.”
4. Ads and ad privacy choices
The app displays Google AdMob banner ads. Google User Messaging Platform (UMP) updates required consent information and shows consent messages depending on your region and settings. Ads are requested when the SDK permits ad requests. An “Ad privacy settings” option appears in the app settings when UMP requires a privacy-options form.
The ads SDK may process IP addresses, advertising and device identifiers, interactions such as app launches, ad impressions and clicks, and performance or diagnostic information to serve ads, measure their effects and prevent fraud. An IP address may be used to estimate a general location; the app does not request GPS location permission. Personalization and the information used depend on consent status, region, SDK and device settings. The app does not force all ads to be non-personalized.
Where available, you can change choices through ad privacy settings and your device's advertising-identifier or tracking controls. Ad consent is not a separate control for type-distribution uploads.
5. Authentication, security and SDK technical data
Firebase Authentication and Realtime Database may process IP addresses, user agents and authentication-related technical information to provide their services, protect security and prevent abuse. Firebase App Check processes attestation material and tokens used to verify the app and device. Release builds are configured to use Google Play Integrity on Android and Apple App Attest with DeviceCheck fallback on iOS. This configuration is not a guarantee that every request is blocked when necessary or that security is absolute.
The current app does not implement a separate analytics feature using Firebase Analytics or Crashlytics SDKs. This does not mean that AdMob, Firebase or ML Kit process no service or diagnostic data of their own. Their official notices below provide additional details about processing and retention.
6. Permissions and sharing you choose
- Camera: Used when you choose to take a face photo or scan a personality QR code.
- Photo selection: You choose a photo for the face-story feature through the system photo picker. On Android, this is not implemented by requesting broad access to your entire photo library.
- Saving to your photo library: Used when you save a result card. The app may request add-photo permission on iOS or the required storage permission on Android 9 and earlier.
Denying permission can limit the corresponding capture, scan or save feature; you can still use questionnaires such as MBTI and Egen & Teto. Permissions can be changed in your operating-system settings.
When you choose to share, a result card is passed through the operating-system share sheet to an app or recipient you select. A nickname is shown on the card if you separately choose to include it. A personality QR code may contain a type, axis scores and your chosen nickname. Original face photos are not included in shared result cards.
Cards saved in your photo library, content sent to another app and copies kept by recipients are not removed by deleting data inside this app. The relevant device, service or recipient's storage practices and policies apply.
7. Retention and deletion
- Device records: Results, progress, mood entries and chosen details remain on the device until you change or delete them. Deleting an individual archive result removes that result and its associated app-kept photo and favorite; it does not delete your latest server-side type participation record.
- Delete app data: The deletion feature in app settings first saves a remote-participation deletion request locally, then removes device records such as results, questionnaires in progress, kept photos, nickname, mood entries, fortune birthday and focus. Language preference, ad consent and SDK authentication state may have a different reset scope.
- Remote records: The current version's latest type records remain until replaced by a new result or a deletion request is processed. An offline deletion request is processed after a server connection becomes available, and the related participation is then removed from the distribution. Immediate, complete deletion is not guaranteed; check the participation-processing status in the app.
- Anonymous authentication account: The app's data-deletion button removes type participation records, not the Firebase anonymous Authentication account itself. Authentication identifiers, security logs and SDK-related records are handled separately under Google's policies and retention procedures.
Uninstalling the app alone does not send a server-deletion request. If you want remote participation removed, use the in-app deletion feature before uninstalling and check its status after a connection is available. Content you already shared or saved to a photo library must be deleted separately from those locations.
Server records or existing aggregates from earlier versions may remain. The content and access conditions of earlier records may differ from the current version. Earlier records not linked to the current anonymous UID may not be automatically removed by the new deletion feature. Contact us below about those records.
8. Service providers and international processing
Paeek uses the following external services to provide app features. Relevant information is sent to the provider when network services are used, and each provider's privacy policy and service-specific retention procedures apply.
- Google LLC — Firebase Authentication, Realtime Database and Cloud Functions: Anonymous authentication, storage of latest types and type-distribution processing. The app's Realtime Database and aggregation functions are configured in Singapore (asia-southeast1). Firebase Authentication is processed in the United States according to Google's documentation.
- Google LLC — AdMob, UMP, ML Kit and App Check/Google Play Integrity: Ads and consent management, the SDK for on-device face analysis and its usage/performance metrics, and app/device verification. Technical and service data may be processed on Google's global infrastructure, including the United States.
- Apple Inc. — App Attest/DeviceCheck: Attestation material and tokens used to verify an iOS app and device. Apple's global infrastructure and privacy policy apply.
Type transfers may occur at result completion and on connection or retry; authentication and security processing on connection; ad processing when the SDK permits requests; and ML Kit technical-data processing when the feature is used. Inquiry information is processed when you send an email. Technical-log and backup retention periods vary by service; consult the providers' official notices.
Photo analysis itself happens on the device, and the Firebase type upload does not include face photos, detailed answers or birthdays. This does not mean that all app information is processed only on the device or in South Korea. Without a connection, network features such as remote distribution and ads can be limited, and type transfers or deletion requests can remain pending.
9. Safeguards and your choices
Communication with external services uses HTTPS/TLS, and device records are kept in app storage. Current-version individual server records are restricted by Firebase UID-based access rules; the public distribution screen shows aggregate counts by type only. Separate administrative permissions are used for service operation and aggregation. These measures do not guarantee protection against every risk or the security of your device and external services.
You can change optional details and delete device records in the app, or change camera/photo permissions and advertising choices in device settings. You can contact Paeek to ask about access, correction, deletion or processing of information. If an anonymous record cannot be linked to your current authentication state, it may be difficult to locate or delete a particular server record. Use the in-app deletion feature first where possible.
10. Contact and younger users
Send privacy questions or requests to developer and operator Paeek at eovkf2040@gmail.com. If you email us, your email address and message are used to respond and handle your request. Inquiry records are kept as needed to handle and follow up on the request; information no longer needed is deleted.
The current app does not require age or gender as mandatory information. Younger users and their guardians may also contact us about data handling. Do not send unnecessary sensitive information such as national identification numbers, financial information, face photos, passwords or authentication tokens in your inquiry.
11. Updates and official references
If app features or data practices change, this page and its effective and last-updated dates will be updated. These official resources describe the privacy practices of the services used.