Privacy Policy - RunAstra
Last updated: May 2, 2026
This is the English translation of the French version, which prevails in case of discrepancy.
1. Who we are
RunAstra is a mobile application dedicated to astrology, Norse runes, numerology, and oracle readings (Belline, Tarot of Marseille). It is published by:
- Publisher: Digital Memories, Lille Trade Registry (RCS) - 927 636 886
- Legal representative / Publication director: the President of Digital Memories, reachable at
runastra.contact@gmail.com
The publisher of RunAstra is the data controller within the meaning of the General Data Protection Regulation (GDPR, EU 2016/679).
2. Who is the app for?
RunAstra is intended for adult users (18 years and older). The app is neither designed nor marketed to minors. As declared in our Google Play Console listing, Google actively blocks access to accounts identified as belonging to minors.
If you are a minor, do not use RunAstra and please uninstall the app.
3. What data do we collect?
We collect only the data strictly necessary for the app to function and to display optional rewarded advertising (see section 9). We do not sell or rent your data. We share a limited set of technical data with our advertising partner Google AdMob only when you watch a rewarded ad, in accordance with the consent you grant via the advertising consent form (UMP).
3.1 Data collected at sign-up (via Google Sign-In)
When you sign up with your Google account:
| Data | Source | Purpose |
|---|---|---|
| Email address | Google OAuth | Account identification, essential service communications |
| Name (first name and/or display name) | Google OAuth | UI personalization (greetings, profile screen) |
| Google identifier (sub) | Google OAuth | Internal link with your RunAstra account (never displayed publicly) |
We receive no Google password and request no additional access to your account (no Drive, no Contacts, no Calendar).
3.2 Data you enter during onboarding
| Data | Purpose |
|---|---|
| Date of birth | Calculation of your astral profile (natal planetary positions, signs, aspects), numerology profile, and personalized readings |
| Time of birth | Calculation of ascendant and astrological houses |
| Place of birth (city, country) | Calculation of ascendant (longitude/latitude required) and resolution of native timezone |
| Birth first/last name (if different from account name) | Calculation of expression number (numerology) |
The place of birth uses Google Places autocomplete: only the characters you type transit through Google during the search, and only the city you finally select is stored in our databases.
3.3 Data generated during use
| Data | Purpose |
|---|---|
| Drawings performed (runes, oracle cards, tarot cards, positions, reversals) | Visible in your in-app history, used to generate interpretations |
| AI-generated interpretations | Stored to avoid re-charging for an interpretation already produced |
| Personal journal entries (free text, optional) | Visible only to you |
| Daily check-ins | Tracking your routine, awarding rewards (free tokens) |
| In-app purchase history (token packs) | Token balance accounting, double-credit prevention, customer support |
| Rewarded ad views (timestamp, tokens credited) | Daily quota enforcement (3 views per 24h) and fraud prevention (a single ad view can only credit once) |
3.4 Minimal technical data
- Internal RunAstra identifier (UUID): generated randomly at first connection, used to link your data internally.
- Action timestamps (account creation, last drawing, last check-in): required for daily reward windows (e.g., 1 free drawing per 24h).
3.5 Data collected only by our ad partner Google AdMob
If you watch a rewarded ad, the Google Mobile Ads SDK directly collects the following data on behalf of Google AdMob (RunAstra has no access to this data - see Google’s privacy policy):
- Android Advertising ID (AAID), a resettable and disableable identifier from your phone settings (Settings → Privacy → Ads).
- Device technical data (model, OS version, language, timezone).
- IP address (used by Google to infer your approximate country/region).
- Ad-related events (view, click, watch duration).
Sharing of this data with Google’s advertising partners (up to ~200 ad-tech ecosystem actors) depends on your choice in the advertising consent form (UMP) shown on your first use. You can update this choice anytime via the “Manage my advertising consent” button in Profile → Settings.
If you decline consent, non-personalized ads will be served (based only on app context, not your profile).
3.6 Data we do not collect
- ❌ Real-time GPS / location
- ❌ Contacts, calendar, photos, files
- ❌ Microphone, camera
- ❌ List of installed apps
- ❌ Web browsing history
- ❌ Credit card numbers (payments are entirely handled by Google Play - we receive only an opaque transaction identifier)
- ❌ Behavioral analytics (screen views, time spent, clicks)
4. Why do we collect this data? (purposes)
| Purpose | Data involved | Legal basis (GDPR art. 6) |
|---|---|---|
| Account creation and management | Email, name, identifier | Contract performance (T&Cs) - art. 6.1.b |
| Astral / numerology / readings calculation | Date, time, place of birth, birth name | Contract performance - art. 6.1.b |
| AI interpretation generation | Profile data, drawing context | Contract performance - art. 6.1.b |
| In-app purchase accounting | Google Play transaction history | Legal obligation (accounting) + legitimate interest (anti-fraud) - art. 6.1.c and 6.1.f |
| Security, fraud prevention, audit | Internal UUID, timestamps, server logs | Legitimate interest - art. 6.1.f |
| Display and measurement of rewarded ads | Android Advertising ID, device technical data, IP, ad events (collected directly by Google AdMob) | Consent (personalized ads) - art. 6.1.a, OR legitimate interest (non-personalized ads if you decline) - art. 6.1.f |
We do not use your data for automated decision-making producing legal effects. Ad display is opt-in at the view level (you choose whether to watch each rewarded ad to earn tokens) and ad targeting depends on the consent you provide via the UMP form.
5. With whom do we share your data?
We do not sell your data. The only third parties involved are technical processors (data processors within the meaning of GDPR), which act on our instructions and do not use your data for their own purposes:
| Processor | Role | Data involved | Server location |
|---|---|---|---|
| Google LLC (Google Sign-In) | OAuth authentication | Email, name, Google identifier | United States (transfer governed by EU Standard Contractual Clauses - SCCs) |
| Google LLC (Google Play Billing) | In-app payment processing | Transaction identifier (orderId), amount | United States (SCCs) |
| Google LLC (Google Play Developer API) | Server-side validation of sandbox/real purchases | OrderId, productId, purchase token | United States (SCCs) |
| Google LLC (Google Places API) | City autocomplete during onboarding | Search text being typed (never the full profile) | United States (SCCs) |
| Google LLC (Google AdMob + UMP) | Ad partner for rewarded ads and consent management platform | Android Advertising ID, device technical data, IP, ad events | United States (SCCs + EU-US Data Privacy Framework) |
| OpenRouter Inc. | AI-powered astrological interpretation generation | Reading meta-context (signs, cards, positions) - not the journal, not identity, not raw date/time | United States (SCCs) |
| Hostinger International Ltd. | Backend server hosting (VPS) | All collected data, encrypted at rest | European Union (Lithuania) |
No sharing with data brokers or social networks. Sharing with Google AdMob’s advertising partners (third-party ad networks, audience measurement services, etc.) strictly depends on your choice in the UMP consent form. The detailed list of these partners can be reviewed via the “Manage options” button in the consent form.
6. How long do we keep your data?
| Data type | Retention period |
|---|---|
| Active account (email, astral profile, drawings, journal) | As long as the account exists - deleted immediately upon deletion request |
| Google Play purchase history | 10 years (French accounting obligation - Code de commerce art. L123-22) after the transaction, in anonymized form once the account is deleted |
| Server technical logs (auth, errors) | 90-day rolling window |
| Encrypted database backups | 30-day rolling window |
7. Your rights (GDPR)
Under articles 15 to 22 of the GDPR, you have the following rights:
- Right of access: obtain a copy of all data concerning you.
- Right to rectification: correct inaccurate data (date of birth, place, etc.).
- Right to erasure (“right to be forgotten”): request deletion of your account or part of your data.
- Right to restriction of processing: temporarily freeze processing.
- Right to portability: retrieve your data in a structured, readable format (JSON).
- Right to object: object to processing based on legitimate interest.
- Right to withdraw consent at any time, without affecting the lawfulness of prior processing.
How to exercise these rights?
- Complete account deletion: use the procedure documented at https://runastra.com/account-deletion (cascade deletion of all your data, irreversible).
- Partial data deletion (journal, drawing history, etc.) without deleting the account: see https://runastra.com/data-deletion.
- All other rights (access, portability, rectification, objection): send a request to
runastra.contact@gmail.comfrom the email address associated with your account. We respond within 30 days maximum.
Complaint to the supervisory authority
If you believe your rights are not respected, you can file a complaint with your national data protection authority. For French residents:
- CNIL (Commission Nationale de l’Informatique et des Libertés)
- Site: https://www.cnil.fr/en/plaints
- Address: 3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France
8. Data security
We implement the following technical and organizational measures:
- Encryption in transit: all communications between the app and our servers go through HTTPS (TLS 1.3 via Let’s Encrypt).
- Strong authentication: no password stored on RunAstra side (Google Sign-In OAuth only). Signed and expirable JWT access tokens.
- Minimized storage: we store no banking data or passwords.
- Cascade deletion: deleting your account automatically deletes all dependent data (drawings, journal, astral profile, etc.) at the database level (FK CASCADE).
- Payment audit trail: every transaction is traced to prevent fraud and enable refunds.
- Restricted access: only the publisher has access to the production server, via SSH with private key (no password).
No information system is entirely foolproof. In case of a data breach, we will notify the CNIL within 72 hours and, if your rights may be affected, we will inform you directly.
9. Advertising and ad consent
9.1 What ads does RunAstra display?
RunAstra displays only rewarded ads served by Google AdMob. Specifically:
- Ad display is always optional: you actively tap the “Watch +15 tokens” button on the home screen to start an ad.
- No forced banners, no unwanted interstitials, no autoplay videos.
- Strict limit: 3 rewarded ads per 24 hours (reset at midnight in your local timezone).
- In exchange for fully watching an ad, you earn 15 RunAstra tokens credited to your account.
9.2 Consent Management Platform (CMP / UMP)
On first app launch in EEA / United Kingdom / Switzerland, an advertising consent form (UMP - Google’s User Messaging Platform) is displayed to allow you to freely choose:
- Consent: personalized ads (based on your Google ad profile).
- Decline: non-personalized ads (based only on app context, not your profile). The “Decline” button is positioned at the same visual level as “Consent”, in line with French CNIL requirements.
- Manage options: granular choice by purpose and by ad partner.
You can change your choice at any time via the “Manage my advertising consent” button in Profile → Settings.
9.3 Android Advertising ID
The Google Mobile Ads SDK uses your Android Advertising ID (AAID) to limit ad frequency and prevent ad fraud. This identifier is:
- Resettable anytime from your phone settings (Settings → Privacy → Ads → “Reset advertising ID”).
- Deletable from the same settings by enabling “Delete advertising ID”: the SDK then receives a null string instead of your identifier.
- Independent of your identity: it contains neither your email nor your name.
9.4 Cookies and trackers
The RunAstra mobile app does not use cookies (cookies are a web technology, not mobile). The Google Mobile Ads SDK may use technical identifiers on your device to track ad views and prevent fraud - these identifiers qualify as trackers under EU ePrivacy regulations and are subject to your consent via the UMP described in 9.2.
No third-party analytics SDK (Google Analytics, Firebase Analytics, Facebook SDK, Mixpanel, etc.) is integrated in RunAstra. The only audience measurement we use is our self-hosted Umami instance described in 9.5.
The website runastra.com may use strictly technical cookies (session, preferences). No advertising or profiling cookies.
9.5 Self-hosted audience measurement (Umami)
To understand how the app and site are used (pages viewed, screens visited, conversions), we operate a Umami v2 instance on our own server (analytics.runastra.com). No data is shared with any third party. Characteristics:
- Anonymous visitor identifier: a hash of
IP + user-agent + secret salt, recomputed every day at midnight (the salt rotates every 24 h). Consequence: it is impossible to follow a visitor across days, and the IP address is never stored in clear text. - No persistent cookie and no localStorage on your browser.
- No advanced fingerprinting, no cross-site tracking.
- Data collected: pages/screens visited, language, country (derived from IP server-side then IP discarded), web referrer, event type (CTA clicked, draw performed, token purchase, ad watched), prefixed with a virtual site identifier (
app.runastra.comfor events from the mobile app). - Retention: 13 months maximum, then automatic purge.
- Legal basis: legitimate interest (audience measurement strictly necessary to operate the service) — consent exemption under EU ePrivacy regulations and equivalent national rules.
You can disable web collection by enabling Do Not Track in your browser — Umami respects this signal and records no event about you when it is on.
10. Transfers outside the European Union
Some of our processors (Google, OpenRouter) are located in the United States. These transfers are governed by:
- The Standard Contractual Clauses (SCCs) adopted by the European Commission (decision 2021/914), which require these processors to maintain a level of protection equivalent to the GDPR.
- The EU-US Data Privacy Framework (July 2023) when the processor is certified.
You can request a copy of the current SCCs by writing to runastra.contact@gmail.com.
11. Minors
As stated in section 2, RunAstra is strictly reserved for adult users. If we discover that an account has been created by a minor, we will delete it immediately without notice.
If you are a parent or guardian and believe your child has created an account, contact us immediately at runastra.contact@gmail.com.
12. Policy changes
This policy may be modified to reflect changes in the app, processors, or regulations. Any substantial change will be notified to you:
- Either in the app, via an information screen on the next launch,
- Or by email at the address associated with your account.
The “last updated” date at the top of this page indicates the current version. Previous versions remain available on request at runastra.contact@gmail.com.
13. Applicable law and jurisdiction
This policy is governed by French law. Any dispute relating to its application falls within the jurisdiction of French courts, subject to your right, as a consumer residing in the European Union, to bring proceedings before the courts of your state of residence.
14. Contact us
For any question regarding this policy or the processing of your data:
- Email:
runastra.contact@gmail.com - Postal address: Digital Memories - 229 rue de Solferino, 59000 Lille, France
We commit to responding within 30 days maximum (often much faster).
This privacy policy is originally written in French. The French version prevails in case of discrepancy with this translation.