Terms of Service

1. Introduction and Scope of Agreement

Welcome to Mega Plugin Hub. These Terms of Service constitute a legal agreement governing your access to and usage of our marketplace portal, licensing network, software downloads, updates, API services, and client dashboards. By registering an account, purchasing premium licenses, downloading codebase packages, or uploading files to the directory, you accept all guidelines. If you act as an employee or agent for a company, you represent that you hold full authorization to bind that company to these terms.

By creating an account, purchasing premium products, or uploading code files to our servers, you represent that you have reached the age of majority in your jurisdiction. Mega Plugin Hub reserves the right to suspend accounts displaying terms violations without warning.

All resources, databases, software, and document panels provided are subject to these rules. The platform coordinates operations through local edge servers to optimize availability.

Users are responsible for maintaining account authentication details securely. In the event of an account compromise, immediate notification must be sent to platform administrators.

We advise that these terms are updated periodically to adapt to changing legal requirements and database structures. By continuing to use your account after an update is published, you agree to the new version of our Terms of Service in full.

If you do not agree to these terms, please stop using our marketplace services, delete your active license codes, and deactivate our plugins from your WordPress websites immediately.

2. Platform Definitions

In these terms: "Platform," "we," "us," or "our" refers to Mega Plugin Hub; "Buyer" or "Customer" refers to individuals purchasing license keys or subscriptions; "Author" or "Vendor" refers to developer members who submit plugins or addons to our directory; "Plugin" or "Software" refers to the WordPress plugins, themes, or extensions listed; and "License Key" refers to the verification string mapped to domain allowances.

All references to "Plugin" or "Software" include the source files, graphics, stylesheets, templates, and documentation provided. "License Activation" refers to verifying key validity on a single WordPress database instance.

The term "Connected Site" describes a self-hosted WordPress node that has established a secure API connection with our licensing servers. "Options Sync" refers to the automatic configuration transfer feature.

A "Wallet Account" is the virtual ledger inside an Author dashboard that tracks cumulative sales credits before bank payout extraction.

1. The Marketplace Model

Mega Plugin Hub functions as a digital marketplace intermediary. We provide payment gateway integration, secure user dashboards, automated license validation networks, and a remote settings synchronization pipeline. The actual contract of sale and licensing of the software is formed directly between the independent Author listing the software and the Buyer completing the checkout.

Authors retain intellectual property ownership of their uploaded files. Mega Plugin Hub is not a party to the license agreement formed between the Buyer and the Author regarding plugin operations.

The Platform manages transaction clearing systems. Fees and split ledger values are audited weekly by automated accounting loops.

Buyers access purchased files directly from client dashboard download tables. Access is restricted to the specific account that completed checkout.

2. General Public License (GPL) Compliance

All WordPress plugins, themes, and extensions distributed via the Platform's catalog inherit the GNU General Public License (GPL) version 2.0 or later. While the PHP source code is open source, access to premium API infrastructure, the automated dashboard update loop, remote settings sync mechanisms, and support ticket queues is reserved exclusively for users with active, validated subscriptions.

While GPL guarantees code redistribution rights, you acknowledge that access to automated update routes and Remote Option Sync is restricted to active licensing subscriptions.

GPL allowances apply only to the codebase files. Supplementary assets including brand layouts, logos, trademarks, and documentation files remain protected under standard copyrights.

Redistribution of premium plugin keys violates account guidelines. Blacklisted keys suspend connection operations on all connected sites.

Derivative plugins built from code obtained on the platform must comply with GPL licensing. Authors must register derivative works under matching open-source rules.

GPL code rights do not obligate Authors or the Platform to host or maintain active updates for derivative copies.

We protect Author intellectual property from direct trademark abuse. Derivative plugins cannot use the exact names or logos of original listings.

If a user redistributes codebase assets to external repositories, support and updates for their origin account are terminated instantly.

We configure database checks to verify whether client sites are running authentic plugin files. Modified codebases displaying structural changes are flagged by our support teams.

The GPL license allows you to inspect the source code files for educational purposes. We encourage community developers to audit open-source components for security and optimization standards.

Please note that if you package and resell a plugin obtained from our marketplace, you must clearly state that you are not affiliated with the original Author or Mega Plugin Hub, and that you do not offer official support queues.

Lastly, code contributions made to our repository by community developers are subject to automatic GPL licensing transfers upon pull request mergers.

