1. Scope and who this policy is for
This Privacy Policy applies to the Pandia mobile application for iOS and Android and to the Pandia-specific services used by the application. In this policy, “Pandia,” “we,” “us,” and “our” refer to the developer and operator identified in the applicable app-store listing. “You” means a person using Pandia.
This policy does not govern a third-party website, app, operating-system feature, app store, advertisement, or service that you choose to open or use. Those services apply their own terms and privacy notices.
Pandia's palm, horoscope, and numerology content is designed for entertainment and reflection. It is not medical, psychological, legal, financial, or other professional advice. We do not use a palm photo to identify you, authenticate you, determine your identity, or create a face-recognition or biometric identity template.
2. Information Pandia handles
The information processed depends on the features you choose to use. Pandia is designed to work without a conventional user account.
| Category | Examples | Why it is handled |
|---|---|---|
| Palm-reading content | A processed photo of the left palm, right palm, or both; selected hand; generated reading; line coordinates and summaries | To validate the image, generate the requested AI reading, display it, and let you reopen the latest successful reading |
| Birth and astrology details | Birth date, local birth time, GMT offset, corresponding UTC birth moment, Sun sign, Moon sign, and Life Path number | To calculate and display horoscope and numerology experiences and select relevant daily content |
| Anonymous app identifiers | A randomly generated installation identifier, its server-side cryptographic hash, request IDs, and public reading IDs | To associate requests with the same installation, prevent duplicate submissions, return the correct reading, apply limits, and protect the service |
| Notification data | Firebase Cloud Messaging token, platform, locale, time zone, app version, notification status, and delivery timestamps | To deliver requested palm-completion, horoscope, and numerology notifications at an appropriate local time |
| Advertising and consent data | Consent choices, IP address, device or advertising identifiers when permitted, device characteristics, approximate location derived from IP, ad impressions, clicks, and reward events | To request, deliver, measure, limit, personalize where permitted, and prevent abuse of interstitial and rewarded advertisements |
| Local app data | Cached readings, processed palm image, birth chart, daily editions, ad counters, remote configuration, notification preference, and installation ID | To preserve app state, support offline or fast loading, reopen a reading, and enforce user-visible feature behavior |
| Technical data | IP address, HTTP headers, timestamps, response status, server logs, model usage, and error codes | To operate, secure, debug, maintain, and improve reliability of the service |
We do not ask you to provide a name, email address, telephone number, postal address, contacts, microphone recording, or precise GPS location through the current Pandia app. We do not currently offer an in-app purchase or collect payment-card data. An operating system, app store, ad provider, or network provider may independently process information under its own policy.
3. Camera access, palm images, and AI processing
Camera and on-device processing
Pandia requests camera permission only when the palm-capture experience needs it. Camera frames are evaluated on the device for hand presence, side, position, and capture quality. Pandia crops and resizes the selected image before submission. We do not use the camera in the background and do not request microphone access.
Transmission and backend handling
When you choose to analyze a palm, the processed image is encrypted in transit and uploaded to the Pandia backend. The backend reads the upload into temporary request memory, validates its type and dimensions, and sends it to OpenAI's API to produce a reading. The production configuration does not intentionally write uploaded palm-image bytes to Pandia's database or permanent object storage. Temporary files created by web-server or operating-system request handling may exist briefly and are managed by that infrastructure.
OpenAI
The palm image, requested hand, instructions, an anonymous safety identifier, and request metadata are sent to OpenAI. Pandia sets the OpenAI Responses API request to store: false. OpenAI states that API inputs and outputs are not used to train its models by default unless the API customer opts in. OpenAI may nevertheless process or temporarily retain content and related metadata to provide the service, operate background processing, detect abuse, comply with law, and enforce its policies. OpenAI's standard abuse-monitoring logs may be retained for up to 30 days unless different approved retention controls apply; certain safety detections may require longer review or retention.
The text and structured coordinates produced by the model are returned to Pandia. The backend stores the completed reading and operational metadata, but not the palm-image bytes. AI outputs can be inaccurate, incomplete, or unexpected. Do not use Pandia to make consequential decisions.
Copy kept on your device
After a successful reading, Pandia may save the processed palm image and reading in the app's private support storage on your device so that the latest result can be reopened. The image is not added to your public photo library. It remains controlled by your device and may be included in device backups depending on your operating-system and backup settings. Clearing Pandia's app data or uninstalling Pandia normally removes this local copy, subject to platform backup and restoration behavior.
4. Horoscope and Numerology information
If you use Horoscope or Numerology, you may enter a birth date, birth time, and GMT offset. The app converts that entry into a UTC birth moment and transmits the UTC value and original calendar birth date with the anonymous installation ID. The backend stores the UTC birth moment, birth date, calculated Sun and Moon signs, Life Path number, calculation versions, and a cryptographic hash of the installation ID.
This information is used to calculate the requested features, restore the chart for the same installation, select daily content, and schedule notifications if enabled. Pandia does not require your name or birthplace for the current calculation. Birth information can still be personal and should not be entered for another person without their permission.
Daily horoscope and numerology editorial content is common to users with the same relevant sign or number. The app caches published editions locally so they can load quickly and refreshes them from the backend.
5. Advertising, consent, and local counters
Pandia uses Google Mobile Ads (AdMob) to provide interstitial advertisements and opt-in rewarded advertisements. A rewarded advertisement may unlock a reading after a local free-use allowance is exhausted. If advertising inventory is unavailable, the app may allow the experience to continue without an ad.
Google and participating advertising partners may process IP addresses, cookies or similar local storage, mobile advertising identifiers where available and permitted, publisher-provided or first-party identifiers, device and app information, coarse location inferred from IP, diagnostic information, and interactions with ads. They may use this information to deliver and measure ads, limit repeated ads, combat fraud and abuse, and personalize advertising where the law and your choices permit. Third-party advertisers may receive an ad interaction and process it under their own policies.
Where required, Pandia uses Google's User Messaging Platform to request and remember advertising consent choices before requesting ads. The choices and vendors shown in the consent interface can vary by region and by Google's current configuration. Depending on your region and device, you may also control ad personalization or reset an advertising identifier through system settings. Pandia does not receive a readable profile of the interests Google may use to choose an ad.
Pandia maintains local counters and time windows to decide when an ad may be shown. The backend supplies configurable thresholds, but the counters themselves are stored on the device. Google requires publishers using its services to disclose Google's data handling; more information is available at How Google uses information from sites or apps that use its services and in the Google Privacy Policy.
6. Push notifications
Notifications are optional. If you grant permission, Pandia uses Firebase Cloud Messaging to receive a device push token and sends that token to the Pandia backend together with the anonymous installation identifier, platform, locale, local time-zone identifier, and app version when available.
These details support completion notices for palm readings and scheduled daily Horoscope and Numerology messages. The backend stores delivery status and timestamps to avoid duplicate messages. Notification payloads are designed to contain routing details such as a reading ID, sign, or Life Path number rather than palm images or full readings.
You can deny notification permission, disable notifications in system settings, or use any in-app notification control that is available. When Pandia unregisters notifications, it asks the backend to remove push-device records associated with that installation and asks Firebase to delete the local messaging token. Copies may remain temporarily in logs, backups, or provider systems.
7. How and why information is used
We use the information described above to:
- provide the feature you request, including image capture, palm analysis, birth-chart calculations, daily content, sharing, and notifications;
- return data only to the installation that created or requested it;
- save app state and make frequently used content available without unnecessary network requests;
- show, measure, cap, and reward advertisements and manage legally required consent choices;
- detect duplicate, malformed, unsafe, fraudulent, abusive, or excessive requests;
- diagnose failures, monitor service health, maintain security, and improve performance;
- comply with law, court orders, enforceable requests, and our policies; and
- protect users, the public, our service providers, and our rights.
Where privacy law requires a legal basis, the basis depends on the processing: performance of the service you request; our legitimate interests in operating, securing, and improving Pandia; consent for permissions, personalized advertising, or similar storage where required; and compliance with legal obligations. You may withdraw consent where processing is based on consent, without affecting processing already completed.
9. Retention and deletion
We retain information only for as long as reasonably needed for the purposes described in this policy, subject to operational, security, backup, dispute-resolution, and legal requirements. Different categories have different lifecycles:
- Palm-image bytes: not intentionally stored in Pandia's production database or permanent file storage. They are held during request validation and transmission to OpenAI, then released by application code. OpenAI and infrastructure providers apply their own temporary processing and retention practices described above.
- Generated palm readings: stored by the backend with the hashed installation identifier and operational metadata so the installation can poll for and retrieve results. A successful latest reading and processed image may also remain locally on the device.
- Birth chart and Numerology values: stored until replaced for the same installation, removed following a valid request, or no longer reasonably needed to operate the feature.
- Push-device data: stored while notifications are enabled and removed from the active backend record when the app successfully unregisters the installation, subject to temporary backups and logs.
- Daily content and delivery ledgers: retained for editorial operation, delivery deduplication, security, and service records.
- Ad and consent data: retained according to Google, participating vendors, your choices, and applicable law. Local ad counters remain until reset, app data is cleared, or Pandia is uninstalled.
- Technical and security logs: retained for a limited operational period or longer when reasonably necessary for abuse prevention, incident investigation, legal compliance, or dispute resolution.
Deletion from active systems may not immediately remove data from encrypted backups. Backup copies are isolated from ordinary use and expire through normal backup rotation unless preservation is legally required.
10. Your controls and choices
- Camera: deny or revoke camera access in system settings. Palm capture will not function without camera access.
- Notifications: decline the prompt or disable notifications in iOS or Android settings. Some in-app content remains available without notifications.
- Advertising consent: use the Google consent message or privacy-options entry point when one is presented and required in your region. System settings may provide additional advertising controls.
- Birth information: use the change action in Pandia to clear the local birth profile and return to the entry state. A replacement submission updates the backend profile for the same anonymous installation.
- Local data: clear Pandia's app data or uninstall the app to remove ordinary local caches and the randomly generated installation identifier, subject to operating-system backups.
- Sharing: do not use the share action, or cancel the system share sheet, if you do not want another app to receive the generated content.
Reinstalling or clearing app data creates a new anonymous installation identifier. That can prevent the new installation from automatically finding data associated with the old identifier. It does not itself guarantee immediate deletion from backend systems.
11. Privacy rights
Depending on where you live, you may have rights to request access to, correction of, deletion of, restriction of, or portability of personal information; object to certain processing; withdraw consent; opt out of targeted advertising or certain sharing; and lodge a complaint with a data-protection authority. These rights may be limited by exceptions in applicable law.
Pandia does not use a normal account, and backend records generally use a cryptographic hash of a random installation identifier. We may need information available in the app, such as a public reading ID, and reasonable verification before acting on a request. We will not ask for more personal information than reasonably necessary to locate and verify the relevant data.
We do not discriminate against a user for exercising an applicable privacy right. We may retain information that is exempt from deletion or needed for security, fraud prevention, legal compliance, or the establishment, exercise, or defense of legal claims.
12. Children
Pandia is not directed to children under 13, and we do not knowingly collect personal information from a child under 13. If a higher minimum age applies where a user lives, the user must meet that age or use Pandia only with the consent and supervision required by local law. Do not submit a child's palm image or birth information without appropriate authority.
If we learn that information was collected from a child in a manner that violates applicable law, we will take reasonable steps to delete it. A parent or guardian may contact us using the method below.
13. Security
We use administrative, technical, and organizational measures intended to protect information, including encrypted network transport, randomly generated installation identifiers, server-side hashing of those identifiers, access controls, validation, request deduplication, and limiting the information included in notifications.
No application, transmission, or storage system is completely secure. We cannot guarantee that information will never be lost, accessed, disclosed, altered, or destroyed. You are responsible for securing your device, operating-system account, backups, and any app to which you share content.
14. International processing
Pandia's developer and service providers may process information in countries other than the country where you live. Those countries may have different privacy laws. Where required, we rely on recognized transfer mechanisms or other lawful safeguards. Google, OpenAI, Apple, hosting providers, and their subprocessors may operate globally according to their respective policies and contractual commitments.
15. Changes to this policy
We may update this policy when Pandia's features, providers, data practices, or legal obligations change. The “Last updated” date above identifies the current version. If a change is material, we may provide additional notice in the app, through a consent message, on this page, or by another reasonable method. Continuing to use Pandia after an update means the updated policy applies to later activity to the extent permitted by law.
16. Contact and requests
For a privacy question, rights request, or deletion request, contact the Pandia developer through the developer-contact method shown in the Apple App Store or Google Play listing from which you downloaded the app. Include “Pandia Privacy Request” in the subject and, if relevant, the public reading ID shown by the app. Do not email a palm image, full birth details, push token, or other sensitive content.
If you are unable to use the store-listing contact method, revisit this page after an app update for the current contact channel.