Build, improve or fix your WordPress website with expert support. Post a Project → Post a Project →

Terms and Conditions

Agency governance · Professional WordPress Solutions

Terms and Conditions.Clear expectations. Better Projects.

Understand the rules for using Esposearch.net, commissioning managed WordPress Projects, participating as an Expert and protecting your rights. Search the terms, review the topics that matter, and clarify important conditions before approving a Project.

Last revised 3 November 2026Applies to Esposearch.netAgency Projects only
The agreement at a glance

Who the Terms protect and what they cover.

Project rules are clearest when everyone understands their role. These terms support accountable delivery and fair communication, with agency coordination at every stage.

For Clients

Understand the scope, responsibilities, payments and rights linked to a managed WordPress Project.

Explore the terms

For Experts

Understand professional eligibility, confidentiality, assignment standards and agency coordination.

Explore the terms

For everyone

Protect accounts, respect third party rights and know how to raise a concern.

Explore the terms
General contractual framework

Explore 20 clear sections of our Terms.

Read the sections in order or jump directly to the clause relevant to your account or Project. Specific agreed Project documents may provide additional commercial detail, and mandatory legal rights remain applicable.

SECTION 01 / 20Accounts

Who operates this website

Operator, scope, acceptance

Operator and website

Esposearch.net is operated by Esposearch Limited Company, registered under the laws of the Republic of Kenya. These Terms and Conditions explain the general rules for accessing the website, maintaining an account and commissioning Professional WordPress Solutions through our managed agency Project process.

When these terms apply

By accessing or using the website, you agree to the website rules relevant to your use. A legally binding paid Project engagement also depends on the specific scope, price, milestones and other commercial terms accepted for that Project. If you do not agree with these general Terms, do not use features that require agreement.

Other applicable documents

An approved Project agreement, written statement of work and applicable payment terms may contain more specific obligations. Our Privacy Policy, Content Privacy Policy and Refunds Policy address related subjects. If documents conflict, the specific agreed Project terms generally govern that Project, subject to mandatory law and any expressly stated order of priority.

SECTION 02 / 20Accounts

Key definitions and user roles

Clients, Experts, Administrators, Projects

Client

A Client is an individual or organization requesting, commissioning, reviewing or paying for a WordPress Project. Where an individual acts for an organization, that individual must have authority to act on its behalf.

Expert

An Expert is a professional assessed or approved to contribute to defined Project work. Registration or training does not create automatic approval, an employment relationship or a right to paid assignments. An Expert may be subject to additional written participation terms.

Administrator and agency

An Administrator manages the platform, user permissions, Project administration and agency governance as authorized. Esposearch is the contracting agency point of contact for approved client Projects; Client engagements are managed through the agency instead of separate direct Expert contracts.

Project and scope

A Project is a custom WordPress requirement submitted for review and, if accepted, governed by an agreed written scope. A scope may identify deliverables, milestones, review criteria, timing, dependencies, fees and permitted technical methods.

SECTION 03 / 20Accounts

Eligibility and account security

Registration, credentials, authority

Eligibility and accuracy

You must have the legal capacity and authority needed for your use of the website and any Project. Supply accurate registration and contact information, keep relevant details up to date and do not impersonate another person or organization.

Account access

Keep login credentials secure, use appropriate authentication controls and report suspected unauthorized access promptly. You are responsible for activities you authorize or cause through your account, subject to applicable law and the facts of any account compromise.

Permissions and approval

Account privileges, Client access, Expert eligibility and Administrator capabilities depend on authorized platform settings and agency approval. Users must not attempt to obtain access to accounts, systems or Project information beyond their permission.

SECTION 04 / 20Accounts

The managed agency relationship

Who coordinates the work

Agency coordination

Esposearch reviews requirements, organizes suitable delivery expertise and coordinates the approved Project. The Client works with the agency under the applicable Project terms rather than engaging Experts independently of that agreement.

Expert participation

Qualified Experts may perform relevant work under agency coordination and their own participation arrangements. Esposearch may use suitable professional contributors where the accepted Project terms permit; confidentiality, security, scope and quality obligations should apply to those contributors as appropriate.

No automatic assignment

Submitting a Project or joining as an Expert does not guarantee acceptance, funding, an offer of work or any particular outcome. The agency may decline work that falls outside its capabilities, operating standards or lawful requirements.

SECTION 05 / 20Projects

Project requests and acceptance

Submission, review and formation

Request is not acceptance

