LeadPass

LeadPass Terms of Service

(Regulamin świadczenia usług drogą elektroniczną — Terms for the provision of services by electronic means)

Effective date: 27 July 2026 Version: 1.1

1. Who we are; what this document is

1.1. The LeadPass service available at useleadpass.com (the "Service") is provided by:

Jose Ramon Leon Rodriguez, a sole trader (jednoosobowa działalność gospodarcza) established in Poland Registered address: Egipska 5/69, 03-977 Warszawa, Poland NIP (tax ID): 8992886524 · EU VAT: PL8992886524 · REGON: 387147849 Registered in the CEIDG (Centralna Ewidencja i Informacja o Działalności Gospodarczej) Contact: legal [at] useleadpass.com

(the "Provider", "LeadPass", "we", "us").

1.2. These Terms of Service (the "Terms") are the terms for the provision of services by electronic means (regulamin świadczenia usług drogą elektroniczną) required by Article 8 of the Polish Act of 18 July 2002 on Providing Services by Electronic Means (UŚUDE). They set out the types and scope of the services we provide electronically, the conditions of providing them (including technical requirements and the prohibition on unlawful content), the conditions for concluding and terminating contracts, and our complaint-handling procedure.

1.3. These Terms are made available free of charge, before any contract is concluded, at https://useleadpass.com/legal/terms, in a form that allows you to retrieve, reproduce, save and print them. On request to legal [at] useleadpass.com we will send you a copy of the current version.

1.4. Documents incorporated into these Terms by reference:

If these Terms conflict with the DPA regarding the processing of Lead Data, the DPA prevails.

2. Definitions

3. Types and scope of services; business use only

3.1. We provide the following services by electronic means:

a) the Platform (paid) — access for the Customer and its Users to the LeadPass application: creating and configuring Flows with AI assistance, publishing Public Flow Pages, automatic transcription of Leads' voice answers, AI evaluation of answers against the Customer's criteria, a review queue with manual verdict override, reports, team and Workspace management, and billing management;

b) Public Flow Pages (free of charge for Leads) — enabling a Lead to open a Flow link, submit the contact details requested by the Flow, and answer questions by voice recording.

3.2. The Service is offered exclusively to businesses. By creating an Account you declare that you are concluding the Agreement directly in connection with your trade, business, craft or profession, and not as a consumer. We do not offer the Service to consumers within the meaning of Article 22¹ of the Polish Civil Code. The Account owner concludes and administers the Agreement for the Customer; other Users access the Service under the Customer's authority and do not become separate customers merely by accepting an invitation.

3.3. If you are an Entrepreneur with Consumer Rights, these Terms apply to you with the modifications set out in Section 21. Nothing in these Terms excludes rights that mandatorily apply to Entrepreneurs with Consumer Rights under Polish law.

3.4. Leads are not parties to the Customer's Agreement. A contract for the free electronic service described in Section 3.1(b) is concluded between the Provider and the Lead when the Lead starts using a Public Flow Page and terminates when the Lead completes or leaves the page. These Terms are made available to the Lead free of charge, before the Lead starts using that service, via a link on every Public Flow Page, in a form that allows their retrieval, reproduction and storage (Article 8 UŚUDE). The processing of Lead Data is governed by Section 8 and the DPA. The Customer must ensure that the actual controller of Lead Data — the Customer itself or, for an agency acting on a client's behalf, that client — processes the data lawfully.

4. Conclusion of the Agreement; registration

4.1. Registration and Account contract. Registration requires acceptance of these Terms: the registration form links these Terms and the Privacy Policy and requires the registering person to confirm acceptance by ticking a checkbox that is not pre-ticked. For a person registering independently, the Account contract is concluded when registration completes and we create the Account. A Team Member or Client User registering through an invitation receives the invited User profile and membership but does not create or become the owner of a separate Account; that User accesses the existing Customer's Service under Sections 3.2 and 6.

4.2. Subscription contract. A contract for the paid Platform service is concluded at checkout, when the Account owner selects a Plan and Billing Period, provides a payment method and billing details, makes the separate express request for access to begin immediately during any applicable withdrawal period, and confirms the order through the checkout action. That request starts performance immediately but does not state that a withdrawal right is waived. The order summary and the information beside that action state whether the order starts with a free trial or an immediate charge and show the amount and Billing Period selected; the applicable Terms and DPA are linked beside the action, and Section 11 sets out automatic renewal. Use of the Platform beyond checkout requires an active subscription or trial.

4.3. You must provide true, accurate and current information at registration and checkout (including business identity and invoicing data) and keep it up to date. You are responsible for maintaining the confidentiality of your credentials and for all activity under your Account. The Service supports two-factor authentication and passkeys; we recommend enabling them.

4.4. You must be at least 18 years old and have the capacity to enter into contracts. If you accept these Terms on behalf of a company or other entity, you represent that you are authorised to bind it.

4.5. The Service keeps an internal, application-level append-only electronic record of contract, payment and material subscription actions. It records the Account and time and, for user-initiated actions, the acting User; the exact versions and SHA-256 fingerprints of the Terms, DPA and acknowledged Privacy Policy; the immediate-performance request; and a frozen snapshot of the selected Plan, Billing Period, price excluding VAT, currency, trial and included limits. A paid credit-pack invoice instead records the exact pack, credits, price excluding VAT, tax, currency and purchase source, without presenting it as a Plan charge. The canonical text of every referenced legal-document version is archived with that record. Verified formation, paid invoices, later Plan changes, cancellation/resumption and an early end to a free trial are separate events. A user-confirmed action is normally recorded before its Stripe mutation and the provider-applied result is recorded separately, so an abandoned or failed checkout or mutation is never presented as formed or applied. An outage of this auxiliary record never prevents the Account owner from cancelling renewal. For billing reconciliation, fraud prevention and contractual claims, the ledger also retains at most one authenticated paid-service access per User/Account/UTC day and a minimal event for each real metered qualification delivered. The latter contains identifiers, counts and times but no Lead contact details, transcripts, audio, answer text, score or verdict. The current Terms remain available as described in Section 1.3. We recommend that you also download and keep the Terms, DPA and checkout summary that apply when you order; the Service does not currently provide a customer-facing archive of earlier versions or a separately signed contract.

