Privacy Policy

1) General principles

Firefly — Reading Journal is built around local-first storage. Core reading data is stored on the user's device. The app has no advertising.

2) Data stored by Firefly

• On the device: library, notes, quotes, reading progress, statistics, voice notes, images/covers and local backups created by the user.
• Google account: if Google Drive backup is enabled voluntarily, Google Sign-In may be used for authorization and to show the signed-in email in the interface.
• Firefly catalog: bibliographic metadata about works and editions, such as title, author, ISBN, publication year, publisher, format, language, page count, cover and series relations.
• Voluntary server actions: book ratings, reviews, proposed bibliographic corrections and a donor name only when publication was explicitly permitted.

Firefly does not upload the user's private reading library to the Firefly server as part of normal use.

3) Data we do not normally collect

During ordinary use, Firefly does not request passport, payment or postal-address data. Name and delivery address may be requested separately from a confirmed raffle winner only when a physical prize requires delivery.

We do not sell data to third parties and do not use advertising identifiers. If paid features are introduced through Google Play, payment-card data is processed by Google rather than stored by Firefly.

4) Internet and external services

• Internet access may be used to search bibliographic metadata through public APIs or the Firefly API.
• The Firefly server can receive ratings, reviews and proposed catalog corrections only following a user's voluntary action.
• The app may read the public Monobank fundraising total without receiving donor payment data.
• The SVH Group website uses its own aggregate counters for page views and direct APK downloads. Google Analytics, advertising cookies and third-party advertising trackers are not used for these counters; website statistics are separate from the mobile app.

5) Firefly Book of the Year and the voluntary raffle

• Voting and a raffle application are separate actions. Withdrawing from the raffle does not remove or change a vote.
• To protect voting integrity, the server may process the vote, season/category, a technical installation/user identifier and installation-authenticity checks.
• A vote does not require contact details. Contact information is entered only when the user separately and voluntarily joins the raffle.
• Supported contact channels: Email, Telegram, phone, WhatsApp or Viber.
• The contact is stored in encrypted form. Client or administrative interfaces may use a masked representation.
• Each active raffle entry receives a stable public code that can appear in public lists or results without exposing the full contact.
• The 2026 season has three separate prize slots. Only the information required to contact and fulfill a specific winner's prize is retained.
• Name and delivery address are requested only from a confirmed winner when a physical prize requires delivery.
• If delivery of a physical prize outside Ukraine is separately agreed for a confirmed winner, only the additional data necessary for that agreed delivery method is processed.
• Full contact details, names and delivery addresses are never published in participant lists, results or the historical archive.
• Raffle data is deleted or anonymized after the season and the required retention period. The archive keeps only public results.

Read the full raffle rules →

6) Backups and user control

The user decides whether to create local or cloud backups and is responsible for storing them safely. Removing data from the app or withdrawing optional participation does not automatically change unrelated server records unless the relevant feature specifies it.

7) Contact

Questions about privacy can be sent to svhgroupua@gmail.com or via Telegram.