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

Content Privacy

Confidentiality and Project protection · Professional WordPress Solutions

Content Privacy Policy.Your content. Protected by purpose.

Discover how website files, business information, technical credentials and confidential Project materials should be handled when you commission Professional WordPress Solutions. Search any topic, understand your responsibilities, and request clarity before sharing sensitive information.

Draft prepared 3 November 2026Managed WordPress ProjectsClient and Expert responsibilities
Content privacy at a glance

Clear boundaries for the content entrusted to a Project.

A professionally coordinated WordPress Project may require confidential materials and technical access. The goal is to use the right information for the authorized work and avoid unnecessary exposure.

For Clients

Understand what you may share, how ownership is treated and how to request eligible return or removal.

Review the policy

For Experts

Understand the limits of assigned access, confidentiality, approved tools and agency supervision.

Review the policy

For everyone

Learn about safe sharing, personal information, incidents and support routes.

Review the policy
Four practical principles

Confidence starts with responsible handling.

Strong Project delivery requires purposeful access, suitable safeguards and appropriate control of what happens after work is complete.

Customer control

Sharing content for a Project does not itself transfer ownership or unrelated use rights.

Ownership remains defined
Minimum necessary access

Only approved people and tools should receive the information reasonably needed for the work.

Permissions follow purpose
Responsible technical work

Backups, staging, vendor selection and automation require risk aware decisions.

Scope before access
Clear completion

Handover, retention, credentials and eligible deletion should be considered at the end of work.

No unnecessary lingering access
Full content protection policy

Explore 34 searchable policy sections.

Browse the table of contents or use the search above to find the relevant terms on access, confidentiality, third party tools, AI, retention and support.

SECTION 01 / 34Foundations

Purpose and application

The content and work covered by this policy

What this policy addresses

This Content Privacy Policy explains the standards for handling nonpublic files, website content, technical credentials, datasets, communications and other materials entrusted for Professional WordPress Solutions. It applies to requirements assessment, accepted Projects, relevant support and authorized follow up work.

Relationship with other documents

The Privacy Policy addresses information relating to identifiable individuals. The Terms and Conditions address the contract and the applicable Project agreement defines the precise scope. Content may include personal data, so more than one document may apply.

Company identity

Esposearch.net is operated by Esposearch Limited Company, registered under the laws of the Republic of Kenya. This page does not replace a tailored nondisclosure agreement or data processing agreement where required.

SECTION 02 / 34Foundations

What counts as Customer Content

Website material, business files and technical information

Content categories

Customer Content includes text, images, brand assets, media, documents, source code, custom configurations, design files, websites, plugin settings, databases, product records, private reports, API configurations, approved AI materials and Project messages that a Client controls or is authorized to provide.

Sensitive technical information

Access tokens, passwords, account recovery details, system logs, administrator interfaces, DNS settings, infrastructure documentation and database exports may be especially sensitive. Their inclusion in a Project does not make them public information.

Not every Project needs every item

Information requested or accessed should be relevant to the agreed work. A brief description or sanitized screenshot is often preferable to a full database or production administrator account.

SECTION 03 / 34Foundations

Ownership and customer control

Customer rights do not transfer through access

Existing rights

Customers retain ownership or other lawful rights in material they provide. Uploading, sharing, inspecting, modifying or temporarily copying materials for a Project does not by itself transfer those rights to the agency.

Other rights holders

Open source WordPress components, third party themes, plugins, APIs, photographs, fonts and licensed software continue to be governed by their own applicable terms.

Control of critical accounts

Clients should retain appropriate control of hosting subscriptions, domain registration, payment accounts, recovery methods and other essential systems unless a separate authorized arrangement provides otherwise.

SECTION 04 / 34Foundations

Limited permission for approved work

Use is connected to an agreed Project purpose

Permission to perform work

When a Client provides authorized Customer Content, the agency may use it as reasonably necessary to evaluate requirements, implement agreed changes, test, troubleshoot, document, coordinate support and comply with legitimate related obligations.

No blanket reuse

Permission to carry out a Project does not grant unrestricted permission to resell Customer Content, publish confidential details, create unrelated datasets, contact customer lists for unrelated marketing or use material outside the authorized engagement.

Changes of purpose

Materially different uses, methods or recipients should be assessed against the Project terms, relevant permissions and applicable law before proceeding.

SECTION 05 / 34Foundations

Confidentiality and professional discretion

Nonpublic customer information is handled for defined purposes

Confidential content

Business plans, unpublished websites, source code, strategy documents, customer information, revenue records and internal workflows can be confidential even when not individually stamped confidential.