5. Technical requirements

5.1. Using the Platform requires: a device with a current version of a modern web browser (e.g. Chrome, Firefox, Safari, Edge) with JavaScript and cookies enabled; an internet connection; and a valid email address.

5.2. Answering a Flow additionally requires a microphone and granting the browser permission to record audio. Voice answers must be between 3 seconds and 10 minutes long and no larger than 20 MB per recording; supported formats are those produced by current browsers (webm, m4a/mp4, ogg, mp3).

5.3. The Service uses first-party cookies strictly necessary for its operation (session — which also remembers your language choice — security/CSRF, and an optional "remember me" cookie). Details are set out in the Cookie Policy and the Privacy Policy. Public Flow Pages may additionally load Cloudflare Turnstile, an anti-bot protection.

5.4. Prohibition of unlawful content. It is prohibited to supply through the Service, or cause the Service to store or transmit, content of an unlawful nature (zakaz dostarczania treści o charakterze bezprawnym). This prohibition binds the Customer, all Users and Leads.

5.5. Particular risks of services provided by electronic means (Article 6(1) UŚUDE). Particular risks connected with using services provided by electronic means include: the possibility of malware infection of the user's device, phishing and spoofing attempts by third parties impersonating the Service or its emails, and interception or modification of transmissions on untrusted networks. We apply the safeguards described in the Privacy Policy; users should keep their devices and browsers updated, protect their credentials, verify that they are connecting to the Service's genuine address, and enable two-factor authentication or passkeys. Information about the software and data introduced into the user's system by the Service (Article 6(2) UŚUDE) is provided in the Cookie Policy at https://useleadpass.com/legal/cookies.

6. Users: Team Members and Client Users

6.1. The Customer may invite Team Members to its Account and Client Users to individual Workspaces. Invitations are sent by email, contain a personal acceptance link and expire 7 days after being sent.

6.2. Client Users receive read-only access limited to the Workspace(s) they were invited to (Leads and reports); they have no access to billing, Account settings or verdict overrides.

6.3. The Customer is responsible for the acts and omissions of its Users as for its own, including compliance with these Terms. The Customer decides whom to invite and must remove access of persons who should no longer have it.

6.4. Each User must keep their credentials confidential. Accounts and User logins are personal and must not be shared.

6.5. Only the Account owner may start or manage the subscription, payment method and Account deletion. Team Members and Client Users act within the access granted by the Customer and have no authority through the Service itself to amend or terminate the Agreement.

7. The Service; AI nature; no guarantee of accuracy

7.1. LeadPass is an AI-based lead-qualification tool. When a Lead answers a Flow: (a) voice answers are recorded in the browser and stored by the Service; (b) recordings are transcribed automatically on infrastructure operated by the Provider (self-hosted speech-to-text); (c) transcripts and the Lead's name and company (if collected) are evaluated by a third-party large-language-model provider (currently OpenAI) against the criteria configured in the Flow; (d) the Service may generate follow-up questions asked to the Lead in a second round; and (e) the Service produces structured model assessments and synthetic text, including band scores and supporting evidence per criterion and a summary. LeadPass code then derives the Pass / Review / No pass recommendation from the stored assessments according to a fixed mapping and any applicable required-evidence and gate rules; the model does not freely generate that label. Incomplete is likewise a system state used where the available answers lack enough required or usable evidence for one of those three reliable overall recommendations; this may follow a partial response or a fully answered response that still omits a required fact, while a partial response with enough evidence may still produce Pass, Review or No pass. There are four public result states — Pass, Review, No pass and Incomplete — and each uses the corresponding Customer-configured response, which may include an authored message and an optional button. Internal result labels are not shown automatically. While a real Lead processed under per-Flow manual-review mode awaits the Customer's decision, its public result is Review and its result button is disabled. Once the Customer records Pass or No pass, that outcome and any configured button become the public result. If an authorised reviewer moves the Lead from Review to Pass and the per-Flow switch is enabled, LeadPass emails a private signed link to that Lead's Pass result screen; the screen resolves the Customer-authored Pass response and current button, and no other result or transition sends a Lead email. Manual-review runs receive no public AI personalization. The Customer may separately enable personalization only for an eligible automatic Pass; Review, No pass, Incomplete and real Leads processed in manual-review mode are not personalized. When eligible personalization is enabled, a separate post-verdict AI process receives the Lead's questions and answers, a factual identity of the offer extracted from the Customer's offer material (if that material does not yield a usable identity, no personalization occurs), compact units compiled from that material, and tone guidance. It must propose one natural introduction and three connections, each linking a distinct fact stated by the Lead to a distinct real offer unit. For each connection it returns answer evidence that the Service validates against the stored answers; connections that fail validation are omitted individually, and between one and three validated connections are shown. If no valid connection remains, no personalized AI block is shown. The Lead sees only a natural point title and connection text for each match, not transcript quotations, source cards, source titles or underlying claims. The Customer can audit in the application the exact introduction, point titles and connection text stored for that Lead — the same generated copy rendered on the public result — but neither view exposes the internal answer-evidence or source-validation fields. LeadPass uses those fields internally to validate the proposed connections against stored answers and Customer-supplied offer material. Optional presenter identity is resolved by the Service and appears only beside the Customer-authored outcome, not as the author of generated text. The composer does not receive the verdict, criteria, bands, outcome message, button, URL or routing instructions. The outcome message and CTA remain Customer-configured and server-resolved. The personalized response never determines or changes the verdict, criteria, score or routing, is stored as part of the assessment and deleted with it. The audit record proves which generated copy was stored for that Lead; it does not establish that the Lead opened or viewed the result.

