Security, Privacy & Compliance
When you manage participant information and NDIS compliance, where your data lives and how it's protected is not a secondary concern. Here's exactly how Eze Taskr handles it.
Infrastructure & Hosting
Where is Eze Taskr hosted?
All Eze Taskr infrastructure runs on Amazon Web Services (AWS) in the Sydney region (ap-southeast-2). This is Australian infrastructure, physically located in Australia, operated under Australian law.
Is data sent anywhere else?
Participant records, shift data, progress notes, compliance records and staff information are stored in Australian AWS infrastructure and are not transferred to overseas servers. Optional AI-assisted features (for example, progress note writing assistance) send the text you submit to a third-party AI service for processing. Those features can be left switched off.
What cloud provider do you use?
Amazon Web Services (AWS) Sydney. AWS is one of the world's most trusted cloud infrastructure providers, used by Australian government agencies, banks, and healthcare organisations.
What uptime and reliability can I expect?
Our infrastructure is designed for high availability. AWS Sydney provides enterprise-grade reliability with redundancy built in. Planned maintenance windows are communicated in advance.
Data Ownership & Portability
Who owns the data in Eze Taskr?
You do. The NDIS provider organisation retains full ownership of all data entered into Eze Taskr — participant records, shift history, progress notes, incident reports, compliance records, and staff data. Eze Taskr does not claim any rights to your operational data.
Can I export my data?
Yes. Providers can export operational records at any time — including progress notes, shift records, compliance reports, audit packs, incident histories, and timesheet data — in standard formats suitable for audits and handover.
What happens to my data if I cancel?
Your data remains accessible and exportable for 90 days following cancellation. After this period, data is securely deleted from our systems. We provide written confirmation of deletion upon request.
Is participant data used for any other purpose?
No. Participant data is used solely to deliver the Eze Taskr service to your organisation. We do not use participant or operational data for analytics, benchmarking, or any commercial purpose beyond service delivery.
Access Controls & Security
Who can access my data within Eze Taskr?
Access is controlled by role-based permissions. Business administrators define what each staff role can see and do. Support workers access only their assigned clients and shifts. Coordinators and administrators have broader access appropriate to their role.
How is authentication handled?
Eze Taskr uses secure authentication provided by the platform infrastructure. Sessions are time-limited and access tokens are managed securely. Administrators can revoke access immediately when staff leave.
Is data encrypted?
Yes. All data is encrypted in transit (TLS) and at rest within AWS infrastructure. Communications between your browser and Eze Taskr are encrypted using industry-standard protocols.
Can I see who accessed or changed records?
Yes. Eze Taskr maintains detailed audit trails of key actions — including who created, modified, or reviewed records. This audit history is available to administrators and is exportable.
NDIS Compliance & Audit Readiness
How does Eze Taskr support NDIS Commission compliance?
Eze Taskr includes built-in compliance monitoring aligned with NDIS Practice Standards — progress note tracking, certification expiry alerts, incident reporting, behaviour support workflows, handover checklists, and GPS-verified shift records.
Can I produce records for an NDIS audit?
Yes. The platform is designed with audit readiness in mind. You can export comprehensive audit packs including progress notes, shift records, incident reports, compliance alerts, staff certifications, and service agreement documentation.
Does Eze Taskr support mandatory incident reporting?
Yes. Eze Taskr includes a structured incident reporting workflow — categorised by severity type and aligned with NDIS reportable incident requirements. Records are date-stamped, assigned, and trackable.
What about the Australian Privacy Principles (APPs)?
Eze Taskr is operated in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles. Participant information is handled in accordance with our Privacy Policy, which is available on our website.
Backups & Incident Handling
Are backups performed?
Yes. Data is backed up regularly as part of the AWS infrastructure. Backups are stored within Australian infrastructure in alignment with our hosting arrangements.
What happens if there is a data security incident?
In the event of a notifiable data breach, Eze Taskr will comply with the Notifiable Data Breaches scheme under the Privacy Act 1988 — notifying affected organisations and the OAIC as required within mandated timeframes.
How do you handle platform security vulnerabilities?
Security updates are applied on a regular basis. Critical security patches are applied promptly. We follow responsible disclosure practices and take security reports seriously.
Who can I contact about security concerns?
Contact our team directly at admin@ezetaskr.com.au for any security-related questions or disclosures. We are committed to responding promptly to legitimate security concerns.
Have More Questions?
Our Australian-based team is happy to answer specific questions about data handling, compliance workflows, or security practices. We understand that trust is not optional when managing participant information.