Privacy notice

Aggregate visit statistics

The library measures successful visits to public pages to understand use and improve the service. It records daily page views, visits separated by 30 minutes of inactivity, daily measured browsers and totals per public page. A browser is not a person: multiple devices, deleted or blocked cookies and undetected automation can affect counts. History starts when measurement is activated; earlier traffic is not reconstructed. Administration, sign-in, private pages, recognised robots and prefetch requests are excluded.

This first-party counter uses __Host-utopia-stat, a random Secure, HttpOnly, SameSite=Lax cookie lasting at most 24 hours and rotated at the UTC day boundary. A daily hash and last-seen time prevent duplicate counting; these keys are not linked to accounts or page histories, and are excluded from backups. Keys older than 24 hours are removed during counting, report access and daily maintenance; cleanup can be delayed if all these operations are unavailable. Aggregate daily totals are retained for historical comparison. No IP addresses, browser fingerprints, search queries, referral URLs, email addresses or advertising identifiers are stored in these statistics. No Google Analytics or external advertising tracker is used. Hosting providers process technical requests under their own policies.

The purpose is limited first-party aggregate audience measurement, based on the operator’s legitimate interest in understanding service use, without individual profiling or cross-site advertising. You can exclude this browser below without losing any library feature. The exclusion cookie utopia_stats_optout lasts one year; deleting it removes that preference. Do Not Track and Global Privacy Control signals are also respected. Changing the preference affects future visits, not existing aggregate totals. Counts are visible only to the administrator.

1. Controller and contact

The individual operating Utopia Library in Italy, identified in the operator panel, determines the purposes of this application’s processing and is its data controller. Contact contact@utopialibrary.com or use the private contact form for privacy matters. The website’s brand is not a separate legal entity. No data-protection officer, certification or contractual arrangement with a provider is claimed merely by publishing this notice. If the operator panel cannot load, the contact email remains available to request the identifying details.

2. Data and where it comes from

Google or email sign-in through Firebase Authentication, and optional native Sites / ChatGPT sign-in, supply a user identifier and the account name and email made available to the application. The identifier links books, likes, comments, saved lists, contest entries and requests to the account. Email passwords and password recovery are handled directly by Firebase Authentication; our application database stores no password. We receive a signed identity token, verified email status and optional display name. ChatGPT passwords are entered only at its provider. You supply book metadata, pen name, excerpts, covers, optional PDF/EPUB files, AI declarations, public author profile and links. The system records revisions, publication status, rights and terms acceptance, the declared 18+ status and their dates; an age declaration is not documentary age verification.

Comments include text, replies, spoiler flags and dates. Private reports and cases include the subject, message, relevant book/comment, status and administrator response. Contest records preserve the submitted version and rules. Promotion/support orders store the selected service, price, acceptance version, scheduling, reasons and verified payment/refund identifiers, amount, currency and dates. We have no application fields for card numbers, IBANs or payment passwords. Access and security infrastructure may process IP addresses, request metadata and technical logs under its own configuration.

3. Purposes and legal bases

Providing the functions you request—account access, publication, saved lists, discussions, contest participation and order preparation/performance—uses data necessary for the service relationship or pre-contractual steps you request (GDPR Article 6(1)(b)). Required identifying or content data cannot be omitted if that makes the selected function impossible; browsing public pages does not require submitting a book or order. Public profile fields, excerpts and comments are published because you choose those functions, not because this notice requests blanket consent for unrelated use.

Abuse prevention, access controls, duplicate-request recovery, moderation, evidence of decisions and protection of claims rely on legitimate interests in a safe and accountable service, balanced against your rights (Article 6(1)(f)). Records required by applicable accounting, tax, consumer or legal obligations rely on Article 6(1)(c), only where the obligation actually applies. If a separate optional use requires consent, it must be requested specifically and can be withdrawn for the future. We do not treat acceptance of terms as consent to marketing, AI training or unrelated data sharing.

4. Public and private information

Published book presentations, selected excerpts, covers, author profiles and visible discussions are public. Comments show the available account name or a fallback reader name, not your email; your pen name on a book may differ. Public likes show totals rather than a list of voters. Approved sponsored placements display only the book or sponsor information selected for publication. Private saved lists, unapproved/hidden works, reports, support cases, order/payment records and administrative logs are restricted to the authorized user and administrator as appropriate. Published contest results can include title, author, place and editorial note.

5. Providers, recipients and international processing

The deployment uses Sites/OpenAI for the site service and native ChatGPT authentication, and Cloudflare infrastructure for application execution, database and file storage. Google/Firebase processes the selected Google or email authentication, verification and password recovery. Google Analytics is not enabled for this project. Stripe processes hosted checkout and payment data on its own service; any configured PayPal links are separate provider services. External bookshops and destinations are independent sites. We disclose necessary information to these services to deliver the selected function, and to authorities only where legally required or justified. We do not label every provider a processor: its controller/processor role depends on the actual service and applicable agreement.

Operator review still required: the exact contracting entities, subprocessors, processing countries, retention arrangements and international-transfer safeguards for this deployment must be checked and documented against the applicable provider contracts. This notice does not claim EU-only storage, an executed data-processing agreement, standard contractual clauses or an adequacy mechanism merely because a provider offers them. Where data leaves the EEA, an applicable GDPR transfer basis and any necessary supplementary measures must be established. Ask the operator for the documented recipients and safeguards; this outstanding review is not represented as completed compliance.

6. Retention and deletion

We retain active account and publication records for the requested service, then assess what remains necessary for unresolved support, rights disputes, legal claims, fraud prevention and applicable legal retention duties. Financial evidence is retained for the statutory period that actually applies to the operator, not an invented universal period. Contest snapshots, acceptance records, previous revisions and moderation logs may need restricted retention to explain decisions or defend rights. Backups and technical copies have their own recovery lifecycle. Retention must be reviewed by necessity and purpose; there is no promise that hiding content or sending a deletion request immediately erases every database, historical file or backup.

Withdraw a book in the studio to stop new public access. Use the private deletion request for account or stored-content removal and the account export for a machine-readable copy. The administrator must assess and respond, including any justified records that must remain. Browser preferences and request recovery records are managed separately as described in Cookies. Keep your own file copies; removing public access cannot recall copies lawfully downloaded by readers.

7. Your rights and response times

Where the GDPR applies, you can request information and access, correction, erasure, restriction, portability where its conditions are met, and object to processing based on legitimate interests. You may withdraw any optional consent for the future without affecting prior lawful processing. Rights are subject to their legal conditions; a request is not automatically granted or refused. We may seek proportionate identity verification when necessary, not extra sensitive documents by default. There are no application decisions with legal or similarly significant effects based solely on automated profiling; editorial and moderation decisions are reviewed by the administrator.

Send requests to contact@utopialibrary.com or the private contact form. Under the GDPR, a response is normally due without undue delay and within one month; where legally justified by complexity or number of requests, an extension of up to two further months requires notice and reasons within the first month. You may lodge a complaint with the Italian Garante per la protezione dei dati personali or another competent supervisory authority, and seek judicial remedies. Contacting us first is optional, not a prerequisite for a complaint.