Security + data

Your calls become work.
Your data stays governed.

OrderStaff is built around controlled business workflows. We use technical and organisational measures designed to protect information throughout the call, processing and dashboard lifecycle.

01Call arrives

A telephony provider connects the caller to the configured OrderStaff service.

02AI processes

Speech and business context are processed to understand the caller’s request.

03Rules applied

Configured business information and workflow rules are used to structure the response or action.

04Work created

The resulting order, booking, appointment or enquiry is made available to the business.

Access

Only what is needed.

We design administrative access around authentication, role-appropriate access and operational need. Business users should protect their own credentials and remove access when staff no longer need it.

Infrastructure

Layered providers.

OrderStaff uses specialist infrastructure for telephony, AI/voice processing, cloud delivery and website services. Providers may include Cloudflare, ElevenLabs, Twilio and Shopify where relevant to the configured service.

Data lifecycle

Keep what serves a purpose.

We aim to retain information only while it is reasonably needed for service delivery, support, security, legal requirements and legitimate business records, then delete or de-identify it where required.

Incidents

Assess. Contain. Respond.

We maintain processes for investigating security incidents and will assess notification obligations, including the Australian Notifiable Data Breaches scheme where it applies.

What we do not claim

Security without theatre.

We do not describe OrderStaff as “unhackable”, guarantee that internet services will never fail, or claim certifications we do not hold. Security is an ongoing engineering and operational responsibility.

Shared responsibility
Keep business data current

Incorrect menu, service, price, hours or availability information can create incorrect caller outcomes.

Protect credentials

Use strong authentication practices and restrict dashboard access to people who need it.

Use lawful recording settings

Determine what caller notice or consent is required for your business and jurisdiction if recording or monitoring is enabled.

Do not collect what you do not need

Keep automated workflows focused on information necessary to complete the customer request.

Questions about security
or data handling?

Contact support