Software Licensing
This page explains how open-source licences, product-specific permissions, Veyra branding, documentation, updates, support and future connected services relate to Veyra software.
Who publishes Veyra software?
Unless a product notice identifies another rights holder, Veyra software is published by:
- Legal name
- [[LEGAL NAME OF THE SOFTWARE PUBLISHER]]
- Trading name
- Veyra Apps
- Business address
- [[PUBLIC BUSINESS OR PROFESSIONAL ADDRESS]]
- Country of establishment
- Spain
- General contact
- hello@veyraapps.com
- Product support
- support@veyraapps.com
Replace the legal-name and public-address placeholders with the verified publisher details used across the Legal Notice and other legal documents.
What this page does—and does not do
This page provides a public explanation of the licensing structure used across Veyra software. It helps users distinguish between rights in source code and access to updates, support, licence keys, hosted services, documentation and brand assets.
It does not replace the licence included with a product. Where this page and a product’s licence file conflict regarding permissions in the software package, the product’s licence file and applicable mandatory law control.
Product pages, order details or plan descriptions may add commercial conditions relating to delivery and services without reducing rights already granted under the applicable open-source licence.
Always check the licence included with the software
Each Veyra software package should identify its licence through the product header, readme, licence file, package metadata or equivalent notice.
The included notice determines matters such as:
- Whether the software may be used, studied, modified and redistributed.
- Whether source code and licence notices must accompany redistributed copies.
- Which licence must apply when modified or derivative versions are distributed.
- Any attribution, notice or source-availability requirements.
- Warranty and liability disclaimers contained in that licence.
Users and redistributors are responsible for reading and complying with the exact licence applying to the version they receive.
GPL-compatible distribution in the WordPress ecosystem
WordPress itself is distributed under the GNU General Public License version 2 or any later version. Veyra products distributed through the official WordPress.org directories will use a GPL-compatible licence and will declare that licence in the product package.
Code, data, images and included third-party materials placed in a WordPress.org plugin package must be compatible with the directory’s licensing requirements.
Code permissions
Open-source licenceThe applicable GPL-compatible licence grants rights in the software code according to its own terms.
Commercial services
Separate layerDistribution, automatic updates, support, account services and hosted functionality can be offered separately from the code licence.
Brand identity
Separate rightsAn open-source code licence does not automatically authorise misleading use of Veyra names, logos or product identity.
Third-party licences
Retained noticesLibraries and other included materials remain subject to the compatible licences and notices identified by their rights holders.
Rights granted by a GPL-compatible package
Subject to the exact licence included with the package, users may generally install and run the software for any lawful purpose, inspect its source code, modify it and redistribute original or modified copies.
Those permissions arise from the software licence itself. They are not dependent on maintaining a support plan or purchasing automatic updates unless a separate service is required to access those particular delivery channels.
Nothing on this page is intended to remove or narrow rights that the applicable open-source licence grants directly to the recipient.
Responsibilities when sharing copies or modifications
A person who redistributes Veyra software must comply with the licence included with that software. Depending on the licence and the way the software is distributed, obligations may include:
What an open-source code licence does not automatically include
Access to an official update server, private repository or customer download area may depend on the product channel or an active commercial plan.
Installation guidance, troubleshooting, response targets and priority assistance are services whose scope can vary by product and plan.
APIs, cloud storage, online applications, processing capacity and account features may be governed by separate service and acceptable-use terms.
Veyra logos, product marks, promotional artwork and distinctive brand presentation are not automatically licensed for unrestricted commercial branding.
Website copy, commercial documentation, tutorials, screenshots and design assets remain subject to their own notices unless a reusable-content licence is expressly stated.
Veyra Custom Content Manager
Current licensing position
Veyra Custom Content Manager is the first public Veyra product. Its exact software licence, copyright notice and third-party acknowledgements must be taken from the version-specific package distributed to the user.
The public product page and documentation should link to the current package licence and repository whenever those locations are available.
Future paid access can package services around open-source software
A future commercial product or plan may charge for convenient delivery, automatic updates, licence-key management, official support, premium documentation, proprietary remote services or access to additional products.
Where the distributed software code is licensed under the GPL or another open-source licence, payment does not remove the software freedoms granted by that licence. The commercial agreement instead defines access to the additional services, channels and benefits described at purchase.
Free public software
Distributed under the licence included with the package, through the channels identified on the product page.
Commercial product access
May include private downloads, official updates, plan-based support and licence management after the model is defined.
Hosted and proprietary services
May require separate account, subscription, usage and service terms that will be published before activation.
Before paid products launch, replace this note with the final licence-plan matrix: [[FREE / SINGLE SITE / MULTI-SITE / AGENCY / SUBSCRIPTION / LIFETIME DECISIONS]].
Installation rights and service activations are not always the same
An open-source licence may allow the software code to be installed and used without a contractual site limit. A commercial plan may still limit the number of websites that can receive automatic updates, official support, licence activation or connected services.
Development, staging, local and production environments will be treated according to the plan description published for the relevant commercial product.
Complete the following decisions: [[NUMBER OF ACTIVATIONS]], [[STAGING AND LOCAL RULES]], [[MULTISITE TREATMENT]], [[CLIENT-SITE TRANSFERS]] and [[DEACTIVATION / REACTIVATION PROCESS]].
Maintenance channels can vary by product
Free products may receive updates through WordPress.org, a public repository, the Veyra website or another channel identified on the product page. The timing, frequency and duration of future updates are not guaranteed unless a specific product or commercial agreement says otherwise.
Support may be provided through public documentation, community channels, email forms or plan-based assistance. A response from support does not transfer administrative responsibility for the user’s website or replace the need for backups and safe testing.
Security fixes, compatibility work and feature development may be prioritised differently according to product maturity, impact and available maintenance resources.
What may end when a commercial plan expires
Expiry or cancellation of a future commercial plan may end access to official update delivery, private downloads, licence activations, priority support or hosted services, as described in the applicable plan.
Expiry does not retroactively remove rights already granted in copies of open-source software lawfully received under their package licence.
Where a remote service is necessary for a feature, that feature may stop or become limited after the service entitlement ends. This dependency must be identified before purchase.
Define the final post-expiry behaviour before commercial launch: [[SOFTWARE CONTINUES TO RUN]], [[UPDATES END]], [[SUPPORT ENDS]], [[REMOTE FEATURES END OR CHANGE]] and [[RENEWAL TERMS]].
Remote communication must be documented
A product that contacts Veyra servers for licence activation, update checks, security notices, diagnostics or optional telemetry must describe the relevant data flow in its product documentation and Privacy Policy.
Licence validation should be limited to information reasonably necessary to provide the licensed service, protect against abuse and maintain the product. Optional telemetry must be clearly distinguished from communication required for a requested remote feature.
Insert the verified position for each product: [[NO REMOTE COMMUNICATION]], [[UPDATE CHECKS]], [[LICENCE KEY, DOMAIN AND VERSION DATA]], [[OPTIONAL TELEMETRY]] and [[OPT-OUT OR DISABLE CONTROLS]].
Dependencies keep their own licences and notices
Veyra products may include or depend on third-party software, icons, libraries, frameworks or other materials. Those components remain subject to their respective licence terms and copyright notices.
Each distributed product should include a third-party notice, dependency manifest, source reference or equivalent record where required or useful.
| Component | Used in | Licence | Notice or source |
|---|---|---|---|
| WordPress | WordPress plugins and themes | GPLv2 or later | wordpress.org/about/license |
| [[THIRD-PARTY COMPONENT]] | [[PRODUCT OR WEBSITE]] | [[LICENCE IDENTIFIER]] | [[NOTICE / SOURCE / ATTRIBUTION LINK]] |
Code permissions do not create false official status
Veyra Apps, product names, logos, visual identity and other source-identifying signs are separate from the copyright licence applying to software code.
Users may make truthful references to compatibility, origin and modifications, but must not present an unofficial fork, redistributed copy or third-party service as an official Veyra product or imply endorsement, partnership or certification that has not been granted.
Modified versions should use sufficiently distinct naming and presentation where necessary to avoid confusion about their source and maintenance.
Licence disclaimers and mandatory rights
Open-source packages may include warranty and liability disclaimers in their licence text. Users should review those terms before installing, modifying or redistributing the software.
Software should be tested in a safe environment, with appropriate backups, before use on an important or production website. Compatibility may depend on WordPress, PHP, server, database, browser, theme and third-party plugin versions.
Nothing on this page excludes liability or statutory rights where exclusion is prohibited by applicable law. Paid digital products and services may also be subject to mandatory conformity and consumer protections described in the applicable commercial terms.
Reports concerning licences, copyright or branding
Questions or good-faith reports concerning a licence notice, third-party dependency, copyright issue, unauthorised official branding or misleading redistribution may be sent to hello@veyraapps.com.
A report should identify the product, version, relevant URL or package, the rights or notice concerned and enough context to investigate the issue.
Technical vulnerabilities should use the separate Security and Vulnerability Disclosure Policy.
Changes to this licensing overview
This page may be updated when Veyra releases new product types, introduces commercial plans, changes distribution channels or activates remote services.
The licence applying to a previously distributed software version remains the licence included with that version. Updating this explanatory page does not retroactively replace a package licence.
Licensing questions
Questions about product licences, official distribution or use of Veyra branding may be sent to:
- General and legal contact: hello@veyraapps.com
- Product support: support@veyraapps.com
- Software publisher: [[LEGAL NAME OF THE SOFTWARE PUBLISHER]]
- Address: [[PUBLIC BUSINESS OR PROFESSIONAL ADDRESS]]