ecHOSTS is committed to protecting customer data and respecting privacy rights. This policy explains how data is stored, how long it is retained, and how we comply with GDPR requirements.

🔐 Data Privacy Rights

Customers have full rights over their personal data.

Your Rights Include

• Right to access your personal data

• Right to correct inaccurate information

• Right to request data deletion (where legally applicable)

• Right to restrict or object to data processing

• Right to data portability

📌 Requests related to data privacy can be submitted via the ecHOSTS support team.

🗄️ Backup Retention Period

ecHOSTS maintains backups to ensure service reliability and data protection.

Backup Retention Overview

• Daily backups retained for a limited period

• Weekly or monthly backups based on hosting plan

• Older backups are automatically removed

• Retention duration varies by service type

📌 Backups are for disaster recovery, not long-term data storage.

🌍 GDPR Compliance Overview

ecHOSTS follows GDPR principles to protect user data:

• Data is collected only for legitimate service purposes

• Personal data is stored securely with restricted access

• Data is not shared with third parties without legal or operational necessity

• Customers can request data access or removal

• Security measures protect against unauthorized access

📌 GDPR applies to users located in the European Economic Area (EEA).

✅ Customer Responsibilities

• Keep account information accurate

• Secure login credentials

• Obtain user consent when collecting personal data on websites

• Ensure GDPR compliance for hosted content

⚠️ Important Notes

• ecHOSTS does not control data collected by customer websites

• Website owners are responsible for privacy policies and cookie notices

• Legal data retention may apply for billing or compliance reasons

📩 Need Help with Data Requests?

For GDPR or data retention requests, contact ecHOSTS support with proper verification.

The post 🔹 Data Retention & GDPR appeared first on ecHOST.

The Email & Spam Policy is designed to protect ecHOSTS users from spam, abuse, and blacklisting issues, while ensuring reliable email delivery for all customers.

📧 Bulk Email Rules

To maintain a good email reputation and deliverability:

• Bulk or mass emailing is not allowed on shared hosting

• Sending unsolicited emails (spam) is strictly prohibited

• Purchased or scraped email lists are not permitted

• Transactional emails (password resets, order confirmations) are allowed

• Newsletters must use opt-in subscribers only

📌 For large-scale email campaigns, we recommend using dedicated email marketing services.

🛡️ Spam Prevention Measures

ecHOSTS uses multiple layers of spam protection:

• Spam filtering and mail scanning

• Rate limits on outgoing emails

• SPF, DKIM, and DMARC enforcement

• IP reputation monitoring

• Malware and script detection

User Responsibilities

• Configure SPF, DKIM, and DMARC correctly

• Secure contact forms and scripts

• Keep CMS and plugins updated

• Use strong email passwords

📌 Proper configuration helps prevent emails from landing in spam folders.

🚨 Email Abuse Handling

If email abuse is detected:

1. Affected email accounts may be temporarily suspended

2. Outgoing email may be restricted immediately

3. User will be notified via registered email

4. Investigation will be conducted by the ecHOSTS support team

Repeated Violations May Result In

• Permanent email suspension

• Account termination

• IP blacklisting prevention actions

📌 ecHOSTS prioritizes server reputation to ensure reliable email delivery for all customers.

✅ Best Practices for Safe Email Usage

• Use email only for legitimate communication

• Avoid sending large attachments frequently

• Monitor email sending logs

• Use professional email clients securely

• Contact ecHOSTS support if unsure about email limits

The post 🔹 Email & Spam Policy appeared first on ecHOST.

The Acceptable Use Policy (AUP) ensures that all ecHOSTS users use our services responsibly, securely, and fairly. Violations can lead to account restrictions or suspension.

🚫 Prohibited Activities

Users must not use ecHOSTS services for:

• Hosting illegal content (copyright infringement, piracy, fraud)

• Sending spam, phishing emails, or unsolicited marketing

• Distributing malware, viruses, or harmful scripts

• Performing DDoS attacks or hacking attempts

• Hosting adult or offensive content in violation of the law

📌 Any detected violation may result in immediate action.

⚡ Resource Abuse Rules

To maintain server stability for all users, resource abuse is strictly monitored:

• Excessive CPU, RAM, IO, or NPROC usage beyond your plan limits

• Running background scripts or bots that overload servers

