Auspera Privacy Policy
In short. The app has no accounts, and we operate no servers that store your personal data. Your birth date, time and place, the names of people you add, palm photos, pictures and conversations with the Oracle stay on your device. Ads are provided by Google AdMob, payments by Google Play, and install attribution and ad measurement by AppsFlyer and Google Analytics for Firebase; these services receive technical device data and a few in-app events — an ad was viewed, a subscription was bought and at what price — described in section 3, and are responsible for it under their own policies. We do not sell your personal data.
1. Who we are and what this policy covers
Auspera: Horoscope & Tarot (the “app”) is published by Alsvarel (“we”). This policy describes what data is processed when you use the app. It does not apply to third-party services, websites or apps, including those reached through links or ads in the app; they have their own policies. Questions: alsvarel.developer@gmail.com.
2. Data that stays on your device
- birth date, time and place — yours and of the people you add;
- names, relationships and photos of people;
- palm photos and the lines detected on them;
- conversations with the Oracle, tarot and rune readings, settings;
- whether a subscription is active.
This data is stored inside the app on your device and processed only there: birth charts, forecasts and the lunar calendar are calculated on the device, and the Oracle is a language model running on the device. We do not receive this data, have no access to it and cannot restore it. None of it is sent to the services described in section 3, except that a subscription was bought and at what price (sections 3.3 and 3.4). Deleting the app or its data erases it permanently. You are responsible for the security of your device — screen lock, backups and access by others.
The camera is used only when you tap to photograph your palm. The photo library is accessed through the system picker: the app receives only the photo you choose.
3. Data received by third-party services
The companies below process data as independent controllers under their own policies and are responsible for that processing.
3.1. Advertising — Google AdMob
Some readings and the detailed forecast open after a short video ad, and an ad is shown only when you tap to watch it. The Google Mobile Ads SDK, however, starts working when the app opens — also for subscribers — and loads a video as soon as a reading that opens with an ad is offered to you, so that you do not have to wait for it. It may collect the device advertising ID, IP address and approximate location derived from it, device information, ad interaction data and diagnostic data, for serving and measuring ads, analytics and fraud prevention. No ads are shown while a subscription is active. Google’s policies: policies.google.com/privacy, policies.google.com/technologies/partner-sites.
Consent is requested with Google’s consent dialog (User Messaging Platform) when the app opens, wherever the law requires it, including the European Economic Area, the United Kingdom and Switzerland. The dialog decides by itself whether it needs to ask you; your choice is stored on your device and passed to Google and to the advertising partners listed in the dialog. You can change your choice at any time in the app: Settings → Ads → Change consent. Without consent to personalized ads, ads may be shown in non-personalized form; without any consent, ads may not be shown at all.
3.2. Payments — Google Play
Subscriptions are purchased and paid for through Google Play. Payment details are processed by Google; we do not receive them. The app receives from Google Play only the subscription status and its price in your currency. When you buy a subscription, the fact of the purchase and its price are reported to AppsFlyer (section 3.3) and Google Analytics for Firebase (section 3.4); payment details are not. You can manage or cancel the subscription in Google Play; the app opens that page with the “Manage subscription” button on the subscription screen and in the settings.
3.3. Install attribution — AppsFlyer
To learn which of our ad campaigns brought the app to you, whether they bring subscribers, and to protect those campaigns from fraud, the app uses the AppsFlyer SDK. It starts when the app opens, once the consent dialog (section 3.1) has answered, and sends AppsFlyer:
- identifiers: the device advertising ID, the app set ID and an identifier AppsFlyer assigns to this installation;
- installation data: install and first-launch time, the Google Play install referrer and the installing store;
- app launches;
- three in-app events: a video ad was shown, the revenue the ad network reported for that view, and a subscription was bought — with its price, currency and the store order number;
- device information: manufacturer and model, operating system version, screen size, language and region settings, mobile carrier and network type, battery level and charging state, free storage space and readings of the motion sensors (accelerometer, gyroscope, magnetometer), which AppsFlyer uses to detect fraud;
- the IP address, from which AppsFlyer may derive your approximate location;
- your answer in the consent dialog (section 3.1), where it applies.
Apart from these three events, the app does not send AppsFlyer what you do inside the app, and never sends birth data, names, photos, readings or conversation texts. Where the consent dialog applies, the app passes your answer to AppsFlyer before AppsFlyer starts sending data. AppsFlyer’s policy: appsflyer.com/legal/privacy-policy.
3.4. Analytics — Google Analytics for Firebase
So that Google’s ad campaigns can learn which of them bring subscribers, the app includes the Google Analytics for Firebase SDK. It is switched off when the app is installed and is switched on only after the consent dialog (section 3.1) has answered. Where the dialog applies and you decline, it stays off entirely. Once on, it sends Google:
- identifiers: the device advertising ID and an identifier Firebase assigns to this installation; the Android ID is not collected;
- device information: model, operating system version, language and region settings, app version;
- the IP address, from which Google derives your approximate location (country, region, city);
- events it records by itself: the first launch, app sessions and their length, a video ad shown with the revenue reported by AdMob, and a subscription purchased through Google Play with its price and currency;
- your answer in the consent dialog, passed to Google as consent settings.
Firebase does not record which screens you open or what you do in them, and never receives birth data, names, photos, readings or conversation texts. Google’s policies: policies.google.com/privacy, firebase.google.com/support/privacy.
3.5. Oracle model download
The first time you use the Oracle, the app downloads the language model file from our file storage, hosted by Cloudflare; if it is unavailable, from a public mirror on Hugging Face. On Android the download is performed by the system download manager, so it continues while the app is in the background and is shown in the notification panel. As with any download, the server sees your IP address and standard request information. None of your data is sent.
3.6. Reporting an Oracle answer
If you report an answer, the app opens an email to our address with the question, the answer and the reason. It is sent only if you send it yourself from your email app. We use such emails to review the report and improve answers, and keep them for no longer than 24 months.
We do not sell your personal data. Under the laws of some U.S. states, personalized advertising and ad campaign measurement may be considered “sharing”; you can opt out by deleting your advertising ID in the device settings (section 7) or, where it is offered, in the consent dialog.
4. Legal bases
For users in the EEA, the UK and Switzerland: personalized ads, install attribution, analytics and ad measurement — your consent given in the consent dialog; non-personalized ads and fraud prevention — our legitimate interest in operating and securing the app; subscriptions — performance of a contract.
5. International transfers
Third-party services may process data outside your country, including in the United States, under the safeguards they apply, such as standard contractual clauses.
6. Retention
Data on your device — until you delete it. Data held by third-party services — for the periods set by their policies. Report emails — no longer than 24 months.
7. Your rights
Depending on where you live, you may have the right to access, correct, delete, restrict, object to and port your data, to withdraw consent and to lodge a complaint with a supervisory authority. We keep no servers with your data, so you can view, change and delete it directly in the app. Rights over data held by third-party services are exercised through their tools; if you need help, contact us and we will respond within the time required by law.
You can reset or delete your advertising ID in Android settings: Privacy → Ads. Deleting it stops advertising, install attribution and analytics from using it; the identifiers AppsFlyer and Firebase assign to the installation are reset when you delete the app or its data. Where the consent dialog applies, you can withdraw or change your consent in the app: Settings → Ads → Change consent.
8. Children
The app is intended for users over 18. We do not knowingly collect data from children. If you believe a child has provided us with data, contact us and we will delete it.
9. Security
We take reasonable measures for the app to handle data securely. However, no method of storage or transmission is completely secure, and we cannot guarantee absolute security. We are not responsible for access to data on your device by third parties who gain access to the device itself.
10. Changes
We may update this policy. A new version is published on this page with a new date; we will announce significant changes in the app. By continuing to use the app after changes take effect, you accept the new version.
11. Contact
Alsvarel · alsvarel.developer@gmail.com
Version history
- 1.3, October 21, 2026 — the app’s name in Google Play is now “Auspera: Horoscope & Tarot” (previously “Auspera: Tarot & Astrology”). Nothing else has changed.
- 1.2, October 14, 2026 — the app reports to AppsFlyer that a video ad was shown, the revenue reported for it and that a subscription was bought, with its price; Google Analytics for Firebase added (section 3.4); AppsFlyer and Firebase start only after the consent dialog has answered.
- 1.1, September 30, 2026 — the data sent to AppsFlyer is listed in full; Google Firebase removed, as the app does not use it; clarified that the ad SDK starts when the app opens; where consent can be changed in the app; how to manage the subscription; where the Oracle model is downloaded from.
- 1.0, September 11, 2026 — first version.