LunaloQ data & privacy overview

Account and authentication data

LunaloQ uses the shared MAVIORB account and authentication layer so you can create or access an account, verify email access, recover sign-in access, and reach protected LunaloQ experiences. Where Google Sign-In is chosen, that shared identity processing is described in the MAVIORB Privacy Policy.

Profiles, birth data, and location context

LunaloQ profiles can contain a name or relationship label, birth date, birth time or an explicit unknown-time state, birthplace, timezone, and location context. These details are used only where the selected experience needs them to calculate or present relevant astrological context.

Reading requests, generated readings, and history

LunaloQ can store reading requests, selected Reading Type and participant context, generated reading output, history and visibility state, and operational metadata needed to deliver the reading, prevent duplicate charging or generation, support recovery, and troubleshoot failures.

Calculation engines, AI-assisted interpretation, and OpenAI

LunaloQ's astrology and transit engines calculate the underlying chart and timing context using defined algorithms. AI is a later interpretation layer, not the source of those calculations. For First Glimpse, raw birth input stays inside the calculation-engine boundary and the OpenAI path receives bounded calculated astrology facts together with the three context choices supplied in that journey.

For signed-in readings, the exact AI context depends on the selected Reading Type. It can include calculated chart or transit context, a question or prompt, relationship context, and limited profile or background information that the reading contract permits and genuinely needs. LunaloQ currently uses the OpenAI API for these AI-assisted interpretation paths and records bounded provider and usage metadata needed to operate and audit them.

MAVIORB explicitly asks the OpenAI Responses API not to store application state for these LunaloQ generation requests. That setting is not the same as a claim of Zero Data Retention: OpenAI may still process limited content under its applicable API safety and abuse-monitoring controls. See the AI transparency & guidance notice for the user-facing explanation of how calculation and AI interpretation work together.

Moondrops, purchases, and subscriptions

Moondrops govern Reading Type access. Browser Moondrop Pack checkout can use Stripe for one-time purchases. Where Android purchase or subscription functionality is enabled, Google Play may process the applicable transaction. Moondrop Packs and Subscription Plans are separate product paths: Packs are one-time Moondrop purchases, while Subscription Plans are recurring entitlement products with their own allowances and limits.

LunaloQ stores the order, entitlement, fulfilment, and provider-reference information needed to verify and operate those product paths. Payment providers process payment or store-billing information under their own services and policies.

Notifications, devices, and support

Where notification features are used, LunaloQ can store notification preferences and device-token information needed for the selected channel. Support submissions can contain the subject, message, product context, operational metadata, and user-visible response needed to handle and review the request. Internal administrator notes are not part of the user-visible support response.

Optional Early Access communications

LunaloQ Early Access is a separate optional email communication list for testing invitations, early-access opportunities, and LunaloQ launch availability. Submitting that form is not acceptance of LunaloQ Terms, is not blanket consent to privacy processing, and does not subscribe you to unrelated MAVIORB lists. The shared communications registry keeps the scoped consent and suppression evidence needed to honour that choice.

Read the MAVIORB Communications Privacy Notice for the shared communications collection baseline.

Contract withdrawal records

If you use the LunaloQ online contract withdrawal function, MAVIORB records the name, confirmation email, contract type/reference, declaration text, submission time, acknowledgement state, and bounded operator-review information needed to evidence and process that consumer request. Contract withdrawal is separate from account deletion and subscription cancellation.

Where an applicable statutory withdrawal right exists for a transaction, you can use the LunaloQ online withdrawal function to submit the declaration.

Retention, deletion, and privacy rights

Different LunaloQ records have different operational, security, billing, tax, support, dispute, and audit needs. MAVIORB keeps records only for as long as they are needed for the applicable purpose or lawful retention requirement and limits retained information when an account is closed or a deletion request is completed.

The public LunaloQ Account Deletion page is the current request route for deletion of the LunaloQ product relationship and associated product data. It does not silently delete the shared MAVIORB identity or promise that every transaction, security, contractual, suppression, dispute, or audit record can be erased immediately. For other privacy questions or rights requests, use the contact route in the MAVIORB Privacy Policy. Do not send birth details, reading content, passwords, or other unnecessary sensitive information by email.