Privacy should be practical and explicit.

ezWorka is built for the South African market and is designed around the Protection of Personal Information Act (POPIA). Workas operate on a least-privilege basis, receive only the personal information needed for the approved job, and are built to mask personal information where it is not required.

Customers act as the responsible party for the business and personal data they connect, and they decide which systems a worka may access. ezWorka processes that data to deliver the requested workflow. Irreversible actions - payments, outbound customer messages, SARS filings such as VAT201 and EMP201, and record deletions - always wait for a human to approve, so a worka never acts on personal data on its own.

ezWorka may process account details, contact information, workspace settings, connected-tool metadata, task instructions, uploaded or connected business content, generated drafts, review notes, support messages, and technical logs.

The exact data depends on which worka is selected and which tools a customer chooses to connect. Customers should only connect systems and records that are needed for the approved workflow.

Data should be used to provide the requested worka workflow, maintain security, troubleshoot the service, support billing and account administration, and improve reliability. Sensitive customer data should not be used to make public claims or published proof without permission.

ezWorka is designed around limited access and reviewable outputs. Customers remain responsible for deciding what systems to connect, who can approve work, and whether any generated output is suitable for use.

Retention periods may vary by account, connected service, support need, and legal requirement. Customers should request deletion or export through the contact channel provided by ezWorka once formal support details are published.