Have a startup idea? Turn it into a live, operational WordPress website. Start Your Project

Content Privacy

Esposearch Content Privacy

Your Website Content Stays Connected to the Work You Approve.

This Content Privacy page explains how Esposearch handles website content, files, credentials, business materials and other customer-controlled information made available for WordPress services, Products, Tasks, Customized Offers, custom Projects and related support.

Last updated 9 September 2026Applies to Esposearch.netSpecialist WordPress Agency
Customer-Controlled Content
Purpose-Limited Use
Minimum Necessary Access
Agency-Managed Access
No Unapproved Publicity

Content Privacy is different from personal-data privacy.

This page focuses on customer-controlled website and project materials entrusted to Esposearch for service delivery. Personal data such as account, contact, transaction and website-usage information is addressed separately in the Esposearch Privacy Policy. Contractual rights, responsibilities and intellectual-property terms should also be read together with the applicable Terms and Conditions and service scope.

Content Privacy at a Glance

Three principles guide how customer content should move through Esposearch.

Esposearch may need files, content, permissions or technical access to complete approved WordPress work. The aim is to keep that access connected to the scope, limited to what is reasonably needed and managed under agency oversight.

01
Your Materials

You keep control of the content you provide.

Providing content to Esposearch for a service does not by itself transfer ownership of that material to Esposearch. Rights in customer materials remain subject to the customer’s existing rights, applicable licences, the service agreement and relevant law.

What this means in practice
  • Content is connected to the requested work.
  • Ownership is not claimed merely because files are shared.
  • Public use requires an appropriate basis or authorization.
02
Access by Need

Access follows the approved scope.

Esposearch should make customer content available only to the people, systems or providers reasonably needed to review, implement, test, support, secure or verify the approved work. Access should reflect the responsibility being performed.

What this means in practice
  • Need-to-know access for assigned personnel.
  • Permissions can be limited or temporary where practical.
  • Access can change as the work moves through delivery.
03
No Unrelated Reuse

Delivery access is not a licence for unrelated use.

Customer materials should not be republished, resold, exposed publicly or reused for unrelated commercial purposes simply because Esposearch received them during delivery. Portfolio, case-study or promotional use should have an appropriate authorization or other valid basis.

What this means in practice
  • No automatic portfolio permission.
  • No unrelated sale of customer content.
  • Public disclosure is separated from service delivery.
Core content-privacy principle

Esposearch should request, access and use only the customer content reasonably connected to the approved website function, service scope, support request or delivery responsibility.

Content Covered

Content Privacy applies to the materials needed to understand, build, improve or support your website.

The exact content varies by service. It may be supplied directly by you, made available through an approved website or account, or created as part of the delivery workflow.

Website Copy, Drafts & Documents

Page copy, blog drafts, product descriptions, policies, research documents, downloadable files, unpublished materials, briefs and other written content supplied for implementation, editing, migration, SEO or website structuring.

Examples: pages, articles, PDFs, briefs, drafts

Brand, Image & Media Assets

Logos, photographs, illustrations, videos, audio, brand guidelines, design files, typography references, social assets and other media used to represent the customer or support the approved website experience.

Examples: logos, photos, graphics, media

Commerce & Catalogue Content

WooCommerce product data, descriptions, images, prices, categories, inventory information, downloadable product files, shipping content, store settings and other materials required for approved commerce work.

Examples: products, prices, catalogue information

Technical & Configuration Materials

Website structure, plugin and theme settings, configuration exports, database-related information, analytics configurations, SEO settings, staging data, error logs and other technical information reasonably required for diagnosis or implementation.

Examples: settings, logs, exports, staging data

Credentials & Access Permissions

Temporary or approved access to WordPress, hosting, domain management, analytics, email, CDN, security, cloud or connected services where that access is necessary to perform the agreed work.

Prefer limited, temporary access where practical

Business, Research & Confidential Materials

Internal business information, research materials, campaign information, private drafts, customer-supplied datasets, process documents and other non-public content needed to understand or complete an approved website requirement.

Share only what the approved scope genuinely requires

Purpose-Limited Use

