This English translation is provided for convenience. If it differs from the Polish version, the Polish document is authoritative.
info@meetlead.eu1. Profile identification and conversation access
The Customer is responsible for the identifiers sent by its integration and for reviewing the preview before merging contacts. Accepted identification, matching emails and profile merging do not establish permission to access orders or conversation history. History recovery, where available, requires separate verification and applies only to permitted threads. The WordPress plugin does not add automatic WordPress account login.
2. General provisions
These Terms govern use of meetlead.eu, provided by 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, the Meetlead operator and owner. Creating an account or using the service requires accepting these Terms and reviewing the Privacy Policy.
Meetlead is intended for businesses and organizations. A person acting for an organization confirms authority to create the account, accept the Terms and configure external services.
3. Definitions
Platform means Meetlead with its API, operator/admin panels and widget. Customer means the business or organization holding a Workspace; User means a person invited to it; Website means a separated site or brand context; Application means an optional Website module; Meta Integration means a connected Facebook Page or professional Instagram account; WordPress Plugin means the GPL-2.0-or-later Meetlead Live Chat connector; Customer Data means submitted data, content, configuration and files; Plan defines features, limits and retention.
4. Account and permissions
Users must provide a genuine email address, secure their credentials and accept responsibility for account activity. Sharing access with unauthorized persons or bypassing roles and Website assignments is forbidden.
The Customer manages users. Only a Website administrator may install, configure or uninstall Applications. Destructive operations may require the current password and are unavailable during support impersonation.
5. Service scope and Plans
The Platform may include the communication widget, Inbox, contacts, tickets, callback, recordings, heatmaps, analytics, automations, bookings, Meet AI and catalog Applications. Actual access follows the Plan, individual grants/blocks and active installations.
Meet AI is optional and requires acceptance of the current DeepSeek transfer notice. The default Copilot mode prepares private suggestions for operators and sends nothing without operator action. In the Autonomous handling and Hybrid modes, only the visitor can start a chat with the AI assistant by choosing it in the widget — in Hybrid mode only when nobody from the team is available; Meet AI never takes over conversations handled by people. The Autonomous handling and Hybrid modes must clearly disclose the assistant as AI and allow the conversation to be handed to the team — at the visitor’s request or with their consent, and also automatically when the assistant cannot continue (e.g. provider outage, exhausted limit, Meet AI disabled). The assistant answers based on fragments from the knowledge sources configured for the Website; when it finds no matching fragments, it does not generate an answer. The assistant becomes available to visitors only once the knowledge base is prepared. The AI generation limit follows the Plan (including any individual workspace settings), is shared by all Websites of the workspace and renews at the start of each calendar month (UTC); once it is exhausted, the assistant stops answering and its conversations are handed to the team, and Copilot, “Fix text” and private tests that need a generation are unavailable until the limit renews.
6. Subscriptions, trials and renewals
Starter is free forever. The paid plans listed in the current catalog are offered to businesses in Poland and the other EU member states in PLN or EUR, billed monthly or annually. Before ordering, the customer sees the price, tax treatment, billing interval, first charge date and renewal terms. The final amount includes applicable taxes and accepted discounts. Publishing a new price list does not change an existing subscription price.
The first paid subscription includes 14 free days after a payment method is added, once per buyer. Another account, workspace or upgrade does not restart the trial. We send a reminder seven days before the standard trial ends. Payment is collected automatically after the trial and at each renewal unless renewal has been canceled beforehand. A platform administrator may grant an individual trial, extension or free days; the next charge date is moved accordingly and shown in billing settings.
Renewal can be canceled in workspace billing settings. Access continues until the trial, paid period or granted extension ends. Cancellation prevents the next renewal, does not automatically switch the plan to Starter and does not delete the account or data. Downgrades are unavailable. An upgrade takes effect after the displayed and accepted additional charge is successfully settled. Switching between monthly and annual billing takes effect at the next renewal.
We retain the accepted Terms version, purchase conditions and confirmation of acceptance. A Checkout offer lasts at most 30 minutes. Returning from the payment page does not itself confirm settlement. A clearly labeled test environment collects no real payments; test documents are not live sales documents.
7. Shared communication allowance and backlog
One monthly unit is a thread with incoming communication or one callback. Further messages in the same thread do not consume another unit in that month. The allowance renews at the start of each UTC calendar month, including annual subscriptions; the panel shows the precise local date. Agent, website, tag and automation limits restrict their respective actions, not all communication.
Once the allowance is exhausted, each subsequent new piece of content is locked, including messages from an existing contact in an existing thread. New content is locked immediately when the paid or granted period ends without successful renewal, even while payment retries continue. Active channels continue receiving and storing messages, offline forms and callbacks, subject to consent, anti-spam measures, technical limits and integration rules.
The oldest backlog is released automatically before new submissions. It consumes the allowance of the release month, without charging the same thread twice in that allowance. For example, 30 backlog threads against a limit of 100 leave 70 units. Excess backlog waits for the next month, an upgrade or a grant. Payment and quota are separate conditions: a monthly reset does not clear unpaid billing, and payment does not remove usage limits.
Previously released history remains readable. Locked representations contain no message content, new contact details, callback phone number or attachment details. Product search, exports, notifications, mobile, AI, automation and outbound integrations cannot reveal it. The panel directs an authorized administrator to the relevant billing action. Expiration does not uninstall Applications or start data deletion.
8. Retention of locked content
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.
9. Invoices, tax and complaints
Issued invoices and corrections are read-only for the customer. The customer cannot edit their details after purchase. Changes to the company name, address, tax identifier or other billing-profile details apply only to future documents and do not change documents already issued. Report an error in an issued document to info@meetlead.eu; after verification we handle it through a separate correction procedure under applicable law, preserving the original document and settlement history.
Stripe handles payments and subscriptions. Card details are provided directly to the payment provider. Customer invoices and corrections come exclusively from Fakturownia. Meetlead stores each document and its immutable number before delivery to Fakturownia; during an outage it retains the pending document and retries. The PDF becomes available after receipt from Fakturownia. Only Fakturownia submits documents to KSeF where required; the KSeF identifier is separate from the invoice number.
The customer supplies accurate company, country and tax-identification details. Tax treatment follows applicable law, customer status and VAT/VAT-EU verification. One VAT rate does not apply to every country. Effective discounts, refunds and corrections are reflected in settlement and documents. Unverified tax details may require clarification before purchase.
Service or billing complaints can be sent to info@meetlead.eu with the workspace or document identifier, a description and the requested resolution. We reply within 14 days, or sooner if mandatory law requires it. We do not offer a voluntary subscription money-back guarantee. Canceling renewal stops the next subscription renewal but does not entitle the customer to a refund for the current period, including its unused portion. Access remains active until the end of the paid period, subject to the plan and its limits. This does not limit repayment of amounts collected without entitlement or rights arising from accepted complaints or mandatory law, including any mandatory consumer-equivalent protection applicable to a business customer.
10. Applications and Meta integrations
An integration starts only after installation and deliberate administrator authorization for a specific Facebook Page or Instagram account; one source cannot be active in two Websites. The Customer warrants authority and must follow Meta terms, messaging windows, anti-spam and data-use rules.
Meetlead requests only permissions needed for resource selection, webhook configuration and messaging. Meta data may not be used for ad profiling, resale, independent marketing databases or unrelated contact. Standard replies are blocked outside Meta’s 24-hour window unless an approved mode applies. Meta may change its API, access, limits or review; Meetlead does not guarantee Advanced Access, App Review approval or uninterrupted Meta services.
11. WordPress plugin
The free GPL connector is not a standalone chat service and requires a Meetlead account, active Website, installed WordPress Application and feature entitlement. GPL covers packaged plugin code, not the cloud service, data, infrastructure or marks. The plugin fetches no PHP add-ons or premium versions from Meetlead; the remote widget script is the selected service runtime.
Only an authorized administrator may connect it. The Customer is responsible for site URL, panel security, HTTPS/cache, supported WordPress/PHP and consent integration. New connections can start chat, presence and enabled analytics/heatmaps/recordings without waiting for a cookie-banner decision; alternative WordPress Consent API and consent-dependent modes are available. Configuration does not itself guarantee GDPR or cookie-law compliance, and compatibility with every theme, plugin, CSP, CMP or WordPress.org approval is not guaranteed.
12. Customer Data and privacy
The Customer retains rights to Customer Data and grants Meetlead a limited right to host, copy, transfer and technically process it solely to provide, secure and maintain the Platform.
The Customer is responsible for legal basis, notices, consent configuration, minimization, masking, retention and data-subject rights. Payment-card data, passwords, tokens, document numbers and special-category data should not be requested or sent unless strictly necessary and lawful.
13. Acceptable use
Spam, unlawful content, impersonation, connecting Meta or WordPress resources without authority, bypassing Plan limits, messaging windows, safeguards or access controls, unrelated use or sale of provider data, malicious code, webhook disruption and unauthorized access are prohibited.
Customers must not conceal the use of the Meet AI assistant, present AI output as a named human, or use it as standalone medical, legal or financial advice. On reasonable suspicion of abuse, Meetlead may restrict a feature, integration or account as needed to protect people, the Platform or comply with law.
14. Availability and liability
We use reasonable efforts to operate securely and reliably but do not guarantee uninterrupted availability. Maintenance, failures, networks, infrastructure and external providers may cause interruptions.
Meetlead is not responsible for Customer conversation content, decisions, missing consents or permissions, Customer breaches of provider rules, or outages caused by Meta or an AI provider. Model output can be incomplete or incorrect; the Customer controls instructions, knowledge, supervision and professional-use restrictions. Liability limitations apply only to the extent permitted by mandatory law.
15. Intellectual property
Rights in the Platform, code, interface, documentation and Meetlead marks belong to the operator or licensors. The Customer receives a limited, non-exclusive, non-transferable right to use the Platform while the account is active and under these Terms.
These Terms do not transfer rights in Customer Data or marks belonging to Meta or other providers.
16. Cancellation, uninstall and deletion
Uninstalling an Application immediately stops its runtime and removes disclosed operational data; audit, usage and selected history-legibility data may remain under retention. Deactivation or local removal of the WordPress Plugin does not automatically delete the Meetlead account, panel Application or remote conversations, contacts, recordings and analytics. Full removal requires account deletion or a verified request.
Uninstalling Facebook or Instagram removes tokens, OAuth state, connection configuration, raw events, imports and pending outbound messages; read-only history and minimal identifiers may remain under retention. Customer account deletion starts Workspace and integration hard-delete subject to legally required and pseudonymized security records.
17. Changes to the Terms
We may update the Terms as the Platform, law, provider rules or billing model changes. Material changes affecting active accounts will be announced by email or in the panel before taking effect where law or the nature of the change requires it.
18. Final provisions
Polish law applies, including the Civil Code, electronic-services and data-protection rules, without limiting mandatory rights of applicable persons. If one provision is invalid, the remaining provisions continue to the extent permitted by law.
19. Contact
Questions may be sent to info@meetlead.eu or by post to 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.