Privacy Policy

1. Customer identification

Profile identification may include a stable account ID, name and email supplied by the website without a mandatory secret. Profile attribution, matching emails and contact merging do not grant conversation access. When history recovery is enabled, we process the email used to send a code, a short-lived verification challenge and permissions for specific threads. Merging retains source data and an operation journal supporting undo; data follows the Website retention and deletion rules. The WordPress plugin does not automatically identify WordPress accounts.

2. Controller and roles of the parties

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 operates Meetlead and is the controller for service, contract, account, security and direct-contact data. Contact: info@meetlead.eu.

For conversations, contacts, widget activity, recordings, WordPress installations and Meta messages held in a Workspace, the Meetlead customer is normally the controller and Meetlead acts on its documented instructions as processor. Meta processes Facebook, Messenger and Instagram data under its own policy and is not part of Meetlead.

3. Scope and sources of data

Depending on configuration, we process account and organization details; hashed authentication, IP, user agent, session, security and audit data; conversations, attachments and contact profiles; visited URLs, events, device activity, recordings and heatmaps; callback and booking details; support correspondence; and Meet AI prompts, selected knowledge, pseudonymous participant identifiers and generation audit. This includes questions entered by authorized users in the Meet AI “Tests” tab (private tests) with the generated test results (answer and cited sources), and an operator’s draft submitted to “Fix text”, processed only to return the corrected text — URLs, email addresses and numbers are replaced with placeholders before sending. Meet AI does not send conversation attachments to its model provider.

Data comes from platform users, the customer-installed widget, the official WordPress plugin after deliberate connection, the customer identity API and—after administrator authorization—Meta APIs and webhooks.

4. WordPress plugin

Activating the optional Meetlead Live Chat plugin alone creates no account, starts no widget and sends no data. Pairing begins only after an administrator accepts the external-service notice and enters a one-time code. Pairing sends that code, site URL, random installation ID, plugin/WordPress/contract versions and the ordinary network IP to api.meetlead.eu; it does not send the WordPress administrator name or email, or installed plugin/theme lists.

Per-site connection settings and revocation credentials are stored locally, including in multisite; chat content and visitor profiles are not. Once connected, the loader may fetch the widget from widget.meetlead.eu. The site owner chooses the legal basis and consent mode. Active features may send communication, page, behavioral, heatmap or recording data only under their configuration and consent policy.

5. Mobile app

The Meetlead mobile app for iOS and Android is intended for users of customer accounts, that is administrators and agents. It lets them sign in with an existing account, handle conversations, callback requests and tickets, and receive notifications. Accounts cannot be created and nothing can be purchased in the app. The app contains no ads or analytics tools and is not used to track users.

When signing in, the app sends the email address and password, a random installation ID, the platform, device name and model, and the app version to https://api.meetlead.eu. We use this to create a separate mobile session linked to the user account ID and independent of the panel session. The session expires after 30 days without use and ends earlier on sign-out or when the password is changed or reset. Session tokens are kept in the system's secure storage: Keychain on iOS and Keystore on Android. So that the app also works offline, the most recently viewed inbox and conversation, messages waiting to be sent and app settings are stored on the device. This data is removed together with the app.

We send push notifications through Google Firebase Cloud Messaging and, on Apple devices, also through the Apple Push Notification service. For this we store a notification token linked to the mobile session, and the Firebase package in the app creates an installation ID used only to deliver notifications. A notification may contain the website name, the name or email address of the person who wrote or asked to be called back, part of the message and the phone number given in a callback request. We delete the token on sign-out or password change and when the notification service reports it as invalid. Notifications can be turned off in the system settings, and in the app selected websites can be muted and quiet hours set. These preferences are stored with the mobile session. Google may process data outside the European Economic Area using the safeguards described in the section on recipients and transfers.

Camera and photo access is used only when the user chooses to attach a photo or file to a conversation. The selected file is uploaded as an attachment. The Face ID, Touch ID or passcode lock works locally in the operating system, and Meetlead receives no biometric data. A reply sent from a notification reaches Meetlead in the same way as a reply sent in the app.