Customer content should be used for the service, Project, Task, Product, Customized Offer, support request, quality review or related website function for which it was provided or made accessible.

Minimum Necessary Access

Esposearch should request the smallest reasonable set of files, permissions and credentials needed to complete the approved work safely and efficiently.

Agency-Managed Participation

Esposearch reviews the requirement and coordinates the appropriate Expert, technician or authorized personnel. Customers should not need to distribute content broadly or manage a public pool of service providers.

Confidentiality by Context

Non-public customer materials should be treated according to their sensitivity, the delivery context and any applicable confidentiality, contractual or legal requirements.

Reasonable Security

Esposearch may use access controls, secure systems, backups, monitoring, role separation and other safeguards appropriate to the website environment, content and delivery risk.

Lifecycle Awareness

Content should not remain in active working environments longer than reasonably needed. Retention may still be necessary for support, backups, records, disputes, legal obligations or continuity of an ongoing service.

Assigned Esposearch Experts

Specialist access is coordinated by Esposearch—not opened broadly.

Some WordPress work requires an assigned Esposearch Expert, technician or authorized collaborator to see customer materials or access a website environment. Esposearch should coordinate that participation around the confirmed requirement and the level of access reasonably needed to perform the assigned responsibility.

Where practical, customers may use role-based accounts, staging environments, temporary credentials or limited permissions rather than sharing unrestricted administrator access.

Scope Before Access

The requirement should be understood before access is requested. This helps connect permissions and files to a defined Task, Product, Customized Offer, Project or support outcome.

Role-Based Participation

An assigned Expert should receive only the information and access reasonably connected to the responsibility being performed, rather than unrestricted visibility into unrelated customer materials.

Review & Verification

Authorized reviewers may need access to relevant deliverables, staging areas or technical information so Esposearch can verify that completed work reflects the approved scope and quality expectations.

Access Changes With the Work

Permissions may be reduced, revoked or replaced when a delivery stage is complete, a role changes or the access is no longer reasonably needed for the purchased service or ongoing support.

Customer Content & Ownership

Esposearch does not claim ownership of customer content merely because that content is uploaded, shared or made accessible for service delivery. Ownership and permitted use remain subject to the customer’s own rights, third-party licences, the applicable service agreement, the Terms and Conditions and relevant law.

  • Customers should provide only content they own, are licensed to use or are otherwise authorized to provide.
  • Third-party themes, plugins, fonts, media, stock assets and software remain subject to their own licences.
  • Ownership of newly created deliverables should follow the applicable service scope, agreement and relevant law.
  • Providing access for delivery does not automatically authorize unrelated public or promotional use.

Permitted Delivery Use

Customer content may need to be copied, edited, transformed, uploaded, migrated, tested, backed up, displayed in staging or otherwise processed where those actions are reasonably necessary to perform the work the customer requested.

  • Review and understand the website requirement.
  • Design, develop, optimize, migrate, secure or maintain the website.
  • Prepare staging, testing, backup or quality-review copies where appropriate.
  • Communicate about the work and provide applicable support.

Portfolio, case-study and promotional use are separate from ordinary delivery.

Esposearch should not treat customer content, private drafts, screenshots, internal information or unpublished work as automatically available for public portfolio or promotional use. Where Esposearch wants to feature identifiable customer work, an appropriate authorization, contractual basis or other valid permission should apply. Public content that is already lawfully available may still be referenced in ordinary ways permitted by law, but confidential or restricted materials should remain subject to their applicable limitations.

AI-Assisted Work

Esposearch may use artificial intelligence tools where they create practical value for an approved website, content, analysis, support or workflow requirement. Customer content should be minimized before external AI processing and should not be submitted merely because an AI tool is available.

  • Use AI where it supports the defined service or approved workflow.
  • Avoid unnecessary confidential, sensitive or identifying information in prompts or uploads.
  • External AI providers may process submitted information under their own service and privacy terms.
  • Important outputs should remain subject to appropriate human review before implementation.

Third-Party Tools & Integrations