7.2. The model-generated and model-assessed parts of AI Outputs are probabilistic. They may be inaccurate, incomplete, outdated or misleading, including transcription errors and misjudged evaluations. A deterministically derived recommendation or Incomplete state may therefore also be wrong because its underlying assessment or the Customer's configuration is wrong. We do not warrant the accuracy, completeness or fitness of any AI Output. The Service may route a Lead automatically to a next step selected by the Customer for the resulting verdict, but the AI Output remains a recommendation for which the Customer is responsible.

7.3. Human oversight required. The Customer must exercise its own judgment when configuring criteria, verdict thresholds and automatic next steps, and when reviewing AI Outputs. The Service provides a manual review queue and a verdict override that preserves the analyzer's proposal and records the published verdict, who decided or overrode it, and when. The Customer must not use verdicts or scores as the sole basis for a decision that produces legal effects concerning a Lead or similarly significantly affects a Lead, without meaningful human review by a person authorised and competent to change the outcome before that decision is made.

7.4. The Service does not analyse voice tone, pitch, prosody or any other vocal or biometric characteristic. Voice recordings are used solely for transcription and content-based evaluation. The Service does not create voiceprints and does not identify, authenticate or infer emotions of any person from biometric data.

7.5. Public Flow Pages display a fixed, non-editable notice to Leads about the recording and the retention of their voice answers (see Section 9.6), a link to a per-Flow privacy notice page, and — before the Lead starts answering, at the latest at the Lead's first interaction and before the first question — a clear notice that the Lead's answers are voice-recorded, transcribed and assessed by an AI system. This transparency measure is designed to support the disclosure in Article 50(1) of Regulation (EU) 2024/1689 (AI Act) when that provision applies.

7.6. The AI interaction is disclosed before the Lead starts answering, and the per-Flow privacy notice explains that an enabled personalized result may be written by AI. The Service does not add a separate visible "AI-generated" label to each personalized response. LeadPass attaches a versioned, signed first-party machine-readable provenance envelope to qualification-report projections containing model outputs, AI-generated follow-up questions, personalized responses and webhook projections; rendered surfaces expose that marker only while its content hash and signature remain valid. A marked report or webhook is a mixed artifact and can also contain Customer-authored labels, deterministic fields and verbatim Lead evidence; the marker does not claim that every nested value was synthesized. This integrity envelope is not represented as an interoperable watermark or public detector. These technical markers and the lead-facing disclosures serve different transparency purposes, and LeadPass may update them as the technical standards and final guidance for Article 50(2) of the AI Act mature.

7.7. Public Flow Pages include a discreet "Powered by LeadPass" notice linking to our website. This notice is part of the Service and may not be removed or obscured by the Customer.

7.8. We may improve and update the technical means used to provide the Service (including transcription and evaluation models and infrastructure), provided the changes do not diminish the protections and material characteristics of the Service. Section 22 governs material changes.

8. Data protection roles; the DPA; Lead-facing notices

8.1. Data-protection roles. (a) For personal data of the Customer and its Users (registration, team, billing, support and service emails), the Provider is the data controller; the Privacy Policy applies. (b) Where the Customer determines the purposes and means of processing Lead Data, the Customer is the controller and the Provider is its processor. (c) Where an agency Customer processes Lead Data on behalf of its own client, that client may be the controller, the Customer acts as its processor, and the Provider acts as the Customer's sub-processor. The Customer is responsible for identifying and documenting the correct arrangement, obtaining any authorisation needed to appoint the Provider, and passing the controller's documented instructions to the Provider under the DPA.

8.2. The Provider processes Lead Data solely to provide the Service and does not use Lead Data to train or improve AI models or for its own purposes. Sub-processors (including OpenAI and hosting providers) are listed in the DPA and its sub-processor list.

8.3. Customer's data-protection duties. The Customer is responsible for ensuring that it and, where applicable, its client controller lawfully process Lead Data, including: (a) establishing and documenting a valid legal basis for collecting and evaluating Leads' answers; the Workspace profile supports legitimate interests under Article 6(1)(f) or necessary pre-contractual steps requested by the Lead under Article 6(1)(b), but selecting an option does not itself establish that the basis applies; (b) entering and keeping accurate the actual controller's identity, postal address, privacy contact and any applicable representative/DPO details in the Workspace profile, rather than identifying the agency automatically; (c) handling or assisting with Leads' data-subject requests (access, erasure, objection, etc.); the Service supports this with per-lead deletion and the criteria/band data needed to explain evaluations; (d) configuring Flows (questions, contact fields, retention and feedback to the Lead) lawfully; and (e), where the Customer acts as a processor, maintaining an appropriate agreement with its client controller and using the Service only within that controller's instructions. While the Workspace controller profile is not confirmed, the Public Flow Page presents a default notice identifying the Workspace and the Account owner's contact details; the Customer remains responsible for reviewing that default or replacing it with the actual controller's details. Neither the default notice nor any technical check is legal advice or a substitute for the Customer's assessment.

8.4. The Provider will forward to the Customer without undue delay any data-subject request from a Lead that it receives directly, and will not respond on the merits except on the Customer's instruction or where legally required.

8.5. The Customer must not configure Flows to deliberately elicit special categories of personal data (e.g. health, religion, ethnicity, sexual orientation, trade-union membership) or data relating to criminal convictions. If such data may incidentally arise in free-form answers, the Customer is responsible for its own compliance, including any required legal basis and impact assessment. The evaluation pipeline instructs the AI model not to use protected characteristics for scoring or reproduce them in an output, but this probabilistic safeguard does not replace the Customer's review of questions and results.

8.6. Where the Customer directs Flows at Leads in a given language or country, the Customer is responsible for ensuring that the notices it is required to give are available in a language those Leads understand. The Service currently ships lead-facing interface text in English and Spanish.

9. Acceptable use; content; recording rules; moderation

9.1. The Customer and its Users may not:

