INDEPENDENT DEVELOPER · PAKISTAN / WORLDWIDELet’s talk about your idea
Samiullahsamiullah.devWEB · MOBILE · AI
WORKING TOGETHER / CLEAR EXPECTATIONS

Terms &
conditions.

The ground rules for using this website and planning a project with me. Please read these alongside your project proposal before confirming work.

Last updated: September 22, 2026 · Version 2026-09-22

A request comes first.

Submitting a booking does not take payment or automatically start work.

Scope is agreed in writing.

Deliverables, payment terms, timing, and ownership are confirmed for your project.

Your legal rights remain.

Project terms do not remove protections that apply under law.

1. Who these terms apply to

These terms describe the use of samiullah.dev and the process for requesting freelance services from Samiullah, an independent developer based in Pakistan. “I”, “me”, and “my” refer to Samiullah. “You” and “client” refer to the person or organization using the site or requesting work.

Services may include website and mobile app development, design, ecommerce, APIs, AI agents, automation, data tools, SEO, deployment, and maintenance. You must have the legal capacity to enter a project agreement, or be authorized to act for the organization you represent.

2. Website terms and project agreements

These website terms provide the general framework. Before paid work starts, we will agree in writing on the deliverables, price, payment schedule, timing, responsibilities, and any project-specific conditions. Written agreement may be recorded in an accepted proposal, statement of work, or clear email confirmation.

If an expressly agreed project term conflicts with these general terms, that project term takes priority for that project, subject to applicable law. Browsing the website, using the planner, or sending an inquiry does not by itself commission paid work.

3. Booking requests and accounts

A package booking is a request for review, not automatic acceptance or a guaranteed start date. The booking form does not collect payment. A reference number or “requested” status confirms receipt only. Work starts after we confirm the project and any agreed prerequisites are met.

Provide accurate contact details and keep your password and verification codes private. You are responsible for activity you authorize through your account. Contact me if you suspect unauthorized access. Do not share passwords, private keys, or sensitive client records in public reviews or ordinary inquiry forms.

4. Scope, packages, and additional features

Package descriptions set out the published starting scope. Platform, programming language, and feature selections are preferences to discuss; selecting them does not add unlimited work to a package. Page counts, screens, integrations, data volumes, testing, deployment, and handover should be confirmed in the written scope.

A new feature, substantial redesign, extra integration, or change to an approved direction may require a separate estimate. I will explain its effect on price and timing and seek written agreement before carrying out additional chargeable work. Planner recommendations are guidance, not final quotations.

5. Prices, invoices, and third-party costs

Published package prices are in US dollars and are starting prices for the stated scope. The agreed proposal or invoice will identify the final amount, currency, payment method, payment milestones, applicable taxes, and any disclosed transaction charges. There is no automatic recurring subscription created by a booking.

Hosting, domains, premium themes, paid plugins, app-store accounts, advertising spend, model/API usage, telephony, and third-party subscriptions are separate unless expressly included. We will agree who owns and pays for these accounts. Estimates of usage-based charges are not fixed-price guarantees.

Any deposit, due date, late-payment consequence, or recurring support arrangement must be stated in the project agreement. If an agreed payment becomes overdue, I will contact you before pausing affected work and discuss the impact on delivery.

6. Client materials, access, and decisions

You are responsible for supplying the content, feedback, approvals, and authorized access needed for the agreed work. You must have permission to use any text, images, trademarks, code, datasets, and other materials you provide.

Use secure access-sharing methods and grant only the permissions needed. Before changing an existing production system, we should agree on backups, staging, deployment approval, and rollback responsibilities. You remain responsible for your business decisions, the accuracy of your content, and the legal requirements of your products and customer relationships.

7. Timelines and communication

Published delivery days are estimates for the described package. The start date, milestone dates, dependencies, and whether time is counted in working or calendar days will be confirmed in writing. Delays in content, access, feedback, payment, or third-party review can affect the schedule.

I will communicate material changes or blockers as they become known. Neither party should assume that silence approves additional work or a revised deadline. If a project becomes inactive, we will discuss a revised schedule before resuming.

8. Revisions, testing, and acceptance

A revision is a round of consolidated feedback on work within the agreed scope. The included number of rounds is shown in the selected package and confirmed in the proposal. Revisions do not include a different product, a new design direction after approval, or features outside the agreed scope.

We will identify the supported browsers, devices, acceptance criteria, and review process for the project. Please describe reproducible issues clearly, including the steps and environment involved. A defect is a failure to meet the agreed requirements; it is different from a new feature request. Any post-delivery defect-correction period will be stated in the project agreement. Silence is not automatic acceptance under these website terms.

9. Cancellation, pauses, and refunds

You can cancel a booking through your account while its status is “requested”. After confirmation or once work has started, contact me in writing to request cancellation or a pause. A change in dashboard status alone does not determine any payment or refund entitlement.

For an active project, we will review completed work, payments received, and authorized third-party commitments against the agreed cancellation terms and applicable law. Any settlement or refund should be documented with its amount, basis, and payment timing. These website terms do not impose a blanket “no refunds” policy or an automatic non-refundable deposit.

