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

Privacy Policy

Privacy and Trust · Professional WordPress Solutions

Privacy Policy.Your data. Your choices.

Understand how personal information may be used when you explore WordPress solutions, open a Client account, participate as an Expert or work on a professionally managed Project. Find the answers you need, learn about your choices and reach our privacy contact easily.

Draft review date · 3 November 2026Esposearch.netProjects only
Privacy at a glance

A clearer approach to handling personal information.

We organize privacy responsibilities around the work people actually do on this website. Each activity has its own purpose, access needs and applicable rights.

For Clients

Understand registration, Project briefs, payment records and how customer website information should be handled.

Review this topic

For Experts

See how professional applications, eligibility assessments and assigned Project information are considered.

Review this topic

For everyone

Learn about website technology, personal data rights, security and the privacy contact.

Review this topic
Privacy and Content Privacy are not identical. This notice addresses personal information. The Content Privacy Policy focuses on files, materials and technical access entrusted for WordPress Projects. This website page does not itself configure cookie consent, collect privacy requests or change any account settings.
Four practical principles

Privacy that supports professional Project delivery.

Professional WordPress Solutions should make clear why information is needed, who can use it and how requests are handled.

Purpose first

Gather information to understand requirements, maintain accounts and meet genuine Project obligations.

Clear reasons

Limited access

Keep Client, Expert and Administrator permissions appropriate to their functions.

Defined responsibilities

Secure handling

Consider account security, safe technical access and responsible sharing.

Risk based safeguards

Individual choices

Explain access, corrections, objections and other rights where they apply.

Practical contact routes
The full privacy notice

Explore 22 clearly organized privacy topics.

Read everything or jump straight to the information most relevant to your account, Project or privacy request. Our searchable index works in the browser without sending your search text to a server.

SECTION 01 / 22Overview

Who operates the website and how to contact us

Controller identity and privacy contact

Website operator

Esposearch.net is operated by Esposearch Limited Company, registered under the laws of the Republic of Kenya. This notice explains how personal information may be handled when people visit the website, request Professional WordPress Solutions, use accounts or participate in agency Projects.

Privacy contact

Send privacy questions, requests or concerns to admin@esposearch.net. Please include enough information to identify the relevant account or Project, but do not send passwords, payment credentials or unrelated sensitive records by ordinary email.

Related documents

This Policy focuses on information about identifiable individuals. The Content Privacy Policy explains how client supplied website files and confidential materials are handled. The Terms and Conditions and Cookies Policy address related contractual and website technology matters.

SECTION 02 / 22Overview

When this policy applies and who controls data

Visitors, clients, experts and data roles

Who this notice covers

This notice covers ordinary website visitors, registered Clients, applicants and approved Experts, authorized Administrators, and individuals whose details appear in agency enquiries or Project records. The privacy terms of Esposearch.courses and external providers may apply separately.

Agency processing

For account management, website operation, commercial communication, payment records and lawful administration, Esposearch generally determines the purposes and means of using relevant personal data and may act as a data controller.

Customer website information

When a Client instructs the agency to work on a website containing customer or employee information, the Client may remain the controller and Esposearch or authorized contributors may process data under instructions. The actual relationship and any required data processing agreement must be defined for the Project.

SECTION 03 / 22Overview

Personal information that may be involved

Contact details, profiles and activity

Information you provide

Depending on the activity, details may include your name, business name, email address, username, role, professional background, Project description, uploaded files, invoices, support requests and messages. Only information relevant to the chosen activity should be requested.

Expert and administrator records

Expert eligibility assessments may involve professional skills, portfolio evidence, training completion and assignment history. Authorized Administrators may have role permissions and audit records needed to run the agency and protect the platform.

Other people in Project materials

A Client website or Project brief may contain personal information about visitors, customers, members or staff. Such information must be handled only where authorized and necessary, and it should not be made public through ordinary Project descriptions.

SECTION 04 / 22Overview

Where information comes from

Direct, technical and authorized sources

Directly from individuals

Information can come from registration, Project enquiries, expert applications, submitted work, email, support channels and other actions you choose to take.

Generated in normal operation

WordPress and connected components may create authentication, transaction, activity, technical error, login security and administrative records. The details depend on what is actually enabled.

Relevant third parties

Subject to the applicable notices and permissions, information may be received from authorized Client representatives, payment processors, messaging providers and websites involved in approved Projects.