Submitting a Project request is an invitation for assessment, not an automatic acceptance or promise to deliver. The agency may request clarification, technical information, feasibility checks or evidence of authority before proposing terms.

Agreement formation

A paid Project begins only when the parties accept the material scope and commercial terms through the applicable written confirmation or native Project workflow, together with any agreed funding prerequisite. A draft estimate or informal discussion alone is not a final binding specification.

Clear expectations

Before approval, the Project record should identify deliverables, exclusions, client inputs, review arrangements, ownership or licensing assumptions, relevant dependencies, fees and any applicable milestones.

SECTION 06 / 20Projects

Scope, changes and revisions

Change requests and approval

Agreed work

Implementation and completion are assessed against the approved Project scope. A requested feature, integration, design variation or other activity is not included solely because it relates to the same website.

Change control

Material changes may require a revised scope, price, schedule or separate Project approval. Neither party should assume that unapproved additions or informal messages replace signed or recorded commercial terms.

Revisions and corrections

Included revision rounds, defect correction arrangements and acceptance criteria should be specified in the Project agreement. A correction to an agreed deliverable is different from a request for new functionality. Unlimited changes are not implied.

SECTION 07 / 20Projects

Client cooperation and technical access

Materials, permissions and decisions

Customer inputs

Clients must provide information, feedback, content and approvals reasonably necessary for the agreed work. Delays, incorrect inputs or changing requirements can affect price, feasibility and delivery timing.

Authorized access

Provide access only to websites, accounts, databases, hosting and integrations that you are authorized to control. Where practical, use separate or temporary credentials and the least permissions necessary. Do not send bank passwords, unrelated personal secrets or complete payment card details as ordinary Project materials.

Backups and ownership control

The Client should retain appropriate control of domain ownership, hosting recovery, important accounts and independent backup options. For work with material risk, the approved scope should clarify backup verification, staging tests, rollback and responsibility for business continuity.

SECTION 08 / 20Payments

Project fees, funding and milestones

Pricing, checkout and payment records

Quoted fees

Fees are established for the specific approved Project and may vary with complexity, urgency, technical condition, integrations and third party costs. No price is binding merely because it appears in an informal example or preliminary discussion.

Payment instructions

Accepted Project terms and the payment interface determine how and when deposits, milestones or other amounts become payable. Clients should use authorized payment routes and review any taxes, currency conversion or payment provider charges disclosed before authorization.

Platform records

The site may use native Project payment statuses, funding steps, account balances or milestone controls depending on its configuration. A displayed balance is not a promise of a separately regulated escrow or trust arrangement. The actual provider and platform terms govern payment processing and release controls.

Expert remuneration

Where an Expert is engaged, compensation and withdrawal eligibility are governed by the approved professional assignment and relevant platform payment records; Client payment does not itself create an unrestricted right to withdraw funds.

SECTION 09 / 20Payments

Cancellations, refunds and disputes

Fair review and customer rights

Ending a Project

A Client may request cancellation, and the agency may review the request against the accepted scope, work completed, incurred or committed costs, milestones, payment status and applicable law. An unaccepted request can ordinarily be withdrawn without an obligation for work not approved.

Assessing refunds

Refund eligibility and amount are determined from the facts, the Project agreement, approved payment terms, work performed and any mandatory legal rights. A cancelled Project does not automatically produce either a full refund or a zero refund.

Credits and cash refunds

An internal account balance or Project credit is not automatically the same as a refund to the original payment method. If a cash refund is legally required or properly approved, its processing must follow an available lawful route and applicable provider requirements.

Dispute evidence

Raise concerns through the relevant Project record or Support Center and provide a concise description, agreed scope, delivery evidence and payment reference. A fair review should consider information from all relevant parties. Statutory remedies and eligible payment provider rights remain available where applicable.

SECTION 10 / 20Projects

Scheduling and technical dependencies

Timing and third party conditions

Timelines are scoped

Projected dates are based on information available when the parties agree the Project. Actual timing can depend on Client feedback, technical access, external approvals, hosting, APIs, third party vendors and complexity discovered during implementation.

Changes or delays

The parties should communicate material delays and agree adjustments where necessary. A stated timeline is not automatically a guarantee of third party uptime or uninterrupted access to external applications.

Dependencies

If an essential dependency is unavailable or unsuitable, the agency may propose an alternative, a change of scope or a lawful termination or resolution. Such changes should be recorded before materially different paid work proceeds.

SECTION 11 / 20Projects

