Book a call
Access card held to a secure office door reader

Security

Security: your data stays in your environment

Written for CIOs and security teams. What happens to your data, and who controls it.

Our commitments

  • Data stays in your environment

    AI runs on your cloud or your own servers, in Australia.

  • Never used for training

    Your data does not train anyone's model.

  • You own the code

    It lives in your repository, documented.

  • Your identity provider

    Access through your existing sign-in and roles.

  • Everything logged

    Every AI action and approval is recorded.

  • A person approves

    AI does the first pass. Your team decides.

Runs on your infrastructure

AI does the first pass. Your team approves. Your data never leaves your environment.

How we keep it secure
Your systems feed AI, which does the first pass. Your team approves each result before it goes back into your systems. All of it runs inside your infrastructure in Australia.Your infrastructure, in AustraliaYour cloud or your own serversYour systemsFinance and ERPOperationsDocuments and emailAssets and fieldAI does thefirst passReads, checks, draftsYour teamapprovesNothing moves without a personBack intoyour systemsApproved results update the systems your team already usesYour systems feed AI, which does the first pass. Your team approves each result before it goes back into your systems. All of it runs inside your infrastructure in Australia.Your infrastructure, in AustraliaYour cloud or your own serversYour systemsFinance and ERPOperationsDocumentsAssets and fieldAI does the first passReads, checks, draftsYour team approvesBefore anything movesBack into your systemsApproved results update thesystems your team already uses
  • Data stays in your environment
  • Never used to train models
  • Access through your identity provider
  • You own the code

Questions we answer up front

  • Where is data processed?

    In an Australian or New Zealand location you choose, in your cloud or on your own servers.

  • Who can see it?

    Only people your access controls allow.

  • What leaves your boundary?

    Nothing, unless you approve a specific connection.

  • What if we part ways?

    You keep the code, the data and the documentation.

Senior team workshop in a Brisbane meeting room

The Privacy Act, in practice

Australian Privacy Principle 11 asks for reasonable steps to protect personal information. APP 8 covers sending it offshore. Processing on your infrastructure in Australia, with logging and human approval, makes both easier to evidence.

  • Data mapped before we build
  • Access reviewed with your IT team
  • Documentation for your auditors

Questions

Do you hold security certifications?

We do not claim certifications. We build inside your environment, under your security policies, so your existing controls, audits and certifications cover the work, and your security team reviews the architecture before anything is deployed.

What Privacy Act obligations apply when we use AI?

The Australian Privacy Principles apply to personal information used in AI just as anywhere else: APP 6 limits use to the purpose it was collected for, APP 8 covers sending it offshore and APP 11 requires reasonable security. The OAIC published guidance on AI and privacy in 2024.

Who can access our data during an AI project?

Only the people your access controls allow. Our engineers sign in through your identity provider with the roles you grant, every action is logged, and you can remove access at any time without asking us.

What happens to our data if we stop working together?

It stays where it always was, in your environment. You keep the code, documentation and any models or configuration built for you, and our access is removed through your identity provider, so nothing needs to be returned or migrated.

Related

Bring your security team in early

We will walk your IT team through the architecture before any proposal.

Talk to us How we work

Fixed-fee phases, agreed before we start. Stop after any phase.