Privacy policy

Lighthouse AI Technologies LLC ("Lighthouse," "we," "us," or "our") provides a business-metric monitoring service that connects to a customer's data warehouse or analytics tool, runs metric queries on a schedule, and sends alerts when a metric moves outside its expected range. This Privacy Policy explains how we collect, use, share, and protect information when you visit lighthouseai.co (the "Site"), use app.lighthouseai.co, our API, our MCP server, or any related services (together, the "Service"), or otherwise interact with us.

This policy covers three groups of people:

• Visitors who browse the Site, read the docs, or contact us.
• Users who create an account and use the Service on behalf of an organization (the "Customer").
• Individuals whose information appears in Customer Data (for example, a customer record inside a warehouse table that a metric queries). For that data we act as a processor or service provider on the Customer's instructions, as explained in Section 12.

This policy does not cover third-party websites, warehouses, or tools that you connect to the Service. Their own privacy policies govern their handling of your information.

Information you provide to us

• Account and profile information. When you sign up or sign in, our authentication provider (Clerk) collects and passes to us your name, email address, profile image (if you sign in through an identity provider that supplies one), and the identifier of the organization you create or join. We also record when your account was created and whether you have completed onboarding.
• Organization information. Organization name, members, invitations (the invited email address and the invitation's status), roles, and organization settings such as the AI model you select, notification preferences, and whether API or MCP access is enabled.
• Billing information. Paid subscriptions are sold by our payment partner, Paddle, which acts as merchant of record. Paddle collects your payment card or bank details, billing address, and tax information directly. We never receive or store full payment card numbers. Paddle sends us the subscription status, plan, seat count, and transaction identifiers needed to operate your account.
• Connection credentials. To run metrics we need credentials for the data sources you connect: PostgreSQL, Snowflake, BigQuery (a service-account key), Microsoft SQL Server, Mixpanel, or an HTTP endpoint. We store these encrypted (see Section 8). We never display them back to you in full once saved.
• Metric definitions and conversations. The metrics, filters, segments, thresholds, schedules, saved filters, and data sets you create, and the messages you exchange with the Lighthouse AI assistant, including any attachments you add to a conversation.
• Communications. When you email us, book a call, or submit the contact form on the Site, we collect your name, email address, company, your message, and (for the contact form) an analytics session identifier so we can see which pages you visited before writing to us.
• Referral information. If you share a referral link, we generate a referral token tied to your account. If someone signs up through it, we record that they were referred by you.

Customer Data we retrieve from your connected sources

The Service is built to retrieve as little of your underlying data as it can. When you connect a data source and create metrics, we retrieve and store:

• Schema metadata: table and view names, column names and data types, and the structure of the schemas you expose to Lighthouse. This powers autocomplete and metric setup.
• Distinct values of selected columns. For columns you use as filters or segment dimensions (for example, a country or plan column), we collect and store the list of distinct values so you can pick from them. If such a column contains personal data (for example, customer names or emails), those values will be stored with us. We recommend you do not use columns containing personal data as filters or segments.
• Metric results. The aggregated result of each metric run (the metric value, segment values, timestamps, severity, and whether the run triggered an alert), and the SQL we generated and executed, together with its start time, end time, status, and any database error message.
• Data previews. While you build a metric with the AI assistant, the assistant can request a bounded preview of up to 100 rows from the columns of a data set, so it can discover exact filter values. Those rows are transmitted to the AI provider (Section 5) and may be stored in our AI request logs. Previews are run only in response to your metric-building activity.

We do not copy, crawl, or replicate your tables, and we do not run queries other than those needed for the metrics, previews, and schema discovery you set up. Whether any of the above contains personal data depends entirely on what your warehouse holds and how you configure your metrics.

Information from integrations

• Slack. If you connect Slack, we receive your workspace identifier, the channels you choose, the names and identifiers of Slack users relevant to alert routing, and an access token. We store the alert messages we post and the interactions (button clicks, acknowledgements, feedback) taken on them, including the Slack identity of the person who acted.
• Identity provider. If you sign in through Google or another provider offered on the sign-in page, that provider sends us the profile fields listed above.

Information collected automatically

• Usage analytics. We use PostHog to record page views, page leaves, feature usage, and events in the Site and the Service. On the Site, PostHog identifies you only after you submit the contact form; in the Service, usage is tied to your account (email and name). Analytics records include IP address, browser type, operating system, device type, screen size, referrer, and timestamps.
• Advertising measurement. The Site loads the Google Ads conversion tag, which sets cookies and reports to Google that a conversion (such as a sign-up click) occurred. See Section 6.
• Server and security logs. Request logs, error logs, and trace identifiers that include IP address, user and organization identifiers, endpoint, and status code. For API keys we keep a call log with the endpoint, outcome, status code, originating IP address, and time of each request.
• Audit logs. A record of significant actions in your organization (who created, edited, or deleted what, and when) and of authentication events, so administrators and we can investigate problems and security incidents.
• AI request logs. For each call to an AI provider we store the request and response payloads, token counts, the model used, and whether your organization's own API key or ours was used. This lets us debug, audit cost, and investigate abuse.
• Cookies and similar technologies. See Section 6.

We use the information described above to:

• Provide the Service: authenticate you, run your metrics on schedule, evaluate thresholds, deliver alerts to Slack and email, show metric history, and operate the API and MCP server.
• Power AI features: generate SQL and metric configurations from natural language, suggest metrics, optimize thresholds, and answer questions in the assistant (Section 5).
• Manage your account and billing: enforce plan limits (number of metrics, monitoring frequency, seats), process subscriptions through Paddle, send invoices and receipts, and handle refunds.
• Communicate with you: transactional email about your account, alerts, security notices, policy changes, and responses to your requests; and, with your consent where required, product news and marketing that you can opt out of at any time.
• Secure and maintain the Service: detect, investigate, and prevent fraud, abuse, unauthorized access, and security incidents; enforce rate limits; debug errors; and keep audit trails.
• Improve the Service: understand which features are used, measure performance, and develop new features. We may create aggregated or de-identified statistics that cannot reasonably be linked to you and use them for any purpose.
• Measure marketing: understand which campaigns bring visitors to the Site, using the tools in Section 6.
• Comply with law: meet legal, tax, and accounting obligations, respond to lawful requests, and establish, exercise, or defend legal claims.

We do not sell your personal information, and we do not use Customer Data to train artificial-intelligence models of our own.

If you are in the European Economic Area, the United Kingdom, or Switzerland, we rely on the following legal bases:

Several features of the Service use large language models: natural-language metric creation, the metric assistant, metric suggestions, and threshold optimization. We use model APIs from OpenAI and Google (Gemini). Your organization's administrator chooses which model is used.

When you use an AI feature, the following may be sent to the selected provider:

• Your messages to the assistant and the conversation history.
• Schema metadata for the data sets involved (table and column names and types) and the distinct values collected for filter columns.
• Existing metric definitions, generated SQL, and recent metric results and alert interactions, where the assistant needs them to answer you.
• Data previews of up to 100 rows that the assistant requests to find exact filter values.

These providers process the data as our sub-processors under their business API terms, which do not permit them to use API inputs to train their models. They may retain inputs for a limited period for abuse monitoring under their own policies. We do not control those retention windows.

Bring your own key. Your organization may supply its own OpenAI or Google API key. In that case the provider processes your data under your agreement with it, and we store your key encrypted and use it only for your organization's requests.

AI outputs can be wrong. Generated SQL and suggested thresholds are proposals that you should review before relying on them. See the Terms and Conditions for the related disclaimers.

We use cookies, local storage, and similar technologies for the following purposes:

Your choices. You can block or delete cookies in your browser settings; blocking strictly necessary cookies will prevent you from signing in. You can opt out of Google's ad personalization at adssettings.google.com and install the Google Analytics opt-out add-on. You can also ask us to exclude you from analytics and advertising cookies on the Site at any time by emailing admin@lighthouseai.co.

We share information only as described here. We do not sell personal information and do not rent lists of users to anyone.

Sub-processors and service providers

We use the following third parties to run the Service. Each is bound by a contract that limits its use of your information to providing its service to us.

We will update this list when we add or replace a sub-processor. Customers with a data processing agreement will be notified as that agreement provides.

Other sharing

• Within your organization. Members and administrators of your organization can see your name, email, role, and the metrics, conversations, and actions you create or take in the organization, as permitted by their roles.
• Connected tools you choose. When you connect Slack or another integration, we send alerts and related data to it on your instructions.
• Professional advisers. Lawyers, accountants, auditors, and insurers under confidentiality obligations.
• Legal and safety. When we believe in good faith that disclosure is required by law, subpoena, or court order, or is necessary to protect the rights, property, or safety of Lighthouse, our users, or the public, or to enforce our agreements.
• Business transfers. In connection with a merger, acquisition, financing, reorganization, or sale of all or part of our business, your information may be transferred to the successor, who will be bound by this policy.
• With your direction or consent. For any other purpose you ask us to.

We maintain administrative, technical, and physical safeguards appropriate to the sensitivity of the information we hold, including:

• Encryption in transit with TLS 1.2 or higher for all connections to the Site, the Service, and our sub-processors.
• Encryption at rest. Our databases and backups are encrypted by our cloud provider. Data-source credentials and customer-supplied AI API keys are additionally encrypted at the application layer with AES-256 using keys that are not stored with the data.
• Least-privilege access. We ask you to grant Lighthouse a read-only role with access limited to the schemas and tables your metrics need. Our own staff access to production systems is restricted, protected by multi-factor authentication, reviewed periodically, and revoked promptly on offboarding.
• Logging and monitoring. Authentication, infrastructure, and deployment events are logged, and we maintain incident response procedures.
• Rate limiting and abuse controls on API keys and public endpoints.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security. You are responsible for keeping your credentials and API keys confidential and for choosing strong authentication options. If we learn of a breach affecting your personal data, we will notify you and any applicable regulator as required by law. Details of our security program are available on our Trust Center.

We keep information only as long as needed for the purposes described in this policy, then delete or de-identify it. Our standard periods are:

We may keep information longer where required by law, to resolve disputes, or to enforce our agreements, in which case we isolate it from ordinary use.

We are based in the United States, and the Service is hosted and operated there. If you use the Service from outside the United States, your information will be transferred to, stored in, and processed in the United States and in the countries where our sub-processors operate.

For transfers of personal data from the EEA, the United Kingdom, or Switzerland, we rely on the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum or Swiss amendments where applicable), together with supplementary measures where needed. Customers who need a data processing agreement incorporating these clauses can request one at admin@lighthouseai.co.

