Last updated: 21 May 2026
iDilap is a private, internal software application developed by Dilap Group Pty Ltd. This policy describes how iDilap handles data.
1. What data iDilap accesses
iDilap reads and writes data from Dilap Group’s own accounts on third-party services that the user has authorised, including:
- QuickBooks Online — customers, items, invoices
- ClickUp — projects, lists, tasks
- Geoscape G-NAF and OpenStreetMap — public Australian address and mapping data
iDilap also reads and writes Dilap Group’s internal business data stored locally on the user’s computer, including tender, project, and CRM records.
2. Where data is stored
Operational data (tenders, projects, contacts, generated documents) is stored in files on Dilap Group’s own OneDrive folder, accessible only to authorised users.
Authentication tokens for third-party services (such as QuickBooks Online OAuth tokens) are stored in a local secrets file on the user’s computer. This file is excluded from version control and is never transmitted to any party other than the service it authenticates with.
3. What iDilap does NOT do
- iDilap does not share data with any third party other than the services the user has explicitly connected to.
- iDilap does not collect analytics or telemetry about its users.
- iDilap does not transmit user data to the developer outside of the user’s own machine.
4. Retention and deletion
To remove iDilap’s local data, the user deletes the iDilap application folder. To revoke third-party access (for example QuickBooks Online), the user revokes the connection in that third-party service.
5. Contact
For questions about this policy contact:
