Clear scope, clear access, clear ownership.
This website explains our operating model. A specific project begins only when the actual scope, commercial terms and responsibilities are accepted.
No automatic acceptance
Submitting a brief does not oblige either party to begin work. Scope, price, timing, responsibilities, review points and payment terms must be accepted for the specific engagement.
Agency relationship
When WebAgencyOn is engaged as an agency delivery partner, the agency retains its client relationship unless a different arrangement is expressly agreed. Direct technical contact does not by itself transfer commercial ownership of that relationship.
Domain, hosting and third-party services
Unless the project expressly states otherwise, domains, hosting, licences, paid APIs and other third-party services are contracted directly by the client or agency with the relevant provider. WebAgencyOn may recommend options, send provider links and assist with configuration without becoming the provider of those external services.
The customer remains responsible for the information supplied to those providers and for their billing, renewals and account terms. Any affiliate/referral relationship should be disclosed.
Remote access and authorisation
The person granting remote, hosting, registrar, DNS or administration access confirms that they are authorised to do so. Attended remote assistance may be used so the customer can log in personally and remain present while agreed technical work is carried out.
Primary passwords, recovery codes and unrelated confidential information should not be sent through ordinary project forms. Unattended access is not assumed.
Confidentiality and data-processing roles
Information accessed for a project should be used only for the agreed work and handled with appropriate confidentiality. Where WebAgencyOn processes personal data on a client’s behalf, applicable controller/processor responsibilities should be documented where required.
Backups and deployment
Where deployment replaces an existing website and backup capability is available within the agreed scope, a pre-change backup should be made before destructive replacement. A post-launch backup may also be created where supported and included. A backup reduces risk but is not itself a guarantee of successful restoration unless recoverability has been verified.
Low-maintenance design
Some projects can be built with fewer moving parts—for example, without a CMS, plugin ecosystem or application database. This can materially reduce routine maintenance. It does not mean hosting, domains, certificates, forms, external integrations, security changes or future content requirements will never require attention.
Dependencies and timing
Delivery and launch can depend on client/agency feedback, third-party platforms, hosting, DNS, registrars, certificates, payment providers and access. We do not guarantee control over external-provider timing.
Security and performance
No website or configuration can be guaranteed immune to every future attack, outage, browser change or incompatibility. Performance and commercial outcomes are not guaranteed by arbitrary scores.
Intellectual property and handover
Ownership and licences for final deliverables, third-party components and supplied materials are defined in the applicable project agreement. Temporary access should be removed at handover unless an ongoing service expressly requires it.
Support boundary
Project delivery does not automatically create unlimited or 24/7 support. Ongoing support responsibilities must be expressly agreed where required.