PocketOracle ("we", "our", or "us"), created by Oaie Cornel-Sebastian, is committed to protecting your privacy. This policy explains what information is collected when you use the PocketOracle mobile application ("the App") and how it is used. The App is provided as a freemium service on an "as is" basis.
1. Information We Collect
1.1 Information We Do Not Collect
PocketOracle does not send your questions to us or to anyone else. All oracle answers are selected locally on your device from a built-in set of responses. If you choose to save a question to your Journal, the question text is stored only on your device (see Section 2) and is never included in analytics, crash reports, ad requests, or notifications.
The App does not use artificial intelligence (AI) or large language model (LLM) technologies, and does not send your input to any AI service for processing. The App does not require an account, and it does not access your precise location, camera, microphone, or contacts, or read your photos.
1.2 Information Collected by Third-Party Services
We do not operate our own servers. The App integrates the following third-party services, which collect data from your device as described below and in their own privacy policies:
Google Analytics for Firebase (Google) – collects usage events linked to a random app-instance identifier (not to your name or email) to help us understand how the App is used. Events include: screen views, questions asked, pages swiped, navigation chevrons tapped, language selected, edition switched (Classic, Love, and limited editions), upgrade button tapped, dialogs shown or dismissed, support opened, rewarded ads tapped and their outcome, privacy choices opened, reminder choices, notifications opened, spreads revealed, share cards opened and answers shared, the Journal opened, Journal entries saved, marked right or wrong, or deleted, Journal check-ins shown, Pro plans selected, purchases started and their outcome (completed, cancelled, or failed), and the update-required screen shown and its update button tapped. Event properties are limited to values such as the current edition, screen, swipe direction, language code, source, dialog type, ad placement, Pro plan, notification type, and outcome. The text of your questions and Journal entries is never included. Google Analytics also automatically collects the app-instance identifier, your advertising ID on Android and the identifier for vendor (IDFV) on iOS (see Section 1.4), general location derived from a masked IP address, device model and operating-system version, app-session timing, and in-app purchase events (product and price). See the Firebase Privacy Policy.
Firebase Crashlytics (Google) – collects crash reports (stack traces, the app's state at the time of the crash, device model, operating-system version, installation identifiers, and the names of the most recent analytics events) so we can diagnose and fix stability issues. See the Firebase Privacy Policy.
Firebase Remote Config and A/B Testing (Google) – used to remotely configure app behavior, such as the free question limit, the cooldown timer, rewarded-ad settings, limited editions, and the minimum required app version, and to compare different settings across groups of users. Remote Config receives your device's country and language codes, time zone, operating-system and app version, and a Firebase installation identifier. See the Firebase Privacy Policy.
Firebase Cloud Messaging (Google) – used only if you turn on news notifications (see Section 2), to send you occasional news such as new editions. The App does not register with Cloud Messaging until you turn them on. When you do, Cloud Messaging receives a Firebase installation identifier and a push registration token for your installation (on iOS, linked to the device token Apple assigns for push notifications), and the App subscribes that token to the news topic for your app language (for example "news_en"), so that you receive news in your language. Google Analytics for Firebase records when a news notification is received or opened, and which campaign it belongs to. When you turn news notifications off, the App deletes its push registration token, and no further news is delivered. See the Firebase Privacy Policy.
RevenueCat – used to manage in-app purchases and Pro status. RevenueCat receives your purchase history (products, prices, dates, and store transaction identifiers) linked to a random anonymous identifier it creates for your installation; we do not ask for your name or email address. RevenueCat also receives information about the rewarded ads you watch, linked to the same identifier, so that we can see ad and purchase revenue together: when an ad is loaded, fails to load, is shown, or is tapped, the ad network and ad unit that provided it, where in the App it was offered (for an extra answer or a Love Edition pass), and the revenue Google reports for it. We also give RevenueCat your Google Analytics app-instance identifier so that purchase events can be reported to Google Analytics. See the RevenueCat Privacy Policy.
Google Play Services – required on Android devices to deliver Firebase, Google Mobile Ads, and Google Play billing functionality. See the Google Privacy Policy.
1.3 Advertising
The free version of the App offers optional rewarded video ads: you can choose to watch an ad to unlock an extra answer or a temporary Love Edition pass. Ads are provided by Google AdMob through the Google Mobile Ads SDK. Pro users are not shown ads.
To deliver, measure, and protect ads, the Google Mobile Ads SDK collects your device's IP address (which may be used to estimate your general location), identifiers such as the Android advertising ID and app set ID and, where applicable, identifiers related to accounts signed in on your device (see Section 1.4), information about your interactions with the App and with ads (such as app launches, taps, and video views), and diagnostic information (such as app launch time, hang rate, and energy usage). The SDK may start and send this information before you choose to watch an ad, for example while the App prepares one. In the European Economic Area, the United Kingdom, and Switzerland, it does so only after you have made a choice in Google's consent message (see Section 1.5).
The App also reports these ads' load, display, tap, and revenue events to RevenueCat, as described in Section 1.2.
This information is shared with Google, which uses it under its own Privacy Policy to serve ads (including personalized ads where you have allowed them), to measure ad performance, for analytics, and to prevent fraud. Where you have allowed it, Google may also share information about ad requests with the ad technology providers listed in the consent message. Learn more in How Google uses information from sites or apps that use its services.
1.4 Device Identifiers
Android advertising ID and app set ID – on Android, the Google Mobile Ads SDK reads your device's advertising ID and app set ID, and Google Analytics for Firebase reads your advertising ID, for advertising, analytics, and fraud prevention. You can reset or delete your advertising ID at any time in your device settings (for example Settings > Privacy > Ads, or Settings > Google > Ads, depending on your device).
Apple advertising identifier (IDFA) – on iOS, the App does not ask for App Tracking Transparency permission, so neither we nor the services above can access your IDFA, and the App does not track you across apps and websites owned by other companies.
Other identifiers – Google Analytics uses an app-instance identifier and, on iOS, the identifier for vendor (IDFV); Firebase uses a Firebase installation identifier; if you turn on news notifications, Firebase Cloud Messaging uses a push registration token (and, on iOS, Apple's push device token); Crashlytics uses a crash-reporting installation identifier; and RevenueCat uses a random anonymous customer identifier. These identifiers relate to your installation of the App, not to your name or email address, and are generally replaced with new ones if you delete and reinstall the App.
1.5 Your Advertising Privacy Choices
We use Google's User Messaging Platform to ask for your choices where the law requires it. To find out whether a consent message is required where you are, the App checks with Google's User Messaging Platform when you open it; this request includes your IP address.
European Economic Area, United Kingdom, and Switzerland – the first time you choose to watch an ad, the App shows Google's consent message, where you can accept or reject the use of your data for personalized ads and other purposes and see the list of ad technology providers. Ads are only requested after you have made a choice. If you do not consent, Google may still show non-personalized or limited ads, or no ad may be available. Your choices also apply to Google Analytics for Firebase through Google's consent mode.
You can review or change your choices at any time by tapping Privacy choices at the bottom of the App's home screen. The option appears where these choices apply. On Android you can also reset or delete your advertising ID as described in Section 1.4.
2. Local Data Storage
PocketOracle stores the following data only in the App's own storage on your device. It is not sent to us or to any of the services described in Section 1:
Your selected app language
Your selected edition (Classic, Love, or a limited edition) and, if you unlocked it by watching an ad, when your Love Edition pass ends
Your free question count, the time at which your free questions reset, and the extra answers you unlocked by watching ads
Your reminder and news notification settings, the news topic your installation is subscribed to, and the time you last asked a question (used to plan reminders)
Whether the pro-feature swipe hint has already been shown to you
Your Journal, if you use it: the questions you choose to save (up to 150 characters each), the Oracle's answers, the edition, the date, and whether you marked each answer as right or wrong. The Journal keeps up to 200 entries, and you can delete any entry in the App.
The Daily Omen texts shown by the home-screen widget (the same omen for every user each day)
Google's User Messaging Platform also stores your advertising consent choices on your device.
Your device's own backup features (such as Android backup to your Google account, or iCloud and computer backups on iOS) may include this data in backups that you control. We cannot access those backups. Deleting the App removes this data from your device.
Notifications. If you turn on reminders, the App schedules local notifications on your device: reminders (daily for a week, then weekly for three weeks, after which they stop until you open the App again), a "free questions are back" alert, and Journal check-ins a week after you save a question. They are created on your device, not sent from a server, and Journal check-ins never contain your question. When you tap one, the App records which kind of notification you opened in Google Analytics, but not its text. You can turn reminders off in the App's Reminders settings or in your device settings.
News notifications. News notifications are off unless you turn them on in the App, for example with the News switch in the App's Reminders settings. Unlike reminders, they are sent by us through Firebase Cloud Messaging (Section 1.2), to everyone who turned them on in the same app language; they never contain anything about you, your questions, or your Journal. You can turn them off at any time with the same switch or in your device's notification settings.
Home-screen widget. The Daily Omen widget only displays omen text that the App saves on your device; it sends nothing off your device.
Sharing. When you share an answer, the App creates an image of the answer (it does not include your question) and hands it to your device's share sheet. Where it goes next is up to you and the app you choose; we do not receive it. If you choose "Save Image" on iOS, the image is added to your photo library; the App cannot read your photos.
3. In-App Purchases and Subscriptions
Subscription and one-time purchase transactions are processed entirely by Apple (App Store) or Google (Google Play). We do not have access to your payment information. Purchase and subscription status is managed via RevenueCat as described in Section 1.2, using an anonymous identifier rather than your name or email address.
4. How We Use Information
We use the information described above to:
understand how the App is used and improve it, for example to check that the free question limit is set appropriately (Google Analytics, Remote Config, and A/B Testing);
find and fix crashes (Crashlytics);
show the optional rewarded ads that fund the free version, measure them, and prevent ad fraud (Google Mobile Ads);
provide and restore Pro purchases, and measure purchase and ad revenue together (RevenueCat);
deliver the reminders you turn on (on your device only);
send the news notifications you turn on, and measure how many are received and opened (Firebase Cloud Messaging and Google Analytics).
We do not sell your personal information for money, and we do not use your information to send you marketing emails. Under some US state laws, making advertising identifiers available to Google for personalized ads may count as "selling" or "sharing" personal information; you can limit this by resetting or deleting your advertising ID, or by opting out of ads personalization, in your device settings (Section 1.4).
5. Legal Disclosure
We may disclose information we hold (or that is held on our behalf by third-party services):
when required by law, such as to comply with a subpoena, court order, or similar legal process;
when we believe in good faith that disclosure is necessary to protect our rights, protect your safety or the safety of others, investigate fraud, or respond to a government request;
to service providers that process data on our behalf (Google Firebase and RevenueCat) and may not use it for their own purposes;
to Google, as described in Section 1.3, which uses advertising data under its own privacy policy.
6. Data Retention
Data stored on your device (Section 2) is kept until you delete it in the App or delete the App. For data held by third-party services:
Google Analytics for Firebase – user-level and event-level data is kept for up to 14 months; aggregated reports that do not identify you may be kept longer.
Firebase Crashlytics – crash reports and their identifiers are kept for 90 days.
Firebase Remote Config – Firebase installation identifiers are kept until we ask Firebase to delete them, and are then removed within 180 days.
Firebase Cloud Messaging – your push registration token and its news topic subscription stop working when you turn news notifications off, because the App deletes the token. Firebase installation identifiers are kept as described for Remote Config.
RevenueCat – purchase records and ad events are kept as described in the RevenueCat Privacy Policy and can be deleted at our request.
7. Opt-Out Rights
You can stop all collection of information by the App at any time by uninstalling it, using the standard uninstall process on your device or via the App Store or Google Play. You can also:
review or change your advertising consent choices with Privacy choices on the App's home screen, where available (Section 1.5);
reset or delete your Android advertising ID, or opt out of ads personalization, in your device settings;
turn reminders and news notifications off in the App or in your device's notification settings.
8. Security
We take the confidentiality of your information seriously. PocketOracle is designed around data minimization — we do not operate our own servers and we do not collect question text, personal profiles, or contact details — so there is very little user data for us to hold in the first place. Data that the App sends to the third-party services described above is encrypted in transit. For the data handled by those services (Google Firebase, Google AdMob, and RevenueCat), we rely on those providers' physical, electronic, and procedural safeguards, which are described in their own privacy policies linked above.
9. Children's Privacy
PocketOracle is intended for users aged 13 and over (see our Terms & Conditions) and is not directed at children. The App's ads are not configured for child-directed treatment. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe a child has provided personal data through the App, please contact us at the address below so that we can take appropriate action.
10. Your Rights
Depending on where you live (for example in the European Economic Area, the United Kingdom, or certain US states), you may have the right to access, correct, or delete your personal data, to object to or restrict its processing, to withdraw consent at any time, and to complain to your local data protection authority.
Because the App has no accounts, the data held by our service providers is linked only to random identifiers, not to your name or email address. To ask us to delete data, email us at the address below (see Request Data Deletion). If you made a purchase, include the order number from your Google Play or App Store receipt so that we can find and delete your record at RevenueCat, including its ad events. We will also delete any Google Analytics or Crashlytics data we are able to link to you; data we cannot link to you expires as described in Section 6. For advertising data, use Privacy choices and your device's ad settings, or contact Google. You can delete the data stored on your device (Section 2) by deleting Journal entries in the App or by deleting the App.
11. Your Consent
By using the App, you consent to the processing of your information as described in this Privacy Policy, including any future amendments we publish on this page.
Where the law requires your consent, for example for personalized advertising in the European Economic Area, the United Kingdom, and Switzerland, we ask for it through Google's consent message, and you can withdraw it at any time with Privacy choices (Section 1.5).
12. Changes to This Policy
We may update this Privacy Policy from time to time. Any changes will be reflected by the "Last updated" date at the top of this page. Continued use of the App after changes constitutes acceptance of the revised policy.
13. Contact Us
If you have any questions or concerns about this Privacy Policy, please contact us at: corneloaie@gmail.com