Effective 21 August 2026 Last updated 21 August 2026 Version 2026-08-21
Terms of Service
These Terms govern access to atpai.io and ATPAI LLC's AI receptionist, telephony, messaging, automation, client-dashboard, and related business services. They are written for business use in the United States.
01Acceptance and eligibility
These Terms of Service (the Terms) are a legal agreement between ATPAI LLC, a Delaware limited liability company (ATPAI, we, us, or our), and the person or entity accessing the website or Service (you or Client). The Service is offered to businesses and their authorized personnel, not for personal, family, or household use.
You accept these Terms by signing or accepting a document that incorporates them, creating or using an account, authorizing payment, paying an invoice or checkout page that references them, or using the Service after receiving them. If you use the Service for an entity, you represent that you have legal authority to bind that entity. If you lack authority, you may not accept or use the Service for it.
You must be at least 18 years old and legally capable of entering a contract. Electronic signatures, checkbox acceptance, payment records, account logs, and other electronic records may evidence acceptance and have the same legal effect as paper records to the maximum extent permitted by law.
02Service and order of precedence
The Service includes the website and the AI receptionist, telephony, call handling, routing, recording, transcription, summarization, messaging, appointment or lead capture, automation, client dashboard, reporting, implementation, support, and related services identified in the applicable ordering document. Features vary by package, configuration, provider availability, approval status, and client readiness. A demo, prototype, roadmap item, sales statement, or website description is not a commitment to deliver a feature unless it appears in a controlling written agreement.
The order of precedence for conflicting terms is: (1) a signed amendment or addendum that expressly addresses the conflict; (2) a signed Service Agreement, Order Form, or statement of work; (3) a signed data processing addendum for the personal data it covers; (4) these Terms; and (5) an invoice, checkout page, documentation, onboarding material, proposal, email, message, demo, or sales material. A higher-priority document controls only the conflict. Verbal statements do not modify the agreement.
ATPAI may update operational documentation, safety controls, support channels, vendors, models, workflows, and non-material configurations as reasonably necessary to operate, secure, or improve the Service. Material scope or commercial changes require the process stated in the controlling agreement or these Terms.
03Accounts and security
Client is responsible for all users, permissions, instructions, and activity under its organization. Client must provide accurate registration and billing information; limit access to authorized personnel; use unique, strong credentials; enable multi-factor authentication where available; promptly remove former personnel; and notify ATPAI of suspected unauthorized access.
Credentials, API keys, magic links, session tokens, and administrative access may not be shared except with authorized users who need access. Client is responsible for securing its devices, networks, inboxes, phone systems, accounts, integrations, and vendor credentials. ATPAI may suspend a user, integration, or account that appears compromised, unauthorized, abusive, or unsafe.
04Client information and responsibilities
Client must:
- provide complete, accurate, authorized, and current business information, including services, hours, pricing, policies, service areas, availability, staff and escalation contacts, scripts, offers, booking rules, and integration instructions;
- review and approve the knowledge base, scripts, voice presentation, recording and AI notices, routing, workflows, integrations, offers, customer-facing messages, and launch settings;
- promptly notify ATPAI of operational changes and correct inaccurate or outdated information;
- maintain all licenses, insurance, notices, consents, permissions, and legal bases required for Client’s business and use of the Service;
- maintain staff coverage, emergency procedures, alternate contact methods, and systems needed to receive transfers, alerts, leads, appointments, and requests; and
- remain responsible for pricing, estimates, fulfillment, service quality, safety, scheduling, hiring, refunds, taxes, customer disputes, and all other business decisions and operations.
ATPAI may rely on Client’s information and instructions. Client is responsible for harm, disputes, refunds, or missed opportunities caused by inaccurate, incomplete, unlawful, outdated, or unauthorized Client materials or instructions.
05AI limitations and human review
The Service uses probabilistic AI, speech recognition, text-to-speech, and automation. AI may hallucinate, mishear, mistranscribe, misclassify, omit information, fail to recognize context, produce an unsuitable response, or perform differently across accents, languages, noise conditions, topics, and providers. Transcripts, summaries, classifications, recommendations, and other AI Output are aids, not guaranteed records of what occurred.
Client must apply appropriate human reviewbefore relying on AI Output for material pricing, appointments, dispatch, purchases, refunds, commitments, public statements, legal compliance, safety, or customer outcomes. Unless a controlling agreement expressly states otherwise, captured orders, appointments, quotes, leads, and requests remain subject to Client confirmation. ATPAI does not guarantee that every call will be answered, understood, transferred, converted, booked, or completed.
Client may not represent AI Output as professional advice, an official record, or a guaranteed decision. Evidence logs, recordings, transcripts, and audit trails are operational records only; ATPAI does not guarantee they satisfy a particular legal, evidentiary, regulatory, or recordkeeping requirement.
06Emergency, high-risk, and regulated use
The Service is not a 911 service, emergency dispatch system, crisis hotline, medical triage system, public safety system, or guaranteed urgent-response channel. Client must maintain direct emergency instructions, staffed escalation paths, and alternative communications. Client may not rely on the Service to prevent death, injury, property damage, or other imminent harm.
Unless ATPAI approves a signed addendum, Client may not use the Service for protected health information or HIPAA-regulated workflows; legal, medical, tax, financial, or investment advice; payment-card processing; biometric identification; employment, credit, housing, insurance, education, or benefits eligibility decisions; government services; children’s services directed to children under 13; or another high-riskor regulated decision with legal or similarly significant effects.
Client must notify ATPAI before introducing sensitive or regulated data. ATPAI may refuse, restrict, require additional safeguards for, or terminate a proposed use that creates unreasonable legal, security, safety, vendor, or reputational risk.
07Recording, transcription, and AI disclosure
The Service may record, monitor, transcribe, summarize, and analyze calls and communications. Laws governing call recording, monitoring, wiretapping, transcription, employee notice, consent, and AI disclosure vary by jurisdiction and circumstance. A standard announcement or a caller’s continued participation may not satisfy every legal requirement.
Client is responsible for identifying every jurisdiction relevant to its callers, employees, operations, advertising, routing, and service area; obtaining legal advice where needed; approving required disclosures; providing alternate channels where required; and maintaining consent and notice records. Client may not disable, obscure, or bypass a required recording or AI notice. ATPAI remains responsible for obligations that applicable law imposes directly on ATPAI and may require a more protective notice or workflow.
Client must tell ATPAI before routing calls from a jurisdiction, workforce, or use case that requires special handling. ATPAI may change, pause, or reject a call flow that lacks adequate disclosure, consent, or documentation.
08Communications compliance
The default Core scope is inbound call handling. A callback, appointment reminder, owner alert, review request, reactivation message, SMS, email, upsell, transfer, or campaign is a separate communication flow. No outbound flow is approved merely because a recipient previously called or because another channel or purpose was approved. Outbound functionality may be used only when included in the controlling Order Form and separately approved in writing for launch.
Client is responsible for ensuring that every communication it requests or approves complies with applicable law and platform rules, including the Telephone Consumer Protection Act (TCPA), the Telemarketing Sales Rule, National and state Do Not Call requirements, CAN-SPAM Act, state mini-TCPA and telemarketing laws, consumer-protection laws, and carrier or industry rules. Contractual allocation does not eliminate obligations that law imposes directly on ATPAI, a provider, a seller, a telemarketer, or another participant.
Before an outbound communication is launched, Client must:
- identify the responsible seller or sender, recipient, number or address, channel, purpose, content category, list source, and every relevant jurisdiction;
- provide and maintain proof of opt-in, prior express consent, or prior express written consent when required, including the scope, timestamp, disclosure version, signature or other acceptance evidence, and a clear statement that telemarketing consent is not a condition of purchase where required;
- not initiate an automated call using an artificial or prerecorded voice, including an AI-generated voice, unless the approved workflow establishes the applicable consent or exemption; advertising or telemarketing calls require prior express written consent when federal law requires it;
- screen against applicable National, state, seller-specific, and internal Do Not Call or suppression lists; where the federal National Registry applies, use data obtained no more than 31 daysbefore the solicitation;
- check for reassigned telephone numbers through the FCC Reassigned Numbers Database or another counsel-approved process before relying on historical telephone consent;
- resolve the recipient’s local time and observe the federal 8:00 a.m. to 9:00 p.m. window for covered residential solicitations and any stricter state, carrier, or contractual limit;
- use accurate sender and caller identification, non-deceptive content, required disclosures, and usable callback, unsubscribe, or automated opt-out methods;
- for commercial email, use accurate headers and subject lines, include any required advertisement identification and a valid physical postal address, keep the Internet-based opt-out available for at least 30 days, and honor the request within 10 business days;
- accept STOP, QUIT, END, REVOKE, OPT OUT, CANCEL, UNSUBSCRIBE, Do Not Call, and any other language a reasonable person would understand as revocation; promptly propagate the request across ATPAI, Client, CRM, carrier, and vendor systems within the shortest applicable deadline; and
- preserve consent, disclosure, call-detail, script, campaign, opt-out, and suppression evidence for the period required by law. Where the Telemarketing Sales Rule applies, covered records may need to be maintained for five years.
Client must not use purchased, scraped, appended, or third-party lists unless ATPAI approves the source in writing and Client documents legally sufficient consent for the exact sender, recipient, channel, purpose, and content. ATPAI may require consent evidence, suppress recipients, throttle volume, revise content, delay launch, or refuse a communication that appears unlawful, deceptive, abusive, unsupported, or likely to create deliverability, carrier, vendor, litigation, or reputational risk. ATPAI does not guarantee message delivery, caller identification, carrier acceptance, or legal compliance.
09Acceptable use
Client and its users may not use or instruct the Service to:
- violate law, regulation, court order, platform policy, contract, or third-party rights;
- deceive, impersonate unlawfully, conceal required AI use, misrepresent identity, or make false or unsupported claims;
- send spam, harass, threaten, discriminate, exploit, manipulate reviews, create fake urgency, or target vulnerable persons unfairly;
- collect, infer, disclose, or use personal or sensitive data without required authority, notice, consent, and safeguards;
- facilitate fraud, malware, phishing, credential theft, unauthorized surveillance, security attacks, or evasion of carrier or platform controls;
- reverse engineer, probe, scrape, overload, disrupt, benchmark for a competitor, or bypass access, usage, safety, or rate limits;
- extract prompts, hidden instructions, credentials, source code, non-public workflows, or other Provider Materials; or
- resell, sublicense, white-label, or provide the Service to another business, location, or brand outside the approved scope.
ATPAI may investigate suspected misuse and preserve or disclose related records where reasonably necessary to secure the Service, enforce agreements, protect persons or systems, or comply with law.
10Third-party platforms and service changes
The Service depends on third-party platforms, including carriers, telephone numbers, communications tools, AI and speech providers, hosting, databases, authentication, automation, calendars, dashboards, payment processors, email, and APIs. Their terms, privacy practices, limits, approvals, fees, models, security, and availability may apply and may change.
Client must maintain any client-owned account, number, domain, integration, permission, payment method, campaign registration, and vendor approval needed for the Service. Client authorizes ATPAI and approved subcontractors to access and act in client-approved accounts as reasonably necessary to configure, operate, secure, troubleshoot, and support the Service.
ATPAI may replace or reconfigure third-party platforms when commercially reasonable. ATPAI is not responsible for third-party outages, filtering, suspensions, policy changes, model changes, API restrictions, deliverability, data loss, price increases, or security incidents outside ATPAI’s reasonable control. If a vendor becomes unavailable, restricted, or materially more expensive, ATPAI may modify the affected workflow, pass through approved costs, require a package change, suspend the feature, or terminate the affected Service as provided below.
11Fees and billing
Fees, package, included scope, payment timing, and approved pass-through costs are stated in the controlling Order Form or Service Agreement. Unless that document states otherwise, the Core — AI Receptionist + Client Dashboard package has a $1,500 setup fee due at signing and a $750 monthly subscriptionbilled in advance, with the first monthly payment due at signing. The setup fee is non-refundable after ATPAI begins discovery, onboarding, configuration, vendor setup, planning, or other fulfillment work.
Client authorizes ATPAI and its payment processors to charge the approved payment method for fees, subscriptions, approved changes, pass-through costs, taxes, and other amounts due. Fees are in U.S. dollars and exclude sales, use, telecom, excise, withholding, and similar taxes, except taxes on ATPAI’s net income. Client must keep a valid payment method and accurate billing details on file.
Client must dispute an invoice or charge in writing within 10 days after it is issued or posted, unless law requires a longer period, and must first allow a reasonable opportunity to resolve the issue before initiating a chargeback. Overdue amounts may accrue interest at 1.5% per month or the maximum lawful rate, whichever is lower. Client is responsible for reasonable collection, chargeback, and enforcement costs to the extent permitted by law.
Standard usage applies to the business, location, agents, numbers, and workflows in the Order Form. Additional locations, numbers, agents, campaigns, integrations, unusually high vendor costs, storage, custom development, paid media, or out-of-scope work require written approval and may require a change order, pass-through payment, or package upgrade.
12Term, renewal, and termination
Unless a controlling Order Form states otherwise, the Service begins on its effective date and has a 12-month initial term. Client may not cancel for convenience during the initial term, and an attempted early cancellation does not eliminate fees owed for that term. After the initial term, the Service automatically renews month-to-month until either party gives at least 30 days’ written notice of non-renewal. Cancellation takes effect at the end of the applicable paid period after the required notice. Fees already paid are non-refundable except as required by law or agreed in writing.
Either party may terminate for a material breach not cured within 15 days after written notice. ATPAI may suspend or terminate immediately when reasonably necessary because of non-payment or chargeback; unlawful, deceptive, abusive, or unsafe use; missing consent; security compromise; vendor or carrier risk; threat to persons, systems, deliverability, or reputation; violation of these Terms or platform rules; or a request that exposes ATPAI to unreasonable legal or financial risk.
ATPAI may terminate or materially modify an affected Service if a necessary third-party platform becomes unavailable, prohibited, or commercially unreasonable and ATPAI cannot provide a reasonable substitute. When practicable, ATPAI will give notice and a transition opportunity.
On termination, Client must pay outstanding amounts; stop using the Service; replace or remove routing, numbers, integrations, and credentials as needed; and request any standard export within the period below. Provisions that by their nature should survive—including payment, confidentiality, intellectual property, data retention, disclaimers, indemnification, limitations, disputes, and general terms—will survive.
13Data, privacy, export, and deletion
As between the parties, Client owns Client Data and Customer Data, including authorized recordings, transcripts, messages, contact information, and job or appointment records, subject to ATPAI’s rights to process them to provide, secure, support, improve, document, bill, and defend the Service. Client is generally the controller or business for its callers, customers, prospects, and personnel, and ATPAI is generally its processor or service provider. The ATPAI Privacy Policy is incorporated by reference.
Client is responsible for privacy notices, recording and AI notices, consent, lawful basis, data-subject request intake, staff notices, suppression records, and industry-specific requirements. ATPAI will provide reasonable assistance with verified requests, security inquiries, and standard exports as required by the controlling agreement and applicable law. Non-standard migration, formatting, redaction, or consulting may require additional fees.
Unless a controlling agreement states otherwise, production call recordings, transcripts, summaries, messages, approvals, and dashboard records may be retained for up to 12 months during active service. After termination, Client may request a standard export of reasonably available data within 30 days; ATPAI may retain production data for up to 90 days for transition and may retain backup, security, billing, tax, audit, consent, suppression, and dispute records for up to 180 days or longer where reasonably necessary or required. Vendor backup cycles and legal holds may delay complete deletion.
14Intellectual property
Client retains ownership of its names, logos, business information, customer data, lists, content, policies, and other materials it provides (Client Materials). Client grants ATPAI and approved providers a non-exclusive, worldwide, limited license to host, copy, transmit, modify, display, and otherwise use Client Materials as reasonably necessary to configure, operate, secure, support, improve, document, and provide the Service and as otherwise authorized in writing.
ATPAI and its licensors retain ownership of the Service and all pre-existing or independently developed software, prompts, system instructions, agent and workflow designs, automation, schemas, dashboards, templates, methods, documentation, configurations, QA processes, analytics, know-how, and other materials (Provider Materials). During the active paid term, Client receives a limited, non-exclusive, non-transferable, non-sublicensable license to use the configured Service internally for the approved business and scope. No ownership transfers unless a signed agreement expressly says so.
Client represents that it has rights to all Client Materials and instructions and that their use will not violate law or third-party rights. ATPAI may use feedback and suggestions without restriction or payment, provided it does not disclose Client Confidential Information. ATPAI may use de-identified, aggregated, and statistical information that does not reasonably identify Client or an individual.
15Confidentiality
Confidential Information means non-public business, technical, financial, customer, security, product, pricing, credential, workflow, prompt, data, and other information disclosed in connection with the Service that a reasonable person would understand is confidential. It excludes information lawfully public without breach, already lawfully known, received lawfully without restriction, or independently developed without the other party’s information.
Each party will use the other’s Confidential Information only for the agreement, protect it with reasonable care, and disclose it only to personnel, contractors, subprocessors, and advisers who need it and are bound by confidentiality duties. A party may disclose information when legally compelled after giving notice where permitted and reasonable cooperation.
Confidentiality obligations continue for three years after disclosure, except trade secrets remain protected while legally qualifying as trade secrets and personal data, credentials, security information, Provider Materials, and records subject to longer legal duties remain protected as required. A party may retain archival copies required for backup, legal, security, tax, billing, insurance, or dispute purposes. Unauthorized disclosure may cause irreparable harm for which injunctive relief may be appropriate.
16Support and availability
Automated workflows and monitoring may operate continuously where supported, but human support is available through ATPAI’s approved channels and is prioritized by severity, package, client responsiveness, and vendor availability. Unless a signed Service Agreement states a service level, response and resolution times are targets rather than guarantees.
ATPAI may perform maintenance, updates, model changes, vendor changes, safety changes, and emergency work. The Service may be unavailable because of maintenance, carriers, internet, APIs, AI providers, client systems, credentials, security events, force majeure, or other third-party conditions. No service credits apply unless a signed agreement expressly provides them.
17Warranties and disclaimers
Each party represents it has authority to enter the agreement. Client warrants that its Client Materials, data, lists, scripts, offers, consents, instructions, and use of the Service are accurate, authorized, lawful, and do not infringe third-party rights. ATPAI warrants that it will perform paid professional services in a commercially reasonable and workmanlike manner. Client’s exclusive remedy for a proven breach of that limited warranty is commercially reasonable re-performance of the affected service.
EXCEPT FOR THE EXPRESS WARRANTY ABOVE, TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE WEBSITE, SERVICE, THIRD-PARTY PLATFORMS, AND AI OUTPUT ARE PROVIDED “AS IS” AND “AS AVAILABLE.” ATPAI DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, UNINTERRUPTED OPERATION, ERROR-FREE OPERATION, SECURITY, DELIVERABILITY, AND RESULTS.
ATPAI does not guarantee revenue, sales, lead volume, appointment volume, conversion, cost savings, response rate, customer satisfaction, review score, ranking, business outcome, or that the Service will meet every legal or operational requirement.
18Indemnification
Client will defend, indemnify, and hold harmless ATPAI, its owners, officers, personnel, contractors, affiliates, and providers from third-party claims, investigations, fines, penalties, damages, settlements, judgments, costs, and reasonable attorneys’ fees arising out of or related to:
- Client’s business, products, services, fulfillment, personnel, customers, or operations;
- Client Materials, Customer Data, lists, offers, pricing, scripts, instructions, or integrations;
- missing or defective notice, consent, opt-in, suppression, recording disclosure, AI disclosure, or communications compliance;
- unlawful, deceptive, infringing, discriminatory, abusive, or unauthorized use of the Service;
- Client’s breach of the agreement, law, or third-party rights; or
- actions ATPAI takes in reasonable reliance on Client’s approval or instruction.
ATPAI will give reasonably prompt notice, allow Client to control the defense with qualified counsel, and provide reasonable cooperation at Client’s cost. Client may not settle a claim in a manner that admits ATPAI wrongdoing, imposes non-monetary obligations on ATPAI, or requires ATPAI payment without ATPAI’s written consent. ATPAI may participate with counsel at its own cost.
19Limitation of liability
TO THE MAXIMUM EXTENT PERMITTED BY LAW, EACH PARTY’S TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THE AGREEMENT WILL NOT EXCEED THE FEES CLIENT PAID ATPAI FOR THE AFFECTED SERVICE DURING THE THREE MONTHS IMMEDIATELY BEFORE THE EVENT GIVING RISE TO THE CLAIM.
Neither party will be liable for indirect, incidental, consequential, special, exemplary, punitive, or enhanced damages; lost profits, revenue, leads, orders, data, goodwill, or reputation; business interruption; cost of substitute service; or damages resulting from AI Output, third-party platforms, caller or customer conduct, Client data, Client-approved actions, or Client business decisions, even if advised that the damage was possible.
The cap and exclusions do not limit Client’s payment and tax obligations, Client’s indemnification obligations, misuse of the Service, infringement or misappropriation of Provider Materials, fraud, willful misconduct, or liability that cannot legally be limited. A signed agreement may state additional exclusions. The limitations apply to all theories of liability and are an essential basis of the bargain.
A claim must be brought within one year after it accrues unless a longer period is required by law. Some jurisdictions do not allow certain exclusions or limitations, so they apply only to the maximum extent permitted.
20Delaware law and dispute resolution
The agreement is governed by Delaware law, without regard to conflict-of-law rules. Before starting a formal proceeding, the parties will have authorized representatives attempt in good faith to resolve the dispute for 15 days after written notice. This requirement does not delay payment collection, small-claims matters, emergency or injunctive relief, or action needed to protect confidentiality, intellectual property, security, or persons from urgent harm.
EXCEPT FOR THE COURT MATTERS LISTED BELOW, ANY DISPUTE ARISING OUT OF OR RELATING TO THE AGREEMENT WILL BE RESOLVED BY BINDING INDIVIDUAL ARBITRATION ADMINISTERED BY THE AMERICAN ARBITRATION ASSOCIATION (AAA) OR JAMS UNDER ITS APPLICABLE COMMERCIAL RULES, SEATED IN DELAWARE, BEFORE ONE ARBITRATOR. THE FEDERAL ARBITRATION ACT GOVERNS THIS ARBITRATION PROVISION.
Either party may bring an eligible individual claim in small-claims court. ATPAI may bring payment or collection claims in court. Either party may seek temporary, preliminary, or permanent injunctive relief in court for misuse of intellectual property, confidentiality, security, unauthorized access, or urgent harm. For permitted court proceedings, the parties consent to exclusive jurisdiction and venue in the state and federal courts located in Delaware.
EACH PARTY WAIVES THE RIGHT TO A JURY TRIAL. DISPUTES MUST BE BROUGHT ONLY ON AN INDIVIDUAL BASIS, NOT AS A CLASS, COLLECTIVE, CONSOLIDATED, REPRESENTATIVE, OR PRIVATE-ATTORNEY-GENERAL ACTION. THE ARBITRATOR MAY AWARD RELIEF ONLY TO THE INDIVIDUAL PARTY SEEKING RELIEF AND ONLY AS NEEDED TO RESOLVE THAT PARTY’S CLAIM.
If the class or representative waiver is finally held unenforceable for a particular claim or remedy, that claim or remedy will proceed in a Delaware court after the arbitrable issues are completed. Nothing in this section prevents a party from reporting an issue to a government agency where law permits.
21Notices
Operational notices may be sent through email, the portal, an invoice, support channel, or other approved business channel. Legal notices must be in writing and sent by email to the addresses in the applicable Order Form or Service Agreement. Notices to ATPAI must also be sent to privacy@atpai.io with “Legal notice” in the subject. Existing clients must also send a duplicate by trackable mail to ATPAI LLC at 300 Delaware Ave., Suite 210, Wilmington, DE 19801, unless a controlling signed agreement identifies a different notice address.
Notice is effective when received, when electronic delivery is confirmed without an error, when delivery is refused, one business day after deposit with a nationally recognized courier, or three business days after deposit by trackable U.S. mail, whichever applicable event occurs first. Client must keep contact, billing, and notice information current.
22General terms
Client may not assign or transfer the agreement without ATPAI’s written consent. ATPAI may assign it to an affiliate or in connection with a merger, financing, reorganization, sale of assets, or change of control. An unlawful assignment is void.
Neither party is liable for delay or failure caused by events outside its reasonable control, including carrier, internet, cloud, utility, API, model, vendor, payment, labor, government, war, terrorism, epidemic, natural disaster, cyberattack, or supply-chain events (force majeure). This does not excuse amounts already due. The affected party will use commercially reasonable efforts to reduce the impact.
If a provision is unenforceable, it will be modified to the minimum extent necessary and the remainder will remain effective. Failure to enforce a term is not a waiver. Remedies are cumulative. Headings are for convenience. The parties are independent contractors; no partnership, agency, employment, franchise, fiduciary, or joint venture is created. No third party is a beneficiary unless expressly stated.
The controlling documents described in Section 2 are the entire agreement concerning their subject matter and replace prior or contemporaneous proposals, statements, and understandings. An amendment must be in a writing accepted by authorized representatives, except ATPAI may update these Terms as stated below. Counterparts and electronic records are valid.
23Changes and contact
ATPAI may update these Terms to reflect changes in law, security, vendors, or the Service. The “Last updated” date identifies the current version. We will provide advance notice of a material change to existing paid clients when required by a controlling agreement or law. A change does not retroactively modify accrued payment obligations, claims, or a signed agreement. Continued use after the effective date of a properly noticed change constitutes acceptance to the extent permitted by law; if Client rejects a material change, its remedy is to stop using the affected Service subject to its existing term and payment obligations.
Questions about these Terms may be sent to ATPAI LLC at privacy@atpai.io.