YOUR INFORMATION. YOUR CHOICES.

Privacy Policy

Buz Horoscopes · Buzly Labs Ltd.
Last updated: October 12, 2026

Buzly Labs Ltd. is responsible for the personal information handled by Buz Horoscopes, also known in earlier versions as Horoscopes Light / Horoscopes Lite. This policy covers our iOS app (com.buzlylabs.horoscopelite), Android app (com.appiato.horoscope), the buzhoroscopes.com website, and related horoscope and sharing services. Contact us at ask@buzlylabs.com.

1. Your profile and the content you use

We use the name, birth date and zodiac sign you enter to personalize your experience. In the new native iOS and Android versions, your birth profile, journal entries, saved fortunes, reminder choices and app preferences are stored locally on your device. Signing in does not currently upload or synchronize that profile or journal to an account. Earlier Android versions also store the entered name and birth date locally.

Requests for horoscopes, dream-dictionary content, compatibility and celebrity birthdays go to our content services. These requests can include a selected zodiac sign or pair of signs, requested date, dictionary search or entry, and the month and day used to find matching celebrity birthdays. The native iOS celebrity-birthday request does not include your birth year. Our servers and hosting providers receive technical request data such as IP address, request path, time, response status and device/browser user agent for delivery, troubleshooting and security.

Your journal is not sent to an AI provider. Public celebrity information comes from our content database; viewing it does not create a public user profile.

Individually purchased AI reports

Personal report forms and saved reading history are stored locally on your device. After your confirmation and purchase, calculated chart positions, time-accuracy flags, the selected report type, relationship mode and, for annual reports, the selected starting month are processed by Firebase and OpenAI. Annual reports also use calculated monthly planetary positions. Names, raw birth dates, cities and geographic coordinates are not sent to OpenAI. We store generated report text, model, a chart hash, a hashed transaction identifier, delivery status, attempt counts and timestamps in Firebase to resume delivery without charging or generating again. Raw chart inputs and Apple signed receipts are not stored in that report database. A purchase receipt is kept in the device Keychain to authorize later link sharing. These individual reports do not automatically synchronize between devices; exporting a PDF preserves a separate copy. Contact ask@buzlylabs.com to request deletion of server report records, with information identifying your order. Deletion may prevent later recovery.

Birth charts and optional AI interpretations

Cosmic Blueprint and You & Me use birth date, time, birth-place coordinates and time zone to calculate charts on your device. Your saved birth details remain local. In iOS, a birth-city search is sent to Apple’s geocoding service. The new Android version searches a bundled city database locally. Enter another person’s details only with their permission.

If you confirm “Explore with AI,” calculated planetary positions, uncertainty/time-accuracy flags, the interpretation type and Partner or Friend mode are sent through our Firebase backend to OpenAI. A comparison includes both charts. Names, raw birth dates, birth cities, geographic coordinates, email addresses and journal entries are not included in that AI request. Calculated charts are derived from birth information and should still be treated as personal information.

To check eligibility, the backend also receives an Apple signed transaction or a Google Play purchase token and verifies the subscription. This purchase proof is not sent to OpenAI. We store a hashed purchase identifier, daily usage counts and dates to enforce limits; the subscription interpretation service does not save your chart, generated interpretation or raw purchase proof in our application database. Individually purchased reports are handled differently, as described below.

We request that OpenAI not store the response as retrievable application history. This does not eliminate provider retention: OpenAI’s standard API abuse-monitoring logs may retain inputs and outputs for up to 30 days, with longer retention for legal or safety reasons. OpenAI states that API content is not used for model training by default unless the customer opts in. See OpenAI’s API data controls. You can use the locally calculated charts without choosing AI generation. For a comparison, continue only if the other person agrees to that processing.

2. Optional accounts in the new native versions

You may use the app without creating an account. If you choose email/password or Google Sign-In, or Sign in with Apple on iOS, Firebase Authentication processes your account identifier, email address, authentication credentials and sign-in information. Apple or Google may supply the name and basic account information you authorize; Apple may supply a private relay email address. Authentication also processes IP addresses and device/user-agent information to secure sign-in and prevent abuse.