SECTION 05 / 22Overview

Why information is used and on what basis

Purposes and legal grounds

Delivery and account purposes

Information may be used to respond to enquiries, assess Project requirements, prepare and administer agreed work, authenticate accounts, coordinate Experts and provide support. Depending on the circumstances, applicable grounds may include steps before a contract or performance of an agreement.

Compliance and protection

Relevant records may be retained or processed to satisfy legal obligations, protect accounts, investigate security incidents, prevent misuse, maintain accurate accounting or resolve legitimate disputes. Any reliance on legitimate interests must be appropriately assessed where that basis applies.

Optional activity

Where consent is required for a nonessential tracker, marketing message or other processing, it should be requested before the relevant activity. Consent can be withdrawn for future processing without automatically affecting other lawful processing of necessary Project records.

SECTION 06 / 22Accounts

Client accounts and authentication

Registration, access and recovery

Account registration

A Client account may require a name, contact information, username or other details needed to register, sign in and use the permitted Project workflow. Additional information may be needed to verify authority to act for a business.

Login protection

Authentication records such as sign in attempts, IP information and session data may be used for fraud prevention, access control, account recovery and troubleshooting. Exact security tools depend on the installed configuration.

Your choices

Keep registration details accurate, protect your password and report suspected unauthorized use. Request account correction or eligible deletion using the privacy contact, subject to lawful retention and active Project obligations.

SECTION 07 / 22Accounts

Expert applications and professional records

Vetting, training and assignments

Application information

Professionals seeking Expert status may provide work samples, technical specializations, previous experience, training evidence and responses to assessment requests.

Assessment purposes

The agency may review relevant information to determine eligibility, suitable permissions, training needs, assignment suitability and ongoing quality standards. Registration or course participation does not guarantee professional approval or paid Projects.

Visibility and limitations

Sensitive verification records should not be intentionally published as marketing or public portfolio content. Any professional information displayed publicly must match the actual account permissions and relevant notices.

SECTION 08 / 22Accounts

Administrator permissions and account integrity

Authorized administration and access controls

Administrative records

Authorized Administrators may review necessary account, Project and transaction information for delivery coordination, support, security, compliance and dispute handling.

Role based access

Clients, Experts and Administrators have different permissions. Access should follow a legitimate role and Project need rather than be granted merely because an account exists.

System audit information

Administrative changes, access events and moderation decisions may generate logs to support accountability, lawful oversight and incident investigations. These records should be retained only as long as justified.

SECTION 09 / 22Projects

Project briefs, files and communications

Scope and delivery records

Project information

A Project can contain the Client brief, budget, contact person, approved specifications, technical discussion, milestone status, deliverables, review comments and completion documentation.

Limited sharing

Information relevant to an approved assignment may be accessed by authorized agency staff or qualified Experts where necessary. Client Projects are coordinated through the agency rather than public direct contracting between unrelated providers and customers.

Private details in public fields

Clients should avoid posting passwords, live API keys, complete customer exports or other sensitive data in potentially visible fields. Share required access through a suitably restricted method agreed for the Project.

SECTION 10 / 22Projects

Personal data on client websites

Client systems and processing instructions

Authorized purpose

A WordPress Project may require limited access to WooCommerce customers, site members, bookings, support tickets or other records. This is not a general permission to repurpose or export information outside the agreed work.

Client responsibilities

Clients should identify relevant privacy obligations, provide appropriate instructions and ensure they are authorized to provide website access. Where needed, the parties should agree a data processing agreement, permitted subprocessors, security measures and deletion or return procedures.

Safe implementation

Use staging, data minimization, masked test data and temporary access wherever practical. Any live data use must follow an appropriate purpose, agreed safeguards and applicable laws.

SECTION 11 / 22Projects

Payments, billing and transaction records

Invoices, payments and reconciliations

Transaction information

Payment and accounting processes may involve billing details, invoice identifiers, payment amounts, currency, dates, Project references, funding status, refund requests or payout records where applicable to authorized Expert arrangements.

Payment processors

Approved payment providers may process payment credentials and transaction information under their own policies and legal requirements. The agency should not request full card numbers or banking passwords in ordinary Project messages.

Accounting and disputes

