Product-Specific Terms

How These Terms Apply

These terms supplement the Customer Subscription Agreement and apply when a Customer enables or uses the relevant feature. They prevail over the Customer Subscription Agreement only for a direct conflict about that feature.

Award Rules, Labour Costs, and Pay Interpretations

TaskForceOne may apply documented software rules to Customer-supplied information to produce pay interpretations, labour-cost estimates, segments, adjustments, and warnings. A rule set represents TaskForceOne's implementation of selected conditions; it does not determine which modern award, enterprise agreement, classification, employment type, pay point, allowance, exemption, or other obligation applies to a worker.

The Customer must:

• obtain its own legal, payroll, tax, and industrial-relations advice where needed;
• select and configure the correct rules, rates, classifications, hours, breaks, allowances, and employee information;
• review rule documentation, effective dates, warnings, incomplete results, and changes between rule versions;
• compare outputs against applicable source instruments and actual working arrangements; and
• approve final pay through its payroll process.

Roster costs and pay interpretations are estimates and workflow aids, not a guarantee of compliance or final wages payable. A result marked complete means the configured calculation completed; it does not mean every legal obligation has been identified.

Payroll Exports and Integrations

Payroll integrations may exchange employee identifiers, settings, pay items, leave information, timesheets, and export status with Xero or another provider marked as supported in the product. Availability and supported operations can differ by provider, subscription, or provider API.

The Customer authorises the exchange when it connects an integration and must verify the selected organisation or company file, employee mappings, earnings rates, pay calendars, leave types, exported hours, and provider response before processing payroll. An accepted or successful API response does not confirm that payroll is legally or factually correct.

Third-party outages, authorisation expiry, API changes, rate limits, and partial failures may delay or prevent an export. ROVYN may retain request, response, status, and error records to support reconciliation and troubleshooting. The Customer must not submit the same payroll data twice without checking whether an earlier export partially succeeded.

GPS Clock-In and Geofencing

When GPS clock-in is enabled, the service may record a precise point submitted by the user's device at clock-in, including latitude, longitude, reported accuracy, and calculated distance from a configured workplace. Device conditions and mapping data can make location records inaccurate. The feature is not a guarantee that a person was at a location or performed work.

The Customer decides whether to enable location collection and is responsible for necessity, proportionality, workplace-surveillance notices, policies, consultation, consents, signage, alternatives, access, and retention required by applicable Commonwealth, State, or Territory law. ROVYN does not authorise covert or unlawful surveillance. Customers must provide a non-GPS process where required by law or workplace arrangement.

Messaging and Attachments

Messaging is intended for ordinary workplace coordination. It is not designed as an emergency service, whistleblower hotline, medical-record system, or privileged legal-communications system. Delivery, push notifications, read indicators, and attachments may be delayed or unavailable.

The Customer must set appropriate workplace rules and permissions. Users should not place medical details, identity documents, payment-card information, passwords, or exceptionally sensitive allegations in general chats. Messages and audit metadata may be retained in the Customer's organisation record after a user is archived or de-identified.

Staff Requirements, Documents, and Signatures

TaskForceOne can help collect documents, licences, certificates, expiry dates, acknowledgements, and signatures. The Customer decides which records are required and must verify authenticity, validity, expiry, legal sufficiency, access restrictions, and retention. An electronic acknowledgement or stored signature may not satisfy every statutory or evidentiary requirement.

Automated Assistance and Human Review

Features may calculate estimates, detect conflicts, issue warnings, apply configured rounding, auto-approve configured events, or suggest workflow actions. Outputs depend on available data and may be incomplete, delayed, or wrong. The Customer must maintain meaningful human review for decisions that materially affect hiring, rostering, discipline, performance, termination, classification, working hours, or pay.

The Customer must not use a TaskForceOne output as the sole or determinative basis for a significant employment decision without checking the source data, configuration, context, applicable law, and the affected person's opportunity to raise an error.

Preview and Beta Features

A feature identified as preview, early access, trial, or beta may change or be withdrawn and may have limited support. The Customer should not rely on it for a critical payroll, safety, or legal workflow unless ROVYN expressly agrees otherwise in writing.

Contact

Questions about supported behaviour or rule coverage can be sent to [email protected].