1. General Provisions
1.1. This Policy sets out how personal data is processed and protected in the astronavi service available at https://astronavi.org (the “Service”).
1.2. The data controller is FirstLab OÜ, an Estonian private limited company with registry code 17605078 and registered address Vesivärava tn 50-201, Kesklinn, Tallinn, Harju maakond, Estonia (the “Operator”).
1.3. The email address for data subject requests, withdrawal of consent, and requests to correct data, cease processing, or destroy data is [email protected].
1.4. FirstLab OÜ is registered in the Estonian Business Register under code 17605078.
1.5. This Policy describes processing under the EU General Data Protection Regulation (GDPR) and applicable Estonian data-protection law, whether processing is automated or manual.
1.6. Authorized personnel and contracted processors may access personal data only to the extent needed for their assigned duties, subject to confidentiality and access controls.
2. Processing Principles
2.1. Processing is carried out lawfully and fairly for specific, predetermined, and lawful purposes.
2.2. The content and volume of the data correspond to the processing purposes. The Operator must not collect data that is excessive for those purposes or retain it longer than the established period.
2.3. Data is corrected, blocked, deleted, or destroyed where the law provides grounds for doing so.
2.4. The Operator does not process biometric personal data and does not make decisions that produce legal consequences for the User solely through automated processing.
3. Data Subjects, Purposes, Data, and Legal Bases for Processing
| Category of data subjects and purpose | Data processed | Legal basis |
|---|---|---|
| Website visitors: website operation, security, and prevention of abuse | IP address, User-Agent, request date and time, URL, technical cookies, session identifiers, and error information | Performance of an agreement or steps taken at the data subject's request before an agreement is concluded; exercise of the Operator's rights and legitimate interests, provided the data subject's rights are not infringed |
| Website visitors: web analytics | URL and referral source, technical characteristics of the browser and device, actions on the website, analytics cookie identifiers, and IP address | Separate consent to analytics cookies |
| Registered Users: registration, login, and account | Email, telephone number, password hash, OAuth profile identifier and data, registration date, IP address, User-Agent, information about logins, sessions, and access recovery | Performance of an agreement; consent where the Operator has selected it as the legal basis |
| Registered Users: creation of personalized calculations and interpretations | Name, sex, date, time, and place of birth, country, city, coordinates and time zone of the place of birth, city and country of residence or relocation, and User preferences | Performance of an agreement; User consent |
| Registered Users: Service history and memory | Questions, messages, descriptions of dreams and situations, wishes, concerns, notes, selected categories, calculations received, responses, and interpretations | Performance of an agreement; User consent |
| Users making a payment or taking out a subscription, once checkout opens | User identifier, email, payment identifiers, amount, currency, status, date, plan, subscription identifier, and tokenized payment-method identifier | Performance of an agreement; compliance with applicable tax and accounting obligations |
| Users contacting support | Name, contact details, content of the request, attached materials, and response history | Performance of an agreement; handling the request and protecting the rights of the Operator and User |
| Mailing recipients | Email, name, profile data needed for the selected personalization, history of consent and refusal, and technical delivery data | Separate consent for advertising mailings; performance of an agreement for service messages |
| Persons whose information a User enters into the compatibility or memory function | Name or designation, nature of the relationship, date, time, and place of birth, and note | The User's confirmation that they have that person's consent or another legal basis |
3.1. A registered User's consent covers only that User's own personal data.
3.2. A User may not enter another person's data without a legal basis. Before entering such data, the User must obtain that person's consent or have another lawful basis, and must provide evidence of it if requested by the Operator. If the User provides no evidence, the Operator may block or delete the information.
3.3. Free-text fields are not intended for information about racial or ethnic origin, political opinions, religious or philosophical beliefs, health, intimate life, or criminal records, including such information about other people. The User must not enter such data. If such information is detected, the Operator ceases processing it and deletes it unless an applicable legal basis exists.
4. Processing Operations and Methods
4.1. The Operator may collect, record, organize, accumulate, store, correct, retrieve, use, transfer data in the cases described in this Policy, de-identify, block, delete, and destroy data.
4.2. Processing is primarily automated. Manual access is possible when handling requests, carrying out a security review, correcting an error, complying with a legal obligation, or responding to a data subject's request.
5. Storage Location and Other Parties Involved
5.1. The primary application database and locally retained backups are hosted in France. The Operator does not claim that using the Service from another country moves that person's data to a database in their country.
5.2. The Service runs on OVHcloud infrastructure in France. The database backup job stores restricted-access copies on the same server for up to seven days. The Operator must update this notice before adding an off-site backup destination.
5.3. Depending on configured functions and the User's choices, data may be disclosed to the following parties. Email, payment, and external sign-in providers must be identified here before those integrations are enabled:
| Recipient | Purpose and data transferred |
|---|---|
| OVHcloud | Hosting, database storage, and local backups in France |
| Cloudflare | Delivery and security of web traffic, including IP address, request headers, and requested URL |
| OpenStreetMap geocoding service | Place names submitted for location lookup and the technical data needed to answer the request |
| User-selected identity provider, if enabled | Sign-in identifier and profile fields authorized by the User |
| Email delivery provider, once configured | Email address, message content, delivery metadata, and consent state needed to deliver Service messages |
| Payment provider, once configured | Information needed for checkout, subscriptions, refunds, and receipts; the Operator does not receive full card details |
The DeepSeek API, based in China, is also used for text generation. A model request may include a User's question, description of a situation or dream, or birth-related information depending on the function. Further details appear in Section 6.
5.4. Where a party acts as a processor on the Operator's instructions, the Operator must have a GDPR Article 28 agreement defining the permitted processing, confidentiality, security measures, sub-processors, assistance with rights and incidents, and deletion or return of data. A party's role also depends on the actual service and contract.
6. Artificial Intelligence and Cross-Border Transfers
6.1. The Service uses the DeepSeek API for some generated texts. The application masks selected personal values in its own diagnostic logs, but this does not mask the prompt sent to DeepSeek. Depending on the function, the prompt may include a User's question, description of a situation or dream, or birth-related information. Users should not enter special-category data or another person's data without a lawful basis.
6.2. DeepSeek states that it directly collects, processes, and stores personal data in the People's Republic of China. The Operator must assess the actual payload and the provider's terms before enabling the integration for identifiable User data.
6.3. Before personal data is transferred outside the EEA, the Operator must establish a valid GDPR Chapter V transfer mechanism, assess any required supplementary measures, and provide the relevant information to Users.
7. Retention Periods
| Category | Maximum period |
|---|---|
| Account, profile, OAuth links, and active settings | Until account deletion or termination of the agreement; deletion from the primary database without undue delay, with full deletion completed no later than 30 days unless another legal basis exists |
| User texts, saved interpretations, situations, people, and places | Until deletion by the User or account deletion; full deletion completed no later than 30 days |
| Draft of unfinished onboarding | No more than 7 days from the last change |
| Request and response texts in the technical generation log | No more than 30 days; on account deletion, texts are deleted or irreversibly anonymized earlier |
| Active refresh token | Until expiry, but no more than 30 days; a revoked token and associated IP/User-Agent data: no more than 30 days after revocation |
| Tokens for email and telephone verification and access recovery | Until use or expiry, and thereafter no more than 24 hours for technical deletion |
| Request to change email address | No more than 48 hours after creation |
| Failed logins without an identified User | No more than 30 days |
| Login history of an identified User, activity log, and onboarding events | No more than 180 days; deleted earlier on account deletion unless a separate legal basis exists |
| Administrative action log | No more than 1 year; fields containing personal data are minimized |
| Technical billing and integration events | Processed events: no more than 90 days; failed events: until the error is resolved and then no more than 90 days |
| Data of an unregistered lead or incomplete funnel | No more than 90 days, then deletion or irreversible anonymization |
| Evidence of consent and withdrawal | For the duration of consent and 3 years after withdrawal or termination of the relationship; after account deletion, identifiers, IP addresses, and User-Agent strings are deleted if no longer needed |
| Support requests and responses | Until the request is resolved and no more than 3 years after closure, unless longer retention is required for a specific dispute |
| Payment and primary accounting records, once payments are available | For the period required by applicable Estonian tax and accounting law; data not needed for those obligations is deleted separately |
| Analytics cookies | According to the selected setting and the lifetime of the particular cookie, but no more than 14 months; consent can be withdrawn at any time |
| Backups containing personal data | No more than 30 days; before a restored backup is put into operation, previous deletions and withdrawals must be applied to it again |
7.1. These are the Operator's maximum retention periods, except for periods that the law expressly sets as mandatory minimums. Data may be deleted earlier once the processing purpose has been achieved.
8. Data Subject Rights and Deadlines for Requests
8.1. A data subject may request access, rectification, erasure, restriction, portability, or object to processing where the GDPR provides that right; withdraw consent at any time; and complain to the Estonian Data Protection Inspectorate or another competent supervisory authority.
8.2. A request should be sent to [email protected] and include information sufficient to verify the person's identity and relationship with the Operator. The Operator does not request a passport copy if identity can reliably be verified by a less excessive means.
8.3. The Operator responds without undue delay and within one month of receiving a request. Where necessary because of complexity or the number of requests, this period may be extended by up to two further months, with notice and reasons given within the first month.
8.4. Inaccurate data is corrected without undue delay after the Operator has enough information to verify the request. Data that is no longer needed is erased or anonymized unless another lawful basis requires retention.
8.5. If processing is found to be unlawful, the Operator stops or restricts it without undue delay and determines whether the data must be erased or retained for another lawful reason.
8.6. An objection to processing is assessed under the applicable GDPR grounds, including any compelling legitimate grounds or the need to establish, exercise, or defend legal claims.
8.7. Following withdrawal of consent, processing based on that consent stops without undue delay. Data may be retained where a separate lawful basis applies; withdrawal does not affect prior lawful processing.
9. Data Security
9.1. The Operator takes legal, organizational, and technical measures, including access restrictions, security-event logging, local backups, encrypted communication channels, and procedures for data recovery and deletion. Additional controls are reviewed as the Service develops.
9.2. Where a personal-data breach is likely to result in a risk to individuals' rights and freedoms, the Operator notifies the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it. Affected individuals are informed when the GDPR requires it.
10. Changes to the Policy
10.1. The current revision is published at https://astronavi.org/legal/privacy. Previous revisions are retained to document the terms that applied when the data was processed.
10.2. If a change requires fresh consent, the Operator obtains it separately. Continued use of the Service does not, by itself, replace consent where the law requires a demonstrable form of consent.