Terms and Conditions

1. About SpidLabs

SpidLabs is an AI automation and systems service provider based in Ahmedabad, Gujarat, India. SpidLabs is certified by the Government of India under MSME. These terms apply to the use of our website and to services provided by SpidLabs unless a separate signed agreement states otherwise.

2. Acceptance of Terms

By using this website, contacting SpidLabs, accepting a proposal, making a payment, or allowing us to begin work, you agree to these Terms and Conditions. If a signed project contract, proposal, statement of work, or invoice has different terms, that document will apply to the specific project.

3. Services

SpidLabs provides custom AI automation and systems services, including:

• AI automation and workflow systems
• Agentic AI and decision systems
• Lead intake, follow-up, CRM, and operations automation
• Internal process automation
• System optimization and scaling
• Browser automation and integrations for tools without APIs

The exact scope, deliverables, support period, revisions, price, and timeline for each project will be described in the relevant proposal, contract, invoice, or written project agreement.

4. Payments, Milestones, and Refunds

Payment terms may vary by project. In some cases, payment is due after project completion. In other cases, SpidLabs may require milestone payments or an advance payment before work begins. Payment terms will be agreed in the project contract, proposal, or invoice.

Payments may be collected through third-party payment or transfer providers such as Stripe, Skydo, PayPal, or other supported payment services.

Refunds are handled based on the signed contract, project agreement, and the stage of work completed. In some cases, a full refund, partial refund, or no refund may apply depending on the work already done, costs incurred, and the agreed project terms.

If a client does not make payment within the agreed payment period, SpidLabs may pause work, withhold access or delivery, remove or disable project access where appropriate, and take legal action to recover unpaid amounts.

5. Client Responsibilities

Clients are responsible for providing the access, information, approvals, and materials needed to complete the project. This may include:

• Account access
• API access and credentials
• Access to tools, platforms, CRMs, and software
• Current workflow access and process details
• Documents, data, approvals, and business rules needed for the work

Clients must provide accurate, complete, and lawful information. If incorrect or incomplete information causes rework, changes, delays, or additional requirements after completion, SpidLabs may charge separately for that additional work.

6. Timelines and Delivery

Project timelines are estimates based on the project scope, client cooperation, available access, and technical requirements. SpidLabs does not guarantee exact delivery dates or specific output results. Work may be completed before or after the estimated timeline depending on project conditions.

Timelines may change if there are delays in credentials, API access, data, client responses, approvals, third-party tools, or if the client requests additional work or changes to the original requirements.

7. Revisions and Change Requests

Some projects may include a limited number of revisions or changes after delivery. The number of free revisions, support period, and included changes will be specified in the project contract or written agreement.

Larger changes, new features, changed requirements, additional workflows, or work outside the agreed scope may be charged separately and may extend the timeline.

8. Ownership and Handover

After the agreed payment is completed and the project is delivered, the client will receive access to the final automation, workflow, or system deliverables agreed for that project. Where applicable, credentials and project access will be transferred or returned to the client after completion.

SpidLabs may continue to use general methods, templates, reusable code patterns, technical structures, and internal know-how for other projects. SpidLabs will not copy a client's full workflow into another client project and will not use one client's private data for another client.

9. Third-Party Tools and Costs

SpidLabs may use third-party tools based on project requirements, including Supabase, n8n, Cal.com, Google Analytics, OpenAI, LLM providers, browser automation tools, CRMs, APIs, client software, and other platforms.

The client is responsible for third-party tool fees, SaaS subscriptions, API credits, software licenses, payment provider fees, and any costs related to tools used in the client's automation or workflow unless otherwise agreed in writing. SpidLabs is not responsible for outages, pricing changes, limitations, API changes, or failures caused by third-party services.

10. AI and Automation Limitations

AI systems, automations, agents, integrations, and browser workflows may fail, produce incorrect responses, break due to third-party changes, or behave unexpectedly. SpidLabs tests projects before delivery, but does not guarantee 100% accuracy, uptime, output quality, or error-free operation.

Clients are responsible for reviewing outputs before business use and for monitoring automations after deployment. SpidLabs recommends that clients do not rely on AI agents or automations alone for payment, money movement, or other high-risk financial decisions without human review and safeguards.

11. Confidentiality and Client Data

SpidLabs may receive client data, credentials, workflows, documents, and business information during a project. We will use such information only for the purpose of providing the agreed services. We do not sell client data to third parties.

Clients should only provide access and data necessary for the project and should remove or rotate access after completion where appropriate.

12. Limitation of Liability

To the maximum extent permitted by law, SpidLabs will not be responsible for indirect, incidental, special, consequential, or business losses, including loss of revenue, loss of profit, planned outages, data errors, third-party service failures, misuse of an AI agent or workflow, or decisions made based on automation outputs.

13. Suspension, Termination, and Non-Payment

SpidLabs may pause or stop work if the client does not provide required access, delays approvals, requests work outside the agreed scope, violates these terms, or fails to make payment on time.

If payment remains unpaid, SpidLabs may withhold project access, stop support, delete or disable unpaid project resources where appropriate, and take legal action to recover unpaid amounts. If access was provided before full payment and the client fails to pay, SpidLabs may take steps to resolve, disable, or recover the unpaid project work.

14. Governing Law

These terms are governed by the laws of India, unless a signed project agreement states otherwise. Any disputes will be handled under the applicable laws and courts having jurisdiction in India.

15. Changes to These Terms

SpidLabs may update these Terms and Conditions from time to time. When changes are made, the "Last updated" date at the top of this page will be updated.