Professional access

Authorized personnel and assigned Experts should respect confidentiality and use information only as necessary for their responsibilities. More restrictive obligations may be specified in a separate written agreement.

Exceptions and limits

Information already legitimately public, independently available without breach, or lawfully required to be disclosed may receive different treatment subject to the applicable terms and law.

SECTION 06 / 34Foundations

Information shared before a Project

Initial enquiries need appropriate safeguards too

Early stage briefs

Preliminary scope descriptions, quotations and diagnostic conversations may include private technical facts. Share only the information necessary to explain the request before terms and access arrangements are agreed.

Project acceptance

Sending a file, initial brief or access request does not automatically create a paid engagement or authorize every form of testing, downloading or configuration change.

Avoid unsolicited secrets

Do not include full databases, live API keys, payment card data or unrestricted administrator credentials in public project fields or general enquiry forms.

SECTION 07 / 34Access

Client, Expert and Administrator access

Permission reflects actual responsibilities

Clients

Clients provide lawful requirements, choose appropriate sharing methods and review scope or access decisions relevant to their Projects.

Experts

Assigned Experts may receive only the Customer Content needed for the approved contribution, subject to agency oversight, suitable authorization and any applicable confidentiality terms. Expert registration alone does not give access to Client Projects.

Administrators

Authorized Administrators may access information needed to supervise delivery, handle permissions, secure systems, resolve disputes and maintain the platform. Access should be proportionate and accountable.

SECTION 08 / 34Access

Safer ways to share project materials

Minimize exposure before uploading or sending data

Minimize first

Provide limited excerpts, test accounts, masked data, redacted screenshots or small examples when they can resolve the technical question without exposing a complete production dataset.

Use an approved route

Choose the restricted upload or credential sharing route agreed for the Project where available. Ordinary chat, public comments and email attachments may be unsuitable for highly sensitive secrets.

Validate recipients

Check who is authorized to receive materials and whether sharing is necessary. Do not send banking passwords, full card details, unrelated identity documents or secret recovery codes.

SECTION 09 / 34Access

Passwords, credentials and API secrets

Least privilege and time limited access

Access accounts

Where practical, create separate temporary accounts with minimum required privileges. Avoid sharing a permanent primary administrator login if a restricted alternative will support the work.

Secret handling

Credentials, private keys, API secrets and authentication tokens should not be published in Project descriptions, screenshots, public repositories or unprotected documents.

Revoke when finished

After Project completion or an access change, review and revoke temporary accounts and rotate relevant credentials where appropriate. Continuing access requires a continuing authorized purpose.

SECTION 10 / 34Access

WordPress administration and plugin access

Only what implementation requires

Administrative scope

WordPress backend access may expose user profiles, orders, comments, settings, files and sensitive plugin data. Administrators or Experts should use only the functions reasonably needed for the approved work.

Changes and approvals

Material changes to security settings, plugin configurations, checkout behavior, user roles or production content should follow the agreed review and implementation process.

Updates and audit trails

Where relevant, the Project should address update compatibility, staging, change records, backup readiness and rollback responsibilities.

SECTION 11 / 34Access

Hosting, domains and infrastructure

Protect foundational website systems

Systems involved

Hosting dashboards, DNS, database consoles, deployment credentials, server logs and backup consoles may expose critical website functions and confidential information.

Limited authority

A Project to migrate hosting or adjust DNS does not authorize unrelated changes to other domains, unrelated server accounts or systems outside the approved scope.

Third party accounts

Hosts, registrars and infrastructure providers may operate under their own contracts and privacy conditions. Clients should review these when assigning access.

SECTION 12 / 34Access

Professional supervision and collaboration

Agency coordinated assignments with restricted access

Team allocation

The agency may coordinate qualified Experts for approved Project work. Assignments should reflect relevant technical capability and permissions rather than open access to all Client material.

Confidentiality boundaries

Experts must not use entrusted content for independent client solicitation, personal portfolios, unrelated research, private datasets or later projects without an appropriate basis.

Access changes

If an Expert changes or leaves an assignment, the agency should review relevant permissions, handover needs and outstanding confidentiality obligations.

SECTION 13 / 34Data and tools

WooCommerce, membership and bookings

Store and account records need extra care

Customer information

WooCommerce orders, subscriber lists, booking details, course records and membership profiles may contain personal or commercially sensitive data. Access should correspond to the approved requirements.

Safe testing

Use sandbox transactions, staging environments, synthetic orders and masked records where practical. Real customer data should not be copied merely for convenience.

