Transparency centre · Zodiac beta
Personal data privacy notice
What information we use, for which purposes and what still needs clarification.
Contents17 sections
1. Controller and notice scope
DAVINA EMPIRE S.R.L. is the controller designated by the project owner for Zodiac. Privacy contact: qservices@gmail.com; company details are on Contact. This email is not represented as a data protection officer (DPO) address; whether appointment is required has not been established. This notice describes Zodiac, not processing in the company’s other applications, even where the operator is the same.
2. What we receive and from where
We receive the account holder’s name/alias, birth date, time, locality, coordinates and time zone, language and settings. Full name and context about relationships, work/study, interests and travel are optional. Email/phone sign-in involves the supplied identifier, a password hash and session information; the inspected flow does not store plaintext passwords. Family information may come from the account manager rather than the person described. We generate the chart, age, interpretations, translations, replies and audio files. Infrastructure providers may process network metadata including IP; their settings and retention have not been confirmed.
3. Concrete purposes
Profiles and birth information support calculations and age-based personalisation; optional context adjusts subjects without assuming unknown circumstances. Credentials support access to your own data and abuse limitation. Questions and replies support conversation, history and refusal review. Audio text supports requested listening and greetings when enabled. Contact, appointments and feedback support services and bug fixing. Token/cost records and technical logs support operations and diagnosis. Statistics on visits, sections and listening are a separate optional purpose, enabled only after acceptance.
4. Legal bases — decisions still required
CONFIRM BEFORE PUBLICATION: the operator and legal adviser must approve a basis for each purpose and category of person, including family members. The working proposal is to assess contractual necessity for requested features, documented legitimate interests for security/support and separate consent for optional statistics. These are proposals, not legally validated justifications. Acceptance of terms is not blanket consent to all processing, and entering data does not by itself establish a legal basis. Actual applicable duties must be identified for legal obligations. Accidentally submitted sensitive data needs a separate assessment, not assumed consent.
5. Who may receive data
Cloudflare hosts the application and server storage. OpenRouter may receive the question and necessary context and route it to the selected model provider; the actual provider must be tracked in generation records. An OpenAI fallback may be used when configured. ElevenLabs receives synthesis text and returns audio. Authorised administrators and the astrologer may view requests, feedback and review materials within their access scope. The operator’s local generator may receive context batches for readings and retains a local journal. Providers do not automatically receive your password or API key from the browser. Exact subprocessor lists, contractual roles and processing agreements remain to be verified.
6. Locations, transfers and provider use
TO CONFIRM: processing countries, contracts, safeguards for any transfers outside the EEA, log duration and provider-account training options. We do not claim all data stays in the EU, that retention is zero or that no provider uses data for its own purposes. Providers’ public policies do not establish this account’s settings. Before commercial launch, agreements must be checked and this section updated with actual recipients and safeguards. You may request available information through the contact channel.
7. Retention and deletion limits
Inspected technical behaviour: detailed statistics events are cleaned after 90 days; totals may remain until account deletion. Current statistics choices expire after 180 days and minimal choice history is cleaned after 90 days; these are proposed technical values, not legally mandated periods. Readings, questions, audio and profiles do not all have a general automatic retention deadline. Some logs have configurable retention. The local generator may retain results after cloud deletion; deletion synchronisation needs remediation. TO CONFIRM: complete periods, backups, providers and any separately justified retention. We do not promise instantaneous deletion from every system.
8. Personalisation and AI
The application calculates astrological data and age, then automatically adapts text to life stage and supplied context. Depending on purpose and use, this may constitute profiling for data protection purposes. In inspected features, interpretation is not used to decide credit, employment or legal entitlement. We do not claim definitive personality assessment. AI generation can be wrong, and age adaptation and translation do not guarantee correctness. The AI and voice page explains the difference between automated generation and human review.
9. Security and device data
Profile-data API access checks credentials and account ownership; account passwords are hashed. These measures are not a security certification. The browser/PWA may retain the profile, access credentials, readings and audio for continuity/offline use. On a shared device, sign out and clear private content; uninstalling the PWA does not guarantee erasure of all browser storage. Do not send identity documents, passwords or keys through feedback. If you suspect an incident, contact the operator with the minimum necessary information.
10. Choices and rights
You can refuse or withdraw statistics in Cookie settings without losing access to readings. The profile provides export and deletion; for additional access, correction, restriction, objection or other requests, see Your rights and email qservices@gmail.com. Rights have conditions and exceptions depending on the situation; technical limits do not remove your ability to seek assistance from the operator. You may complain to ANSPDCP or the competent authority in your jurisdiction. The final notice, retention and legal bases have not yet received legal approval.
11. Devices, campaigns and automation clues
Only after optional statistics are selected, the browser sends the exposed system/version, browser family, screen/window dimensions, language, theme, reduced-motion preference and browser/PWA mode. Installation is marked only when an install event or standalone use is observed; clicking Install does not prove installation. We cannot reliably identify a phone model, CPU, emulator or person. Webdriver, headless-browser and certain platform/user-agent inconsistencies indicate possible automation only and do not trigger automatic blocking. Approximate country comes from Cloudflare infrastructure and can reflect a VPN or another access point. The server may retain encrypted IP addresses with access limited to 7 days, shown to an administrator only on request; lists use a masked form. The keyed network hint changes daily, remains pseudonymous personal data and does not establish a unique visitor. Without the encryption secret, this flow does not store an exact address. Detailed metadata have a technical 90-day retention. Administrators create up to 100 recognised campaign keys; arbitrary URLs/query parameters do not create campaigns. Visits without an account use an opaque consent token expiring within 24 hours and a per-tab session identifier. These visits are pseudonymous, not anonymous. Associating an ordinary visit with a signed-in account also requires valid account consent. This does not turn sign-in into a new registration; profile-creation and account-registration sources are distinct, described in section 14. Statistics measure consenting observations, not all traffic or verified real people. Withdrawal stops future collection; account export/deletion covers associated records. For visits without an account, contact the operator without publishing the token. Proposed retention and legal bases still need legal validation. IP access expires at the deadline even if maintenance is delayed. Ciphertext cleanup is automatically scheduled at expiry and performed by server maintenance; infrastructure unavailability can delay physical erasure. This does not establish instantaneous erasure from provider backups.
12. Languages, referrals and community feedback
On first opening, language may come from a campaign/invitation link, approximate Cloudflare country or browser language. A saved manual choice takes priority. Installation from an invitation can retain its public key in the PWA start address; the key alone never automatically associates an account. This functional request creates no analytics identifier and stores no country in the browser. Demo prices use the configured reference, initially EUR 1 = RON 5, rounded to whole units; this is not a current exchange rate. Billing is disabled. Referrals are optional and available to adult accounts: an association between a new account and an invitation link is created only after a separate unchecked signup choice. Inviters see totals, not invitee identities. Sharing/copying counts actions rather than recipients; attributed accounts are distinct from consented traffic observations. Activity over 7/30 days comes from explicit in-app check-ins. Associations and share actions have a technical 90-day retention, cleaned through maintenance; the link remains until account deletion. No automatic or guaranteed rewards are provided. Reviews may be submitted voluntarily once every 30 days. Ratings, liked text and aliases are published only with separate permission and moderation. Suggestions remain private to administrators. Publication permission can be withdrawn through your reviews; account export/deletion includes these data. Private reviews are retained until account deletion or completion of a request to the operator; a final period and legal bases still need confirmation.
13. Private messages and notifications
Messages supports conversations with Andreea, technical staff and support, separately from automated astrology answers. The server retains the text and subject, recipient, account holder, reply sender, dates, status and read acknowledgement to manage conversations and show notifications. Authorised staff and administrators can read these messages; they are not sent to an AI model to produce a reply. Automatic notices are labelled separately. Messages belong to the account holder and remain visible when switching a family profile or device; avoid sensitive information about others, passwords and banking information. Drafts remain only in window memory and are cleared when leaving the section or changing identity. Conversations have technical volume and frequency limits, are included in export and are removed by server-managed account deletion. There is no general automatic deadline for all conversations yet; final retention, legal bases and staff access still require validation. Messages are private, do not trigger email/SMS and are not an emergency service or a promise of a fixed reply deadline.
14. Visit, profile and signup sources
Only with current optional-statistics consent, the browser classifies the referring page into a category such as Google, TikTok, Facebook, Instagram, YouTube or another external source. This flow does not transmit or retain the full address, raw domain, path, parameters or search terms. A registered campaign link takes priority over a valid invitation, followed by the browser-reported category. Campaign identifiers, keys, names and registered aliases are retained; invitations retain identifiers and keys. Link presence is browser-reported and checked against the server registry, without proving who distributed it. Missing referrer information is shown as “direct or source not provided”; it does not prove direct access. Google/TikTok and other categories are reported hints, not independent identification: the browser or app may hide or alter the information. First observed entry means the first consented observation still retained, not the person’s first-ever visit. Creating the primary profile and actual email/phone registration are separate stages, each with available dates and source. Current anonymous consent proof may associate a visit with a new primary profile at creation; the explicit choice made before the profile is retained with its original version and expiry, without extension. Signing into an existing account does not transfer an anonymous visit source as its signup source. Refusal, missing evidence, expiry or an older profile leave the source unavailable; we do not retrospectively fill it by guessing. Family profiles inherit the owner’s information and are not counted as signups. The signup source is already associated with the owner before registration, not a later visit. An invitation visit is separate from a referral association explicitly accepted at signup; inviters receive totals only, without invitee identities. Administrators see sources and totals in paged reports filtered by period, user or campaign and grouped by UTC day/month. Source data have a technical retention of up to 90 days from observation, with maintenance removal and unavailability at expiry. They are included in the owner’s export and removed upon owner deletion. Withdrawal stops future observations and hides these sources from the owner’s reporting; it is not a promise of immediate erasure of all prior records. These new sources are explained in version 2026-10-10.1; an old choice does not automatically enable this expanded purpose. Legal bases, periods and contracts still need operator and legal-adviser validation.
15. Welcome screen and technical details
With current optional-statistics consent, we measure the initial welcome display, pressing “Continue to Zodiac”, closing it or choosing feedback. Continuing is not statistics consent and remains possible without it. Account previews are excluded. If you accept while the welcome is open, measurement starts then; earlier clicks are not reconstructed. Reports cover received consented observations, not every visit or visitor. “No observed Continue” includes pending states and interrupted delivery; it does not prove abandonment. Events use deduplication identifiers, server receipt times and the same anonymous consent proof or authenticated owner. A new primary profile may adopt a valid anonymous observation with its original consent expiry; logging into an existing account does not transfer it as a signup. To explain display and usage differences, the first measured observation of the loaded page collects a limited snapshot: user agent/appVersion, platform/vendor, language and language list, online/cookie state, webdriver, maxTouchPoints, hardwareConcurrency and deviceMemory if exposed, Do Not Track/Global Privacy Control and basic userAgentData brand/version, mobile and platform information. Navigator also includes appCodeName/appName, product/productSub, vendorSub, oscpu/buildID, pdfViewerEnabled and standalone where exposed; deprecated or nonstandard fields are not verified identification. Connection includes only available effectiveType, downlink, rtt and saveData: browser estimates, not measurements or proof of the real connection technology. Screen includes available width/height, availWidth/availHeight, colorDepth/pixelDepth, availLeft/availTop/left/top, isExtended and orientation.type/angle; viewport includes width/height and devicePixelRatio. In the current version, the snapshot also includes inner/outer window dimensions, position and scroll, visualViewport, document state and dimensions, display mode, pointer/hover/theme/motion preferences, timezone and cpuClass/type/downlinkMax where exposed; page content is not read. Missing values remain unavailable. Location is reduced to the application origin, protocol, host/hostname/port and an allowed public route; full href, query/search, hash, address credentials and private paths are not retained. Link routes are checked against campaign/invitation registries. The separate inventory of exposed Location/Navigator/Screen properties contains names, descriptor kind and collection status only, up to 32/120/64 names and six prototype levels, excluding Object.prototype, symbols and internal names; limits or inspection errors are marked. We retain the field values described above; other objects/getters stay unread, functions are not called, and href/search/hash are marked redacted without reading their values. We do not read plugin lists, devices, permissions, battery, contacts, clipboard, precise location or accounts, request high-entropy hints or use canvas/audio fingerprints. This inventory does not guarantee enumeration of every browser extension, nested API or future browser version. HardwareConcurrency is a reported logical-processor count, not a CPU model. Browser values can be altered and do not prove identity, exact phone model, emulation or a human visitor. Separately, available Cloudflare infrastructure metadata may include approximate country, ASN/network organisation, edge centre, HTTP/TLS protocol and, only if provided, bot or corporate-proxy signals. Missing signals do not establish the absence of automation or a proxy. With the new consent, ipapi.is may enrich network details as described in section 16; the external source stays separate from Cloudflare, and historical data without a result remain unavailable. Exact IP is encrypted only on the server, accessible by an explicit audited administrator action for up to 7 days; ordinary reports do not expose it. Welcome records and technical details have a maximum 90-day retention, becoming unavailable at expiry and removed by maintenance. Protected owner export includes associated observations and the owner’s own available IP within the 7-day limit; account deletion removes them. Withdrawal removes this screen’s observations associated with the owner or anonymous proof and stops the local queue. Version 2026-10-11.5 requires a new choice; an older version does not enable these details. Final legal and contractual project validation is still pending.
16. ipapi.is network information and configurable reports
Only after a valid optional-statistics choice under version 2026-10-11.5, the server may send the IP observed by Cloudflare infrastructure to ipapi.is (Nikolai Tschacher, Berlin, Germany), over HTTPS to de.ipapi.is. The public provider DPA describes this endpoint as processing in Germany without automatic failover to other countries. The purpose is to enrich our own usage report with network provider, ASN, approximate country/region/city, timezone and reported mobile-network, VPN, proxy, Tor, datacenter, crawler or abuse indicators. IP-derived location is not GPS location and may describe a network or exit point. We do not send your name, account, birth date, questions, horoscope content, page address or browser details to this provider. The key stays exclusively on the server and is sent in the request body rather than the URL. The observation is saved before lookup; unavailability, the daily limit or an error does not prevent application access. The cache uses a keyed IP identifier without plaintext IP and expires within 7 days. Normalized metadata associated with a visit last at most 90 days; missing data stay unavailable, with result source and time shown. Cache use does not extend result age. A shared network does not mean a shared person. A negative flag means “not detected by the provider”, not proven absence; a positive flag does not prove the user is a bot. These results do not automatically deny access. The public ipapi.is policy and DPA state that queried IPs are not retained after a response; the DPA clarifies that API-customer usage metadata (key, calling-system address, request type/count, time and user agent) are used for billing, limiting and abuse prevention. These are provider statements, not an audit of our account. Evidence of the contractual agreement and legal validation remain on the administrator checklist. Withdrawal stops new lookups and removes the association of network results with the owner/anonymous proof; caches with no active associations are removed. Protected export/deletion include retained results belonging to the owner. Administrator reports may select columns and save named configurations; a configuration is not an astrology profile and does not change source data. Ordinary reports and CSV files use a masked IP, not the exact address. Opening a report does not retrospectively enrich an old observation.
17. HTTP requests and security before cookies
The server separately retains successful entry-document requests and authentication, origin or limit API denials (401/403/429) to examine automated access and abuse. This evidence may exist before cookie choice and after refusal. It contains time, method and status, country from trusted Cloudflare context, header-reported browser/OS families and possible header indications. IP is encrypted on the server; an administrator may explicitly reveal it, with an audit record, for at most 7 days. All evidence expires after 7 days and is capped at 20,000 groups; similar requests are aggregated hourly using a daily identifier separated from analytics. No URLs, parameters, referrers, JavaScript data, names, accounts or campaigns are kept here; ipapi.is is not called for this purpose. Counts represent requests, not people, visits or viewed screens. Headers may be forged, IPs shared, and absent hints cannot verify a human. This report does not automatically block access. Necessity, interest balancing and the legal basis remain in provisional documentation requiring operator validation; beta publication is not legal approval.
Have a question?
For questions about the application or your data, write to us.
Sources and checks
Sources and checks
Sources explain the reviewed framework; they do not certify project settings or contracts. The legal framework was consulted on 8 October 2026; MDN technical sources on browser referrers on 10 October 2026. Romanian legal consolidation, applicability and final approval must be rechecked. Cloudflare/MDN metadata sources, GDPR Articles 5 and 7 and EDPB Guidelines 05/2020 on consent were also rechecked on 10 October 2026. Availability in this project account is separate from provider documentation. The ipapi.is API documentation, privacy policy and public DPA were consulted on 10 October 2026; provider statements and the account contract are distinct evidence.
- Company identity / Identitatea firmei
- GDPR — ANSPDCP (Arts. 5–9, 12–22, 25, 28, 30, 32–35, 44–49)
- EDPB — Data subject rights / Drepturi
- European Commission — Information for individuals
- Legea 506/2004, art. 4 — forma actuală de reverificat / recheck current version
- AI Act — Article 50 (applicability review required)
- OpenRouter — provider logging
- ElevenLabs — privacy
- Cloudflare — customer DPA
- MDN — browser referrer availability / Proveniența disponibilă în browser
- Cloudflare — trusted request metadata
- Cloudflare — conditional bot-management signals
- MDN — Screen colorDepth/pixelDepth
- MDN — basic userAgentData availability
- GDPR — EUR-Lex, Articles 5 and 7
- EDPB — Guidelines 05/2020 on consent
- MDN — Referrer-Policy
- ipapi.is — API documentation
- ipapi.is — Data Processing Agreement / Germany endpoint
- ipapi.is — Privacy policy (provider statements)