Legal
Terms of Use and Policies
LeadAI Legal Policy Stack
LeadAI Pty Ltd · ABN 83 679 856 305 · ACN 664 941 253
These documents contain LeadAI's standard legal and policy terms. Together with Customer's accepted in-app or checkout controls and any accepted Custom Plan Document, they form the complete Agreement between LeadAI and each Customer. A feature-specific, conditional, or optional schedule applies only when its stated scope is triggered. By accessing or using the Service, you agree to be bound by the applicable terms below.
1. Master Terms / Terms of Use and Sale
Last Updated: 13 November 2026
Parties
LeadAI Pty Ltd (ABN 83 679 856 305; ACN 664 941 253), with its principal place of business in Victoria, Australia ("LeadAI", "we", "us", "our") and the entity or person accepting these Master Terms ("Customer", "Client", "you", "your").
Scope
These Master Terms govern access to and use of the hosted software-as-a-service platform known as the "LeadAI Voice AI Agent Portal" and any related features, modules, tools, APIs, integrations, updates, onboarding assistance, professional services, support, credits, and services introduced from time to time (collectively, the "Service"), including communications delivered via voice calls, SMS, email, and related workflows, automations, and analytics.
1. Acceptance of these Terms and authority to bind
1.1 Acceptance
You accept and agree to these Master Terms (the "Terms") when you: (a) click an "I agree", "Accept", "Confirm", "Purchase", "Subscribe", or similar button or checkbox; (b) create an account; (c) place an order through any checkout flow; (d) access or use any part of the Service; (e) authorise any End User to use the Service; or (f) agree, verbally or in writing, to go ahead with a plan, or log in using a voucher, temporary login or other Early Access (see clause 10.9).
1.2 Authority to bind
If you accept these Terms on behalf of a company or other entity, you confirm you have authority to bind that entity. If you do not have authority, do not accept these Terms or use the Service.
1.3 Updates
We may update these Terms and any incorporated policies from time to time. The "Last Updated" date shows the current version. We will give at least thirty (30) days' notice of a material change that adversely affects an existing Customer, and the change will take effect from that Customer's next subscription date unless a later date is stated. We may make an immediate change where reasonably necessary to comply with law, address a security or abuse risk, correct an error, or introduce a change that does not materially reduce the Customer's rights during a paid Term. A change to pricing or usage rates will not apply retrospectively to a Term already paid for unless an applicable Custom Plan Document expressly provides otherwise. Continued use after the effective date constitutes acceptance.
1.4 Additional terms
Some features may have additional terms shown in the Service (for example, feature-specific terms, beta terms, or usage limits). If presented, those terms form part of this Agreement.
2. What's included and which terms control
2.1 Agreement
These Master Terms, together with all incorporated policies and schedules (the "Policy Stack"), any Order Form (if any), and any in-app/checkout plan controls and settings, form the entire agreement between the parties (the "Agreement").
2.2 Incorporated Policies
The following documents are incorporated by reference and form part of the Agreement, as published by LeadAI from time to time:
- Acceptable Use Policy (AUP);
- Communications Compliance Policy (Voice/SMS/Email);
- Data Processing Addendum (DPA);
- Privacy Policy;
- Cookie Notice;
- Service Credits, Metering, Billing, Overages, Refunds, Chargebacks & Collections Policy;
- Support Policy;
- Security & Data Handling Statement;
- Appointment Setting / Scheduling Addendum (if enabled);
- Prohibited/Restricted Use and Risk Categories Schedules;
- AU Compliance Schedule;
- US Compliance Schedule;
- Recording & Transcription Schedule; and
- Definitions Schedule.
2.3 Order of Precedence
If there is any conflict or inconsistency, the following order of precedence applies (highest to lowest), and Customer agrees that pricing and operational controls are governed accordingly:
- Customer-specific in-app plan controls, account settings, and checkout controls (including allowances, metering, billing cadence, payment authorisations, credit/top-up settings, and feature toggles) as accepted for the current paid Term, subject to the paid-Term protections in the Billing Policy;
- any Order Form, SLA, promotional plan terms, or other custom plan document expressly accepted by LeadAI in writing or through checkout (each a "Custom Plan Document"), but only to the extent it expressly identifies the term it overrides;
- these Master Terms;
- the incorporated Policy Stack documents and schedules; and
- any proposals, statements of work, marketing pages, public pricing pages, promotional materials, emails, or verbal statements (all of which are non-binding and do not vary the Agreement), except agreements made on a call, in a meeting or in writing under clause 2.5, and LeadAI's written confirmation of an Early Access plan and Fees under clause 10.9, all of which bind.
Despite the commercial order above, the DPA governs over these Master Terms solely to the extent of a direct conflict concerning data-protection or processing obligations. In-app and checkout controls do not reduce LeadAI's or Customer's obligations under the DPA or applicable law unless an accepted Custom Plan Document lawfully and expressly varies the relevant DPA term.
2.4 Promotions and "Unlimited*"
Promotions or discount links may be offered from time to time and may be withdrawn before acceptance. Pricing, eligibility, and application of a promotion are determined by the in-app controls, checkout controls, and any applicable Custom Plan Document. A Custom Plan Document may override these standard Terms only where it expressly states the override; otherwise, these Terms continue to apply. If a plan description uses "Unlimited*" or an asterisk, it means the feature is subject to the Fair Usage Limits and restrictions described in this Agreement and the Billing Policy.
2.5 Agreements Made on Calls and Meetings
Anything Customer agrees with LeadAI's team on a phone call, in a video or virtual meeting (such as Microsoft Teams, Zoom or Google Meet) or in person is a binding agreement, in the same way as if it had been agreed in writing. This includes agreeing to go ahead with a plan, a price, a start date, onboarding, an add-on, an upgrade or another change to the account. An agreement on a plan, price or other commercial term made with a human member of LeadAI's team has the same effect as a Custom Plan Document.
It works both ways. A request Customer makes on a call or in a meeting, including a request to change or cancel a plan, counts as made on the day of that call or meeting, and clause 12.2 then sets when it takes effect. The recording or transcript of the call or meeting (clause 7.6) is the record of what was agreed, and LeadAI may also confirm it in writing.
Only a human member of LeadAI's team can agree, on LeadAI's behalf, a discount, a free period or a change to these Terms. General sales conversation, estimates, examples and descriptions of features are not agreements and do not vary the Agreement.
3. Key definitions
3.1 End Users
"End Users" means any individual who accesses or uses the Service under Customer's account, including Customer's employees, contractors, agents, and authorised users, as well as any person Customer permits to interact with workflows, dashboards, recordings, transcripts, analytics, or outputs.
3.2 Contacts
"Contacts" means any individual whose information, identifiers, or communication details are processed through the Service in connection with Customer's use, including call recipients, SMS recipients, email recipients, leads, customers, prospects, and any other data subjects, whether or not they are End Users.
3.3 Customer Data
"Customer Data" means all data, content, records, contact lists, scripts, messages, templates, prompts, call lists, suppression lists, recordings, transcripts, campaign configuration, metadata, and other materials submitted to, generated within, transmitted through, or otherwise processed via the Service by or on behalf of Customer (including by End Users), including Personal Information of Contacts.
3.4 Personal Information
"Personal Information" has the meaning given under applicable privacy laws, including the Privacy Act 1988 (Cth), and includes information about an identified individual or an individual who is reasonably identifiable.
3.5 Feature Outputs
"Outputs" means any results, analytics, insights, summaries, classifications, recommendations, or generated content provided by the Service (including AI-assisted outputs), whether displayed in dashboards, delivered via messages, or produced via exports or APIs.
4. Accounts and security
4.1 Eligibility
Customer must be legally capable of entering into a binding contract. Customer must ensure End Users meet applicable age and eligibility requirements.
4.2 Account Registration
Customer must provide accurate, current, and complete information and keep it updated. LeadAI may refuse, suspend, or terminate accounts for inaccurate information or risk concerns.
4.3 Account Security
Customer is responsible for maintaining the confidentiality of credentials and for activities occurring under its account to the extent caused by Customer's or an End User's act, omission, credential sharing, or failure to use reasonable security controls. Customer must promptly notify LeadAI of any suspected unauthorised access or security incident. Customer is not responsible to the extent unauthorised activity is caused by LeadAI's breach of the Agreement or failure to maintain the safeguards expressly required by the Agreement.
4.4 Administrators
Customer is responsible for managing access, roles, permissions, API keys, integrations, and administrator settings. Customer acknowledges that administrators may access, export, delete, or otherwise control Customer Data and End Users.
4.5 Device and Network
Customer is responsible for all devices, telecommunications services, internet connections, email domain configuration, DNS records, authentication (SPF/DKIM/DMARC where applicable), and security controls used to access the Service.
5. Using the Service
5.1 License
Subject to Customer's compliance with the Agreement and payment of all Fees, LeadAI grants Customer a limited, non-exclusive, non-transferable, non-sublicensable (except to End Users as permitted), revocable right to access and use the Service during the Term solely for Customer's internal business purposes and in accordance with the Agreement.
5.2 Use Restrictions
Customer must not, and must not permit any End User or third party to:
- use the Service in violation of any law, regulation, code, or third-party rights;
- use the Service for emergency services, dispatch, or life-safety communications;
- interfere with, disrupt, or attempt to gain unauthorised access to the Service, systems, networks, or data;
- reverse engineer, decompile, disassemble, or otherwise attempt to derive source code or underlying components except to the extent prohibited by law (and then only after providing notice and allowing LeadAI to respond);
- bypass or circumvent usage limits, security controls, or access restrictions;
- use the Service to transmit malware, spyware, ransomware, or destructive code;
- scrape, harvest, or collect information from the Service except as permitted via provided export tools;
- resell, rent, lease, time-share, or provide the Service to third parties as a service bureau, except as expressly authorised by LeadAI in writing;
- use the Service for any prohibited or restricted categories identified in the AUP or Prohibited/Restricted Use Schedules, without required approvals; or
- do anything prohibited by clause 9.7 (Prohibited Conduct), including accessing or operating the Service with AI agents, bots or other automation, or trying to extract prompts, scripts or other Protected Materials.
5.3 No Reliance; AI and Automated Outputs
Customer is solely responsible for all decisions, actions, and outcomes arising from use of the Service and any Outputs. AI-generated or automated Outputs may be inaccurate, incomplete, delayed, misleading, unsuitable, or inconsistent. Customer must independently review and verify Outputs before relying on them or allowing them to affect a Contact, transaction, quote, booking, payment, legal right, compliance process, or business decision. The Service is a communications and workflow tool; it is not a substitute for legal advice, compliance review, professional judgment, or human supervision.
5.4 Assisted Setup, Onboarding and Customer Approval
LeadAI may, at Customer's request, assist with onboarding, configuration, prompts, scripts, templates, integrations, workflows, testing, publication, activation, or operation of the Service ("Assisted Setup"). Assisted Setup is technical and administrative assistance only. It is not legal advice, compliance advice, campaign approval, recipient-list verification, or an independent audit of Customer's instructions or use.
Customer retains access to and control of its account and is solely responsible for reviewing, testing, validating, and approving every configuration before it is released to Contacts or the public. This includes scripts, prompts, disclosures, recording notices, sender identity, recipient lists, consent and list provenance, suppression settings, calling times, integrations, automations, pricing, representations, appointment rules, escalation paths, and Outputs.
If Customer directs LeadAI to activate, publish, launch, run, or continue a configuration, or permits a configuration to go live after having a reasonable opportunity to review it, Customer is deemed to have completed its review and given final approval. Customer remains responsible even where LeadAI performed the technical act of activation or operated the Service at Customer's direction. To the maximum extent permitted by law, LeadAI is not liable for claims, losses, penalties, communications, or outcomes arising from Customer-approved instructions, configurations, content, recipient data, compliance settings, or use that Customer failed to review or correct.
5.5 Business Use Warranty
Customer represents and warrants that it acquires and uses the Service solely for business or commercial purposes and not for personal, domestic, or household use. This clause does not exclude any right or remedy that cannot lawfully be excluded, including protections that apply to eligible small business standard-form contracts.
6. Communications and compliance
6.1 Customer-Directed Communications
Customer controls, selects, and determines all communication recipients, targeting, timing, cadence, scripts, content, sender identities, phone numbers, email domains, and campaign parameters. The Service executes communications only as configured, instructed, approved, or operated by Customer. As between LeadAI and Customer, Customer is the sender, caller, authoriser, and business responsible for each communication and campaign.
6.2 Customer Compliance Obligation (Critical)
Customer bears sole responsibility for ensuring that all communications and related processing comply with all applicable laws, including without limitation:
- Australia: Spam Act 2003 (Cth), Do Not Call Register Act 2006 (Cth), Privacy Act 1988 (Cth) (including APPs), applicable state/territory surveillance devices and call recording laws, ACMA guidance, consumer and telemarketing rules;
- United States: TCPA, TSR, CAN-SPAM, state telemarketing laws, state recording/two-party consent laws, and all federal/state DNC/DND obligations; and
- Other regions: GDPR/UK GDPR, PECR/ePrivacy, CASL (Canada), and any local telecom, privacy, consumer protection, marketing, and surveillance laws.
LeadAI does not determine whether a communication is lawful, whether a Contact has consented, whether an exemption applies, or which jurisdiction's rules govern. Customer must obtain its own legal or compliance advice where required. Nothing in this allocation excludes any obligation imposed directly on LeadAI that cannot lawfully be transferred or excluded.
6.3 Suppression Lists and Consent Records
Customer must maintain suppression lists (including DNC/DND), opt-out handling, consent records, lawful bases, disclosure scripts, and proof of permissions for all Contacts.
6.4 Prohibited Emergency Use
Customer must not use the Service for emergency calling, emergency response, crisis lines, medical emergencies, dispatch, or any use where failure, delay, or inaccuracy could lead to harm. Customer acknowledges telecom routes, delivery, and availability are variable, and the Service is not designed or warranted for emergency use.
6.5 Carrier and Deliverability Factors
Customer acknowledges message deliverability and call completion depend on carriers, telecom routing, spam and fraud filters, recipient device settings, number reputation, email authentication, and third-party systems. LeadAI does not guarantee delivery, answer rates, call quality, or message placement.
6.6 Continuing Review and Supervision
Customer must continuously supervise its use of the Service and promptly pause or correct any workflow, campaign, Output, or communication that may be inaccurate, unlawful, misleading, unsafe, or inconsistent with Customer's instructions. LeadAI's assistance, monitoring, testing, moderation, failure to detect an issue, or decision not to suspend an account does not approve Customer's use or reduce Customer's responsibility.
6.7 Communications from LeadAI to Customer
By accepting these Terms, Customer agrees, and confirms it has authority to agree for its End Users, to receive phone calls, SMS, emails and meeting invitations from LeadAI's team (human staff and AI staff) about the account, onboarding, support, billing, and LeadAI's products, updates and offers. This consent is on by default. Customer can stop marketing messages at any time by using the unsubscribe link, replying STOP or telling LeadAI. Account, billing, security and service messages continue while the account is open.
7. Recording and transcription
7.1 Default ON
Call recording and transcription are ON by default as part of the Service workflow, and transcription is required for agent operation.
7.2 Customer Notice and Consent
Customer is solely responsible for providing legally sufficient notices and obtaining all required consents for recording, transcription, monitoring, and communications, including consents required by surveillance and privacy laws in every relevant jurisdiction.
7.3 Scripts and Disclosures
Customer must ensure scripts, prompts, and call flows include required disclosures (including recording notices) and comply with applicable laws and platform requirements.
7.4 Alternative Workflows by Request
Disabling recording and/or transcription, or implementing an alternative workflow, may be available on request and is subject to technical feasibility, LeadAI approval, and any fees or terms stated in the applicable in-app controls, checkout controls, Order Form, or SLA. LeadAI may refuse a request where the alternative would materially affect Service integrity, security, supportability, or lawful operation.
7.5 Customer Risk Allocation
Customer assumes all risk arising from recording/transcription configuration, including legal compliance, evidentiary consequences, and disputes with Contacts.
7.6 Calls, Meetings and Messages with LeadAI
All phone calls, video and virtual meetings (such as Microsoft Teams, Zoom or Google Meet), voicemails, SMS, emails and chat messages between LeadAI's team (human staff or AI staff) and Customer, its End Users or anyone acting for Customer are recorded and transcribed by default, and kept with Customer's account records. By accepting these Terms, Customer consents to this recording and must make sure its End Users and anyone acting for it know about it.
LeadAI uses these recordings and transcripts to provide and support the Service, keep a record of what was agreed (clause 2.5), handle billing and disputes, check and improve the quality of its team and AI staff, and meet its legal obligations. Customer may ask at the start of a call or meeting for it not to be recorded; LeadAI may then ask for anything agreed to be confirmed in writing instead. Recordings and transcripts are handled under the Privacy Policy.
8. Customer Data; Ownership; Licences; De-Identified Improvement Use
8.1 Customer Data Ownership
As between the parties, Customer retains its rights in Customer Data. LeadAI does not acquire ownership of Customer Data by providing the Service.
8.2 Licence to Operate
Customer grants LeadAI a worldwide, non-exclusive licence to host, process, transmit, copy, display, perform, analyse, disclose, and otherwise use Customer Data as necessary to provide, maintain, secure, support, and improve the Service; operate Customer-directed communications and integrations; prevent abuse; comply with law; and enforce the Agreement. This licence includes authority to disclose or make Customer Data available to Subprocessors, telecommunications and delivery providers, infrastructure and hosting providers, payment processors, analytics and support providers, security providers, professional advisers, and Customer-authorised integration providers where reasonably necessary for those purposes.
8.3 De-Identified Improvement Use
LeadAI may use data processed in connection with the Service to improve, test, develop, and train the Service and its models where the data has been anonymised, de-identified, or aggregated so that no individual, Contact, or Customer is reasonably identifiable. LeadAI will not knowingly attempt to re-identify that data. LeadAI may also process identifiable Customer Data where reasonably necessary for quality assurance, support, safety, abuse prevention, security, compliance, billing, and operation of the Service, including human review by authorised personnel subject to confidentiality obligations.
8.4 Customer Representations
Customer represents and warrants that it has all rights, permissions, lawful bases, notices, and consents necessary to provide Customer Data to LeadAI and to direct LeadAI and its Subprocessors to process and disclose Customer Data as contemplated by the Agreement, including cross-border processing and Customer-directed communications.
8.5 Sensitive Categories
Customer must not provide sensitive categories of information (including health data, biometric identifiers, payment card data, government identifiers, or special category data) unless expressly approved by LeadAI in writing and configured using safeguards required by LeadAI.
9. Intellectual Property; Feedback
9.1 LeadAI IP
LeadAI retains all rights, title, and interest in and to the Service, including software, models, workflows, templates, designs, interfaces, documentation, AI Staff, LeadAI Brand Assets and all other Protected Materials (clauses 9.4 to 9.6), and any improvements, derivatives, or modifications, and all associated intellectual property rights. Nothing in the Agreement transfers any of these to Customer.
9.2 Feedback
If Customer provides suggestions, ideas, requests, or feedback, Customer grants LeadAI an irrevocable, perpetual, worldwide, royalty-free right to use and incorporate such feedback without obligation or restriction.
9.3 No Implied Rights
Except as expressly stated, no rights are granted by implication, waiver, estoppel, or otherwise.
9.4 AI Staff, Personas and Brand Assets
LeadAI's AI staff members and avatars, including Emily (Emily Swift), Anna, Carol, Jenny, Emma and Sam, and every other AI staff member, persona, character or avatar that LeadAI creates or uses now or in the future (each an "AI Staff" member), are LeadAI's business assets and intellectual property. This includes, for each AI Staff member:
- names, nicknames, titles, roles and job descriptions;
- images, likenesses, appearance, avatars, photographs, illustrations, animations and videos;
- voices, voice profiles, accents, tone, speech patterns and audio recordings; and
- personalities, backstories, résumés, profiles, catchphrases, greetings, humour and manner of speaking.
LeadAI also owns the LeadAI name, logos, trade marks (registered or not), trade dress, business and domain names, social media pages and accounts, slogans, the look and feel of LeadAI's app, websites, videos and materials, and the goodwill in all of them ("LeadAI Brand Assets").
9.5 Protected Materials
The following are LeadAI's intellectual property, trade secrets and Confidential Information, together with AI Staff and LeadAI Brand Assets (all of them the "Protected Materials"):
- system prompts, role prompts, agent instructions, prompts and prompt structures;
- call, email and SMS scripts, templates, openers, objection handling, booking rules, scripting rules, standards and playbooks;
- call flows, conversation designs, stages, journeys, workflows, automations, outcome and classification logic, lead scoring, routing, cadences and timing rules;
- the configurations, settings, tools, functions, integrations and knowledge bases that make up how AI Staff behave and perform;
- the Service's software, source code, object code, models, model settings, APIs, databases, data structures, architecture, interfaces and documentation; and
- LeadAI's testing methods and results, call-review processes, improvement data and know-how.
This applies wherever the material appears (in the app, on calls, in emails and texts, on LeadAI's websites, videos and social media, or anywhere else), whether it was created before or after the date of this Agreement, and whether it was created for Customer's account (including during Assisted Setup). Customer's own business information inside a script or configuration (such as its business name, services, prices and contact details) remains Customer Data, which LeadAI may use under clause 8.2.
9.6 The Unique Combination
Even where a single element of an AI Staff member or other Protected Material might not be protected on its own (for example a common first name, a stock voice, a generic image or a standard phrase), the particular selection, arrangement, combination and coordination of those elements is LeadAI's intellectual property, trade secret and Confidential Information. For example, an AI Staff member's name together with their voice, image, personality, scripts, prompts and behaviour is protected as a whole. Customer must not copy, imitate or recreate that combination, or anything substantially or confusingly similar to it.
9.7 Prohibited Conduct
Customer must not, and must not permit or help any End User, staff member, contractor, related body corporate, AI tool, agent or other third party to, directly or indirectly:
- copy, reproduce, record, download, extract, export, reconstruct, adapt, translate, imitate or create derivative works of any Protected Materials, except as needed to use the Service in the normal way;
- reverse engineer, decompile, disassemble, decrypt, inspect, analyse or probe the Service's code, network traffic, APIs, prompts, models or anything behind the user interface, including with browser developer tools, proxies, traffic interception or API exploration;
- try to reveal, extract or reconstruct any system prompt, script, instruction, rule or configuration, including by prompt injection, jailbreaking, social engineering or questioning AI Staff on calls, by text or by email;
- access, use or operate the Service with any AI agent, AI assistant, computer-use or browser-control tool, bot, crawler, scraper, headless browser, script, macro, robotic process automation or other automated means, or in any way that goes beyond a person using the Service through its normal user interface, except through LeadAI's published APIs and integrations used as documented, or as LeadAI approves in writing;
- use any Protected Materials, Outputs, recordings, transcripts or the Service to train, fine-tune, test, benchmark, evaluate or improve any AI model, agent or product, or to design, build or improve any product or service that competes with or is similar to LeadAI;
- clone, synthesise, deepfake or imitate the voice, image, likeness or persona of any AI Staff member, or use their names or likenesses in any product, advertising, social media or content, other than references to the Service that LeadAI has approved;
- register or use any business, company or domain name, social media handle, trade mark or AI persona that is the same as, or confusingly similar to, any LeadAI Brand Asset or AI Staff member;
- disclose, publish, sell or give any Protected Materials to any third party, including another AI or software provider, a consultant or a competitor; or
- remove or obscure any LeadAI notice, branding or attribution.
Each of these is a "Protected Materials Breach". Customer must make sure its End Users, staff, contractors and anyone given access to its account comply with this clause, and is responsible for their breaches as if they were its own.
9.8 Monitoring
LeadAI may monitor, log and analyse access to and use of the Service, including access patterns, devices, automation signals and AI Staff conversations, to detect, investigate and prove a Protected Materials Breach.
9.9 Remedies for a Protected Materials Breach
Customer agrees that a Protected Materials Breach would cause LeadAI serious and irreparable harm for which damages alone would not be an adequate remedy. If Customer commits a Protected Materials Breach, or LeadAI reasonably suspects one, then in addition to every other right and remedy LeadAI has:
- Account freeze. LeadAI may immediately and without notice suspend, freeze or restrict all access to the Service, including every account, End User and API key linked to Customer, and keep it frozen while it investigates.
- Termination. LeadAI may terminate the Agreement immediately by notice. All amounts owed, including Fees for the rest of the current Term, become immediately due, and no Fees are refunded.
- Injunction. LeadAI may seek urgent injunctive relief, specific performance and other equitable relief in any court, without having to prove actual damage. Customer will not oppose an application on the ground that damages would be an adequate remedy.
- Liquidated damages. Where Customer, or anyone it is responsible for, copies, extracts, discloses or uses Protected Materials, or uses them to build, train or improve another product or service, Customer must pay LeadAI AUD $100,000 for each such breach. The parties agree this amount is a genuine pre-estimate of LeadAI's minimum loss, reflecting the cost, time and value of developing the Protected Materials, and is not a penalty. LeadAI may instead elect to recover its actual loss, or an account of Customer's profits, where either is greater.
- Damages without limit. Customer's liability for a Protected Materials Breach is not limited or excluded by any part of the Agreement, and includes LeadAI's loss of profits, revenue, goodwill and the value of the Protected Materials.
- Costs. Customer must pay LeadAI's costs of investigating and enforcing the breach, including legal costs on a full indemnity basis, and forensic and expert costs.
- Delivery up. Customer must immediately stop all use of the Protected Materials and, on request, return, destroy or permanently delete every copy of them and anything made from them, and confirm in writing (by statutory declaration if LeadAI asks) that it has done so.
- Cooperation. Customer must preserve evidence and give LeadAI the information and access it reasonably asks for to investigate the breach.
- Indemnity. Customer must indemnify LeadAI against all claims, losses, liabilities, costs and expenses arising from the breach.
9.10 Survival and Other Rights
Clauses 9.4 to 9.11 continue after the Agreement ends. LeadAI's ownership of the Protected Materials does not depend on the Agreement: LeadAI may also enforce its rights under the law of copyright, trade marks, designs, passing off, confidential information and trade secrets, and the Australian Consumer Law, against anyone, whether or not they have accepted these Terms.
9.11 LeadAI's Successors
References to LeadAI in this clause 9 include its related bodies corporate, successors and assigns, and any company, business name or brand that LeadAI or its successors operate under in future. LeadAI may assign or license any of its rights in the Protected Materials without Customer's consent.
10. Fees and billing
10.1 Fees
Customer must pay all fees, charges, and amounts displayed or incurred via the in-app plan controls and checkout controls ("Fees"), including subscription fees, usage-based charges, overages, credits/top-ups, add-ons, implementation fees, and any applicable taxes.
10.2 Pricing Hierarchy Controls
Subject to any express Custom Plan Document override and the paid-Term protections in the Billing Policy, Customer-specific in-app plan controls and checkout controls prevail over public pricing pages, proposals, marketing materials, or verbal statements.
10.3 Metering
Customer acknowledges and agrees that:
- inbound and reception calls are billed in one-minute increments;
- outbound calls are billed in six-second increments;
- a Connected Minute begins when a call is answered, including by voicemail; dialling, ringing, and unanswered calls are not billed as Connected Minutes;
- SMS is billed per SMS Segment, with each segment billed separately;
- email is billed per message; and
- AI usage may be billed per AI Conversation, token, compute unit, or other unit shown in the in-app or checkout controls.
LeadAI may change measurement methods or billing increments prospectively by giving thirty (30) days' notice, effective from Customer's next subscription date. Usage records maintained by LeadAI are authoritative except in the case of manifest error or to the extent prohibited by non-excludable law.
10.4 Overages and Automatic Charging (Enabled by Default)
If Customer exceeds included allowances or consumes additional usage, Customer authorises LeadAI (and its payment processors) to automatically charge for overages at then-current in-app rates and/or automatically purchase additional credits/top-ups. This mechanism is enabled by default unless LeadAI enables a disablement feature for Customer's account and Customer successfully disables it.
10.5 Taxes
Fees are exclusive of taxes, duties, levies, GST/VAT, and similar charges. Customer is responsible for all applicable taxes (except taxes on LeadAI's net income). LeadAI may collect taxes where required.
10.6 Payment Methods; Authorisation
Customer must maintain valid payment details. Customer authorises recurring and usage-based charges without further notice. Failure to maintain valid payment details constitutes a material breach.
10.7 Pricing Errors
LeadAI may correct obvious pricing or billing errors at any time, including after payment. LeadAI may (at its discretion) charge the corrected amount or terminate the affected order and refund the amount paid for the erroneous charge.
10.8 Onboarding, Support and Custom Plans
Onboarding, implementation assistance, support packages, purpose-built agents, custom journey flows, pilots, promotional plans, and other custom arrangements may be available on request. Scope, availability, fees, billing cadence, minimum term, prepayment requirements, and any included support are plan-dependent and apply only where shown in the in-app controls, checkout controls, Order Form, or SLA. No fixed onboarding or support fee is created by these Terms. Onboarding, setup and implementation fees are non-refundable (clause 11.1).
10.9 Early Access, Vouchers and Temporary Logins
LeadAI may give Customer access to the Service before checkout or payment is complete, for example through a voucher or voucher code supplied by a member of LeadAI's team, a temporary or early-access login, or an account set up after Customer agrees to go ahead on a phone call, in a video or virtual meeting, by email, by text message or in person ("Early Access"). Early Access is a paid arrangement, not a free trial, unless LeadAI's written offer expressly says the access is free and for how long. Early Access is "first given" on the day LeadAI first sends Customer the voucher, voucher code, login or account details.
- Agreement to pay. Customer agrees to these Terms, and to pay the Fees for the plan offered, when Customer agrees to go ahead (verbally or in writing) or first logs in to or uses the Service through Early Access, whichever happens first. A verbal agreement, including one made on a phone call or in a video or virtual meeting, binds Customer in the same way as clicking "Accept" (see clause 2.5).
- Plan and Fees. The plan, Fees and any onboarding fee are those agreed with Customer on a call or in a meeting, or confirmed to Customer in writing (for example by email, text message, voucher or in-app controls), when Early Access is given. That agreement or confirmation forms part of the Agreement. If no plan or price has been agreed or confirmed, the standard price for the plan set on Customer's account, as shown in the Service or in LeadAI's published pricing, applies.
- Automatic billing within seven (7) days, and no later than fourteen (14) days. LeadAI will normally bill the first Fees within seven (7) days after Early Access is first given, and in any case no later than fourteen (14) days after (the date LeadAI bills being the "First Billing Date"). Customer authorises LeadAI and its payment processors to charge those Fees on or before the First Billing Date. This applies whether or not Customer has completed checkout, added a payment method or held a follow-up call with LeadAI. LeadAI may bill earlier if Customer completes checkout or asks to be billed.
- First Term. Customer's first paid Term starts on the day Early Access is first given, unless LeadAI's written offer states a different start date.
- No payment method on file. If no valid payment method is on file at the First Billing Date, LeadAI may issue a tax invoice, which is payable within seven (7) days of its date. Clauses 11.3 (Collections) and 12.3 (Suspension) apply to any amount not paid by its due date.
- Deciding not to go ahead. Customer may decide not to go ahead by telling LeadAI in writing, at support@leadai.com.au, before the First Billing Date. LeadAI will then close the Early Access and will not charge the plan Fee or onboarding fee. Usage beyond anything the offer included (for example calls, SMS or email) may still be charged at the plan rates. After the First Billing Date, clauses 11 and 12 apply as for any other subscription.
11. Refunds, disputes and non-payment
11.1 No Refunds
LeadAI does not give refunds. All Fees are non-cancellable and non-refundable once paid or invoiced. This includes subscription Fees for the full paid Term, onboarding, setup, implementation and build fees, usage charges, overages, Service Credits and top-ups. The only exceptions are a refund that non-excludable law requires (see clause 23.2) and clause 12.5 (LeadAI ending the Service for its own convenience).
Onboarding is non-refundable. Onboarding, setup, implementation and build fees pay for work LeadAI starts as soon as Customer signs up. That work includes planning, building AI Staff, scripts, prompts and call flows, setting up numbers and integrations, and reserving onboarding time. These fees are non-refundable once paid or invoiced, whether or not onboarding is finished and whether or not Customer uses the Service.
What does not give a refund. None of the following entitles Customer to a refund, credit, discount or early release from a Term:
- change of mind, or deciding after sign-up that the Service is not a fit;
- inconvenience;
- Customer or its staff not being available, or being unable to make time, for onboarding, training, setup or review meetings;
- missed, late, cancelled or rescheduled meetings or calls;
- delays of any kind, including delays in onboarding, setup or going live, and delays caused by Customer (such as late information, approvals, access, number porting or integrations) or by third parties (such as carriers, email and calendar providers, or integration providers);
- not logging in, not using the Service, or using less of it than expected;
- results such as answer rates, conversations, bookings, leads or sales not meeting Customer's expectations;
- temporary unavailability, deliverability issues, carrier filtering or ordinary performance variability;
- changes in Customer's business, staff, plans or circumstances; or
- suspension or termination of the account because of Customer's breach or non-payment.
11.2 Billing Disputes and Chargebacks
Customer must first raise a billing dispute with LeadAI and provide reasonable information to allow investigation. A chargeback or payment reversal does not extinguish the underlying payment obligation. Where a chargeback is initiated, LeadAI may suspend paid functionality, require prepayment or a deposit, restrict further usage, and recover reasonable processor and administrative costs while the matter is investigated. LeadAI will review a properly documented billing dispute within a commercially reasonable period. Nothing in this clause prevents a Customer from exercising a right that cannot lawfully be waived.
11.3 Collections
Overdue amounts accrue interest from the due date until paid at the lower of 1.5% per month and the maximum rate permitted by law. Customer must reimburse LeadAI for commercially reasonable collection costs, including legal fees, agency fees, and enforcement expenses.
11.4 Set-Off
LeadAI may set off an overdue and undisputed amount owed by Customer against an amount payable by LeadAI to Customer.
12. Term, suspension and termination
12.1 Term
The Agreement begins on acceptance and continues until terminated in accordance with this Agreement ("Term").
12.2 Subscriptions
Subscriptions renew automatically for successive periods as set in the in-app or checkout controls unless cancelled before the applicable renewal date. To avoid being charged for the next Term, Customer must complete cancellation through the available Service controls before the renewal date shown in the Service or applicable checkout controls. If cancellation controls are unavailable, Customer may cancel by sending a request to support@leadai.com.au that is received before the renewal date.
A monthly subscription commits Customer for the month, a quarterly subscription commits Customer for the quarter, and an annual subscription commits Customer for the year. "No lock-in" means Customer is committed only for the selected paid Term; it does not convert a quarterly or annual Term into a monthly arrangement. Annual subscriptions are prepaid and cannot be ended early for convenience. Cancellation takes effect at the end of the current paid Term and stops the next renewal. A cancellation received after a renewal has occurred takes effect at the end of the newly renewed Term and does not reverse or refund the renewal charge, except where required by non-excludable law. Discontinuing use, deleting an application, removing a payment method, or allowing a payment method to expire does not cancel a subscription. Purpose-built agents and custom journey flows may require annual prepayment where stated in the applicable Custom Plan Document.
12.3 Suspension
LeadAI may suspend or restrict access immediately where reasonably necessary if LeadAI believes:
- Customer or End Users breached the Agreement or applicable law;
- Customer's use poses a security risk, reputational risk, or risk to telecom deliverability;
- fraud, chargeback abuse, or material payment risk exists;
- required consents are missing;
- prohibited or restricted use is suspected; or
- suspension is required to protect the Service, other customers, or third parties.
For ordinary non-payment, LeadAI may place the account into read-only mode and pause communications when an amount remains unpaid for seven (7) days after its due date. LeadAI may terminate the account when the amount remains unpaid for thirty (30) days after its due date. LeadAI may act sooner in cases of fraud, repeated payment failure, chargeback abuse, unlawful use, security risk, or where required by law.
12.4 Termination by Customer
Customer may terminate by cancelling all subscriptions through the Service controls or, where those controls are unavailable, by sending a cancellation request to support@leadai.com.au. Cancellation and renewal timing are governed by clause 12.2. Merely discontinuing use does not cancel a subscription or relieve Customer of accrued payment obligations. Cancelling does not give a refund of any Fees already paid or invoiced, including onboarding fees (clause 11.1).
12.5 Termination by LeadAI
LeadAI may terminate the Agreement immediately for a material breach that is incapable of remedy, unlawful or prohibited use, fraud, serious security or compliance risk, insolvency, or non-payment continuing for thirty (30) days. For a remediable material breach, LeadAI may terminate if Customer does not remedy the breach within a reasonable period stated in notice. LeadAI may discontinue the Service or terminate for convenience on at least thirty (30) days' notice. If LeadAI terminates for convenience and Customer is not in breach, LeadAI will provide a pro-rata refund or account credit for unused prepaid recurring plan Fees, excluding consumed usage, Service Credits, setup work, and non-refundable third-party costs.
12.6 Effect of Termination
Upon termination:
- Customer's licence ends immediately;
- Customer must cease use of the Service;
- all amounts owed become immediately due;
- Customer may request an export during the thirty (30)-day post-termination export window, after which LeadAI may delete Customer Data in accordance with its retention and deletion practices; and
- any provisions that by their nature should survive will survive, including limitations of liability, indemnities, confidentiality, dispute resolution, and payment obligations.
13. Data Retention; Backups; Export; Deletion
13.1 Default Retention
Unless a different period is stated in an applicable Custom Plan Document or required by law, primary Customer Data is retained for up to ninety (90) days from creation or last active processing. Following termination, Customer Data will remain available for export for up to thirty (30) days and will be deleted or irreversibly de-identified no later than ninety (90) days after termination, subject to clause 13.4.
13.2 Backups
LeadAI may maintain backups and limited copies for operational, security, disaster recovery, compliance, billing, abuse prevention, or legal purposes. When Customer Data is removed from primary systems, backup copies will be placed beyond active use and deleted or irreversibly de-identified within the same applicable ninety (90)-day retention or post-termination deletion period. Normal backup rotation does not create an additional ninety (90)-day retention period. A legal hold or non-excludable obligation may require longer retention as described in clause 13.4.
13.3 Export Requests
Customer may request export of Customer Data at any time while the account is active and during the thirty (30)-day period after termination, subject to identity verification, reasonable administrative fees disclosed in advance, and technical feasibility. LeadAI will process a valid request within a commercially reasonable timeframe.
13.4 Deletion
Deletion occurs within the periods stated above and is subject to legal holds, security requirements, billing reconciliation, abuse prevention, dispute preservation, and other non-excludable obligations. Where longer retention is required for one of those purposes, LeadAI may isolate and restrict the data to that purpose and delete or irreversibly de-identify it when the reason ends.
13.5 Inactive Accounts
If an account has no meaningful login, communication, workflow, or usage activity for six (6) consecutive months, LeadAI may give notice and close the account. Any remaining Service Credits are forfeited, have no cash value, and are non-refundable. LeadAI may grant an extension on request at its discretion.
14. Confidentiality
14.1 Confidential Information
"Confidential Information" means non-public information disclosed by one party to the other that is marked confidential or should reasonably be understood as confidential, including Customer Data (to the extent it is non-public), the Service's non-public features and security details, and all Protected Materials (clause 9.5), whether or not marked confidential.
14.2 Obligations
Each party must protect the other's Confidential Information using commercially reasonable safeguards and must not disclose it except as permitted by the Agreement.
14.3 Permitted Disclosures
A receiving party may disclose Confidential Information to its employees, contractors, and professional advisers who have a need to know and are bound by confidentiality obligations at least as protective as those herein.
14.4 Compelled Disclosure
A party may disclose Confidential Information if required by law or court order, and where lawful, will provide reasonable notice and cooperate in seeking protective treatment.
14.5 Exclusions
Confidential Information does not include information that is publicly available without breach, independently developed, lawfully received from a third party, or approved for release in writing.
15. Disclaimers
15.1 Service Provided AS IS
The Service is provided "AS IS" and "AS AVAILABLE", with all faults and without warranties of any kind.
15.2 No Warranties
To the maximum extent permitted by law, LeadAI disclaims all warranties and conditions, express or implied, including merchantability, fitness for purpose, title, non-infringement, accuracy, and uninterrupted availability.
15.3 No Guarantee of Outcomes
LeadAI does not warrant deliverability, call completion, answer rates, call quality, transcription accuracy, analytics accuracy, AI output correctness, compliance outcomes, revenue outcomes, or suitability for any specific campaign.
15.4 Third-Party Dependencies
Customer acknowledges the Service relies on telecom carriers, email delivery networks, infrastructure providers, and other third parties. LeadAI is not responsible for third-party outages, filtering, blocking, throttling, latency, or policy enforcement.
16. Limitation of liability and risk allocation
16.1 Risk Allocation
Customer acknowledges that the Fees reflect the allocation of risk and limitation of liability set out in the Agreement.
16.2 Excluded Damages
To the maximum extent permitted by law, in no event will LeadAI be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for loss of profits, revenue, goodwill, data, business interruption, or replacement service costs, even if advised of the possibility.
16.3 Liability Cap
To the maximum extent permitted by law, LeadAI's total aggregate liability arising out of or relating to the Agreement will not exceed the total Fees actually paid or payable by Customer to LeadAI for the Service in the twelve (12) months preceding the event giving rise to the claim.
16.4 Time Bar
To the extent permitted by law, a claim arising from the Agreement must be brought within twelve (12) months after the claimant became aware, or reasonably should have become aware, of the facts giving rise to the claim. This clause does not shorten a limitation period that cannot lawfully be shortened.
16.5 Customer-Controlled Risks
To the maximum extent permitted by law, LeadAI is not liable for claims, penalties, losses, or liabilities to the extent caused by Customer's or an End User's instructions, Customer Data, recipient selection, scripts, prompts, configuration, Assisted Setup approval, failure to test or supervise, unlawful or prohibited use, lack of consent, missing disclosure, or breach of the Agreement. Customer acknowledges that these matters remain within Customer's control even where LeadAI provides technical assistance or performs an action at Customer's direction.
16.6 Essential Purpose
If any remedy fails of its essential purpose, the limitations and exclusions of liability remain in effect to the maximum extent permitted by law.
17. Indemnity
17.1 Indemnity
To the maximum extent permitted by law, Customer must indemnify, defend, and hold harmless LeadAI from and against third-party claims, regulatory investigations, demands, fines, penalties, damages, liabilities, and reasonable costs and expenses (including legal fees) to the extent caused by or arising from:
- Customer's or End Users' use of the Service;
- Customer Data, scripts, prompts, content, targeting, and campaigns;
- alleged or actual violations of communications, privacy, telemarketing, spam, surveillance, consumer protection, or similar laws;
- failure to obtain required consents or provide required disclosures (including recording/transcription notices);
- alleged infringement or misuse of third-party rights arising from Customer Data or Customer's instructions;
- any fraudulent or improper chargeback, reversal, or payment dispute initiated by Customer or on Customer's behalf;
- any restricted or prohibited use category, whether or not LeadAI detected such use; and
- Assisted Setup, activation, publication, or operation performed in accordance with Customer's instructions or approval.
The indemnity does not apply to the extent a claim is finally determined to have been caused by LeadAI's breach of the Agreement, negligence, fraud, wilful misconduct, or breach of a non-excludable obligation.
17.2 Process
LeadAI will give Customer reasonable notice of a claim subject to indemnity and may, at its option, control its defence and settlement. Customer must provide reasonable cooperation at Customer's expense. Neither party may settle such a claim in a manner that requires an admission of liability or non-monetary obligation from the other party without that party's written consent, not to be unreasonably withheld or delayed.
18. Publicity; References; Testimonials
18.1 Logo and Identification
Unless Customer opts out in writing to legalteam@leadai.com.au, LeadAI may use Customer's name and logo to identify Customer as a customer of LeadAI in marketing materials and on LeadAI channels, provided LeadAI does not disclose Customer's Confidential Information.
18.2 Case Studies
Publication of non-confidential case studies requires Customer's approval, which may be granted or withheld in Customer's discretion.
18.3 Testimonials and Feedback
LeadAI may publish a testimonial attributed to Customer only with Customer's prior written approval. LeadAI may use unattributed and de-identified feedback to improve and market the Service where it does not identify Customer or disclose Customer Confidential Information.
19. Security; Data Location; Incident Handling
19.1 Safeguards
LeadAI will maintain commercially reasonable administrative, technical, and physical safeguards designed to protect Customer Data.
19.2 Data Location
Primary storage is in Australia. Limited processing may occur in other jurisdictions due to telecom routing, delivery providers, and infrastructure/subprocessors.
19.3 Subprocessors
Customer authorises LeadAI to use and change Subprocessors and third-party providers where reasonably necessary to provide, secure, support, bill, and improve the Service. Customer Data may be disclosed to those providers for the relevant service purpose, subject to contractual, confidentiality, security, and legal controls appropriate to the nature of the processing. LeadAI is not required to publish a named provider list unless required by applicable law or an accepted Custom Plan Document.
19.4 Security Certifications
LeadAI may use providers with industry certifications (ISO 27001 / SOC 2 or equivalents). LeadAI does not promise that LeadAI itself is certified.
19.5 Incidents
LeadAI will notify Customer of a confirmed Security Incident affecting Customer Data where required by law and otherwise where LeadAI reasonably determines notification is appropriate. Timing and content may depend on investigation, containment, law-enforcement requirements, and applicable law.
20. Disputes and notices
20.1 Informal Resolution
Before commencing formal proceedings, Customer must provide written notice of the dispute to legalteam@leadai.com.au describing the dispute and the relief sought. The parties will attempt in good faith to resolve the dispute for at least thirty (30) days after notice.
20.2 Formal Proceedings
If the dispute is not resolved during the informal resolution period, either party may commence proceedings in a court of competent jurisdiction in Victoria, Australia. The parties may instead agree in writing to binding arbitration administered by the Australian Centre for International Commercial Arbitration ("ACICA"), seated in Melbourne, Victoria, Australia, in English, by a single arbitrator.
20.3 Injunctive Relief
Either party may seek urgent injunctive or equitable relief in a court of competent jurisdiction to protect intellectual property, Confidential Information, security, or prevent ongoing harm without first completing informal resolution.
20.4 Notices to LeadAI
Legal notices to LeadAI must be sent to legalteam@leadai.com.au and will be deemed received when acknowledged by LeadAI or, if not acknowledged, within two (2) business days of successful transmission.
20.5 Notices to Customer
LeadAI may provide notices to Customer via email associated with the account, in-app notifications, or other reasonable means. An email notice is deemed received on the next business day after sending unless LeadAI receives a delivery-failure notice; an in-app notice is deemed received when displayed in Customer's account.
21. Governing Law
The Agreement is governed by the laws of Victoria, Australia, excluding conflict of law principles. Subject to clause 20, the parties submit to the exclusive jurisdiction of the courts of Victoria, Australia.
22. Miscellaneous
Customer must not assign or transfer the Agreement without LeadAI's prior written consent, which will not be unreasonably withheld. LeadAI may assign the Agreement to an Affiliate or in connection with a merger, financing, reorganisation, or sale of all or substantially all of the relevant business or assets, and may otherwise assign with reasonable notice. LeadAI is not liable for delays or failures due to events beyond its reasonable control, including carrier outages, infrastructure failures, internet disruptions, strikes, pandemics, regulatory changes, or acts of God. If any provision is held invalid or unenforceable, it will be modified to the minimum extent necessary to be enforceable, and the remaining provisions remain in full force. Failure to enforce any provision is not a waiver of future enforcement. The parties are independent contractors. The Agreement is the entire agreement regarding its subject matter and supersedes prior agreements or representations. Headings are for convenience only. "Including" means "including without limitation".
23. Schedules & Appendices
23.1 Policy Stack Schedules
The Policy Stack documents listed in clause 2.2 are incorporated and form part of this Agreement as schedules and appendices, as published and updated by LeadAI from time to time.
23.2 Australian Consumer Law (ACL) and Non-Excludable Rights
Nothing in the Agreement excludes, restricts, or modifies any consumer guarantee, right, or remedy that cannot be excluded under the Australian Consumer Law or other non-excludable law. Where LeadAI is liable for breach of a non-excludable guarantee, LeadAI's liability is limited (at LeadAI's option) to resupplying the relevant services or paying the cost of resupply, to the maximum extent permitted by law.
2. Acceptable Use Policy (AUP)
Last Updated: 12 November 2026
Scope
This Acceptable Use Policy governs permitted and prohibited use of the LeadAI Voice AI Agent Portal and applies to all End Users, Contacts, Customer Data, communications, campaigns, integrations, and use of voice, SMS, email, and related workflows/analytics.
1. Application; Incorporation; Enforcement
1.1 Incorporation
This AUP forms part of the Agreement and is incorporated into the Master Terms.
1.2 Responsibility
Customer is responsible for all End Users and all activity under Customer's account, including any third-party integrations configured by Customer.
1.3 Monitoring and Enforcement
LeadAI may monitor usage patterns and may take measures reasonably necessary to enforce this AUP or protect the Service, Contacts, communications networks, or third parties, including suspending or terminating affected use, limiting throughput, disabling features, or requiring corrective actions. LeadAI will provide notice where practicable, but may act immediately where reasonably necessary to address illegality, abuse, security, safety, or material network risk. LeadAI has no obligation to monitor and does not assume liability for failing to detect violations.
2. General Prohibitions
Customer must not, and must not permit any End User or third party to, use the Service to:
2.1 Break the Law
Violate any applicable law, regulation, code, directive, industry rule, or regulator guidance, including privacy, communications, consumer protection, spam, telemarketing, surveillance, and recording laws.
2.2 Infringe Rights
Infringe or misappropriate intellectual property rights, privacy rights, publicity rights, confidentiality obligations, or contractual rights of any person.
2.3 Harm, Threaten, or Harass
Engage in harassment, threats, intimidation, stalking, defamation, hateful conduct, discrimination, or targeted abuse.
2.4 Fraud and Deception
Engage in fraud, phishing, scams, social engineering, impersonation, misrepresentation of identity or affiliation, or deceptive practices, including misleading caller ID practices where unlawful.
2.5 Illegal Content or Services
Promote or facilitate illegal goods, illegal services, or unlawful conduct.
2.6 Exploit or Endanger
Exploit, groom, or endanger minors or vulnerable persons, or facilitate trafficking or exploitation.
2.7 Security Abuse
Introduce malware; probe, scan, or test vulnerabilities; attempt to bypass rate limits or access controls; or otherwise interfere with Service security or integrity.
2.8 Spam and Unsolicited Communications
Send, initiate, or facilitate spam, bulk unsolicited messages, or high-volume outreach without valid consent and lawful bases, including failure to honour opt-outs.
2.9 Data Misuse
Collect, purchase, use, or upload lists obtained unlawfully or without appropriate consents; use harvested data; or upload Personal Information without authority.
2.10 Interference with Networks
Disrupt carriers, email networks, recipient systems, or third-party services, including excessive bounce/spam rates or abusive calling patterns.
2.11 Platform Circumvention
Circumvent compliance controls, risk checks, identity verification, or feature restrictions; use workarounds to enable prohibited categories; access or operate the Service with AI agents, bots or other automation beyond a person using its normal user interface; or try to extract, copy or reverse engineer prompts, scripts, AI Staff or other Protected Materials (see Master Terms clauses 9.4 to 9.9).
2.12 Emergency Use
Use the Service for emergency services, dispatch, life-safety communications, or any use where failure or delay could reasonably be expected to cause harm.
3. Restricted and High-Risk Categories
3.1 Risk Categories
The Service may be used in higher-risk industries only if Customer (a) discloses the category before use, (b) provides documentation reasonably requested by LeadAI, and (c) obtains written approval if required by LeadAI. High-risk categories include those described in the Prohibited/Restricted Use Schedule and Risk Categories Schedule.
3.2 No Implied Approval
Absence of detection or enforcement by LeadAI does not constitute approval. Customer remains solely responsible for compliance and assumes all risk.
3.3 Right to Suspend
LeadAI may suspend or terminate access immediately where LeadAI determines, in its discretion, that Customer's use creates unacceptable risk to recipients, regulators, carriers, deliverability, or LeadAI.
4. Data and Privacy Requirements
4.1 Minimum Necessary Data
Customer must limit Customer Data to what is necessary for lawful use and must avoid uploading sensitive categories unless approved in writing by LeadAI.
4.2 Security Controls
Customer must maintain reasonable security controls, including access control, least privilege, MFA where available, secure API key storage, and prompt removal of access for departed End Users.
4.3 Suppression Lists and Consent Records
Customer must maintain suppression lists and consent records and must be able to evidence lawful permission for communications when requested by LeadAI.
5. Communications-Specific Rules
Customer must comply with the Communications Compliance Policy and applicable schedules. Customer must use accurate and lawful sender identities and must not spoof, misrepresent, or conceal identity where unlawful or deceptive. Customer must implement opt-out mechanisms and honour opt-outs promptly across channels, including maintaining updated suppression lists.
6. Investigations; Cooperation; Remediation
LeadAI may request information to assess compliance, including samples of scripts, consent records, suppression list practices, campaign descriptions, and identity verification. Customer must respond promptly and accurately. LeadAI may require Customer to take corrective actions, including pausing campaigns, changing scripts, enabling disclosures, reducing volume, or reconfiguring workflows. Customer is responsible for reasonable costs caused by Customer's breach or non-compliance, including remediation, audits, investigations, and LeadAI administrative work, provided LeadAI discloses any non-urgent charge in advance.
7. Consequences of Violation
LeadAI may suspend, restrict, or terminate affected use for an AUP violation or reasonably suspected violation. LeadAI may act immediately where necessary to address illegality, abuse, security, safety, communications-network integrity, or material third-party risk and will provide notice where practicable. Suspension or termination caused by Customer's breach does not create a refund or credit entitlement except where required by non-excludable law. LeadAI may report conduct where legally required or reasonably necessary to protect rights, safety, or the Service.
3. Communications Compliance Policy (Voice/SMS/Email)
Last Updated: 15 July 2026
Scope
This Communications Compliance Policy applies to all communications initiated, scheduled, sent, or facilitated through the Service (voice calls, SMS, email), including call recording and transcription, workflows, automations, analytics, and any use of Contact data for communications purposes. This policy allocates compliance obligations to Customer and sets minimum compliance expectations for use of the Service.
1. Core Compliance Allocation
1.1 Customer Sole Responsibility
Customer bears full responsibility for all compliance obligations related to the use of the Service and all communications, including content, targeting, recipients, timing, frequency, disclosures, consents, suppression lists, and lawful bases.
1.2 Non-Exhaustive Laws
Customer must comply with all applicable laws and guidance, including those listed in the AU Compliance Schedule and US Compliance Schedule and any other regional requirements applicable to Customer, End Users, or Contacts.
1.3 No Compliance Services
LeadAI does not provide legal advice, compliance advice, campaign review, or regulatory assurance. Any information provided by LeadAI is general and does not replace independent legal review.
1.4 Assisted Setup Does Not Transfer Responsibility
Customer's responsibility is unchanged where LeadAI assists with onboarding, scripts, prompts, templates, list import, disclosures, integrations, campaign configuration, testing, activation, or operation. Customer must independently review and approve the complete setup before communications begin and must continue supervising it after launch. Directing LeadAI to launch, publish, activate, run, or continue a campaign constitutes Customer approval. LeadAI's assistance or failure to identify an issue is not compliance approval and does not create a duty to verify Customer's use.
2. Consent; Lawful Basis; Permissioning
2.1 Affirmative Consent Where Required
Customer must obtain prior express consent or prior permission where required by applicable law for voice calls (including automated or AI-assisted calls), SMS, and email communications.
2.2 Consent Records
Customer must maintain verifiable records of consents and lawful bases, including timestamp, method, scope, channel, and any disclosures shown at the point of consent.
2.3 Scope and Purpose Limitation
Customer must ensure communications are within the scope and purpose for which consent was obtained and must not use Contact information for unrelated campaigns without a lawful basis.
2.4 Third-Party Lists
Customer must not use purchased, scraped, harvested, or brokered lists unless Customer can prove lawful collection and valid permissions for the intended channels and jurisdictions. LeadAI may require proof at any time.
3. Suppression Lists; Opt-Out; DNC/DND
3.1 Suppression Lists Mandatory
Customer must maintain suppression lists (including do-not-contact/do-not-call/do-not-email) and ensure suppression is applied across all campaigns and channels.
3.2 Prompt Honour of Opt-Outs
Customer must provide opt-out mechanisms where required and must honour opt-outs promptly and consistently. Customer must ensure that "STOP" (or equivalent) SMS opt-outs and email unsubscribe requests are processed and propagated across relevant systems.
3.3 DNC/DND Compliance
Customer must comply with all DNC/DND obligations, including registry checks, internal do-not-contact lists, and any required time-of-day restrictions.
3.4 No Workarounds
Customer must not circumvent suppression by rotating numbers, domains, identities, or accounts. Such conduct is a material breach and a violation of the AUP.
4. Disclosures; Identification; Transparency
4.1 Accurate Identification
Customer must accurately identify itself (and where required, identify that an AI agent is being used) and must not mislead Contacts as to identity, affiliation, or purpose.
4.2 Required Disclosures
Customer must provide all required disclosures, including telemarketing disclosures, consent disclosures, and recording/transcription disclosures, as required by law in each relevant jurisdiction.
4.3 Sender Identity and Reply Paths
Customer must ensure sender identities (numbers, email addresses, domains) are valid, lawful, and capable of receiving replies or opt-out requests where required.
5. Recording and Transcription Compliance
5.1 Default ON; Customer Notice Duty
Recording is ON by default and transcription is ON by default and required for agent operation. Customer must provide notice and obtain all required consents for recording and transcription.
5.2 Two-Party Consent Jurisdictions
Where two-party (all-party) consent applies, Customer must ensure consent is obtained prior to recording. Customer must implement scripts or preambles to secure consent and must handle refusal (including terminating the call or switching to non-recorded alternatives where lawful and approved).
5.3 Retention and Access Controls
Customer must control access to recordings and transcripts, apply least privilege, and ensure only authorised End Users access recordings and transcripts.
5.4 Opt-Out Requests
Disabling recording/transcription is by request and subject to approval and fees as set out in the Agreement and Recording & Transcription Schedule.
6. Campaign Design; Frequency; Quiet Hours
Customer must design outreach with reasonable frequency and must avoid harassment or excessive contact attempts. Customer must comply with time-of-day restrictions, public holiday restrictions, and local calling rules applicable to the Contact's location. Customer must ensure content is lawful, not deceptive, not harassing, and not in violation of consumer protection laws.
7. Prohibited Use for Emergency Services
Customer must not use the Service for emergency calling or dispatch. Customer must not represent to Contacts that the Service is suitable for emergencies or time-critical safety communications.
8. Verification; Audit Assistance; Enforcement
LeadAI may request evidence of consents, suppression list practices, scripts, and campaign details. Customer must provide information promptly. LeadAI may throttle, suspend, restrict, or terminate affected use where reasonably necessary for compliance risk or suspected non-compliance, with notice where practicable. LeadAI's monitoring or enforcement does not transfer Customer's obligations or constitute approval of any use.
4. Data Processing Addendum (DPA)
Last Updated: 15 July 2026
Scope
This Data Processing Addendum ("DPA") governs LeadAI's processing of Personal Information and other Customer Data on behalf of Customer in connection with the LeadAI Voice AI Agent Portal and related Service. This DPA forms part of the Agreement and applies where LeadAI processes Customer Data that includes Personal Information relating to Contacts or End Users.
1. Incorporation; Order of Precedence
This DPA is incorporated into and forms part of the Agreement. If there is a conflict between this DPA and the Master Terms, this DPA governs solely with respect to data protection and processing obligations; otherwise, the Master Terms govern. In-app plan and checkout controls remain controlling for commercial and operational settings. This DPA includes an Australia-first core module and a conditional GDPR/UK GDPR module that applies automatically only where Customer's use of the Service is subject to GDPR or UK GDPR.
2. Roles and Scope of Processing
Customer as Controller
Customer is the Controller of Customer Data (including Personal Information of Contacts and End Users) to the extent Customer determines the purposes and means of processing through use of the Service.
LeadAI as Processor
LeadAI is the Processor of Customer Data processed on behalf of Customer to provide the Service. LeadAI may process limited data as an independent controller where required for LeadAI's legitimate business operations, including account administration, billing, collections, fraud prevention, security, risk management, product and service integrity, and compliance with law.
Customer Instructions
Customer instructs LeadAI to process and disclose Customer Data as necessary to provide the Service as configured by Customer and End Users, including for call routing, SMS/email delivery, workflows and automations, recording and transcription (default ON), analytics, customer support, Assisted Setup, integrations, billing, security, and technical operations.
3. LeadAI Obligations
Processing on Instructions
LeadAI will process Customer Data on documented instructions from Customer unless required by law to process otherwise. LeadAI will ensure persons authorised to process Customer Data are subject to confidentiality obligations. LeadAI will implement and maintain commercially reasonable administrative, technical, and physical safeguards designed to protect Customer Data.
Subprocessing
Customer gives LeadAI general authorisation to engage and change Subprocessors and third-party providers to process Customer Data for the Service, including telecommunications routing, delivery, infrastructure, hosting, analytics, payments, support tooling, integrations, and security services. LeadAI will impose contractual confidentiality, data-protection, and security obligations appropriate to the nature of the processing. LeadAI is not required to publish a named Subprocessor list unless required by applicable law or an accepted Custom Plan Document.
4. Customer Obligations
Customer is solely responsible for establishing and documenting lawful bases for processing, including consents, notices, and opt-out mechanisms required for voice, SMS, email, recording, and transcription. Customer is responsible for configuring the Service to comply with applicable law, including suppression list handling, scripts, disclosures, recording consent flows, and any campaign timing rules. Customer must maintain and apply suppression lists, DNC/DND rules, and consent records and ensure such controls are used across channels. Customer must maintain appropriate access controls and account security.
5. Cross-Border Processing and Data Location
Primary storage of Customer Data is in Australia. Customer acknowledges and authorises limited processing in other jurisdictions where reasonably necessary for telecommunications routing, delivery, infrastructure, Subprocessors, integrations, support, and operation of the Service. Customer is responsible for ensuring its instructions, notices, consents, and use are lawful under Applicable Data Protection Laws, including APP 8 where applicable to Customer. LeadAI remains responsible for obligations imposed directly on LeadAI that cannot lawfully be transferred or excluded.
6. Security Incidents
LeadAI will notify Customer of a confirmed Security Incident affecting Customer Data where required by law and otherwise where LeadAI reasonably determines notification is appropriate. Timing and content may depend on investigation, containment, law-enforcement requirements, and applicable law. LeadAI will take commercially reasonable steps to investigate, mitigate, and remediate a Security Incident within LeadAI's control. Customer must cooperate with LeadAI's reasonable requests for information and actions to address Security Incidents.
7. Audits and Assessments (Limited)
Any audit rights are limited to assessing LeadAI's compliance with this DPA as it relates to Customer Data and are subject to reasonable security, confidentiality, and operational controls. LeadAI may ordinarily satisfy an audit request by providing summaries of security measures, third-party attestations, or other relevant compliance documentation. Where Applicable Data Protection Laws require further access and the supplied information is not reasonably sufficient, LeadAI will allow and contribute to a reasonable audit or inspection by Customer or its independent auditor. Audits must be remote where possible, occur no more than once per 12-month period unless required by a regulator or following a material Security Incident, exclude penetration testing and vulnerability scanning, and be conducted on at least 30 days' prior written notice where practicable. Customer must protect LeadAI's and other customers' Confidential Information and pay LeadAI's reasonable costs unless the audit identifies a material breach by LeadAI.
8. GDPR / UK GDPR Module (Conditional)
This module applies automatically only where GDPR or UK GDPR applies to Customer's use of the Service. Customer is the Controller and LeadAI is the Processor for Customer Data processed on Customer's behalf. Clauses 2 to 7, this clause 8, and Schedule 1 are intended to form the parties' controller-processor terms for that processing.
In addition to its other DPA obligations, LeadAI will, to the extent required by applicable GDPR or UK GDPR:
- process personal data only on Customer's documented instructions, including instructions concerning international transfers, unless processing is required by applicable law;
- inform Customer where LeadAI reasonably believes an instruction infringes applicable data-protection law, unless LeadAI is prohibited from doing so;
- ensure authorised personnel are bound by confidentiality and implement appropriate technical and organisational security measures;
- taking into account the nature of processing, assist Customer through appropriate technical and organisational measures with data-subject requests, and provide reasonable assistance with security, breach-notification, data-protection impact-assessment, and regulator-consultation obligations, subject to reasonable Fees where the assistance is not caused by LeadAI's breach;
- at the end of the Service, make Customer Data available for return/export during the stated export window and then delete it under the ninety (90)-day deletion process, unless applicable law requires retention; and
- make information reasonably necessary to demonstrate compliance available and permit audits as described in clause 7.
Customer gives LeadAI general written authorisation to engage Subprocessors. Where required by applicable GDPR or UK GDPR, LeadAI will provide reasonable advance notice of a new or replacement Subprocessor. Customer may object on reasonable, documented data-protection grounds, and the parties will attempt a commercially reasonable solution. If no solution is reasonably available, either party may discontinue the affected processing or feature, subject to accrued payment obligations. LeadAI will impose on each Subprocessor a written contract providing an equivalent level of protection for the relevant personal data and remains responsible for that Subprocessor to the extent required by applicable law. LeadAI may implement lawful transfer mechanisms appropriate for international transfers.
Schedule 1 – Processing Details
- Subject Matter: Provision of an AI-powered communications platform for outbound calling, call scheduling, call analytics, AI-assisted communications, and related workflows/automations and analytics, including call recording and transcription by default.
- Duration: For the Term and the ninety (90)-day default retention and deletion periods, plus any longer period required by a legal hold or non-excludable obligation.
- Nature of Processing: Collection, recording, organisation, structuring, storage, adaptation, retrieval, consultation, use, transmission, dissemination, alignment/combination, restriction, erasure, and destruction, as applicable.
- Purpose: To provide, maintain, secure, and improve the Service; route voice/SMS/email communications; generate analytics; perform recording/transcription; provide customer support; prevent abuse; comply with law; enforce the Agreement.
- Categories of Data Subjects: Contacts; End Users; Customer personnel; recipients of communications; individuals whose information appears in call recordings/transcripts, emails, or messages.
- Types of Personal Information: Names, phone numbers, email addresses, business details, communication content, timestamps, call metadata, recordings, transcripts, suppression preferences, consent records (if provided by Customer), identifiers, device and usage data, and other information uploaded or generated at Customer's direction.
5. Privacy Policy
Last Updated: 12 November 2026
SCOPE
This Privacy Policy explains how LeadAI collects, uses, stores, discloses, and otherwise handles Personal Information in connection with the LeadAI Voice AI Agent Portal, related websites, support channels, and business operations.
1. Personal Information We Collect
1.1 Information You Provide Directly
We may collect Personal Information when you interact with us, including:
- account registration and administrator setup information;
- billing and payment administration details (including tokenised payment details handled by payment processors);
- support requests, communications, and correspondence;
- recordings and transcripts of phone calls, video and virtual meetings (such as Microsoft Teams), voicemails and messages with LeadAI's team, human staff or AI staff, which are recorded by default (see Master Terms clause 7.6);
- identity verification information where required for risk, compliance, or fraud prevention; and
- preferences and settings.
1.2 Information Processed Through the Service
Depending on how a Customer uses the Service, we may process:
- Contact identifiers (names, phone numbers, email addresses, business details);
- communication content (call audio, SMS content, email content);
- call metadata (timestamps, duration, routing, disposition);
- recordings and transcripts (default ON);
- campaign configuration, scripts, prompts, templates, analytics, and outputs;
- calendar and email data from accounts a Customer connects, such as Google Calendar and Gmail (see section 7); and
- suppression preferences and opt-out indicators, where provided or generated through workflows.
1.3 Automatically Collected Information
We may collect technical and usage data, including:
- device identifiers, browser type, operating system, IP address;
- log data and event data (access times, pages viewed, feature usage);
- security telemetry and audit logs; and
- cookie and similar technology data (see Cookie Notice).
1.4 Third-Party Sources
We may collect information from Customers (for End Users and Contacts); telecom carriers, delivery providers, and infrastructure providers (e.g., delivery status, routing, anti-fraud signals); integration partners authorised by Customer; and public sources and compliance sources where required for risk checks.
2. How We Use Personal Information
2.1 Provide and Operate the Service
Including authentication, access control, communications routing, recording/transcription, analytics, and feature delivery.
2.2 Support and Customer Service
Including responding to queries, troubleshooting, and providing support communications via support@leadai.com.au.
2.3 Safety, Security, Fraud Prevention
Including monitoring for abuse, protecting recipients, protecting the Service, enforcing the AUP, and investigating suspicious activity.
2.4 Billing, Payments, and Collections
Including subscription administration, usage billing, overages, credits/top-ups, invoice management, dispute handling, and collections.
2.5 Compliance and Legal Obligations
Including responding to lawful requests, regulatory inquiries, and enforcing contractual rights.
2.6 Improve and Develop the Service
We may use anonymised, de-identified, or aggregated data to improve, test, develop, and train the Service and its models where no individual, Contact, or Customer is reasonably identifiable. We will not knowingly attempt to re-identify that data. We may process identifiable data where reasonably necessary for quality assurance, support, safety, abuse prevention, security, compliance, billing, and operation of the Service, including human review by authorised personnel subject to confidentiality obligations. This section 2.6 does not apply to Google user data, which is handled only as set out in section 7.
2.7 Marketing and Communications
Where permitted by law, we may send administrative and service-related messages, product updates, and marketing communications to Customer representatives and End Users. You may opt out of marketing communications by using provided mechanisms or contacting us.
3. Disclosures of Personal Information
Personal Information and Customer Data may be shared with, disclosed to, accessed by, or processed through third parties where reasonably necessary to provide, secure, support, bill, integrate, and improve the Service. These parties may include telecommunications and message-delivery providers, infrastructure and hosting providers, analytics providers, customer-support tooling, security and fraud-prevention providers, payment processors, professional advisers, and integration providers authorised by Customer. We may also disclose information to regulators, courts, or law enforcement where required or authorised by law, and to counterparties in a merger, financing, reorganisation, or sale subject to appropriate confidentiality and legal controls. Depending on Customer configuration and communications routing, processing outside Australia may occur in the United States, Singapore, the European Union or European Economic Area, and other jurisdictions through which communications or Customer-authorised integrations are routed. We do not authorise service providers to use identifiable Customer Data for their independent marketing purposes. Google user data is shared only as set out in section 7.4.
4. Data Retention
Unless a different period is stated in an applicable Custom Plan Document or required by law, primary Customer Data is retained for up to ninety (90) days from creation or last active processing. Following termination, Customer Data is available for export for up to thirty (30) days and will be deleted or irreversibly de-identified no later than ninety (90) days after termination. When data is removed from primary systems, backup copies are placed beyond active use and deleted or irreversibly de-identified within the same applicable ninety (90)-day period; backup rotation does not create an additional retention period. Data retained for a legal hold or non-excludable obligation will be restricted to that purpose and deleted or irreversibly de-identified when the reason ends. Google user data is also subject to section 7.5.
5. Your Choices and Rights
You may request access to Personal Information we hold about you and request correction where it is inaccurate, out of date, incomplete, irrelevant, or misleading, subject to legal exceptions. Requests may be sent to the Privacy Officer using the email or postal address in section 8. We may take reasonable steps to verify identity and authority before providing access or making a correction. If you are a Contact and a Customer controls your data in the Service, we may refer or redirect your request to that Customer where appropriate.
You may opt out of marketing communications using the mechanism provided or by contacting us. If you believe we have handled Personal Information inappropriately, you may submit a privacy complaint to the Privacy Officer describing the issue and the outcome sought. We will acknowledge and assess the complaint within a reasonable period and ordinarily aim to respond within thirty (30) days. If you are not satisfied with our response, you may contact the Office of the Australian Information Commissioner or another relevant regulator.
6. Children
The Service is not intended for use by children. Customers must not knowingly provide children's data to the Service unless lawful and approved in writing by LeadAI.
7. Google User Data
This section applies when you connect a Google account to LeadAI, through Calendar › Connect Google or Emails › Connect Google. It explains what LeadAI accesses from your Google account, why, and how you stay in control. Where this section and the rest of this Privacy Policy differ, this section applies to Google user data. Google Calendar and Gmail are covered separately below, and you can connect one without the other.
7.1 Google Calendar
What we access. The calendars and events on the Google account you connect, including event times, titles, descriptions, notes, locations and attendees, and your free and busy times.
What your AI staff do with it. Your AI staff use Google Calendar to:
- check when you're free before offering a time;
- book appointments with your customers into your calendar;
- add the appointment's details, such as the customer's name and contact details, the appointment type and notes from the call;
- reschedule or cancel appointments when a customer asks; and
- avoid double-booking.
We don't use your calendar data for anything else.
7.2 Gmail
What we access. If you connect a Gmail or Google Workspace mailbox, LeadAI can read the messages in it, create drafts, send emails from your address, and update a message's status (for example, mark it as read or add a label). We also see your name and email address.
What your AI staff do with it. Your AI staff use Gmail to:
- send emails to your customers from your own address;
- read your customers' replies and keep them on the customer's record in LeadAI; and
- draft replies for you or your AI staff to send.
We only act on emails as part of the features you set up in LeadAI. We don't use your email data for anything else.
7.3 What we never do with Google data
- We don't sell it.
- We don't use it for advertising, including personalised ads or retargeting.
- We don't use it to train or improve general artificial-intelligence or machine-learning models. The AI services that power your AI staff process it only to carry out your requests, and aren't permitted to use it to train their models.
- Our staff don't read your emails or calendar unless you ask us to (for example, for support), it's needed for security (such as investigating abuse), or the law requires it.
7.4 Who it's shared with
Only the service providers that run LeadAI's features for you (hosting, the AI services that power your AI staff, and email and calendar delivery), under contract, and only as much as each feature needs. Otherwise, only where the law requires it, or as part of a merger or sale of LeadAI, with notice to you.
7.5 How it's protected and how long we keep it
Google data is encrypted in transit and at rest, and only authorised LeadAI systems and staff can access it.
We keep it while the connection is active. When you disconnect, we delete the stored access tokens straight away. We delete the Google data copied into LeadAI within thirty (30) days, unless you ask us to keep a record or the law requires us to.
7.6 Disconnecting and deleting
- In LeadAI: Calendar or Emails › your connected account › Disconnect.
- In Google: myaccount.google.com › Security › Your connections to third-party apps & services › LeadAI › remove access.
- To have your Google data deleted, email legalteam@leadai.com.au. We'll confirm it's done within thirty (30) days.
7.7 Google's Limited Use requirements
LeadAI's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
8. Contact Us
For support questions, contact support@leadai.com.au.
For privacy requests, corrections, complaints, or legal notices, contact:
Privacy Officer
LeadAI Pty Ltd
Suite 36, Level 2, 21–31 Hall Street
Moonee Ponds Central
Moonee Ponds VIC 3039
Australia
Email: support@leadai.com.au
GENERAL SUPPORT
LEGAL & PRIVACY NOTICES
6. Cookie Notice
Last Updated: 15 July 2026
Scope
This Cookie Notice explains how LeadAI uses cookies and similar technologies in connection with our websites, web-based Service interfaces, portals, and support resources.
1. What Cookies and Similar Technologies Are
Cookies are small text files stored on your device when you visit a website or use a web-based interface. We may also use similar technologies such as local storage, pixels, tags, SDKs, and device identifiers to enable functionality, analytics, and security. Some cookies and similar technologies may be placed by third parties that provide services to us.
2. Why We Use Cookies
Strictly Necessary
To operate our websites and web interfaces, including authentication, session management, security, load balancing, and fraud prevention.
Preferences
To remember settings and preferences (such as language, interface preferences, and login-related choices) to improve user experience.
Analytics and Performance
To understand how websites and interfaces are used, diagnose issues, monitor performance, and improve reliability and usability.
Security and Integrity
To detect suspicious activity, abuse, automated traffic, and to protect accounts and the Service.
Support and Diagnostics
To enable support features, error reporting, and diagnostics to resolve incidents and improve the Service.
3. Managing Cookies
You can manage cookies through your browser settings, including blocking cookies or deleting stored cookies. Disabling cookies may affect functionality, including login, session continuity, security protections, and performance. Mobile devices may provide additional controls to manage identifiers and tracking settings, depending on operating system and device.
7. Service Credits, Metering, Billing, Overages, Refunds, Chargebacks & Collections Policy
Last Updated: 13 November 2026
Scope
This policy governs all commercial billing mechanics for the Service, including subscriptions, service credits, metering, usage charges, overages, automatic top-ups, payment authorisations, invoicing, refunds, chargebacks, collections, and related enforcement.
1. Order of Precedence; Controls; No Reliance
Subject to any express Custom Plan Document override and the paid-Term protections in this Billing Policy, Customer-specific in-app plan controls and checkout controls prevail over public pricing pages, proposals, marketing materials, or verbal statements. Promotions and discount links may exist; pricing, eligibility, and application are determined by the controlling in-app, checkout, and Custom Plan Document terms accepted for the current paid Term.
2. Pricing Structure; Fees; Taxes
2.1 Fees
Customer must pay all Fees incurred through subscription plans, add-ons, usage charges, overages, credits/top-ups, implementation fees, and any other charges displayed or incurred via in-app/checkout controls.
2.2 Taxes
Fees are exclusive of taxes. Customer is responsible for all applicable taxes, duties, levies, and governmental charges, including GST/VAT where applicable.
2.3 Currency
Unless otherwise stated in the in-app/checkout controls, charges may be billed in AUD or another currency displayed at checkout. Customer is responsible for foreign exchange and bank fees.
3. Metering and Usage Measurement
- Inbound and reception calls are billed in one-minute increments.
- Outbound calls are billed in six-second increments.
- A Connected Minute begins when a call is answered, including by voicemail. Dialling, ringing, and unanswered calls are not billed as Connected Minutes.
- SMS is billed per SMS Segment, and each segment is charged separately.
- Email is billed per message.
- AI usage may be billed per AI Conversation, token, compute unit, or other unit shown in the in-app or checkout controls.
LeadAI may change measurement methods or billing increments prospectively on thirty (30) days' notice, effective from Customer's next subscription date. LeadAI's usage records are authoritative for billing purposes except in the case of manifest error or to the extent prohibited by non-excludable law.
4. Service Credits; Top-Ups; Expiration; No Cash Value
Service Credits, including prepaid credits, bundles, top-ups, and Included Allowances, are non-refundable, non-transferable, have no cash value, and may only be used for the Service. Monthly Included Allowances renew each month, do not roll over, and expire at the end of the applicable monthly allowance period. Published Call Hours assume the entire Included Allowance is used on the stated call type; actual available hours vary when usage is divided between inbound, outbound, SMS, email, or other metered usage. LeadAI may correct balances for billing errors, fraud, abuse, chargebacks, or manifest pricing errors. If an account is inactive for six (6) consecutive months, LeadAI may close it after notice and forfeit remaining Service Credits. Extensions may be granted on request at LeadAI's discretion.
5. Overages and Automatic Charging (Enabled by Default)
If Customer exceeds Included Allowances, Customer authorises automatic charging for overages at the rate shown for its plan and/or automatic purchase of additional Service Credits or top-ups. Automatic overage charging and top-up are enabled by default unless a disablement feature is available and Customer successfully disables it. LeadAI is not liable for paused campaigns, delayed communications, or lost opportunities caused by billing controls, risk controls, exhausted credits, or payment failures.
6. Payment Authorisations; Failed Payments; Suspension
Customer must maintain valid payment details and authorises LeadAI and its payment processors to charge recurring subscription Fees, usage Fees, overages, top-ups, taxes, and other amounts owed. LeadAI may retry failed charges and require updated payment details. For ordinary non-payment, LeadAI may place the account into read-only mode and pause communications after seven (7) days and may terminate after thirty (30) days. LeadAI may act sooner for fraud, chargeback abuse, unlawful use, security risk, or repeated payment failure.
7. Invoicing; Disputes; Time Limits
Customer may receive invoices and receipts electronically. Billing cadence and format are determined by the in-app and checkout controls. Customer should notify LeadAI of a billing dispute within thirty (30) days of the charge or invoice date and provide reasonable supporting information. Failure to do so does not waive a right that cannot lawfully be waived.
8. Refunds; No Refund Policy
LeadAI does not give refunds. All Fees, including subscription Fees for the full paid Term and all onboarding, setup, implementation and build fees, are non-cancellable and non-refundable once paid or invoiced. The only exceptions are a refund that non-excludable law requires and clause 12.5 of the Master Terms (LeadAI ending the Service for its own convenience). Onboarding fees pay for work LeadAI starts as soon as Customer signs up, so they are non-refundable whether or not onboarding is finished and whether or not Customer uses the Service.
None of the following entitles Customer to a refund, credit, discount or early release from a Term:
- change of mind, or deciding after sign-up that the Service is not a fit;
- inconvenience;
- Customer or its staff not being available, or being unable to make time, for onboarding, training, setup or review meetings;
- missed, late, cancelled or rescheduled meetings or calls;
- delays of any kind, including delays in onboarding, setup or going live, and delays caused by Customer (such as late information, approvals, access, number porting or integrations) or by third parties (such as carriers, email and calendar providers, or integration providers);
- not logging in, not using the Service, or using less of it than expected;
- results such as answer rates, conversations, bookings, leads or sales not meeting Customer's expectations;
- temporary unavailability, deliverability issues, carrier filtering or ordinary performance variability;
- changes in Customer's business, staff, plans or circumstances; or
- suspension or termination of the account because of Customer's breach or non-payment.
9. Chargebacks and Reversals
A chargeback or payment reversal does not extinguish the underlying payment obligation. LeadAI may suspend paid functionality, restrict further usage, require prepayment or a deposit, and recover reasonable processor and administrative costs while a chargeback is investigated. Nothing in this policy prevents Customer from exercising a right that cannot lawfully be waived.
10. Collections; Interest; Set-Off
Overdue amounts accrue interest from the due date until paid at the lower of 1.5% per month and the maximum rate permitted by law. Customer must reimburse LeadAI for commercially reasonable collection costs, including legal fees and agency costs. LeadAI may set off an overdue and undisputed amount owed by Customer against an amount payable by LeadAI to Customer.
11. Fair Usage Limits for "Unlimited*" and Asterisked Items
11.1 Asterisked Items
Where a plan or feature is described as "Unlimited*" or includes an asterisk, it means the relevant entitlement is subject to Fair Usage Limits and other restrictions described in the Agreement. "Unlimited" does not mean unmetered, free of usage charges, or free of risk/throughput controls.
11.2 Fair Usage Limits
"Unlimited inbound reception" applies only to inbound reception for one person and unanswered calls forwarded from one mobile number. It is not available for use as a general office line, main business number, hunt group, shared reception service, bureau, agency, reseller, or shared-service offering for third parties unless LeadAI agrees in writing.
The monthly Fair Usage Limits for unlimited inbound reception are:
| Plan | Included inbound reception minutes per month |
|---|---|
| Starter | 120 minutes |
| Growth | 180 minutes |
| Scale | 240 minutes |
| Enterprise | 320 minutes |
When Customer reaches the applicable limit, LeadAI may issue an automated notice. Reception usage may continue without an automatic cut-off and will be billed at Customer's plan rate as shown in the Service.
Email fair use is approximately fifty (50) emails per day per AI staff member, consistent with normal human sending activity. The Service must not be used for bulk email or email marketing unless expressly approved. Emails above that level may be charged at AUD $0.02 per email.
LeadAI may also apply proportionate fair-use controls to prevent abnormal use, protect the Service and communications networks, and manage security or compliance risk. Controls may include additional usage Fees, required top-ups, throughput limits, or movement to an appropriate plan.
11.3 Prospective Changes and Paid-Term Protection
Plan Fees, usage rates, Fair Usage Limits, and Included Allowances are fixed for a Term already paid for unless an applicable Custom Plan Document expressly states otherwise. LeadAI may change them prospectively on thirty (30) days' notice, effective from Customer's next subscription date. Where a promotion expressly includes a price lock, both the plan Fee and usage rates are locked for the stated period. At the end of that period, the then-current published or in-app Fees and rates apply. LeadAI may withdraw an offer before acceptance.
11.4 Plan Enforcement
If use materially exceeds or falls outside the scope of the applicable plan, LeadAI may notify Customer and require a top-up, additional usage payment, configuration change, or movement to an appropriate plan. LeadAI may suspend the affected feature only where reasonably necessary to protect the Service, communications networks, or legal compliance.
12. Plan Changes and Custom Arrangements
Customer may upgrade a standard plan immediately. Unless the in-app controls state otherwise, the unused portion of the current plan Fee will be applied as a pro-rata credit against the upgraded plan. A downgrade takes effect at the end of the current paid Term. Onboarding, support packages, purpose-built agents, custom journey flows, pilots, promotional plans, and bespoke SLAs are available only on request or where offered and are governed by the applicable in-app controls, checkout controls, Order Form, or SLA. These Terms do not set a fixed onboarding or support price.
13. Automatic Renewal and Cancellation
Subscriptions renew automatically for successive Terms unless cancelled before the renewal date shown in the Service or applicable checkout controls. To avoid the charge for the next Term, Customer must complete cancellation through the available Service controls before that renewal date. If cancellation controls are unavailable, Customer may cancel by sending a request to support@leadai.com.au that is received before the renewal date.
Cancellation takes effect at the end of the current paid Term. A cancellation received after renewal takes effect at the end of the newly renewed Term and does not reverse or refund the renewal charge, except where required by non-excludable law. Stopping use, deleting an application, removing a payment method, or allowing a payment method to expire does not cancel a subscription.
14. Early Access, Vouchers and Temporary Logins
Where LeadAI gives Customer access before checkout or payment is complete ("Early Access"), billing follows clause 10.9 of the Master Terms. In short: Customer's agreement to go ahead (verbal or written, including on a call or in a video or virtual meeting) or first login binds Customer to the plan and Fees agreed or confirmed; the first Fees are normally billed within seven (7) days, and no later than fourteen (14) days, after Early Access is first given, whether or not a payment method is on file; any tax invoice issued is payable within seven (7) days of its date; and Customer may decide not to go ahead by telling LeadAI in writing, at support@leadai.com.au, before that billing date. Early Access is not a free trial unless LeadAI's written offer expressly says so.
8. Support Policy
Last Updated: 15 July 2026
Scope
This Support Policy describes support channels, operating practices, severity classifications, and response targets for the LeadAI Voice AI Agent Portal. This Support Policy does not create a service level agreement (SLA) unless LeadAI expressly agrees in writing.
1. Support Channels; Contact Methods
1.1 Primary Support Channel
Customer may contact support via email at support@leadai.com.au.
1.2 Legal and Policy Notices
Legal notices and policy-related communications must be directed to legalteam@leadai.com.au.
1.3 In-App Support
LeadAI may provide in-app messaging or ticketing. Email remains the authoritative channel unless LeadAI states otherwise.
1.4 Account Verification
LeadAI may require verification of identity and account authority before providing account-specific support, exports, configuration changes, or data disclosures.
2. Scope of Support
Included Support (General)
Support may include:
- assistance with access and account login (subject to verification);
- general guidance on configuration and available features;
- troubleshooting incidents affecting Service functionality;
- responding to questions about billing mechanics and usage records (subject to dispute limits); and
- addressing security concerns and suspected abuse.
Out of Scope
Support does not include:
- legal advice, compliance advice, or campaign vetting;
- deliverability guarantees or carrier dispute management;
- custom development, integration engineering, or workflow design beyond general guidance;
- data cleansing, list validation, consent verification, or suppression list design;
- recovery of deleted data beyond available backups (if any);
- remediation of Customer's internal systems, network issues, devices, or third-party tools; and
- forensic analysis or evidentiary services unless separately agreed.
3. Assisted Setup and Customer Acceptance
Onboarding, implementation, configuration, workflow design, custom support, and other Assisted Setup may be offered on request under the in-app controls, checkout controls, an Order Form, or an SLA. No fixed scope, Fee, response commitment, or outcome is included unless expressly stated there.
LeadAI may assist with scripts, prompts, integrations, recipient-data imports, disclosure placement, recording configuration, automations, testing, activation, and operation. Customer retains access to its account and must independently test, review, and approve the resulting configuration before public or Contact-facing use. LeadAI does not verify legal compliance, consent, list provenance, suppression status, calling times, the accuracy of Customer information, or suitability for Customer's business.
Customer's direction to publish, activate, launch, run, or continue a configuration constitutes final approval, including where LeadAI performs the technical action at Customer's request. Support activity, testing, suggestions, silence, or failure to identify an issue does not transfer Customer's compliance obligations or create a warranty that the configuration is accurate, lawful, or fit for purpose.
4. Severity Levels and Response Targets (Non-Binding)
Severity 1 – Critical
Widespread Service outage or material security incident affecting multiple customers, or complete inability for Customer to access core Service functions due to Service-side defect.
Target response: same day where practicable.
Severity 2 – High
Significant degradation of core functions with no reasonable workaround; repeated failures materially affecting communications workflows.
Target response: within 1–2 business days.
Severity 3 – Medium
Partial impairment, intermittent issues, or non-critical bugs with available workaround.
Target response: within 3–5 business days.
Severity 4 – Low
General questions, cosmetic issues, feature requests, or informational requests.
Target response: within 5–10 business days.
Response targets are non-binding and commercially reasonable only. LeadAI does not guarantee resolution times. Resolution depends on complexity, third-party dependencies, and priority. This Support Policy does not create an SLA.
9. Security & Data Handling Statement
Last Updated: 15 July 2026
Scope
This Security & Data Handling Statement summarises LeadAI's approach to security and data handling for the Service. It is informational and incorporated into the Agreement. This statement does not create additional warranties, SLAs, or representations beyond those expressly stated in the Agreement.
1. Security Principles
LeadAI maintains commercially reasonable administrative, technical, and physical safeguards designed to protect Customer Data. Controls are implemented and adjusted based on risk, operational needs, and evolving threats. Security is a shared responsibility. Customer is responsible for secure access, credential protection, administrator controls, integration security, endpoint security, and lawful use.
2. Data Location and Processing
Primary storage of Customer Data is in Australia. Limited processing may occur in other jurisdictions where reasonably necessary for telecommunications routing, delivery, infrastructure, Subprocessors, integrations, support, and operation of the Service. Customer authorises that processing and remains responsible for the legality of its instructions, notices, consents, and Customer-directed disclosures. LeadAI remains responsible for obligations imposed directly on LeadAI that cannot lawfully be transferred or excluded.
3. Access Controls and Authentication
The Service may support role-based access controls and administrative permissions. LeadAI designs access controls with least privilege principles; Customer must configure roles appropriately. Customer must secure credentials, use strong passwords, enable MFA where available, and promptly revoke access for departing users.
4. Encryption and Transmission
LeadAI uses encryption in transit and at rest where commercially reasonable and supported by underlying systems. Voice/SMS routing involves third-party carrier networks where encryption and security characteristics may vary. LeadAI does not control carrier networks and disclaims liability for carrier network security properties.
5. Monitoring, Logging, and Abuse Prevention
LeadAI may monitor systems and usage patterns to protect the Service, detect abuse, and manage risk. LeadAI may maintain logs for security, troubleshooting, billing, compliance, and operational integrity. Logs containing Customer Data follow the ninety (90)-day retention period unless a legal hold, security investigation, billing dispute, abuse investigation, or non-excludable obligation requires longer retention. De-identified operational and security metadata may be retained for longer where no individual, Contact, or Customer is reasonably identifiable. LeadAI may throttle, pause, suspend, or restrict campaigns, accounts, or features for security or abuse prevention.
6. Subprocessors and Third-Party Providers
LeadAI may share Customer Data with and permit access by third-party providers where reasonably necessary to deliver, secure, support, bill, integrate, and improve the Service, including infrastructure, hosting, telecommunications, delivery, payments, analytics, support tooling, integration, and security providers. LeadAI will use contractual confidentiality, data-protection, and security controls appropriate to the nature of the processing and may change providers and Subprocessors. LeadAI may use providers with industry certifications such as ISO 27001 or SOC 2; LeadAI does not represent that LeadAI itself holds those certifications unless expressly stated.
7. Incident Handling
LeadAI maintains internal processes designed to investigate and mitigate Security Incidents. LeadAI will notify Customer of a confirmed Security Incident affecting Customer Data where required by law and otherwise where LeadAI reasonably determines notification is appropriate. Timing and content may depend on investigation, containment, law-enforcement requirements, and applicable law. Customer must cooperate with reasonable requests to mitigate and remediate incidents, including access verification steps.
8. Data Retention, Backups, and Deletion
Primary Customer Data is retained for up to ninety (90) days unless a different period is stated in a Custom Plan Document or required by law. Following termination, Customer may request export for thirty (30) days, and Customer Data will be deleted or irreversibly de-identified no later than ninety (90) days after termination. When data is removed from primary systems, backup copies are placed beyond active use and deleted or irreversibly de-identified within the same applicable ninety (90)-day period; backup rotation does not create an additional retention period. Any data held longer for a legal hold or non-excludable obligation will be restricted to the relevant purpose and deleted or irreversibly de-identified when the reason ends.
10. Appointment Setting / Scheduling Addendum
Last Updated: 15 July 2026
Scope
This addendum applies if Customer enables or uses appointment setting, scheduling, booking, calendar integration, or related features (collectively, "Scheduling Features") within the Service.
1. Customer Responsibilities; Accuracy; Disclosures
Customer is solely responsible for:
- ensuring appointment details are accurate;
- ensuring scheduling messages comply with applicable laws and consents;
- ensuring calendar settings reflect Customer's operational reality;
- providing required disclosures to Contacts; and
- ensuring staff are available to attend scheduled appointments.
These responsibilities apply even where LeadAI assists with calendar connection, workflow setup, prompt design, availability rules, testing, or activation. Customer must test and approve time zones, appointment types, durations, buffers, locations, notifications, escalation logic, and connected calendars before launch. Directing activation constitutes Customer's final approval.
LeadAI does not guarantee booking conversions, attendance rates, contact responsiveness, or calendar acceptance. LeadAI does not verify the identity or authority of Contacts.
2. Calendar Integrations; Third-Party Systems
Scheduling Features may integrate with third-party calendar providers. Customer authorises such integration and is responsible for third-party terms, permissions, and security. Integrations may be affected by third-party outages, API changes, permission changes, or configuration errors. LeadAI is not liable for failures or inconsistencies caused by third parties. Customer is responsible for verifying time zones, locale settings, and formatting across systems.
3. No-Shows; Cancellations; Rescheduling
Customer acknowledges that no-shows are common and that reminders do not guarantee attendance. Customer is responsible for establishing and communicating cancellation/no-show policies and any fees or consequences, and for complying with consumer protection laws. Automated reminders are sent as configured by Customer. LeadAI does not guarantee delivery or receipt.
11. Enterprise Order Form Schedule Template
Last Updated: 15 July 2026
Scope
This Enterprise Order Form Schedule Template ("Order Form") may be used to document enterprise commercial terms. This template is incorporated into the Agreement if executed or otherwise accepted by LeadAI. Notwithstanding anything else, in-app plan controls and checkout controls always prevail for pricing, metering, and billing mechanics.
Key Provisions
Commercial Terms
Plan tier is as selected in-app or checkout. Any plan descriptions in this Order Form are descriptive unless the Order Form expressly identifies an override. Included Allowances, subscription Fees, add-on Fees, implementation Fees, and usage rates are as shown in the controlling in-app controls, checkout controls, or express Custom Plan Document terms and are fixed for the paid Term. Prospective changes apply on thirty (30) days' notice from the next subscription date. Overage charging and automatic top-up are enabled by default as described in the Billing Policy unless a disablement feature is available and successfully disabled by Customer. Taxes are charged as required and are Customer's responsibility.
Term and Renewal
The subscription Term is as selected in-app or checkout (monthly, quarterly, annual, or another expressly agreed period). Auto-renewal occurs under the controlling settings unless cancelled before renewal. Annual Terms are prepaid and cannot be ended early for convenience. Termination rights are governed by the Master Terms and any express override in the Order Form.
Priority of Documents; No Modification by Template
Customer-specific in-app and checkout controls prevail unless this Order Form expressly identifies and states an agreed override accepted by LeadAI. The Order Form does not otherwise modify the Master Terms or published Policy Stack. Execution is optional where Customer accepts the same terms through clickwrap or checkout.
12. Prohibited/Restricted Use Schedule and Risk Categories Schedule
Last Updated: 15 July 2026
Scope
This schedule forms part of the Agreement and applies to all use of the Service. It identifies prohibited uses and restricted uses requiring disclosure and approval. LeadAI may update categories on thirty (30) days' notice, or immediately where reasonably necessary to comply with law or address an urgent safety, security, abuse, or communications-network risk. Customer remains solely responsible for lawful use and compliance.
1. Prohibited Uses (Non-Exhaustive)
Customer must not use the Service for, in connection with, or to facilitate:
1.1 Emergency and Life-Safety
Emergency services, dispatch, crisis lines, medical emergencies, suicide prevention, or any time-critical safety communications.
1.2 Illegal Activities
Promotion, facilitation, or execution of unlawful activities, including fraud, scams, phishing, identity theft, and money laundering.
1.3 Harmful Content and Harassment
Threats, harassment, hate speech, discrimination, exploitation, stalking, doxxing, or targeted abuse.
1.4 Malware and Intrusion
Distribution of malware, ransomware, spyware, or attempts to breach systems, including credential harvesting.
1.5 Deceptive Impersonation
Impersonation of government, banks, utilities, or other entities in a deceptive manner, or misleading representations about identity, authority, or purpose.
1.6 Unlawful Telemarketing/Spam
Bulk outreach without valid consent and lawful bases, failure to honour opt-outs, or deliberate evasion of DNC/DND rules.
1.7 Unapproved Sensitive Data Processing
Processing sensitive categories of data (health, biometrics, payment card data, government identifiers) unless explicitly approved by LeadAI in writing.
1.8 Child-Directed or Exploitative Campaigns
Campaigns targeting children or vulnerable persons without lawful basis and LeadAI's written approval.
1.9 Regulated Illegal Substances
Promotion or sale of illegal drugs or controlled substances where unlawful.
1.10 Circumvention
Bypassing compliance, risk controls, identity verification, or carrier rules, including rotating identities to evade suppression.
2. Restricted Uses (Disclosure and LeadAI Approval Required)
Customer must disclose and obtain written approval prior to using the Service in connection with:
- financial services outreach involving credit, lending, debt relief, investment advice, insurance solicitations, or collections;
- healthcare communications involving patient outreach, diagnostics, treatment, or regulated health advice;
- legal services solicitation or regulated legal marketing;
- gambling or wagering promotions (where lawful);
- political campaigning, advocacy, or issue-based mass outreach;
- adult-oriented content or services (where lawful);
- high-volume debt collection or repossession outreach;
- multi-level marketing or pyramid-adjacent outreach;
- real estate lead generation at scale involving recorded calls and automated follow-ups;
- recruitment outreach at scale involving automated screening.
LeadAI may condition approval on documentation, scripts, consent proof, suppression handling, volume limits, number reputation controls, additional fees, deposits, or additional contractual terms. Absence of enforcement is not approval. LeadAI may suspend or terminate access immediately for prohibited uses or use of restricted categories without approval. No refunds or credits are provided for enforcement actions, except where required by non-excludable law.
13. AU Compliance Schedule (Non-Exhaustive)
Last Updated: 15 July 2026
Scope
This schedule provides a non-exhaustive list of Australia-specific compliance considerations for voice, SMS, email, recording/transcription, privacy, and consumer/telemarketing rules. This schedule is informational only and does not constitute legal advice. Customer bears sole responsibility for compliance.
1. Spam Act 2003 (Cth) – Electronic Messages (SMS and Email)
Customer must ensure it has valid consent (express or inferred, as lawfully applicable) before sending commercial electronic messages. Customer must ensure messages clearly and accurately identify the sender and include required contact information. Customer must include a functional unsubscribe facility and honour unsubscribe requests within the legally required period. Customer must not use address-harvested lists or lists obtained through unlawful means. Customer remains responsible where LeadAI or another provider technically sends messages on Customer's behalf.
2. Do Not Call Register Act 2006 (Cth) – Telemarketing Calls
Customer must check or "wash" calling lists against the Do Not Call Register and any applicable industry registers as required and maintain proof of compliance. Customer is responsible for determining whether calls are telemarketing or otherwise regulated and for complying with calling-time restrictions, industry standards, identification and disclosure requirements, internal do-not-call lists, consent withdrawals, and lawful calling line identification. Customer remains responsible where LeadAI, the Service, or another provider technically facilitates or makes a call on Customer's instructions. Nothing in this allocation limits an obligation imposed directly on LeadAI that cannot lawfully be transferred or excluded.
3. Privacy Act 1988 (Cth) and APPs
Customer is responsible for compliance with APP obligations applicable to Customer, including collection notices, use and disclosure limitations, cross-border disclosure, and complaint handling. Customer must provide required privacy notices and collection statements to Contacts as required. Customer must ensure Contact data is used and disclosed only as permitted by law and within the scope of consents and lawful purposes. Customer is responsible for cross-border disclosure compliance where Customer directs data to be processed overseas, including through telecom routing and delivery providers.
4. State/Territory Surveillance Devices and Call Recording Laws
The Service records calls by default and transcribes by default. Customer must ensure compliance with all applicable surveillance and recording laws in every relevant state and territory. Requirements differ between jurisdictions and may depend on the location of each participant, how the recording is made, and how it is later used or disclosed. Customer must implement disclosures and obtain all required consents before recording, handle refusal lawfully, and ensure recordings and transcripts are stored, accessed, used, and disclosed only within the scope of applicable law, notice, and consent.
5. Consumer Protection and Misleading Conduct
Customer must ensure communications are not misleading or deceptive and comply with consumer protection obligations under the Australian Consumer Law. Customer must avoid harassment, coercion, undue pressure, or unconscionable conduct. Customer should maintain accurate records of representations made during calls or in messages. Customer must comply with relevant ACMA guidance and industry standards applicable to telemarketing and spam compliance.
6. Official Australian Compliance Resources
The following official resources are provided for convenience only and are not exhaustive or legal advice. Customer must check the current requirements applicable to its activities:
- ACMA — Avoid sending spam
- Do Not Call Register — Using the Register
- Do Not Call Register — Telemarketing industry standards
- OAIC — Australian Privacy Principles
- OAIC — APP 7 direct marketing guidance
- OAIC — APP 8 cross-border disclosure guidance
- ACCC — Contracts and unfair contract terms
- Australian Law Reform Commission — State and territory surveillance-device laws
14. US Compliance Schedule (Non-Exhaustive)
Last Updated: 15 July 2026
Scope
This schedule provides a non-exhaustive list of U.S.-specific compliance considerations for voice, SMS, email, telemarketing, recording consent, and related rules. This schedule is informational only and does not constitute legal advice. Customer bears sole responsibility for compliance.
1. TCPA (Telephone Consumer Protection Act) and FCC Rules
Customer must determine whether its use of the Service constitutes use of an automatic telephone dialing system (ATDS), artificial voice, AI-generated voice, or prerecorded voice, and obtain any required prior express consent or prior express written consent. The FCC has confirmed that AI-generated voices fall within the TCPA's artificial or prerecorded voice restrictions. Customer must ensure consent standards meet applicable requirements for calls and texts, including disclosures at the point of consent and recordkeeping. Customer must honour consent revocation requests in a timely manner, comply with applicable federal and state quiet hours, and ensure calls and messages identify the sender and use of AI where required.
2. TSR (Telemarketing Sales Rule) and State Telemarketing Laws
Customer must determine whether its outreach is telemarketing and comply with all applicable TSR requirements. Customer must provide required disclosures at the start of telemarketing calls and comply with any script and recordkeeping requirements. Customer is responsible for determining and complying with any state telemarketing licensing, bonding, registration, or reporting requirements. Customer must maintain internal do-not-call lists and honour opt-outs promptly.
3. DNC Obligations (Federal and State)
Customer must comply with the National Do Not Call Registry rules, including scrubbing, recordkeeping, and operational processes. Customer must comply with any additional state-specific DNC requirements. Where Customer relies on any safe harbor provisions, Customer must implement all required policies, training, and recordkeeping.
4. CAN-SPAM (Email)
Customer must ensure email headers and subject lines are not misleading. Customer must include required identification and any required physical address or valid contact mechanism as mandated by CAN-SPAM and applicable state laws. Customer must provide a functioning unsubscribe mechanism and honour opt-outs within required timeframes. If Customer sends on behalf of others, Customer is responsible for allocating compliance and ensuring lawful sending practices.
5. State Recording and Two-Party Consent Laws
Calls are recorded by default and transcribed by default. Customer must comply with all applicable state recording laws, including two-party/all-party consent requirements where applicable. Customer must implement scripts and workflows to obtain legally required consent prior to recording. Customer must implement lawful handling where a Contact refuses recording, including termination or alternative processes if legally required and approved by LeadAI.
6. Consumer Protection and Carrier Rules
Customer must comply with unfair/deceptive acts and practices laws and must not misrepresent identity, affiliation, pricing, or terms. If Customer engages in collections, lending, debt relief, or financial solicitations, Customer must comply with all applicable federal and state rules. Customer acknowledges carriers may filter, block, or throttle messages and calls based on content, volume, reputation, and policy. Customer is responsible for any required A2P messaging registrations, brand/campaign registrations, or other carrier program requirements.
7. Official United States Compliance Resources
The following official resources are provided for convenience only and are not exhaustive or legal advice:
- FCC — TCPA application to AI-generated voices
- FCC — Stop unwanted robocalls and texts
- FTC — Complying with the Telemarketing Sales Rule
- FTC — National Do Not Call compliance questions
- FTC — CAN-SPAM compliance guide
15. Recording & Transcription Schedule
Last Updated: 15 July 2026
Scope
This schedule governs call recording and transcription in the Service, including defaults, Customer responsibilities, consents, retention, access, alternative-workflow requests, and legal risk allocation. This schedule is incorporated into the Agreement.
1. Defaults and Operational Requirements
1.1 Recording Default ON
Call recording is enabled by default as part of the Service workflow.
1.2 Transcription Default ON and Required
Transcription is enabled by default and is required for agent operation, analytics, quality controls, and related features.
1.3 Workflow Coupling
Customer acknowledges that disabling recording and/or transcription may reduce functionality, disable features, and impact analytics accuracy and operational workflows.
1.4 No Guarantee of Accuracy
Transcriptions may be inaccurate, incomplete, or delayed. Customer must not rely on transcriptions as a verbatim legal record.
2. Customer Compliance Responsibilities (Primary Allocation)
2.1 Notice and Consent
Customer bears full responsibility to provide all required notices and obtain all consents required by law for call recording, transcription, monitoring, storage, and use of recordings/transcripts.
2.2 Jurisdictional Variability
Customer is responsible for determining applicable consent requirements in every jurisdiction relevant to the call, including where parties are located in different jurisdictions.
2.3 Scripts and Disclosures
Customer must ensure scripts and call flows:
- disclose recording and transcription in a clear and prominent manner;
- obtain legally required consent prior to recording where required;
- identify Customer and purpose as required by law; and
- address refusal to consent, including safe termination logic and suppression list updates as required.
2.4 Consent Evidence
Customer must maintain records evidencing consent and disclosure where required and must be able to produce such records. LeadAI does not determine which laws apply to Customer calls and does not ensure Customer has obtained consent.
2.5 Assisted Setup and Final Approval
If LeadAI assists with recording notices, scripts, prompts, consent logic, alternative workflows, configuration, testing, or activation, Customer must independently review the complete implementation against every jurisdiction applicable to the call. Customer's direction to activate, publish, run, or continue the workflow constitutes final approval. LeadAI's assistance does not constitute legal advice or an assurance that notice or consent is sufficient.
3. Access Controls and Internal Handling
Customer must restrict access to recordings and transcripts to authorised End Users with a legitimate need. Customer must implement least privilege, remove access for departed End Users, and manage administrator privileges carefully. Customer is responsible for lawful export, sharing, and downstream handling of recordings/transcripts, including compliance with privacy and confidentiality obligations. Customer must avoid collecting sensitive information via recorded calls unless legally permitted and approved by LeadAI where required.
4. Retention and Deletion
Recordings and transcripts are Customer Data and follow the default ninety (90)-day retention policy unless a different period is stated in an applicable Custom Plan Document or required by law. Following termination, they remain available for export for up to thirty (30) days and will be deleted or irreversibly de-identified no later than ninety (90) days after termination. When removed from primary systems, backup copies are placed beyond active use and deleted or irreversibly de-identified within the same applicable ninety (90)-day period; backup rotation does not create an additional retention period. A legal hold or non-excludable obligation may require longer restricted retention.
5. Opt-Out and Alternative Workflows
5.1 Opt-Out by Request Only
Disabling recording and/or transcription is available only by request and subject to LeadAI approval.
5.2 Custom Scope and Fees
Alternative workflows may require engineering, configuration, compliance controls, or a different operational design. Availability, scope, Fees, and other terms apply only where stated in the in-app controls, checkout controls, Order Form, or SLA. No fixed alternative-workflow Fee is created by this schedule.
5.3 Refusal
LeadAI may refuse opt-out requests where disabling would materially impact Service integrity, security, supportability, or lawful operation.
6. Legal Risk Allocation; Indemnity
6.1 Customer Assumes Risk
To the maximum extent permitted by law, Customer assumes the risk of claims arising from Customer's recording/transcription choices, instructions, scripts, disclosures, consent handling, access, use, or failure to review and supervise, including regulatory investigations, civil claims, evidentiary disputes, and consent disputes.
6.2 Indemnity Applies
Customer's indemnity obligations apply to any claims arising from recording/transcription, including failure to obtain consent, inadequate notice, unlawful monitoring, or unlawful use of recordings/transcripts. LeadAI is not responsible for script content, disclosure placement, or Customer compliance logic.
16. Definitions Schedule
Last Updated: 12 November 2026
Scope
This Definitions Schedule supplements and clarifies defined terms used across the Agreement and Policy Stack. If a term is defined in the Master Terms, that definition governs unless expressly stated otherwise.
Core Defined Terms
"Agreement"
The Master Terms together with all incorporated policies, schedules, addenda, in-app plan controls and account settings, checkout controls, and any Order Form accepted by LeadAI.
"Applicable Data Protection Laws"
Privacy, data-protection, and data-security laws that apply to processing under the Agreement, including the Privacy Act 1988 (Cth), the Australian Privacy Principles, GDPR, and UK GDPR, in each case only to the extent applicable to the relevant processing.
"AUP"
The Acceptable Use Policy, as updated by LeadAI from time to time.
"Charges"
Includes all Fees, usage charges, overages, credits/top-ups, taxes, and any other amounts payable under the Agreement.
"AI Conversation"
A billable unit of AI interaction or processing measured according to the in-app or checkout controls applicable to Customer's plan.
"AI Staff"
LeadAI's AI staff members, personas, characters and avatars, including Emily (Emily Swift), Anna, Carol, Jenny, Emma and Sam, and any others LeadAI creates or uses now or in future, with all their elements described in clause 9.4 of the Master Terms.
"Assisted Setup"
Technical or administrative assistance provided by LeadAI at Customer's request, including onboarding, configuration, scripts, prompts, templates, integrations, workflows, testing, publication, activation, or operation of the Service.
"Call Hours"
The indicative call duration published for a plan based on allocating the full relevant Included Allowance to a single call type. Actual Call Hours vary according to the mix of metered usage.
"Checkout Controls"
The pricing, plan, billing, payment authorisations, and acceptance controls presented in any checkout flow used to purchase or renew the Service, including controls provided through a third-party payment processor.
"Connected Minute"
Call time beginning when a call is answered, including by voicemail. Dialling, ringing, and unanswered calls are not Connected Minutes.
"Contacts"
Any individual whose information, identifiers, or communication details are processed through the Service in connection with Customer's use, including call recipients, SMS recipients, email recipients, leads, customers, prospects, and other data subjects, whether or not they are End Users.
"Customer Data"
All data, content, records, contact lists, scripts, messages, templates, prompts, call lists, suppression lists, recordings, transcripts, campaign configuration, metadata, and other materials submitted to, generated within, transmitted through, or otherwise processed via the Service by or on behalf of Customer (including by End Users), including Personal Information of Contacts.
"Custom Plan Document"
An Order Form, SLA, promotional plan term, pilot term, or other custom plan document expressly accepted by LeadAI in writing or through checkout that identifies any agreed variation to the standard Terms.
"De-Identified Data"
Data that has been anonymised, de-identified, or aggregated so that no individual, Contact, or Customer is reasonably identifiable.
"Early Access"
Access to the Service that LeadAI gives Customer before checkout or payment is complete, including through a voucher or voucher code supplied by a member of LeadAI's team, a temporary or early-access login, or an account set up after Customer agrees to go ahead verbally (including on a call or in a meeting) or in writing. Early Access is billed under clause 10.9 of the Master Terms.
"End Users"
Any individual who accesses or uses the Service under Customer's account, including employees, contractors, agents, and authorised users, and any person Customer permits to interact with workflows, dashboards, recordings, transcripts, analytics, or outputs.
"Fees"
All amounts payable for the Service as determined by in-app plan controls and checkout controls, including subscription fees, add-ons, usage charges, overages, credits/top-ups, and implementation fees.
"In-App Plan Controls"
The plan selection, allowances, metering configuration, billing cadence, credit/top-up settings, feature toggles, and account settings configured and displayed within the Service that govern Customer's entitlements and Charges.
"Included Allowance"
A monthly plan entitlement for specified usage. Unless expressly stated otherwise, an Included Allowance renews monthly, does not roll over, expires at the end of the applicable monthly allowance period, is non-transferable, and has no cash value.
"LeadAI Brand Assets"
The LeadAI name, logos, trade marks (registered or not), trade dress, business and domain names, social media pages and accounts, slogans, the look and feel of LeadAI's app, websites, videos and materials, and the goodwill in them (clause 9.4 of the Master Terms).
"Outputs"
Any results, analytics, insights, summaries, classifications, recommendations, or generated content produced by the Service, including AI-assisted outputs, whether displayed, delivered, or exported.
"Personal Information"
Has the meaning given under applicable privacy laws, including the Privacy Act 1988 (Cth), and includes information about an identified individual or an individual who is reasonably identifiable.
"Policy Stack"
The Master Terms and all incorporated policies, schedules, addenda, and statements listed or referenced in the Agreement.
"Protected Materials"
AI Staff, LeadAI Brand Assets and the materials listed in clause 9.5 of the Master Terms, including prompts, system prompts, scripts, scripting rules, call flows, workflows, configurations, code and know-how, and any unique combination of them (clause 9.6).
"Protected Materials Breach"
Any of the conduct prohibited by clause 9.7 of the Master Terms.
"Security Incident"
An actual or reasonably suspected unauthorised access to, acquisition of, or disclosure of Customer Data within LeadAI's control, excluding unsuccessful attempts or activities that do not compromise the security of Customer Data (such as pings, port scans, or denial-of-service attempts).
"Service"
The "LeadAI Voice AI Agent Portal" and any related features, modules, tools, APIs, integrations, updates, support, credits, and services introduced from time to time, including voice calls, SMS, email, workflows/automations, analytics, recording, and transcription.
"Service Credits"
Prepaid credits, bundles, top-ups, or similar units purchased or granted for consumption of usage-based elements of the Service, which are non-refundable and have no cash value.
"SMS Segment"
A billing unit for SMS. A standard GSM-7 message contains up to 160 characters, or 153 characters per segment when concatenated. A Unicode/UCS-2 message, including a message containing many emoji or special characters, contains up to 70 characters, or 67 characters per segment when concatenated. Each segment is billed separately.
"Subprocessor"
Any third party engaged by LeadAI to process Customer Data to provide the Service, including telecom routing, delivery providers, infrastructure providers, analytics, support tooling, and security services.
"Suppression List"
Any list or system rule identifying Contacts who must not be contacted, including DNC/DND lists, unsubscribe lists, revocation lists, complaint-driven suppression, and internal policy-based suppression.
"Fair Usage Limit"
A usage scope or threshold stated in the Billing Policy or applicable plan controls for an entitlement described as unlimited, asterisked, included, or subject to fair use.
"Term"
The duration of the Agreement as described in the Master Terms.
Interpretation Rules
"Including" means "including without limitation". Words in singular include plural and vice versa. References to "law" include statutes, regulations, rules, codes, guidance, and binding orders. Headings are for convenience only and do not affect interpretation. Where a term is defined in multiple documents, the Master Terms definition governs unless expressly stated otherwise for a specific document.
Policy Coverage Index
The following topics are addressed across the Master Terms and published Policy Stack:
- AI Output and Reliance Rules
- Telecommunications, Deliverability, and Carrier Policy Disclaimers
- Customer Compliance Evidence; Verification; Cooperation
- Exports, Migration, and Transition Assistance
- Beta, Preview, and Experimental Features
- Notices Standard; Electronic Notices
- Sanctions, Export Controls, and Restricted Use
- Third-Party Services, Integrations, and Customer-Configured Providers
- Legal Process, Data Requests, and Disclosure Handling
- Service Changes, Deprecation, and Operational Discretion
- Additional Customer Security and Operational Requirements
- Policy Stack Index
- Publicity, References, and Feedback Licence
- Data Retention and Backup Clarifications
- Suppression, Opt-Out, and Contact Preference Handling
- Consent, List Provenance, and Right-to-Contact Representations
- Recording/Transcription Notice Language Principles
- Anti-Abuse, Integrity Monitoring, and Platform Protection
- Data Rights, Usage Data, and De-Identified Improvement Use
- Communications Content Standards
This index is descriptive only and does not incorporate any unpublished document. Only the terms actually published on the Terms page or expressly accepted in a Custom Plan Document form part of the Agreement. The Agreement is governed by the laws of Victoria, Australia. If any provision is held invalid or unenforceable, it will be severed or modified to the minimum extent necessary and the remaining provisions will remain in effect.
General Support & Privacy: support@leadai.com.au
Formal Legal Notices: legalteam@leadai.com.au
© LeadAI Pty Ltd (ABN 83 679 856 305; ACN 664 941 253) · Victoria, Australia · Governing Law: Victoria, Australia · Last Updated: 13 November 2026
LeadAI Pty Ltd, Melbourne, VIC, Australia. Questions about this page: support@leadai.com.au.