LynxWorks · Public information

Privacy

What LynxWorks handles when you bring product context into a project.

Effective October 6, 2026

Website activity

We record homepage visits, the first interaction with the input field, successful Room creation and saved-message events. We do not collect text before you submit it. Traffic records and operator email alerts contain event metadata rather than message content.

Where the hosting service provides a verified address, we use the public IP to group activity and exclude internal traffic. An IP may be shared by several people or change over time; it does not identify a customer. Traffic-monitor records are retained for 30 days. An internal-browser cookie or an administrator's IP exclusion suppresses notifications; excluded IPs are kept on the exclusion list until removed. Operational hosting logs and project records have separate retention.

What we handle

When you use LynxWorks, we receive the project details, selected conversation snippets, links and files you choose to send. The service stores private project sources and canonical Work, including revisions and decision context. It also stores raw model output and processing receipts used to explain and troubleshoot what happened.

We record timestamps, pseudonymous project and event identifiers, and usage and cost receipts for correctness, abuse control, support and service accounting. A pseudonymous analytics session identifier is stored in your browser for session correlation. IP-derived hashes may be held in memory for abuse throttling for up to one hour.

How content is used and shared

We use submitted content to prepare and continue your project work, maintain the service, investigate failures and provide support. Relevant task content is processed by our hosting and database services and configured model providers. An authorized LynxWorks operator may access project data and diagnostics for support and operations.

Send only the snippets relevant to the task. You do not need to send an entire chat history. Do not submit passwords or other credentials, identity document numbers, payment card details, protected health information, or other sensitive personal data.

Access and retention

Anonymous access uses a 256-bit bearer capability valid for seven days. Expiration, rotation or revocation of that capability affects access only; it does not delete the underlying project, sources, Work, model outputs or receipts. We do not currently have a fixed automatic purge period for project data. It is retained until an operator-approved deletion.

There is no self-service deletion. To request a review or deletion, email jarvis@lynxworks.ai without sending the capability secret. We verify project authority through an existing live access tool or another secure channel before taking project-level action.

Questions

For questions about this notice or a data request, contact jarvis@lynxworks.ai.