Privacy policy
Last updated 1 October 2026
MechConnect answers the phone for trade businesses. That means we handle two different kinds of information, and it matters which one you are.
- If you rang a business and we answered — we took down what you told us so the business could follow up your booking. Section 1 is about you.
- If you are a business using MechConnect — we hold your account and billing details. Section 2 is about you.
We do not record calls. No audio is captured, stored, or kept for any period. What exists is a written note of the conversation, and nothing else. This is a design decision, not a setting — there is no audio store to turn on.
The standard we hold ourselves to. Australian privacy law exempts small businesses — under $3 million a year — from the Australian Privacy Principles. We are telling you that rather than letting you assume otherwise. We follow them anyway, and this policy is written to them. The Government has said the exemption should go; when it does, nothing here will need to change.
1. If you called a business that uses MechConnect
We tell you at the start
Every call opens by saying that the call is being noted down so your booking can be followed up. You hear this before you say anything.
What we write down
Only what you tell us, and only what the business needs to do the job:
- Your name and the phone number you called from
- Where the work is needed
- What you are driving, where that is relevant
- What the problem is, in your words
- The time you agreed to
A written transcript of the conversation is kept alongside those details.
Because there is no recording, that transcript is the only record of what was said. We are not built to take payments over the phone and you should not be asked for a card. If you read a card number out anyway, we look for it and remove it before the transcript is saved.
Who it is for, and who is responsible for it
The business you called. We are answering their phone on their instructions — they decide what happens with your booking, and you are their customer, not ours. In privacy law terms they are the ones responsible for your information and we handle it for them.
That matters if you want something changed or removed: you can ask either of us. If you ask us, we will do it and pass the request on, because they hold their own copy of the booking.
We do not sell it, rent it, share it for advertising, or use it to contact you about anything other than the job you rang about.
Where your booking goes
Into the business's calendar, so the mechanic turns up. And if the business runs its jobs in ServiceM8 or its books in Xero and has connected them to MechConnect, the booking goes there too, on their instruction: a message in their ServiceM8 Inbox with your details, or a contact and a draft invoice in their Xero, with nothing on it until the mechanic prices the job. Those are the business's own systems, and what is in them is theirs. ServiceM8 and Xero hold it on their own servers under their own privacy policies, which may be outside Australia — section 3 says what each company has published about that.
If you ring again
When you call a business you already have a booking with, we check the number you are calling from, and any number you give us, against that business's bookings — ones still to come and ones from the last five days — so the call can be handled as a call about your booking. We never read the details of a booking back to you over the phone, so anyone who rings from your number learns nothing about it from us.
How long we keep it
| What | Kept for |
|---|---|
| Call transcripts and booking details | 12 months, then deleted |
| Technical system logs | 90 days maximum |
| A small number of transcripts kept to check and improve how the receptionist handles calls | Longer than 12 months — see below |
That last row is a real exception and we would rather write it down than have you find it. A small sample of calls is retained beyond the normal 12 months so we can measure whether the receptionist is getting things right — hearing an address correctly, understanding what is wrong with a vehicle. If you would prefer your call was not used this way, tell us and we will remove it.
SMS
If a text message is part of following up your booking, we send it to the number you called from, in the name of the business you rang. We do not add you to a marketing list.
2. If you are a business using MechConnect
We hold what you give us to run the service: your business name and contact details, your phone number and hours, your service area and pricing, and the settings that tell the receptionist how to answer.
Your calendar
With your permission, MechConnect connects to your calendar so it knows when you are free and can write bookings into it.
We do read the events already in your calendar, and we are not going to pretend otherwise, because it is the whole reason the booking works. If we could only see our own bookings we would cheerfully offer a customer three o'clock while you were already at the dentist. Knowing what is in your day is how we avoid booking on top of it.
- Google Calendar — you sign in with Google and grant access there; the details are below.
- Outlook and Microsoft 365 — you sign in with Microsoft and grant
Calendars.ReadWrite, which Microsoft describes as full access to your calendars. It is the narrowest permission Microsoft offers that can write a booking; we use it only on the one calendar you pick. The tokens Microsoft gives us are encrypted before they are stored. - Apple Calendar and other CalDAV calendars — we use an app-specific password you generate, which is encrypted before it is stored. We read the calendar you nominate to see when you are free, and write the bookings we make for you into it.
Whichever you connect, we look at your existing events to answer one question — are you free then, and can you get there? — and for nothing else. We do not store the titles or descriptions of your events: we keep their start and end times, whether they are all-day, how they repeat, and the location, if the event has one, so we can work out the drive to and from it.
Disconnecting is available at any time and removes our access immediately. Calendar data is never used for advertising and never sold.
Your Google Calendar
If you connect a Google calendar, you are sent to Google to sign in and choose what to allow, then brought straight back. We never see your Google password.
- What we ask Google for. Four permissions, and nothing else in your Google account:
calendar.events.owned, which Google describes as seeing, creating, changing and deleting events on calendars you own;calendar.calendarlist.readonly, to list your calendars so you can pick which one is the work calendar; andopenidandemail, to learn which Google account you signed in with. We do not ask for your email, your contacts, your files, or calendars that are only shared with you. If you untick either calendar permission on Google's screen, we connect nothing and tell you which one was missing. - What we read. The events on the one calendar you pick, for four weeks ahead and a day behind, about once a minute: when each one starts and ends, whether it is all-day, and its location. That is what tells the receptionist when you are busy and how far you would have to drive. We also read the calendar's name, so the settings page can show you which one is connected. We skip the working-location and birthday entries Google adds by itself, because they are not jobs.
- What we write. One event per booking the receptionist agrees, on the calendar you picked: the job, the car, the caller's name and number, and the address, at the time the caller was given. A reschedule moves that event and a cancellation deletes it. We never change or delete an event we did not create.
- What we keep. The tokens Google gives us, encrypted before they are stored and never shown back, even to us; your Google account's id and address; the name and id of the calendar you picked; and the copy of your calendar's times and locations described above, which is replaced every time we read it, so an event you delete or move in Google is gone or moved here within a minute or two.
- Where it goes. Your calendar's times and locations stay in our database in Sydney. The one exception is an event's location, which we send to Google Maps to work out drive times. A calendar detail may appear in a notification we send you about a booking, such as a warning that a job clashes with one already in your diary; that goes to you and nobody else. None of it is ever given to the language model that holds the conversation, shown to a caller, sold, used for advertising, or used to train or improve any AI model.
MechConnect's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the calendar features described here, which you can see and control. We do not transfer it to anyone except as needed to provide those features, to comply with the law, or as part of a merger or sale of MechConnect with notice to you. No person at MechConnect reads your calendar data unless you ask us to for support, it is needed for security, or the law requires it.
Disconnecting. Press Disconnect on the calendar settings page and we delete the tokens, your account details and the copy of your calendar's times and locations, ask Google to revoke MechConnect's access, and stop reading and writing, all at once. You can also remove MechConnect at myaccount.google.com/permissions; that cuts us off immediately, and pressing Disconnect here afterwards deletes what we hold. Bookings we already wrote into your calendar stay there, because they are yours.
Your ServiceM8 account
If you connect ServiceM8, every booking your receptionist takes is placed in your ServiceM8 Inbox as a message, so that Convert to Job lands a filled-in job card. The integration was built by MechConnect and is supported by MechConnect; ServiceM8 did not develop it and does not endorse it.
- What you give us. An API key you generate in ServiceM8 under Settings → API Keys and paste into the console. We prove it against your account before we keep it, which reads your account's name, its ServiceM8 id and its time zone — the three things the settings page shows you so you can see what is connected. The key is encrypted before it is stored and is never shown back, even to us.
- What we write. One Inbox message per booking, sent under the caller's name: the time agreed, the job, the car, the caller's name and number, and the address, with the fields filled so the job card is populated when you convert it. A reschedule or a cancellation is a fresh message, not an edit. We never create a job, a client or a diary entry, never send a text message from your account, and never touch a job you have converted.
- What we read. Before we write, we read the most recent page of your Inbox — up to 500 messages, whoever sent them — and look for our own reference on a message we already sent, so a booking is never posted twice. We look, and we keep nothing from that read. We do not read your jobs, your clients, your diary or your staff.
- What we keep. The encrypted key, the three account details above, and for each booking the id of the message we sent, so we can find it again.
- Your plan. The Inbox is a feature of ServiceM8's Growing plan and above, with Email Inbox switched on. That is ServiceM8's rule, not ours, and a job card you convert counts against your plan the way any job does.
Disconnecting. Press Disconnect on the ServiceM8 settings page and we delete the key and the account details at once and stop sending. Revoking the key in ServiceM8 stops us just as fast; if you do it that way, press Disconnect here as well so nothing is left with us. Either way, the messages already in your Inbox and the jobs you made from them stay in ServiceM8, because they are yours.
Your Xero organisation
If you connect Xero, every booking your receptionist agrees raises a draft sales invoice in your Xero organisation, with the caller as a contact, so pricing the job after you have done it is one screen rather than a retype. MechConnect built and supports this integration independently of Xero; Xero did not develop it, does not endorse it, and is not a party to anything between you and us.
- What you give us. You are sent to Xero to sign in and pick the organisation, then brought straight back. We never see your Xero password. Xero hands MechConnect a pair of tokens — one that lets us act for the next half hour and one that renews it — and we encrypt both before they are stored. Nobody can read them back, us included.
- What we ask Xero for. Four permissions, in Xero's names for them:
openid, to learn which organisation you picked;offline_access, so we can keep the connection alive between bookings without sending you back to sign in; andaccounting.contactsandaccounting.invoices, which Xero describes on its consent screen as viewing and managing your contacts and invoices. That is the narrowest set that can create a contact and a draft. What we actually do with it is the next two points, and nothing else. - What we write. For each caller, a contact carrying their name, mobile and address, plus a reference number of ours so a repeat caller is found again however their name was heard. For each agreed booking, a draft sales invoice with one line — the job and the car, no amount, dated for the booking — a link back to the call in your console, and a note in the invoice's History and notes with the time, the address, the caller's number, who took the call and our reference. A reschedule edits that line; a cancellation deletes the draft. Both only while the invoice is still a draft. Once you have approved it, we never touch it again, and we never approve, send, void or pay anything.
- What we read. Whether a caller already has a contact (by our reference on it, then by name), and whether a booking already has a draft (by its reference), so nothing is created twice. We do not read your other invoices, your contacts in general, your bank feeds or your reports, and nothing we read is kept beyond the ids of the contact and the draft we made.
- What we keep. The encrypted tokens, your organisation's id and name, and for each booking the id and number of its draft.
- The connection lapses. Xero keeps a connection alive for 60 days from its last use. Every booking renews it; a quiet two months lets it lapse, and the settings page tells you when that is coming and asks you to connect again.
Disconnecting. Press Disconnect on the Xero settings page and we ask Xero to remove MechConnect from your organisation's connected apps, delete the tokens from our systems, and stop sending — all at once. Removing MechConnect in Xero, under Settings → Connected apps, cuts us off immediately too; press Disconnect here afterwards so we forget the tokens. Contacts and drafts already in Xero stay there, because they are yours.
Anything that passes through a connected ServiceM8 account or Xero organisation is used for one thing: putting your bookings where you asked for them. It is never used for advertising, never sold, never combined with anyone else's data, and never handed to a third party. Section 5 says the same about AI training, and it applies here without exception.
Payments
Subscription payments are processed by Stripe. Your card details go to Stripe directly and are never held by us — we see only the last four digits and the outcome of the charge.
If you leave
Your bookings and call notes are yours to take. The terms set out how to ask for them and how long you have — see section 4 of the terms.
3. Where your information lives
In Australia. The database, your records and your transcripts are in Sydney, and so is every server that answers your calls. Speech-to-text and the voice you hear are processed in Australia.
Two steps are not. The language models that compose what the receptionist says and read the job details out of a call are run by OpenAI, in the United States. OpenAI does not offer this service from Australia, so those steps are always served from overseas.
What those steps receive is the text of the conversation so far. No audio ever leaves Australia. We ask OpenAI not to store it, and under OpenAI's terms for its API it may keep it for up to 30 days to check for abuse and then deletes it. We remain responsible to you for how it is handled.
Two more steps use Google Maps, and Google does not promise where it processes them either, so they may be handled outside Australia. To check that an address is inside the business's service area and to put it on the map, we send the address to Google's Geocoding service: a caller's address, and the location written on an event in a connected calendar. To work out the drive between jobs, we send Google's Routes service the two map points and nothing else. Neither receives a name, a phone number, a description of the job or anything from the conversation beyond the address itself, and Google handles them under its Google Maps Platform terms.
Two more places are yours to choose, and nothing goes to either unless you connect it. If a business connects ServiceM8 or Xero, the bookings we send there are held by those companies, on their servers, under their own privacy policies. Xero has published that it hosts its service on Amazon Web Services in the United States. ServiceM8 has published that its data may be stored and processed in any country where it operates, and is backed up to Amazon's infrastructure in multiple locations around the world. Neither is a step we run; each happens only because the business connected its own account, and only that business's bookings go there.
4. Who else touches it
| Who | What they do |
|---|---|
| Telnyx | Carries the phone calls and text messages, and converts speech to text. All of this happens in Australia |
| OpenAI | Runs the language models that compose what the receptionist says and read the job details out of a call, in the United States — see section 3 |
| DigitalOcean | Hosts the servers and the database, in Sydney |
| Stripe | Processes subscription payments from businesses |
| Google Maps finds a caller's address and works out drive times between jobs. Google Calendar, only where you have connected one, and only for that | |
| Apple / Microsoft | Only where you have connected an iCloud or Outlook calendar, and only for that |
| ServiceM8 | Only where you have connected your ServiceM8 account, and only to put your bookings in its Inbox |
| Xero | Only where you have connected your Xero organisation, and only to raise a contact and a draft invoice for each booking |
That is the whole list, and we keep it that way deliberately. Each of these does one job for us and nothing else with what passes through it. The last three rows are different in kind from the first five: they are systems a business connects for itself, and the data that reaches them is that business's own bookings, sent on its instruction. If we ever add another, this table changes and businesses using MechConnect are told before it happens.
5. Nothing here trains an AI model
Nothing you or your customers say is used to train an AI model. Not the transcripts, not the bookings, not your calendar. OpenAI, which runs the language models, does not train on what is sent through its API, under its terms with us; Telnyx is contractually barred from training on what passes through it.
The one thing we do keep is the accuracy sample described in section 1, and it is worth being precise about what that is. We compare what the receptionist heard against what was actually said — did it get the street name right, did it understand the fault — and we count how often it was wrong. That is us marking our own work against a known answer. It does not change the model, and it never leaves us.
A business using MechConnect can ask to be left out of that sample. A caller can ask for their own call to be removed from it. Either way, just tell us.
The same goes for anything that comes back from a connected calendar, ServiceM8 account or Xero organisation. It is read to do the one job described in section 2, and it is never used to train, tune or improve a model, ours or anyone else's.
6. Keeping it safe
- Every connection is encrypted in transit.
- Each business's data is isolated from every other business's at the database level.
- Credentials are encrypted at rest and are never displayed back, even to us. That covers your calendar password, your ServiceM8 key and your Xero tokens alike, each sealed under a key that lives outside the database, so a copy of the database on its own cannot open them.
- Access to production systems is restricted to keys held by the operator.
7. If something goes wrong with your information
If we find that information has been accessed, disclosed or lost when it should not have been, we tell the affected business within 48 hours of confirming it, in writing, with what we know so far and what we are doing about it. We tell you at 48 hours even if we do not yet have the full picture, because you may have your own obligations running on their own clock.
Where the law requires the people affected and the Office of the Australian Information Commissioner to be notified, we do that too, and we do not wait to be asked. If the information came through a system you connected, we tell that company as well, within the time its developer terms set — which can be as short as 24 hours.
8. Your rights, and how to complain
You can ask us what we hold about you, ask us to correct it, or ask us to delete it. Write to the address below and we will respond within 30 days. We do not charge for it. For anything we hold from a connected calendar, ServiceM8 account or Xero organisation, you do not need to ask: pressing Disconnect in the console deletes it at once.
If you called a business and want your details removed, we will pass the request to that business as well, since they hold their own copy of the booking.
If you think we have handled your information badly, complain to us first at the address below. We will acknowledge it within five business days and give you an answer within 30 days, in writing, including what we are doing about it.
If that answer doesn't satisfy you, you can take it to the Office of the Australian Information Commissioner at oaic.gov.au or 1300 363 992. You do not need our permission and we will not hold it against you.
9. Cookies, and what this website doesn't do
This website sets no cookies at all. There is no Google Analytics, no advertising pixel, no tracker of any kind, and nothing here follows you anywhere else. We know how much of your business day this page is worth and it is not worth that.
The signed-in area sets one cookie, which keeps you signed in and does nothing else. It stays on our own site, it lasts at most 30 days and expires sooner if you stop using it, and there is no way to be signed in without it.
10. Changes
If this policy changes, the date at the top changes with it. We will not quietly broaden what we do with information already collected.
11. Contact
MechConnect Pty Ltd
ACN 702 185 822 · ABN 66 702 185 822
trading as MechConnect
privacy@mechconnect.com.au
That address reaches the person responsible for privacy at MechConnect. For anything else, contact support@mechconnect.com.au.