Payments and regulated data

Full payment card details, CVV values and banking passwords should not be requested in ordinary communications. Payment providers control their own processing systems under applicable terms.

SECTION 14 / 34Data and tools

Databases, migrations and exports

A single export can expose an entire business

Database contents

WordPress database exports can contain user records, tokens, orders, contact form submissions, private settings, logs and other sensitive material even when the live page appears public.

Extraction limits

Choose the smallest practical data subset and record why a full copy is required where relevant. Transferring a production database should be authorized and appropriately safeguarded.

Post migration review

Confirm intended data location, temporary copies and access before accepting the completed migration. A restore point or rollback method should be considered where the risk justifies it.

SECTION 15 / 34Data and tools

Files, code, documents and media

Handle supplied assets within the authorized scope

Types of files

Projects can involve source code, design assets, text, images, video, spreadsheets, reports, PDF documents, plugin packages, configuration files and other customer supplied materials.

Lawful rights

Clients should have appropriate permission to share files and request adaptations. Third party licenses and intellectual property restrictions remain relevant.

Copies and sharing

Working copies and attachments should be limited to the intended Project and not distributed to unrelated professionals or public channels merely because they are technically accessible.

SECTION 16 / 34Data and tools

Screenshots, diagnostics and logs

Technical evidence can contain secrets

Diagnostic content

Error messages, access logs, browser consoles, screen captures, analytics reports and support tickets can expose identifiers, file paths, email addresses, cookies or access tokens.

Redaction

Remove or mask unrelated personal data and secrets where possible before sharing evidence or attaching logs to a Project.

Purpose

Use such evidence for authorized troubleshooting, quality assurance, security investigation or other agreed technical work, not unrelated surveillance or profiling.

SECTION 17 / 34Data and tools

Project messages and support records

Delivery communication can also be confidential

Project records

Briefs, milestones, review comments, work notes, support messages and relevant decisions may be retained as needed for delivery, quality control, payment records, disputes and lawful administration.

Authorized review

A communication sent through the agency should not be assumed to be visible to one Expert alone; authorized administrators may need to review relevant discussions.

Choose appropriate channels

Use Support for general guidance and an approved restricted method for sensitive technical details. Do not send complete passwords or customer exports through ordinary live chat.

SECTION 18 / 34Data and tools

External tools, hosting and suppliers

Vendor conditions matter when content leaves the site

Potential systems

Approved Projects may involve hosting, storage, backup systems, email, analytics, support, project management, code repositories, APIs and other compatible applications.

Provider assessment

The suitability of an external provider depends on actual configuration, data involved, confidentiality obligations, retention practices and applicable legal requirements. No particular provider is automatically authorized for all content.

Client restrictions

If a Client requires an approved provider list, data residency or a specific subprocessor restriction, it should be raised before the work is accepted and recorded in the Project terms where agreed.

SECTION 19 / 34Data and tools

Webhooks and automated data flows

Connected systems can transmit more than intended

Workflow definition

Automation Projects should identify triggers, destinations, permitted fields, handling of duplicates or failures and human approval points where appropriate.

Avoid unnecessary data

Do not transmit full customer records or confidential attachments where a limited status, identifier or event notification would meet the business need.

Review before launch

API scopes, recipient authorization, test records, logging and recovery should be considered before enabling a workflow on live systems.

SECTION 20 / 34Data and tools

AI assistants, prompts and outputs

Confidential material is not automatically AI input

Before sending content

Confidential Customer Content should not automatically be submitted to external AI models, assistants or knowledge bases. The Project should assess necessity, permissions, model provider terms, data sensitivity and alternatives.

AI provider controls

Depending on the selected provider and configuration, uploaded data and outputs may be subject to separate retention, monitoring or model improvement terms. The actual product settings must be verified rather than assumed.

Human oversight

AI-generated output can be inaccurate or disclose sensitive information. Appropriate human review, access boundaries and verification belong in the scope for material use cases.

No unrelated training

Entrusted Client materials should not be deliberately reused to build unrelated training datasets, general marketing datasets or public demonstrations without a valid contractual, lawful or client authorized basis.

SECTION 21 / 34Protection

Cross border handling and client restrictions

Data location requirements should be agreed early

Where material may travel

Hosting, backups, emails, support platforms, external Experts or AI providers may process information in different countries depending on the actual approved configuration.

Legal safeguards

Where personal data is involved, transfers and onward sharing must satisfy applicable law and relevant data protection arrangements. The separate Privacy Policy addresses individual data rights.

Special requirements

