Skip to policies
Brightery WordPress products

Clear policies.
Better plugin experiences.

These policies explain how Brightery licenses, updates, supports and maintains its WordPress plugins—so you know what to expect before, during and after installation.

Effective date 21 July 2026Applies to Brightery WordPress pluginsLanguage English
Brightery Plugin Center
Policy active
Policy overviewBuilt around clarity
12 sections
01GPL-compatible licensingClear rights and product-specific terms
02Updates & compatibilityActive licenses receive eligible releases
03Support boundariesPlugin help without hidden expectations
04Privacy by designTransparent data and service disclosures
Security reportsPrioritized
Policy changesPublished
Third-party servicesDisclosed
At a glance

The essentials, without the fine-print fog.

This summary helps you understand the intent of the policy. The detailed sections below control where the summary and full text differ.

Security

Responsible reports are welcome.

We prioritize verified vulnerabilities, protect reporters acting in good faith and publish fixes or guidance when appropriate.

Licensing

Your license defines updates and support.

Open-source rights and commercial services are explained separately.

Updates

Compatibility is maintained, not promised forever.

We test supported versions and communicate major lifecycle changes.

Support

We support the plugin—not every part of your website.

Support covers installation, documented functionality and reproducible plugin defects. Custom development, hosting administration and unrelated third-party conflicts may require a separate service.

Policy framework

How Brightery WordPress plugins are provided and maintained.

These WordPress Plugin Policies form part of the agreement between Brightery and the person or organization that downloads, purchases, installs or uses a Brightery plugin. They supplement our Terms of Use and Privacy Policy.

01
Scope and agreement

Which products and users are covered

These policies apply to WordPress plugins developed, published, sold or distributed by Brightery through Brightery websites, approved marketplaces, private delivery channels or the WordPress.org Plugin Directory.

By downloading, purchasing, activating or using a plugin, you confirm that you have authority to accept these policies for yourself or the organization you represent. Product-specific terms shown on a product page, checkout screen, license notice or marketplace listing also apply. Where product-specific terms conflict with this general policy, the more specific terms control.

This policy does not govern third-party plugins merely recommended, integrated or referenced by Brightery.

02
Licensing and ownership

Open-source code and commercial services are different layers

Unless a product states otherwise, Brightery WordPress plugin PHP code is distributed under the GNU General Public License or another WordPress-compatible license. The applicable license notice included with each plugin defines your rights to use, study, modify and redistribute covered code.

A commercial license key, subscription or purchase may separately control access to services such as automatic updates, premium downloads, cloud features, support, templates, licensed media, account features or private repositories. Expiry of those commercial services does not retroactively remove rights granted under the open-source license, but it may end access to those additional services.

  • You may not falsely claim authorship, official endorsement or ownership of Brightery branding.
  • Brightery names, logos, documentation, product artwork and non-code assets remain protected unless expressly licensed.
  • License activation limits, if any, are shown on the relevant plan or product page.
03
Installation and activation

Your environment must meet the published requirements

You are responsible for maintaining a secure, supported WordPress environment, including appropriate hosting, PHP and database versions, valid administrator access, backups and any dependencies stated in the plugin documentation.

Before installing or updating a plugin on a production website, you should create a current backup and test significant changes on a staging environment. Brightery is not responsible for loss caused by missing backups, unsupported server configurations, direct file modification or installation methods that bypass documented procedures.

Use a staging website Keep a verified backup Review requirements Protect administrator access
04
Updates and compatibility

We maintain supported releases through a defined lifecycle

Eligible customers with an active license or subscription may receive updates through the method described for the product. Updates may include security fixes, compatibility changes, defect corrections, improvements, new features or removal of obsolete functionality.

Brightery aims to support currently maintained versions of WordPress and the product dependencies listed in the documentation. Compatibility with every theme, plugin, hosting stack, browser, custom codebase or future WordPress release cannot be guaranteed.

  • We may require a minimum WordPress, PHP, database or dependency version for security or maintainability.
  • Major changes may require configuration updates, migrations or template adjustments.
  • Automatic updates can fail because of hosting permissions, firewalls, expired licenses or third-party update blockers.
  • Security fixes may be released without adding new features to older product branches.
05
Support policy

What standard plugin support includes

Support availability, duration and channels depend on the product and plan. Unless otherwise stated, standard support is limited to installation guidance, documented configuration, explanation of existing features and investigation of reproducible defects in an unmodified supported release.

Included
  • Plugin installation and activation questions
  • Documented settings and functionality
  • Reproducible bugs in supported versions
  • License and update delivery issues
  • Reasonable troubleshooting guidance
Not standard support
  • Custom features or bespoke integrations
  • Hosting, DNS, email or server administration
  • Repairing unrelated themes or plugins
  • Training entire teams or managing content
  • Support for modified or pirated copies

