At a glance
- We collect your business name, phone number, and email when you enquire about our service.
- We use your information only to provide our AI receptionist service.
- We do not sell, rent, or trade your personal information.
- Marketing website data (enquiries, waitlist sign-ups) is processed on Vercel edge infrastructure in the United States.
- If you become a customer, the main voice pipeline for your calls — telephony, AI, recordings and transcripts — runs on Sydney infrastructure. It is not exclusively onshore: where an alternative voice provider or an overseas sub-processor handles part of a call, that content is processed overseas under Australian Privacy Principle 8 safeguards. Section 7 sets out exactly which layer runs where.
- You can request access to, correction of, or deletion of your data at any time.
- This policy covers both this marketing website and the Smoko Android app (Google Play package
au.com.localvoiceai.smoko), our AI receptionist app for tradies. - The Smoko app records and transcribes business calls answered by the AI — see the Smoko app data sections below.
Who We Are
LOCALVOICEAI PTY LTD (ABN 64 692 275 997; ACN 692 275 997) trades as Local Voice AI and is based in Sydney, New South Wales, Australia.
This policy covers both this marketing website and the Smoko Android app (Google Play package au.com.localvoiceai.smoko), our AI receptionist app for tradies.
If you have questions about this privacy policy or how we handle your personal information, you can contact us at hello@localvoiceai.com.au.
Information We Collect
We collect the following types of personal information:
Lead form data: When you fill out an enquiry form on our website, we collect your business name, phone number, email address, and business type. This information is stored in our PostgreSQL database.
Waitlist data: When you join our waitlist, we collect your email address.
Technical data: Our web servers automatically record standard log information, including your browser type, IP address, and pages visited. This is collected through normal website operation.
Through this marketing website, we do not collect sensitive information such as health data, religious beliefs, or political opinions, and we collect only organisation-level and business contact details. The Smoko Android app handles additional personal information — including recordings of individual callers — as described in the app sections below.
How We Collect Information
We collect information in two ways:
- Directly from you: When you fill out a form on our website, such as the lead enquiry form or waitlist sign-up.
- Automatically: Standard web server logs record your IP address, browser type, and pages visited when you use our website.
We do not collect information about you from third parties.
How We Use Your Information
We use your personal information to:
- Respond to your enquiry about our AI receptionist service
- Set up your account if you sign up for the service
- Send you information about the service you enquired about
- Improve our website and service
We do not use your information for automated decision-making or profiling.
Smoko mobile app
The Smoko Android app (Google Play package au.com.localvoiceai.smoko), published by Local Voice AI Pty Ltd, is an AI phone receptionist for tradespeople. This section describes the personal information the app collects and how it is handled, in addition to the website practices described above.
Information the Smoko app collects
The Smoko app collects the following information:
- Account and identity data — your name, email address, business name, and phone number. If you choose Google Sign-In, we receive your Google account name and email through Firebase Authentication / Android Credential Manager.
- Business call recordings and transcripts — calls to your business number that the AI receptionist answers are recorded, and we generate transcripts. We store the call audio, transcripts, AI-generated call summaries, and call detail records (CDRs).
- In-app call audio (microphone) — when you take over a live call inside the app, Smoko uses your device microphone to carry that call. Audio is used only for the live call.
- Product analytics — app usage events (screens viewed, features used) collected to help us improve the app.
- Push notification tokens — Firebase Cloud Messaging (FCM) push tokens and VoIP push tokens, used to notify you of incoming calls and account events.
- Subscription and billing status — Smoko subscriptions are purchased through Google Play Billing (in AUD). Google processes your payment; we receive your subscription and purchase status, not your card details.
- Device permissions — the app requests microphone, notifications, and phone / foreground-service (
phoneCalltype) permissions, plus full-screen intents, to run the in-app calling experience and show incoming-call screens.
How the Smoko app uses this information
We use the information the Smoko app collects to:
- Provide and operate the AI receptionist that answers your business calls.
- Record, transcribe, and summarise calls so you can review them in the app.
- Notify you of incoming calls and account activity via push notifications.
- Let you take over and handle live calls from your device.
- Manage your subscription and provide customer support.
- Understand feature usage (analytics) to improve the app. We do not use your information for automated decision-making that has legal or similarly significant effects, and we do not sell it.
Call recording and transcription
Business calls answered by the Smoko AI receptionist are recorded and transcribed so the AI can understand the caller, respond, and give you a summary. Callers are told at the start of the call that the call is recorded and that they are speaking with an AI assistant.
As the operator of the business number, you are responsible for meeting any additional call-recording notification or consent obligations that apply in your state or territory.
Third parties that process Smoko app data
We use the following third parties to process Smoko app data:
- Telnyx — telephony provider that routes and records the business calls.
- Anthropic (Claude) — AI language processing of call content so the receptionist can understand callers and respond.
- PostHog — product analytics.
- Google — Firebase Authentication and Firebase Cloud Messaging — sign-in and push notifications.
- Google Play Billing — subscription payment processing.
- Fly.io (Sydney region) — application hosting and the Postgres database, located in Australia, with row-level security controls.
Smoko app account data and call recordings are hosted in Australia (Fly.io, Sydney). Some processors above (for example AI language processing and analytics) may process data outside Australia; where they do, we take reasonable steps under Australian Privacy Principle 8 to ensure comparable protection. A full, current list of sub-processors and their locations is available on request at hello@localvoiceai.com.au.
Google user data (Google Calendar)
If you choose to connect your Google Calendar to Smoko, we access Google user data through Google's APIs with your explicit consent, granted on Google's OAuth consent screen. You can use Smoko fully without connecting Google Calendar.
What we access: with the permissions you grant, we access your calendar's free/busy availability and create, update, or delete the calendar events that represent bookings made through Smoko. If you use Google Sign-In, we also receive your Google account name, email address, and profile picture.
How we use it: Google Calendar data is used for one purpose only — keeping your Smoko booking diary and your Google Calendar in sync, so jobs booked by your AI receptionist appear in your calendar and your availability is respected. We do not use Google user data for advertising, profiling, or any purpose beyond these user-facing features.
What we share: we do not sell, rent, or transfer Google user data to third parties. Google Calendar data is processed and stored on our own infrastructure (Fly.io, Sydney) and is not disclosed to any other party, except where required by law.
AI and Google user data: we never read the content of your calendar events — Smoko reads only your free/busy times, and uses its write permission to add or remove booking events. When your calendar is connected, the appointment slot times derived from your free/busy information are processed by the AI service that powers your receptionist (Anthropic) solely to offer callers appointment times — a core user-facing feature. Google user data is never used by us or by our service providers to develop, improve, or train AI or machine-learning models: Anthropic's commercial API terms prohibit training on this data. The use of raw or derived user data received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Protection: Google user data is protected in transit with TLS and at rest with encryption on infrastructure in Sydney, Australia, with row-level security controls limiting each account to its own data. OAuth tokens are stored encrypted and are never exposed to other users or third parties.
Retention and deletion: we keep Google Calendar access only while your calendar remains connected. You can disconnect Google Calendar at any time from Smoko's settings, or revoke Smoko's access at myaccount.google.com/permissions; on disconnection we delete the stored tokens. A verified Smoko account-deletion request includes stored Google user data under our control. You should also revoke Smoko's Google access directly using the permissions link above.
How long we keep Smoko app data
We keep your account data for as long as your account is active. A verified deletion request covers call recordings, transcripts, summaries, and CDRs in active Smoko product systems. Deletion is not treated as complete until storage cleanup is reconciled. Limited records may remain where law or a disclosed service-provider retention requirement applies.
Deleting your Smoko account and data
You can request deletion of your Smoko account and associated data from within the app or by email. Account deletion does not by itself cancel an active subscription. Full cancellation steps, deletion instructions, and completion limitations are on our Delete Your Account page. To request deletion by email, contact hello@localvoiceai.com.au.
Cross-Border Data Disclosure
We use a split hosting architecture so that the most sensitive data stays in Australia. Different layers of our platform are hosted in different locations:
- Marketing website (this site): Hosted on Vercel's edge network, which may process requests in the United States. Lead enquiry and waitlist form submissions may be transferred to and temporarily stored on Vercel infrastructure outside Australia.
- Voice telephony, AI processing, and call recordings: Our primary AI receptionist pipeline is hosted and processed within Sydney, Australia — telephony, speech recognition, language model inference, speech synthesis, and the storage of call recordings, transcripts, and usage logs all run on Sydney infrastructure. Where an alternative voice provider or overseas processor is used (see the app sections above), call content may be processed outside Australia under the safeguards described below.
- Product application backends: Hosted on Fly.io. Customer account data, including PostgreSQL databases, is held on Fly.io infrastructure. Fly.io may operate across multiple regions; we select Australian regions where available.
In line with Australian Privacy Principle 8, we take reasonable steps to ensure that any overseas recipient of your personal information protects it in accordance with the Australian Privacy Principles. Our hosting providers, including Vercel and Fly.io, each maintain industry-standard security practices including encryption in transit and at rest. The Australian voice infrastructure that powers our AI receptionist service is SOC 2 Type II certified.
Data that leaves Australia includes: information you submit via enquiry or waitlist forms on this website (with standard web server logs), product analytics events, and — where an alternative voice provider is used — call content processed by overseas AI processors. Call recordings, transcripts, and account data for our primary pipeline are stored in Sydney, Australia.
A current list of the specific sub-processors we rely on, including the Australian voice infrastructure provider, is available on request. Please email hello@localvoiceai.com.au to receive the latest register.
Accessing, Correcting, or Deleting Your Information
You have the right to request access to, correction of, or deletion of your personal information that we hold.
To make a request:
- Email us at hello@localvoiceai.com.au with details of your request.
- We will verify your identity before processing your request.
- We will respond within 30 days of receiving your request.
Access to and correction of your personal information is provided free of charge.
Data Security
We take reasonable steps to protect your personal information from misuse, interference, loss, and unauthorised access, modification, or disclosure. Our security measures include:
- HTTPS encryption on all pages
- Database access restricted to authorised personnel
- Regular review of our data handling practices
No method of electronic transmission or storage is completely secure. While we strive to protect your personal information, we cannot guarantee absolute security.
We Don't Sell Your Data
We do not sell, rent, or trade your personal information to third parties.
We do not share your information with third parties for their marketing purposes.
Complaints
If you believe we have breached the Australian Privacy Principles, you can lodge a complaint with us by emailing hello@localvoiceai.com.au.
We will investigate your complaint and respond within 30 days.
If you are not satisfied with our response, you may lodge a complaint with the Office of the Australian Information Commissioner (OAIC):
- Website: oaic.gov.au/privacy/privacy-complaints
- Phone: 1300 363 992
Changes to This Policy
We may update this privacy policy from time to time to reflect changes in our practices or for legal, operational, or regulatory reasons.
When we make material changes, we will update the date at the top of this page. We encourage you to review this page periodically.