Cookies and private sessions

Public pages have no tracking. Private sign-in uses a short-lived session.

In short

Public Settlens pages and free tools use no tracking cookies or browser storage. Signing into private monitoring sets one HttpOnly, Secure, SameSite=Strict cookie, scoped to the monitoring API and expiring after one hour. No analytics or advertising runs.

On this page

Public pages and free tools

Public pages, the pilot form and the MCP endpoint set no cookies. Scripts use no local storage, session storage or IndexedDB. There is no analytics, advertising pixel, session recording or third-party browser resource.

Private monitoring session

After you sign in to the private monitoring workspace, the server sets settlens_monitor. It contains an opaque random session identifier, not an access token, email address or payment data. Sign-in can use a one-time code emailed only to contact@settlens.com; that code expires after ten minutes and is consumed on use. Its purpose is to authenticate monitoring API requests.

  • Path: /api/monitor.
  • Lifetime: one hour; signing out revokes the session and clears the cookie.
  • Flags: HttpOnly, Secure, SameSite=Strict.
  • Sessions are held in server memory and disappear when the server restarts.

The workspace requires JavaScript. CLI monitoring and history exports are also available.

Browser resource policy

HTTPContent Security Policy
default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; object-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests; require-trusted-types-for 'script'; trusted-types 'none'

Server-side data

Pilot submissions, private monitoring observations and technical error logs are described in the privacy notice. Email notifications, when enabled, go to contact@settlens.com through our Hostinger mailbox.

Last updated Oct 14, 2026. Contact contact@settlens.com with questions.