Trust Center

Trust should be verifiable.

Provider Shield is designed to help NDIS providers review sensitive documentation without turning AI into a black box. We show where sensitive product data is processed, what our AI is allowed to do, how findings are produced and where human review remains required.

AI you can verify, not just trust.

Last reviewed 14 October 2026 · Assurance Pack version 1.0

Where sensitive data is handled

Provider Shield uses Australian-region infrastructure for sensitive AI inference, document storage, database hosting and application compute.

The detail behind this statement, including what stays outside the boundary, is on the Data & Privacy page.

  • Australian-region AI

    Azure OpenAI

    Australia East

    Standard deployment

  • Australian-region storage

    Azure Storage

    Australia East · ZRS

    Private container

  • Database hosting

    Neon PostgreSQL

    AWS Sydney

  • Application compute

    Vercel Functions

    Sydney

  • Human review

    AI-assisted findings are labelled

    and left for a person to confirm

  • Explainable findings

    Each finding shows its source evidence

    and why it was raised

What Provider Shield AI is allowed to do

Provider Shield uses AI to help your team review documentation. It works only from the records you provide.

Provider Shield AI is allowed to

  • Allowed: Improve the wording of notes using only the facts supplied by your team
  • Allowed: Extract information that is explicitly written in a document, such as agreement dates and goals
  • Allowed: Compare records to point out potential inconsistencies
  • Allowed: Suggest areas that need human review
  • Allowed: Help compare the meaning of participant goals with documentation
  • Allowed: Summarise evidence that is already present in the records you provided

Provider Shield AI is not allowed to

  • Not allowed: Invent activities, outcomes, incidents, participant goals, behaviours or observations
  • Not allowed: Make eligibility decisions
  • Not allowed: Approve or reject NDIS claims
  • Not allowed: Give legal advice
  • Not allowed: Guarantee compliance or an audit result
  • Not allowed: Quietly switch to another AI provider if the Australian service is unavailable

If something is missing, Provider Shield says so. A draft shows a clear prompt such as “[Add observed outcome]” where a fact was not provided, explains what is missing, and will not let that placeholder be saved as if it were a real note.

Not every finding comes from AI

Provider Shield labels how each finding was produced, so you know how much interpretation is involved.

Deterministic check

Based on defined system logic: the same records always give the same result. It does not mean a legal conclusion.

  • Overlapping service records
  • A service date outside the agreement period
  • A duplicate service record
  • Weekly service hours compared with confirmed agreement hours

AI-assisted review

Used where language or meaning needs interpreting. These findings are labelled, show a confidence level where relevant, and always remain open to your review.

  • Comparing the meaning of a participant goal with what documentation describes
  • Reading explicitly stated fields out of a Service Agreement

What a finding looks like

Every finding shows its source evidence, why it was raised and what to check, so you can inspect it rather than take it on trust.
Illustrative example

Potential inconsistency

Source
  • Service Agreement: Support period ends 30 September 2026.
  • Service record: Service recorded 4 October 2026.
Why it was flagged
The recorded service date falls outside the agreement period currently stored in Provider Shield.
Recommended action
Confirm whether a newer agreement exists, or whether the service record needs review.
Finding type
Deterministic

Invented example for illustration only; it is not customer data.

Human review stays in control

Findings

  • Reviewed
  • Resolved
  • Not applicable

Extracted agreement fields

  • Confirmed
  • Corrected
  • Marked not present
  • Marked incorrect

Reviewing a finding does not change the original note, document or service record. Corrections you make are stored separately from what the AI read, so the original reading stays visible.

How data moves

Provider names and regions only. Credentials and internal identifiers are never shown.
  • AI analysis

    1. You
    2. Vercel — Sydney
    3. Sensitive AI gateway
    4. Azure OpenAI — Australia East
  • Documents

    1. You
    2. Vercel — Sydney
    3. Azure Storage — Australia East
  • Product data

    1. Vercel — Sydney
    2. Neon — AWS Sydney

Service providers