WordPress delivery can involve hosting, domain, security, backup, analytics, SEO, email, cloud, payment, automation, content-delivery and other technology providers. Customer content may be processed by those services when their involvement is necessary for the selected website function or approved scope.

  • Provider access should remain connected to the service the provider supplies.
  • Third-party services operate under their own terms, privacy practices and security arrangements.
  • Customers may need to approve or maintain licences, accounts or permissions for tools used on their websites.
  • Cross-border processing may occur where a provider operates infrastructure in multiple countries.

Confidential & Sensitive Materials

Some website projects involve non-public business information, research, unpublished content, customer records or other material that may require additional care. Customers should identify unusual confidentiality requirements before delivery where those requirements affect how the work must be handled.

  • Share only the confidential material genuinely needed for the work.
  • Flag special handling, contractual or regulatory requirements before access is granted.
  • Avoid placing unrelated sensitive information in ordinary project messages or uploads.
  • Where personal data is involved, the separate Privacy Policy and applicable data-protection obligations also apply.

Credentials & Administrative Access

Credentials can create broad control over a website or connected service. Where practical, customers should create dedicated or temporary accounts with only the permissions needed for the approved work instead of sharing personal master credentials.

  • Use role-based WordPress accounts where appropriate.
  • Prefer temporary passwords, invitation-based access or limited permissions where supported.
  • Do not send banking credentials, full payment-card details or unrelated personal passwords for website work.
  • Review and revoke access after completion when ongoing access is not part of the service.
Content Lifecycle

Content can move through review, active delivery, handover and retention.

Not every file follows the same timeline. The type of service, ongoing support, backups, dispute risk, legal obligations and technical environment may affect how long particular working materials remain available.

01

Review & Scoping

Content may first be reviewed to understand the requirement, confirm whether Esposearch can perform the work and determine the appropriate scope, access level or next step.

02

Active Delivery

Working copies, staging versions, exports, backups or transformed content may be created where reasonably necessary for implementation, testing, migration, quality review or troubleshooting.

03

Handover & Support

Relevant materials may remain available for customer handover, post-delivery support, continuity, maintenance or evidence of the approved scope where those purposes still apply.

04

Deletion or Continued Retention

Content no longer reasonably needed should be removed, anonymized or allowed to expire where appropriate, while necessary records, backups or materials may remain for legitimate contractual, operational, legal or security reasons.

Deletion requests and backups

Customers may contact Esposearch about removal or return of specific materials. A request may not always result in immediate deletion from every backup, archive, transaction record or system where continued retention is reasonably required or technically unavoidable for a limited period.

Customer Responsibilities

Good content privacy also depends on what is shared and how access is granted.

Customers remain responsible for deciding what they are authorized to provide and for avoiding unnecessary exposure of content that is unrelated to the requested website work.

Have the Right to Provide the Content

Provide content, data, media, software and credentials only where you own them, hold an appropriate licence, have the required permission or otherwise have authority to make them available for the requested work.

Share Only What Is Necessary

Remove or avoid unrelated confidential, personal or sensitive material when a smaller file, redacted copy, staging version or narrower permission would allow Esposearch to complete the work.

Use Appropriate Access Controls

Create temporary or role-limited accounts where practical, protect master credentials and revoke access that is no longer required after delivery or when an ongoing management service ends.

Identify Special Restrictions

Tell Esposearch before work begins if content is subject to unusual confidentiality, licensing, contractual, regulatory or third-party restrictions that materially affect storage, access, transfer or processing.

Respect Other People’s Rights

If content contains personal data, copyrighted materials, confidential information or other third-party interests, make sure the requested use is appropriate and that any required permissions or lawful basis are in place.

Report Access Changes Promptly

Tell Esposearch if credentials are compromised, permissions change, an employee or provider should no longer have access, or a project contains content that requires urgent restriction or removal.

Content Security Concerns

Report suspected unauthorized content access as soon as practical.

If you believe customer content, credentials, website files or other entrusted materials have been accessed, disclosed, altered or used inappropriately in connection with Esposearch delivery, contact Esposearch with enough information to identify the affected service or Project. Do not include unnecessary passwords or sensitive information in the initial report.

1
Identify the affected work

Provide the relevant order, Task, Project, website or support context.

2
Describe what you observed

