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

Cookie Policy

Website transparency · Professional WordPress Solutions

Cookies Policy.Understand your browser choices.

Learn how cookies and similar browser technologies can support website sessions, security, measurement and connected tools. Search our Cookies Policy for clear guidance on your choices while using Professional WordPress Solutions and managed Projects.

Draft prepared 3 November 2026Applies to Esposearch.netProjects only
Cookies at a glance

Clear information for every website visitor.

Whether you are exploring WordPress solutions or working on an accepted Project, cookie information should be easy to find, accurate and relevant to the features you use.

For visitors

Learn which types of cookies may support a visit and how optional technologies should be explained.

Explore this topic

For Clients

Understand account sessions, Project actions and any payment provider technologies involved.

Explore this topic

For Experts

Learn how authorized sign in and technical safeguards can support qualified expert participation.

Explore this topic
Important distinction: this is a searchable policy, not a working consent dashboard. Accepting or rejecting optional cookies must happen through the configured website consent mechanism where one is required. A final cookie inventory must be confirmed against the live website before this draft is approved.
Four practical areas

Understand purpose before making a choice.

Not all cookies do the same thing. Explore the common purposes below and read the full policy for the important details and limitations.

Essential operation

Certain session and security technologies may support requested website features.

Read more

Optional measurement

Analytics and other optional tracking require the correct classification and choice.

Read more

Informed decisions

Where consent is required, people need understandable choices before optional tracking begins.

Read more

Review and change

Visitors should be able to revisit applicable preferences and understand browser controls.

Read more
The full Cookies Policy

Explore 28 searchable cookie topics.

Use the contents to jump to a policy section or search the questions that matter to you. This draft does not claim to provide a verified cookie name inventory or to manage browser consent.

SECTION 01 / 28Overview

Purpose and application

Website technology and the reason for this notice

About this website

Esposearch.net provides Professional WordPress Solutions through a professionally managed agency using Projects. This policy explains cookies and comparable browser technologies that may be involved when someone visits, signs in, requests support or manages an approved Project.

Who operates the website

Esposearch.net is operated by Esposearch Limited Company, registered under the laws of the Republic of Kenya. The policy concerns the Esposearch.net website. Other websites, including separately operated learning platforms, may have their own notices.

Important scope distinction

This page explains categories and choices. It does not operate the website consent tool, change cookie settings, or create or delete tracking records on its own.

SECTION 02 / 28Overview

What cookies are

Small pieces of information saved by a browser

Basic explanation

A cookie is a small value that a website or an authorized third party can ask a browser to store and send back on later requests. Cookies may help maintain a sign in, remember a preference or support measurement.

Session and persistent cookies

Some cookies usually end when a browser session closes; others last for a specified duration or until removed. Actual expiry periods depend on the specific cookie and its configured provider.

Cookies are not automatically harmless

A cookie may contain an identifier that can relate to an individual or online activity. Privacy obligations depend on purpose, technology, location and applicable law.

SECTION 03 / 28Overview

Other tracking and storage technologies

Local storage, pixels and related technical mechanisms

Beyond ordinary cookies

Websites and embedded tools can use local storage, session storage, pixel tags, script identifiers, server logs, device information and similar techniques. The legal rules can apply beyond files literally named cookies.

Device and browser information

Some systems may process browser type, language, approximate network location, IP address, referral information or device characteristics. These details depend on installed technologies and their settings.

No blanket tracking claim

The presence of a plugin does not prove every optional feature is active. An accurate published inventory requires review of the live website, its scripts and the consent configuration.

SECTION 04 / 28Essential

Essential website operation

Cookies that support requested core functions

What may be necessary

Authentication, session continuity, fraud prevention, request routing and certain security checks may require cookies or equivalent technology to operate a feature someone has requested.

Essential is a narrow category

A tool is not essential merely because it is helpful to the business. Analytics, marketing and convenience features must be classified on their actual purpose and applicable rules.

User experience

Rejecting optional cookies should not prevent essential website functions. Certain features may not operate as intended if a person also blocks cookies genuinely required for sign in or security.

SECTION 05 / 28Essential

Client sign in and account sessions

Account authentication and session continuity

Account functions

WordPress and WorkReap account workflows may rely on session or authentication cookies to recognize a signed in Client, Expert or Administrator and maintain the relevant login state.

Role permissions

