Website use and information boundaries

Website terms

These terms describe how the public website may be used and distinguish published information and interactive estimates from a signed engineering or support agreement.

The website provides an overview of engineering services, delivery approaches, illustrative platforms, research material and contact channels. Reading the site or preparing an enquiry does not itself create a client engagement, procurement commitment, confidentiality agreement, service-level obligation or promise to deliver a particular architecture.

A project begins only through an authorised written agreement that defines the parties, scope, acceptance evidence, charges, responsibilities, information handling and support terms. Where a signed agreement conflicts with general website material, the signed agreement governs that engagement.

Permitted use

Visitors may use the public pages to understand the company offer, compare delivery patterns, read technical material and make a legitimate business enquiry. Use must not interfere with site availability, attempt to bypass access controls, impersonate another person, submit unlawful material or probe systems without written authorisation.

Automated access should remain proportionate and respect published technical controls. The absence of a visible restriction is not permission to perform load testing, vulnerability exploitation, credential attacks, destructive scraping or collection of contact details for unsolicited campaigns.

Interactive tools and estimates

The Blueprint Designer and SLA Cost Calculator expose planning choices through an interactive interface. Their output is an indicative model based on the selected options, not a quotation, bill of materials, warranty, availability commitment or assurance that a particular technology is suitable for production.

A reliable proposal requires discovery of traffic shape, recovery objectives, dependency behaviour, data classification, residency constraints, support coverage and acceptance criteria. Values displayed by a dashboard or calculator should be checked in a written proposal before they are used for budgeting or procurement.

Research and technical information

Research pages explain engineering trade-offs and operational patterns. They are educational material, not legal, regulatory, financial or security certification advice. Examples simplify real environments and can become outdated as standards, provider capabilities and regional obligations change.

A reader remains responsible for validating a design against the actual system, applicable law, threat model and accountable organisational approvals. No article should be copied into production as a control without testing its assumptions and failure modes.

Company and third-party references

Company names, marks and original site material remain associated with their respective owners. A visitor may quote brief portions with clear attribution and link to the relevant page, but may not present the site, brand board or research as their own service or imply an endorsement that has not been given.

Links to telephone, email, messaging, government or other external services are provided for convenience and context. An external service controls its own availability, information practices and terms; its presence on a page does not make it part of this website or create a general endorsement.

Enquiries and confidential information

The public enquiry surface is not a confidential project workspace. Visitors should provide enough context to arrange a conversation but should not submit passwords, private keys, live customer records, privileged legal material or information they are not authorised to disclose.

The form must not describe information as transmitted when no provider is configured. When a provider accepts a request, that technical acceptance is not confirmation that Wavelink has accepted the proposed work, a tender condition, a deadline or a confidentiality obligation.

Availability and changes

The public website may be maintained, corrected or temporarily unavailable. General availability figures shown elsewhere are product or architecture claims that require their stated scope; they should not be read as a website uptime guarantee or a contractual remedy.

Material changes to these terms should be published with sufficient context for a visitor to understand the new boundary. A production launch review should confirm the governing-law, contact, change-notice and effective-date details rather than inventing them in code.

Responsibility and project agreements

To the extent permitted by an applicable signed agreement and law, responsibility for project work is allocated through the agreed scope, acceptance process, change control, warranty, support and liability terms. This public page does not replace those negotiated protections or expand a remedy beyond them.

Questions about a proposed engagement should be raised before relying on an estimate or delivery assumption. The contact page provides the real Kampala channels available in the repository for that conversation.

Discuss an engagement boundary

Use the contact page to describe the intended outcome and ask for the written scope, assumptions and acceptance evidence relevant to your organisation.

Contact the team