a) use the Service to violate any law or the rights of any person, or supply unlawful content (Section 5.4); b) upload or publish in Flows content that is defamatory, deceptive, infringing, harassing or fraudulent, or impersonate another person or entity; c) use Flows for phishing, collection of credentials or payment-card data, or any deceptive data collection; d) probe, scan, overload or disrupt the Service, circumvent usage limits, quotas, rate limits or access controls, or access the Service by automated means (scraping, bots) other than interfaces we document; e) resell, sublicense or provide the Service to third parties as a service bureau, except that serving the Customer's own clients through Workspaces (including Client Users) is permitted; f) reverse engineer the Service except to the extent a statutory right cannot be excluded; g) introduce malware or test the Service's security without our prior written consent; h) direct Flows at children or knowingly collect personal data of persons under 16 through the Service; the Customer must design and target its Flow audiences accordingly.

9.2. Prohibited AI uses. The intended purpose of the Service is the qualification of sales and business enquiries (leads) before a next commercial step. The Customer must not use the Service:

a) for recruitment, evaluation or screening of job candidates or workers, or for any decisions in the employment context; b) to evaluate creditworthiness or establish a credit score, or to price life or health insurance; c) for admission, evaluation or proctoring in education or vocational training; d) for law-enforcement, migration/asylum/border-control, or administration-of-justice purposes; e) to determine natural persons' access to essential public or private services (e.g. housing, healthcare, public benefits); f) to infer emotions, intentions or psychological states of natural persons — in particular in workplace or education contexts — or to derive any conclusions from voice characteristics rather than the content of answers; g) to identify or verify the identity of a person by their voice or other biometric characteristics; or h) in any manner that would make the Service a prohibited practice under Article 5 of the AI Act.

9.3. AI Act roles. Under the AI Act, the Provider is the provider of the LeadPass AI system and the Customer is its deployer. If the Customer modifies the intended purpose of the Service so that its use becomes a high-risk AI system (Article 6 and Annex III of the AI Act), the Customer thereby becomes the provider of that high-risk system within the meaning of Article 25(1)(c) AI Act and assumes all resulting obligations; the Customer will indemnify the Provider against claims and penalties arising from such repurposing. The Customer must not remove, hide or obscure any AI-related disclosure, label or notice built into the Service (including the lead-facing AI and recording notices).

9.4. If the Customer ever publishes AI Outputs or other AI-generated content from the Service to the public, any disclosure duty applicable to such publication (e.g. Article 50(4) AI Act) rests with the Customer as deployer.

9.5. Recording rules. Flows are designed so that the Lead personally and knowingly records their own answers after seeing an on-page notice. The Customer must not use the Service to record any person other than the responding Lead, or any person who has not seen the pre-recording notice — for example by playing back another person's audio into a Flow, recording persons present in the room, or embedding a Flow in a way that hides the notice. The Customer is responsible for compliance with any recording-consent laws applicable to its Leads.

9.6. Retention notice integrity. For each Flow the Customer selects an audio-retention policy (delete after qualification / keep 30 days / keep). The corresponding notice shown to Leads is fixed and non-editable, and the policy a Lead recorded under is honoured even if the Flow's setting is later relaxed (the stricter of the two always applies). The Customer must choose the policy consistently with its own privacy commitments to its Leads.

9.7. Moderation; notice-and-action. Anyone may report allegedly illegal content or misuse of the Service (including content on a Public Flow Page) to legal [at] useleadpass.com, describing the content, its location (URL) and why it is considered illegal. We review reports diligently, objectively and proportionately. We may remove or disable access to content, close a Public Flow Page, or suspend a Flow, a User or an Account where these Terms or the law so require. Except where the law prevents it or protection of the Service demands immediate action, we will inform the affected Customer of the measure taken and its reasons, and the Customer may contest it through the complaint procedure in Section 20.

9.8. Public URL identifiers. Each Workspace and Flow is published under a URL identifier (a "slug") chosen by the Customer, forming part of the public address of its Public Flow Pages on useleadpass.com. Certain Workspace slugs are reserved and cannot be selected: identifiers set aside for LeadPass's own first-party pages, for system or administrative paths and predictable public routes, and any identifier that contains the LeadPass brand. Separately, and whether or not a slug was available when it was chosen, the Provider may require or make a change to a Workspace or Flow slug where it: (a) is or becomes reserved, or collides with a first-party or system route; (b) impersonates, or is likely to be confused with, the Provider, another person or entity, or an official LeadPass page; (c) is unlawful, infringing, deceptive, offensive or otherwise breaches this Section 9; or (d) must be changed for technical, security or operational reasons. Where practicable the Provider will assign a functionally equivalent replacement slug and, except where the law prevents it or protection of the Service or third parties demands immediate action, will inform the Customer of the change and its reasons; the Customer may contest it through the complaint procedure in Section 20. Allocation or use of a slug does not by itself grant the Customer any ownership of, or trademark or other right in, the useleadpass.com identifier, nor guarantee its continued availability; this is without prejudice to the Customer's rights in its own names and marks (Section 16.2). The Customer has no right to transfer or sell a Workspace or Flow slug.

10. Free trial

10.1. The first subscription of an Account includes a 14-day free trial. Subsequent subscriptions of the same Account do not include a trial.

10.2. A supported payment method and billing address are collected at checkout. You will not be charged during the trial. Unless you cancel before the trial ends, your saved payment method will be charged automatically on the first day after the 14-day trial, at the price of the selected Plan and Billing Period disclosed at checkout, and the subscription will then renew as described in Section 11. This is stated at checkout before you confirm the order.