A cookie does not itself grant a user authority. Server controlled authorization and site configuration determine what a Client, Expert or Administrator is permitted to access.

Safety guidance

Sign out on shared devices and protect account credentials. Blocking necessary session cookies may cause repeated login prompts or prevent account dashboards from opening.

SECTION 06 / 28Essential

Project access and transaction integrity

Keeping authorized Project actions connected

Project workflow

Where enabled, cookies or session data may preserve a client session during Project preparation, milestone review, account messaging or authorized payment steps.

Payment processor technologies

A payment provider may set its own risk, fraud prevention or authentication cookies when its payment interface is used. The exact provider, purposes and lifetimes must be verified before publication.

One managed Project pathway

The agency operates with custom Projects. Account sessions and payments, where relevant, are described in relation to an approved Project rather than unrelated purchase flows.

SECTION 07 / 28Essential

Security, anti abuse and site reliability

Protecting accounts and keeping site functions reliable

Protection measures

Depending on configuration, security tools can use device or request identifiers for login protection, bot detection, session integrity, rate limiting or similar safeguards.

Infrastructure and caching

Hosting, content delivery or load balancing tools can use narrowly necessary cookies when supporting requested website access.

Classification requires inspection

A label such as security or performance does not automatically make every associated tracker strictly necessary. Each implementation must be evaluated.

SECTION 08 / 28Essential

Remembered settings and convenience

Distinguishing necessary preferences from optional features

Preference cookies

A website may save language, display or accessibility choices. Whether consent is required depends on what is remembered, why it is used and the laws relevant to the visitor.

Privacy choices

A consent management system may need to remember a visitor’s preference so it does not repeatedly ask for the same selection.

No false control

Buttons or topic filters on this page are informational navigation only. They are not cookie consent controls and do not change a browser’s actual consent state.

SECTION 09 / 28Optional

Analytics and measurement technologies

Understanding visits and website performance

Potential uses

If enabled, analytics technologies may measure page visits, referral sources, navigation patterns, errors and interactions so the agency can evaluate the clarity of its WordPress information.

Consent and lawful basis

Analytics cookies are not automatically essential. Where consent is required, they should not be activated before the visitor makes a valid affirmative choice.

Avoid promising a specific product

The actual analytics provider, configuration, data sharing, identifiers and cookie lifetime require checking. A familiar plugin name alone is not a reliable cookie inventory.

SECTION 10 / 28Optional

Functional enhancements and embedded tools

Extra experiences beyond the core website

Possible features

Optional functionality may include enhanced chat, language tools, form assistance, media players, accessibility widgets or remembered interface preferences.

Different providers

Some integrated features operate only when opened, while others may load third party resources immediately. Each integration should be assessed according to actual behavior.

Your choice

Where the feature relies on nonessential storage, refusal should be possible under applicable consent requirements, and the consequences for that extra feature should be explained.

SECTION 11 / 28Optional

Marketing, personalization and advertising

Tracking intended to personalize or measure promotional content

What may be involved

Marketing technologies can attribute campaign visits, assess conversions, build audiences or personalize offers if a site has enabled them.

No assumption of activation

This policy does not claim that Esposearch operates advertising pixels, behavioral profiles or remarketing cookies. Such claims must reflect the actual website audit.

Consent choices

Where relevant law requires consent, marketing tracking should remain off until the visitor positively chooses it, and withdrawal should be possible.

SECTION 12 / 28Providers

Live chat and customer support

Third party support widgets and conversations

Live support

A live chat widget can use browser storage to maintain an active conversation, remember a session or help support staff reply. Storage may be provided by the chat supplier rather than WordPress.

Third party policies

Before publishing a final cookie list, review which chat system is actually installed, when its scripts load, which identifiers it sets and whether any optional elements require prior consent.

Safer communication

Use the Support Center for account or Project questions. Do not place passwords, bank credentials or unnecessary personal records in ordinary chat messages.

SECTION 13 / 28Providers

External media, fonts and embedded content

Connected content may involve separate providers

Embedded content

Videos, maps, social media panels or remotely hosted assets can contact outside servers when the content loads. Some of these providers may also set cookies.

Fonts and visual assets

A font request or image request does not prove a cookie is set. Nevertheless, third party requests and associated data processing should be checked as part of the privacy audit.

Display alternatives