Review, acceptance and handover

Quality checks and completion

Review against scope

The Client should review outputs within the agreed review period, where one exists, and identify specific discrepancies with the accepted requirements. The agency should have a reasonable opportunity to address valid in-scope issues under the Project terms.

Handover materials

The approved Project scope should specify which files, access details, configuration notes, training materials or credentials are handed over, and which recurring licenses, hosting obligations or maintenance arrangements remain with the Client.

After completion

Further enhancements, ongoing maintenance or new integrations are separate unless explicitly included. Completion, approval, milestone release and support coverage follow the agreed Project record and applicable legal rights.

SECTION 12 / 20Rights

Content, custom work and licensing

Copyright, GPL and external components

Client materials

Clients retain rights they already hold in their own trademarks, content, business information, customer data and supplied materials. By supplying these, the Client authorizes their limited use as reasonably necessary to perform the approved Project.

Custom deliverables

Ownership or licenses for new custom code, designs, files, documentation and other deliverables follow the applicable written Project agreement and payment conditions. These Terms do not promise blanket transfer of all third party or pre-existing intellectual property.

Open source and third parties

WordPress and many related components are distributed under open source licenses, including the GNU GPL. Themes, plugins, libraries, stock assets, fonts and APIs can have additional terms or obligations. Applicable licenses continue to govern those components.

Reused know how

General technical techniques, pre-existing tools and reusable methods are not exclusively transferred unless expressly agreed, while use of confidential Client information remains restricted as applicable.

SECTION 13 / 20Rights

Privacy, confidentiality and data handling

Project information and personal data

Privacy framework

Personal information handled through Esposearch.net is subject to the published Privacy Policy and applicable data protection requirements. The agency and Clients should clarify relevant controller, processor or other roles where a Project involves access to customer or staff information.

Confidential materials

Project briefs, website credentials, unreleased business information and supplied files should be used only for authorized assessment, delivery, administration and lawful record keeping. Confidentiality can also be governed by the written Project terms and Content Privacy Policy.

Sharing and retention

Limit data access to authorized people and tools reasonably needed for the engagement. Retention, deletion and legal disclosure obligations depend on the nature of the data, applicable law and the relevant privacy notices. Do not upload unnecessary sensitive personal information to ordinary Project discussions.

SECTION 14 / 20Rights

AI agents, automation and connected tools

Approvals, data boundaries and oversight

AI assisted delivery

Projects may include AI assisted content, automated workflows, external APIs and intelligent agents when expressly in scope. Actual functionality depends on approved tools, available integrations, technical feasibility and third party terms.

Human review

The Project should specify which outputs require human validation and which high impact actions require explicit authorization, including publishing, account changes, transactions and communications where appropriate.

Data and credentials

API keys, customer records and confidential data must be handled under agreed access and privacy measures. An automated recommendation, generated text or model output is not automatically verified or suitable for every business or regulated use.

SECTION 15 / 20Rights

Hosting, platforms and external providers

Dependencies outside agency control

Independent providers

WordPress projects may rely on hosting providers, registrars, DNS, payment gateways, plugins, themes, APIs, analytics systems and other external providers. Their availability, fees, licenses and policy changes are governed by their respective terms.

Purchases and licenses

Unless the Project agreement states otherwise, third party subscriptions and accounts remain under the Client’s control and expense. The parties should confirm who obtains licenses and what happens when a subscription expires.

Compatibility

The agency may configure a compatible integration but cannot guarantee that a separate provider will preserve a particular feature, API, ranking, uptime or pricing indefinitely.

SECTION 16 / 20Legal

Acceptable use and prohibited requests

Safety, legality and third party rights

Lawful instructions

Do not request or use Projects for fraud, credential theft, harmful malware, unauthorized system access, deception, infringement or activities that clearly breach applicable law or third party rights.

Respectful collaboration

Clients, Experts and Administrators must use professional communication and not misuse accounts, threaten others, harass staff, interfere with platform operations or conceal material conflicts of interest.

Right to decline

The agency may reject or pause clearly unlawful, abusive or unreasonably dangerous instructions. Where appropriate, the parties should discuss a lawful alternative or a fair termination and payment resolution under the actual Project terms.

SECTION 17 / 20Legal

Professional standards and limitations

What can and cannot be promised

Professional care

Esposearch aims to perform accepted Project work with reasonable professional care and attention to the agreed scope. Specific warranties, remediation periods and technical standards, where applicable, should be recorded in the Project agreement.

