No licence is granted by this website
This notice explains the subjects that a SOVRAX software agreement needs to address. It is not an end-user licence, automatic activation offer or permission to access software. Website diagrams and the red access card are illustrative only.
A licence exists only under the applicable agreement with the identified SOVRAX entity or other authorised rights holder. The actual agreement determines the software, permitted use and obligations. Where its terms differ from this explanatory notice, the executed agreement and mandatory law govern.
Define the permission
A licence should identify the application and version or edition, the authorised person or organisation, the intended purpose and the limits of permission. Rights not granted in the applicable agreement are not implied by access to a demonstration or discussion.
- Users, seats, installations, devices, environments or usage limits.
- The licence term, territory if relevant, and whether transfer or sublicensing is permitted.
- Permitted production, evaluation, development or testing use.
- Any usage restrictions, notices and dependencies that apply to that software.
Activation and entitlement checks
Where agreed, a product may include activation, entitlement validation and controls for editions or installations. The product documentation and agreement should explain required connectivity, validation intervals, offline behaviour and what happens if validation is unavailable.
Activation credentials should be protected and used only by authorised users. Do not bypass controls, share credentials outside the permitted scope or present an expired or unauthorised entitlement as valid. If access behaves unexpectedly, contact the support channel specified in the agreement rather than attempting to defeat the control.
Ownership and third-party components
Software use rights are distinct from ownership. Source-code delivery, bespoke development ownership, reuse of pre-existing components and rights in project materials must be stated expressly in the project agreement. Payment alone should not be assumed to transfer every intellectual-property right.
Third-party and open-source components may have their own terms. Those terms and notices must be considered alongside the product licence. Nothing here removes rights that applicable law or a relevant open-source licence grants independently.
Delivery, support and changes
Delivery format, installation responsibilities, compatibility, acceptance testing and customer dependencies are project-specific. Updates, security maintenance, technical support, response windows and upgrade rights are included only to the extent agreed.
A licence does not by itself promise perpetual updates, uninterrupted operation, universal compatibility or a particular business outcome. Version changes, entitlement changes and migration work should be handled through the agreed process.
Fees, renewals and ending access
Prices, taxes, payment timing, cancellation, renewal, refunds and any suspension or termination rights belong in the applicable commercial agreement. The corporate website does not take payments or publish a universal refund or renewal entitlement. Mandatory rights continue to apply.
The agreement should explain any notice or cure period, the effect on access, treatment of data and copies, and obligations that survive termination. Do not assume that access renews automatically or that an expired licence remains valid without checking its terms.
Data, authorised use and enquiries
Licensing telemetry or account data, if a particular product uses it, requires product-specific privacy information. The corporate website’s email-only policy is not a description of every future software product. Software security testing requires permission for the relevant systems and scope.
To discuss a licence, email contact@sovrax.io with your application, intended users, platforms and deployment needs. Do not send live licence keys or credentials in an initial enquiry.