• Using hosting for cryptocurrency mining on shared plans

• Continuous heavy database queries or large-scale file operations

📌 Resource abuse may trigger temporary suspension or throttling.

🛑 Account Suspension Reasons

Accounts may be suspended temporarily or permanently if:

1. Violating the Acceptable Use Policy

2. Causing server instability or affecting other users

3. Non-payment or fraudulent transactions

4. Repeated abuse of resources despite warnings

5. Hosting illegal or unsafe content

Notice & Recovery

• Users will typically receive a warning before suspension

• Support may assist in resolving issues and restoring service

✅ Best Practices for Users

• Monitor your resource usage regularly in Plesk

• Follow the hosting plan limits and upgrade if needed

• Avoid sending bulk emails from shared hosting

• Keep your website secure to prevent malware abuse

• Contact ecHOSTS support for guidance on safe hosting practices

The post 🔹 Acceptable Use Policy (AUP) appeared first on ecHOST.

🧑‍💻 User Responsibilities

As a user of ecHOSTS services, you are expected to:

• Provide accurate contact and billing information

• Keep login credentials secure and private

• Use hosting resources responsibly

• Comply with applicable laws and regulations

• Maintain backups of your own data

📌 Users are responsible for content uploaded to their websites.

⚠️ Service Limitations

ecHOSTS strives to provide reliable hosting, but there are limitations:

• Downtime may occur due to maintenance or unforeseen technical issues

• Resource usage is limited based on your hosting plan (CPU, RAM, storage, etc.)

• ecHOSTS is not liable for data loss beyond backup provisions

• Certain software or scripts may be restricted for security reasons

📌 Upgrades to higher plans may be necessary for higher traffic or resource-intensive websites.

📊 Fair Usage Policy

To ensure all customers enjoy stable and fair service, ecHOSTS enforces fair usage rules:

• Excessive CPU, RAM, IO, or NPROC usage may be temporarily limited

• Spam, phishing, malware, or illegal content is strictly prohibited

• Resource abuse may result in account suspension or service restrictions

• Customers are encouraged to monitor their resource usage regularly

📌 The Fair Usage Policy ensures server performance remains optimal for all users.

✅ Key Takeaways

• Read the Terms of Service carefully before using the hosting services

• Follow guidelines for account security and legal use

• Upgrade hosting plans when needed to meet higher resource demands

• Contact ecHOSTS support for clarification or questions

The post 🔹 Terms of Service (ToS) appeared first on ecHOST.

A staging environment is a private copy of your live website where you can safely test changes before applying them to your main site.

🧪 Creating a Staging Site

A staging site duplicates your live website, including files and databases, into a separate testing space.

How to Create a Staging Site in Plesk (WordPress Toolkit)

1. Log in to Plesk

2. Go to WordPress Toolkit

3. Select your WordPress website

4. Click Clone

5. Choose Staging as the target

6. Create the staging site

📌 The staging site is not visible to search engines or visitors.

🔍 Testing Changes Safely

Use the staging environment to test:

• Theme updates

• Plugin installations

• Design changes

• PHP version updates

• Custom code edits

• WooCommerce updates

Why Use Staging?

• Avoid website downtime

• Prevent broken layouts

• Detect errors early

• Test compatibility issues

📌 Always test major updates in staging first.

🚀 Pushing Staging to Live

Once testing is successful, you can move the changes to your live website.

How to Push Staging to Live

1. Open WordPress Toolkit

2. Select the staging site

3. Click Sync

4. Choose what to copy:

   • Files only

   • Database only

   • Files + Database

5. Confirm and deploy

⚠️ Important:
Syncing the database may overwrite recent orders or content on live sites.

✅ Best Practices for Staging

• Disable search engine indexing on staging

• Use strong passwords

• Avoid sending emails from staging

• Backup your live site before syncing

• Test on multiple devices

❗ Common Issues & Solutions

💡 Who Should Use Staging?

• Business websites

• WooCommerce stores

• Developers & agencies

• High-traffic websites

The post 🔹 Staging Environments appeared first on ecHOST.

Redis and Memcached are object caching systems that dramatically improve website performance by reducing database load and speeding up page delivery.

⚡ What Is Object Caching?

Object caching stores frequently used data in server memory (RAM) instead of loading it from the database every time.

