Privacy Policy¶
Effective date: 2026-10-17 · Version: 2026-10-17
This policy explains how CHISHCHIN FEDOR, sole proprietor, Montevideo, Uruguay (Astrolinkers, "we") processes personal data in the Astrolinkers API, dashboard, documentation and website (the Service). Contact: hello@astrolinkers.com.
1. Two roles¶
- Our customers' accounts (people who sign up, their e-mail, API keys, usage): we are the controller.
- Our customers' end users — the birth data a customer sends through the API about people who use the customer's product: the customer is the controller and we are a processor acting on the customer's instructions (Terms, section 6). End users should contact the customer first; we help customers fulfil their requests.
2. What we collect¶
Account data: e-mail address, password hash (argon2id), e-mail verification state, the organisation (tenant) and its plan, API key metadata (the key itself is stored only as a hash), refresh-token hashes.
Billing data (paid plans and packs): the subscription status, plan, billing period, the products bought and Dodo's customer and payment ids. Card details are entered on Dodo Payments' checkout and never reach us.
Usage data: per-key hourly request counts and latency, error rates, an audit log of changes (who did what, when), and technical logs (request id, method, path, status, duration). Request bodies are not written to our logs.
Data sent through the API:
- Charts: the birth moment (date and time) and the latitude and longitude. The API does not ask for names, e-mails or other identifiers — please do not send them.
- Derived results: computed planets and houses, compatibility, interpretations, reports (PDF files), skill profiles and feedback you submit.
- LLM interpretations (paid plans only): the request parameters and the context we built for the model (birth moment in UTC and planet positions) are stored with the generated text.
- Place search: the place text you send, to return coordinates and a time zone.
We do not knowingly collect special categories of personal data and we do not sell personal data.
3. Why we use it¶
- To provide the Service: compute and store results so you can fetch them again by id.
- To secure it and prevent abuse: rate limits, quotas, fraud and abuse detection, audit log.
- To operate and improve it: error monitoring and aggregate usage statistics.
- To communicate about your account: verification, security and service notices.
Legal bases (where GDPR or similar laws apply): performance of the contract with the customer, our legitimate interests in securing and improving the Service, and legal obligations.
4. Who receives data¶
Only the sub-processors listed on Sub-processors, each for its stated purpose, and authorities where the law requires it. On the Free plan nothing is sent to LLM providers. On paid plans, LLM interpretations send the birth moment and planet positions — never names or coordinates — to OpenRouter and the model provider it routes to.
5. Where data is stored¶
The API, database and caches run on servers in Germany (EU). Report files and off-site copies of the database backups are stored in Cloudflare R2 buckets bound to the EU jurisdiction (data stays in the EU). Some sub-processors (for example e-mail delivery and LLM providers) are in the United States; where required, transfers rely on appropriate safeguards such as standard contractual clauses.
6. How long we keep it¶
| Data | Kept |
|---|---|
| Charts and derived results (compatibility, interpretations, reports, skill profiles, feedback) | Until you delete them (DELETE /v1/charts/{id} or DELETE /v1/tenant/data) or close your account |
| Computation caches (keyed by a hash of the birth input, no account data) | Expire automatically, within 1 hour for charts |
| Idempotency snapshots of API responses | 24 hours |
| Account data | While the account exists; deleted within 30 days after closure, except what the law requires us to keep |
| Usage counters and audit log | Up to 24 months |
| Technical logs and error reports | Rotated automatically; at most 90 days |
| Database backups (daily: on the EU servers and an off-site copy in the EU) | 14 days — deleted data disappears from backups within 14 days |
7. Deletion and your rights¶
- Customers can delete one chart with everything derived from it
(
DELETE /v1/charts/{id}) or all of their data at once (DELETE /v1/tenant/data), or ask us at hello@astrolinkers.com. Deletion removes the database rows, the report files and the cached computation for that chart at once; daily backups that still contain it roll off within 14 days. - End users of a customer's product should ask that customer; we act on the customer's instruction.
- Depending on where you live you may have the right to access, correct, delete, restrict or object to processing, to data portability, and to complain to a supervisory authority. Write to hello@astrolinkers.com; we answer within 30 days.
8. Security¶
TLS for all traffic (HSTS), API keys and passwords stored only as hashes, strict tenant isolation (each customer can read only its own data), least-privilege access for our staff, and monitoring. No system is perfectly secure; we will notify affected customers without undue delay if a breach affects their data.
9. Children¶
The Service is for businesses and developers, not for children. Customers whose products reach minors are responsible for obtaining any consent the law requires.
10. Changes¶
We will post any change here with a new effective date, and announce material changes at least 30 days in advance.