Linten was engineered by Loopstates with a developer-first ethos: what happens on your computer stays on your computer. We do not sell your personal data, employ invasive third-party tracking scripts, or ingest your authored documentation into AI model training corpuses.
Linten operates on a strict processor-only, headless architecture. When integrating with customer platforms like Notion, Linten never retains or copies customer documents, notes, pages, or markdown text in any external persistent database. All document analysis, block parsing, and token budget calculations are executed in memory during the request lifecycle and discarded immediately.
When connecting third-party platforms (such as Notion via OAuth), Linten securely stores only the tenant connection tokens and workspace identifiers necessary to authenticate authorized API requests. Tokens are encrypted in transit and at rest and are used solely to perform actions explicitly initiated by the user (such as auditing link health, normalizing formatting, or compiling companion documentation).
When executing link health audits, Linten performs standard HTTP HEAD and GET requests against the URLs listed within your documentation to report HTTP status codes and latency. No payload or page contents from target endpoints are archived or cached permanently on our infrastructure.
You maintain complete control over your connected workspaces. You can revoke Linten's access at any time through your Notion workspace integration settings. Upon disconnection, associated authentication tokens are permanently purged from our routing layer.
For questions or verification of our privacy architecture, contact our engineering team at hello@loopstates.com or visit loopstates.com.