Your website.
The start of a good conversation.

1. What the plugin is

Meetlead Live Chat installs the Meetlead widget on a WordPress website without requiring manual theme edits. The plugin is a connector to the external Meetlead SaaS and does not provide a local chat service by itself. It requires a Meetlead account, a Website configured in the panel and an active WordPress Application.

Activating the plugin does not create an account or contact Meetlead. The first connection occurs only after an administrator deliberately accepts the external-service notice and submits a one-time pairing code.

The PHP code, local JavaScript loader and other files distributed through WordPress.org are licensed under GPL-2.0-or-later. The remote widget is an integral part of the Meetlead service runtime; it is not used to update plugin code, install add-ons or download premium versions.

2. External services

The plugin connects to https://api.meetlead.eu to exchange a one-time code for connection data, revoke a connection, retrieve widget configuration, handle chat communication and accept permitted functional or analytics data. It connects to https://widget.meetlead.eu to load the widget, recorder and heatmap collector, and may asynchronously load interface fonts from https://meetlead.eu/fonts when the browser supports FontFace.

These services are operated by GESEL.IO sp. z o.o., the operator and owner of Meetlead. We do not sell visitor data or use plugin connections for advertising. SaaS use is governed by the Terms of Service and data processing by the Privacy Policy.

3. Local and remote data

During pairing, the plugin sends the one-time code, WordPress home URL, a random plugin-instance identifier, plugin version, WordPress version and integration-contract version to the API. The server also receives the request IP address. The plugin does not send the WordPress administrator account, installed plugin or theme lists, or post content.

Only information required to maintain and safely revoke the connection is stored locally in WordPress options. Visitor profiles, conversations, attachments, recordings and heatmaps are not stored by the plugin in WordPress.

After the widget starts, it may send the visitor IP address and user agent, current page and referrer, visitor identifier, secure session-resume data, chat and form content, and uploaded files to Meetlead. Depending on configuration and consent, it may also send page events, goals, clicks, DOM snapshots, heatmaps and session recordings.

4. Consent and privacy

The default load_immediately mode starts chat, presence and enabled analytics without waiting for a cookie-banner decision. If heatmaps or recordings are enabled in Meetlead, they may also start immediately. The administrator selects this mode during pairing and is responsible for the appropriate legal basis and visitor notice.

The wait_for_consent mode integrates with the WordPress Consent API and does not download the widget before functional consent. The retained load_chat_immediately mode starts chat immediately and analytics only after consent. Another CMP may provide the current state before the loader or dispatch a meetlead:consent event with functional and analytics values. Installing or configuring the plugin does not by itself guarantee legal compliance.

The plugin adds suggested wording to the WordPress Privacy Policy Guide. It must be adapted to the website’s actual settings, retention periods and controller contact details.

5. Deactivation, disconnection and deletion

Deactivation stops the widget from loading but keeps local connection settings for later activation. Disconnecting in plugin settings disables the widget locally and attempts to revoke the Meetlead connection; when the API is unavailable, only the minimum revocation data remains for a safe retry.

Deleting the plugin removes all local settings and secrets and makes a time-limited, best-effort remote revocation attempt. The administrator should then verify the integration status in Meetlead. Uninstalling the WordPress Application in Meetlead removes pairing codes, connections and integration credentials, while conversation history, contacts, recordings, audit and usage follow service retention.

Deleting the Meetlead account or submitting a verified request is required to remove remaining remote data, subject to legal retention and pseudonymized audit exceptions. WordPress personal-data export and erasure tools do not cover data stored in Meetlead; visitor requests must also be handled in the Meetlead workspace or sent to info@meetlead.eu.

6. Operator and support

The service operator and owner of Meetlead is GESEL.IO sp. z o.o., ul. Jagiellońska 5/22, 58-100 Świdnica, Poland, KRS 0001258062, NIP 8842841661, REGON 545371616, share capital PLN 5,000. Company information is available at gesel.io.

Technical support, privacy questions and data requests: info@meetlead.eu.