Without Object Caching

• Every page load hits the database

• Slower response time

• Higher server resource usage

With Object Caching

• Data is served from memory

• Faster page loads

• Reduced CPU and database usage

📌 Ideal for WordPress, WooCommerce, and dynamic websites.

🔧 Enabling Redis

How to Enable Redis in Plesk

1. Log in to Plesk

2. Go to Websites & Domains

3. Select your domain

4. Enable Redis (if available on your plan)

5. Install a Redis-compatible plugin (WordPress)

Popular WordPress Plugins

• Redis Object Cache

• W3 Total Cache

• LiteSpeed Cache (if supported)

📌 After activation, always test your website to confirm Redis is working correctly.

🚀 Performance Benefits

Key Advantages

• Faster page load times

• Reduced database queries

• Better performance during high traffic

• Improved Core Web Vitals

• Lower CPU & RAM usage

Best Use Cases

• WooCommerce stores

• Membership websites

• High-traffic blogs

• Large WordPress websites

🆚 Redis vs Memcached

📌 Recommendation: Redis is preferred for most WordPress websites.

⚠️ Important Notes

• Object caching requires compatible hosting plans

• An incorrect setup may cause cache issues

• Clear cache after major website updates

• Not recommended for very small static websites

✅ Best Practices

• Combine Redis with page caching

• Monitor resource usage

• Keep plugins updated

• Disable unused caching systems

The post 🔹 Redis & Memcached appeared first on ecHOST.

Scheduled backups help protect your website by automatically saving copies of your data at regular intervals. If anything goes wrong, you can restore your website in just a few clicks.

🕒 Custom Backup Schedules

With ecHOSTS hosting, you can set backups to run automatically based on your needs.

Available Schedule Options

• Daily backups (recommended for active websites)

• Weekly backups (for low-update sites)

• Monthly backups (basic safety)

What You Can Back Up

• Website files

• Databases

• Emails

• Full account backup

📌 Best Practice:
E-commerce or dynamic websites should use daily backups.

☁️ Remote Backup Storage

Remote backups store your data outside the main server, adding an extra layer of security.

Benefits of Remote Backups

• Protection from server failures

• Safer during malware attacks

• Independent recovery source

Supported Remote Storage

• External backup servers

• Secure cloud backup locations

• Off-site storage managed by ecHOSTS

📌 Even if your hosting account is compromised, your backups remain safe.

🗂️ Backup Retention Policy

Backup retention defines how long backups are stored before being automatically deleted.

Typical Retention Periods

• Daily backups: last 7–14 copies

• Weekly backups: last 4 copies

• Monthly backups: last 1–3 copies

Why Retention Matters

• Saves storage space

• Ensures access to recent and stable backups

• Prevents outdated data clutter

📌 Older backups are removed automatically based on your plan’s retention policy.

🔄 Restoring from Scheduled Backups

You can restore:

• Individual files

• Databases

• Email accounts

• Full website

Restores are fast and can be done directly from the control panel without technical knowledge.

✅ Best Practices for Backup Safety

• Keep at least one off-site backup

• Test restores occasionally

• Avoid manual changes during backup time

• Monitor backup notifications

The post 🔹 Scheduled Backups appeared first on ecHOST.

⏰ What Are Cron Jobs?

A Cron Job is a scheduled task that runs automatically at a specific time or interval on the server.

In simple words:
👉 Instead of manually running a task again and again, cron jobs do it for you.

Examples

• Running WordPress scheduled tasks

• Sending automated emails

• Cleaning old files

• Running backup scripts

• Updating databases

⚙️ Setting Up Scheduled Tasks (Cron Jobs)

How to Create a Cron Job in Plesk

1. Log in to Plesk

2. Go to Websites & Domains

3. Select your domain

4. Click Scheduled Tasks

5. Click Add Task

6. Choose:

   • Command to run

   • Schedule (daily, hourly, weekly, custom)

7. Save the task

📌 Tip: Use absolute paths for files to avoid execution errors.

🧩 Common Cron Job Use Cases

WordPress Cron

Clear Cache Automatically

• Clear cache files at midnight

• Improve website performance

Backup Automation

• Schedule database or file backups

• Useful for large or dynamic websites

Email Automation

• Send reports or notifications

• Process contact form data

