Privacy Policy
This Privacy Policy is published at https://freshtechcommunity.com/privacy-policy and is free to read, always available, and does not require you to log in or pay. It is the same policy linked from our homepage, our Google sign-in / consent screen, the in-app Settings, and (when our mobile apps launch) the Apple App Store and Google Play store listings. This is the single, canonical Alice privacy policy; it is not a supplement to, and does not defer to, any separate FreshTech policy.
1. Who we are
Alice (also called "Alice Booking Diary") is an AI receptionist and booking assistant for trades and small businesses. Alice answers inbound phone calls with an AI voice, runs a website chat widget, qualifies enquiries, and books jobs into the business owner's diary.
Alice is provided by FreshTech-Community Pty Ltd — a proprietary company registered in Victoria, Australia — ACN 699 190 513. We operate the public-facing brands "FreshTech Community", "Alice", and "Alice Booking Diary". (FreshTech Community was previously operated by Tien Thanh Tran as a sole trader; the business was incorporated as FreshTech-Community Pty Ltd on 18 June 2026, which is now the provider and data controller. This is the change of controller anticipated in our earlier policy — your rights, and the way we handle your information, are unchanged.)
In this policy, "we", "us", "our", "FreshTech" and "FreshTech Community" mean FreshTech-Community Pty Ltd (ACN 699 190 513). "You" means the person reading this — most often a business owner who uses Alice, or a customer of one of those businesses whose details pass through Alice.
We handle personal information in line with the Australian Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). Where the law of another place applies to you (for example, the EU/UK GDPR or California's CCPA/CPRA), the relevant section below also applies.
Our two roles. Alice is used by business owners, and their customers' personal information flows through Alice:
- For a business owner's own account information (your name, login, business profile, billing), FreshTech is the data controller — we decide how that information is handled.
- For an owner's end-customers' personal information (the people who call, chat, or get booked in — including call recordings and transcripts), FreshTech acts as a data processor / service provider on the owner's behalf and instructions. The business owner is the controller of that customer information. If you are a customer of a business that uses Alice and you want to access, correct, or delete your details, your first point of contact is that business; we will assist the business to action your request (see Section 13).
Privacy contact
- Email (general support): info@freshtech.community
- Privacy enquiries and data-rights requests: info@freshtech.community
- Postal address for service of legal documents and formal privacy notices: FreshTech-Community Pty Ltd, Unit 323, 4 Acacia Place, Abbotsford VIC 3067, Australia.
2. The personal information we collect
We only collect what Alice needs to do its job. Below is every category of personal information Alice handles — we do not collect data for undisclosed purposes.
A. Information about a business's customers (end-customers) — supplied by the owner or captured by Alice when it answers a call or chat:
- Name of the customer.
- Phone number.
- Email address.
- Postal / job address (where the work is to be done).
- Job and booking details — what the customer wants done, notes, quotes or prices discussed, preferred times, and the booking history for that customer.
B. Call audio recordings and call transcripts (a distinct, sensitive category we call out separately) — when a customer calls a business's Alice voice line, Alice may record the call audio and create a written transcript of the conversation. These recordings and transcripts can contain anything the caller says (name, contact details, address, the nature of the job, and any other personal information they choose to share). Because this is voice and conversation data, we treat it with particular care (see Sections 5 and 6).
C. Business owner account information:
- Account details: name, email address, sign-in method and authentication status.
- Business profile: business name, website, phone number(s), location, staff/roster, services, opening hours, and the instructions you give Alice about how to handle bookings.
- Subscription and billing status (your plan, whether payment succeeded). See the card-payment note below.
D. Google Calendar data (only if you connect your Google Calendar):
- Your calendar's busy / free times and calendar event data, which Alice reads so it never books a customer on top of something you already have on.
- The Google OAuth access token and refresh token that let Alice connect to your calendar on your behalf.
- See the dedicated Google Calendar / Limited Use section (Section 10).
E. Google Search Console data (only if you separately connect it): verified website properties; clicks, impressions, click-through rate and average position for the property you choose; and the OAuth tokens needed to read that report. See Section 10.
F. Technical and usage information needed to run the app, keep it secure, prevent abuse, and debug errors (for example, log and device/connection information).
We do not store card numbers
Card and bank payments are processed by Stripe. When Alice creates or sends a payment request, the customer enters their card details directly with Stripe. FreshTech does not see, collect, or store full card numbers. Stripe handles card data under its own terms and security standards.
We also do not intentionally collect sensitive information beyond what is described above. Please don't volunteer health, biometric, or other sensitive information to Alice unless it's genuinely needed for the booking.
3. How we collect your information
We collect personal information in these ways, and this section also serves as our APP 5 collection notice (the things we must tell you at or before we collect your information):
- Directly from the business owner, when you create an account, set up your business profile, connect a calendar or other service, and tell Alice how to handle your bookings.
- From the owner about their end-customers. Owners may enter, import, or instruct Alice to capture a customer's details. So in many cases we collect an end-customer's personal information from a third party (the business owner), not from the customer directly. This happens because the owner is using Alice to run their booking diary and asked us to handle that information on their behalf.
- From the customer during a call or chat, when Alice answers an inbound phone call or website chat — including, for phone calls, the call audio recording and transcript (see the call-recording announcement in Section 6).
- From services you connect — for example, your Google Calendar busy/free times when you connect Google (Section 10), and (once the Social feature ships) Facebook/Instagram information if you connect Meta (Section 17).
- Automatically, basic technical/log information when you use the app.
What we must tell you at collection (APP 5): our identity and contact details are in Section 1; the purposes of collection are in Sections 4–6; the parties we usually disclose information to are in Sections 8–10; the fact that your information is likely to be disclosed to recipients overseas (and which countries) is in Section 9; and the main consequence if information is not provided is that Alice may not be able to take or complete a booking, answer the call properly, or run the relevant feature. This policy also explains how you can access and correct your information and how to complain (Sections 13–14).
4. How we use your information, and why
We use personal information only for the purposes described in this policy. We do not use it for undisclosed secondary purposes.
| What we use | Why we use it (purpose) |
|---|---|
| Account + business profile | To create and secure your account, run the app, and support you. |
| Customer name, phone, email, address, job/booking details | To answer enquiries, qualify the job, prepare and (where you've enabled it) make bookings, contact the customer about their booking, and keep your booking history. |
| Call recordings + transcripts | To handle the call, capture booking details accurately, let the owner review what was said, and improve reliability and quality (Section 6). |
| Google Calendar busy/free + events | So Alice doesn't double-book you, and to add/update the bookings Alice itself makes (Section 10). |
| Google Search Console performance | To show you your connected website's search performance and guide your own AI Search workflow (Section 10). |
| Conversation + booking data sent to our AI "brain" | So Alice can understand the caller/chatter and respond (see the AI note below). |
| SMS sending (Twilio) | To send booking confirmations and, where the owner has set them up, permitted messages to customers. |
| Payment requests (Stripe) | To create and send invoices/payment links at the owner's direction. |
| Technical/log data | To keep the service secure, prevent abuse, and fix faults. |
Our AI "brain" and third-party AI
Alice's voice and chat responses are generated by artificial intelligence. To do this, conversation content and relevant booking data are sent to OpenAI, whose large-language-model API (by default, the gpt-5 model) powers Alice's "brain". This is a core part of how Alice works.
- We obtain your permission before personal data is shared with this third-party AI as part of normal use (for owners, when you set up and use Alice; for callers and chatters, via the in-call recording/AI disclosure described in Section 6 and the chat notice).
- OpenAI processes this data to generate Alice's responses for your account. OpenAI does not use data submitted to it through its API to train or improve its models, under OpenAI's standard API data-usage policy. In addition, FreshTech does not use your data — and never your connected Google data — to train, fine-tune, or improve any AI or machine-learning model beyond serving your own account.
- Google Calendar and Google Search Console data are never sent to the AI provider, and are never used to train, fine-tune, or improve any AI model (see Section 10).
We do not sell your personal information, and we do not use it for third-party advertising.
5. Limiting use and disclosure (APP 6)
We use and disclose end-customer personal information for the primary purpose we collected it (running the booking) and for closely related purposes you would reasonably expect — and not for unrelated purposes without a lawful basis or your consent. In particular:
- We do not sell, rent, or trade personal information.
- We do not use Alice's data to build advertising or behavioural profiles.
- We do not repurpose collected personal information (for example, to train our AI "brain" on it) beyond serving your own account, without a lawful basis.
6. Call recording and transcription
Alice records and transcribes inbound phone calls to a business's Alice voice line. This section explains how that works and your rights.
A spoken announcement at the start of the call. Alice announces at the start of every inbound call that the call is recorded for training and quality purposes. Because Alice answers callers anywhere in Australia, and because New South Wales, Western Australia, South Australia, Tasmania and the ACT require the consent of all parties to record a private conversation (one-party consent in VIC/QLD/NT is not enough for callers from those states), the recording is disclosed up front: if you continue with the call after the announcement, that establishes your consent to the recording. If you do not consent, you can hang up and contact the business another way. Recording is of a call answered by Alice — we do not intercept calls in transit, consistent with the Telecommunications (Interception and Access) Act 1979 (Cth).
How Alice identifies herself. Alice introduces herself by name. She does not open by announcing that she is software, in the same way a human receptionist does not open by announcing that they are human. But Alice never claims to be a person and never denies being AI. If you directly ask whether you are speaking to a real person, a human, an AI, a robot, an automated system or a recording, Alice tells you plainly, in her first sentence, that she is the AI receptionist for that business — and then keeps helping. This behaviour is built into Alice's voice and chat instructions, not left to chance.
Purpose. We use recordings and transcripts to handle and complete the call, capture booking details accurately, let the business owner review what was discussed, resolve disputes, and improve reliability and quality.
Who can access them. The relevant business owner (and their authorised staff) can access the recordings/transcripts for their own customers. Our service providers (telephony, speech-to-text, hosting, and the AI brain — see Section 8) process them only to deliver the feature. FreshTech staff access them only where necessary for support, security, legal compliance, or to fix faults.
Retention. Call audio recordings and transcripts are kept while the owner's account is active, and are deleted on account closure (within approximately 30 days of closure), except where we must keep specific records longer to comply with the law (see Section 12). Transcript retention is also controlled by the business owner in Alice's Settings, and an owner can request earlier deletion of specific customer records. See Section 12.
7. Automated decision-making and AI (transparency)
Alice is an automated system, so we explain here how it makes or contributes to decisions. (Australia's Privacy Act will require this kind of transparency from 10 December 2026 under the Privacy and Other Legislation Amendment Act 2024 / new APP 1.7–1.9. We include it now as a matter of good practice.)
- The kinds of personal information Alice's automated programs use: caller/chatter name and contact details, the job/enquiry details, conversation content (including call recordings/transcripts), the owner's services/pricing/opening hours, and the owner's calendar busy/free times.
- Decisions Alice may make on its own (automatically): understanding and responding to a caller or chatter; qualifying an enquiry (e.g. whether the job is something the business does); proposing available appointment times; and, where the owner has switched on automatic booking, creating or confirming a booking in a free slot.
- Decisions Alice substantially and directly contributes to (a human then relies on): which leads the owner sees and follows up; the times offered to a customer; and the draft bookings, prices, and messages the owner reviews and confirms.
Alice can make mistakes (for example, mishearing a name or time). The business owner remains responsible for reviewing and confirming bookings, availability, prices, and customer communications before relying on them (this responsibility is set out as an enforceable term in our Terms of Service). If a decision made or supported by Alice affects you and you want it reviewed by a person, you can ask for human review: contact the business, or contact us using the details in Section 1, and a person will review the decision.
8. Who we share your information with (our service providers / sub-processors)
To run Alice, we use trusted service providers ("sub-processors"). They process your data only to deliver the Alice features you see, under confidentiality obligations, and never for their own advertising. Using them to run the service is not a sale of your data.
| Provider | What they do for Alice |
|---|---|
| Cloudflare | Hosting, app delivery, serverless Workers, and our KV + D1 databases (where booking and account data are stored). |
| Supabase | Account authentication (sign-in / login). |
| Vapi | Voice telephony — connecting and handling the AI phone calls. |
| ElevenLabs | Text-to-speech and speech-to-text (Alice's voice and call transcription). |
| Deepgram | Speech-to-text transcription for calls. |
| OpenAI | Powers Alice's AI "brain" — generates Alice's voice and chat responses from conversation and booking data (by default the gpt-5 model). Does not train its models on data submitted via its API. |
| Stripe | Payment processing (invoices and payment links). Stripe handles card data directly. |
| Twilio | Sending SMS (e.g. booking confirmations). |
| Resend | Transactional email delivery (account, booking and notification emails). |
| Payment provider (subscription billing) | Takes your subscription payment and keeps the billing record. Card details are entered with the provider — FreshTech never sees or stores your full card number. Where the provider acts as merchant of record it is also the seller for that purchase and issues your tax invoice. The current provider is shown at checkout and on your receipt. |
| Google Calendar API and, if separately connected, the read-only Google Search Console API. See Section 10. |
When our mobile apps launch, this list will be kept consistent with our Google Play Data safety form and our Apple App Privacy label. We will update this policy if our service providers change.
We may also disclose personal information where we are required or permitted by law, to protect our or others' rights and safety, to prevent fraud, or in connection with a sale or restructure of our business (and, for Google-derived data, only with your explicit consent as required by Google's policy).
9. Sending information overseas (cross-border disclosure)
Your personal information is likely to be disclosed to recipients located outside Australia. Several of our service providers store and process data overseas — predominantly in the United States (where, depending on the provider and its configuration, Cloudflare, Stripe, Twilio, Vapi, ElevenLabs, Deepgram, OpenAI, Resend, and Google may host or process data), and possibly other countries where those providers operate.
Before disclosing personal information overseas, we take reasonable steps to ensure the overseas recipient handles it consistently with the Australian Privacy Principles — for example, through data-processing terms with our providers that require appropriate protection. No data transfer can be guaranteed perfectly secure.
For individuals protected by the GDPR (EU/UK): where we transfer your personal data outside the EEA/UK, we rely on an appropriate safeguard such as the European Commission / UK Standard Contractual Clauses or an adequacy decision. You can request a copy or further detail using the contact in Section 1.
10. Connected Google data and Google API "Limited Use"
This section applies only if you connect Google Calendar or separately connect Google Search Console to Alice.
Alice'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.
What Google data we access:
- Your Google Calendar events / busy-free times.
- Your verified Search Console properties and the selected property's clicks, impressions, click-through rate and average position.
- The OAuth access token and refresh token that let Alice connect on your behalf.
Why (purpose): Alice reads your busy times so it never double-books you, and writes or updates only the bookings Alice itself makes on your behalf. Google Calendar data is used by Alice's booking code for availability — it is not fed into the AI/LLM brain.
The exact permission (scope) we request: https://www.googleapis.com/auth/calendar.events.
Why we need this scope and not a read-only one. Alice does two things with your calendar: (1) reads your busy/free times so it won't book over an existing commitment, and (2) writes the confirmed bookings Alice makes back into your calendar so your diary stays in one place. A read-only scope (such as calendar.events.readonly or freebusy) would let Alice see your busy times but not write the bookings it creates, which is core to the product — so the read-write calendar.events scope is the minimum scope Alice needs. Alice does not request broader Google scopes than the feature requires.
Google Search Console. If you connect it, Alice requests the read-only https://www.googleapis.com/auth/webmasters.readonly scope. Alice lists the verified website properties available to your Google account, lets you choose one, and reads its clicks, impressions, click-through rate and average position for the latest 28 complete days. Alice cannot change your Search Console property or Google account.
Search Console purpose and storage. This data is used only to show you your own search performance and guide your own Alice AI Search workflow. The selected property and a report cache are stored per business; the report is refreshed no more than every six hours unless you ask for a refresh. It is not used for advertising, sold, or sent to an AI/LLM provider.
How we store it. Your Google busy/free times are cached transiently in Cloudflare KV with an approximately 60-minute time-to-live, after which the cache expires. Your access/refresh tokens are stored securely so Alice can keep your calendar in sync.
A clear notice before you connect. When you go to connect Google Calendar inside Alice ("Connect Google Calendar" / Cal-Sync), we show you what Alice will access (your calendar busy/free times) and why (so it won't double-book you), and we ask for this access in context at the point you connect — not bundled into sign-up — so you reach Google's consent screen already knowing what is being requested.
What we will never do with Google data. Consistent with Google's Limited Use requirements, we do not: use connected Google data for advertising or retargeting; sell, rent, or transfer it to third parties; use it to develop, train, fine-tune, or improve any AI or machine-learning model; or allow anyone to read it except where you've given consent, for security, to comply with law, or in limited aggregated/operational cases permitted by Google's policy.
Disconnecting and deletion. You can disconnect either Google feature in Alice, or remove Alice at https://myaccount.google.com/permissions. Calendar disconnect deletes its token and busy/free cache. Search Console disconnect deletes its token, selected property and report cache. Alice then stops accessing that Google service. All stored Google data is deleted on account closure (Section 12).
11. How we keep your information secure
We use reasonable technical and organisational measures appropriate to the product to protect personal information:
- Personal and sensitive data is transmitted using modern encryption (HTTPS/TLS) in transit.
- Data is stored with our infrastructure providers (Cloudflare KV/D1, Supabase) under their security controls.
- Access controls limit who can reach customer data — owners see their own workspace; FreshTech staff access only where necessary for support, security, or fault-fixing.
- We work with reputable sub-processors (Section 8) that maintain their own security standards.
No internet service can be guaranteed perfectly secure. If a data breach occurs that is likely to cause serious harm, we will respond in line with the Notifiable Data Breaches scheme under the Privacy Act and notify affected individuals and the OAIC where required.
12. How long we keep your information, and deletion
We keep personal information only for as long as we need it for the purposes in this policy, then delete or de-identify it. As a single, consistent rule: call recordings, transcripts, and customer/booking data are kept while the owner's account is active and deleted on account closure (within approximately 30 days), except transaction and financial records, which we keep for approximately 7 years to comply with Australian tax-record law. An owner can request earlier deletion of specific customer records.
| Information | How long we keep it |
|---|---|
| Account + business profile | While your account is active; deleted within ~30 days of account closure. |
| Booking details + booking history | While your account is active; deleted within ~30 days of account closure, except transaction/financial records kept ~7 years for Australian tax-record law. |
| Call audio recordings + transcripts | While your account is active; deleted within ~30 days of account closure (transcript retention is also owner-configurable in Settings; owner can request earlier deletion of specific records). |
| Google Calendar busy/free cache | Transient (≈60-minute expiry); purged immediately on disconnect, and on closure (Section 10). |
| Google Search Console property + report cache | While connected; purged immediately on Search Console disconnect, and on closure (Section 10). |
| Google access/refresh tokens | Until you disconnect Google or close your account (deleted immediately on disconnect). |
| Transaction / financial records (invoices, payment records) | Approximately 7 years, to comply with Australian tax-record law. |
| Technical/log data | A limited period for security and debugging. |
On account closure / deletion we delete the personal information associated with your account that we hold in our own systems (our Cloudflare KV and D1 storage), except a defined, limited set we may keep where we are required to by law (in particular transaction/financial records kept ~7 years for tax purposes), or to prevent fraud, or to resolve disputes or enforce our agreements — and only for as long as necessary. Any such retained data continues to be protected under this policy.
Data held by our voice/SMS providers. Some call recordings, transcripts and SMS records are also held by our service providers (for example Vapi, ElevenLabs, Deepgram and Twilio). These provider-held copies are deleted on each provider's own retention cycle.
13. Your privacy rights and how to use them
Subject to the role split in Section 1 (we are the processor of end-customer data on the owner's behalf), you have the following rights.
Access and correction. You can ask us for access to the personal information we hold about you, and to correct it if it's wrong. Owners can update much of their business profile directly in the app. To make a request, contact us at info@freshtech.community (Section 1); we aim to respond within 30 days.
Deleting your account and data. You can delete your Alice account and the associated personal information we hold in any of these ways: (a) in the app, at Settings → Account → Delete business; (b) on our public web page at https://alicefamily.app/delete-account (no login required); or (c) by emailing info@freshtech.community. For your security, in-app and web deletion are confirmed with a one-time code sent to your account email. On deletion we purge the personal data we hold in our own systems (Cloudflare KV and D1) and revoke any connected Google access, subject only to the limited legal/fraud/dispute retention described in Section 12 (and the provider-held-data position there). You can also delete or edit individual customer records inside the app.
Withdrawing consent and disconnecting services. You can withdraw consent to optional processing at any time — for example, by disconnecting Google Calendar or Google Search Console (Section 10), or, once the Social feature ships, disconnecting Facebook/Instagram (Section 17). Withdrawing consent doesn't affect processing already carried out.
If you are an end-customer of a business that uses Alice: the business is the controller of your details. Please direct access, correction, or deletion requests to that business in the first instance; we will help the business action your request, and you may also contact us.
14. How to make a privacy complaint
If you think we have mishandled your personal information:
- Contact us first at info@freshtech.community (the privacy contact in Section 1). Tell us what happened and what you'd like us to do.
- We will investigate and aim to respond within a reasonable time (generally within 30 days), explaining our findings and any steps we'll take.
- If you're not satisfied, you can escalate to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au or 1300 363 992.
- GDPR users may also lodge a complaint with their local data-protection supervisory authority.
15. Additional rights for EU / UK individuals (GDPR)
This section applies if and to the extent the EU or UK GDPR applies to you.
- Controller: FreshTech-Community Pty Ltd (ACN 699 190 513) (Section 1).
- Lawful bases. We rely on: contract (to provide Alice to owners); consent (e.g. connecting Google Calendar, AI call recording, optional messaging); legitimate interests (running, securing, and improving the service, and — for end-customer data — the owner's legitimate interest in operating its bookings), balanced against your rights; and legal obligation where applicable.
- Recipients: the service providers in Section 8.
- International transfers: see Section 9 (SCCs/adequacy; copy available on request).
- Retention: see Section 12.
- Your rights: access, rectification, erasure, restriction, data portability, objection, and the right to withdraw consent at any time.
- Automated decision-making: see Section 7 for the logic involved, its significance, and your right to request human review.
- Source of data (Art 14): where we did not collect your data from you directly, we obtained it from the business owner using Alice (and, for calls/chats, from the conversation).
- Providing data: giving us certain information is necessary to use Alice or to be booked in; if it isn't provided, we may be unable to deliver the relevant feature.
- Complaints: you can complain to your local supervisory authority (Section 14).
16. Additional rights for California residents (CCPA/CPRA)
This section applies if and to the extent the California Consumer Privacy Act (as amended by the CPRA) applies.
- Categories of personal information we collect, the sources, and the business/commercial purposes are described in Sections 2–4. This serves as our notice at collection.
- We do not "sell" or "share" your personal information as those terms are defined under the CCPA/CPRA, and we do not use sensitive personal information for purposes that would trigger the right to limit. Because we do not sell or share, no "Do Not Sell or Share My Personal Information" link is required, and we honour browser Global Privacy Control (GPC) signals as opt-out requests.
- Your rights: to know/access, delete, correct, opt out of any sale/sharing, limit the use of sensitive personal information, and to non-discrimination for exercising your rights.
- Categories of third parties we disclose to for business purposes are the service providers in Section 8.
- Retention is described in Section 12.
- How to exercise: contact us at info@freshtech.community (Section 1); we will verify and respond as the CCPA requires.
17. Facebook / Instagram ("Social" feature)
This section applies once the Social feature (Meta / Facebook / Instagram integration) launches; until then it is forward-looking. If you connect Facebook or Instagram to Alice, we will:
- Collect the Meta information needed for the feature — for example your name, email, app-scoped ID, and any Page/Instagram data you authorise — and use it only as described in this policy and only with your consent.
- Use any messaging data (if Messenger/Instagram messaging is enabled) only as necessary to support the message types you've chosen, and use any advertising data only on an aggregate/anonymous basis — we do not build profiles from Meta data.
- Let you delete Meta-sourced data. You can disconnect Facebook/Instagram in your Meta settings, and request deletion of the Meta-sourced data we hold by contacting us at info@freshtech.community; when the Social feature launches we will publish a dedicated data-deletion page and reference it here. We will delete that data except where we must keep it by law.
18. Children
Alice is a tool for businesses and is not intended for use by children, and we do not knowingly collect personal information from children. If you believe a child's personal information has been provided to us, contact us (Section 1) and we will delete it.
19. Changes to this policy
We may update this policy from time to time — for example, to reflect new features or legal changes (such as the December 2026 automated-decision-making rules). When we do, we'll update the "Last updated" date at the top and, for material changes, take reasonable steps to let you know. The current version always lives at https://freshtechcommunity.com/privacy-policy.
When our mobile apps launch, our store and platform disclosures — the Google Play Data safety form and the Apple App Privacy label (which will declare "Voice or sound recordings" for Alice's call recordings) — will be kept consistent with this policy and with how Alice actually behaves.
20. Governing law and how to contact us
Governing law. This Privacy Policy and any dispute arising out of or in connection with it are governed by the laws of Victoria, Australia. You and we submit to the non-exclusive jurisdiction of the courts of Victoria, Australia (and the Commonwealth courts that hear appeals from them).
Goods and Services Tax (GST). FreshTech Community is not currently registered for GST. That does not change what you pay: our subscription prices — a permanent free tier, Alice Chat at AUD $49/month, Call Cover at AUD $99/month, and Full Receptionist at AUD $199/month — include GST. Purchases are made through a reseller acting as merchant of record (clause 9.3 of our Terms); that reseller — not FreshTech — calculates, collects and remits the GST on that sale, and its tax invoice shows the amount charged. If we become required to register for GST in the future, GST may then apply to these prices, and we will update our billing disclosures accordingly.
Contact us.
- General support: info@freshtech.community
- Privacy enquiries and data-rights requests: info@freshtech.community
- Post (service of legal documents and formal notices): FreshTech-Community Pty Ltd, Unit 323, 4 Acacia Place, Abbotsford VIC 3067, Australia.
- Provider / controller: FreshTech-Community Pty Ltd, a proprietary company, ACN 699 190 513, Victoria, Australia.
To delete your account and data, see Section 13. To complain, see Section 14.