Privacy Policy

Last updated October 13, 2026

Lispa processes information to run your agents, maintain your workspace, and provide the service. This page explains what that includes and the choices you have.

Information we handle

• Account information: your username, sign-in details, profile information supplied by Google if you use Google sign-in, organization membership, and preferences.
• Your work: connected repository content, prompts, conversations, files, tool output, generated results, and saved workspace knowledge. These may contain personal information you or your team provide.
• Connected services: credentials and information you authorize Lispa to access through code hosts, model providers, and other integrations.
• Billing and support: subscription and credit records, payment status, billing details, and messages you send us. Stripe processes card payments; Lispa does not store full card numbers.
• Operational information: requests and security logs, which may include IP addresses, device information, errors, model usage, and machine runtime.

How we use it

We use this information to sign you in, run tasks, preserve work across sessions, calculate charges, respond to support requests, prevent abuse, and maintain and improve reliability. We also keep records needed for legal obligations and resolving disputes.

Where data protection law requires a legal basis, we rely on performing our agreement with you, legitimate interests in running and securing Lispa, legal obligations, and consent for optional analytics. For work an organization asks us to process on its behalf, that organization directs the use of its content.

AI providers and other services

Running an agent sends relevant prompts, code, files, and tool results to the selected or routed model providers. Their retention and data-use policies depend on the provider, model, and account you use. This also applies to your own API keys and subscriptions. Saved workspace knowledge lets future agents reuse context from earlier tasks.

We use service providers to operate Lispa, including Google Cloud and Modal for infrastructure, Stripe for payments, Intercom for support chat, and PostHog EU for optional analytics. Connected code hosts and other integrations receive information needed for the actions you request.

Content shared with your team is available according to workspace permissions. We may also disclose information when legally required, to address fraud or security threats, or as part of a business transfer subject to applicable privacy protections. We do not sell personal information.

Cookies and analytics

Cookies and browser storage keep you signed in and remember preferences. On the signed-in platform, Intercom connects automatically to deliver support replies and show unread messages. On the landing page, it connects when you open support.

For support and onboarding, we share your account identifier, username, verified email when available, signup date, and whether you have started a task with Intercom. This status can update while you are offline. Your task content, repository code, and credentials are not included. Intercom also processes messages you send to support and the browser information needed to deliver them. You can unsubscribe from onboarding emails using the link in each email.

Optional PostHog analytics starts only after you allow it. It measures visits and feature use, including account activity from connected agents and background jobs. Signed-in events are linked to your Lispa username. We do not send code, chat content, credentials, payment details, or screen recordings to analytics.

You can decline or withdraw analytics using the Privacy button on the homepage or app. See Analytics choices for what is collected, retention, and how browser privacy signals work.

Storage and security

For signup trials granted before October 13, 2026, we keep hashed versions of the verified Google identifier and email, the organization identifier, and the trial’s grant and expiry dates. This minimal claim record remains after account deletion.

We retain information for as long as needed to provide the service and for security, billing, and legal obligations. The period depends on the type of data, account status, and why it is needed. Backups and required records may remain after an account closes; usernames remain reserved to prevent reuse.

Lispa uses access controls and encryption for stored credentials. No service can guarantee absolute security. Our providers may process information in countries other than yours, including the United States, where privacy laws may differ.

Your choices and rights

You can update account settings, disconnect integrations, and change analytics preferences. Contact tedj@lispa.ai to request access, correction, export, or deletion of personal information, or to close your account. We may verify your identity before acting.

Depending on your location, you may also have rights to object to or restrict processing and complain to your local data protection authority. If your organization controls the information, contact its administrator too. Disconnecting an integration does not erase copies already held by that provider.

Children, updates, and contact

Lispa is intended for adults, not children under 18. Contact us if a child has provided personal information. We will update this page when our practices change and notify you of material changes through the service or your account contact details.

For privacy questions, email tedj@lispa.ai.