Depending on where you live, you may have some or all of the following rights regarding your personal information:

• Access: obtain a copy of the personal information we hold about you.
• Correction: have inaccurate or incomplete information corrected. You can edit your name and email in your account profile.
• Deletion: have your personal information deleted, subject to the exceptions in Section 9.
• Portability: receive the information you provided to us in a structured, commonly used, machine-readable format.
• Objection and restriction: object to, or ask us to restrict, processing based on legitimate interests, including direct marketing.
• Withdraw consent at any time where we rely on consent, without affecting processing that already happened.
• Opt out of marketing by using the unsubscribe link in any marketing email or by emailing us. We will still send transactional and security messages.
• Non-discrimination: we will not deny you service, charge you a different price, or provide a different level of service because you exercised a privacy right.

How to exercise your rights

Email admin@lighthouseai.co from the address associated with your account, or ask your organization's administrator. We will verify your identity (for example, by confirming control of your email address) before acting, and we respond within the time required by law, which is generally 30 days (GDPR) or 45 days (US state laws), extendable once where the request is complex. You may use an authorized agent where the law allows; we may ask the agent for proof of authorization and may ask you to confirm the request directly.

If a request concerns Customer Data that we process on behalf of a Customer, we will refer it to that Customer and help the Customer respond, because the Customer decides how that data is used.