Data residency, regulated sectors, restricted locations or enterprise access rules should be documented before Project approval; such arrangements may affect feasibility and pricing.

SECTION 22 / 34Protection

Personal information in Customer Content

The client and agency may have distinct data responsibilities

Roles depend on the activity

A Client may determine the purposes of personal information held on its website, while the agency may process relevant information under authorized instructions for that Project. Actual legal roles depend on circumstances.

Specific agreements

Where required, parties should put appropriate controller and processor responsibilities, technical measures, permitted subprocessors and return or deletion instructions in a written agreement.

Individual rights

Individuals retain rights under applicable data protection law. Customer ownership of commercial files does not override the rights of people represented in those files.

SECTION 23 / 34Protection

Reasonable content protection safeguards

Risk based controls, not guarantees of absolute security

Safeguard planning

Appropriate measures may include role limited access, authenticated accounts, encrypted transfers, protected backups, tested permissions, patching, access review and confidentiality arrangements where applicable.

Proportionality

The required controls depend on sensitivity, Project risks, technical environment and agreed responsibilities. A public policy alone cannot verify how every external provider or client system is configured.

No absolute warranty

No digital platform, network or storage method is completely immune to failure or unauthorized access. Material Project guarantees require their own express terms.

SECTION 24 / 34Protection

Security incidents and escalation

Report suspected unauthorized exposure promptly

What to report

If a party discovers possible loss, disclosure, misuse or unauthorized access to entrusted Project material, it should promptly contact the designated Project channel or the Support Center with available facts.

Response

A response may require containment, evidence preservation, access revocation, technical investigation, customer cooperation and notices required by law or agreed terms.

Avoid unfounded timelines

Notification responsibilities and deadlines vary by data type, legal role, jurisdiction and contract. This policy does not establish a universal incident notice period.

SECTION 25 / 34Protection

Portfolios, examples and testimonials

Nonpublic work is not automatic marketing material

Customer approvals

Private screenshots, confidential client names, unpublished features, revenue figures and Project files should not be made public as case studies or promotional examples without an appropriate basis and authorization.

Scope of permission

Permission to quote a testimonial does not necessarily authorize use of a business logo, personal photo or additional private information. Relevant permissions should be specific.

Public websites

Publicly visible facts may have different confidentiality status, but private access or knowledge obtained through a Project should still be treated responsibly.

SECTION 26 / 34Protection

Custom deliverables and intellectual property

Contracts and licenses define rights in new work

Agreed results

The relevant Project terms should specify ownership, licensing, handover materials and any conditions affecting new code, designs, documentation or configuration.

Existing components

WordPress core, open source libraries, licensed plugins, APIs, fonts, assets and pre-existing technical know how remain governed by their applicable rights and licenses.

Confidentiality continues

A reusable technical approach does not permit disclosure of entrusted Client secrets or reuse of proprietary material beyond valid permissions.

SECTION 27 / 34Retention and requests

Storage, working copies and backups

Copies may exist in different operational systems

Working environments

Approved work can require temporary staging copies, development backups, test records and Project attachments. These should be limited to reasonable need and subject to appropriate access safeguards.

Backup limits

A copy removed from a working folder may remain in snapshots or provider backups until relevant retention cycles end. Absolute immediate erasure from all systems should not be assumed.

Client systems

Clients remain responsible for backups and account recovery under their control except to the extent a written Project explicitly assigns such duties to the agency.

SECTION 28 / 34Retention and requests

Retention and lawful records

Different records may require different periods

Purpose and necessity

Project files and confidential material should not be retained indefinitely without a defensible purpose. Short term diagnostics can have different retention needs from invoices, contract records or security evidence.

No invented fixed schedule

Actual retention periods depend on configured systems, backup lifecycles, contract terms, records obligations and applicable laws. These should be confirmed operationally and disclosed where required.

Review and access

Continuing access or storage should be reviewed when a Project ends or support arrangements change.

SECTION 29 / 34Retention and requests

Return, deletion and access removal

Ask for eligible content handling after completion

Client requests

Clients may request return or removal of materials that are no longer required for an authorized purpose, subject to lawful retention, active agreements, disputes or other applicable constraints.

What to agree

A Project may specify file delivery, deletion of staging data, repository access, temporary backup handling and responsibility for revoking accounts.

Practical limits

Deletion from active Project folders may not instantly erase permitted backups or independent customer systems. Requests should identify the relevant Project and material.

SECTION 30 / 34Retention and requests

Customer responsibilities and lawful authority

Share only information you can authorize

Authority and accuracy

