Privacy policy
This policy explains what personal data Borgiana collects when you use the Borgiana apps for Android, iOS and the web (borgiana.com), why, who helps us process it, how long we keep it, and the rights you have. It is written to meet the Argentine Personal Data Protection Law No. 25,326, the EU and UK General Data Protection Regulation (GDPR) and similar laws.
1. Who is responsible
Borgiana is developed and operated by Juan Manuel Ganancias, an individual developer based in Mendoza, Argentina, who is the data controller (“Borgiana”, “we”, “us”). For any privacy question or request, write to [email protected].
2. What we collect
- Account data: email address, display name, @handle, avatar and bio. If you sign in with Google, we receive the email, name and picture of your Google account.
- Private details: birth date and country, asked once when you join. We use them to apply the minimum age and the protections for readers under 18. Other readers never see them.
- Reading data: the books on your shelves, reading progress and reading time, notes, highlights, bookmarks, ratings, reading goals and favourite genres and authors. Books you open from your own files stay on your device; we do not upload them.
- Community content: messages, board posts, replies, polls, reactions, voice messages and images you share in clubs, groups and chats; friendships and blocks; reports you make and reports about you.
- Device and usage data: app version, platform, app language, a push-notification token, and when and how long the app is used, so we can show your reading statistics, keep the app working and fix problems.
- Purchases: if you subscribe to Borgiana Pro, Google Play or Apple handle the payment. We receive whether your subscription is active and its type, never your card details.
- Beta access: the invite code you used, if you joined during the closed beta, or the email you left on the waitlist before Borgiana opened to everyone.
- How you found us: when you join through a club or group link another reader shared, we record which reader's link brought you. We use it to understand how readers find Borgiana.
- Messages to us: what you send when you contact support, suggest a book or report a problem.
3. Why we use it, and on what basis
- To provide Borgiana — your account, library, progress, clubs, chat and notifications (performance of our agreement with you, the terms of use).
- To keep readers safe — age rules, protections for minors, reviewing reports, removing content and sanctioning abuse (our legitimate interest in a safe community, and legal obligations).
- To send push notifications — only if you allow them; you can turn them off in Settings or on your device (your consent).
- To send account emails — sign-in codes, confirmations and password resets (performance of the agreement).
- To understand and improve the app — aggregated usage and error information (our legitimate interest).
- To comply with the law — for example, answering valid requests from authorities.
We do not sell your personal data, we do not show third-party ads, and we do not use your data to build advertising profiles.
4. Who processes it for us
We use these service providers, who process data only on our instructions and under their own data protection terms:
- Supabase — database, sign-in and file storage (servers in the United States).
- Google — Google Sign-In, Firebase Cloud Messaging for push notifications, and Firebase Hosting, which serves the files of the web app (borgiana.com/app).
- Resend — sending account emails.
- RevenueCat, Google Play and Apple — subscriptions.
- Cloudflare — the borgiana.com website and our email addresses.
Some features call outside services directly. They receive what the feature needs and, like any website, your device's IP address, but never your account or profile:
- Book and author catalogues — Open Library, Google Books and Wikidata, to search books and show covers and author details. They receive your search terms.
- Reader tools — when you look up a word or translate a passage in the reader, the selected text is sent to Google Translate, MyMemory, Datamuse or Wiktionary.
- Cover images on the web — some covers are loaded through the wsrv.nl image service so browsers can show them.
We may disclose data when the law requires it, or to protect the safety of readers.
5. International transfers
Your data is stored and processed in the United States and other countries where our providers operate, which may not offer the same level of protection as your country. These transfers rely on the providers' standard contractual clauses and security commitments, as allowed by Argentine law and the GDPR.
6. Who can see what
Your profile is visible according to the privacy setting you choose. Members of a club or group see what you post there, and club admins can read the reading rooms their club manages. For readers under 18 the handle is hidden, they do not appear in people search and strangers cannot message them.
7. How long we keep it
- Account, reading and community data: while your account exists.
- When you delete your account, your personal data is deleted at once. Club messages and posts remain under “Deleted User”, with no link to you, so conversations keep making sense. Reports keep their copy of the reported content, without your account, only as long as needed to keep readers safe. See how to delete your account.
- Waitlist emails left before the open beta: until we write to tell you Borgiana is open, or you ask us to remove them.
- Support messages: up to two years after the conversation ends.
8. Security
Data travels encrypted (HTTPS). Access in the database is limited by row-level security rules, private details are kept apart from public profiles, and staff actions are logged. No system is perfectly secure; if a breach affects you, we will tell you and the authorities as the law requires.
9. Your rights
You can access, correct, update and delete your data, and object to or restrict some uses of it. Under the GDPR you can also ask for a portable copy and withdraw consent at any time. Much of this you can do yourself in the app: edit your profile, change privacy and notification settings, export your library (Settings → Export library) and delete your account. For anything else, write to [email protected] from your account's email. We answer within the time the law sets (for example, 10 calendar days for access requests under Argentine law) and in any case within 30 days.
The AGENCIA DE ACCESO A LA INFORMACIÓN PÚBLICA, in its role as the Control Body of Law No. 25,326, has the power to handle the complaints and claims of those whose rights are affected by non-compliance with the rules on personal data protection. (La AGENCIA DE ACCESO A LA INFORMACIÓN PÚBLICA, en su carácter de Órgano de Control de la Ley N° 25.326, tiene la atribución de atender las denuncias y reclamos que interpongan quienes resulten afectados en sus derechos por incumplimiento de las normas vigentes en materia de protección de datos personales.)
The holder of personal data has the right to access it free of charge at intervals of no less than six months, unless a legitimate interest is shown (Law No. 25,326, art. 14). If you live in the European Economic Area or the United Kingdom, you can also complain to your local data protection authority. If you live in California, note that we do not sell or share personal information as those terms are defined by the CCPA.
10. Children and teens
Borgiana is for readers aged 13 and over, or the age of digital consent where you live if it is higher (for example, 14 in Spain and Italy, 15 in France, 16 in Germany and the Netherlands). The app checks this with the birth date and country you give when you join, and accounts below the minimum age are not completed. Readers aged under 18 get the protections described above. If you believe an account belongs to someone under the minimum age, write to us and we will delete it.
11. Cookies and local storage
We do not use advertising or tracking cookies. The web app stores your session and preferences (such as language and theme) in your browser's local storage so it can work.
12. Changes
If we change this policy in a way that matters, we will tell you in the app before the change applies. The effective date at the top shows the current version.