LITERUNICO · POLICIES
Privacy Policy
Version 2026-08-31.1 · Published August 31, 2026
English translation of the current Portuguese document. Account acceptance records the source document’s version and hash.
This Policy explains how Literunico processes personal data. Reading it is required at registration; optional consents remain separate and revocable.
1. Controller and contact
The controller is Literunico, CNPJ 43.408.163/0001-10, at Rua Professor Belfort Roxo, 410, Vila Pereira Barreto, São Paulo/SP, postal code 02936-030, Brazil. Data-subject and privacy requests may be submitted through Contact us.
2. Data processed
- Registration and identity: name, username, email, credentials, country, account confirmation, age or representation when necessary.
- Profile and content: photo, biography, works, chapters, posts, comments, reactions, messages, media, communities and visibility preferences.
- Reading and Living Books: access, progress, read chapters, current-reading markers, copy ownership, history, offers, transfers and identity choices.
- Commerce: orders, products, amounts, shipping, payments, refunds, payouts, invoices and transaction evidence. Full card details are processed by the payment provider where applicable.
- Technical and security: IP address, session and device identifiers, browser, logs, cookies, notifications and anti-fraud signals.
- Support and rights: support messages, reports, privacy requests and records of actions taken.
3. Purposes and legal bases
- Contract performance: creating accounts, authentication, publishing, reading, delivering purchases, transfers, payments, support and requested features.
- Legal or regulatory obligations: tax, accounting and consumer records, anti-money-laundering measures where applicable, and responses to authorities.
- Exercise of rights: preserving evidence, preventing abuse, resolving disputes and protecting the platform and its users.
- Legitimate interests: security, service improvement, aggregate metrics and recommendations, following an assessment of need and impact and without overriding the data subject’s rights.
- Consent: only for specifically identified optional purposes, such as marketing, identifiable disclosure of certain reading data or optional integrations.
4. Publicity, discovery, SEO and AI
Profiles and content set to public may be indexed by search engines and appear in Literunico recommendations and AI-assisted search. Private or restricted content should not deliberately be exposed through these features. External indexing may take time to reflect privacy changes.
5. Living Books, history and preserved initials
A choice to make an ownership period’s identity public is specific to that period and remains associated with it. Without permission, we display only an initial, without a name or link. Account deletion disables public identity; the recorded initial may remain as minimised data to preserve the historical chain. Transactions, text and images may remain where required by law, third-party rights or defence needs, with minimisation wherever possible.
6. Reading and sharing with authors
The system may record the progress needed to resume reading and establish access. Identifiable sharing of read chapters with an author or rights holder depends on a specific control and remains off by default where indicated. Aggregate or anonymised data may be used for statistics without identifying the reader.
7. Sharing
We share only what is necessary with hosting, storage, email, notification, security analysis, payment, logistics and support providers; with authors, sellers or buyers as needed for the operation; and with authorities where there is a legal basis. We do not sell personal data as contact lists.
8. International transfers
Some providers may process data outside Brazil. We seek providers with appropriate contractual and technical measures and observe the applicable legal mechanisms for international transfers.
9. Cookies and similar technologies
Strictly necessary cookies support sessions, security and essential preferences. Measurement, personalisation or advertising cookies, where present and based on consent, must offer choices by category and a way to withdraw consent.
When you authorise optional cookies, Literunico uses Google Tag Manager to load measurement configuration and Google Analytics 4 to understand, for example, visited pages, traffic sources, device type, interactions and site performance. These services remain disabled until authorisation and may use their own identifiers and cookies. Authorisation may be withdrawn at any time in Privacy and Authorisation Settings.
Google’s processing follows its Privacy Policy. See also how Google uses information from sites and apps that use its services.
10. Children and teenagers
Processing must respect their best interests, privacy by default, responsible supervision and age-assurance measures proportionate to risk. Children’s and teenagers’ data must not be used for prohibited behavioural advertising. Where the law requires guardian consent or participation, the corresponding process must be completed before processing.
11. Retention and deletion
We retain data as needed for the account, the stated purpose and legal retention periods. After deletion, we delete or anonymise what need not be kept. Tax, transaction, anti-fraud, consent and defence records may remain for the applicable period, with restricted access. Backups are deleted according to the secure technical cycle.
12. Security and incidents
We use access controls, logs, credential protection, backups and monitoring appropriate to the risk. No system is infallible. Significant incidents will be assessed and reported to data subjects and Brazil’s ANPD when required.
13. Data-subject rights
You may request confirmation and access, correction, information about sharing, portability where regulated, anonymisation, blocking or deletion of irregular data, objection, review of automated decisions, withdrawal of consent and information about the consequences of withholding consent. We may need to confirm your identity and observe legal exceptions.
14. Acceptance records
We store the version and hash of accepted documents, date, source flow and technical hashes of the IP address and browser. These hashes help establish the event without retaining the raw values in that record. This Policy does not make optional purposes mandatory.
15. Updates
This version takes effect on the indicated date. Material changes will be highlighted and may require renewed acknowledgement or acceptance, depending on the change and its legal basis.