Privacy Policy

Article 1 — Information We Do Not Collect

The Service does not collect or request access to:

• Name, email address, phone number, or physical address
• User accounts or passwords (there is no registration)
• GPS location data
• Contact lists, photos, camera, or microphone
• SMS content or usage history of other apps

Article 2 — Data Stored Only on Your Device

1. The following data is stored only in your device's local storage and is never sent to our servers:
   • Your consent status for this Policy
   • Your credit balance (remaining questions)
   • Your reading history and questions
   • Your last check-in date and streak count
2. You can delete all of the above at any time via "Settings → Delete all data" in the app, or by uninstalling the app.
3. The day of the week you select in the Birthday Buddha feature is used only for on-screen display in that session; it is not stored permanently and never leaves your device.

Article 3 — Data Sent to Our Server for Deep Readings

1. When you use the "Deep Consultation" feature, the following is sent to our server to generate your reading: the selected topic (e.g., love, money), the optional question text you typed, and the app language.
2. This data is processed via the OpenAI API to generate the reading text. Under OpenAI's API policy, data sent through the API is not used to train AI models.
3. Our server is stateless: we do not store your questions or readings on our servers (temporary technical error logs, which do not contain question content, may be kept briefly). The generated reading is stored only on your device.
4. Please do not type personally identifiable information (such as real names or ID numbers) into the question field.

Article 4 — Push Notifications

1. The daily fortune reminder is scheduled locally on your device. You can turn notifications on or off at any time in your device settings.
2. If you allow notifications, the app registers a push notification token on our server so that we can also deliver notifications remotely. This token is a random identifier generated by Google's Firebase Cloud Messaging; it contains no name or other personal details and cannot be used by us to identify who you are.
3. The token is stored on our server and used solely for delivering notifications. It becomes invalid when you uninstall the app, and you can request its deletion at any time via the contact details in Article 11.

Article 5 — In-App Purchases

1. All payments are processed by Google Play. We never see or store your card numbers or payment details.
2. We use RevenueCat to validate purchases. Only an anonymous app-generated user ID and the Google Play purchase receipt are transmitted.

Article 6 — Ads and Analytics in the App

The current version of the app contains no advertising and no analytics or tracking SDKs. If this changes in the future, this Policy will be updated first.

Article 7 — Sub-processors

1. The Service relies on the following third-party providers: Google Play (payments), RevenueCat (purchase validation; US), OpenAI (reading generation; US), Supabase (server hosting), and Google Firebase Cloud Messaging (notification delivery; US).
2. These sub-processors implement appropriate data protection measures, including encryption and compliance with applicable data protection laws.

Article 8 — Your Rights under the PDPA

1. You have the right to access, correct, and delete your data under Thailand's Personal Data Protection Act B.E. 2562.
2. Because almost all data lives on your device, you can exercise these rights yourself immediately via "Settings → Delete all data" or by uninstalling the app.
3. For any other request, please contact us via the details in Article 11.

Article 9 — Children

The Service is not directed at children under 13, and we do not knowingly collect data from children. All readings are provided for entertainment and self-reflection only, and do not constitute medical, legal, or financial advice.

Article 10 — Changes to This Policy

We may revise this Policy as necessary. Material changes will be announced on this page. The date of the latest update is shown at the top of this document.

Article 11 — Contact