Account Deletion and De-identification

Individual Accounts and Organisation Records Are Different

An individual user account provides access to one or more Customer organisations. Rosters, timesheets, clock events, leave, messages, requirements, payroll audit records, and related history belong to the relevant organisation record. Deleting an individual's login does not automatically delete the Customer's workforce records or the records of other users.

ROVYN uses de-identification and access revocation in TaskForceOne where records need to remain connected to an organisation's operational, audit, legal, security, or dispute history. This page describes current product behavior and should be read with our Privacy Policy.

Delete from the App

1. Sign in at app.taskforceone.com.au or open the mobile app.
2. Open Account Settings and the Danger Zone.
3. Select Delete Account, read the effect shown in the product, and complete the confirmation.

If you cannot sign in, email [email protected] from the account email where possible. We may ask for information needed to verify identity, organisation membership, and authority.

What Happens to the Individual Login

When deletion is processed, ROVYN revokes active access and authentication tokens and replaces or removes direct account identifiers such as email address, username, linked sign-in identifiers, and profile or presence information. Organisation membership identity fields such as name, contact number, and profile image may also be scrubbed or replaced with a deleted-user label.

Deletion is not an instantaneous erasure of every database row or backup. Limited security, consent, billing, abuse-prevention, and deletion-audit evidence may remain where reasonably needed or legally required.

Records That May Remain

• Rosters and time records: shifts, clock events, original and adjusted times, approvals, reasons, and audit history may remain in the Customer organisation.
• Messages: existing message content, attachments, reactions, and conversation history are not automatically erased solely because the author's login is deleted. The author's account identity may be de-identified.
• Requirements and signatures: documents, acknowledgements, review history, and expiry records may remain under Customer control or be de-identified.
• Payroll and integration records: mappings, export requests, responses, status, and errors may remain for reconciliation, support, and audit purposes.
• Billing, consent, and security records: invoices, subscription events, accepted-document records, and security logs may remain for legal, tax, fraud, dispute, and security purposes.
• Backups: deleted or de-identified information may remain until the applicable backup cycle expires.

Requests About Customer-Controlled Records

An employee or contractor should ask the Customer organisation to correct or delete workforce records. The Customer may need to preserve accurate wage, time, safety, licensing, or employment records and can instruct ROVYN where deletion is lawful and supported. ROVYN will assist with a verified request where reasonably required.

Sole Organisation Owners

If the deleting user is the sole owner of an organisation, the product may cancel or end the organisation's subscription, remove user access, and archive the organisation rather than immediately erase its records. Transfer ownership to another authorised administrator before deleting the account if the organisation should continue.

Exports Before Deletion

Use available account, roster, timesheet, payroll, and other product exports before deleting access. An individual account-data export may contain profile and membership information and a limited selection of recent activity; it should not be treated as a complete export of every Customer workforce record. Organisation administrators should export required business records or contact support before cancellation.

Further Deletion Requests

After an account is de-identified, a person or Customer may request review of remaining personal information. We will consider Customer instructions, the person's rights, other people's privacy, technical feasibility, backups, legal retention, security, and dispute needs. Where we cannot delete a record, we may restrict access or further de-identify it where appropriate.

Contact

Email [email protected] with questions. Do not send identity documents unless we ask for them through an appropriate channel.