Updated October 8, 2026
Optional analytics help us understand how people find Lispa, start using it, and use its features. We use PostHog’s EU service for this purpose.
Analytics starts only after you choose “Allow analytics.” Declining does not change how Lispa works. You can change your choice using the Privacy button on the landing page or platform. Your choice applies across lispa.ai and app.lispa.ai and is remembered for 180 days. When signed in, it also applies to your account’s server activity, including connected CLI usage and jobs that finish after you close the browser. We ask for a new choice when expanding from browser-only to account analytics. Browser Do Not Track and Global Privacy Control signals disable browser analytics and withdraw account consent when the signed-in browser next contacts Lispa.
With your permission, analytics cookies connect visits to the landing page and platform. We collect page categories, referring website domains, campaign labels, browser and device information, and named actions such as signing up, connecting a repository, starting a chat, creating an automation, or opening checkout. We record whether selected actions succeed or fail. Signed-in events are linked to your Lispa username.
Server events include successful and failed actions, chat and machine state changes, automation outcomes, connected agent usage reports, and confirmed payment/subscription outcomes. Opaque references connect related events without exposing repository or organization names. Payment outcomes come from verified billing records, not the checkout return page. Offline CLI activity that never reaches Lispa is not collected.
We do not send prompts, conversations, source code, repository names, file contents, passwords, API keys, payment details or amounts, or raw error messages. We remove query parameters containing account, task, invitation, and sign-in details. Screen recording and automatic collection of page text, clicks, and form inputs are disabled. IP addresses are not stored as analytics event properties; requests still pass through PostHog’s servers.
Analytics is accessible to Lispa’s authorized PostHog project members. Our current free plan retains analytics events for one year. Server events wait in Lispa’s delivery queue for at most seven days during an outage. A signed-in withdrawal clears pending account events and stops future account collection; a stale browser choice cannot re-enable it. An offline preference change reaches the account when connectivity returns. Withdrawal clears the analytics identity in that browser; it does not delete previously collected events.
See PostHog’s privacy information. This page describes optional analytics. Our Privacy Policy covers the operational data Lispa needs to provide your account, run tasks, and bill for usage.