Every line on this page is verifiable, from public record, from the engagement contract or from a downloadable document. We have written it down so you do not have to ask, and so your legal and security people can pre-clear us before the first commercial conversation.
Every item below can be confirmed independently. We are not asking you to take our word for it.
Plain-English summary of the IP clauses we put in every contract. The contract itself is reviewed against your legal team's amendments before signing.
Anything we bring to the engagement that already existed before the project starts, internal libraries, methodology, templates, third-party open source, remains owned by the original owner. We list these explicitly in the contract as Background IP. Open source remains under its existing licence.
On final payment, all source code, designs, schemas, infrastructure-as-code, runbooks and documentation created specifically for your project transfer to you in full. We retain no licence, no usage rights and no ability to resell.
No phone-home telemetry to our infrastructure. No hard-coded API keys that route through us. No "you can only deploy this if we host it" architecture. You can fire us and run the system on day one without our involvement.
Source repository, DNS, hosting account, secret store, third-party service accounts, every credential is in your control before final invoice. We are removed from every system within five business days of project closeout.
The specific operational practices we hold ourselves to on every engagement. Independent audit and formal certification can be scoped into enterprise engagements on request.
The questions procurement asks about AI: where data is processed, whether it trains anyone's model, and how AI is used in our own delivery. See also our guide to data residency vs data sovereignty.
Engagements handling personal information of Australian individuals are designed to the Australian Privacy Principles (APPs) under the Privacy Act 1988. Whether your specific use case triggers APP entity status is a call for your privacy counsel; our architecture holds up either way, so the answer changes obligations rather than build.
Default hosting region for Australian engagements is Australia (AWS ap-southeast-2 / GCP australia-southeast1). Cross-border data flows are documented and signed off in the architecture phase, not retrofitted later.
The portion of a software build conducted in Australia is generally eligible for consideration under the AU R&D Tax Incentive (RDTI). We structure our project documentation, technical uncertainty registers, experiment logs, time tracking, to support your eventual claim. This is a structural advantage of working with an Australian agency, not a claim only we can make.
For clients with European users, we implement data subject request handling, consent management and the right-to-erasure machinery as standard. Designed to GDPR principles even where the strict legal obligation is local.
An honest note. Our founder has been shipping software since 2019 and running All Webbed Up as a Sydney marketing and development agency since 2021. All Webbed Labs itself launched in mid 2026 as a new company, a partnership with a group of exceptional developers and founders. We have deliberately not stamped this site with certifications we have not earned, badges we cannot produce on request, or client logos we cannot show under NDA. If something on this page matters to your procurement process and we have not addressed it, ask us directly at admin@awlabs.com.au, we will tell you yes, no or "not yet" without dressing it up.