3. Entitlement Assets and Licenses

Upon checkout, the Platform generates a unique, cryptographically signed License Key for the purchased plugin. This key belongs to the Buyer's account. Keys must not be shared or redistributed. If a key is distributed on public forums or shared outside of the designated developer team, the Platform reserves the right to terminate the key without refund.

The Platform reserves the right to audit license activations. Sharing keys on discount websites or public repositories will lead to immediate key blacklist status.

4. Domain Allowances and Verification

Each license tier grants a maximum number of concurrent domain activations ("Domain Allowance"). Our API validates requests from connected sites. Domain allocations can be managed or revoked by the Buyer within their dashboard. If a domain is deactivated, its settings sync and automatic updates cease immediately.

Connected site activations must use valid domain patterns. If the domain format is invalid (e.g. testing layouts), the activation might be flagged as temporary.

Verification scans check host namespaces periodically. Subdomains mapped to local developer systems (such as localhost or .test) do not count against limits.

If domain migrations occur, buyers can transfer allocations from their dashboard. Transfers execute instantly upon confirmation.

API calls checking domain validity use encrypted transport headers. Mismatched hashes terminate the activation loop.

Domain allowances represent concurrent sites. Active license checks verify active domain allocations before delivering ZIP files.

If an activation limit is exceeded, subsequent activation pings return diagnostic block messages. License upgrades are available via dashboards.

We archive domain logs to prevent license key fraud. Domain history records are purged upon license deletion.

For instance, if you purchase a 5-domain license tier, you can link exactly 5 production WordPress sites simultaneously. Testing or staging environments running on standard ports (such as 8080 or 3000) are automatically whitelisted without utilizing slots.

Our licensing API runs quick ping queries. If a server goes offline permanently, the slot is released automatically after 7 days of non-response.

Please make sure that your client domains are configured correctly in the panel. Incomplete domain names (e.g. leaving out TLDs) block update validation.

We do not inspect visitor IPs or tracking statistics on connected domains. The check query reads only the domain URL string and license key hash.

5. License Key Misuse and Piracy

We enforce zero-tolerance policies for license key misuse, including loading keys into "nullified" plugin versions, resale of activations on third-party forums, or using automated script loops to request updates for multiple unauthorized domains. Violating keys will be blacklisted automatically.

We run automatic detection scans to block keys linked to scraping actions. Legitimate users can request key reactivation if blocked erroneously.

Nullified version detection triggers automatic key blacklist alerts. Suspended keys cannot be restored except by compliance officer review.

Automated loops querying update endpoints are flagged by security systems. Scraping accounts face permanent portal blocks.

We trace IP patterns checking API configurations. Proxy networks attempting to validate invalid keys are blocked by firewalls.

Reselling keys under corporate license tiers is strictly prohibited. Violating vendors face contract de-registrations.

1. Periodic Subscription Fees

Premium plugins are billed on a recurring subscription basis (weekly, monthly, or yearly) or via a one-time lifetime fee. Prices are shown in regional currencies. Subscriptions are billed at the start of each period and grant continued access to updates and synchronization APIs during that period.

Subscription fees are processed automatically at the start of each billing cycle. If you cancel your subscription, updates and sync operations remain active until the period ends.

Pricing parameters are adjusted based on market criteria. Current active subscriptions are locked against inflation changes.

If account balances display arrears status, sync hooks are suspended. Renewals payment clears historical balances.

2. Automatic Renewal Protocol

By subscribing, you authorize us to collect recurring renewal fees through Stripe or Razorpay. Renewals occur automatically unless you disable auto-renewal in your dashboard before the renewal date. If a renewal payment fails, we allow a 3-day grace period before update access and settings sync are suspended.

Auto-renewal notifications are sent via email 7 days before charging. Failed charges are retried up to 3 times before subscription suspension.

3. Taxation and Compliance (GST/VAT)

Platform prices are exclusive of tax unless noted. Tax registration values (such as GSTIN for India or VAT for European Union) must be supplied during checkout. Invoices are generated as tax-compliant documents and cannot be edited retroactively once issued.

Tax calculation follows checkout location rules. Authors are responsible for filing local income tax returns on their payouts.

1. Escrow, Commissions, and Splits

Mega Plugin Hub processes all customer checkouts and retains a transaction fee commission (defined in the Author terms). The remaining split is automatically calculated and credited to the Author's vendor ledger. All transaction splits are subject to audit logs.

