lok.computer privacy information
This page explains what the lok.computer web application stores locally, which network services it contacts, and where to send privacy questions.
Browser storage
lok.computer does not require a visitor account. The desktop stores application state, cached API responses, usage counters, preferences, and restorable window state in the visitor's browser using IndexedDB or related browser storage. This local data is used to restore the interface and reduce repeated network requests. It remains under the browser profile's control and can be removed with the browser's site-data controls. Clearing it may reset preferences, windows, and cached content.
Network requests and third parties
Using an application can send requests to lok.computer's Cloudflare-hosted site and API, and to public upstream services used by that application. Those services may include Are.na, Bluesky, a fediverse server, NeoDB, weather providers, and websites opened by the web viewer. The Ask AI application sends the request and any pasted content to the server-configured planner model and to TypeSafe's Jev decision model. Do not enter confidential, regulated, or personally sensitive information into it. Upstream providers and Cloudflare process requests under their own terms and privacy practices.
Like most hosted sites, infrastructure providers may process technical request information such as IP address, user agent, requested URL, timestamps, and security signals to deliver the site, prevent abuse, and diagnose failures. lok.computer does not publish or sell a visitor profile and does not expose browser-local desktop state through its public API. Public social and media data shown by the site remains subject to the source service's controls and may change or disappear upstream.
Questions and scope
For a privacy question or a request concerning data controlled directly by lok.computer, email l3on@duck.com with the relevant URL and details. Requests about content or accounts hosted by an upstream service should be directed to that service. This information describes the current public project as of 2026-08-24 and should be reviewed when storage, analytics, authentication, or API behavior changes.