Dictating a message is optional and starts when the user chooses it after granting microphone access. We send the recording through the Meetlead API to OpenAI to convert speech to text. Meetlead does not store or log the recording or the text returned by the transcription service; the text goes to the editor and becomes a message only when the user sends it. According to the OpenAI API data controls (https://developers.openai.com/api/docs/guides/your-data), the transcription endpoint does not use this data to train models or retain it as application state or abuse-monitoring content. Provider processing may take place outside the European Economic Area. Audio files deliberately attached to a conversation are instead stored as attachments under the conversation retention rules.

6. Facebook Messenger and Instagram

These optional Applications run separately per Website. An uninstalled or inactive integration receives no webhooks for processing, starts no import and writes no new integration data.

After authorization we process only the selected Facebook Page or professional Instagram account, permissions and capabilities, encrypted access token and short-lived OAuth state, participant PSID/IGSID and Meta-provided profile details, message content and attachments, delivery/read/reaction data, timestamps and technical deduplication/import/outbox data. This supports Inbox handling only—not advertising, ad profiling, data sales or independent marketing enrichment. Meetlead enforces channel restrictions including the standard 24-hour reply window.

7. Purposes and legal bases

We process data to perform the service and account contract; carry out customer communications on the controller’s instructions; generate Meet AI suggestions or disclosed AI assistant replies (for visitors who choose the assistant in the widget) only after installation; protect the service, prevent abuse, audit and establish claims under legitimate interests; meet tax, accounting and legal duties; and, where applicable, operate marketing or optional technologies with revocable consent.

Meetlead does not make solely automated decisions producing legal effects about widget or Meta participants. Meet AI supports communication rather than ad profiling or decisions about a person. Customer automations execute customer-defined operational rules.

8. Recipients and international transfers

Authorized customer users, hosting, email and security providers, professional advisers and legally entitled authorities may receive data as needed. WordPress connects to Meetlead infrastructure; message data reaches Meta only for the selected action.

If Meet AI is installed, the necessary data is sent by API to Hangzhou DeepSeek Artificial Intelligence Co., Ltd. after separate versioned confirmation. The customer must disclose this and provide a lawful basis and transfer safeguards. Meta services may involve transfers outside the EEA. Where required, Meetlead uses Chapter V GDPR safeguards such as adequacy decisions or standard contractual clauses. We do not sell personal or Meta API data or share it with data brokers.

9. Payments and invoicing

Billing data includes company and address details, country, tax identifiers, billing contact, plan, payment and discount history, invoices and corrections, accepted terms and records of granted periods and allowances. We process this data to perform the contract, meet tax and accounting obligations and secure and demonstrate correct billing. A buyer identifier derived from tax details prevents repeated trials; it remains data associated with billing.

Billing-profile changes update details for future documents. They do not overwrite buyer details recorded on issued invoices or corrections. Reported errors in those documents follow a separate correction procedure that preserves the required document and settlement history.

For a Polish buyer, when preparing a purchase we send the NIP tax identifier and query date directly to the public VAT register of the Polish Ministry of Finance. We retain the returned status, query date and time, and request identifier as billing verification evidence. We do not retain bank account numbers, representative details or PESEL personal identifiers from that response. The result does not change data on issued documents.

Before starting a subscription for a buyer from another EU country, we send the country and EU VAT number directly to the European Commission’s VIES system. We retain the result, registry response date, lookup time and consultation identifier if supplied. We do not retain the company name or address from that response. This check concerns the particular purchase and is not continuous monitoring of VAT registration.

Stripe receives data needed for payments, subscriptions, tax verification and fraud prevention. Meetlead does not store full card numbers or CVC codes. Fakturownia receives the data required for invoices and corrections and exclusively submits required documents to KSeF. Meetlead stores the document number and status, the separate KSeF identifier and a PDF copy received from Fakturownia. Card details are entered only in the payment provider interface.

10. Retention and deletion

Locked messages, callbacks and necessary attachments remain stored outside ordinary retention until release. Plan retention starts when that content is made available. The customer may explicitly delete data, the Website or the account earlier through the applicable procedure. Non-payment or exhausted allowance does not itself initiate deletion. Previously released data remains subject to applicable retention.

Product access restrictions do not restrict statutory data-subject rights. Such requests follow a separate procedure with identity and role verification, independently of payment status. Invoicing data and settlement evidence may remain after account deletion for the legally required period; operational test data has a separate controlled deletion process.

WordPress pairing codes and Meta OAuth state expire after 10 minutes; raw webhook events after at most 30 days; temporary Instagram imports after at most 7 days. Access tokens remain encrypted only until disconnect, uninstall, expiry or reauthorization. Conversation retention follows the plan or customer setting: the period depends on the selected plan terms and individual configuration. If no automatic retention limit is set, the customer should define an appropriate period or delete data when its purpose ends. Copilot suggestion content is deleted when the operator inserts it into the editor or rejects it, and at the latest after 24 hours; content-free decision audit remains. Private Meet AI test questions and results are kept for 7 days and then deleted automatically (earlier if Meet AI is uninstalled). Drafts submitted to “Fix text” and the corrected text are not stored; only a content-free usage entry remains.

Disconnecting or removing the WordPress plugin stops local loading and attempts revocation but does not itself delete the Meetlead account or remote history. Uninstalling Facebook or Instagram removes tokens, OAuth state, connection configuration, raw events, imports, pending outbox and avatar URLs; read-only conversation history, contact name and minimal provider identifiers may remain under retention. Customer hard-delete removes integration data and secrets except legally required and pseudonymized security/audit records.

11. Your rights

Depending on the legal basis and circumstances, you may request access, correction, deletion, restriction, portability, object, withdraw consent and complain to the Polish supervisory authority. A person contacting a company using Meetlead should normally ask that company as controller first.

You may also write to info@meetlead.eu. We will help identify the controller and handle a securely verified request without undue delay, normally within one month subject to legal exceptions.

12. Cookies, localStorage and privacy settings

Recognition across the landing page and panel uses a separate __Host-meetlead_support cookie on the API host, protected by HttpOnly and Secure and valid until the login session ends. Logout or expiry disables recognition. The ml_support_revision cookie lasts up to 7 days and signals a change without account data. The landing page never receives login tokens; the meetlead_support_account local-storage entry helps reset the widget when accounts change.

Our Meetlead widget runs on meetlead.eu and panel.meetlead.eu, providing chat, visit and event analytics, and session recording from entry. Form fields are masked; customer content, secrets and embedded players in the panel are excluded from recordings. An accepted registration form creates an unverified email contact; verification or sign-in links the contact and sessions to the account identifier. We do not run advertising tools. ml_consent_v1 remembers acknowledgement for up to 180 days; ml_theme and the local theme preference last up to 12 months. This notice can be reopened at any time; dismissing it does not change widget settings. Contact info@meetlead.eu about data processing.

A customer-installed widget may use localStorage for visitor identity, secure session-resume secret and preferences, and sessionStorage for the current session and pending messages. The customer must provide its own notice and obtain required consent before optional features such as session recording.

13. Security

We apply risk-appropriate controls including password hashing, AES-256-GCM encryption of Meta tokens, role and Website access controls, short-lived OAuth state, webhook signature verification, rate limiting, deduplication, audits and rechecking integration activity before background work. Meet AI receives only data needed for a generation and no user credentials.

Passwords, tokens, encryption keys, OAuth state and raw provider payloads are excluded from logs and Application lifecycle audit records.

14. Children and special-category data

Meetlead is a business service and is not directed at children. Do not send special-category data, identity-document numbers, payment-card data, passwords or other secrets through Messenger, Instagram or the widget. Customers must configure forms, access and retention to avoid excessive collection.

15. Changes to this Policy

We may update this Policy when features, providers, law or external-platform rules change. The current version date appears above. Material changes affecting account users will be announced by email or in the panel.

16. Contact

For privacy, deletion or integration questions, contact info@meetlead.eu. Use of the service is also governed by the Meetlead Terms of Service.