Explain the suspected access, disclosure, change or misuse and when you noticed it.

3
Protect access where possible

Reset or revoke compromised credentials when safe and appropriate to do so.

4
Esposearch reviews the concern

Appropriate investigation, containment and follow-up should reflect the circumstances and applicable obligations.

Changes to this Content Privacy page

Esposearch may update this page as services, WordPress delivery practices, technology providers, security processes or legal requirements change. The current version should be published on this page with an updated date. Where a service agreement or another policy contains more specific content-handling terms, those terms should be read together with this page.

Content Privacy Contact

Questions about files, credentials or confidential website content?

Contact Esposearch if you need clarification before sharing content, want to discuss access requirements, need to request removal of particular materials or want to raise a content-security concern.

Content Privacy Emailadmin@esposearch.net

Use this address for content-handling, access and removal questions.

Contact PageContact Esposearch

Use the website contact options for service and delivery guidance.

Personal DataPrivacy Policy

Review the separate policy for personal-data handling and privacy rights.

Contractual TermsTerms and Conditions

Review service rules, user responsibilities and applicable contractual terms.

Content Privacy FAQs

Practical answers before you share website materials.

These answers summarize how Esposearch approaches customer-controlled content during WordPress and practical AI website work. They cover ownership, assigned Expert access, credentials, AI tools, portfolio use, retention and content-security concerns.

Content Privacy should be read together with the Privacy Policy, Terms and Conditions and the actual scope of the Product, Task, Customized Offer or Project being purchased.

QWhat does Esposearch mean by “content privacy”?+

Content Privacy concerns the website materials, files, credentials, business information, drafts, technical configurations and other customer-controlled content made available so Esposearch can understand, deliver, test, review or support approved work.

QHow is Content Privacy different from the Privacy Policy?+

The Content Privacy page focuses on customer-controlled website and project materials. The separate Privacy Policy addresses personal data such as account information, contact details, transactions, technical usage data and applicable privacy rights.

QDoes Esposearch own the content I provide?+

Esposearch does not claim ownership merely because customer content is provided for service delivery. Rights remain subject to the customer’s ownership or licences, third-party rights, the service agreement, Terms and Conditions and applicable law.

QCan an assigned Esposearch Expert see my files or website?+

Where the approved work requires it, an assigned Expert or other authorized person may receive access to the relevant files, website environment or connected service. Access should be limited to what is reasonably necessary for the assigned responsibility and coordinated under Esposearch’s agency-managed process.

QHow should I provide WordPress, hosting or domain credentials?+

Where practical, create a temporary or role-limited account instead of sharing personal master credentials. Provide only the permissions required for the approved scope, avoid sending unrelated sensitive passwords, and revoke access when the work no longer requires it.

QCan Esposearch use my content with artificial intelligence tools?+

Esposearch may use AI tools where they support an approved website, content, analysis or workflow requirement. Customer content should be minimized before external AI processing, and unnecessary confidential or sensitive information should not be submitted merely because an AI tool is available.

QWill Esposearch show my website or materials in a portfolio or case study?+

Ordinary delivery does not automatically authorize public portfolio or promotional use of private customer materials. Identifiable customer work should be featured only where an appropriate authorization, contractual basis or other valid permission applies.

QWhat happens to working files after the service is completed?+

Working copies may be removed when they are no longer reasonably needed, but some materials may remain for support, continuity, backups, transaction records, disputes, security or legal obligations. Backup copies may also persist for a limited period according to the systems involved.

QWhat if my website content includes personal data or information belonging to other people?+

You should provide such information only where you have an appropriate right, permission or lawful basis to do so. The Esposearch Privacy Policy and applicable data-protection requirements also apply when personal data is involved.

QHow do I request removal of content or report a content-security concern?+

Email admin@esposearch.net or use the Esposearch Contact page. Identify the relevant website, order, Task or Project and describe the material or concern clearly, but do not include unnecessary passwords or sensitive information in the initial message.

Content Privacy & Trust

Share what the work needs—not more than the work needs.

Esposearch’s content-handling approach is designed around customer-controlled materials, defined service scopes, agency-managed access and practical safeguards throughout WordPress delivery.