These Service Terms & SLA ("Service Terms", "Agreement") apply to all customized statements of work (SOW), technical consulting agreements, and engineering engagements entered into with Spyber Polymath ("Contractor", "we", "us", directed by Aman Anil):
•
Hierarchy of Documents:In the event of a direct conflict between these Service Terms and a specific executed Statement of Work (SOW), the executed SOW shall prevail for that engagement.
•
Independent Contractor:Spyber Polymath performs services strictly as an independent contractor. Nothing in this Agreement creates an employment, partnership, joint venture, or agency relationship.
SECTION 02
2. Primary Service Disciplines
Professional engineering services are offered across three primary disciplines: Software Development, Offensive Security, and Cloud Security & DevSecOps, supported by Technical Advisory & Consulting engagements.
•
A. Software Development:Full-stack web application engineering, Next.js App Router and React 19 architecture, Python/Django APIs, PostgreSQL relational modeling, and integrated applied AI/RAG workflows.
•
B. Offensive Security:Adversarial threat modeling, exploit research, defensive software architecture reviews, and code-level vulnerability mitigation guidance. We do not conduct third-party commercial penetration testing.
D. Technical Advisory & Consulting:High-level architectural teardowns, technology stack evaluations, single-point-of-failure analysis, technical debt remediation roadmaps, and engineering quality benchmarking.
SECTION 03
3. Deliverables, Milestones & Acceptance
Engagements are structured around clearly defined milestones and written deliverable schedules:
•
Milestone Definition:Each SOW sets forth specific deliverables, milestone criteria, and estimated delivery dates.
•
Review Window:Upon milestone delivery, Client has ten (10) business days to review and confirm compliance with agreed specifications.
•
Deemed Acceptance:Deliverables are deemed accepted if no written defect notification is provided within the review window.
SECTION 04
4. Client Responsibilities & Cooperation
Successful technical execution requires timely client cooperation and resource provisioning:
•
Access & Credentials:Client must provide necessary API keys, repository permissions, cloud sandbox access, and design assets in a timely manner.
•
Decision-Making:Client must designate a primary technical point of contact authorized to make timely architectural decisions.
•
Project Delays:Delays resulting from client non-cooperation or delayed approvals extend milestone timelines accordingly.
SECTION 05
5. Change Orders & Scope Adjustments
Modifications to project scope must be formally documented before work commences:
•
Written Change Requests:Any addition, reduction, or modification to deliverables must be requested in writing.
•
Impact Assessment:We evaluate the impact on cost, architecture, and timeline, and provide a written Change Order for client approval prior to execution.
SECTION 06
6. Commercial Terms & Milestone Billing
Financial terms, invoicing schedules, and expense pass-throughs:
•
Invoicing Schedule:Invoices are issued based on agreed milestone schedules or monthly retainer intervals as defined in the SOW.
•
Payment Terms:Invoices are due within fifteen (15) calendar days of invoice date unless otherwise agreed in writing.
•
Third-Party Pass-Through Costs:Client is directly responsible for third-party subscriptions, hosting infrastructure (AWS, Vercel, Supabase), API token quotas, and domain registrations.
SECTION 07
7. Cancellation & Refund Principles
Our refund policy reflects the professional service nature of custom engineering:
•
Completed Milestones:Payments made for completed, delivered, and accepted milestones represent completed engineering labor and are non-refundable.
•
Advance Deposits:Advance milestone deposits are non-refundable once engineering work on that milestone has commenced.
•
Retainer Engagements:Ongoing retainers may be cancelled with thirty (30) days prior written notice. Unused, unearned advance retainer funds are returned pro-rata.
•
Dispute Procedure:Invoice disputes must be submitted in writing to legal@spyberpolymath.com within fourteen (14) days of invoice date.
SECTION 08
8. Confidentiality & Non-Disclosure
Both parties agree to hold proprietary information in strict confidence:
•
Confidential Information:Encompasses source code, architectural blueprints, database credentials, business roadmaps, and client data.
•
Protection Standard:Parties must exercise reasonable technical safeguards and not disclose confidential information to third parties without prior written consent.
SECTION 09
9. Intellectual Property Assignment
Ownership of bespoke deliverables versus pre-existing tools:
•
Work Product Assignment:Upon full and final payment of all milestone invoices, all rights, title, and interest in bespoke code created specifically for Client are assigned to Client.
•
Pre-Existing IP:Spyber Polymath retains sole ownership of pre-existing software, boilerplates, libraries, scripts, and methodologies. Client receives a perpetual, non-exclusive license to use incorporated pre-existing assets.
SECTION 010
10. Infrastructure Commitments & SLA Standards
Where a SOW includes managed infrastructure or retainers, service level standards apply:
•
Uptime Targets:For managed cloud infrastructure, we engineer configurations aiming for 99.9% target availability, excluding scheduled maintenance or upstream cloud outages.
•
Incident Severity Tiers:Critical operational defects receive response within 4 hours; standard non-critical requests within 24–48 business hours.
•
Remediation Window:We provide a thirty (30) day warranty window following deployment to correct reproducible defects in deliverables without charge.
SECTION 011
11. Termination & Legal Inquiries
Either party may terminate an engagement for material breach upon fourteen (14) days written notice if the breach remains uncured.
•
Legal Correspondence:Direct all contractual notices and SOW inquiries to legal@spyberpolymath.com.
