Transparency centre · Zodiac beta
Children’s and family profiles
Adult-managed profiles and care for children’s data.
Contents6 sections
1. Proposed account policy
The launch proposal is adult-managed accounts, with child profiles created only by an entitled parent/representative. Implementation does not yet fully verify adult identity or parental authority. The existing checkbox is not represented as independent proof. We do not claim all processing of a child’s data is prohibited below a fixed age; conditions depend on the service, basis and applicable law. This policy needs legal validation and suitable mechanisms before commercial launch.
2. Minimal data, no public profile
For a child, prefer an alias and only birth-chart essentials; avoid full name, school, home address, photographs, diagnoses and vulnerability details in free text. Family profiles are associated with the managing account and are not intended as a public directory. The adult with access can view that profile’s materials. Do not share credentials or exports. Data and interpretations may reach providers involved in the chosen feature; we do not claim they remain solely on the device.
3. Age-appropriate interpretation
For young children, text should address the adult using calculated years and months, without assumptions about speech, work, marriage or adult relationships. For children and adolescents, readings should avoid fixed labels, sexualisation, pressure on choices and medical recommendations. No astrological text establishes a child’s development, abilities or future. The adult remains responsible for critical reading and may report/challenge wording; automated systems do not guarantee every result is appropriate.
4. Adult family members and informing them
For a partner, relative or another adult, inform them of entered data, recipients and access by the managing account. A family relationship is not universal permission. If the person disputes use of their data, contact the operator; they do not need the account holder’s password to make a request. The basis and notice procedure for indirectly obtained data must be determined separately, including any justified exceptions.
5. Correction, deletion and representation
The account holder can manage family profiles through existing features. Requests concerning a child or another member may also be emailed to qservices@gmail.com. The operator must proportionately verify identity and representation before disclosing data; do not send complete identity documents unsolicited. Rights belong to the person concerned and need care where their interests differ from the account holder’s. Cloud deletion does not yet guarantee erasure of the local generator journal or provider copies; see Your rights.
6. Conditions for completion
Outstanding work includes impact/risk assessment for child profiling, legal bases, representation verification, age-appropriate notices where relevant and dispute handling. We do not claim a DPIA is complete or a DPO is unnecessary. Statistics remain optional and are controlled at account level rather than through assumed child consent.
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)