PRIVACY & BOUNDARIES
Your choice starts
with knowing.
The capabilities should be clear. So should the boundaries.
Last updated: October 1, 2026
This website
This is a static product website. It does not provide accounts, payments, or storage for product data. The site code includes no third-party analytics, advertising, tracking scripts, or contact forms. Fonts, images, and video do not rely on third-party content services.
Hosting and network providers may still process IP addresses and basic request logs according to the actual hosting configuration. External services, including GitHub, apply their own terms and privacy policies.
Each tool has its own data boundaries
Lumen Open is a collection of independent projects, not a shared account or unified data service. Desktop apps, local storage, self-hosting, and cloud processing can coexist.
Local does not mean fully offline. Cloud models, speech recognition, code review, and chat integrations may send relevant inputs to the selected providers. Read each project’s documentation and choose a configuration appropriate for your data.
Control begins with understanding permissions
Before installing, check the source, version, device architecture, and required permissions. Enable recording, screen or activity capture, and code access only when you understand their scope.
Confirm your permission to process other people’s voices, images, code, or personal information. AI-generated content, transcripts, and review findings still require human checking.
Clear availability and licensing
Descriptions reflect public repositories. Features in current source may not yet be available in packaged releases. Prereleases, source builds, and invitation-only hosted access are labeled separately.
Each project has its own license. Plan of Plan has not declared a license, so this website does not describe all nine projects as licensed open-source software. Consult repository license files before using or distributing code.
Questions and feedback
For questions about functionality, data processing, or security boundaries, follow the product page to its GitHub repository and read its documentation and feedback channels.
Never include API keys, passwords, raw recordings, or other sensitive material in a public issue.