Disclaimer

1. No Guarantees on Business Outcomes

While we build highly optimized, secure, and production-ready workflows (n8n, Supabase, chatbots, custom websites), Smesh.dev cannot guarantee specific business outcomes, timeline efficiencies, traffic increases, or financial returns. Business results depend entirely on your operational data, customer interaction quality, and how you manage and run the deployed systems.

2. Third-Party Tools & API Services

Our integrations rely on third-party SaaS providers and cloud services (including, but not limited to, n8n, Supabase, OpenAI, Meta, WhatsApp, Vercel, and Twilio).

Smesh.dev provides no warranties (express or implied) regarding the operational uptime, future pricing, security compliance, or feature availability of these third-party platforms. Any system errors, downtime, or cost changes caused by these external platforms are not the responsibility of Smesh.dev.

3. AI Chatbots & LLM Limitations

We construct AI chatbots and customer support pipelines using advanced semantic prompt designs and Retrieval-Augmented Generation (RAG). However, because these systems utilize large language models (LLMs), they have inherent limitations.

AI agents can occasionally hallucinate, output incorrect details, or present outdated suggestions. Smesh.dev is not liable for customer support mistakes, communication errors, or database errors caused by automated AI replies. We recommend adding human moderation (human-in-the-loop) for high-impact business flows.

4. Scope of Support & Warranties

All systems are built and tested to meet client-approved specifications. Post-launch, technical support is limited to the agreed scope in the proposal and includes 30 days of free support.

After the 30-day support period, any troubleshooting, system revisions, API upgrades, or troubleshooting of third-party system outages will require a separate paid maintenance contract or hourly billing.

5. Limitation of Liability

Smesh.dev and BismillahTC Digital Services will not be liable for any direct, indirect, special, or consequential losses, including lost revenue, loss of business data, database corruption, or system disruptions. You assume full operational responsibility for the systems once they are deployed to your active servers or cloud accounts.

6. General Information Only

The case studies, articles, blueprints, and database guides hosted on this site are for general educational purposes. They do not constitute professional, legal, or data compliance advice. It is your responsibility to verify that your data processing pipelines comply with local laws (such as Pakistan's Prevention of Electronic Crimes Act - PECA) or global rules (GDPR, HIPAA).