Privacy Policy
Last updated 18 November 2026
Doovalacky (formerly TradieBridge) is a backup of the records a trade business keeps in the systems it connects, such as Simpro, Xero, Verizon Connect, Deputy, Employment Hero, The Fleet Office, Dialpad, Moveware, ELMO and Emailed reports, and a way for that business to connect its own AI assistant to the copy. It is made by Oli Nelson in Australia. In this policy, “we”, “us” and “our” mean Oli Nelson, and “the service” means Doovalacky, including the app at app.doovalacky.ai and this website.
We handle personal information under the Australian Privacy Act 1988 and the Australian Privacy Principles. This policy explains what we collect, why, where it goes, and how you can reach us.
Who the information is about
- Account holders and staff of a trade business that uses the service.
- Clients, contacts, staff and suppliers of that business, whose details sit in the documents the business copies.
- Partners who refer trade businesses to Doovalacky.
- Visitors to this website.
What we collect
- Account details: your name, email address and role in the business.
- Source documents: the records the business’s connections can read, such as jobs, quotes, invoices, timesheets, customers and sites; employee records, with employment details and leave; people being onboarded and job candidates; payroll records, such as pay runs and payslips, which can include tax file numbers, bank accounts and birth dates; vehicle locations, trips and drivers; phone calls, with who called whom, call recording and voicemail links, call transcripts, contacts and phone numbers; and removal jobs, with the customer’s addresses, an inventory of their goods and the goods they keep in storage. We store those documents as each system sent them.
- Connection details: the Simpro host and API key, the Xero, Deputy, Employment Hero and Moveware consents, the Verizon Connect and The Fleet Office API credentials, the Dialpad and Employment Hero Payroll API keys, and the ELMO client ID and client secret the business gives us. These are encrypted at rest.
- Emailed reports: every email sent to a business’s Emailed reports address at in.tradiebridge.com, whole: the sender, recipients, subject, body and attachments. We keep it until the business removes that source or closes its account. The business can export it, with every attached file.
- Feedback: what your assistant sends us with your approval, or what the help chat in the app passes on to our team. We store it against the business and the person who sent it.
- Help chats: every question you ask the help chat in the app, and every reply, stored against the person who sent them. The chat panel starts fresh after a day, but we keep the stored chat. Do not put a password, API key or token in the chat.
- Agent numbers: each SMS sent to a business’s agent number, an Australian mobile number the business gets from Doovalacky to receive sign-in codes, and the phone numbers the business confirms to receive the forwards.
- Partner details: a partner’s name, email address and business, its code, the businesses that signed up with that code, and what we paid the partner for each. Stripe collects the partner’s identity and bank details for its payouts. We do not hold those details.
- Technical data: IP address, browser and device details, sign-in times, and error reports.
We do not collect payment card numbers. Stripe handles cards. This website uses the Meta Pixel to measure how our ads perform. The same pixel runs on the public sign-in and sign-up pages at app.doovalacky.ai. It does not run inside the signed-in app, or on the docs. Meta sets its _fbp and _fbc cookies. No names, emails or business records are sent to Meta. The app uses a session cookie so you stay signed in. When you arrive at the app by a partner’s link, the app sets a partner_code cookie that holds the partner’s code for 60 days, so that the partner’s trial applies when you sign up. Scripts on the page cannot read it. This website sets two DataFast analytics cookies, and the app reads them. The visitor cookie, datafast_visitor_id, holds a random ID for 365 days. The session cookie, datafast_session_id, lasts 30 minutes.
Why we collect it
- To copy the business’s documents from the systems it connects into a backup the business owns.
- To receive the reports a business’s systems email to its Emailed reports address, and keep them in that backup.
- To keep that copy current, let the business browse it, and export it.
- To let the business connect its own AI assistant to that copy.
- To receive each SMS sent to a business’s agent number, and forward it to the phones the business confirms.
- To read the feedback a business sends us, and use it to improve the service.
- To run accounts, billing, and sign-in.
- To give a business the trial that a partner’s code brings, and to pay the partner its share.
- To keep the service secure, fix faults and send service notices.
- To meet legal duties, such as tax and record-keeping rules.
We do not sell personal information. We do not use it for advertising.
Assistants
A business can mint a token and connect its own AI assistant to the copy. When it does, that assistant reads the documents the business already holds. We do not send those documents to an AI provider of our own. The business is responsible for the assistant it connects.
An assistant can also send us feedback. It shows the text to the person using it, and sends it only when that person agrees. We store it and email it to our staff. Do not put a password, API key or token in it.
Feedback in the app
Feedback you submit in the app, and any screenshot you attach, is stored in Doovalacky and emailed to our team's inbox (hosted by a third-party email provider) so we can review and act on it. We use it only to support and improve Doovalacky.
Logins for systems without an official integration
Some systems a business uses offer no official integration. If a business asks us to, and we switch it on, Doovalacky signs in to such a system with a login the business gives us and reads the business’s records there. The business accepts the risks of that access when it connects. For that login, we:
- Encrypt it in transit, and at rest in our database with a key we keep outside that database.
- Use it only to sign in and read the records the business connected. Doovalacky changes nothing in that system.
- Never sell it or show it. No page, export, API or assistant tool shows it, to the business or to our staff. Our staff reach it only where strictly necessary to resolve a support request the business raised.
- Share it with nobody except the trusted infrastructure providers that help us connect to your systems (see below).
- Delete it when the business removes the connection or closes its account: from our database within 30 days, and from our backups as they expire, within 90 days.
Use a unique password for that login. Where the system offers it, give Doovalacky a login of its own with read-only access rather than a person’s login. A login whose second step is a code sent by SMS can be connected through an agent number the business holds. A login whose second step is an authenticator app cannot be connected. If you believe the login is compromised, remove the connection, change the password, and email [email protected].
Who we share it with
We share personal information only with providers that help us run the service:
- Hosting and storage: DigitalOcean, for the app, the database and file storage. Cloudflare, for this website, doovalacky.ai, and to forward email sent to [email protected].
- Email delivery: MailPace, for sign-in codes, export links, and the feedback emails to our staff. MailPace also receives the email sent to in.tradiebridge.com, and passes it to Doovalacky.
- Error monitoring: Sentry, for crash and error reports.
- Help chat: Anthropic, for the help chat in the app, if the business turns it on. It receives each message, the conversation so far, and a briefing: the person’s name and role, the business’s name, the names and sync state of the sources that person can see, and the app’s pages. When the chat looks up a source, Anthropic also receives which lists that source holds, how many records each has and when each was copied, never the records themselves or the source’s credentials.
- Page suggestions: TypeSafe, for the same help chat. After each reply, it receives the question, the reply and the list of the app’s pages, to pick a page to suggest. It receives nothing else.
- Agent numbers: Twilio, for the agent numbers. It receives each SMS sent to an agent number, and sends the forwards to the phone numbers the business confirms.
- Payments: Stripe, for subscriptions, and Stripe Connect, for payouts to partners. Stripe collects each partner’s identity and bank details through its own onboarding.
- Analytics: DataFast, for visits to doovalacky.ai, and for sign-up and subscription steps. It links these to a random visitor ID, never a name or email address. It also reads subscription amounts from Stripe, to show which visits led to a paid subscription.
- Ad measurement: Meta, through the Meta Pixel on this website and on the public sign-in and sign-up pages at app.doovalacky.ai, to measure how our ads perform. It records a visit, and when someone clicks through to sign up or sends an enquiry. No names, emails or business records are sent to Meta.
- Simpro: we call the Simpro API with the key the business gives us, to read the documents the business asked us to copy.
- Xero: we call the Xero API under the read-only consent the business gives, to read the documents the business asked us to copy.
- Verizon Connect: we call the Verizon Connect API with the credentials the business gives us, to read the documents the business asked us to copy.
- Deputy: we call the Deputy API under the consent the business gives, to read the documents the business asked us to copy.
- Employment Hero: we call the Employment Hero HR API under the consent the business gives, and the Employment Hero Payroll API with the API key the business gives us, to read the documents the business asked us to copy.
- The Fleet Office: we call The Fleet Office API with the API keys the business gives us, to read the documents the business asked us to copy.
- Dialpad: we call the Dialpad API with the API key the business gives us, to read the documents the business asked us to copy.
- ELMO: we call the ELMO API with the client ID and client secret the business gives us, to read the documents the business asked us to copy.
- Moveware (MoveConnect): we call the Moveware API under the consent the business gives through MoveConnect’s sign-in, to read the documents the business asked us to copy.
- Connection infrastructure: trusted infrastructure providers that help us connect to your systems. Where they handle a login the business gives us, they use it only to make that connection.
Some of these providers store data outside Australia, including in the United States. We choose providers that commit to protecting personal information to a standard comparable to Australian law.
We also disclose information when the law requires it, or to protect the rights, property or safety of people.
How long we keep it
We keep the copy for as long as the business keeps its account. When a business closes its account, or removes a connection, we delete that connection’s copy. We delete each SMS sent to an agent number after 24 hours. Backups of our own database expire on their own cycle. See our data deletion page for how to request deletion.
Security
Data is encrypted in transit. API keys, logins and the SMS sent to agent numbers are encrypted at rest. Access to production systems is limited to the people who operate the service. No system is perfectly secure, and we will tell affected people and the regulator about a data breach where the law requires it.
Your rights
You can ask us for a copy of the personal information we hold about you, and ask us to correct it. If you are a client or contact of a business that uses the service, you can also ask that business directly, since it controls those records. We respond within 30 days.
Contact
Email [email protected]. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
Changes
We update this policy when the service changes. The date at the top shows the latest version.