1. Purpose of This Content Privacy Policy

This policy applies specifically to confidential or non-public content supplied to Esposearch.net for service delivery. It supplements our general Privacy Policy, which covers personal information such as account, contact, analytics and transaction data.

Its purpose is to explain how project materials are handled inside our managed-agency workflow.

2. What We Mean by “Client Content”

Client Content includes non-public information and materials provided, uploaded, created or made accessible during an Esposearch.net project.

3. Ownership of Client Content

Clients retain their rights in the content and materials they lawfully provide to Esposearch.net. Sharing content with us does not transfer ownership to Esposearch Limited.

You grant Esposearch.net a limited permission to access, process, reproduce, modify or otherwise handle that content only as reasonably necessary to provide the requested services, maintain the project, comply with law or exercise our contractual rights.

4. How We Use Client Content

Client Content may be used only for legitimate project and operational purposes, including:

• Performing a WordPress SEO Audit.
• Reviewing Rank Math configuration and technical SEO.
• Analyzing website speed and GTmetrix findings.
• Implementing approved SEO or speed fixes.
• Developing SEO content and blog strategy.
• Providing ongoing WordPress SEO Management.
• Preparing reports, quotations, recommendations and project documentation.
• Providing support, troubleshooting or quality assurance.
• Maintaining project history, records and evidence where reasonably necessary.

5. Who Can Access Client Content

Access is limited to persons who reasonably need the content to perform, supervise, review, support or administer the project.

• Authorized Esposearch.net administrators.
• Approved specialists assigned to the relevant project.
• Technical support personnel where reasonably required.
• Service providers that host, transmit or process the content as part of website operations.

Access is not intended to be made available to unrelated users, other clients or the general public.

6. How Expert-Team Access Works

Esposearch.net operates as a controlled digital agency. “Freelancers” inside the WorkReap system represent members of our expert team rather than an open public freelance marketplace.

When a project requires specialist execution, the admin may assign relevant tasks and provide the assigned expert with the minimum project information reasonably required to perform the approved work.

7. WordPress, Hosting and Account Credentials

Some projects require access to WordPress, hosting, domains, analytics, SEO tools, caching tools, Search Console or related platforms.

Where possible, clients should create temporary or role-limited accounts specifically for Esposearch.net rather than sharing primary administrator credentials.

• Credentials should be shared only through reasonably secure channels.
• Access should be limited to what is necessary for the project.
• Clients may revoke access after delivery where continued access is not required.
• For ongoing SEO Management, continued access may be necessary for the duration of the service.

8. Storage and Retention of Project Content

Project content may be stored in Esposearch.net systems, connected WordPress tools, email, secure cloud or hosting environments, project-management systems, backups or other operational systems reasonably required for service delivery.

We retain project content only for as long as reasonably necessary for delivery, support, quality assurance, recordkeeping, dispute resolution, legal compliance or continuing service obligations.

Retention periods may vary according to the nature of the project, account status, contractual commitments and whether ongoing management remains active.

9. External Sharing of Client Content

Esposearch.net does not ordinarily disclose confidential project content to unrelated third parties.

Limited disclosure may occur where necessary to:

• Use hosting, cloud, email, security or project-management infrastructure.
• Use client-authorized third-party SEO, analytics, performance or WordPress services.
• Resolve technical issues with a provider when client approval or operational necessity applies.
• Comply with a lawful court order, regulatory request or other legal obligation.
• Protect the rights, systems, security or legitimate interests of Esposearch.net or others.

10. Use of AI-Assisted Tools

Esposearch.net may use AI-assisted tools, including Content AI or other approved software, to support research, content planning, SEO analysis, drafting, classification or optimization workflows.

Where client content is processed through a third-party AI or software service, that provider may process data under its own terms and privacy practices.

We aim to avoid submitting unnecessary confidential information to external AI systems and to use only the information reasonably required for the task.

11. Portfolio, Testimonials and Public Use

Esposearch.net does not treat confidential client content as public marketing material merely because we worked on the project.

We will not intentionally publish private project files, credentials, internal reports, unpublished strategies or non-public client materials as portfolio content without authorization.

If we wish to reference a client name, testimonial, logo, screenshot, case study or project result publicly, we may seek permission where the material is not already public or where authorization is otherwise appropriate.

12. Content Security

We use reasonable administrative and technical measures intended to reduce unauthorized access, misuse, loss or disclosure of client content.

• Need-to-know access for assigned personnel.
• Admin-controlled project assignment.
• Role-limited access where practical.
• Reasonable password and account-security practices.
• Use of reputable hosting and technology providers.
• Internal quality and project oversight.

No online system can be guaranteed to be completely secure. Clients should also maintain backups, use strong passwords and protect their own systems.

13. Client Responsibilities for Content Privacy

Clients also have responsibilities when providing content to Esposearch.net.

• Provide only information necessary for the project.
• Do not share credentials or data that the client is not authorized to provide.
• Remove or redact unnecessary sensitive information where practical.
• Use secure credential-sharing methods where available.
• Maintain current backups before major website changes.
• Notify us of any special confidentiality or data-handling restrictions before work begins.

14. What Happens After Project Completion

After a project is completed, access may be removed, reduced or retained depending on the service relationship.

• Temporary project accounts may be disabled or revoked.
• Clients may change passwords or remove Esposearch.net access.
• Ongoing SEO Management may require continued access.
• Project records and deliverables may be retained for reasonable business, support and legal purposes.
• Backup copies may remain for a limited period according to system retention practices.

15. Legal or Protective Disclosure

Confidentiality obligations do not prevent Esposearch.net from using or disclosing content where reasonably necessary to comply with applicable law, respond to lawful process, enforce our agreements, prevent fraud, investigate misuse or protect the rights and security of Esposearch Limited, clients, experts or other parties.

16. Content Privacy Requests

Clients may contact Esposearch.net to ask about project-content access, request removal of unnecessary access, identify special confidentiality requirements, request deletion where appropriate, or raise a concern about how project content has been handled.

Some records may need to be retained for contractual, tax, security, legal or dispute-resolution purposes.

Submit a Content Privacy Request

17. Changes to This Content Privacy Policy

We may update this policy to reflect changes in our services, project workflows, technology, security practices or legal requirements.

The current version will be published on this page with an updated revision date.