Email verification and password-reset messages are service messages, not marketing subscriptions. We do not receive your Apple or Google password. An account does not currently provide cross-platform purchase transfer or cloud journal backup.

3. Notifications

With your permission, the new native iOS and Android apps schedule daily coffee-fortune reminders and birthday greetings on your device. Those local reminders use your saved choices and birth date without uploading that birth date for scheduling. Notification text, including a name in a birthday greeting, may appear on your lock screen according to your system settings.

The iOS app also integrates Apple Push Notification service and Firebase Cloud Messaging. When push registration is enabled, these services process device registration tokens and installation identifiers to address notifications. The current native version keeps its messaging token locally and does not yet upload it to a Buzly Labs campaign-registration endpoint. The new Android app also integrates Firebase Cloud Messaging and keeps its registration token locally for notification support. Earlier iOS versions also integrate Firebase Messaging. Disabling notifications stops their display; it is not the same as deleting an account or all provider records.

You can change notification permission in iOS or Android settings and disable available reminders in the app.

4. Purchases and subscriptions

Apple App Store or Google Play handles payments, subscriptions and their purchase records. We do not receive your payment card details. The app checks product identifiers, transaction or purchase information and subscription status to determine access and restore eligible purchases.

In earlier Android versions, purchase verification sends a device-derived identifier, app/package and product identifiers, purchase token, and available order, expiry, renewal and status information to our subscription service. This lets us verify purchases and return paid-access status. The device identifier is also used when checking existing entitlements.

The new native Android version uses Google Play Billing for purchase access and restoration. Optional AI requests additionally verify a subscription with Google Play through our backend, as described above.

The new native iOS version reads App Store products and verified entitlements, offers restoration, and initiates subscriptions and the one-time Remove Ads purchase through Apple. An active subscription or verified Remove Ads purchase disables advertising. Earlier versions offer subscriptions, an ad-removal purchase and/or individual personal reports, depending on the version.

Deleting an app or account does not cancel a subscription. Manage cancellation through your Apple or Google subscription settings. Store purchase records remain subject to the store's policies; previously consumed individual reports may not be recoverable through subscription restoration.

5. Personal astrology reports

Earlier iOS versions offer personal reports using the external astrology service at api.astro.delivery. When you submit a report form, information sent for generation can include first and last name, sex/gender selection, birth date, birth time or whether it is unknown, birth city, country and state, email address, and equivalent birth details for a second person in a relationship report. Report type, generated report links and order/status information are used to deliver and access the result.

Only provide another person's information if you have permission to do so. Treat a report link as private: someone with access to it may be able to read the report. The new native versions can open report links already saved on the device; they do not yet submit new report orders. For deletion requests concerning an older report, contact us with enough information to locate it, without sending payment-card details or passwords.

6. Advertising and analytics

New native iOS and Android versions: they integrate Google Mobile Ads / AdMob for banners and occasional full-screen ads. Ad requests are configured as non-personalized, publisher first-party ID is disabled, and the iOS app does not request access to the advertising identifier through a tracking prompt. Non-personalized advertising can still process IP address, approximate location, device information, ad interactions and diagnostics for delivery, measurement and fraud prevention. Google’s User Messaging Platform checks consent requirements before requesting ads and provides Ad privacy choices in You when required. Ads are suppressed while purchase ownership is being checked and for verified ad-free customers. Firebase Analytics collection remains disabled on native iOS; the native Android app does not include the Firebase Analytics SDK. Neither new native version integrates Crashlytics.

Earlier iOS and Android versions: Google Mobile Ads / AdMob is used to display advertising. AdMob can process IP address, approximate location inferred from it, device and advertising identifiers, app/ad interactions and diagnostics for ad delivery, measurement and fraud prevention. Depending on the version, device permissions and available choices, ads may be personalized. Earlier iOS code also uses Firebase Analytics to record app interactions, with app-instance/device information and related usage data.

Use the privacy choices available in your version and your device's advertising/tracking settings to control applicable processing. We do not claim that every older version has an in-app consent-management screen. See Google's advertising controls and Google's Privacy Policy. We do not sell your journal or birth profile. Advertising-related disclosures may be treated as “sharing” or targeted advertising under some privacy laws; contact us to exercise applicable rights.

