TINMOON
JPEN

Privacy Policy

Librino Privacy Policy

Last updated: October 14, 2026

TINMOON ("we") provides the Windows application Librino (the "App"). This policy explains how the App handles user information.

1. Our approach

Librino is designed to keep a personal book library on the user's own PC. Bibliographic data, reading records, tags, notes, cover images, and settings are stored locally by default. We do not include advertising, behavioral analytics, tracking for sale, or our own crash-reporting service.

2. Information handled by the App

The App handles information that the user enters, adds, edits, or imports, including:

  • bibliographic information such as title, author, publisher, publication date, ISBN, and source product URL;
  • reading status, ratings, tags, start and finish dates, and reading notes;
  • user-created bookshelves and shelf membership;
  • cover images provided by the user;
  • settings such as interface language, theme, and integration permissions;
  • backup and export files; and
  • connection information when the user enables Notion integration.

3. Local storage and security

The library, covers, settings, and diagnostic log are stored on the user's PC. Notion access tokens are stored using Windows data protection.

When bibliographic retrieval fails, the diagnostic log may record the time, service, ISBN, a fixed failure category, and a numeric status. New diagnostic records do not include product URLs, credentials, response bodies, or raw error messages. Because the log may contain an ISBN, users should review it before sharing it publicly.

Backups and CSV, JSON, or Markdown exports saved outside the App are controlled by the user.

4. Communications with external services

The App communicates with external services only when required for a feature the user invokes.

Book details and covers

When the user adds a book or refreshes its details, the App may send an ISBN or the product URL pasted by the user to openBD or the corresponding supported bookstore website. Retrieved book details and covers are stored on the user’s PC.

When the user presses the cover-search button, or adds a book while Search for a cover image after adding is enabled, the App opens a Google Images search containing terms such as title, author, and ISBN in the default web browser. This post-add search is enabled by default and can be disabled in Settings. The privacy policies of Google and the browser apply to that activity.

Notion integration

Notion integration is optional. It begins only when the user starts the connection and grants access in Notion. The authentication relay uses Cloudflare Workers and KV to temporarily store a session ID, a hash of the exchange secret, the authorization token response received from Notion, and related temporary authorization data. The relay deletes the corresponding data when the App receives it, and unclaimed temporary data has a ten-minute time-to-live. Book details, reading notes, and cover images do not pass through the authentication relay.

Only when the user selects Send to Notion does the App send the selected bibliographic data, reading records, tags, notes, and covers directly from the PC to the Notion API. There is no automatic synchronization. Information sent to Notion is subject to Notion’s privacy policy.

MCP integration

Connections to MCP-compatible apps such as Codex or Claude Code are optional. Librino provides library information through a local MCP connection configured by the user. Reading or editing memo contents is enabled only when the user explicitly allows it for that connection.

Whether the connected AI app sends information to an external AI service depends on that app’s settings and provider policy. Users should review the connected app and sharing permissions before use.

5. Purposes

The information is used to create, display, search, and organize the user's library; retrieve book details; create or restore backups; export data; and perform integrations selected by the user. It is not used for advertising, user profiling, or sale to third parties.

6. Disclosure to third parties

We do not sell or provide user information to third parties except where required by law. When the user explicitly uses bibliographic retrieval, Notion transfer, or MCP integration, information is sent to the relevant service only as described above.

7. User controls and deletion

Users can edit or delete bibliographic data, reading records, tags, notes, covers, and bookshelves in the App. Deleting a book changes the current library; it does not automatically delete existing backup ZIP files, safety ZIP files created before a restore, exports, or diagnostic logs. Those files and logs must be managed or deleted separately. Users can disconnect Notion in Settings, which removes the local connection information. Pages already sent to Notion must be managed or deleted by the user in Notion.

Uninstalling the App does not automatically delete backups or export files that the user saved elsewhere. Users should delete those files separately if desired.

8. Children's information

The App is not designed to collect personal information from children. Users below the age at which parental consent is required should use the App under the supervision of a parent or guardian.

9. Changes to this policy

We may update this policy when features, external services, laws, or Microsoft Store policies change. Material changes will be announced on the official website or through information provided with the App.

10. Contact

  • Provider: TINMOON
  • Website: https://tinmoon-label-site.pages.dev/

Contact: tinmoon.label@gmail.com

← Back to the Librino page