Where technically feasible and required, optional content can be withheld until choice is made or presented with an alternative way to access it.

SECTION 14 / 28Providers

Third party tools and integrations

Separating first party from external tools

First party and third party

A first party cookie is generally set in the context of the website being visited. A third party cookie or related request may arise from a separate domain, embedded interface or processing provider.

Installed WordPress components

WorkReap, WordPress, WooCommerce, security plugins, performance tools and other components may each contribute browser technology depending on their active configuration.

No invented provider list

The final published inventory must name the technologies actually used and disclose relevant providers rather than treating examples as confirmed installations.

SECTION 15 / 28Providers

Payments and financial verification

Payment systems may use verification and fraud safeguards

When relevant

When an accepted Project uses a configured payment provider, that provider may implement cookies for secure processing, authentication, risk evaluation or checkout continuity.

Provider terms

The actual payment gateway and provider privacy or cookie notice should be linked after verifying which integrations operate on the live site.

Project basis

Submitting a Project does not necessarily create a purchase. Payment and milestone obligations are determined by the accepted Project terms and active payment system.

SECTION 16 / 28Providers

Training websites and external destinations

Following links to a separate website

Other websites

A visit to an external learning site or outside application may expose the visitor to cookies governed by that destination and its own privacy information.

Separate contexts

Links from Esposearch.net to Esposearch Courses or external providers do not automatically establish that those destinations set cookies on Esposearch.net.

Before leaving

Visitors should review the applicable privacy and cookie notices on any separate site.

SECTION 18 / 28Choices

First visit and cookie banner

How a consent interface should present choices

Where needed

A correctly configured consent banner or settings panel should appear before nonessential scripts run for visitors who must consent.

What it should explain

The interface should describe purposes, categories and how to access more detail. The final cookie inventory should disclose the relevant providers and lifetimes.

Technical implementation

This Content HTML block provides information and searchable policy sections. It does not create a functioning site wide consent mechanism. Configure that separately using a compatible consent management solution.

SECTION 19 / 28Choices

Change or withdraw cookie preferences

Revisit consent after your first decision

Changing your mind

When optional cookie consent is used, visitors should be able to change or withdraw that choice through the active website consent interface or other clearly described route.

Availability must be verified

Do not advertise a working Preferences button unless it is actually connected to the installed consent manager and tested with optional trackers blocked when declined.

Ask for assistance

If you cannot find the consent interface, contact the Support Center. You can also review browser controls, although changing your browser is not a substitute for a website meeting its own obligations.

SECTION 20 / 28Choices

Browser controls and device settings

Manage cookies in your own browser

Browser tools

Most browsers let you inspect, block, remove or limit site cookies and adjust some tracking protections. Exact menu names vary by browser and version.

Practical effects

Deleting cookies can sign you out, clear remembered preferences or affect a current authenticated Project session.

Private browsing

Private browsing changes how a browser stores data on a device, but does not make online activity invisible to the visited site or all external providers.

SECTION 21 / 28Choices

Cookie inventory and transparency

A verified list is required before final legal publication

What to record

The operational cookie register should record each cookie or comparable technology’s name, actual provider, purpose, category, first or third party context, persistence or expiry, and relevant consent behavior.

Audit live conditions

Check anonymous visits, fresh browser sessions, accepted optional categories, rejected categories, Client login, Expert login, Project actions and any available payment experience.

Current status

This draft intentionally does not claim a completed live cookie scan or enumerate unverified cookie names. The actual register must be attached or incorporated before final publication as applicable.

SECTION 22 / 28Choices

Cookie lifetimes and data retention

Session expiry is not the same as business retention

Cookie expiry

Browser cookies can expire at session end, a declared timestamp or manual deletion. The correct duration is determined by each actual cookie.

Server records

A browser cookie may disappear while separate server logs, invoices, security evidence or legal records remain under the applicable Privacy Policy and retention rules.

Review regularly

Reassess the inventory after major plugin changes, hosting changes, new chat or payment tools, analytics changes or new marketing integrations.

SECTION 23 / 28Rights

International providers and transfers

Data may cross borders through configured technology

Supplier infrastructure

External hosting, analytics, security, chat and payment providers may process data in different countries depending on the account, vendor and technical route.

Check actual flows

Do not assume a transfer occurs merely because a vendor offers international infrastructure. Confirm where data is processed, applicable safeguards and any required disclosures.

