Effective: 19 July 2026 · Last updated: 28 October 2026
Libration keeps your personal data on your device. Birth details, charts, journal entries, chat history and cached readings are stored in your browser's local storage. We run no user database and cannot see this data.
Payments: none. Libration is free. It sells nothing, never asks for payment details, and loads no payment service.
AI readings: only if you set up an AI provider in Settings, and only to the one you choose. With a local model (Ollama, or a server you run yourself such as LM Studio), nothing leaves your machine. With a cloud provider (OpenAI, Anthropic, Groq or another OpenAI-compatible service), your chart summary, your question and any text you ask it to translate go directly from your browser to that provider, using your own API key. They never pass through our servers, and the provider handles them under its own privacy policy. Settings tells you which of the two applies before you ask anything.
City search: when you type a city name while adding a person, the city name (only) is sent to the Open-Meteo geocoding service to look up coordinates and timezone.
Feedback: the feedback form sends only what it shows you, word for word, before you press send: the kind of report, your message, a reply address if you choose to give one, and — unless you untick it — a short diagnostics block (app build, the screen you were on, Tropical or Vedic mode, language, theme, house system, the name of your AI provider and whether AI translation is on, window size and the time). It never includes your birth details, charts or API keys. The report is delivered by email through EmailJS, which processes it under its own privacy policy, to the address under Contact below. If EmailJS cannot be reached, the report may instead go to our own feedback endpoint, which keeps the report and uses your IP address only for a rate limit that expires after a day, never saving it with the report. A draft stays in your browser so nothing you wrote is lost if sending fails. To have a report you sent deleted, write to us.
Visit counts: we use Vercel Web Analytics, from our hosting provider, to count how many people visit. It sets no cookies and stores nothing on your device. For each page view it records the page path (with anything after ? or # removed before sending), the referring site, your browser, operating system and device type, and the country derived from your IP address. The IP address itself is not stored. Visitors are told apart by a hash that is reset every 24 hours, so you cannot be followed from one day to the next or across other websites. No birth details, charts, questions or anything you type are ever part of it. The legal basis is our legitimate interest in knowing whether the app is used (Art. 6(1)(f) GDPR); you can block it with any content blocker without losing any feature.
No ads, no cookies, no trackers that follow you across sites, no analytics that identify you, no sale or sharing of personal data.
If you configure your own AI provider (OpenAI, Anthropic, Groq, or any OpenAI-compatible endpoint), the API key you paste is stored unencrypted in your browser's local storage on that device, and requests go directly from your browser to that provider. This is normal for a local-first app with no account system, but it does mean any script running on the page could read the key — so use a key with a spending limit, and remove it in Settings if you stop using the app.
Backup files (Settings → export) deliberately do not contain your API keys. Everything else — people, charts, journal, chat history, saved readings and your AI preferences — is included, so treat a backup file as personal data and store it somewhere private. After importing on a new device, re-enter your key in Settings.
Because your data lives on your device, you can export it (Settings → backup) or erase it (clear the site's browser data) at any time without asking us. EU/EEA users: the processing described above is necessary to perform the contract with you (Art. 6(1)(b) GDPR), except visit counts, which rest on legitimate interest as described above, and feedback, which you choose to send (Art. 6(1)(a) GDPR).
zainab@privminds.com