Some billing and payment information may need to be retained for lawful recordkeeping, taxation, reconciliation, fraud prevention or dispute resolution even when an account is closed.

SECTION 12 / 22Projects

Support email, chat and contact channels

Communication and customer care

Contact information

When you use website support, live chat, WhatsApp or email, the information processed may include your contact details, message content, request date and any relevant Project reference.

External messaging tools

A communication provider can separately handle message delivery, account metadata, device identifiers and cookies under its own terms. Avoid submitting sensitive website credentials or confidential datasets in open conversations.

Operational use

Support records can help resolve enquiries, document instructions, follow up on requests and review legitimate complaints. Their retention should follow an appropriate business and legal schedule.

SECTION 13 / 22Technology

Cookies, sessions and privacy preferences

Essential and optional technologies

Necessary website functions

WordPress, WorkReap, authentication components and security systems may use necessary cookies or local storage for login, sessions, account settings and website protection.

Optional cookies

Analytics, advertising, embedded media or other nonessential tools may use additional identifiers if activated. Applicable consent or preferences must be implemented according to the actual installed technologies and the visitor’s jurisdiction.

Your controls

Use any implemented cookie preferences tool and available browser settings to manage optional tracking. Blocking necessary cookies may prevent some account or Project features from functioning. Review the separate Cookies Policy for a verified inventory.

SECTION 14 / 22Technology

Analytics, security and website diagnostics

Logs, measurement and protection

Technical diagnostics

Hosting, caching, monitoring and security systems may collect IP addresses, user agents, error information, timestamps and activity indicators to keep the website running and investigate suspicious activity.

Measurement tools

Where configured, analytics and search performance tools may help evaluate site usage and improvements. Data categories, providers, cookies and retention must be checked against the actual implementation rather than assumed from a general policy template.

Marketing separation

Promotional campaigns and tracking are not necessarily required to deliver a WordPress Project. Any optional marketing communication or tracking must use a suitable lawful basis and offer applicable preference or unsubscribe mechanisms.

SECTION 15 / 22Technology

AI agents, automation and connected tools

Data boundaries and human review

Approved use only

Some Professional WordPress Solutions involve AI assistants, workflow automation or external APIs. Processing of personal data through such tools should be defined in the Project scope, with necessary notices, instructions and permissions.

Controlled access

When designing automations, appropriate practices include limited API permissions, restricted data fields, approval points for material actions, testing and error handling. Confidential information should not be supplied to external AI systems without appropriate authorization and safeguards.

Automated decisions

A technical automation or model output must not be assumed accurate or suitable for consequential decisions without review. Applicable rights relating to automated decisions and profiling should be assessed for any relevant deployment.

SECTION 16 / 22Technology

Who may receive personal information

Providers, professionals and legal disclosures

Agency team and approved Experts

Authorized personnel and assigned Experts may receive only the account or Project information reasonably needed for their approved responsibilities, subject to appropriate confidentiality and permission controls.

External providers

Depending on the installed systems, relevant recipients may include hosting, payment, email, live chat, security, backup, analytics and integration providers. Their actual identities and processing terms must be verified before this policy is published.

Other disclosures

Information may be shared when legally required, needed to protect legitimate rights or appropriate to investigate fraud or safety incidents, subject to applicable law and proportionality.

SECTION 17 / 22Technology

International processing and transfers

Cross border access and safeguards

Global participation

Clients and technical contributors may be located in different countries, and some hosting, communications, payment or other providers may process information outside Kenya.

Transfer controls

Where law requires, the agency must assess the destination, applicable safeguards, contractual protections or other lawful transfer mechanism before making a restricted international transfer.

Specific Project requirements

If a Client Project includes personal data subject to geographic or contractual restrictions, those requirements should be identified during scoping and reflected in instructions to authorized processors.

SECTION 18 / 22Rights

Security safeguards and incident handling

Protection, reporting and recovery

Appropriate safeguards

The agency should apply risk appropriate measures such as role based access, credential protection, software maintenance, backup strategies, secure communication and review of technical permissions. No internet system can guarantee absolute security.

Suspected incidents

Report suspected misuse of account details or a Project data incident through the Privacy Contact or Support Center. Provide relevant context without including unnecessary sensitive material.

Incident response

Incidents should be assessed, documented, contained and notified to affected parties or relevant authorities where required by applicable law and the agency’s actual legal role.

SECTION 19 / 22Rights