Payout logs display transaction values and commissions subtracted. The Platform details fee splits on all vendor invoices.

2. Author Wallet Accounts

Author earnings are tracked in an internal virtual wallet. To protect the marketplace from refund requests and payment chargebacks, earned funds are subject to a standard holding period (e.g. 14 days) before they become available for withdrawal or payout execution.

Wallet balances do not accrue interest. The Platform reserves the right to freeze balances linked to active dispute tickets.

3. Payout Processing and Verification

Available wallet balances are disbursed to Authors on designated payout days, subject to a minimum withdrawal amount. Authors must supply verified payout details and complete identity verification checklines in compliance with global anti-money laundering regulations.

Payouts are executed via direct bank transfer or PayPal. Payout parameters can be updated from the vendor dashboard panel.

Identity verification checks are processed by automated sub-processors. KYC documents are pruned once validation completes.

Tax residency certificates must be uploaded to avoid default withholding rates. Withheld balances are sent to local tax departments.

Payout delays caused by banking system outages are logged on status pages. We execute delayed payouts immediately upon system recovery.

1. Refund Policy for Buyers

We offer a 14-day refund window for initial subscription checkouts. To qualify, you must demonstrate that the software fails to install, exhibits critical bugs, or breaks your server environment, and that you have opened a support ticket and allowed the Author 14 days to debug it. Renewals and lifetime purchases are non-refundable.

Refund requests based on change of mind, feature misunderstandings, or hosting limitations are rejected. We verify technical issues prior to refund approvals.

Technical logs showing plugin errors must accompany refund tickets. Logs are checked by support agents to confirm system conflicts.

Refunds are processed to the original payment method only. We cannot issue refunds to different cards or bank accounts.

Refund approvals deduct the entire split amount from the vendor's wallet ledger. Disputes must be opened via vendor panels.

Renewals are excluded from refunds because subscription cancel features are available inside client dashboards at any point.

Excessive refund requests (e.g. purchasing and refunding 3 items in a month) flag accounts for manual checkouts audits.

Approved refunds terminate corresponding license keys instantly. Option syncing settings are wiped from server records.

Transaction processing fees charged by payment gateways are non-refundable. Refund values equal the net purchase price.

If you purchase a product and request a refund because it lacks a specific feature not listed on its description page, your request will be rejected. Please review product details carefully before completing checkout.

Refund disputes are settled directly between support leads and customers. Authors are notified of the outcome via automated ledger alerts.

If a buyer executes a chargeback via their bank instead of submitting a ticket, we black list the account and block all active license keys immediately.

Staging environments running on custom configurations must be documented inside refund requests. Compatibility checks are required.

If you request a refund because of conflict with a third-party nulled plugin, your request will be rejected. We support only standard repositories.

We run automated diagnostics on support logs before processing refund tickets. Resolved bugs terminate refund claims.

2. Refund Dispute Resolution

If an Author disputes a refund request, the Platform acts as the sole arbitrator. We review the server compatibility logs and support history. If a refund is approved, the amount is deducted from the Author's wallet balance.

Arbitration outcomes are final and binding. Deducted refund amounts reflect on subsequent vendor wallet balances.

1. Author Listing Guidelines

Authors must submit high-quality descriptions, accurate tags, and transparent screenshots. The plugin name, category, and readme.txt contents must represent the plugin features honestly. Obfuscated code, external tracking scripts, or non-functional links are prohibited.

Listing titles must be unique. The Platform reserves the right to edit descriptions displaying grammatical issues or trademark violations.

2. Author Code Quality & Security Policy

Every plugin uploaded to our directory undergoes initial code reviews. Plugins must not contain malware, backdoors, hidden advertisements, or obfuscated PHP commands (e.g. eval or double base64 encodings). Authors must fix security bugs immediately upon discovery.

Plugins displaying security bugs will be suspended from the directory immediately. Authors must push hotfixes within 48 hours to restore status.

Static analysis testing tools check code for deprecated functions and SQL injection vectors. Flawed code blocks upload attempts.

Manual verification checks run on all initial uploads. Code quality leads verify option saving scripts manually.

Telemetry tracking functions must display active opt-in prompts to site visitors. Hidden collection scripts trigger platform bans.

Database queries must use WordPress db-prepare routines. Raw query injections block the listing approval process.

