What the final policy should cover
The approved policy should identify the DayNext operating entity and explain what information is collected, why it is needed, where it is processed, who can access it and how long it is retained.
Product and account information
DayNext may need account details and the project, task, item, cost and property information that customers choose to enter. The final policy must describe this accurately based on the production service design.
Connected services
The final policy should clearly explain optional integrations such as Xero and transactional email, including the limited purpose of access and the relevant third-party terms. DayNext’s Xero connection is designed to read accounting information rather than write transactions back.
Your questions and choices
The approved policy should explain how to request access, correction or deletion where applicable, and how to contact DayNext about privacy.
Contact
Until approved legal contact details are confirmed, privacy questions can be directed to hello@daynext.au.
Placeholder prepared 18 August 2026. Formal review required before launch.