RedLark Clipper icon RedLark Clipper Local-first privacy

Policy / User data

Privacy,
in plain view.

RedLark Clipper processes the page you choose and delivers it to your own Obsidian vault. This page explains every step.

Effective September 1, 2026 Product RedLark Clipper Delivery Local Obsidian vault Developer server None for captured content
Our operating principle

Your capture is initiated by you, processed for the feature you requested, and delivered to storage you control.

Single purpose

RedLark Clipper's single purpose is to save the current web page to a local Obsidian vault. It provides dedicated capture and local-attachment handling for Xiaohongshu and Feishu/Lark pages and standard clipping for other web pages.

Data the extension handles

Depending on the page the user chooses to capture, RedLark Clipper may process:

  • the current page URL, title, text, links, images, media references, and selected content;
  • Xiaohongshu post content, comment text, commenter display names, images, and engagement information visible or loaded on the current page;
  • Feishu/Lark document content, images, attachments, comments, and resources available to the signed-in user;
  • a Feishu/Lark CSRF cookie required to request the current authenticated document;
  • user-created templates, highlights, clipping history, reader preferences, extension settings, and retry metadata; and
  • a local import payload containing the note and its attachments when delivering the capture to Obsidian.

This may include personally identifiable information, authentication information, personal communications, web-history information, and website content, depending on the page selected by the user.

When data is accessed

Page content is processed only for a user-facing action, such as clicking the extension button, using an extension keyboard shortcut, selecting an extension context-menu command, or using the reader or highlighting tools.

The extension does not continuously monitor the clipboard or build a background profile of the user's browsing activity.

How data is used

The extension uses this data only to:

  • extract and convert the current page into Markdown or another user-requested local format;
  • retrieve images, attachments, comments, and resources required for the capture;
  • preview, edit, highlight, or read the selected page;
  • deliver the user-approved note and attachments to the user's local Obsidian vault; and
  • retain user settings, templates, local history, highlights, and retry state.

RedLark Clipper does not use user data for advertising, creditworthiness, lending, profiling, or purposes unrelated to its single purpose.

Data transmission and sharing

RedLark Clipper does not upload captured content to a server operated by the RedLark developer and does not sell user data.

To provide user-requested clipping features, the extension may communicate with:

  • the source website and its resource hosts, such as Xiaohongshu, Feishu/Lark, YouTube, or another page selected by the user;
  • RedLark Receiver at http://127.0.0.1:27124 on the same computer;
  • Obsidian through an obsidian:// local application link if the local receiver is unavailable; and
  • Chrome Sync, when enabled by the user, for settings and templates stored through Chrome synchronized storage.

The extension does not transfer user data to third parties except as necessary to provide these features, comply with applicable law, or protect against security abuse.

Cookies and authentication

When the user captures an authenticated Feishu/Lark document, RedLark Clipper reads the relevant CSRF cookie from that Feishu/Lark domain and uses it only to request the selected document through the user's existing session.

The extension does not store that cookie in its own persistent storage or send it to the RedLark developer.

Clipboard use

RedLark Clipper writes to the clipboard when the user explicitly chooses a copy command. If RedLark Receiver is unavailable, the extension may temporarily place a local import payload on the clipboard and open an Obsidian application link as a compatibility fallback.

The extension does not read or continuously monitor clipboard contents.

Storage and retention

Captured notes and attachments are stored in the Obsidian vault selected by the user and remain there until the user deletes them. Extension settings, templates, highlights, clipping history, reader preferences, and retry metadata may be stored in Chrome local or synchronized storage.

The RedLark developer does not retain copies of captured content. Users can remove extension-stored data by clearing the extension's data or uninstalling the extension. Notes and attachments can be deleted directly from the user's vault.

Security

Remote website requests use the security provided by the source site's HTTPS connection. Communication with RedLark Receiver uses the loopback interface and is limited to the same computer.

Executable JavaScript and conversion libraries are packaged with the extension; remote responses are handled as data and are not intentionally executed as remote code.

Children's privacy

RedLark Clipper is a general productivity tool and is not directed to children. The extension does not knowingly collect children's data for the developer.

Changes to this policy

This policy may be updated when RedLark Clipper's behavior or legal obligations change. The effective date at the top of this page will be updated when material changes are made.

Contact

For privacy questions or data-related requests, contact larrybiu.dev@gmail.com.

Chrome Web Store Limited Use

RedLark Clipper's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.