10.3. During the trial, a Starter, Pro or Scale Plan is limited to 1 Workspace, up to 2 Flows in that Workspace (or the selected Plan's lower Flow limit), and 20 completed qualifications. An Agency Plan is limited to 3 Workspaces, 6 Flows pooled across the Account, and 20 completed qualifications pooled across the Account. Full Plan limits unlock only after the first payment is confirmed and the subscription becomes active. You may end the trial early ("start my plan now"), which initiates the first charge for the selected Billing Period — the full annual fee if annual billing was selected. If that payment is not confirmed or the first invoice remains past_due, the trial limits in this Section remain in force; requesting an early start alone does not grant paid entitlements.

10.4. Cancelling during the trial schedules the subscription to end when the trial ends; no subscription fee is charged. Access may end sooner if the Customer separately requests Account deletion under Section 15.2.

10.5. Service start and mandatory withdrawal rights. Access to the trial or paid Platform normally begins immediately after checkout. Starting to use the Service does not by itself waive any mandatory right of withdrawal held by an Entrepreneur with Consumer Rights. Where applicable law requires a separate express request before paid performance begins during a withdrawal period, acceptance of these Terms alone is not treated as that separate request. Section 21 explains the resulting withdrawal mechanics.

11. Fees, billing, renewal and taxes

11.1. Subscription fees, available Plans, Plan limits and Billing Periods (monthly or annual) are those displayed at checkout and on the pricing page at the time of ordering. Fees are stated in euro (EUR) or United States dollars (USD), as displayed at checkout for your Account; once your first subscription is formed, all further charges under your Account are made in that same currency. Fees are exclusive of VAT and other applicable taxes, which are calculated at your billing address and added at checkout and on each invoice (we use Stripe Tax for this purpose). A monthly subscription is charged monthly. An annual subscription is charged once in advance for the full year and renews annually; any monthly-equivalent figure is provided only for comparison and is not a monthly instalment.

11.2. Payment processing is performed by Stripe. Payment-method credentials are collected by Stripe directly in your browser and never pass through our servers. We store the method type and, for a card, its brand and last four digits, plus the billing name, address, country and any VAT ID you provide. You authorise us (through Stripe) to charge your saved payment method for all fees due under the Agreement.

11.3. Automatic renewal. The subscription renews automatically for successive Billing Periods of the same length (month for month, year for year) at the then-current price of your Plan, until you cancel. Each annual renewal is a single charge for the next full year. You can cancel a future renewal at any time in the application (Billing page), with effect at the end of the current paid (or trial) period; until then the Service keeps working, and you may resume the subscription before that date. Cancellation in the application is no more difficult than subscribing.

11.4. Plan changes. Available self-service changes take effect immediately, with any proration handled by Stripe; while a Plan is in its trial period, a change carries no charge — the trial continues to its original end date and the first charge at trial end uses the new Plan's price. Changes within the Direct track or within the Agency track are self-service. Moves between tracks — from a Direct Plan to an Agency Plan, or from an Agency Plan to a Direct Plan — are not currently automated and must be requested through support. A downgrade or move to a lower-capacity Plan can complete only when the Account's existing Workspaces and Flows fit the target Plan's limits; otherwise you must first reduce or restructure those resources where the Service provides that action, select a Plan that fits, or contact support. We do not silently delete Workspaces, Flows or Lead Data to force a Plan change. Until the requirements are met and the change completes, the current Plan and its fees remain in force.

11.5. Price changes. We may change Plan prices only for valid reasons, namely: (a) documented increases in the Provider's costs of providing the Service, including infrastructure, speech-to-text and AI-model usage, payment-processing and compliance costs; (b) changes in taxes or public levies applicable to the Service; (c) a material extension of the scope or features of the affected Plan; or (d) inflation, where the increase does not exceed the annual consumer-price index announced by the President of Statistics Poland (GUS) for the preceding year. A price change will be announced by email at least 30 days in advance, never takes effect during a Billing Period already paid for, and applies at the earliest from the next Billing Period beginning after the notice period. If you do not accept the new price, you may cancel or terminate with effect before the change applies (Section 11.8 governs refunds); continuing into a Billing Period at the new price constitutes acceptance.

11.6. Failed payments. If a renewal charge fails, Stripe retries automatically and we will inform you in the application; the Service is not cut off immediately. If payment ultimately cannot be collected, the subscription ends, access to paid features is blocked until payment, and the data-retention clocks in Section 15 start running.

11.7. Invoices. The Provider issues fiscal invoices electronically using its invoicing system (currently Fakturownia), based on payment and tax information processed through Stripe. When the fiscal invoice has been generated, its link is made available on the Billing page; Stripe remains the payment processor and its payment record is not presented as the Provider's fiscal invoice. You consent to receiving invoices electronically. You must provide accurate invoicing data and keep it current; Customers with a Polish NIP must provide it.

11.8. Refunds. Except where these Terms or mandatory law (including Section 21 for Entrepreneurs with Consumer Rights) provide otherwise, fees for a started Billing Period are not refundable; cancellation stops future renewals but does not refund the current period. However, if the Customer terminates the Agreement under Section 11.5 (price change), 22.3 (adverse modification of the Service) or 23.3 (amendment of these Terms), or the Provider terminates under Section 13.5 (including discontinuation of the Service), the Provider refunds the unused part of any prepaid Billing Period pro-rata, without undue delay and no later than 14 days after the termination takes effect, using the original payment method where possible. A request for immediate Account deletion under Section 15.2 is different from cancelling renewal at the end of the Billing Period and does not, by itself, create a right to a refund. To keep using an annual subscription for the remainder of the prepaid year, cancel its renewal under Section 13.2(a) and do not request Account deletion until that paid period has ended.

11.9. Credit packs (where offered). If and when the Service offers one-off qualification credit packs: packs are charged immediately to the saved payment method at the price shown plus applicable tax; credits are consumed after the Plan's included quota and remain valid for 12 months from the most recent pack purchase; optional auto-recharge is activated only with your express consent and can be switched off at any time; credit purchases are non-refundable except as mandatory law requires. This Section applies only where the pack purchase option is visible in your Account.

12. Plan limits and quota behaviour

12.1. Each Plan defines entitlements, including the number of Workspaces, the number of Flows for the Account, and a pooled monthly quota of completed qualifications for the whole Account. Current limits are shown on the pricing page and in the application.

12.2. Test runs by the Customer and AI-generated example leads do not count toward the completed-qualification quota.

12.3. The completed-qualification quota applies per monthly Usage Period, including where the subscription has an annual Billing Period. An annual payment therefore provides twelve successive monthly quota windows, not one annual pool. Unused quota does not carry over to the next Usage Period.

12.4. When the quota is exhausted: Public Flow Pages stop accepting new Leads until the next monthly Usage Period begins, credits are added, or the Plan is upgraded; Leads already mid-Flow may finish and are recorded. Leads see only a neutral "link closed/full" message that does not reveal the Customer's billing state. We notify the Account by email when the quota runs out (once per Usage Period).

12.5. When a Flow limit is reached, new Flows cannot be created until the Plan allows it. A change to a lower-capacity Plan cannot complete while the Account's existing resources exceed its limits, as described in Section 11.4. Reaching a limit never deletes existing data.

12.6. We may apply reasonable technical rate limits and anti-abuse measures (including per-IP limits, bot protection and upload validation) to protect the Service.

13. Term; termination by the Customer; suspension and termination by the Provider

13.1. The Account contract is concluded for an indefinite term. The subscription runs per Billing Period and renews under Section 11.3.

13.2. Termination by the Customer. You may (a) cancel the subscription at any time with effect at the end of the current Billing Period, retaining access until that date (Section 11.3), and/or (b) request deletion of your Account in the application (password-confirmed). Account deletion is a separate, immediate closure instruction: it closes public links and stops the subscription on the request date rather than preserving access until the end of a prepaid monthly or annual period, subject to the 30-day data-restoration grace mechanics in Section 15.2 and the refund rules in Section 11.8.

13.3. Suspension or termination by the Provider. We may suspend or restrict access to the Service, a Flow or a Public Flow Page, or — in serious cases — terminate the Agreement with immediate effect, where: (a) the Customer or its Users materially breach these Terms (in particular Sections 5.4, 9.1, 9.2, 9.5); (b) the use of the Service creates a security, legal or operational risk to the Service, other customers or third parties; (c) we are required to do so by law or by a competent authority; or (d) fees remain unpaid after the process in Section 11.6. Where reasonably possible we will give prior notice and an opportunity to cure; a suspension is lifted when its cause is removed.

13.4. Any suspension or content removal will be proportionate and accompanied by a statement of reasons to the Customer (except where the law prevents it), and may be contested through the complaint procedure in Section 20.

13.5. We may terminate the Account contract of a Customer without an active subscription for important reasons (including discontinuation of the Service) with at least 30 days' notice by email; Section 15's retention rules then apply.

14. Availability and support

14.1. We provide the Service with due professional care but do not offer a guaranteed uptime level (SLA) under these Terms. Maintenance, updates and technical incidents may cause temporary unavailability; where planned maintenance is expected to cause material downtime, we will use reasonable efforts to announce it in advance.

14.2. Support is provided in English and Spanish by email at legal [at] useleadpass.com during the Provider's business hours. Support requests concerning security or data protection are prioritised.

14.3. Leads mid-Flow are treated gently by design: an interrupted answer session can be resumed from the same browser session, and sessions abandoned for more than 24 hours are closed automatically. Usable transcribed answers may be assessed and produce Pass, Review, No pass or Incomplete under Section 7.1. A session with no usable answer is closed as failed without an overall recommendation; its recordings are removed after the failed-response retry window, while remaining contact/session data follows the retention and deletion rules in the DPA and Privacy Policy.

15. Effect of termination; data retention and deletion

15.1. Upon expiry or termination of the subscription or trial without Account deletion, the Account and its data are retained as follows (as also described in the Privacy Policy and DPA):

a) if the Account has ever started a subscription — including a payment-method-first free trial that never converted to a paid plan: the Lead Data purge target is 12 months after billing access ended, with a warning email at approximately 11 months and never less than 14 days before the first purge attempt; the Account, Users, Flows and criteria are retained so the Customer can return; b) if the Account never started any subscription (an entry-flow trial without a payment method): the Lead Data purge target is 90 days after the trial ends, with a warning at approximately day 76.

