Privacy Policy
Last updated: 5 November 2026. This policy describes ASTRITSA's data processing and distinguishes our own practices from third-party policies and arrangements that remain to be confirmed.
Jurisdiction: United Kingdom.
Contact: No support email is shown in the ASTRITSA application. For all inquiries — including billing, refunds and support — use the Contact form in the application.
Accounts and sign-in
ASTRITSA requires every user to create an account (sign up) and sign in before using the service. When you sign up you provide your email address and choose a password, and agree to the Terms of Use and this Privacy Policy. Your email address and a secure, salted hash of your password are stored on our server so that you can sign in. Your password is never stored or logged in plain text. This is personal data under UK and EU data protection law (GDPR).
After signing in you complete your profile: name, birth date, birth time (optional), focus area and a personal goal. Your profile stays in your browser (see below); the server holds only your account credentials and your consent record.
What stays in your browser
After you sign in, your profile and journal are kept on your device:
- Your profile (name, birth date, birth time, focus area, personal goal, password) — stored only in this browser's local storage, on your device.
- Your journal entries — same local storage, on this device only.
Nothing is synced to a server. Clearing your browser's site data deletes it permanently — use the Journal's Export button to keep a file backup. When you sign in on a new device, your profile and journal must be re-entered or imported; this application does not currently sync them across devices.
What is sent to ASTRITSA's reading service
To write your reading, the application sends your first name, birth date, focus area and goal, together with computed sky facts (Sun/Moon positions, weekday ruler, personal numbers) and the draft reading, to ASTRITSA's own reading service. That service forwards the text to its AI provider (configured by us) and returns the finished reading. Your name and goal are used to personalise the text; nothing else is collected for that purpose.
Artificial intelligence (AI) — EU AI Act transparency
ASTRITSA uses AI to personalise readings and answer oracle questions. Our server sends the reading inputs and oracle conversation through OneProvider's API gateway, operated by OneProvider Ltd., to the model provider. The configured model identifier is claude-opus-4-6. This identifier alone does not establish the upstream service or its contractual data protections.
ASTRITSA does not use your inputs or outputs to train models. OneProvider's published privacy notice states that it does not train on API requests or store prompt and response content. Anthropic's commercial API policy excludes training by default, unless the customer opts in or submits content as feedback. A data processing agreement with the gateway provider governs this processing. We have not separately verified the upstream model provider's own handling, so we do not promise that training is excluded at every link in the chain.
Gateway non-storage is not a guarantee of zero retention by the model provider. OneProvider's security page states that access logs are kept for up to 30 days and usage records for 90 days; its privacy notice also allows longer retention for legal and operational needs. Anthropic's standard API policy provides deletion of inputs and outputs within 30 days, with safety, legal and agreed exceptions. These are the providers' published periods; our agreement with the gateway provider governs its share of the processing.
OneProvider states that its gateway is hosted in Frankfurt, Germany. Upstream model processing may occur outside the UK and EEA. The upstream service, processing countries, subprocessors and applicable transfer safeguards are governed by our agreement with the gateway provider and, for the model provider's own processing, by its terms. Frankfurt gateway hosting does not establish EU-only processing. You may contact us about third-party data processing through the Contact form.
Under the EU AI Act, ASTRITSA informs you that AI is used to generate part of the content you see, and that this content is personalised to you from the data you provide. AI-generated readings are not professional advice and are not guaranteed to be accurate. You can always choose not to use the AI features and still use the locally derived readings.
What is never collected
- No analytics cookies, no advertising cookies, no third-party trackers, no session recording.
- No payment card data: subscriptions, when enabled, are entered on Stripe's hosted checkout page; ASTRITSA never sees or stores your card.
- ASTRITSA does not train models on your inputs. Third-party policies and the pending upstream confirmation are described above.
Cookies and consent (GDPR)
ASTRITSA uses only strictly necessary storage and cookies: a session cookie that keeps you signed in (an opaque, signed value — it cannot be read by scripts), the entitlement token that authorises paid readings, and the local storage that holds your profile, journal and language preference. These are not used for marketing, profiling or analytics, and are required for the service to function for you. Because they are strictly necessary, GDPR does not require prior opt-in consent for them — but ASTRITSA still asks for your agreement to the Terms and this Policy before you enter, and records it.
On every visit, a consent notice asks you to agree to the Terms of Use and this Privacy Policy before you enter. By checking the box and signing up, you consent to: (a) the storage of your account credentials and consent record as described above; (b) the use of strictly necessary session and entitlement storage; and (c) the sending of your name, birth date, focus and goal to ASTRITSA's reading service to generate your reading. The version of the terms you agreed to and the time of agreement are recorded.
You can withdraw consent for non-essential elements at any time by clearing site data or not signing up. Because no analytics or advertising cookies are used, there is no separate cookie banner for marketing cookies. For a full list of the data ASTRITSA processes and the reasons, see the table below.
Payments
If subscriptions are enabled, Stripe processes the payment under its own privacy policy. The only billing data ASTRITSA receives is your email address and subscription status, used solely to give you access. ASTRITSA does not store payment card details.
Mobile app (iOS and Android)
The official ASTRITSA mobile app is a native wrapper around this same application: it loads www.astritsa.com, so everything described above applies unchanged — the same account data, the same on-device storage, the same reading service and the same rights.
- Daily reminder: if you switch it on in Account & data, the app schedules a local notification for 09:00 your time. It is scheduled and shown entirely on your device — no data about you is transmitted for it, and refusing the permission changes nothing else.
- Offline readings: your most recent readings are kept in the app's local storage on your device so they open without a connection. Clearing the app's data or signing out removes them.
- In-app purchases: subscriptions bought in the app are sold and processed by Apple (App Store) or Google (Google Play) under their own privacy policies. We receive only your subscription status and a transaction identifier, solely to grant access — never your card details. Subscriptions bought on the website continue to be processed by Stripe as described under Payments.
- Push notifications: not currently used. Reminders are scheduled locally; no device token is transmitted to us. If that ever changes, this policy will be updated before the feature is enabled.
Deleting the app removes all app-local data (profile, journal, cached readings) from your device. To delete the account record itself — your email, password hash and consent record — open Account → Delete account in the app (or on the website) and confirm: deletion happens immediately, in product, without contacting us. You can also ask through the Contact form as described under Your rights. Messages you have already sent us through that form are not part of the account record; they are kept for the retention period stated in the table below, because they may be needed to answer a claim.
Data we process
| Data | Why | Retention |
|---|---|---|
| Email address | Create and identify your account; sign you in | Until you delete the account yourself (Account → Delete account) or ask us to |
| Password (stored only as a salted cryptographic hash) | Verify your identity at sign-in | Kept only as a hash; never in plain text; deleted with your account |
| Consent record (that you agreed to these terms, and when) | Prove consent was given, as required by GDPR | Kept for the life of your account |
| Name, birth date, birth time, focus area, personal goal (profile, provided after sign-up) | Personalise your readings | In your browser only; the reading service receives it only during a reading request |
| Session and entitlement tokens | Keep you signed in and authorise paid readings | For the life of the session/entitlement; cleared when you sign out or clear site data |
| Journal entries | Let you save and revisit your readings | In your browser until you delete them or clear site data; the Journal also lets you export a backup file |
| Reading inputs, drafts and oracle conversations sent through OneProvider to the model provider | Generate personalised readings and oracle responses | OneProvider states that it does not store content. Upstream retention is not yet confirmed for our route; Anthropic's standard API policy states deletion within 30 days with exceptions. No full-chain zero-retention or no-training guarantee is made. |
| Monthly reading allowance (a count of readings used, kept against your account) | Apply the fair-use and fair-pay limits on paid model calls | Reset at the start of each month; deleted with your account |
| Billing email and subscription status (if you subscribe) | Give you access and manage your subscription | As long as your subscription is active, via Stripe |
| Support messages (the name, email, subject and message you send through the Contact form) | Answer your request, and keep a record if a claim is later made | 24 months from your last message, then deleted; kept longer only while a dispute or a legal obligation is active |
Server logs
The reading service logs operational events only — start-up configuration, account creation, sign-in, sign-out and account deletion, and errors. It does not keep request logs, profiles, or reading content on the server. Log lines identify an account by its internal identifier, and an address by a short one-way hash: the IP address itself is never written to a log.
Sale or sharing
ASTRITSA does not sell or rent your data or send it to third parties for marketing. AI reading inputs and oracle conversations are transmitted through OneProvider to the model provider as described above. This includes personal information you put in the text; gateway filtering of account identifiers does not anonymise that content. Website billing is processed through Stripe; in-app purchases are processed through Apple or Google. The applicable provider policies and contractual arrangements govern their processing.
Your rights
You have the right to access, correct, delete and port your personal data, and to withdraw consent where processing is based on consent. Because your profile and journal live in your browser, you can erase them at any time by clearing site data for this site, or delete journal entries individually. To delete your account (which removes your email, password hash and consent record from our server), open Account → Delete account in the app or on the website — it takes effect immediately. To exercise any other right for data we hold, use the Contact form. We will respond within one month, as required by UK/EU law. You also have the right to lodge a complaint with the UK Information Commissioner's Office (ICO) or your local EU supervisory authority.
Lawful bases (UK/EU GDPR)
- Contract: your account, profile-based readings and any subscription are processed to perform the contract you sign up to.
- Legitimate interests: rate limiting, abuse prevention and the security of the service.
- Consent: the strictly-necessary storage you agree to on entry, and any future non-essential feature (which will ask separately before it is added).
Automated decision-making and profiling
Readings are personalised automatically from the data you provide. They are for entertainment and reflection: they produce no legal or similarly significant effect, and you can request human review of any outcome through the Contact form.