Private processing
Australia only keeps private AI processing with Australian-served models. Global permits the wider provider catalogue, including providers outside Australia.
Data & AI for Australian RTOs
Clear rules for the work AI touches. Before you start.
RTEO separates public, non-sensitive work from private, sensitive data so your workspace can make a deliberate choice about where each kind of work runs.
- Private data defaults to Australia-only processing.
- Public processing has its own Australia or Global control.
- Unknown or unsupported calls are refused rather than quietly sent overseas.
Data & AI controlsWorkspace setting
Choose the lane.
Private and public work are classified before a model is selected.
Private / sensitivePublic / non-sensitive
Australia only
Separate public control
Two data classes
The important boundary is what the call contains.
RTEO treats a call as private whenever it contains personal, customer or workspace-held material. Public means openly available content that does not identify a person. The label belongs to the call, not to the AI model.
Private / sensitive
Students, contacts, enrolments, email content, conversations over workspace data and client-authored drafts. These follow the private processing setting.
Public / non-sensitive
Your public website, public competitor pages, search data, open-web research and generated public assets. These follow the separate public setting.
Unknown means private
If a call is not explicitly classified, RTEO uses the safer private route. It never guesses that a call is safe to send overseas.
Workspace controls
One setting for private data. One for public work.
Your workspace chooses where private data may run. When private processing stays Australia-only, the public setting can keep public work in Australia where a suitable model exists or use Global for the wider model catalogue. If private processing is Global, public work is Global too.
Public processing
Australia where available keeps public work on an Australian model when one exists. Global keeps more public features available.
Choose the workspace instruction
Workspace owners can tighten private processing to Australia only; enabling Global private processing requires RTEO support. Members can choose the separate public lane in Settings > Data & AI.
Route by data class
The router uses the call's classification and the selected lane before it chooses a provider or model.
Keep the decision visible
The settings page explains what runs where, and why a feature is unavailable when Australia has no suitable model.
What runs where
A known route for every call.
The exact model depends on the AI role, the data class and the workspace setting. The useful promise is simple: Australia-only private work does not silently fall back to a Global model.
Australia-only route
Private calls use Australian-served models through AWS Bedrock when the role has one. Public calls can use the same lane when the public setting is Australia where available.
Global route
Global processing uses the wider model catalogue through the configured gateway and named providers described in the DPA.
Refused when no safe model exists
If Australia-only processing is selected and a role has no Australian model, that feature reports unavailable instead of routing overseas. The rest of the workspace keeps working.
For your client review
Read the agreement before you sign up to RTEO Connected.
The DPA sets out the data classes, processing modes, subprocessors, security measures and deletion commitments in detail. It is public so your team can review it before signup.