Authors must use secure password APIs when configuring custom access levels. Local password caching is prohibited.

Zero-day security reports trigger automatic plugin deactivation. Author alerts are dispatched via email nodes instantly.

We check code files using standardized tools like PHP_CodeSniffer with WordPress Coding Standards. Listings with many syntax notices are rejected.

Plugins must use custom namespaces or unique function prefixes to prevent execution conflicts on customer databases.

If you include third-party scripts (such as JavaScript tracking blocks or font packages), they must be loaded locally. Loading assets from unsecured external CDNs is blocked.

Lastly, codebase uploads must not exceed 50MB. Large file directories must use external mirrors or split package archives.

Obfuscated code checks run on nested PHP directory targets. If our scanner detects complex encoding variables, it blocks release pings.

We verify option validation filters before updating version endpoints. Options configurations must match database models.

Authors must exclude node_modules or source build scripts from ZIP distributions. Archive packages must contain build code files only.

3. Gating Premium Features

Authors who offer freemium plugins must use clean coding gates to separate free features from pro features. Pro features must check license status using our local license queries to prevent unauthorized execution.

Premium blocks must check license activation loops. Bypassing check processes violates Author guidelines.

4. Plugin Updates Distribution

When an Author publishes a new release (stable or beta), the Platform packages the ZIP and updates the JSON meta endpoint. Connected sites verify their license key and download the ZIP from our edge servers. Authors must ensure all releases are stable.

Connected sites receive update alerts dynamically. The updates API checks target site WordPress versions before downloading files.

1. Remote API Webhook Sync Services

When a Buyer edits settings in the Hub, our server sends a REST API sync request to the connected site's endpoint. By installing our plugins, the Buyer authorizes this synchronization. We do not download or copy database tables - sync actions only persist option arrays.

Option sync uses HTTPS pings to write option variables. Options are validated before saving to prevent corrupting database structures.

Sync loops run asynchronously to avoid impacting website performance. Sync latency logs trace average network connection limits.

If database option writes fail due to server memory limits, the sync loop queues retries for a 5-minute cooldown interval.

2. X-Mega-License Signature Checks

To prevent unauthorized remote settings changes, all incoming webhook requests to connected sites must include the X-Mega-License header. Connected sites check this signature before saving settings.

Signatures are computed using key hashes. Requests with invalid signatures are dropped immediately by site endpoints.

Signature validation scripts verify timestamp variations to block replay attacks. Webhooks with expired stamps terminate instantly.

Security logs record invalid headers histories locally. IP nodes displaying continuous mismatch errors block at server firewalls.

3. Database Snapshot Backups

Our database optimization plugins include safety snapshots. Before executing a cleanup, the plugin clones metadata table rows into local custom tables. You are responsible for ensuring your database engine has adequate local storage capacity.

Snapshot database files are saved in local WordPress directories. The plugin does not read or save user records during cleanup.

4. Safety Vault Storage Exclusions

Local backups stored in the Safety Vault are stored on your server, not on our Hub. If you delete your WordPress site or drop the custom vault tables, backup snapshots are lost. We do not store backups of your site contents.

You must verify hosting storage limits before starting backups. The Platform is not liable for data loss caused by local server space runs.

5. PageSpeed Analytics Integration

Our performance plugins query PageSpeed APIs. By enabling PageSpeed analytics, you authorize the plugin to query scores for your public pages. These results are processed on our servers to render health metrics in your dashboard.

PageSpeed data collection runs asynchronously. Analytics charts are rendered in the portal dashboard once scans complete.

6. Uptime and Site Sync Scans

Connected sites are pinged periodically to check connection status. We trace uptime metrics, database overhead sizes, and blocked threats. This diagnostics data is aggregated on our servers to display connection health.

Uptime tests happen every 5 minutes. Scans can be disabled from settings, which stops uptime charts rendering.

1. Support SLA Limits

Support is provided to active premium subscription holders only. We provide assistance for plugin configurations, bugs, and updates. We do not offer support for custom theme integrations, custom coding, or general hosting management.

Support tickets are handled in order of submission. Support agents do not resolve server-side memory leaks or custom theme conflicts.

Support is restricted to English. Standard tickets receive replies within 24 business hours; premium plans priority is 4 hours.

Providing staging database details accelerates bug tracking. We recommend changing passwords once support calls conclude.

We do not write custom scripts or layout styles under support terms. Customizations must be acquired independently.

