Master Services Agreement
Last updated May 2026 · Provider: Linkd AI Limited · Applies to any business entity acquiring services from the Company
Part A: Commercial Terms & Operational Delivery
1. Scope of Work and Scope Creep Protection
Documented Scope Only: The Company will deliver only the specific automation architecture, software integrations, API connections, and data parsing routines expressly detailed in the signed Quote or Statement of Work (SoW).
Out-of-Scope Work: Any requests for modifications, additional system integrations, data migrations, or feature additions not explicitly documented in the original SoW are classified as Change Requests.
Change Request Process: Change Requests will be scoped separately and billed either at the Company's current standard hourly rate or as a new fixed-price build quote. Work will not commence on changes until the Client provides written or electronic authorization.
2. Document Hierarchy and Order of Precedence
In the event of any conflict, the following strict descending order of priority shall apply:
- First Priority: This Master Services Agreement (MSA)
- Second Priority: The specific Statement of Work (SoW)
- Third Priority: The initial commercial Quote
3. Client Acceptance and Testing Period
Testing Window: The Client has five (5) business days from deployment notification to test the workflow and report any structural errors or functional deviations from the agreed scope.
Deemed Acceptance: If the Client fails to report functional errors in writing within the Testing Period, or begins utilizing the workflow in active operations, the deployment shall be deemed completely accepted.
Subsequent Issues: Any modifications requested after the Testing Period will be managed under the monthly maintenance agreement or treated as an independent Change Request.
4. Payment, Retainers, and Suspension Rights
Invoicing: One-off setup fees must be cleared in full before live deployment. Recurring monthly fees are invoiced monthly in advance.
Suspension for Non-Payment: If any payment remains outstanding for more than seven (7) business days past the due date, the Company reserves the right to immediately suspend or disable all automated pipelines, API tokens, and scripts without further notice.
Liability Excluded for Suspension: To the extent permitted by law, the Company shall not be liable for any missed data synchronization, accounting ledger gaps, failed dispatches, or operational delays resulting from a suspension enacted due to Client non-payment.
5. Client Obligations and Core Responsibilities
The Client acknowledges that the performance of the automation pipelines relies upon active Client cooperation. The Client shall:
- (a) License Maintenance: Maintain valid, active software licenses for all third-party platforms integrated into the automated workflows.
- (b) API Access Control: Maintain uninterrupted and functional API access tokens, endpoints, webhooks, and communication routes.
- (c) Accurate Credentials: Provide accurate, secure, current, and correctly formatted system access keys and user privileges.
- (d) Informational Accuracy: Supply complete, accurate sample files and procedural data payloads necessary for configuration.
- (e) Deployment Testing: Thoroughly test and review system modifications within the established Testing Window.
- (f) Independent Backups: Maintain independent system backups and redundant databases of all critical commercial data.
6. Intellectual Property Rights & License Terms
Company Ownership: The Company retains all right, title, and interest in all proprietary software, scripts, templates, workflows, automation logic, and related intellectual property, unless expressly transferred in writing.
License Grant: Conditional upon timely payment of all fees, the Company grants the Client a non-exclusive, non-transferable, revocable, and non-sublicensable license to utilize the deployed workflows.
Permitted Use: This license is granted strictly for the Client's internal business operations. The Client is explicitly prohibited from reselling, redistributing, sub-licensing, or reverse-engineering the logic.
Client Ownership: The Client retains ownership of all Client data and content processed through the services.
Part B: Allocation of Risk & Liability Boundaries
7. B2B Statutory Contracting Out (New Zealand Law)
The Client confirms that all services are acquired solely for the purposes of a business. To the maximum extent permitted by law, the provisions of the Consumer Guarantees Act 1993 do not apply. Both parties expressly contract out of sections 9, 12A, and 13 of the Fair Trading Act 1986.
8. Warranty Disclaimer ("As-Is" Basis)
All services, custom scripts, API connections, configurations, and data automation pipelines are provided strictly on an "As-Is" and "As-Available" basis. To the maximum extent permitted by law, the Company makes no warranties, express or implied, and explicitly does not warrant that the operation of the services will be entirely uninterrupted, secure, or free from functional software errors.
9. Exclusion of Consequential and Indirect Loss
To the maximum extent permitted by law, the Company shall not be liable for any indirect, incidental, special, or consequential losses. This explicit exclusion covers: loss of business profits or revenue; discrepancies or calculation errors inside accounting platforms (e.g., Xero, MYOB); missed dispatch logs or scheduling delays within operational software (e.g., MyTrucking, Fergus, Simpro); or any loss, corruption, or temporary deletion of data payloads, PDF attachments, or incoming emails.
10. Defensible Liability Cap
If the Company is found liable to the Client, the Company's total aggregate liability for all claims shall be strictly limited to the total fees actually paid by the Client to the Company during the six (6) months immediately preceding the event that gave rise to the liability.
11. Limitation Period for Claims
No legal proceedings arising out of or related to this agreement may be brought against the Company more than twelve (12) months after the specific date of the event or omission giving rise to the alleged claim.
12. Third-Party Platform and API Dependencies
The Company shall not be liable for system failures or data variances caused by: structural updates, deprecated endpoints, or breaking code changes enacted by third-party software vendors; rate-limiting restrictions, token expirations, or vendor-side cloud outages; or inaccurate, malformed, or corrupted data input provided by the Client's customers, staff, or suppliers.
13. Client Indemnification Obligations
To the maximum extent permitted by law, the Client agrees to indemnify and hold harmless the Company from and against any third-party claims arising out of or related to: (a) unlawful use of the automation pipelines; (b) the nature, legality, or accuracy of any supplied data or payloads; (c) privacy violations or data leaks resulting from processing data in accordance with the Client's instructions; and (d) any regulatory non-compliance committed by the Client.
14. Force Majeure (External Cloud Failures)
Neither party shall be liable for any delay or failure to perform obligations (excluding payment obligations) caused by events beyond its reasonable control, including major infrastructure outages, internet routing failures, widespread DDoS attacks, upstream cloud provider collapses (e.g., DigitalOcean, AWS, Microsoft Azure, OpenAI, Cloudflare), acts of God, pandemics, or state-declared emergencies.
Part C: Support, Data Handling, & Compliance
15. Support SLA and Severity Framework
Standard Business Hours: 8:30 AM to 5:30 PM, Monday to Friday (excluding New Zealand public holidays).
Formal Logging: An issue is only deemed "Formally Logged" when written notification is delivered directly to the Company's designated support email or text channel. Notifications sent outside Business Hours are deemed received at 8:30 AM on the following business day.
Critical Severity (total workflow outage, financial transaction duplication, or total integration framework failure): acknowledge and initiate technical review within 8 Business Hours of Formal Logging.
Non-Critical Severity (cosmetic issues, enhancement requests, minor delays, or non-blocking bugs where data continues to flow): addressed asynchronously on a best-efforts basis with no fixed response window.
16. System Logs and Activity Evidence
The Company's technical system logs, automated execution timestamps, and cloud-hosted database registries shall constitute prima facie evidence of service activity, pipeline actions, or system errors in any dispute. These records shall be presumed accurate unless the Client provides clear counter-evidence proving manifest error or backend tampering by the Company.
17. Privacy Act 2020 & Shared Security Model
Data Processor Status: The Company processes information strictly as a Technical Processor on behalf of the Client (the Data Controller). All data processed remains the Client's property.
Ephemeral Processing: Payload data is handled transiently and cached only long enough to execute the transfer and manage necessary retry loops. System execution logs are systematically purged after 90 days.
No Absolute Security Guarantee: The Client acknowledges that no digital pipeline is completely immune to sophisticated cyber threats.
Mandatory Breach Notification: If the Company confirms a security breach that is reasonably likely to cause serious harm, it will notify the Client within twenty-four (24) hours to ensure statutory notification obligations to the Office of the Privacy Commissioner can be fulfilled.
18. Confidentiality and Survival
Each party agrees to hold in strict confidence all proprietary or commercially sensitive information acquired from the other party. Confidentiality obligations shall survive the termination of this agreement for a period of three (3) years. Obligations concerning security credentials, system passwords, API tokens, and access keys shall survive indefinitely.
19. Subcontractors and Cloud Infrastructure
The Company reserves the right to utilize specialized subcontractors, automated AI development utilities, and reputable third-party cloud infrastructure providers (including, but not limited to, DigitalOcean, Amazon Web Services (AWS), or Google Cloud) to host, run, deploy, and monitor the automated pipelines.
Part D: Offboarding & General Legal Terms
20. Termination for Cause and Material Breach
Either party may terminate this agreement immediately by providing structured written notice where the other party: (a) commits a material breach and fails entirely to remedy it within fourteen (14) days of receiving written notification; or (b) becomes insolvent, enters into liquidation, or formally ceases to carry on its primary commercial business operations.
21. Termination Assistance and Offboarding Handover
Upon termination (requiring 30 days' written notice, or processed under Section 20):
- Credential Deletion: The Company will securely purge all stored Client API credentials, system tokens, and authentication accesses within seven (7) business days of the final service date.
- Code and Configuration: Unless explicitly agreed otherwise in a separate IP transfer contract, the Company's proprietary monitoring configurations and backend script deployments will be deactivated.
- Migration Assistance: If the Client requires technical documentation or transitional data exports, this assistance will be scoped separately and billed at the Company's current standard commercial hourly rates.
22. Assignment and Transfer Restrictions
The Client shall not assign, novate, delegate, or otherwise transfer any of its rights or obligations under this agreement to any third party without the express prior written consent of the Company. Any attempted assignment without such consent shall be null, void, and constitute a material breach of this agreement.
23. Entire Agreement and Supersession
This agreement, incorporating all executed Statements of Work and active commercial Quotes, constitutes the entire agreement between the parties. It completely supersedes all prior oral or written discussions, negotiations, representations, emails, promises, or marketing assurances. Both parties acknowledge they have not relied on any representation outside of these written terms.
24. Governing Jurisdiction
This agreement is governed exclusively by the laws of New Zealand. Both parties submit to the sole and absolute jurisdiction of the Courts of New Zealand to resolve any disputes arising out of these terms.