External outcomes

No general guarantee is made of search rankings, revenue, conversion rates, continuous availability, third party API behavior or immunity from security incidents. These outcomes can depend materially on external systems, customer decisions and conditions beyond the agency’s control.

Liability and protected rights

Responsibility for loss is assessed under the agreement, applicable law, causation and the circumstances. Nothing in these Terms excludes or restricts liability, remedies or consumer rights that cannot lawfully be excluded or restricted.

SECTION 18 / 20Legal

Suspension, termination and records

Accounts and unfinished work

Reasonable grounds

Accounts or Project activity may be restricted where necessary for serious security risk, nonpayment, suspected fraud, unlawful conduct or substantial breach. Appropriate notice and opportunity to respond should be provided where reasonably possible and legally required.

Consequences of termination

Ending access does not automatically resolve financial obligations, work already completed, confidentiality, intellectual property, dispute rights or necessary record retention. Applicable obligations should be settled against the Project and legal requirements.

Record preservation

The agency may retain appropriate Project communications, approvals, payment status, technical records and dispute materials when reasonably necessary for administration, security, accounting or lawful compliance, subject to applicable privacy obligations.

SECTION 19 / 20Legal

Complaints, governing law and dispute resolution

Where to raise a concern

Support first

For a Project concern, use the relevant authenticated Project record where available or contact the Support Center. Supply the relevant reference, agreed work and a short explanation of the remedy sought, without sending account passwords or other secrets.

Applicable law

These general Terms are governed by the laws of the Republic of Kenya to the extent permitted by applicable law and the actual transaction. Mandatory rights and rules that protect customers in other jurisdictions are not intended to be waived by this clause.

Other lawful options

The parties should attempt reasonable direct resolution before escalation, where appropriate. Nothing here prevents eligible payment provider processes, regulatory complaints or access to a court or other forum available under mandatory law.

SECTION 20 / 20Legal

Updates, interpretation and contact

Version, severability and official channels

Changes to these Terms

The agency may revise these Terms to reflect legal, technological or operating changes. Material updates should be presented and notified where legally required. A later revision does not automatically override an already agreed Project term or remove accrued legal rights.

Severability and waiver

If a provision is held unenforceable, the rest should continue to operate where legally possible. A failure to enforce a provision on one occasion does not automatically waive it for every future situation.

Questions and official contact

For clarification before approving a Project, visit the Support Center at esposearch.net/support/ or email admin@esposearch.net. You may also review the current Privacy Policy, Content Privacy Policy and Refunds Policy before you make a payment.

Where an agreed Project document describes a specific fee, deliverable, deadline, ownership arrangement or approval condition, check that document together with these Terms before making a payment or authorizing work.

Plain language help

Questions before a Project commitment?

These short answers explain common situations. The full clauses above and your accepted Project agreement provide the operative detail.

Visit Support Center
Is submitting a Project a contract?
No. A request is reviewed first. A paid engagement is created only when the applicable scope and commercial terms are accepted, together with any agreed funding prerequisite.
Can I contract directly with an Expert?
Esposearch is the client agency contact for approved Projects. Expert participation and communication follow the agency’s authorized workflow and any specific written Project conditions.
Are all Projects priced the same way?
No. Each Project is priced according to the approved requirements and the specific commercial terms. Milestones or deposits apply only when agreed and available through the configured workflow.
Do cancellation requests always produce a refund?
No automatic full refund or blanket refusal applies. Completed work, the agreement, relevant evidence and mandatory rights are considered.
Who owns a completed website?
Existing Client content remains with the Client. Ownership and licenses for custom deliverables follow the agreed Project scope, while WordPress and other third party components retain their applicable licenses.
Can I send administrator passwords through chat?
Avoid sharing master passwords or unrelated secrets through ordinary chat. Agree on restricted or temporary access and an appropriate secure handover method.
Are AI workflows allowed to publish or act automatically?
Only within the permissions, limits and approval requirements agreed for the Project. High impact actions may require human review.
How do I raise a payment or delivery concern?
Use the relevant Project record or the Support Center. Include a Project reference and clear description, without exposing credentials or unnecessary personal information.
Supporting information

Use these pages when you need the rules for personal data, confidential content, refunds or starting a WordPress Project.

Questions about your rights or Project?

Clarify important terms before you commit.

Review scope, payment, ownership, confidentiality or cancellation questions through the Support Center before approving a Project. We aim to make Professional WordPress Solutions easier to commission and understand.