Privacy, in concrete terms

lattedit is local-first. This page explains each place data can go so users and agents can make an informed decision before placing a document in the editor.

Projects stored in the browser

Without sign-in, project metadata, source files, uploaded assets, and the last compiled output are stored in IndexedDB for the current site in the current browser profile. Theme and layout preferences use local browser storage. Clearing site data, using private browsing, or browser storage eviction can delete this material. Exporting a ZIP is the reliable way to keep a separate copy.

Files sent for compilation

When Compile is pressed or automatic compilation runs, the complete project is sent over HTTPS to the lattedit compilation service on Render. TeX cannot produce a PDF without reading those files. The service writes them into a randomly keyed temporary workspace, disables shell escape, restricts file paths, and removes idle workspaces after ten minutes. Workspaces also disappear when the free service restarts or redeploys. Do not submit secrets or documents whose processing by this hosted service is unacceptable.

Optional account sync

Supabase account and project synchronization is inactive unless authentication is configured and the user signs in. When active, signed-in project copies are stored under that account and protected with row-level security. Anonymous browser projects are not silently uploaded. Google authentication may be added as an identity provider, but signing in remains optional.

Analytics

Microsoft Clarity is used to understand page reliability and interaction patterns. Advertising storage is denied and analytics storage is granted. The Clarity project should use strict masking so editor and document text are not recorded. Analytics does not replace project storage and is not used to sell document content. Browser privacy controls and content blockers may restrict the analytics request.

Compile API and logs

API requests pass through Vercel and Render infrastructure, which may process standard operational data such as timestamps, IP addresses, user agents, request paths, status codes, and latency. Compile responses include TeX logs and PDFs for the caller. The service does not promise permanent retention of requests or outputs. Questions and privacy reports can be raised through the paths on the contact page.