Privacy policy

How we handle personal information, in plain English.

Last updated: 14 November 2026

This policy explains how Osborne Digitals collects, uses, shares and protects personal information. It follows the structure of the Australian Privacy Principles and covers our website, our website and care plan services, our AI receptionist services (including callers to our clients' AI receptionists), and our Switch services (Studio Switch and Review Switch).

1. Who we are

Osborne Digitals is a sole trader business run by Tyson Osborne, ABN 26 384 573 254 ("we", "us", "our"). We build websites and provide care plans, Google Business Profile services, AI receptionists and Switch services for tradies and small businesses. Our website is osbornedigitals.com.au. Contact: osbornedigitals@gmail.com.

2. What we collect

Website visitors. Like any website, our hosting provider receives technical information when you visit, such as your IP address, browser type and the pages you request. We don't use analytics or advertising tracking on our website (see section 12). The chat assistant on our website gives automated answers inside your browser. It doesn't send or store what you type.

Enquiries. When you use our contact form or email us, we collect what you send: usually your name, business name, phone number, email address, town or suburb, the service you're interested in and your message.

Customers and clients. When you buy from us or sign up, we collect:

  • contact and business details: name, business and trading name, ABN, email, phone, business address, opening hours, service area and the services you offer;
  • content for your website or profiles: logo, photos, files, wording, colours, links to your Google Business Profile and social media pages, and anything else you send us;
  • AI receptionist setup details: your mobile number, assistant name, greeting, voice choice, emergency and booking preferences, mobile carrier (so we can give you the right call divert codes), and any notes on what your receptionist should or shouldn't say;
  • access keys for your other systems: if you choose to connect job management software such as ServiceM8, the API key you create for us. We store it encrypted and use it only to connect your AI receptionist;
  • payment and billing details: what you bought, amounts paid, invoices and subscription status, and your billing address. Card payments are handled by Stripe. We don't see or store your full card details;
  • change requests, support messages and other correspondence with us;
  • if you use the AI receptionist owner app: your username and login sessions (passwords are stored only in hashed form), the availability, job and contact settings you enter, and any personal contacts or blocked numbers you add so the receptionist can recognise or screen them;
  • calendar connection: if you choose to connect Google Calendar or an Outlook / Microsoft 365 calendar, a secure access token and the account and calendar you chose (see sections 8 and 9).

Callers to our clients' AI receptionists. When someone calls a business that uses our AI receptionist, the call is answered by an AI voice assistant, and the call is recorded and transcribed. We collect the caller's phone number, the call recording, the transcript, an automated call summary, call times and duration, and the details the caller gives, such as their name, suburb or postcode, address, job details, preferred times and whether it's urgent. A caller may also get a text with a secure link to check or complete their details (for example, a street address) and may reply by text. We keep those details and replies too. On our Missed Call Saver plan, a caller can leave a voicemail, which is recorded, and is sent an automatic text. If the business has switched on emergency transfers, the AI receptionist may put an urgent call through to the business owner or their backup contact.

Job photos. If you choose to add photos of the job when you finalise a booking, we store them securely so the business can quote and bring the right parts.

Our AI receptionist demo. If you call our demo receptionist or try the demo in your browser, we collect the same kinds of call information. For browser demo calls, we also keep a scrambled (hashed) form of your IP address to apply fair-use limits.

We don't ask for sensitive information, such as health information. If a caller mentions it, it may appear in the call recording or transcript.

You can browse our website and ask our chat assistant questions without telling us who you are. To give you a quote or provide a service, we need your contact details.

3. How we collect it

  • Directly from you: through our website forms (contact, onboarding, AI receptionist setup, Reviews Care setup, change requests and "manage my plan"), by email, by phone and through the owner app.
  • Through Stripe when you pay at checkout, which passes us your name, business name, email, phone and billing details.
  • Through calls and texts handled by the AI receptionist service for our clients.
  • From your Google Business Profile or Facebook page, when you give us manager access so we can set up or look after it for you.
  • Automatically, as technical information when you use our website.

4. How we use it

  • To reply to enquiries and prepare quotes.
  • To build, host and look after your website, Google Business Profile and care plan.
  • To set up and run your AI receptionist: answering calls, taking messages, booking jobs, sending texts to you and your callers, and showing the details in your owner app.
  • To take payments, send invoices and receipts, and manage your plan.
  • To give support, fix problems and improve our services.
  • To keep our services secure and prevent misuse, for example limits on demo calls.
  • To meet our legal obligations, such as tax and business record keeping.

We use information only for the purpose we collected it for, a related purpose you'd reasonably expect, or where the law allows or requires it.

5. AI receptionist callers: our role

When we run an AI receptionist for a business, we handle callers' information on behalf of that business. The business (our client) is responsible for its relationship with its customers, including how it uses their details after we pass them on, and, where the law requires it, telling callers that calls are answered by an AI and are recorded and transcribed. We use callers' information only to provide the service to that business and to support and improve the service. We don't use it to market our own services to callers.

If you've called one of our clients and want to access, correct or delete your information, contact that business. You can also contact us, and we'll work with the business to help.

6. Who we share it with

We don't sell personal information. We share it only with:

  • Our clients: callers' details, messages, bookings, recordings and transcripts go to the business the caller rang, through texts and the owner app.
  • Service providers who help us run the business:
    • Cloudflare: website and app hosting, security, and the database that stores AI receptionist bookings, messages and call records;
    • Stripe: payments, invoices and subscriptions;
    • Resend: sending emails from our website (form submissions, payment alerts and "manage my plan" links);
    • Twilio: phone numbers, call handling, text messages and Missed Call Saver voicemail recordings;
    • Retell AI: the AI voice assistant that answers calls. Retell records, transcribes and summarises calls and stores the recordings and transcripts. Retell uses AI voice and language providers to generate speech and understand calls. If a business connects Google Calendar, Retell also receives the open appointment times the receptionist offers callers, and nothing else from Google (see section 8);
    • Google: our business email (Gmail), where form submissions and correspondence are kept, and Google Fonts, which our website loads from Google's servers;
    • the domain name registrar we use when we register a domain in your name.
  • Systems you choose to connect:
    • ServiceM8 (only if you connect it): we send the job details from each booking (customer name, phone, address and job) to your own ServiceM8 account, and read your ServiceM8 schedule so the receptionist offers suitable times;
    • Google (only if you connect Google Calendar): when a business owner connects their Google Calendar, we send Google the "Pencilled in" job details (customer name, phone, address and job) to put into the owner's own calendar. See section 8;
    • Microsoft (only if you connect Outlook): when a business owner connects their Outlook or Microsoft 365 calendar, we send Microsoft the same "Pencilled in" job details to put into the owner's own calendar. See section 9.
  • Others where the law requires or allows it, for example a government agency or a court.

Overseas disclosure. Most of these providers are based in, or store and process data in, the United States, and some operate global networks that may handle data in other countries. When we use them, your information may be stored or processed outside Australia. We choose established providers and only share what's needed for the service.

7. Storage and security

Information is stored with the providers listed above, not on paper. We take reasonable steps to protect it, including encrypted (HTTPS) connections, password-protected accounts, hashed app passwords, encrypted storage of access keys for your other systems, secure expiring links for callers and voicemails, and limiting access to people who need it to provide the service. We can only sign in to a client's owner app to help with setup or support while the client has switched on builder access in their settings, and those sign-ins are logged, with the most recent ones listed in the client's settings. Job photos are only visible to that business in its app, are never made public, and have location and other camera data removed when uploaded. No system is completely secure. If a data breach is likely to cause serious harm, we'll act quickly to contain it and let the people affected know.

8. Google Calendar connection (Google user data)

Business owners who use our AI receptionist can choose to connect their Google Calendar from the app's Settings. This is optional and only happens when the owner presses Connect Google Calendar and agrees on Google's own screen. Callers and customers never sign in to Google through us.

What we access, and why

Google permissionWhat we do with it
See the list of your Google calendarsShow you your calendar names so you can choose which one the receptionist uses.
See your availability (free/busy)Check when you're busy so the receptionist only offers callers times when you're free. We only receive busy and free times, not your event titles, descriptions, locations or guests.
Create, change and delete events on calendars you ownAdd a "Pencilled in" event for each job a caller books with the receptionist, update it if the job changes, and remove it if the job is cancelled. We only change the events our app created. We never read, change or delete your other events.

What we store

  • A secure sign-in token from Google, so the receptionist can keep checking your calendar without you signing in every time. It's encrypted (AES-256) and kept only on our server. It is never shown in the app and never written to logs.
  • The name of the Google account and calendar you chose, and the ID of each "Pencilled in" event we created (so we can update or remove it).
  • We don't keep a copy of your busy times beyond a few minutes of temporary memory, and we don't store any other calendar data.

What goes into your calendar. The "Pencilled in" events contain the job details the caller gave the receptionist (name, phone number, address, job description and a link to the job in your app). That information comes from your caller, not from Google, and it's handled as described in the rest of this policy.

How the receptionist uses it. Our server works out your open times (your business hours, minus the times Google says you're busy). When a caller wants to book, only those open appointment times (for example, "Tuesday at 10 am") are passed to the AI voice assistant so it can offer them to the caller. We never read your event titles, descriptions, locations or guests, so they never reach any AI. Your calendar names, account details and sign-in token are never sent to the AI.

Who sees it. Google user data is used only to provide the calendar features above, for the business that connected the calendar. We don't sell it, we don't use it for advertising, and we don't use it, or allow it to be used, to train or improve AI or machine-learning models, including generalised or foundation models. We share it only with:

  • the hosting provider that runs our app (Cloudflare), which stores it encrypted on our behalf;
  • Retell AI, the voice platform that runs the receptionist, which receives only the open appointment times described above so the receptionist can offer them to the caller. For calendar-connected receptionists, Retell is set not to store call recordings, transcripts or logs after the call, and data that Retell doesn't store is excluded from its model training. Retell's language, speech-recognition and voice providers process call data under zero-data-retention, no-training terms. Our own copy of the transcript, which can include the times offered, is kept in our app and deleted after 90 days (see section 10);
  • if the law requires it;
  • as part of a sale or merger of our business, with your Google data still protected by this policy.

No person at Osborne Digitals reads your Google calendar data unless you ask us to (for example, to help with a problem), it's needed for security reasons (such as investigating abuse), or the law requires it.

Limited Use. The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements. Osborne Digitals' 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.

Disconnecting and deleting. You can disconnect at any time: press Disconnect in the app's Settings. We then cancel our access with Google straight away and delete the stored token. You can also remove access in your Google Account (myaccount.google.com, then Security, then Your connections to third-party apps). After you disconnect, events we already added stay in your calendar (they're yours, and you can delete them in Google Calendar). Our record of which events we created is deleted with your account, or sooner if you ask. Email osbornedigitals@gmail.com to have your Google-related data deleted.

9. Outlook / Microsoft 365 calendar connection (Microsoft account data)

Business owners who use our AI receptionist can choose to connect their Outlook calendar (a personal Outlook.com/Hotmail account or a work or school Microsoft 365 account) from the app's Settings. This is optional and only happens when the owner presses Connect Outlook and agrees on Microsoft's own screen. Owners connect either Google Calendar or Outlook, not both. Callers and customers never sign in to Microsoft through us.

What we access, and why

Microsoft permissionWhat we do with it
Read and write your calendars (Calendars.ReadWrite)List your calendar names so you can choose the one the receptionist uses; check when you're busy so it only offers callers times when you're free; and add, move or remove one "Pencilled in" event for each job a caller books. Microsoft doesn't offer a smaller "free/busy only" permission for personal accounts, so this permission technically allows more. We only ever ask Microsoft for the start time, end time and busy/free status of your events, never their titles, descriptions, locations or attendees, and we only change or delete events our app created.
Maintain access (offline_access)Keep the connection working without you signing in again every hour.
Sign you in and read your profile (User.Read)Show which Microsoft account is connected (its email address only).

What we store

  • A secure sign-in token from Microsoft, so the receptionist can keep checking your calendar without you signing in every time. It's encrypted (AES-256) and kept only on our server. It is never shown in the app and never written to logs.
  • The email address of the Microsoft account and the calendar you chose, and the ID of each "Pencilled in" event we created (so we can update or remove it).
  • We don't keep a copy of your busy times beyond a few minutes of temporary memory, and we don't store any other calendar or account data.

What goes into your calendar. The "Pencilled in" events contain the job details the caller gave the receptionist (name, phone number, address, job description and a link to the job in your app). We add no attendees, so Microsoft doesn't send anyone an invitation.

Who sees it. Microsoft account data is used only to provide the calendar features above, for you. We don't sell it, we don't use it for advertising, and we don't use it to train AI or machine-learning models. We don't share it with anyone, except the hosting provider that runs our app (Cloudflare, which stores it encrypted on our behalf), if the law requires it, or as part of a sale or merger of our business with your data still protected by this policy. No person at Osborne Digitals reads your calendar data unless you ask us to (for example, to help with a problem), it's needed for security reasons, or the law requires it.

Disconnecting and deleting. Press Disconnect in the app's Settings and we delete the stored token straight away. To remove the permission on Microsoft's side too, open account.live.com/consent/Manage (personal accounts) or myapps.microsoft.com (work or school accounts) and remove Osborne Digitals. After you disconnect, events we already added stay in your calendar (they're yours, and you can delete them in Outlook). Our record of which events we created is deleted with your account, or sooner if you ask. Email osbornedigitals@gmail.com to have your Microsoft-related data deleted.

10. How long we keep it

  • Enquiries: kept for 2 years after your last contact with us, then deleted.
  • Clients: kept while you're a client and for up to 5 years after your service ends, for tax and record-keeping purposes, then deleted or de-identified.
  • AI receptionist call information (bookings, messages, texts, call logs and call summaries shown in the owner app): kept while the client's service is active, so the client can see their jobs and history. It's deleted when the client asks, or within 90 days after the service ends. Some data is deleted automatically: postcode lookups after 2 days, and demo browser call records after 30 minutes. Links sent to callers to check their details expire within 7 days, and voicemail links within 30 days.
  • Access keys for your other systems (such as a ServiceM8 API key, or a Google or Microsoft calendar token): deleted when you disconnect, when your service ends, or sooner if you ask. You can also remove our access in that system at any time.
  • Call recordings and transcripts are deleted automatically 90 days after the call, for all clients. This covers the recordings and transcripts held by Retell AI, the copy of each transcript kept in our database, and voicemail recordings held by Twilio.
  • Job photos are deleted automatically 90 days after they are uploaded.

You can ask us to delete your information at any time. We'll do so unless we need to keep it by law.

11. Marketing

We don't sell or rent your information. We'll only send you marketing emails if you've agreed to receive them, and you can opt out at any time by replying or emailing us. Messages about your service, payments or account aren't marketing and will still be sent while you're a client.

12. Cookies and analytics

  • Our website doesn't use analytics, advertising pixels or tracking cookies. If we add analytics in future, we'll update this policy first.
  • Our website loads fonts from Google Fonts, so your browser connects to Google's servers, which receive your IP address and browser information.
  • Cloudflare, our hosting provider, processes technical request data to deliver and secure the site.
  • The AI receptionist owner app and the browser demo use strictly necessary cookies to keep you signed in (owner app, up to 30 days) or to link you to your demo call (up to 1 hour). They aren't used for tracking.
  • Checkout and the "manage my plan" portal are hosted by Stripe, and Stripe's own privacy policy and cookies apply there.
  • Our Facebook link is a plain link. We don't use Facebook tracking on our website.

13. Access and correction

You can ask for a copy of the personal information we hold about you, or ask us to correct it, by emailing osbornedigitals@gmail.com. We'll check who you are, then respond within 30 days. We don't charge for requests. If we can't give you access or make a correction, we'll explain why. If you've called one of our clients' AI receptionists, see section 5.

14. Complaints

If you have a concern about how we've handled your information, email osbornedigitals@gmail.com with the details. We'll look into it and reply within 30 days. If you're not happy with our response, you can contact the Office of the Australian Information Commissioner (OAIC) at www.oaic.gov.au.

15. Changes to this policy

We may update this policy when our services or providers change. The latest version is always on this page, with the date it was last updated. If a change significantly affects how we use clients' information, we'll let clients know by email.

16. Switch services

If you use Studio Switch or Review Switch, we also handle information as part of that work, on your behalf:

  • contracts, order forms and similar documents you give us from your current provider (for example Trustpilot, Mindbody or Glofox), so we can find notice dates, renewal dates and any steps the provider requires;
  • customer or member contact lists you give us, so we can send review-request emails or texts, or a member card re-save campaign, on your behalf;
  • wording and records for those messages, and a dated copy of any notice we send with your go-ahead.

Those messages are sent for you, not as marketing for Osborne Digitals. We don't use your customer or member lists to market our own services. You are responsible for having the right to contact the people on the list you give us.

If a Switch service includes analytics on your own website (for example Google Analytics on a Studio Switch site), that analytics runs on your site and is your choice. It is separate from osbornedigitals.com.au, which does not use analytics (see section 12).

17. Contact us

Tyson Osborne, Osborne Digitals
Australia
ABN 26 384 573 254
Email: osbornedigitals@gmail.com

See also our terms and our AI plan terms.