If you transfer license keys to client dashboards, support eligibility applies strictly to the primary buyer account.

We do not configure local firewall scripts or DNS parameters. Network routing errors are hosting provider responsibilities.

2. Direct Support Channels

Support requests must be opened through our portal dashboard ticket system. Support emails are traced in compliance with our support queue priorities. Sharing account passwords in tickets is prohibited.

Tickets requesting login credentials must use secure fields. Providing passwords in standard ticket text is at your own risk.

3. Developer-Buyer Direct Interactions

For complex bugs, the Platform may connect the Buyer with the Author. Any exchange of staging credentials or site access is done at the Buyer's discretion. The Platform is not liable for actions taken by Authors on Buyer servers.

The Platform does not supervise external interactions. We recommend utilizing secure staging environments for all code testing.

1. Prohibited Plugin Functionality

Plugins listed on our marketplace must not inject advertisements, redirect admin pages, show unrelated review popups, or perform stealth cryptocurrency mining. Violations will result in immediate plugin removal.

Violating plugins are removed from the directory immediately. Serious code violations will result in vendor account suspensions.

2. Copyright and DMCA Enforcement

We respect intellectual property. If you believe code on our Platform infringes your copyright, submit a DMCA takedown request to support@megapluginhub.com. We will remove the content and review the Author's account status.

Authors must provide proof of ownership if flagged for review. Code found in violation is removed within 24 hours.

DMCA notices must include copyright owner details, specific URLs of infringing listings, and declaration of ownership.

Filing false DMCA claims faces penalty processing. We lock accounts found creating repeated false copyright tickets.

Compliance teams mediate copyright ticket dispute files. Mediation files close within 14 business days of ticket logs.

3. Trademark Representation Guidelines

Authors must respect the trademarks of WordPress, WooCommerce, and other companies. Plugin names must use "for WordPress" or "for WooCommerce" formats and avoid using protected brand names as main identifiers.

Authors must include trademark disclaimers on listing pages. The Platform updates trademark tags to prevent customer confusion.

1. Third-Party Sub-Processors

We engage trusted sub-processors for payments, hosting, and email notifications. These sub-processors are governed by their own policies. By using our platform, you authorize these integrations.

Sub-processor operations comply with GDPR regulations. You can review sub-processor terms on their official websites.

2. Indemnification of the Platform

You agree to indemnify, defend, and hold harmless Mega Plugin Hub, its directors, developers, and partners from any claims, damages, losses, or legal costs arising from your use of the Platform or your breach of these terms.

Indemnity rules survive agreement termination. Users agree to settle claims independently of platform operations.

3. Platform Downtime & Outages

We make reasonable efforts to maintain platform uptime. However, we do not warrant that our servers, API updates, or settings sync will be online 100% of the time. We are not liable for losses caused by service downtime.

Maintenance operations are scheduled during low-traffic periods. System status updates are published on our status page.

4. Data Erasure & Portability

Buyers and Authors can request account deletion at any time. Upon deletion, we erase personal identifiers, except where tax laws require retaining billing records. Connected sites settings remain on the hosting server but sync ends.

Tax logs remain archived separately. Site database options remain intact, but automated updates stop working.

5. Severability and Entirety of Contract

If any clause of these terms is found invalid, the remaining terms continue in full force. These terms represent the entire agreement between the parties regarding the use of the marketplace platform.

Terms updates happen periodically. Continued use of our plugins constitutes acceptance of updated marketplace policies.

6. Force Majeure Exclusions

Mega Plugin Hub is not liable for failures or delays in service delivery caused by circumstances beyond our reasonable control, including grid failures, server host blackouts, internet connectivity outages, acts of God, or government restrictions.

Outages caused by third-party data center failures are covered under force majeure. We restore services as soon as backups activate.

7. Arbitration & Dispute Resolution

These Terms of Service are governed by local laws. Any disputes, claims, or controversies shall be settled through binding arbitration in our local jurisdiction before resorting to court proceedings.

Arbitration hearings happen in our local city. Users waive rights to participate in class-action lawsuits against the Platform.

Arbitration claims must file within 1 year of action triggers. Filing claims after limits expire blocks hearings.

We recommend direct support negotiation prior to initiating arbitration loops. Tickets verify early negotiation tries.

Each party covers personal legal processing costs during arbitration. Shared administration fees split equally by default.