Skip to content
Lunoriaby Luma
  • About
  • Features
  • Privacy Policy
  • Terms of Service
  • Subscription Terms
Get Lunoria (Google Play)
⚠ Two specific operational facts below are still being confirmed, not the whole document. The open items are narrow and named explicitly where they occur (see the highlighted box below): the exact hosting region for our Supabase project, and the final signature status of our Data Processing Agreements. Everything else in this Policy describes the Application's actual, current behavior.

Privacy Policy — Lunoria

English version 1.11 · Published: 2026-11-17 · Effective: changes concerning Lunoria's memory and the consent record — from installing the Application update that introduces them; all other changes — from 2026-12-17 (Section 11) · Applies to the Lunoria application (web/PWA + iOS/Android) · Available languages: polski, Deutsch, français, español (see "Language of this Policy" in Section 13 below).

Table of contents

  1. Data controller
  2. What Lunoria is
  3. Lunoria's memory (Section 2a)
  4. What data we process
  5. AI transparency
  6. Automated decision-making
  7. Recipients and sub-processors
  8. How long we keep your data
  9. Your rights (how to exercise them)
  10. Minimum age
  11. Data security
  12. Changes to this Policy
  13. Contact
  14. Language of this Policy
  15. California and other US state privacy rights (US residents only)
  16. Australia — your Privacy Act rights (Australian residents only)
  17. Quebec, Canada — Privacy Officer and Governance (Quebec residents only)

1. Who is the controller of your data

The controller of personal data within the meaning of Article 4(7) GDPR is:

LUMA Sp. z o.o. (full name: LUMA Spółka z ograniczoną odpowiedzialnością, a Polish limited liability company)
registered office in Warsaw, ul. Gawronia 15, 04-785 Warsaw, Poland
entered in the National Court Register (KRS) under number: 0001244636
Tax Identification Number (NIP): 9522285489, National Business Registry Number (REGON): 544875680
contact email for data-protection matters: support@lumasoft.pl

If we appoint a Data Protection Officer (DPO), their contact details will be published here. Until then, contact us for data-protection matters directly at the address above.

2. What Lunoria is (processing context)

Lunoria is a conversational entertainment application — an AI astrologer, tarot reader, and numerologist. Lunoria is for entertainment purposes only and does not replace medical, financial, legal, or psychological advice. Content (horoscopes, tarot readings, numerology, chat responses) is generated by an artificial intelligence model based on information you provide.

