Terms of Service
These terms explain how Aucsol handles project inquiries, proposals, payments, delivery, emergency engineering, ownership, and support.
Last updated: June 21, 2026
1. Who we are
Aucsol is a senior-led development studio based in Lahore, Pakistan. We provide website development, business systems, online booking systems, payment integrations, customer portals, automation, SaaS improvements, and Emergency Engineering services.
2. No automatic engagement
Contacting us, submitting a form, sending a WhatsApp message, booking a call, or requesting an emergency assessment does not automatically create a client relationship or service agreement. Work begins only after scope, pricing, access, payment terms, and responsibilities are agreed.
3. Scope of work
Each project or engagement is governed by the agreed scope, proposal, estimate, statement of work, email confirmation, or written agreement. Anything not included in the agreed scope is considered additional work and may require a separate estimate or approval.
4. Pricing and payment
Pricing depends on scope, complexity, timeline, integrations, risk, and support requirements.
Most projects require an upfront deposit before work begins.
Remaining payments may be tied to milestones, delivery stages, completion, or another agreed schedule.
Emergency Engineering work is quoted after initial assessment. Transparent pricing is provided before implementation begins.
Payment methods are agreed before work begins. Third-party payment processors may apply their own fees, policies, and processing rules.
5. Emergency Engineering
Emergency Engineering is for critical issues such as payment failures, production outages, critical bugs, SaaS failures, performance degradation, and urgent security-related fixes. Emergency submissions are reviewed based on availability, urgency, technical fit, access requirements, and risk.
We do not guarantee immediate availability, fixed recovery time, or resolution before reviewing the issue. Diagnosis, repair plan, and pricing must be accepted before implementation work begins.
6. Your responsibilities
Provide accurate project details, business requirements, access, assets, credentials, approvals, and feedback in a timely manner.
Ensure you have the right to share any code, files, accounts, content, data, or third-party systems you provide.
Do not send passwords, API keys, private keys, payment card details, sensitive customer data, or confidential source code through unsecured channels.
Review deliverables promptly and communicate requested changes clearly.
Maintain your own backups unless backup work is explicitly included in the agreed scope.
7. Access and security
When access to hosting, repositories, payment providers, databases, admin panels, analytics, or third-party tools is required, access should be limited to what is necessary for the work. We may request temporary, role-based, or read-only access where practical. You are responsible for revoking access after the engagement if appropriate.
8. Timelines
Timelines are estimates unless expressly agreed otherwise in writing. Delivery may be affected by scope changes, delayed feedback, missing access, third-party systems, payment delays, technical discoveries, or events outside our control.
9. Revisions and changes
Reasonable revisions may be included when stated in the agreed scope. New features, major direction changes, additional pages, extra integrations, design changes after approval, or work outside the agreed scope may require additional fees and a new timeline.
10. Refunds and cancellations
Refunds and cancellations depend on the agreed engagement terms, work already completed, time reserved, and costs incurred. Deposits may be non-refundable once work has started or a delivery slot has been reserved, unless otherwise agreed in writing.
If a project is cancelled after work begins, you may be billed for completed work, committed time, third-party costs, and any non-recoverable expenses.
11. Third-party services
Projects may rely on third-party services such as Stripe, PayPal, Paddle, Authorize.net, Coinbase Commerce, Payoneer, hosting providers, email providers, CRMs, analytics tools, SMS providers, APIs, plugins, and software libraries. We are not responsible for outages, policy changes, account restrictions, pricing changes, approval delays, bugs, or failures caused by third-party services.
12. Ownership and licensing
After full payment is received, you own the custom work created specifically for your project, unless agreed otherwise. Pre-existing tools, reusable components, frameworks, internal methods, templates, libraries, know-how, and general development patterns remain owned by their original owners or by Aucsol where applicable.
13. Portfolio use
Unless restricted by written agreement, we may reference completed work in our portfolio, case studies, proposals, and marketing materials. Sensitive details, private metrics, confidential screenshots, or client information are not shared without appropriate permission.
14. Confidentiality
We treat non-public project information, code, business details, credentials, and technical information as confidential. We are willing to sign reasonable NDAs before reviewing sensitive information when needed.
15. Warranty and support
Any warranty, support period, maintenance, monitoring, or post-launch assistance must be stated in the agreed scope. Unless ongoing support is agreed, delivery of a project does not include indefinite maintenance, future updates, third-party changes, hosting issues, or new feature requests.
16. Limitation of liability
To the maximum extent permitted by law, Aucsol is not liable for indirect, incidental, special, consequential, punitive, or lost-profit damages. Our total liability for any claim is limited to the amount paid to Aucsol for the specific service giving rise to the claim.
17. No guarantee of results
We build and improve websites, systems, integrations, and workflows to support business outcomes. However, we do not guarantee specific revenue, traffic, rankings, leads, bookings, conversion rates, review volume, or business results, because these depend on many factors outside our control.
18. Governing law
These terms are governed by the laws of Pakistan, unless a different governing law is agreed in writing for a specific engagement. If a dispute arises, both parties agree to first attempt to resolve it through good-faith communication.
19. Changes to these terms
We may update these Terms of Service from time to time. The updated version will be posted on this page with a revised “Last updated” date.
20. Contact
For questions about these terms, contact:
Aucsol
Lahore, Pakistan
[email protected]→