Home / Privacy
Privacy policy
What RattleGun holds, why, and what a workshop or its customer can ask us to do about it.
Last updated 4 November 2026.
Who we are
RattleGun is workshop software operated by DoubleKlick. This policy explains what we do with information when a workshop uses RattleGun, and when a customer of that workshop deals with it. Questions and requests go to [email protected].
What we hold
- Workshop account details: business name, contact details, staff accounts and their roles.
- The records a workshop enters: customers, vehicles, jobs, parts, invoices, inspections and appointments.
- Messages sent and received through the product, including phone, SMS, email and web chat, with delivery status.
- Payment records. Card details are entered with our payment provider and are not stored by RattleGun.
- Technical logs: sign in events, errors and request metadata, kept for security and support.
Why we hold it
To run the service the workshop has asked for: showing the workshop its own records, sending the messages it asks us to send, keeping the books straight, supporting the people using it, and keeping the system secure. We do not sell information, and we do not use a workshop's customer data for our own marketing.
Who else sees it
Only the providers needed to deliver a feature the workshop has switched on, such as the carriers that deliver SMS, the service that delivers email, a payment provider, and an accounting system the workshop connects. Each receives only what the feature needs. Our own staff see records only where support or a fault requires it.
Where it is held
On infrastructure we control, in data centres in Australia. A provider above may process a message outside Australia to deliver it, and where that happens we take reasonable steps to ensure it is handled consistently with this policy.
How long we keep it
For as long as the workshop's account is open, because the records are the workshop's service history. When an account closes, we delete or de-identify its data on request, except records the workshop is required by law to keep, which are returned to the workshop instead.
Security
Access is scoped to a workshop, so one workshop cannot see another's records. Traffic is encrypted in transit, stored credentials for third party services are encrypted, and access to production is restricted and logged.
Access, correction and complaints
A workshop can export and correct its own records from the product. For anything else, write to [email protected] and we will respond within a reasonable period. If you are not satisfied with our response, you can contact the Office of the Australian Information Commissioner at oaic.gov.au.
Cookies
RattleGun uses the cookies needed to keep a signed-in session working. The public site does not carry advertising or third party tracking cookies.
Book a demo
Half an hour, your workflow, no slides.