Skip to content
Talk to Moe
Find your starting point
Security and your data

Know where the work happens.
Keep control of the decisions.

A useful system needs clear arrangements for data, access and responsibility. Those arrangements belong in the design and the written scope, matched to your work and the services involved.

Where does the work run?

The setup depends on the job. It may use your existing workspace, a cloud server in your name, or another agreed service. We identify the accounts, providers and data involved when we scope the work. Hosting a server in one country does not by itself mean every connected AI service processes data there.

What information do outside services receive?

Connected tools and AI services may receive information needed for their part of the task. The design needs to identify what is sent, why, and the provider settings and retention terms that apply. Bring any location, confidentiality or retention requirements into the conversation before a service is chosen.

Who gets access, and who makes decisions?

We agree the access needed for the build, the people responsible and what the system can do on its own. Your team keeps the decisions that require your judgement. ISA's access is part of the agreed support arrangement; using your own system should not require routine approval from ISA.

What happens at handover?

The handover covers the accounts and work included in your scope, how to use them and the support arrangement you choose. Access that should end is identified for removal, with credential changes agreed with the account owner. Export options, provider licences, backups and retention requirements depend on the actual services involved.

Using this website

A public enquiry
is a different setting.

This website uses services to receive enquiries, process payments and provide its features. Messages entered into the website's AI chat are sent to an external model service to prepare a response. Use it for general questions about ISA; keep passwords and private client records out of the conversation.

The privacy page explains the site's enquiry, payment and analytics handling, including your choice about optional advertising measurement.

Website privacy and choices

The questions
owners ask first.

Can I move to another provider or manage it myself?

Client control is part of the design. The scope should identify what you own, what can be exported and any third-party licence or technical limits. If a future move matters to you, make it part of the requirements so the handover can be planned around it.

Does ISA keep copies of client data?

That depends on the agreed delivery and support setup, including logs, backups and any information needed to investigate an issue. The handling and retention arrangements need to be clear for your project. The website has its own processing, explained below and on the privacy page.

Can I require Australian hosting?

Tell Moe which information must stay in Australia. The scope can then assess hosting and the processing locations of each connected service. Australian server hosting alone is not a promise that every provider or model keeps all processing onshore.

Bring the requirements
that matter to your business.

Talk through your tools, data boundaries and decision rights with Moe. Start with a free 15-minute call.