7. Service providers, sharing and support

• Google / Firebase: authentication, messaging, content hosting and Cloud Functions/Firestore infrastructure; advertising or analytics in the versions identified above. See Firebase privacy and security information.
• Apple: Sign in with Apple, App Store transactions and push-notification infrastructure. See Apple's privacy information.
• Our content infrastructure: some content still comes from our existing Buzly Labs server while selected services use Firebase. HoroscopeServices supplies horoscope feeds to our backend; fetching a general horoscope feed does not require sending your journal or account profile to that supplier. Personal report submissions are separately described above.
• OpenAI: optional chart interpretations after confirmation, as described in section 1. See OpenAI’s privacy policy.
• Support: when you email us, we and our email service providers process your address, message and attachments to respond and resolve the request.

We may disclose information where required by law, to protect users and the service, or in a business transfer subject to appropriate safeguards. We do not upload your contacts to invite friends. Sharing uses the system share sheet and the destination you choose. A shared birthday, sign or fortune message can reveal the information you include; recipients and external apps handle that content under their own policies. The native share URLs do not include your account identifier or full birth date.

8. Websites and local storage

The buzhoroscopes.com website, including this privacy page, is hosted on Firebase Hosting. The hosting service processes technical request information, including IP addresses, to deliver and secure pages. These website pages add no analytics scripts, advertising or tracking cookies. Our fortune landing pages use browser local storage to remember a revealed fortune. You can clear that data in your browser settings. External store and other links are governed by their destination policies.

9. Retention, deletion and your choices

• Local information: profile, journal and saved-content data remain on the device until removed. You can delete journal entries where offered. Deleting the app, or clearing Android app storage, removes its local app data; merely offloading an iOS app does not. Device/cloud backups may retain copies under your backup settings. Removing an account does not erase your local profile or journal.
• Account deletion: in the new native iOS or Android version, open You, open your signed-in account and choose account deletion. Reauthentication may be required. If that option is unavailable or fails, email ask@buzlylabs.com to request deletion. Signing out alone does not delete the account.
• AI usage records: daily usage counters are associated with a hashed purchase identifier, not your sign-in account. Signing out or deleting your account does not automatically remove them. Contact us for applicable access or deletion requests; do not email purchase tokens or signed transaction data.
• Server records and older reports: contact us for access or deletion. Include your account email or relevant order reference, if applicable. We may need to verify your identity. Some security, transaction or legal-obligation records may need to remain after a deletion request.

We keep account information while the account is active and retain support, report and purchase-verification records for the purposes described above and any applicable legal obligations. Service providers can retain logs and backup copies for their documented retention periods after deletion. For example, Firebase describes separate retention for authentication and messaging records; deletion is not necessarily immediate across all backups. We do not promise an automatic deletion period that our systems do not implement.

10. Your privacy rights and international processing

Depending on your location, you may have rights to access, correct, delete or receive a copy of personal information, restrict or object to processing, withdraw consent, and opt out of applicable advertising-related sharing. Contact ask@buzlylabs.com. You may also complain to your local data protection authority, including Bulgaria's Commission for Personal Data Protection where applicable.

Where data-protection law requires a legal basis, we process information to provide requested services and purchases, with consent where required for optional processing, for legitimate interests such as security and responding to support, and to meet legal obligations. Withdrawing consent does not affect earlier lawful processing.

Our providers may process information outside your country, including in the United States. Applicable provider agreements and legally recognized transfer safeguards govern those transfers. We use access controls and secure connections where supported, but no storage or transmission system is completely secure.

11. Children and changes

The app is not directed to children under 13. We do not knowingly collect their personal information. If you believe a child has provided personal information, contact us so we can investigate and arrange appropriate deletion.

We will update this policy when features or data practices change, including before introducing new cloud profile, AI or advertising functionality that materially changes this description. The date above identifies the latest revision; additional notice or consent will be provided where required.

Contact

Buzly Labs Ltd.
ask@buzlylabs.com