Local-first architecture, as a matter of technical fact. Your birth data (date, and optionally time and place of birth) and the content of your conversations with Lunoria are stored only on your device (in your browser's/app's storage) and are not saved in our database. Your place of birth never leaves your device at all — the Application does not send it to us or to the AI model provider. When you have a conversation or request a reading, its content and your date of birth (and, for a birth-chart reading, your time of birth, if you provided it) are transmitted in real time through our intermediary (stateless proxy) server solely to pass them to the AI model and return the response to you — our server does not store the content of that conversation or your birth data. The AI model provider (Anthropic, USA) processes this data under a data processing agreement (DPA) and the cross-border transfer mechanism described in Section 6, and may retain it for up to 30 days on its own servers for safety/legal-compliance purposes (except content flagged by the provider's safety systems — up to 2 years, Section 7); we do not currently rely on a confirmed Zero Data Retention arrangement.

Precision of wording: we do not claim that "your data never reaches any server" — that would not be accurate. The correct statement is: we do not store your data on our servers; content is processed in transit by the AI model provider in order to generate a response.

Daily horoscope notifications — the same local architecture. If you enable the daily horoscope reminder in Settings, the schedule for that notification (the date and time it is shown) is planned and stored only on your device, using the native mechanism of the operating system (iOS/Android) — we do not use any external push-transmission service (we do not register your device with Firebase Cloud Messaging, the Apple Push Notification service, or the Expo Push Service), and we do not generate any device token associated with this feature. The notification's content is generic and identical for all users of a given language (e.g., "Your horoscope for today is ready") — it does not include your zodiac sign or any other personalized content, partly so that it remains uninformative to anyone glancing at your phone's lock screen. Luma does not know on which device this feature is enabled, or which zodiac sign is associated with it — the only information that reaches us in connection with this feature is the single timestamp described in Section 3 below, used solely to measure the feature's effectiveness.

Note on special categories of data (Article 9 GDPR / equivalent US and Australian concepts of sensitive information). A request for a horoscope, tarot reading, or numerology analysis, by itself, is not treated as revealing "religious or philosophical beliefs" within the meaning of Article 9 GDPR. However, free-form conversation with Lunoria may incidentally reveal sensitive information (e.g., about health, sexual orientation, or beliefs) — the local-first architecture minimizes this risk at the source (no persistent storage on our side), but does not eliminate in-transit processing by the AI model provider. This qualification is confirmed for the EU/GDPR framing in this Section, and separately for US law (California's statutory definition of "sensitive personal information") in Section 14 below. This assessment applies equally to the content of the push notifications described above, for the same reasons (generic content, independent of zodiac sign, with no diagnostic or evaluative element).

2a. Lunoria's memory

Lunoria can remember things from your earlier conversations and readings, so that its replies stay consistent over time. This is how it works.

What is saved

  • Summaries and notes from conversations. After a few exchanges of messages, the Application asks the AI model to write a short summary of the conversation and a list of short facts ("notes") extracted from it. The notes are written by the model, not by you, so they may be incomplete or inaccurate.
  • Entries from readings. For tarot and numerology readings, the memory holds a short entry such as the cards drawn (with orientation) and the type of spread, or your Life Path number. These entries do not include the text of your question, the text of the reading, or your birth data.
  • Notes about other people and sensitive information. Notes extracted from a free-form conversation may concern other people (e.g., a family member or a partner you mentioned) and may include information of a sensitive nature (e.g., about health or beliefs) if you wrote about it in the chat. Please keep this in mind when writing about other people or about sensitive matters. See also the note on special categories of data in Section 2.

Where it is stored

The memory is stored only on your device, in encrypted local storage, as part of the Application's local data (it is also included in the "Export data" file). It is not saved in our database.

What is sent, and to whom

With every reply, the Application sends the notes and your most recent messages, together with your new message, through our generate-reading server function to the AI model provider (Anthropic, USA — Section 6). Our function passes this content on only in order to produce the reply and does not store it. Anthropic may retain it for up to 30 days, as described in Sections 2, 6 and 7 (except content flagged by the provider's safety systems — up to 2 years, Section 7); we do not currently rely on a confirmed Zero Data Retention arrangement. Creating a summary is a separate call to the AI model, subject to a monthly limit that depends on your plan; when the limit is reached, no new summary is created.

How to view and delete it

You can review the notes in the Application and delete them:

  • "Forget this" removes one note. Later summaries will not recreate it: the summaries that held the note are cleared, and the messages of the conversation it came from are no longer sent to the model for memory purposes. Because the model writes notes in its own words, in rare cases a differently worded note about the same matter could still appear — you can then delete it as well.
  • "Forget everything" deletes the entire memory: all summaries and notes. Messages from before that moment are not used to build new memory.
  • In both cases your conversations remain in History and stay visible to you. To delete them, use "Clear all history" (which also removes the memory) or "Delete account" (Section 8).
What deletion does not undo. Deleting memory (and history) takes effect on your device. It does not recall content that has already been sent to the AI model provider with an earlier reply — the provider may retain that content for the period described above (up to 30 days, except content flagged by the provider's safety systems — up to 2 years, Section 7), and we have no means of deleting it earlier.

3. What data we process, for what purpose, and on what legal basis

Category of data Examples Purpose of processing Legal basis (GDPR)
Account identifier (initially an anonymous session) A non-meaningful, randomly generated technical identifier (UUID) assigned by Supabase Auth on first launch of the Application (the signInAnonymously() function) — created without registration, a password, or providing an email address. Lunoria does not offer password- or email-based registration. The only form of sign-in is optionally linking this identifier to an Apple account (Sign in with Apple — on iOS) or to a Google account (on Android and in the web version) — the data we receive in that case is described in the "Data from your Apple or Google account" row below. The same identifier is used as the customer identifier in RevenueCat and as the user identifier in Sentry reports (Section 6). Until you link it to an Apple or Google account, we do not connect it with any information identifying you as a person; once linked, it is associated on our side with that account's email address. Enforcing monthly plan limits, linking subscription/entitlement status to your device Article 6(1)(b) GDPR — performance of a contract
Data from your Apple or Google account (optional sign-in) If you link your account in the Application to an Apple or Google account, Supabase Auth stores the data that provider passes in its identity token: your email address (with Sign in with Apple, this may be an Apple relay address if you chose to hide your email) and your account identifier at that provider ("sub"), and, for Google, additionally your name (display name) and the URL of your profile photo from your Google profile. The Application does not send to our server the name Apple may share at your first sign-in. We never receive the password to your Apple or Google account Maintaining your account in the Application linked to your Apple or Google account (sign-in), restoring access to that account and its entitlements (e.g., after reinstalling or on a new device), handling your enquiries and requests, including GDPR requests (Section 8). We do not send marketing to this address Article 6(1)(b) GDPR — performance of a contract (the sign-in you request)
Hashed Apple or Google account identifier (welcome-window anti-farming mechanism) SHA-256 of your Apple or Google account identifier ("sub") with a separate, secret salt, together with a marker of the provider (Apple/Google) — never the raw identifier, email address, name, or any other information about your account Preventing the same Apple or Google account from claiming the free, 7-day welcome window more than once — including after deleting your account in the Application and reinstalling it. Never used to recognize you, for profiling, advertising, or any other purpose Article 6(1)(f) GDPR — our legitimate interest in protecting the one-time nature of this promotion against abuse
Furthest onboarding step reached, and its timestamp A screen label from a closed list of five values (the profiles.onboarding_furthest_step column: "welcome", "language", "age_gate", "disclosure", or "birth_data"), together with its timestamp (onboarding_furthest_step_at), set automatically the moment you successfully complete that screen. The value is monotonic — it never moves backward, no matter how many times you return to an earlier screen. We never record anything you type on any of these screens — not your date of birth, not your chosen language as personal data, nothing beyond the screen's name itself. Diagnosing exactly which onboarding screen users most often abandon the Application on, so we can fix that specific screen (for example, the age gate or the birth-data form) instead of guessing where the problem actually lies Article 6(1)(f) GDPR — our legitimate interest in improving the effectiveness and usability of the registration process, in the same category as the diagnostic data described above (IP addresses / technical logs, Sentry — Section 3 above)
Email address provided for a web-channel purchase An email address provided when purchasing a subscription on lunoria.lumasoft.pl — solely for the payment processor's needs Issuing a payment confirmation/receipt through the payment processor (Stripe); this does not create an account in the Application — see the sub-processor table in Section 6 Article 6(1)(b); accounting records — Article 6(1)(c)
Birth data Date of birth and, optionally, time of birth — sent to the AI model provider (Anthropic) when a reading is generated; optional place of birth — stored only on your device and never sent Astrological/numerological calculations necessary to generate a reading Article 6(1)(b) — processed in transit, not stored server-side (Section 2)
Content of your conversation with Lunoria Chat messages, questions, AI responses Generating a response; potentially Article 9(2)(a), when content incidentally reveals sensitive information (Section 2) Article 6(1)(b), combined with Article 9(2)(a) where applicable. In the Application update that introduces the memory (Section 2a), the Application asks for your separate, explicit consent before your first conversation or first reading with your own text. You can withdraw this consent at any time in Settings; withdrawal does not affect the lawfulness of processing carried out before it (Article 7(3) GDPR)
Consent record for AI text processing and memory Account identifier, consent type (AI text processing or memory), decision (granted, declined or withdrawn; on withdrawal, also your choice whether to delete the data from your device), version and cryptographic hash of the consent text shown, language, Application version, platform, the place in the Application where the decision was made, the time of the decision and the time our server received the record. No IP address and no conversation content. Demonstrating that and when you gave, declined or withdrew consent, and to which text (accountability obligation); defence against legal claims Article 6(1)(c) GDPR in conjunction with Article 7(1) and Article 5(2) GDPR (obligation to demonstrate consent) — for the current state of consent; Article 6(1)(f) GDPR — our legitimate interest in defending against legal claims (Article 82 GDPR) — for earlier entries kept for 3 years (Section 7)
Payment data Subscription status, transaction history (RevenueCat/Stripe/Apple/Google) Managing Plus/Premium subscriptions and top-up purchases Article 6(1)(b); accounting records — Article 6(1)(c)
Content reports (trust & safety) The quoted excerpt of an AI message you reported (the "Report" button) and the reason for the report Handling reports of inappropriate AI-generated content (a requirement of Google Play's and Apple's App Store policies on content moderation — App Review Guideline 1.2), moderation, abuse prevention Article 6(1)(f) — legitimate interest (ensuring the safety and quality of AI-generated content, meeting app-store requirements on moderating generative content, preventing abuse)
IP addresses / technical infrastructure logs (Supabase/hosting) IP address, request timestamp, user agent — generated automatically by the hosting infrastructure while handling requests Security, abuse prevention, detecting and countering attacks Article 6(1)(f) — legitimate interest (infrastructure security)
Diagnostic / telemetry data (Sentry) Error and crash reports (including native crashes) and performance data (app start-up time, frame rendering smoothness, interface stalls); device model, operating system version, Application version, language/locale; the name of the current and previous screen of the Application (the route name only, no content); an approximate location (country/city) that Sentry derives from your device's IP address; the account identifier (UUID — the same as in the "Account identifier" row; if you have linked your account to Apple or Google, it is associated on our side with that account's email address, so it is not anonymous); and, for errors reading from local device storage, the name of the storage and the type of operation Detecting, diagnosing, and fixing technical crashes; monitoring performance; keeping the Application stable Article 6(1)(f) — legitimate interest (Application security and stability, on the same footing as the infrastructure technical logs above)
Subscription event log (RevenueCat event log) Event identifier, event type, store (App Store/Google Play/Stripe Web Billing), app_user_id Payment reconciliation, subscription auditing, fraud/abuse detection Article 6(1)(b)/(f)
Repeated-AI-response marker (quality diagnostics) Only when a generated chat reply is identical to Lunoria's previous reply in the same conversation: the fact that this happened, a cryptographic hash (SHA-256) of that reply, the name of the AI model used, and the account identifier. We never record the content of the reply or of your message Detecting and fixing a quality defect in which the same reply is repeated Article 6(1)(f) GDPR — the controller's legitimate interest in the service working correctly
Push notification consent and its timestamp A single timestamp (the profiles.local_reminder_enabled_at column), recorded once — the moment your device schedules the local, daily horoscope reminder — and never overwritten afterwards. We do not record whether the notification was displayed or tapped. The notification's own schedule and content remain only on your device (Section 2) and are never sent to us. Demonstrating that you gave consent to this feature (consent record, Article 7(1) GDPR); solely measuring the effectiveness of this product feature (whether the reminder increases next-day return to the Application) — not profiling, not content personalization, and no marketing beyond the notification itself Article 6(1)(a) GDPR, together with Article 398 of the Polish Law on Electronic Communications (your consent to communications sent to a telecommunications end-device) — for the reminder feature itself; Article 6(1)(f) GDPR — our legitimate interest in demonstrating consent and measuring the feature's effectiveness, as regards the timestamp itself
Product events (measuring how the Application is used) An event from a closed list of 11 types (e.g., a feature opened, a chat session started, a paywall screen viewed, a widget added), together with the day it occurred (no hour/minute), the platform, and the Application version. We never record the content of your questions, answers, cards, birth data, or any other conversation content. Events may be temporarily buffered locally on your device (e.g., while offline) and sent later. We also record the date consent was given and, if applicable, the date it was withdrawn, as a record of consent (Article 7(1) GDPR). Measuring whether and how you return to the Application (D1/D7/D30 retention), which source you came from, which features you use, and at what stage you abandon a purchase — solely to improve the product Article 6(1)(a) GDPR — your consent (together with Article 5(3) of the ePrivacy Directive, as implemented in local law, for storing and accessing information on your device). Consent is optional and off by default; you can withdraw it at any time in Settings → "App usage measurement" — with no effect on the availability of other features and with no effect on the lawfulness of processing carried out before withdrawal

4. AI transparency (EU AI Act, Article 50; US B.O.T. Act)

Lunoria displays a persistent, visible message informing you that you are talking to an artificial-intelligence system, not a human, in every chat session and with every generated reading (horoscope, tarot, numerology). This satisfies both the EU AI Act (Regulation (EU) 2024/1689, Article 50) and, for users in California, the "B.O.T. Act" (Cal. Bus. & Prof. Code §§ 17940–17943) — see the Terms of Service, Section 8, for the exact places this disclosure appears in the Application. AI-generated content may contain errors or inaccuracies.

5. Automated decision-making

Lunoria's readings and responses are generated by an artificial intelligence model (Anthropic Claude). This is not an automated decision producing legal or similarly significant effects within the meaning of Article 22 GDPR — the content is for entertainment purposes only, and any life decisions are made solely by you, at your own responsibility.

6. Who we share data with — recipients, sub-processors, and independent controllers

We work with trusted providers. Most of them act as processors within the meaning of Article 28 GDPR, with whom we have entered into, or will enter into, data processing agreements (DPAs). Apple and Google are the exception — for native-channel subscription billing (in-app purchases) and for sign-in with an Apple or Google account, they act as independent data controllers (Article 4(7) GDPR) — they are not our processors, and processing of transactional data takes place under their own privacy policies and their own controller responsibility. Each entity's role is indicated in the "Role" column below:

Entity Role Location / region Cross-border transfer mechanism (outside the EEA)
Supabase Processor (Article 28 GDPR). Managing technical accounts (Auth, without passwords) — anonymous, or linked to an Apple or Google account; in the latter case Supabase Auth stores the email address of that account, and for Google also the name and profile-photo URL (Section 3) — as well as subscription limit/entitlement state and the other data described in Section 3. Lunoria's Supabase project has no content tables — it does not store birth data or conversation content (except for the excerpt of an AI message you report yourself using the "Report" button). EU (region to be confirmed with the final project configuration — recommendation: Frankfurt/eu-central-1, consistent with Luma's other products) SCC in the agreement with Supabase, where sub-processors outside the EEA are used
Anthropic (Claude) Processor (Article 28 GDPR). Generating chat responses, horoscopes, tarot readings, and numerology analyses based on content sent through our stateless proxy — the only AI provider processing your data in real time USA Standard Contractual Clauses (SCC, Module 2/3, Decision 2021/914); a data processing agreement (DPA) is being finalized — the status of EU-US Data Privacy Framework (DPF) certification is to be confirmed at source (no unambiguous confirmation of formal certification was found). Anthropic's default retention: up to 30 days, absent a separate Zero Data Retention agreement, except content flagged by the provider's safety systems — up to 2 years (Section 7). For US users, this same relationship is additionally addressed by California's sensitive-personal-information framework in Section 14.
RevenueCat Processor (Article 28 GDPR). Subscription management, synchronization of Plus/Premium entitlements USA (global infrastructure) SCC / DPF, where applicable
Stripe Processor (Article 28 GDPR). Card payment processing (web billing, RevenueCat Web Billing) USA / Ireland (Stripe Payments Europe) SCC for transfers to the USA, where applicable
Apple / Google Independent data controller (Article 4(7) GDPR) — NOT a processor. Native-channel subscription billing (in-app purchases), under the relevant store's own rules; Apple/Google independently decide the purposes and means of processing transactional data and bear their own controller responsibility for it. In the same role, Apple (Sign in with Apple) and Google (Google sign-in) authenticate you if you choose to sign in, and pass us the data described in Section 3 (the "Data from your Apple or Google account" row). Global (Apple/Google) Per Apple's/Google's own privacy policies as independent controllers
Microsoft (Microsoft 365 / Microsoft Graph API) Processor (Article 28 GDPR) — infrastructure deployed, currently inactive. Technical backend for sending transactional emails related to a possible, optional email-login mechanism (confirmation, login link, password reset) from no-reply@lumasoft.pl is deployed (Supabase Auth "Send Email Hook"), but the Application does not currently offer registration, a password, or email login — it operates only on technical sessions, optionally linked to an Apple or Google account (Section 3), so this mechanism is not currently triggered by any feature of the Application, and no email address of yours currently reaches Microsoft this way. If we offer such an optional feature in the future, this Policy will be updated before it launches. Microsoft 365 infrastructure (tenant region to be confirmed — EU/global) SCC / DPF, where a transfer outside the EEA applies
Sentry (Functional Software, Inc.) Processor (Article 28 GDPR). Crash diagnostics, performance monitoring, and keeping the Application stable — automatic reporting of technical errors and performance data. Categories of data processed: device model, operating system version, Application version, language/locale, the name of the current and previous screen of the Application, performance data (start-up time, frame rendering smoothness, interface stalls), an approximate location (country/city) that Sentry derives from the IP address, the account identifier (UUID — once your account is linked to Apple or Google, associated on our side with its email address, Section 3), and, for errors reading from local device storage, the name of the storage and the type of operation. The content of your conversations with Lunoria and your birth data are not sent to Sentry — the Application is configured not to send full personal data and to strip request bodies, parameters, and any authentication tokens from every report before it is sent. Legal basis: Article 6(1)(f) GDPR — the controller's legitimate interest in keeping the Application stable, secure, and quick to repair when it fails, on the same footing as the infrastructure technical logs in Section 3. EU (Germany) — Sentry's organization operates in the EU region, with its event ingestion point in Germany Not applicable — processing takes place entirely within the EU, with no transfer outside the EEA
Note on developer tooling (additional transparency): in producing the Application's graphic assets (icons, backgrounds, illustrations), we used Google's image generation model (Gemini/Google Generative Language API). This tool is used only at the stage of producing the app's graphic materials, before the Application is made available to users, and never processes Lunoria users' personal data — it is not a sub-processor within the meaning of Article 28 GDPR with respect to your data and is therefore not listed in the table above.

We do not sell your personal information to any third party, and we do not disclose it for marketing purposes without your consent. For US consumers, see the more specific "we do not sell or share" statement in Section 14.

To be confirmed before publication (unresolved operational facts, not legal opinion): the status of signed DPAs with Supabase, Anthropic (including Zero Data Retention status and EU-US Data Privacy Framework certification status — no unambiguous confirmation of Anthropic's formal certification was found), RevenueCat, Stripe, Sentry, and Microsoft (Graph API / Microsoft 365 — a DPA is needed before any email-login mechanism is activated, see the table above); the exact processing region for Supabase and for the Microsoft 365 tenant.
Crash reporting and technical diagnostics: Sentry. The Application uses Sentry (Functional Software, Inc.) to automatically detect and diagnose technical crashes and keep the Application stable — the categories of data processed, the processing region, and the legal basis are set out in the table above. Sentry does not receive the content of your conversations with Lunoria, your birth data, or any other content you type in the chat.

7. How long we keep your data

Category of data Retention period Justification
Birth data / conversation content Not stored server-side by Luma (lives locally on your device, at your discretion) Local-first architecture (Section 2)
The same data on Anthropic's side (in transit) Prompts and responses are deleted within 30 days, without Zero Data Retention. Exceptions: if Anthropic's automated safety systems flag content as violating its Usage Policy, Anthropic may retain that content for up to 2 years and the safety classification results for up to 7 years; it may also retain content longer where required by law Anthropic's retention policy for safety/legal-compliance purposes
Account identifier / limit and entitlement state For as long as the Application is actively used on a given device. Usage records for the message limit and for deep readings are deleted after 48 hours (an anti-duplication window and the daily deep-reading limit, not an audit log); unused top-ups (Visions) do not expire with time — the balance stays with the account until used, is forfeited when the subscription ends under the Subscription Terms (clause 3.4) and is deleted together with the account. A record of a Vision forfeiture (the number of Visions and dates, with no conversation or reading content) is kept until the account is deleted, as a billing record. You can also delete the session identifier immediately and yourself, at any time — using the "Delete account" feature described in Section 8 below. The same applies to the furthest onboarding step reached and its timestamp (Section 3), to the push notification consent timestamp (Section 3), and to repeated-AI-response markers (Section 3) — all of them live only alongside the account and are deleted together with it via "Delete account" Performance of a contract (Article 6(1)(b) GDPR); repeated-AI-response markers — Article 6(1)(f) GDPR
Data from your Apple or Google account (email address; for Google also name and profile-photo URL) Until the account is deleted — erased immediately together with the account via "Delete account" (Section 8) Performance of a contract (Article 6(1)(b) GDPR) — providing sign-in
Hashed Apple or Google account identifier (welcome-window anti-farming) For as long as the welcome-window mechanism exists as a feature of the Application, reviewed for continued justification at least once a year — deliberately retained even after account deletion (see Section 8). If the welcome-window mechanism is discontinued or replaced by another solution, this entire data set will be deleted This narrow purpose — preventing a second, free window for the same identity — does not lapse when an account is deleted; account deletion is precisely the situation this mechanism protects against
Consent record for AI text processing and memory Current state of consent (the latest entry of each type) — until the account is deleted; earlier entries replaced by a newer one — 3 years from when they were recorded; all entries are deleted together with the account using the "Delete account" function Demonstrating consent for as long as it applies (Article 7(1) GDPR); defence against legal claims (Article 82 GDPR) for the duration of the limitation period
Billing data 7 years Tax and accounting obligations (Article 6(1)(c) GDPR)
Content reports (trust & safety) Until the report is resolved, plus 12 months from its resolution; a report that is never resolved is deleted no later than 12 months after it was submitted. Deletion is automatic, as part of a daily database clean-up job. Reports are also erased immediately together with the account via "Delete account" Time needed for moderation, and an evidentiary period in case of an appeal against a moderation decision or a dispute about reported content
IP addresses / technical infrastructure logs Per the hosting provider's default policy — to be confirmed, typically 30–90 days Security, abuse prevention (Article 6(1)(f) GDPR)
Diagnostic / telemetry data (Sentry) Per Sentry's default retention policy for the plan we use — the exact period is to be confirmed with the provider before this entry's draft status is fully lifted. We deliberately do not state a number of days here until it is expressly confirmed in the provider's configuration/agreement Application security and stability, crash diagnostics (Article 6(1)(f) GDPR)
Subscription event log (RevenueCat event log) 30 days Payment reconciliation and subscription auditing
Product events Until consent is withdrawn, or a maximum of 13 months; events are deleted promptly after consent is withdrawn or the account is deleted Consent (Article 6(1)(a) GDPR) — a period consistent with standard app-usage-measurement practice; you can withdraw consent at any time in Settings → "App usage measurement"

Because conversation content, reading history, and Lunoria's memory (Section 2a) are not stored on our side (local-first architecture, Section 2), you can delete them yourself by clearing your device's/browser's local storage — the "Clear all history" feature in the Application's Settings, available immediately and without any request to us (it deletes conversations, reading history, and the memory together). To delete only the memory, use "Forget this" (one note) or "Forget everything" (the whole memory) — conversations then stay in History. Deleting locally does not recall content already sent to the AI model provider, which may retain it for up to 30 days (Section 2a; except content flagged by the provider's safety systems — up to 2 years, table above). The "Clear all history" feature deliberately does not delete your birth data or your session identifier on our side — that is what the "Delete account" feature is for (both features are described in full in Section 8 below).

Content reports you have submitted are kept for the period shown in the retention table above under Article 17(3)(e) GDPR (establishment, exercise, or defence of legal claims, and the integrity of the moderation process) — after that period they are deleted automatically.

8. Your rights

Under GDPR, you have the rights listed below. How they are exercised depends on whether you use the Application only with an anonymous technical session or have linked your account to an Apple or Google account — we explain this directly below.

How we identify you when you make a request (Articles 11 and 12(6) GDPR). Lunoria does not collect a password. If you have linked your account in the Application to an Apple or Google account, we keep that account's email address (Section 3) and can use it to locate the data linked to your account — write to us from that address or state it in your message (for a hidden Apple address, the relay address shown in your Apple account settings). If we have reasonable doubts about your identity, we may ask for additional confirmation (Article 12(6) GDPR). If you use the Application only with an anonymous session (not linked to Apple or Google), we do not keep an email address, name, or any other identifier that would let us link that session to a specific, identified person (the sole exception: an email address given to the payment processor when you purchase in the web channel — Sections 3 and 6). In that case, under Article 11 GDPR, if we receive an email requesting the rights described in Articles 15–20 GDPR, we are generally unable to verify which session or which specific data the request concerns — not because we refuse to act on it, but because the Application's architecture deliberately does not create such a link (local-first, Section 2). If you nevertheless want to exercise these rights with respect to data linked to your session, describe the circumstances in your email as precisely as possible (e.g., the approximate date and content of a content report you submitted) — we will handle the request to the extent we are able to locate the corresponding data, using the additional information you provide for identification purposes (Article 11(2) GDPR). Either way, the "Export data" and "Delete account" features described below work inside the Application without contacting us.
  • Access to data (Article 15) — on our side we keep, for your account: the account identifier (UUID); if you have linked your account to Apple or Google, that account's email address, and for Google also your name and profile-photo URL; subscription limit/entitlement state and subscription dates; the furthest onboarding step reached and its timestamp (onboarding_furthest_step); the daily horoscope reminder timestamp (local_reminder_enabled_at); the subscription event log (revenuecat_event_log, 30 days); product events — only if you consented to them; repeated-AI-response markers; the hashed Apple or Google account identifier; and any content reports you submitted (Section 3). The "Export data" feature described below adds to the file — alongside the data from your device — a copy of the data stored for your account in our database (an internet connection is required; the number of exports per day is limited). The email address, name, and profile-photo URL from your Apple or Google account are not currently part of that file — we will provide a copy on request sent to the address below. The data that actually defines your experience in the Application (birth data, reading and conversation history) is exclusively in your possession — on your device — and is also included in that file.
  • Rectification of data (Article 16) — you correct your birth data and settings directly in the Application. Your email address, name, and profile photo come from your Apple or Google account and are managed with that provider; if you want us to correct them on our side, write to us. We do not keep any other personal data on our side that would require correction.
  • Erasure of data / the "right to be forgotten" (Article 17) — full description below.

How to delete your data (Lunoria has no password registration — only a technical account, optionally linked to Apple or Google, and local data)

Lunoria does not offer registration or a password-based login, so there is no traditional "account" in that sense. In the Application's Settings, the feature named "Delete account" (in the "Danger zone" section) refers to the technical account described in Sections 3 and 7 — anonymous, or linked to an Apple or Google account. Here is a full breakdown of what you delete, and how:

  1. Conversation content, reading history, and Lunoria's memory — 100% local, on your device: Settings → "Privacy and Security" → "Clear all history" → confirm. Deletion is immediate, carried out entirely on your device, and does not require any request to us — this data was never permanently stored on our side (Section 2). This feature deliberately does not delete your birth data or your session identifier on our side — see the account-deletion item below for that.
  2. Only Lunoria's memory (Section 2a): in the Application's memory list, "Forget this" deletes one note (later summaries will not recreate it) and "Forget everything" deletes the entire memory. In both cases your conversations remain in History — to delete them, use "Clear all history" (above). These deletions are local and immediate. They do not recall content already sent to the AI model provider with earlier replies, which the provider may retain for up to 30 days (except content flagged by the provider's safety systems — up to 2 years; Sections 2a and 7).
  3. Birth data, the account identifier, and the data linked to it on our side (including data from your Apple or Google account) — account deletion: Settings → "Danger zone" → "Delete account" → check the box confirming you understand the operation is irreversible → confirm. Deletion is immediate and fully self-service — it does not require any request to us. The operation permanently erases your account identifier from our servers, together with the related subscription limit/entitlement state, the other data stored for the account (Section 3), and any content report you submitted (Sections 6 and 7) — and, if the account was linked to Apple or Google, also the stored email address, name, and profile-photo URL — and additionally deletes your birth data, nickname, and full conversation and reading history from your device, then immediately signs you out. One exception: if you signed in with an Apple or Google account, a hashed marker of that account remains on our servers — solely for the purpose described in Section 3 (preventing the same Apple or Google account from claiming the welcome window again), never your email address, name, or any other information about that account. If the operation fails, try again shortly or write to support@lumasoft.pl.
  4. Billing data held by the payment processor (Stripe in the web channel; Apple/Google in the native channel) — these entities process transactional data as an independent controller (Apple/Google) or a processor (Stripe), under their own policies (Section 6); in the web channel, we will forward your request at your request to the address above.
Deleting your account does not cancel your subscription. If you have an active paid Plus/Premium subscription, deleting your account does not end it — cancel it separately, before or independently of account deletion, via Settings → Subscription → "Manage / Cancel", or directly in the app store's own settings (App Store / Google Play). Otherwise, charges for future billing periods will continue even after your account has been deleted. Cancellation is described in Subscription Terms, Section 6.
This page at https://lunoria.lumasoft.pl/en/privacy/#delete-data is a functional, publicly accessible (accessible without logging in and without the app installed) description of the user-data-deletion process — meeting Google Play's Account & Data Deletion requirements and Apple App Review Guideline 5.1.1(v). The description above covers both anonymous accounts and accounts linked to an Apple or Google account, and the full scope of data the Application actually processes.
  • Restriction of processing (Article 18).
  • Data portability (Article 20) — the "Export data" feature in Settings generates a JSON file on your device containing all locally stored data (profile, conversation history, reading history, settings) and — when the device is online — a copy of the data stored for your account in our database (see "Access to data" above), without needing to contact us.
  • Objection to processing based on legitimate interest (Article 21).
  • Withdrawing consent at any time, without affecting the lawfulness of processing carried out before withdrawal (Article 7(3)).
  • Lodging a complaint with a supervisory authority — in Poland: the President of the Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warsaw, www.uodo.gov.pl. If you live in another EU country, you may lodge a complaint with the competent local authority (e.g., the BfDI in Germany, the CNIL in France, the AEPD in Spain). US, Australian, and Quebec residents have additional, specific complaint routes — see Sections 14, 15, and 16 below.

To exercise the rights above to the extent they require contacting us (see how we identify you, above), write to: support@lumasoft.pl.

9. Minimum age

The Application may be used by individuals who are at least 16 years old. The statement of full date of birth made on first launch of the Application is verified only locally, on the User's device — it does not reach us and is not an identity verification (see Terms of Service, Section 3). If we learn that data of a person under 16 has nonetheless been processed, that data will be deleted.

Persons who are at least 16 years old, including 16–17-year-olds, give consent to AI processing of their text (and, optionally, to memory) on their own, without parental consent. We do not verify age or identity — we rely on the date-of-birth statement. Refusing or withdrawing consent does not block content that does not require sending your own text (for example a horoscope or a tarot reading).

10. Data security

We use appropriate technical and organizational measures, including: encryption of data in transit (TLS), an intermediary (proxy) server designed not to log the content of requests or responses (zero storage of content in the database, zero logging of content in monitoring systems), and role-based access control (Row Level Security) for account and subscription data stored in Supabase.

Safety mechanism for sensitive content. Lunoria includes an automated mechanism that recognizes, in conversation content, signals indicating a possible mental-health crisis — in that situation, the Application immediately displays the number of the appropriate support line for your country. The message's content is checked on your device and then — again — on our server: the message is sent to the server just like any other chat message or reading question, and the server checks it with the same mechanism, only in working memory, while handling the request. If the server detects such a signal, it responds with the support line number and does not pass that message to the AI model. In both places the check is ephemeral — neither the message content that triggered the detection nor the fact of the detection itself is recorded on our side (neither in the database nor in logs), and neither is passed to anyone else.

When such a signal is detected, a single timestamp is recorded on your device — only the date and time of the event, with no message content, no type or reason for the detection, and no identifier linked to you or your account. This timestamp is kept on your device for no more than 24 hours from the event, and is deleted no later than the next time the Application is opened or used after that period has elapsed. It never leaves your device — it does not reach us, our database, the data export you can generate on request, or any diagnostic tool we use.

Solely on the basis that this timestamp is present on your device — regardless of the actual state of the person using the Application at that moment — the Application does not display commercial content or ask you to sign in with your Apple or Google account during that period.

To the extent the mechanism described above — the check of the message's content, or the retention of the timestamp — could constitute processing of health data (Article 9 GDPR), the legal basis is Article 9(2)(c) GDPR — protecting the vital interests of the data subject, in a situation where that person is physically or legally incapable of giving consent.

11. Changes to this Privacy Policy

We will notify you of material changes to this Policy at least 30 days before they take effect (e.g., by email or an in-app notification). Continuing to use the Application after that date constitutes acceptance of the changes.

When version 1.10 takes effect. Version 1.10 was published on 2026-11-17. The changes concerning Lunoria's memory (Section 2a and the related passages in Sections 6–8) apply from the moment you install the Application update that introduces the memory: it is a new feature, and you receive this information before you first use it. All other changes in version 1.10 take effect on 2026-12-17, 30 days after publication, in line with the commitment above.

Version 1.11. Version 1.11 was published on 2026-11-17. It adds a description of the consent record for AI text processing and memory (Section 3), its retention (Section 7) and the rules for 16–17-year-olds (Section 9). These changes apply from the moment you install the Application update that records consent: it is a new feature, and you receive this information before you first use it.

12. Contact

For data-protection matters: support@lumasoft.pl
Controller: LUMA Sp. z o.o., ul. Gawronia 15, 04-785 Warsaw, Poland (KRS: 0001244636, NIP: 9522285489, REGON: 544875680)

13. Language of this Policy

Today, this Privacy Policy is published in five language versions: Polish, English, German, French, and Spanish, each equally authentic. Neither is a mere translation of another provided for informational purposes only. You may switch between the available language versions at any time. Where required by the law of your place of habitual residence, the version in your official language (where published) governs the assessment of our compliance with that law.

Operational note, same status as Terms of Service Section 14a: the language gap described in an earlier version of this note is resolved — French, German, and Spanish versions of this Policy are now published, linked above. What remains outstanding, and is tracked as a separate, already-scoped task, is the geography-based ("French-first," not browser-language) routing mechanism for Quebec residents described in the Terms of Service. Until that mechanism is live, this does not, by itself, make this English Policy insufficient for the United States, Australia, Germany, or Spain — it only means Quebec-inclusive Canadian distribution should wait for that separate task, exactly as stated in the Terms of Service, Section 14a. Market-specific business-registration notices (for example, a German Impressum) are tracked separately from the language question addressed here.

14. California and other US state privacy rights

If you are a resident of California or another US state with a comprehensive consumer privacy law, this section supplements the rest of this Privacy Policy and describes your additional rights.

Categories of personal information we collect. Based on the categories defined in Cal. Civ. Code § 1798.140, we collect: (a) identifiers (an account identifier generated by our authentication provider; if you link your account to an Apple or Google account, that account's email address, and for Google also your name and profile-photo URL; your email address if you purchase a subscription through our website); (b) commercial information (subscription and purchase history); (c) internet or other electronic network activity information (technical logs, IP address, diagnostic and performance data, approximate location derived from the IP address); and (d), only incidentally and never by design, information that may fall within the statutory definition of "sensitive personal information" under § 1798.140(v)(1)(K) — specifically, the content of your conversations with Lunoria, which you control and which may incidentally reveal your religious or philosophical beliefs, sex life or sexual orientation, or health information, because you chose to share it in a free-form chat. We do not ask for, categorize, profile, or use this information for any purpose other than generating your requested horoscope, tarot, numerology, or chat response, and we do not retain it on our servers (see Section 2, "Local-first architecture") except for a message you affirmatively submit through the "Report content" feature.

We do not sell or share your personal information for cross-context behavioral advertising, and we have not done so in the preceding 12 months.

Your rights. You have the right to: (1) know what personal information we have collected, used, disclosed, or sold about you; (2) delete personal information we have collected from you, subject to certain exceptions; (3) correct inaccurate personal information; (4) opt out of the sale or sharing of your personal information (not applicable — we do not sell or share); (5) limit the use and disclosure of sensitive personal information to what is necessary to perform the services you requested (which is already the only use we make of it, described above); and (6) not be discriminated against for exercising any of these rights.

How to exercise your rights. If you have linked your account to an Apple or Google account, we can locate your data using that account's email address. If you use Lunoria only with an anonymous session, we do not hold a password, email address, or other information identifying you (see Section 8, "Your rights," which explains the Article 11 GDPR limitation that applies equally here), so we may not always be able to verify which session a request relates to. Contact us at support@lumasoft.pl with as much detail as you can provide (e.g., the email address of your linked Apple or Google account, or the approximate date and content of a report you submitted), and we will act on your request to the extent we can locate corresponding data. You may also designate an authorized agent to make a request on your behalf, subject to our ability to verify that authorization.

Shine the Light (Cal. Civ. Code § 1798.83). We do not share your personal information with third parties for their own direct marketing purposes.

15. Australia — your Privacy Act rights

This section applies to residents of Australia and supplements the rest of this Policy. It describes how the Privacy Act 1988 (Cth) and the 13 Australian Privacy Principles (APPs) apply to Lunoria, and states plainly where we go beyond what the Act strictly requires of us.

Honest status note on the "small business" question — flagged, not silently assumed. The Privacy Act 1988 generally exempts a "small business operator" — an entity with annual turnover of AUD 3 million or less that does not fall within one of the Act's listed exceptions (for example, entities that trade in personal information for a benefit, or that provide a health service and hold health information) — from most of the Act's obligations. LUMA Sp. z o.o.'s current annual turnover is, to the best of our knowledge at the time of writing, below that threshold, and Lunoria is an entertainment service, not a health service, so none of the listed exceptions appears to bring us back within scope on the facts as we understand them today. This means we may, as a matter of strict current law, qualify for the small-business exemption. We do not rely on that exemption to reduce your rights: the remainder of this section describes the protections we apply to you regardless of whether the exemption technically applies, both because the Office of the Australian Information Commissioner (OAIC) has publicly stated it considers the exemption "no longer appropriate," and because, as of the time of writing, the exemption is under active reform with a stated intent to remove it (a related set of small-business obligations already commences 10 December 2026, per the government's published reform timeline), even though no confirmed date for the exemption's full repeal was identified in the sources reviewed for this Policy. Given the size of your organization and this area of law is in the middle of active legislative change, we recommend a licensed Australian privacy lawyer confirm, at least annually, (a) our turnover position relative to the threshold as our revenue grows, and (b) whether any newly enacted reform changes the analysis, rather than relying on this Policy's snapshot indefinitely.

What we do for Australian users regardless of the exemption. Consistent with the Australian Privacy Principles, we: collect only the categories of personal information described in Section 3 of this Policy, and no more than reasonably necessary for the purposes stated there (APP 3); do not use or disclose your personal information for a purpose other than the one for which it was collected, except as described in Section 6 or as required by law (APP 6); do not use your personal information for direct marketing without an appropriate basis (APP 7) — Lunoria does not currently send direct marketing communications; take reasonable steps to keep your personal information accurate, complete, and secure (APPs 10–11, and Section 10 of this Policy); and give you access to, and the ability to correct, the limited operational data we hold, on the same terms described for all users in Section 8 (APPs 12–13).

Overseas disclosure. As described in Section 6, your data may be processed outside Australia (in the EU and the United States) by our sub-processors. If the Privacy Act applies to us, APP 8 would require us to take reasonable steps to ensure an overseas recipient does not breach the APPs, and, in some cases, would make us accountable for that recipient's handling of your data as if it were our own act. We apply that same standard of care as a matter of policy, through the DPAs and Standard Contractual Clauses described in Section 6, regardless of whether APP 8 formally binds us today.

Notifiable data breaches. If we experience a data breach likely to result in serious harm to you, we will notify you and, where the Notifiable Data Breaches scheme applies to us, the OAIC, without undue delay.

How to complain. If you are unhappy with how we have handled your personal information, contact us first at support@lumasoft.pl. If you are not satisfied with our response, and the Privacy Act applies to us, you may complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

16. Quebec, Canada — Privacy Officer and Governance Policy

In accordance with Quebec's Act respecting the protection of personal information in the private sector ("Loi 25"), the person in charge of the protection of personal information for LUMA Sp. z o.o. is:

[Name / title to be inserted before this Policy is relied on for the Canadian market] — reachable at support@lumasoft.pl in the meantime. By default this role falls to LUMA's CEO unless the company formally delegates it. Publishing this placeholder unfilled is, on its own, a Loi 25 compliance gap — independent of whether Canadian distribution is otherwise ready (see Section 13's note on why Quebec-inclusive Canada is not opening on the strength of this English document alone).

Our data governance framework includes: retention and destruction rules for the categories of personal information described in this Policy (see Section 7, "How long we keep your data"); defined roles for personnel who may access personal information; and a complaint-handling process — to file a complaint about how we handle your personal information, write to the address above; we will acknowledge your complaint and respond within a reasonable time. Where our processing involves the transfer of personal information outside Quebec (see Section 6, "Recipients and sub-processors"), we conduct a privacy impact assessment appropriate to the sensitivity of the information and the purpose for which it will be used, as required by Loi 25.

Lunoria

A conversational AI fortune-teller — astrology, tarot, and numerology. A product of LUMA Sp. z o.o. Entertainment only, 16+.

Product

  • About
  • Features
  • Get Lunoria (Google Play)

Legal

  • Privacy Policy
  • Terms of Service
  • Subscription Terms
  • Delete your data
  • Impressum
  • support@lumasoft.pl
© 2026 LUMA Sp. z o.o. · KRS 0001244636 · NIP 9522285489 ul. Gawronia 15, 04-785 Warsaw, Poland