AWLabs

Read this before you brief us.

This page summarises how we work. Where it describes our obligations, the Master Services Agreement is what binds us. We have written it down so you do not have to ask, and so your legal and security people can check us before the first commercial conversation.

The verifiable facts.

The company details below can be checked on public record (ASIC and the ABR). The insurance certificate is available to procurement on request.

Legal entity
AW Labs Pty Ltd
Known as AWLabs. Sister company to All Webbed Up, our marketing business, which is run separately.
ABN
32 698 684 105
Australian Business Number, verifiable on abr.business.gov.au
Registered office
Floor 1, 43 Ware Street, Fairfield NSW 2165
As recorded with ASIC
Business address
1 Ramsay Rd, Five Dock NSW 2046
Greater Sydney, Australia
Operating hours
Monday to Friday, 9am to 6pm Sydney time
A real person reads every reply
Ownership
100% Australian-owned
No offshore parent. Delivery is Australian-led and remains managed and accountable through AW Labs in Sydney.
Insurance
Professional indemnity $1M per claim ($2M in total each year). Public liability $10M. Cyber $500,000 per claim ($1M in total).
Underwritten by Lloyd’s via CFC. Certificate of Currency provided to procurement on request.

You own what we build for you once it is paid for.

A plain English summary of the IP clauses in our Master Services Agreement. Assigned to you on payment. Where this summary and the agreement differ, the agreement applies.

Our own tools stay ours

Anything we bring to the engagement that already existed before the project starts, such as our internal libraries, methods and templates, stays ours. The contract calls these Background IP. You get a permanent licence to use them inside your product. Open source stays under its existing licence.

What we build for you is yours once it is paid for

You own what we build for you once it is paid for. Each part is assigned to you as it is paid for in full, and until then you can see and test the code while we build. After launch we may show non confidential screenshots in our portfolio unless you tell us not to.

We do not embed silent dependencies on us

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. Nothing we build depends on us to keep running. Once your final payment is made, you can run it without us.

You receive the keys

Your hosting, domain, app store and payment accounts are set up in your name before launch, once the amounts due are paid. The full repository, final logins, accounts and deployment details are handed over after the final payment.

How we work on security.

This page summarises how we work. Where it describes our obligations, the Master Services Agreement is what binds us. We build security to fit your risk: not gold plated, and not left exposed. An independent penetration test by a specialist firm is your choice, and we can help you arrange it.

Authentication

  • Multi factor sign in on our internal accounts and the systems that touch client data
  • Single sign on (SSO) where the client provides an identity provider
  • Session tokens rotated; refresh tokens revoked on suspicious activity

Authorisation

  • Least privilege by default: our people get access only to the projects they work on
  • Access to client production data is kept to the people who need it
  • Production changes are made deliberately, not from shared admin logins

Data handling

  • Production data stays in the production environment unless you agree to an export
  • Personal information is redacted from logs that may capture user input
  • Encryption at rest and in transit as standard practice

Code and dependencies

  • Security is tested during every build, including automated penetration testing before launch
  • An independent penetration test by a specialist firm is your choice, and we can help you arrange it
  • Dependencies and secrets are checked during the build; leaked credentials are rotated

If something goes wrong

  • Roll back first, investigate second
  • We tell you without undue delay if an incident affects your data or service
  • We review what happened and track the fixes to closure

How we handle your data around AI.

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.

Where your data goes

  • We can host your data in Australian cloud regions
  • If your data must stay in Australia, tell us before you sign and we write it into your Schedule of Work
  • Unless the Schedule of Work says so, our cloud providers, tools and team may store or access data outside Australia

Model providers and training

  • We use business accounts and settings for AI tools, not consumer AI apps, for client work
  • If you need a tool that does not train on your data, tell us before the Schedule of Work and we will agree it in writing
  • Prompts, documents and embeddings are treated with the same care as the source data

AI in our delivery pipeline

  • Our developers use AI coding tools, and they review AI assisted work before it ships
  • If your contract restricts AI tooling on your codebase, we agree the rules in writing before work starts
  • We take reasonable care to keep secrets and production data out of prompts, and develop with test or masked data

Controls in the systems we build

  • Access control enforced at retrieval, so AI features only see what the user is allowed to see
  • Logging of prompts, sources and outputs where your policy allows, for audit and incident review
  • Evaluation sets and human review paths for high-stakes outputs, aligned with Australia's Guidance for AI Adoption

How we treat Australian and adjacent regulation.

Australian Privacy Principles

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. We build as though the Australian Privacy Principles apply.

Data residency

We can host your data in Australian cloud regions. If your data must stay in Australia, tell us before you sign and we write it into your Schedule of Work.

R&D Tax Incentive

Some software development may qualify. Whether yours does, and what it is worth, is a question for a registered R&D tax agent. Our accountants at Crescendo can advise; they are a separate practice and you engage them directly. We keep build records your tax agent can ask for.

European users

If you have European users, we can scope GDPR features into your build, such as data subject requests, consent management and deletion requests. Your lawyer confirms what applies to you.

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. AWLabs 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 or badges we cannot produce on request. 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.

Let's Build Something Extraordinary

Ready to Transform Your
Technology Operations?

Tell us what you want to build. Let's talk about what we can build together.

Free 30-minute strategy call
No commitment required
Response within 1 business day
Mutual NDA sent before you share your idea