The Service removes referenced recordings before deleting their database records. If storage refuses a deletion, completion is blocked and the scheduled purge is retried rather than falsely recorded as complete; therefore a technical retry may finish after the target date.

15.2. Account deletion. When the Customer requests Account deletion: on day 0 all Public Flow Pages are closed and the subscription is cancelled immediately, including an annual subscription with prepaid time remaining; the Customer may undo the deletion with one click at any time during a 30-day grace period, but restoration does not reinstate the cancelled subscription (a reminder is emailed around day 23); after the grace period the Service runs its permanent purge of Workspaces, Flows, Leads, the recordings still referenced by those records, transcripts, AI Outputs and memberships. A tracked recording-storage failure blocks completion so the purge can be tried again. The owner's user profile is deleted if it belongs to no other account, and the Service requests deletion of the associated Stripe customer object. Section 11.8 explains the refund effect and how to preserve access through a paid period instead.

15.3. Records we are legally required or entitled to keep survive deletion, in particular the Provider's fiscal ledger and invoices held through Fakturownia, payment and tax records held through Stripe, and the minimum contract, payment, access and service-delivery evidence described in Section 4.5. Detached evidence is scheduled for deletion on 31 December of the year in which six years have elapsed from Account deletion, subject to any longer period caused by a payment dispute, complaint, proceeding or interruption/restart of the applicable claims period. Deleting the Account or its Stripe customer object does not delete statutory fiscal records before their own deadline. Anonymous, content-free technical telemetry may also survive deletion.

15.4. During the life of the Account the Customer can delete individual Leads (recordings, transcripts and analysis) at any time, and per-Flow audio-retention policies delete recordings automatically as described in Section 9.6. Deletion operations are permanent.

15.5. Securing your data. You are responsible for retrieving any information you need before deletion becomes effective.

15.6. Sections that by their nature survive termination (including fees due, IP, liability, indemnity, governing law) survive.

16. Intellectual property; Customer Data; AI Outputs