E-commerce Tasks

• Order cleanup

• Stock sync

• Subscription renewals

⚠️ Best Practices for Cron Jobs

• Test scripts manually before scheduling

• Avoid running heavy tasks too frequently

• Monitor logs for errors

• Disable unused cron jobs

• Use the proper PHP version if required

❗ Common Cron Job Issues

• Wrong file path

• Incorrect PHP version

• Permission denied errors

• Script timeout issues

📌 If a cron job fails, always check Plesk logs or enable script logging.

The post 🔹 Cron Jobs appeared first on ecHOST.

Logs help identify what’s breaking your website, emails, or applications. They are essential for troubleshooting errors, performance issues, and security problems.

📄 Error Logs in Plesk

Error logs record server-side issues such as PHP errors, permission problems, and failed scripts.

How to Access Error Logs in Plesk

1. Log in to Plesk

2. Go to Websites & Domains

3. Select your domain

4. Click Logs

Common Errors You’ll See

• PHP fatal errors

• File permission issues (403, 500 errors)

• Missing files or incorrect paths

• Plugin or theme conflicts

📌 Tip: Always check the latest timestamp to find the most recent issue.

🐞 WordPress Debug Mode

WordPress debug mode helps identify errors caused by themes, plugins, or custom code.

How to Enable Debug Mode

1. Open wp-config.php

2. Add or update the following lines:

Where Debug Logs Are Stored

• /wp-content/debug.log

When to Use

• White screen of death

• Plugin/theme errors

• Admin panel issues

⚠️ Important: Disable debug mode after troubleshooting to avoid exposing sensitive information.

📊 Access Logs Explained

Access logs record every request made to your website.

What Access Logs Show

• Visitor IP addresses

• Requested URLs

• HTTP status codes (200, 404, 403)

• User agents (browser/device)

• Request time and load duration

Why Access Logs Matter

• Identify broken links (404 errors)

• Detect unusual or malicious traffic

• Analyze traffic patterns

• Debug redirect issues

📌 Example Use Case:
If users report missing pages, access logs can confirm whether the page exists or returns a 404 error.

✅ Best Practices for Log Analysis

• Always check logs immediately after an error occurs

• Clear logs periodically to avoid clutter

• Share error logs with support when opening a ticket

• Avoid editing files directly without checking logs first

The post 🔹 Logs & Debugging appeared first on ecHOST.

🐢 Common Causes of Slow Loading

Website-Level Issues

• Large, unoptimized images

• Too many plugins or heavy themes (especially WordPress)

• No caching enabled

• Excessive JavaScript & CSS files

• Poorly optimized database

Server-Level Issues

• Low CPU / RAM limits (shared hosting)

• High server load from other users

• Slow disk I/O

• No server-side caching

• Outdated PHP version

🖥️ Server Optimization vs 🌐 Website Optimization

🖥️ Server Optimization (Hosting Side)

• Upgrade PHP version (8.0 / 8.1 recommended)

• Enable OPcache

• Use SSD/NVMe storage

• Increase CloudLinux resources (CPU, RAM, IO)

• Enable server-level caching (LiteSpeed / Redis)

• Use HTTP/2 or HTTP/3

📌 Best for: High-traffic sites, eCommerce, dynamic websites

🌐 Website Optimization (Developer Side)

• Enable caching plugin (LiteSpeed Cache, WP Rocket, W3 Total Cache)

• Optimize images (WebP format)

• Minify CSS, JS, HTML

• Reduce unused plugins & scripts

• Clean the database regularly

📌 Best for: WordPress, CMS-based websites

🔍 Performance Testing Tools

Speed Testing

• Google PageSpeed Insights

• GTmetrix

• Pingdom Tools

Server & Real-Time Monitoring

• cPanel → Resource Usage

• CloudLinux LVE Stats

• New Relic / Query Monitor (advanced)

What to Check

• Time to First Byte (TTFB)

• Largest Contentful Paint (LCP)

• Fully Loaded Time

• Server response time

✅ Best Practices to Improve Speed

• Use CDN (Cloudflare)

• Enable browser & server caching

• Optimize images before upload

• Upgrade hosting if resources are consistently maxed

• Keep themes, plugins & PHP updated

The post 🔹 Website Speed Issues appeared first on ecHOST.