Privacy Policy

Last updated: October 28, 2026

1. Who I Am

Glippy is operated by 11 Internet / Glippy.dev, located at Piet Heinstraat 79, 2518CD, Den Haag, The Netherlands. You can reach me at [email protected].

2. What Data I Collect

I keep data collection to an absolute minimum:

  • Waitlist sign-up: If you join the waitlist, I collect your email address solely to notify you about product availability.
  • License verification: For Glippy Pro users, I process license keys to verify your purchase. No page content or analysis data is transmitted.

Beyond the above, the analytics described in Section 3, and the domain names and usage statistics of the Glippy app in ChatGPT (Section 5), Glippy does not collect, store, or transmit any personal data.

3. Analytics

This website uses two analytics services:

  • Vercel Analytics (Vercel Inc.) collects anonymous, aggregated data about page views and website performance. It does not use cookies, does not track individual users across sites, and does not collect personal information. For more details, see Vercel's Analytics Privacy Policy.
  • PostHog (PostHog Inc., data stored in PostHog's EU cloud in Frankfurt, Germany) records page views, clicks on links and buttons, and time spent on a page, so I can see which pages and features people use. It runs in cookieless mode: nothing is stored on your device. To count unique visitors, PostHog derives an identifier on its servers from your IP address, your browser's user agent and a random value that is replaced every day, so visits on different days cannot be linked to each other. Your IP address is not stored. This data is kept for up to 12 months.

The legal basis for Vercel Analytics and PostHog is my legitimate interest in understanding how the website is used (Article 6(1)(f) GDPR).

Glippy MCP server: the Glippy MCP server (the glippy-mcp npm package) sends anonymous usage statistics to PostHog (EU cloud, Frankfurt) each time one of its tools runs: the tool name, whether it succeeded, how long it took, your license tier or trial status, the render mode and report format chosen, how many domains or URLs the tool was given, the name and version of the AI app running the server (for example Claude Desktop or Cursor), and the Glippy, Node.js and operating system versions. It never sends domain names, URLs, page content, analysis results, file paths, or your license key. Events are linked to a random install identifier stored in ~/.glippy/telemetry-id, not to your license or your identity, and PostHog is set to discard the IP address each request comes from. This data is kept for up to 12 months. You can turn it off at any time by setting GLIPPY_TELEMETRY=0 (or DO_NOT_TRACK=1) in the server's environment. The legal basis is my legitimate interest in maintaining and improving the server (Article 6(1)(f) GDPR).

The Glippy Chrome Extension and Desktop App do not include any analytics or tracking.

4. How Glippy Works

The Glippy Chrome Extension and Desktop App run entirely on your device. All page analysis is performed locally in your browser or on your machine. No webpage content, URLs, or analysis results are ever sent to my servers. The Glippy app in ChatGPT is the exception: it runs on my servers, as described in Section 5.

5. Glippy in ChatGPT

The Glippy GEO app in ChatGPT runs on Glippy's servers, on Google Cloud Run in the EU (Netherlands). It needs no account and no sign-in. When you ask ChatGPT to use Glippy, this is what happens:

  • Personal data collected: the tool request ChatGPT sends contains the domain name or names you asked about (for example "example.com"). A domain is usually not personal data, but it can be, for example if it is your own name. ChatGPT also attaches metadata to each request: your locale, an approximate location (city, region, country), and anonymous identifiers for you and for the conversation. Glippy uses only the locale, the country and the two anonymous identifiers, for the usage statistics described below, and hashes the identifiers (a one-way transformation) before storing them. It does not use the city, region or coordinates. Each request is also logged with a timestamp, the IP address it came from, and its user agent. Those are OpenAI's servers, not your device, so I do not receive your IP address. I do not receive your name, email address, or ChatGPT conversation. Glippy does not ask for, and you should not enter, other personal information.
  • Purposes of use: the domain names are used only to fetch that site's public files (the homepage, robots.txt, sitemap.xml, llms.txt and standard /.well-known discovery files) and return the analysis to ChatGPT. Glippy identifies itself as GlippyBot, does not fetch a site whose robots.txt disallows GlippyBot, and never signs in to or changes a site. Request logs are used only to keep the service running and to stop abuse. I do not use the domain names you ask about to analyse query patterns, I do not use any of this data for profiling, advertising, or training AI models, and I do not sell it. The legal basis is my legitimate interest in providing the analysis you requested and in keeping the service secure (Article 6(1)(f) GDPR).
  • Usage statistics: for each tool call, Glippy records which tool ran, whether it succeeded or declined to fetch a site (and why), how long it took, the page type, the score and grade, which app made the call (ChatGPT, Claude or another MCP client) and its version, and the locale, country and hashed identifiers described above. These statistics do not contain the domain names you asked about. They are stored in PostHog's EU cloud (Frankfurt, Germany) for up to 12 months and used only to understand how the app is used, how many people use it, and where it fails. The legal basis is my legitimate interest in maintaining and improving the app (Article 6(1)(f) GDPR).
  • Categories of recipients: Google Cloud (hosting and logging) and PostHog (usage statistics) are my data processors. The website you ask about receives GlippyBot's requests from Google Cloud addresses; it does not learn who asked. OpenAI processes your conversation under OpenAI's Privacy Policy. No one else receives this data.
  • Data retention: analysis results are held in server memory for about 10 minutes, so repeat questions do not re-fetch the site, and are then discarded. There is no database. Request logs (timestamp, IP address and user agent of the calling server, status, response size, but not the request contents) and error messages, which may include a domain name, are kept by Google Cloud Logging for 30 days and then deleted. Google Cloud may store these logs outside the EU.
  • Your controls: you choose which domains to ask about, and you can disconnect the app in ChatGPT's settings at any time. You can ask me for access to, or deletion of, anything related to your use at [email protected]. You can also complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

6. Chrome Extension Permissions

The Glippy Chrome Extension requests the following permissions. Each permission is used solely for the described purpose:

  • activeTab: Access to the current tab when you click the extension icon. Used to analyze the page you're viewing.
  • scripting: Run analysis scripts on web pages. Used to evaluate GEO checks like structured data, semantic HTML, and accessibility.
  • storage: Store data locally in your browser. Used to save scan history, settings, and your Pro license key. No data is sent externally.
  • tabs: Access to your open tabs. Used for the badge score feature (showing GEO score on the extension icon) and bulk tab scanning.
  • contextMenus: Add right-click menu options. Used for the "Scan all open tabs" feature.
  • identity: Google OAuth authentication. Used only when you choose to save reports to Google Drive. This is optional and only activated when you use this feature.

Additionally, Glippy may request optional access to scan pages on other URLs (for competitor comparison and multi-page scan features). This access is requested on-demand and only when you use these specific features.

7. Google Drive Integration (Optional)

If you choose to use the Google Drive export feature, Glippy will request access to:

  • Google Drive: Save report files (PDF, CSV, Markdown, HTML) to your Google Drive. Glippy can only create and access files it creates - it cannot read, modify, or access any of your existing files.
  • Email: Your email address is used solely for Pro license verification.

This integration is entirely optional and only activated when you explicitly choose to export to Google Drive.

8. How I Use Your Data

The limited data I collect is used exclusively for:

  • Sending you waitlist updates and product announcements
  • Verifying Pro license keys

The domain names sent through the Glippy app in ChatGPT are used only to answer that request. I do not sell, share, or transfer your data to any third parties, other than the service providers named in Sections 3 and 5.

9. Data Storage and Security

Waitlist email addresses are stored securely. I use industry-standard security measures to protect your information. Data is retained only as long as necessary for the purposes described above.

10. Your Rights

You have the right to:

  • Request access to any personal data I hold about you
  • Request deletion of your data at any time
  • Withdraw consent for communications

To exercise any of these rights, contact me at [email protected].

11. Third-Party Services

This website uses Vercel Analytics and PostHog (see Section 3), and the Glippy MCP server and the Glippy app in ChatGPT send usage statistics to PostHog (Sections 3 and 5). I do not embed any advertising services. License verification for Pro users is handled by my own infrastructure. The Glippy app in ChatGPT is hosted on Google Cloud (see Section 5).

12. Changes to This Policy

I may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated revision date. I encourage you to review this page periodically.

13. Contact

If you have any questions about this Privacy Policy, please contact me:

11 Internet / Glippy.dev
Piet Heinstraat 79, 2518CD, Den Haag, The Netherlands
[email protected]

← Back to Glippy

Check your site for AI search readiness

Start free with the Glippy Chrome extension for instant page checks. Scaling up? Automate audits across many URLs and your whole sitemap with the Glippy MCP server.

Add Glippy to Chrome – free Automate with the MCP server →