16.1. The Service — including its software, design, interfaces, templates, question and criteria presets, documentation and trademarks — is and remains the property of the Provider or its licensors. The Customer receives a non-exclusive, non-transferable, worldwide licence to use the Service for its internal business purposes for the duration of the Agreement.

16.2. Customer Data. As between the parties, the Customer owns all content it or its Users submit to the Service (Flow content, questions, criteria, instructions, branding text) and all Lead Data. The Customer grants the Provider a licence to host, store, process, transmit, display and back up Customer Data solely as needed to provide the Service and meet legal obligations.

16.3. AI Outputs. As between the parties, and to the extent the Provider holds any rights in AI Outputs generated for the Customer, the Provider assigns them to the Customer upon creation; AI Outputs are treated as Customer Data. The Customer acknowledges that AI-generated content may not be protectable by copyright, may be similar to outputs generated for others, and is subject to the accuracy disclaimer in Section 7.2.

16.4. Feedback. If the Customer provides suggestions or feedback about the Service, the Provider may use them without restriction or obligation; feedback never includes Lead Data.

16.5. The Customer warrants that Customer Data and its use in the Service do not infringe third-party rights and that it holds all permissions needed for the Provider to process Customer Data as described in the Agreement.

17. Warranties and disclaimers

17.1. We undertake to provide the Service with due professional care. However, to the maximum extent permitted by law, the Service is provided "as is" and "as available": we do not warrant that the Service will be uninterrupted, error-free or secure against all threats, nor that AI Outputs will be accurate, complete or fit for any particular purpose (Section 7.2).

17.2. We do not guarantee any particular business result (lead quality, conversion, revenue). The Customer remains solely responsible for its commercial decisions.

17.3. Availability, maintenance and support are governed by Section 14; no specific service level (SLA) is offered under these Terms.

17.4. To the extent permitted by law, the parties exclude the Provider's statutory warranty for defects (rękojmia) toward Customers other than Entrepreneurs with Consumer Rights.

17.5. Nothing in this Section limits the rights of Entrepreneurs with Consumer Rights under the statutory conformity regime for digital services (Chapter 5b of the Polish Consumer Rights Act) — see Section 21.5.

18. Liability

18.1. To the maximum extent permitted by law, the Provider's total aggregate liability to the Customer arising out of or in connection with the Agreement, whether in contract, tort or otherwise, is limited to the total fees paid by the Customer for the Service in the 12 months preceding the event giving rise to the claim.

18.2. To the maximum extent permitted by law, the Provider is not liable for: (a) lost profits, lost revenue, lost business opportunities or indirect or consequential loss; (b) decisions the Customer takes on the basis of AI Outputs; (c) the content of Flows, the Customer's notices to Leads, or the data-protection compliance of the Customer or its client controller; (d) unavailability or loss caused by the Customer, its Users, Leads or third-party services outside our control; or (e) force majeure.

18.3. Mandatory exceptions. Nothing in these Terms excludes or limits liability: (a) for damage caused intentionally (Article 473 § 2 of the Polish Civil Code); (b) for death or personal injury to the extent liability cannot be limited; or (c) in any other case where the law does not permit exclusion or limitation. Toward Entrepreneurs with Consumer Rights, the limitations in this Section apply only to the extent permitted by the provisions applicable to them (Section 21).

18.4. Claims under the DPA (including for personal-data breaches attributable to the Provider as processor) are subject to the liability regime stated there or, absent one, to this Section 18.

19. Indemnification

19.1. The Customer will indemnify and hold the Provider harmless from third-party claims, fines and reasonable costs (including legal fees) arising from: (a) Customer Data or the content of its Flows; (b) the Customer's breach of Sections 8 (data-protection duties), 9 (acceptable use, prohibited AI uses, recording rules) or 16.5; (c) repurposing of the Service into a high-risk or prohibited AI use (Section 9.3); or (d) the Customer's failure to give Leads legally required notices.

19.2. The Provider will promptly notify the Customer of any such claim and allow the Customer to conduct the defence, while retaining the right to participate at its own cost. The Customer may not settle a claim imposing obligations on the Provider without the Provider's consent.

20. Complaints procedure (reklamacje)

20.1. Complaints about the Service — from Customers, Users or Leads — may be submitted by email to legal [at] useleadpass.com and should include: the complainant's name and email address, the Account or Public Flow Page concerned (if applicable), a description of the issue, and the outcome requested.

20.2. We will respond within 14 days of receipt, on a durable medium (email). If a complaint cannot be resolved in that time, we will explain why and give a target date.

20.3. This procedure also serves for contesting moderation, slug-change and suspension decisions under Sections 9.7, 9.8 and 13.4.

20.4. Using the complaint procedure does not limit the Customer's statutory rights or the right to pursue claims in court. An Entrepreneur with Consumer Rights may also use the out-of-court dispute-resolution options available to them under applicable law.

21. Entrepreneurs with Consumer Rights

21.1. This Section applies to an Entrepreneur with Consumer Rights (as defined in Section 2) and prevails over any conflicting provision of these Terms. It does not apply to companies, partnerships or other non-natural persons, nor to natural persons for whom the Agreement has a professional character.

21.2. At checkout we may ask you to indicate whether the purchase has a professional character for you in view of your registered business activity. Such a declaration helps assess your status but does not override the statutory test.

21.3. Right of withdrawal. An Entrepreneur with Consumer Rights may withdraw from the Agreement within 14 days of its conclusion (checkout), without giving reasons, by an unambiguous statement sent to legal [at] useleadpass.com — the model form in Annex A may be used but is not obligatory. To meet the deadline it is enough to send the statement before the period expires. We will confirm receipt on a durable medium.