If you are in the EEA, UK, or Switzerland

You can lodge a complaint with your local supervisory authority. We would appreciate the chance to address your concern first.

If you are a California resident

The California Consumer Privacy Act gives you the rights to know, delete, correct, and opt out of the sale or sharing of personal information, and to limit the use of sensitive personal information. We do not sell personal information. The Google Ads conversion tag on the Site may constitute "sharing" for cross-context behavioral advertising under California law; you can opt out at any time by emailing admin@lighthouseai.co. We do not use sensitive personal information to infer characteristics about you. In the preceding 12 months we collected the categories of personal information listed in Section 2 and disclosed them for business purposes to the service providers listed in Section 7. If we deny your request, you may appeal by replying to our decision, and we will respond within 45 days.

If you are a resident of another US state with a privacy law

Residents of Colorado, Connecticut, Virginia, Utah, Texas, Oregon, Montana, and other states with comprehensive privacy laws have comparable rights of access, correction, deletion, portability, and opt-out of targeted advertising and sales, and the right to appeal a refusal. Use the contact details above.

When the Service retrieves data from a Customer's warehouse or integrations ("Customer Data"), the Customer is the controller (or business) and we are the processor (or service provider). We process Customer Data only to provide the Service as configured by the Customer and as described in our Terms and Conditions and any data processing agreement, and we do not use it for our own purposes beyond operating, securing, and improving the Service.

Customers are responsible for:

• having a lawful basis to connect their data sources and to let Lighthouse query them;
• giving any notices to, and obtaining any consents from, the individuals whose data appears in metric results, filter values, or data previews;
• choosing which schemas, tables, and columns Lighthouse can access, and avoiding using columns that contain sensitive personal data as filters or segments; and
• configuring Slack channels and recipients so that alerts reach only people authorized to see them.

We will assist Customers with data subject requests, security assessments, and breach notifications relating to Customer Data as required by law and our agreement.

The Site and the Service are intended for business users aged 18 or older. We do not knowingly collect personal information from anyone under 18. If you believe a minor has provided us with personal information, contact admin@lighthouseai.co and we will delete it.

The Site and the Service contain links to, and integrations with, third-party websites and services such as Slack, warehouse consoles, YouTube, and documentation sites. We are not responsible for their privacy practices. We encourage you to read their policies before providing information to them.

We may update this policy from time to time. When we do, we will change the "Last updated" date above. If a change materially reduces your rights or materially changes how we use personal information, we will give you at least 14 days' notice by email to your account address or by a notice in the Service before the change takes effect. Your continued use of the Service after the effective date means you accept the updated policy. Earlier versions are available on request.

Questions, requests, or complaints about this policy or our handling of your information can be sent to:

Lighthouse AI Technologies LLC
Attn: Privacy
Email: admin@lighthouseai.co

If you are in the EEA or the UK and need to reach a representative under Article 27 GDPR, write to the same address and we will provide current contact details.