To investigate efficiently, Brightery may request logs, screenshots, system information, temporary staging access or steps that reproduce the issue. Never send production passwords through an insecure channel. Remove or rotate temporary credentials after the investigation.

06
Data and privacy

Plugins should be transparent about the data they handle

Each plugin's documentation or privacy notice should explain material data collection, external transmission, cookies, remote services and user-facing privacy features relevant to that product. Where a plugin sends information to Brightery or another service, that transfer should be disclosed in the relevant product documentation.

As the website operator, you are responsible for configuring the plugin lawfully, maintaining an accurate website privacy notice, responding to data-subject requests, obtaining required consent and selecting retention settings appropriate for your jurisdiction and business.

Diagnostic information voluntarily shared with support may contain website configuration, plugin versions, error logs, URLs, user identifiers or other technical data. Brightery uses that information to provide support, protect the service and improve products in accordance with the Brightery Privacy Policy.

07
Security and responsible disclosure

Report vulnerabilities privately before public disclosure

If you believe you discovered a vulnerability in a Brightery plugin, contact Brightery privately with the affected product, version, technical impact, reproduction steps and any safe proof of concept. Do not access data that is not yours, disrupt live services, use social engineering or publicly disclose an unresolved issue before Brightery has had a reasonable opportunity to investigate and release guidance.

Good-faith reports that follow these boundaries will be reviewed and prioritized according to severity, exploitability and affected users. Brightery may coordinate a fix, mitigation, advisory, release timeline or responsible disclosure date with the reporter.

Submit a security report
08
Third-party services and dependencies

Integrations remain subject to their own providers

Some plugins integrate with payment gateways, messaging providers, artificial intelligence services, analytics tools, content delivery networks, marketplaces, APIs or other external services. Your use of those services is also governed by the third party's terms, privacy practices, availability, pricing and technical limits.

Brightery does not control third-party outages, API changes, account suspensions, rate limits, discontinued features or policy changes. We may update or remove an integration when continued support is insecure, unlawful, technically impractical or no longer commercially reasonable.

09
Purchases, renewals and refunds

Commercial terms are shown before purchase

Prices, billing periods, renewal settings, taxes, license limits and refund eligibility are determined by the checkout page, product-specific terms, marketplace rules and applicable law. Where a marketplace processes the payment, its refund and billing procedures may apply.

Before requesting a refund for a technical issue, customers should provide Brightery with sufficient information and a reasonable opportunity to reproduce or resolve the problem. A change of preference, failure to review requirements, unsupported customization or third-party service issue may not qualify for a refund unless required by applicable law or expressly allowed by the product terms.

10
Acceptable use

Use plugins lawfully and without harming others

You may not use a Brightery plugin, license service, update system, support channel or hosted feature to violate law, infringe intellectual property, distribute malware, facilitate fraud, bypass access controls, attack systems, harvest data unlawfully, send prohibited communications or misrepresent affiliation with Brightery or WordPress.

Brightery may limit or suspend access to hosted services, license infrastructure or support where reasonably necessary to investigate abuse, protect systems, comply with law or enforce applicable terms. Where practical, Brightery will provide notice and an opportunity to correct the issue.

11
Product lifecycle

Features and products may evolve or reach end of life

Brightery may rename, redesign, combine, replace, discontinue or stop supporting a plugin, feature, integration or legacy version. When a material discontinuation affects an actively supported commercial product, Brightery aims to provide reasonable notice through the website, account area, release notes, email or product documentation.

End-of-life products may remain usable under their applicable open-source license, but Brightery may stop providing downloads, compatibility work, cloud services, security updates, technical support or update infrastructure after the announced date.

Our operating principles

Software policies should build trust—not hide surprises.

Brightery aims to make each plugin's requirements, data handling, support boundaries and lifecycle understandable before customers depend on it.

01Clarity before activation

Material requirements and external services should be disclosed.

02Security over convenience

Unsupported technology may be retired when it creates avoidable risk.

03Responsible maintenance

Updates focus on stability, compatibility and sustainable product quality.

Common questions

Plugin policy FAQs.

These answers summarize the policy and do not replace product-specific terms.

Open-source rights granted by the plugin's software license generally remain, but access to commercial updates, support, cloud features or premium downloads may end when the commercial license expires.

No. Standard support focuses on documented features and reproducible plugin issues. Custom workflows, integrations, redesigns and site-specific development require a separate scope.

No plugin can guarantee universal compatibility. Brightery supports the environments and dependencies stated in the product documentation and investigates reproducible conflicts in supported configurations.

Include the plugin name and version, affected configuration, impact, reproduction steps and a safe proof of concept. Submit the report privately and avoid accessing data or systems you do not own.

The marketplace's billing and refund process may control the transaction. Review the terms shown on the marketplace listing and checkout page before purchasing.

Still have a policy question?

Talk to the team behind the plugin.

Share the plugin name, license email and a clear description of your question so Brightery can route it correctly.

Contact Brightery