Production disclosure
Subprocessors
These services process data when you use llibrary. Repository providers only receive requests after you choose content hosted by that provider.
| Provider | Purpose | Data category | Status |
|---|---|---|---|
| Cloudflare | Pages and Workers hosting, D1 and KV storage, rate limiting, and Workers AI | Application traffic, account identifiers, hosted and indexed note content, AI questions and context, and short-lived OAuth state | In production |
| Clerk | Authentication and account management | Account identifiers, authentication metadata | In production |
| GitHub / GitLab | Repository reads and write-back when selected by the user | Repository metadata and user-authorized repository content | User-selected |
PDF export and Cloudflare Browser Rendering is disabled
The API contains a PDF export route that would send a note’s rendered content to Cloudflare Browser Rendering, a Cloudflare-hosted headless browser. That route is disabled in every deployed environment, so no note content is sent to Browser Rendering. Should PDF export be turned on, this page will list Browser Rendering as a subprocessor before it processes any user data.
Configuration-dependent error monitoring
The API includes an optional Sentry error-monitoring integration. It does nothing unless a Sentry DSN is configured. This repository’s production secret gate neither requires nor verifies that setting, so this repository cannot establish whether Sentry receives production data.
About this list
This engineering-verified disclosure was updated for v0.1.22 on July 31, 2026 and remains subject to legal review. Web fonts are self-hosted. Changes will be posted here before a new subprocessor begins handling user data.