Privacy Policy

Buz Horoscopes · Buzly Labs Ltd.
Last updated: October 18, 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), 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 version, 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. The Android version also stores 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.

The new iOS journal is not sent to an AI provider. Optional AI readings are described below; your journal and saved fortunes are not automatically included in those requests. Public celebrity information comes from our content database; viewing it does not create a public user profile.

2. Optional accounts in the new iOS version

You may use the app without creating an account. If you choose email/password, Sign in with Apple or Google Sign-In, 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 iOS app schedules 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. 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 the Android version, 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 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 native iOS update also offers new AI-generated personal readings where available, as described below. Older report links already saved on the device remain separate from these new readings. For deletion requests concerning an older report, contact us with enough information to locate it, without sending payment-card details or passwords.

Optional AI interpretations and new personal readings

When you request an AI explanation of Your Birth Chart or Your Compatibility, our Firebase backend sends calculated planetary positions and related chart information, such as whether birth time is known and the selected relationship context, to OpenAI. The chart explanation request does not send your name, raw birth date, birth city or journal. Birth details are used on your device to calculate the chart; birth-place searches use Apple's geocoding service. AI requests require your confirmation in the app. OpenAI responses are requested with storage disabled; OpenAI may still retain service or abuse-monitoring records according to its policies. See OpenAI's Privacy Policy.

New personal readings use a report-specific prompt and calculated chart information. We verify the relevant App Store transaction or supported Google Play purchase before granting paid access. Our backend stores the new personal report's generated text, product identifier, a hash identifying the transaction, a chart hash, generation status and timestamps to deliver the report and avoid charging a purchase for multiple different charts. The report record does not store the raw purchase receipt or raw birth details. Chart AI usage records use a hashed purchase identifier and daily counters for abuse and cost controls, with an expiry timestamp set to seven days. Expiry timestamps do not guarantee immediate physical deletion from all backups.

Reading histories and PDF exports are saved locally. If you choose to create a share link, we upload the selected reading text, title and included names to Firebase. Anyone with that link can read the shared content. Links use random identifiers, expire after 30 days and can be revoked using the app's deletion control. Our service also keeps sharing counters for abuse prevention. Sharing a PDF or text instead uses the system share sheet and the destination you select. Only share another person's details with their permission. To request deletion of server-stored reports, contact ask@buzlylabs.com with the relevant order reference.

6. Advertising and analytics

New native iOS version: it integrates 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 builds without Meta advertising measurement do not request tracking permission. Builds with Meta measurement present the permission request described below. 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, and there is no Crashlytics integration.

Optional Meta advertising measurement in newer iOS builds

Newer iOS builds include the Meta SDK to measure installs and app opens associated with our Facebook and Instagram advertising. After onboarding, the app requests permission through Apple App Tracking Transparency. On a fresh launch, Meta is not initialized unless permission is authorized. If you decline or tracking is restricted, we do not start this measurement. You can change permission in iOS Settings > Privacy & Security > Tracking.

With permission, Meta may receive the advertising identifier, app-instance and device information, IP address, SDK diagnostics, and activation/install events. Meta may link this information with information from its services and other companies for advertising attribution and measurement. Automatic purchase logging and automatic screen/URL metadata collection are disabled in this integration. We do not send Meta your name, email, birth details, reading text, journal entries or feedback messages. This measurement is separate from AdMob ads inside the app; removing those ads does not change your tracking permission. See Meta's Privacy Policy for its processing, retention and privacy controls. Versions without this SDK do not perform this Meta measurement.

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. The Android ad request configuration does not restrict requests to non-personalized ads. 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.
• 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

This privacy page is hosted on Firebase Hosting. The hosting service processes technical request information, including IP addresses, to deliver and secure pages. This policy page adds 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 iOS 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.
• 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 when cloud profile, AI or advertising functionality 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