Privacy policy

This policy explains what LLantern collects, why, and who else handles it. The short version: we collect what we need to run your workspace, we don't sell it, we don't use it for advertising, and we don't use it to train AI models.

1. What we collect

Account details. You sign in with Google. We receive your name, email address and profile photo, and we store a record that your Google account is linked to LLantern.

Workspace data you add. Brands, domains, competitors, prompts, target countries, scan settings, content briefs and drafts.

Results we collect for you. Answers from AI assistants to your prompts, the sources they cite, and the analysis we run on them. When you ask for a site audit or brand discovery, we fetch public pages from the domain you entered.

Search performance data, if you connect it. See section 3.

Technical data. Our servers record basic request data such as IP address and browser type, and your session is tied to a sign-in cookie.

2. How we use it

We use your data to run scans, show your results, provide the features you turn on, answer support requests and keep the service secure. We email you about your account. We don’t sell personal data, we don’t use it for advertising, and we don’t use your data or results to train AI models.

3. Google Search Console and Bing Webmaster Tools

Connecting Google Search Console or Bing Webmaster Tools is optional. An owner or admin of your workspace starts the connection, and you choose which property belongs to each brand.

What we access. For Google, we ask for read-only access to Search Console (the webmasters.readonly scope), plus your Google account’s email address so we can show which account is connected. We use Search Console access to list the properties your Google account can see and to read search analytics for the property you select: clicks, impressions, click-through rate and average position, broken down by date, search query, page, country and device. For Bing, we use the access you grant through Bing Webmaster Tools to list your sites and read the same kind of search performance data. We never change anything in your Search Console or Bing account.

How we use it. Only to show search performance alongside your AI visibility results inside your LLantern workspace, and to keep that data up to date with a daily sync. We don’t use it for advertising, we don’t sell it, we don’t use it to train AI models, and we don’t use it to build profiles of you or anyone else.

How we store it. The access and refresh tokens Google and Bing give us are encrypted with AES-256-GCM before they’re written to our database. The search data we import is stored in our database and is only visible to members of the workspace that connected it. We also record which LLantern user made the connection and, for Google, the email of the connected Google account.

Who can see it. Members of your workspace. We don’t share it with the AI engines or other providers listed below, and we don’t transfer it to anyone else except as needed to provide or secure the service, to comply with the law, or as part of a merger or acquisition with notice to you.

Disconnecting and deletion. You can disconnect either provider at any time from your brand’s settings. Disconnecting deletes the stored tokens and the search data we imported through that connection. You can also revoke LLantern’s access from your Google account permissions or from Bing Webmaster Tools; after that we can no longer read new data and show the connection as needing to be reconnected. Deleting your account removes this data along with the rest of your workspace.

Google API Services User Data Policy. LLantern’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. People on our team don’t read your Google data unless you ask us to for support, it’s needed for security or abuse investigations, or the law requires it.

4. Who we share it with

The prompts you track are sent to AI engines as questions, so please keep personal data out of them. These providers process data for us:

Our API server and database run on infrastructure we operate. We only disclose personal data to authorities when the law requires us to.

5. AI assistants you connect

If you connect an AI assistant to LLantern through our MCP server, it can read and, if you allow it, change your workspace data on your behalf, using access you approve on a consent screen. What that assistant does with the data is governed by its provider’s terms.

6. Cookies

We only use cookies the service needs: one to keep you signed in across llantern.com and app.llantern.com, and one that remembers your time zone. The app also stores your light or dark theme choice in your browser. There are no advertising or tracking cookies, so there’s no cookie banner.

7. How long we keep it

We keep your data while your account is open. When you delete your account from Settings, your user record, sessions, workspace, brands, scan history and any connected search data are deleted from our database. If you buy a paid plan, billing records are kept by our payment providers for as long as tax law requires.

8. Your rights

Depending on where you live, including under GDPR and CCPA, you can ask to see, export, correct or delete your personal data, or object to how we use it. Much of this you can do yourself in Settings. For anything else, email hasnain@llantern.com.

9. Security

Traffic to LLantern is encrypted in transit with TLS. Tokens for connected search accounts are encrypted at rest, API keys for our providers are kept out of source code, and access to production data is limited to the people who need it to run the service. If a breach affects your data, we’ll tell you without undue delay.

10. Changes and contact

We’ll email account owners before any material change to this policy and update the date at the top. Questions, data requests and security reports go to hasnain@llantern.com, or use our contact page.