Related information

Read the Privacy Policy for data handling, recipients, international transfers and individual rights.

SECTION 24 / 28Rights

Personal information and privacy rights

Privacy protections may apply to online identifiers

Identifiers

Cookie IDs, IP addresses or tracking events can be personal information when they relate to identifiable individuals, depending on the circumstances.

Available rights

Applicable law may provide rights to information, access, correction, objection, deletion, withdrawal or complaint, subject to relevant conditions and exceptions.

Submit a request

Write to admin@esposearch.net with the general nature of your concern. Do not include your password, full payment card information or unnecessary identification documents in the first message.

SECTION 25 / 28Rights

Children and vulnerable visitors

Additional care with profiling and tracking

Appropriate safeguards

If a feature is directed to children or the operator learns it involves children’s data, stricter obligations may apply to collection, profiling and consent.

Agency audience

Esposearch.net is intended for people who can legitimately use its professional website and account functions. This statement does not itself establish an age verification system.

Contact

Raise concerns about children’s information using the published privacy contact.

SECTION 26 / 28Rights

Security and responsible technical operation

Protecting browser identifiers and account activity

Security design

Where suitable, cookie implementations should use secure transport, restricted scope, appropriate lifetimes and protective attributes such as Secure, HttpOnly or SameSite.

Limits

A cookie policy does not replace technical hardening, access controls, WordPress updates or incident response. The actual implementation must be tested.

Reporting

Contact the Support Center if you suspect an account issue or unsafe session behavior. Avoid sharing secret credentials in a support message.

SECTION 27 / 28Rights

Updates, checks and related policies

Keeping disclosures aligned with the live website

When disclosures change

This policy may need updating after an analytics rollout, consent interface change, new hosting arrangement, additional payment method or relevant legal update.

Related documents

The Privacy Policy covers personal information, the Content Privacy Policy addresses entrusted Project content, and the Terms and Conditions define general contractual matters.

Effective date

The final publication date should reflect actual approval, not merely the date this technical draft was prepared.

SECTION 28 / 28Rights

Contact and support for cookie questions

Ask about tracking, access or consent

Privacy contact

For a cookie, consent or personal data concern, email admin@esposearch.net with the page visited, approximate date and nature of the issue.

Project support

For questions relating to an account or approved WordPress Project, use the Support Center and mention only the necessary Project reference.

Regulatory rights

A visitor may also have access to relevant regulatory complaint channels under applicable privacy law. The agency should respond according to the rights and rules that apply.

Frequently asked questions

Helpful answers to common cookie questions.

Clear up the difference between necessary browser functions, optional technologies, and how consent choices should work.

Visit Support Center

Are all cookies required for Esposearch.net?
No. A browser may encounter technologies necessary for a requested feature and other technologies that are optional. The actual categories require a live audit and the appropriate consent implementation.
Can I decline analytics or marketing cookies?
Where these are used and the applicable law requires consent, you should have a genuine option to refuse before the nonessential technology runs. This page does not itself record your choice.
Does the search box track what I type?
The policy search in this Custom HTML block matches words against the policy sections in your browser. It does not send search terms to a backend or third party.
Will rejecting cookies stop my Client account from working?
Declining optional cookies should not disable essential features. Blocking all cookies at browser level can interfere with login sessions or security measures required by certain account functions.
How can I withdraw my consent?
Use the website cookie preference interface where available and correctly configured. If you cannot find it, contact Support. Browser controls can also help remove saved cookies.
Does an embedded video or chat widget set cookies?
It may, depending on the actual provider and script behavior. The live site must be inspected to confirm whether storage is created before or after interaction and whether consent is required.
Can I see an exact list of the cookies used?
A final policy should disclose a verified inventory with cookie names, providers, purposes and lifetimes. This draft does not invent that list because the live inventory has not been established.
Where can I ask a question about privacy or cookies?
Contact admin@esposearch.net or the Support Center with the general issue and relevant page. Do not include passwords or confidential payment information in the initial enquiry.
Related documents

Cookies are one part of responsible website operation. Review the related rules and guidance when you need more detail.

Professional WordPress Solutions

Clear policies. Confident project decisions.

Understand the technology behind your website experience and move forward with the WordPress Project that matters to your business. Start with a clear scope and professionally coordinated expertise.