21.4. Withdrawal mechanics for a digital service. Access normally begins immediately after checkout as described in Section 10.5. If you withdraw during the first free trial, the subscription ends and you owe no subscription fee. If a subscription starts with an immediate payment, including a later subscription for which no trial is available, the financial consequences of withdrawal follow mandatory law: a proportionate charge for service already supplied applies only where the legally required express request for early performance was made; otherwise no such charge is due. Any refund due will be made without undue delay and no later than 14 days after we receive the withdrawal statement, using the original payment method unless the law permits and you agree otherwise. Nothing in these Terms treats ordinary use of the Service as a waiver of the right of withdrawal.

21.5. Conformity of the digital service. The statutory regime for the conformity of digital services (Chapter 5b of the Polish Consumer Rights Act, implementing Directive (EU) 2019/770) applies, including the duty to supply updates (including security updates), the statutory remedies for non-conformity (bringing into conformity, price reduction, termination), and the conditions for modifying the service. Nothing in Sections 17–18 limits those rights.

21.6. Unfair-clause protection. The provisions of Articles 385¹–385³ of the Polish Civil Code (abusive clauses) apply as provided by Article 385⁵ of the Polish Civil Code.

21.7. Jurisdiction. The exclusive-jurisdiction clause in Section 24.3 does not apply to an Entrepreneur with Consumer Rights (or to any consumer); statutory jurisdiction rules apply instead.

22. Changes to the Service

22.1. We continuously develop the Service and may add, modify or improve features, and change or discontinue features of minor significance, provided the core functionality described in Section 3.1 and the agreed protections are maintained.

22.2. We may modify the Service beyond what is necessary to maintain conformity only for valid reasons, namely: adapting to new legal or regulatory requirements; security; preventing abuse; fixing errors; technical evolution of the infrastructure or of the AI models used; or genuine improvement of the Service. Such modifications are made at no extra cost to the Customer.

22.3. If a modification materially and adversely affects the Customer's access to or use of the Service, we will notify the Customer by email in advance, and the Customer may terminate the Agreement free of charge with effect within 30 days of the notice (or of the modification, if later). For Entrepreneurs with Consumer Rights the statutory regime referenced in Section 21.5 applies.

23. Changes to these Terms

23.1. We may amend these Terms for important reasons only: changes in law or its authoritative interpretation; decisions of authorities or courts; introduction, change or withdrawal of features of the Service; changes of sub-processors or technical providers; security or abuse-prevention needs; editorial corrections that do not reduce the Customer's rights; or changes in the Provider's business data.

23.2. Price changes are governed by Section 11.5.

23.3. We will announce amendments by email to the Account owner and/or a prominent in-application notice at least 14 days before they take effect, together with the new text and its effective date. If the Customer does not accept the amendment, it may terminate the Agreement (or cancel the subscription) with effect no later than the day before the amendment takes effect. Continued use after the effective date constitutes acceptance. Amendments never apply retroactively and never affect a Billing Period already paid, except changes required by law or changes solely in the Customer's favour, which may take effect earlier.

23.4. The current version of the Terms is available at https://useleadpass.com/legal/terms in a form that can be saved and printed. The Service does not currently publish a customer-facing archive of previous versions, so Customers should retain the copy supplied with a change notice or downloaded when they accept or renew.

24. Governing law and jurisdiction

24.1. The Agreement is governed by Polish law, excluding its conflict-of-laws rules. The United Nations Convention on Contracts for the International Sale of Goods (CISG) does not apply.

24.2. The choice of Polish law does not deprive a consumer, or an Entrepreneur with Consumer Rights where applicable, of the protection afforded by provisions that cannot be derogated from by agreement under the law otherwise applicable to them.

24.3. For Customers other than consumers and Entrepreneurs with Consumer Rights, all disputes arising out of or in connection with the Agreement are subject to the exclusive jurisdiction of the Polish common court competent for the registered seat of the Provider.

24.4. Electronic records of the Agreement include the append-only events and archived legal-document versions described in Section 4.5, together with the related Stripe subscription, payment and invoicing records. A checkout offer, the Account owner's confirmation and verified subscription formation are recorded separately and linked by the Checkout Session reference.

25. Final provisions

25.1. Language. The contract language is English. Any courtesy translation of these Terms is for convenience only; the English version prevails, except where mandatory law grants a person the right to a version in another language.

25.2. Contact point. Our single electronic point of contact for authorities and for users of the Service (including for reports under Section 9.7) is legal [at] useleadpass.com. Communications may be made in English or Polish.

25.3. Assignment. The Customer may not assign the Agreement without the Provider's consent, which will not be unreasonably withheld. The Provider may assign the Agreement to an affiliate or to a successor in connection with a merger, reorganisation or sale of the business, with notice to the Customer.

25.4. Confidentiality. Each party will keep confidential non-public information received from the other in connection with the Agreement and use it only to perform the Agreement, except for disclosures required by law or made to professional advisers bound by confidentiality.

25.5. Force majeure. Neither party is liable for failure to perform (other than payment obligations) caused by events beyond its reasonable control.

25.6. Severability. If any provision of these Terms is held invalid or unenforceable, the remaining provisions remain in force, and the invalid provision is replaced by the valid provision closest to its economic purpose.

25.7. Entire agreement; order of precedence. The Agreement (these Terms, the DPA and the Plan/order parameters) is the entire agreement between the parties regarding the Service and supersedes prior arrangements. In case of conflict: (1) the DPA prevails for the processing of Lead Data; (2) otherwise these Terms prevail over any other document unless the other document expressly amends them in writing.

25.8. These Terms enter into force on 12 July 2026.

Annex A — Model withdrawal form

(Complete and return this form only if you are an Entrepreneur with Consumer Rights (or a consumer) and wish to withdraw from the contract.)

To: Jose Ramon Leon Rodriguez, Egipska 5/69, 03-977 Warszawa, Poland, email: legal [at] useleadpass.com

I/We (*) hereby give notice that I/we (*) withdraw from my/our (*) contract for the provision of the following service: LeadPass subscription (Account email: ____________________).

Ordered on: ____________________

Name of the person(s): ____________________

Address of the person(s): ____________________

Signature (only if this form is notified on paper): ____________________

Date: ____________________

(*) Delete as appropriate.