Only services we actually use are listed. Providers that handle account, payment or authentication information do not receive participant notes or documents.
  • Microsoft Azure OpenAI

    Purpose:
    Sensitive AI inference
    Sensitive participant content:
    Yes
    Region / scope:
    Australia East · Standard deployment
  • Microsoft Azure Storage

    Purpose:
    Uploaded documents
    Sensitive participant content:
    Yes
    Region / scope:
    Australia East · zone-redundant · private access only
  • Neon

    Purpose:
    Application database
    Sensitive participant content:
    Yes
    Region / scope:
    AWS Sydney (backup locations are governed by the provider and are being confirmed)
  • Vercel

    Purpose:
    Application execution
    Sensitive participant content:
    Yes
    Region / scope:
    Functions in Sydney
  • Stripe

    Purpose:
    Payments and subscriptions
    Sensitive participant content:
    No
    Region / scope:
    Global specialist provider; no participant notes or documents
  • Sign-in providers (Google, GitHub)

    Purpose:
    Optional sign-in identity
    Sensitive participant content:
    No
    Region / scope:
    Provider infrastructure; no participant notes or documents
  • Resend

    Purpose:
    Transactional account email
    Sensitive participant content:
    No
    Region / scope:
    Provider infrastructure; no note or document content
  • Axiom

    Purpose:
    Operational logs of route-level metadata
    Sensitive participant content:
    No
    Region / scope:
    Provider infrastructure; no participant, document or note content
  • Analytics tools

    Purpose:
    Public marketing pages only, with consent
    Sensitive participant content:
    No
    Region / scope:
    Not used inside the signed-in product

Data minimisation

Provider Shield sends only the information required for each review task where practical. Full document text is used only for workflows that require the document itself to be analysed.

File Review comparisons send only the goal wording and short note excerpts needed for that comparison, without participant names, identifiers or file names.

No silent offshore fallback

If the approved Australian Azure AI service is unavailable, Provider Shield does not silently send sensitive documentation to an alternate external AI provider. The analysis fails safely instead, with a clear message.

Document storage

  • Private storage container; anonymous access disabled
  • Secure transfer required; TLS 1.2 or higher
  • Zone-redundant storage in Australia East
  • Download links are issued only for files in our own storage and expire after one hour

Application security

  • Private routes require sign-in
  • Records are scoped to your account and participant; other accounts cannot access them
  • Operational logs avoid participant, document and note content
  • No marketing analytics run inside the signed-in product
  • Request bodies are excluded from routing middleware
  • Secrets stay on the server

What Provider Shield does not do

Provider Shield supports your team’s review. It does not:

  • Determine NDIS eligibility
  • Submit or approve claims
  • Replace professional judgement
  • Provide legal advice
  • Guarantee an audit result
  • Treat AI output as unquestionable truth
  • Fix source records automatically

Known limitations

We would rather you hear these from us.
  • Microsoft’s standard abuse monitoring for Azure OpenAI is governed by Microsoft’s terms; flagged content may be reviewed under that process. Modified abuse monitoring has not been approved for Provider Shield.
  • Where database backup copies are held is governed by the database provider and is being confirmed.
  • Payment, sign-in and account-email providers may operate outside Australia. They handle account, authentication and billing information, not participant notes or documents.
  • Requests reach our Sydney servers through our hosting provider’s network.
  • Files saved before our current storage was introduced may no longer be available for download.

Independent assurance

This documentation is based on implemented technical controls and internal verification. Independent security and privacy assurance may be added as the platform matures.

Common questions

Where is sensitive Provider Shield data hosted?
Provider Shield uses Australian-region infrastructure for sensitive AI inference, document storage, database hosting and application compute. See the processor table for providers that handle only account, payment and authentication information.
Does Provider Shield send NDIS notes to Anthropic or public ChatGPT?
No. Sensitive AI processing goes through a single gateway to our Azure OpenAI deployment in Australia East. There is no other AI provider in that path.
Can the AI invent missing details?
It is instructed not to, and the product is built to flag missing information with a visible placeholder instead. Please always read drafts before saving them.
Does Provider Shield make compliance decisions?
No. It points out items that may need review. People decide what, if anything, to change.
What happens if the AI service is unavailable?
If the approved Australian Azure AI service is unavailable, Provider Shield does not silently send sensitive documentation to an alternate external AI provider. The analysis fails safely instead, with a clear message.

Read more

For security, privacy or AI questions, contact us through the contact page. Please do not send participant information in a message.

Provider Shield uses Australian-region infrastructure for sensitive AI inference, document storage, database hosting and application compute. Wording on this page is for information and is not legal advice.