CALL DATA

Know where your call data goes.

Before you choose a calling workflow, understand how audio and customer details move through it. Confirm the actual locations, providers and permissions for your deployment.

Discuss your data requirements ↗
01

Voice processing

02

Recordings & transcripts

03

Database

04

Backups

Illustrative data categories. This diagram does not claim an Australian hosting region or an AWS deployment.

DEPLOYMENT FACTS

What to confirm for your deployment.

Confirm these facts separately for website enquiries and voice-service data. Record the agreed details in your service documents before production use.

  1. 01

    Recording and processing

    Confirm whether recording and transcription are enabled, where live audio is processed, and which telephony, speech and model providers receive it. These may use different locations.

  2. 02

    Storage and backups

    Confirm where recordings, transcripts, databases, logs and backups are stored. Include disaster recovery copies; one cloud region does not describe the complete data path.

  3. 03

    Access and overseas recipients

    Identify authorised teams, roles and subprocessors, the countries they access data from, and the purpose of any overseas disclosure. Confirm the safeguards that apply to the arrangement.

  4. 04

    Retention and deletion

    Agree how long each data type is kept, who can request access or deletion, and how deletion affects backups, logs and legal retention requirements.

  5. 05

    Responsible organisation and review date

    Record the responsible organisation, privacy contact, service scope and the date the data facts were confirmed. Recheck them when a provider, location or access arrangement changes.

Questions before you get started.

Contact sales ↗
Does an Australian domain mean the data stays in Australia?

No. A domain identifies a website address. Processing, storage, backups and access must be checked separately.

Are website enquiries and call data the same?

No. Website enquiries are business contact records. Audio, recordings and transcripts belong to the separately scoped voice-service workflow.

Can I request the data locations before a pilot?

Yes. Share your requirements with the team so the proposed workflow and its data path can be reviewed before you agree the scope.

Official sources

OAIC: privacy transparency ↗OAIC: cross-border disclosure ↗

Australian privacy obligations depend on the responsible organisation and processing activity. Confirm the applicable requirements with your advisers.

Solutions