How long information is retained

Retention, archive and deletion

Purpose based retention

Information should be kept only for the time justified by the relevant purpose, agreement, regulatory requirement, security need or legitimate dispute. Different records may require different retention periods.

Examples of retention drivers

Account details may be maintained while the account is active; Project files and communications may be needed for handover and dispute periods; transaction records may be required for accounting and legal duties; security logs may have shorter technical retention periods.

Deletion requests

Eligible deletion or anonymization requests should be considered against ongoing Project duties, lawful retention, technical backups and third party obligations. A verified retention schedule must be adopted before public release of this notice.

SECTION 20 / 22Rights

Your privacy rights and choices

Access, correction, objection and other rights

Making a request

Depending on the law that applies, you may be entitled to information about processing, access to your data, correction, objection, deletion, consent withdrawal, and in some jurisdictions restriction or portability. Requests can be sent to admin@esposearch.net.

Identity and response

The agency may reasonably verify identity or authority before responding to a sensitive request. The applicable legal timeframe, exceptions and permitted remedies depend on the jurisdiction and circumstances.

Marketing and consent

You may object to qualifying direct marketing and withdraw an optional consent where that basis applies. This may not require deletion of independent records needed to provide an agreed Project or meet a lawful duty.

SECTION 21 / 22Rights

Children and sensitive information

Special care and minimization

Intended use

Esposearch.net is designed primarily for professional website owners, adult professionals and authorized organizational representatives. It is not designed to solicit personal information from children as a standalone consumer offering.

Sensitive records

Do not submit health details, identity documents, full payment credentials or other sensitive records unless specifically requested through an appropriate, secure and lawful process.

Accidental collection

If you believe a child’s information or unrelated sensitive data has been submitted inappropriately, contact us so the situation can be assessed and handled under applicable legal requirements.

SECTION 22 / 22Rights

Questions, complaints and policy updates

Privacy contact and ongoing transparency

Get assistance

Email admin@esposearch.net with your privacy concern, account identifier or relevant Project reference. You can also visit the Support Center for general guidance. Do not send passwords or secret tokens in your request.

Regulator and remedies

Where applicable you may have the right to complain to the Office of the Data Protection Commissioner in Kenya or an appropriate regulator in your own jurisdiction. You can also seek other remedies available under relevant law.

Updates and publication

This notice should be reviewed after material changes to payment providers, cookies, analytics, AI integrations, data sharing or account workflows. The published effective date must reflect the final approved version; material changes should be communicated where legally required.

Answers and guidance

Common privacy questions, answered clearly.

Review practical questions about personal information, Project privacy and available choices.

Visit Support Center
How can I ask for a copy of my account information?
Contact admin@esposearch.net with the email linked to your account and the kind of information you want. We may need a reasonable identity check before sharing private records.
Can I ask for my account and Project records to be deleted?
You may request eligible deletion. Some records might need to remain for active Projects, financial reporting, legal duties, security or disputes. We will assess the applicable circumstances.
Do you share my Project brief with every Expert?
Project information should be accessed according to actual WorkReap visibility settings and agency approval. Sensitive information should not be posted in public fields. Authorized Experts should receive only relevant information.
Does the policy cover customer data inside my own WordPress website?
The agency may handle that information only when an authorized Project requires it. The Client may remain responsible as data controller. Additional written data processing instructions may be needed.
Can I control cookies and analytics?
You can use available browser settings and any implemented cookie preference controls. A separate audit of installed tools is needed to confirm which optional identifiers are active and what choices the live website offers.
Will my confidential information be sent to AI tools automatically?
No such blanket practice should be assumed. Any AI processing involving personal or confidential information should be covered by suitable instructions, permissions and safeguards for the specific Project.
Where do I report a suspected privacy incident?
Contact admin@esposearch.net or the Support Center promptly. Describe what happened and which account or Project may be affected, but do not include unnecessary passwords or secret access keys.
Is this Privacy Policy the same as the Content Privacy Policy?
No. This Privacy Policy explains personal information and data rights. Content Privacy focuses on website materials, project files, confidential assets and technical access shared for approved work.
Privacy questions

Need help understanding your data rights?

Contact us about personal information, a Project privacy concern or a request relating to your account. For a new WordPress requirement, the managed Project process can help you agree suitable privacy safeguards before work begins.