Clients must have authority to request access, disclose materials, authorize changes and instruct processing of website information on behalf of an organization where relevant.

Minimize and protect

Clients should identify exceptional confidentiality needs, secure their own accounts, provide accurate instructions, avoid oversharing and review required approvals or access permissions.

After handover

Where the engagement ends, Clients should review temporary accounts, credentials, integrations, downloaded copies and continuing maintenance arrangements.

SECTION 31 / 34Retention and requests

Unlawful content and valid disclosures

Illegal and unauthorized use is not accepted

Excluded instructions

Customers should not request unauthorized system access, unlawful surveillance, stolen datasets, pirated assets, malicious code, fraud or misuse of credentials. The agency may decline work that conflicts with its standards or applicable law.

Legal processes

Entrusted information may be subject to valid legal orders or lawful disclosures. The agency should assess requests appropriately, recognizing that advance notice may sometimes be legally restricted.

Other rules

The Terms and Conditions and accepted Project agreement govern commercial consequences and any permitted suspension or termination.

SECTION 32 / 34Retention and requests

Nondisclosure and enterprise requirements

Additional controls may be agreed before access

Custom confidentiality arrangements

Clients can request nondisclosure agreements, enterprise access conditions, named authorized personnel, restricted vendors, storage limitations or a data processing agreement where relevant.

Before starting

Raise unusual technical, procurement, regulated data or AI processing restrictions before accepting scope or handing over sensitive materials.

No automatic promise

A request for special conditions does not make them operative until the parties agree the necessary terms and confirm feasibility.

SECTION 33 / 34Retention and requests

Policy changes and related documents

Read the version relevant to your Project

Updates

This Content Privacy Policy may be amended when operating practices, capabilities, laws or technical systems change. A genuine publication or revision date should be used only after the wording is approved.

Related documents

Review the Privacy Policy for personal information, Terms and Conditions for contractual rules, Cookies Policy for website technology, and your specific Project agreement for any additional binding requirements.

Conflicts

An agreed project specific confidentiality or data processing term may supplement the general policy subject to applicable law and the documents’ agreed order of priority.

SECTION 34 / 34Retention and requests

Questions, requests and support

Ask before disclosing sensitive information

Contact

For questions about content sharing, authorized access, confidentiality or removal requests, contact admin@esposearch.net or use the Support Center for general guidance.

Useful context

Reference the relevant Project and type of material without including passwords, entire databases, bank secrets or unrelated identity documents in an ordinary email.

Escalation

Where Customer Content includes personal information, individuals should also consult the Privacy Policy and applicable rights. A specific incident may require a more restricted response route.

Frequently asked questions

Common questions about content privacy.

Get a quick orientation before providing materials for a WordPress Project. For a particular agreement or sensitive case, request written clarification.

Visit Support Center

Does the agency own my website content if I upload it?
No transfer of your existing rights occurs merely because material is shared or accessed for a Project. Rights in newly created deliverables follow the agreed Project terms and applicable third party licenses.
Should I send my administrator password in the Project description?
No. Avoid publishing passwords, API keys, full database copies or payment secrets in public or ordinary communication fields. Ask for an approved restricted access route and use limited accounts where possible.
Can Experts access every Client Project?
No. Professional participation or registration does not itself authorize access. Assigned work should use the permissions and content reasonably necessary for that approved Project.
Can confidential documents be sent to an AI tool?
Not automatically. The approved use case, sensitivity, provider terms, permissions and safeguards must be considered before sharing confidential content with an external model or connected tool.
Can you showcase my completed website in a case study?
Nonpublic customer information and private Project screenshots should not be published for marketing without an appropriate authorization. Any permission should cover the particular materials and intended use.
How do backups and deletion work?
Active files may be removed when eligible, but lawfully retained records and provider backup cycles can create limits. Ask for the applicable Project specific return, retention or deletion arrangements.
Who is responsible for personal data on my website?
The answer depends on the processing activity. A Client may determine purposes for customer information, while the agency may process relevant data under instructions. The Privacy Policy and any required written data processing agreement govern the details.
Where can I ask a confidential content question?
Contact admin@esposearch.net or the Support Center with the Project reference and a general explanation. Do not include full passwords, payment secrets or unnecessary personal data in an initial message.
Related governance and next steps

Review the related rules or learn how to commission a professionally managed Project.

Professional WordPress Solutions

Clear Project requirements. Responsible content handling.

Before sharing files or access, confirm the purpose and the people who need them. If you are ready to build, optimize or automate your WordPress website, start with a managed Project.