If I cannot continue, I will notify you and discuss an orderly handover and any payment adjustment for undelivered work. Nothing here removes mandatory cancellation, refund, or consumer rights.

10. Ownership, licensing, and handover

You retain ownership of materials you provide. The project agreement should specify which custom deliverables are assigned or licensed to you, the rights granted, and when those rights take effect, including any agreed payment condition. Do not assume that a booking alone transfers intellectual property rights.

Pre-existing tools, reusable components, open-source software, fonts, stock assets, and third-party services remain subject to their own ownership and license terms. Handover contents—such as source code, design files, documentation, credentials, or deployment instructions—will be listed in the agreed scope.

I will seek your permission before using non-public client work, confidential information, or unpublished results in my portfolio. Website articles, photographs, and branding may not be copied or commercially reused without permission or another lawful basis.

11. AI agents, automation, and generated output

AI systems can produce inaccurate, incomplete, biased, or unexpected output. They may behave differently after a provider or model update. Evaluation reduces uncertainty but does not guarantee error-free operation, business results, or suitability for every use case.

For AI projects, we will agree on data sources, permitted tools, access limits, cost limits where supported, evaluation criteria, escalation paths, and the actions requiring human approval. You should review outputs before publishing them or relying on them for consequential decisions. Automated actions involving payments, account changes, communications, or data modification need explicit permissions and a defined review process.

Before connecting sensitive or confidential data to an external model or service, we must agree on the provider, authorized use, and relevant data-handling terms. Model/API and hosting costs are separate unless included in writing. Availability, output rights, and usage restrictions may also depend on the provider’s terms.

12. Platforms, SEO, and service limitations

Hosting companies, payment processors, app stores, search engines, and other platforms control their own approval processes, policies, pricing, and availability. I cannot guarantee app-store approval, uninterrupted third-party service, a particular search ranking, traffic level, revenue, conversion rate, or advertising result.

Unless included in the agreed scope, a project does not include formal legal compliance certification, a penetration test, an accessibility certification, or unlimited optimization. Any agreed security, accessibility, performance, or SEO work will have defined deliverables and test criteria.

13. Launch, maintenance, and support

Deployment and ongoing support are included only to the extent stated in the project agreement. A completed build does not create unlimited maintenance, monitoring, incident response, or an uptime commitment. One-off maintenance packages cover the stated work period or time allowance, not an ongoing subscription.

After handover, responsibilities for hosting renewals, backups, updates, security monitoring, and access management should be clear. Changes made by you or another provider may require investigation or a new scope before I can support them.

14. Confidentiality and personal information

Project access and non-public materials should be used only for the agreed work. We will identify any special confidentiality requirements before sharing information. Any subcontractor access, external processing, retention, or deletion requirements should be agreed as appropriate for the project.

The website uses information you submit to respond to inquiries, manage accounts and bookings, and review submitted feedback. Session and security functions support account access; saved articles are stored in your browser. Clearing browser storage can remove that reading list.

Contact me about access, correction, or deletion requests. Requests will be assessed under applicable requirements and any necessary record-keeping obligations. This summary is not a substitute for a dedicated privacy notice or a project-specific data-processing agreement where one is needed.

15. Acceptable use and reviews

Do not use the site or request services for unlawful activity, fraud, harassment, infringement, unauthorized system access, malware, or deceptive impersonation. Do not attempt to access another client’s bookings, misuse verification codes, or interfere with the site’s operation.

Reviews should reflect your own experience and must not disclose confidential or sensitive personal information. Reviews are moderated before public display. Spam, threats, unlawful material, and misleading content may be declined or removed; legitimate criticism is not prohibited simply because it is negative.

Access may be restricted when reasonably necessary to address misuse or protect other users. Where appropriate, I will explain the reason and provide a way to contact me. This does not remove contractual or statutory rights.

16. Responsibility and legal rights

Website information is general guidance and may contain errors or become outdated. I aim to provide services with reasonable care and skill within the agreed scope, but no website or software can be promised to be entirely free from faults or interruptions.

Any project-specific warranty, liability allocation, or financial liability cap must be expressly agreed and is effective only to the extent permitted by law. These terms do not exclude liability that cannot lawfully be excluded, or restrict mandatory consumer rights. No claim is made that every clause is enforceable in every jurisdiction.

17. Questions, disputes, and applicable law

If something is wrong, contact me with the booking reference, a description of the issue, and the outcome you are seeking. We should first try to resolve the matter through a direct written discussion. You do not lose a legal remedy merely by raising a concern.

Samiullah operates from Pakistan and works with clients in other countries. Any choice of governing law, court, or dispute-resolution procedure should be recorded in the project agreement. These website terms do not impose mandatory arbitration or an exclusive foreign court, and do not displace protections that apply by law.

18. Updates and contact

The version date on this page identifies the current website terms. Updates apply prospectively and do not automatically rewrite an already accepted project agreement. Material project changes require agreement between us; continued browsing is not treated as consent to retroactive project changes.

For questions about these terms or a project, email [email protected], call +92 345 6484082, or use the contact page. Please include your booking reference if you have one.

Ask about these terms ↗

◉ Let’s chat