Transparency centre · Zodiac beta
Your rights, export and deletion
Access, export, correction, deletion and preparing a request.
Contents7 sections
1. How to make a request
Email qservices@gmail.com with subject “Zodiac — personal data”, explain your request and provide a reply channel. The form below prepares an email; it does not send it automatically and no request is lodged until you send it. Do not include passwords, access tokens, API keys or complete identity documents. If you no longer have account access, say so. Identification and verification must be proportionate and avoid disclosing another person’s data.
2. Access and export
The profile provides a JSON data export. It includes account data and content available to that feature, including privacy preferences and associated records; do not assume it inventories all provider copies or the operator’s PC. For broader copies or explanations of recipients, sources or retention, request access by email. Portability has separate conditions and does not automatically cover every inference or internal document. Keep exports secure: they may contain family information.
3. Correction and technical limits
You can edit information through the profile where supported. Application limits on certain birth-data changes are technical rules, not cancellation of the right to request rectification. If a limit prevents correcting inaccurate data, contact the operator. A change may archive old readings and trigger new text; the chart and previously generated audio may be treated differently. Request review of materials that still use inaccurate information.
4. Deletion and closing the account
Profile deletion requests removal of server-managed data for the authenticated account and associated profiles, with ownership checks. It may irreversibly remove current access; export beforehand if you want a copy. Clearing the browser and signing out do not replace account deletion. In the inspected version, deletion propagation to the local generator journal is incomplete, and provider/backup retention remains to be confirmed. For complete deletion, contact the operator; they must document what was erased, what remains and any justified exception. This draft contains no general seven-day recovery rule.
5. Other choices and rights
You may request restriction where applicable, object to legitimate-interest processing and withdraw consent without retroactively affecting prior lawful processing. Use settings for statistics and contact the operator for other situations. Rights concerning solely automated decisions are assessed where legal or similarly significant effects occur; not every automated text is such a decision. Legal conditions/exceptions must be assessed for the request, and refusal must be explained.
6. Response and identity verification
The general GDPR rule is a reply without undue delay and within one month of receiving the request. Where complexity/number requires an extension, up to two additional months may apply, with notice and reasons during the first month. Requests are generally free; statutory exceptional cases must be substantiated. Additional identity information should be sought only for reasonable doubts and proportionately. Astrologer response estimates do not change these rules.
7. Complaints and assistance
You may contact ANSPDCP through its official information/procedures at www.dataprotection.ro or the competent authority where you live/work or where the alleged infringement occurred. Keep the request and reply for clarification. Contacting the operator is a resolution channel, not a compulsory precondition for a complaint or judicial remedy. Internal handling procedures, request retention and local-copy handling must be finalised before commercial publication.
Prepare a request
Email prepared locally. Nothing has been sent. Check the text and send it from your email application.
Open in emailHave 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)