Privacy Policy Last updated: October 21, 2026 Version 2026-10-21 — read the archived copy of this exact version (/legal/privacy-policy/2026-10-21.txt) Published 21 October 2026. This is a material change, so we are giving at least 30 days’ notice of it: it takes effect on 21 November 2026 for an account that already existed when it appeared on this page, and an account created after that is bound by it from the moment it is created. It is material because it describes a new use of personal information and the services that carry it out. The version it replaces is 2026-10-14, which you can read here (/legal/privacy-policy/2026-10-14.txt). That version gave its own 30 days’ notice and takes effect on 14 November 2026 for an account that already existed when it was published, so an account that existed then may be asked on this website to accept 2026-10-14 from 14 November 2026 and this version from 21 November 2026. Everything 2026-10-14 changed is in this version too, unchanged. What changed in this version. It describes the AI receptionist: an AI assistant that answers a business’s phone calls once the business switches it on. No customer can switch it on before 21 November 2026. Section 1b is new and says what a call collects. Section 2 has one new purpose. Section 2b has a new entry for the AI receptionist — that every call starts with an announcement that the caller is talking to an AI assistant and that the call is transcribed and not recorded, what a call is used for, who keeps what and for how long, and what Twilio’s and OpenAI’s terms allow them to do with it. In section 3a the Twilio entry now covers phone calls, a new entry names the speech services Twilio uses for a call, the OpenAI entry says what it receives from a call, and two sentences after the list of services that are not enabled say what those names mean for a call. Section 3b says where a call is processed, section 5 says when the record of a call is deleted, and section 6 says how a caller can ask about it. The Data Controller section now gives our ABN and says that for the information a business keeps about its own clients, including the people who phone it, we act for the business, as our Data Processing Agreement already says; that agreement has been republished with the same additions. Section 2a, about text messages, is rewritten: it says what we collect when you agree to receive text messages and how we use it, that no mobile information is shared with third parties or affiliates for marketing or promotional purposes, that we send no marketing by text message, and that no text message is sent before United States mobile carriers approve BookIQ.ai’s registration for them; the entry for email and text messages in section 2b, the introduction to section 3a and the Twilio entry say the same. This version also corrects six things the previous version said: the AI features entry in section 2b and the OpenAI entry in section 3a said that audio is recorded, transcribed and sent to OpenAI, and no feature of BookIQ.ai does that; the Twilio entry said that Twilio verifies phone numbers for us, which it does not; and section 1a and the entry for running a business’s bookings in section 2b said that a business can delete a client record from inside BookIQ.ai, but deleting a client on the BookIQ.ai website marks the client inactive and erases nothing, and a business cannot delete a booking request; and section 1a also said that we would act ourselves on a request sent to privacy@bookiq.ai about a child’s information, but we hold that information for the business, so we pass the request to the business, as our Data Processing Agreement says. Our Data Processing Agreement now also says what deleting a client does, on the BookIQ.ai website and in the BookIQ app, and that deleting an account does not erase a business’s client data. Nothing else in this policy has changed. Data Controller BookIQ.ai is operated by PairOx Pty Ltd (ABN 82 154 477 728, registered in Australia), the data controller for the purposes of GDPR (where applicable). Where this policy uses "we", "us", or "BookIQ.ai" it refers to PairOx Pty Ltd. That is our role for the information whose purposes we decide ourselves, such as your account. Where a business keeps information in BookIQ.ai about its own clients — including the people who phone it, if it uses the AI receptionist described in section 2b — we handle that information for the business, on the terms of our Data Processing Agreement (/legal/data-processing-agreement.html), and the business is responsible for having a lawful basis for it. 1. Information We Collect We collect information you provide directly to us, such as your name, email address, phone number, business details, and payment information. We also collect usage data and device information to improve our services. 1a. Children and Young People BookIQ.ai is a tool for running a business, and it is not directed at children. You must be at least 18 to open or use a BookIQ.ai account — clause 1a of our Terms of Service (/terms-of-service.html) says so. We do not knowingly collect personal information directly from a child. We should be plain about the limits of that: we do not ask a visitor their age and we have no way to verify it, so we rely on what an account holder tells us. If you believe a child has given us information directly, email privacy@bookiq.ai and we will delete it. Separately, a business that uses BookIQ.ai can record information about its own clients, and some of those clients are children — a parent books an appointment for a child, and the business records the child’s name, contact details, date of birth or a note about the service. Where that happens the business decides what to record and why, and clause 4a of the Terms of Service requires it to have a lawful basis for putting that information into the service, which for a child normally means the consent of a parent or guardian. We hold it for the business under this policy, and we do not use a client’s information for BookIQ.ai’s own marketing. If you are a parent or guardian and you want a child’s information removed, ask the business directly — it can ask us to erase a client’s information — or email privacy@bookiq.ai and we will pass the request to the business. 1b. Phone Calls Answered for a Business If a business that uses BookIQ.ai switches on the AI receptionist, we answer calls to its BookIQ.ai number for it. When you make such a call we collect the number you are calling from, the number you called, when the call started and how long it lasted, and the words you and the assistant say, as text. We do not record the call. If you book an appointment or leave a message, we also collect what you give us for it — your name, and an email address or a number to call you back on if you choose to give one. Section 2b explains all of it. 2. How We Use Your Information - Provide, maintain, and improve our booking and business management services - Process transactions and send related information - Send technical notices, updates, security alerts, and support messages - Respond to your comments, questions, and customer service requests - Monitor and analyze trends, usage, and activities in connection with our services - Answer phone calls for a business that has switched on the AI receptionist: tell a caller about the business, book an appointment the caller agrees to, or take a message, and tell the business what happened (section 2b) 2a. Text Messages (SMS) BookIQ.ai is operated by PairOx Pty Ltd (ABN 82 154 477 728). This section is about text messages (SMS) sent through BookIQ.ai about appointments: what we collect when you agree to receive them, how we use it, and who it is shared with. No text message is sent through BookIQ.ai before United States mobile carriers have approved BookIQ.ai’s registration for these messages. What we collect. A BookIQ.ai booking form can show a box for agreeing to receive text messages about your appointments. The box is never ticked for you, and you can book without ticking it. If you tick it and submit your booking, we record, with your client record at the business you booked with, that you agreed, the date and time you agreed, and that you agreed on the booking form. A business can also record in its client record that you agreed to receive text messages about your appointments, for example when you told it so yourself; we then record that the business recorded it, and when. How we use it. For text messages, we use that record, and the mobile number in your client record, only to send you messages about your own appointments made through BookIQ.ai — such as booking confirmations, appointment reminders and notices that a booking was changed or cancelled — and to stop them when you opt out. We do not send marketing or promotional messages by text message; the separate box on a booking form for news and offers is for email only. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. We do not share, sell or provide your mobile phone number, or your text-message opt-in data and consent, to any third party or affiliate for marketing or promotional purposes. Text messaging originator opt-in data and consent are excluded from all of the sharing described elsewhere in this policy and will not be shared with any third parties: the record stays with the business you booked with, in its client record and, for a booking made through a booking form, in the booking request, stored for us by Supabase, and to send a message Twilio receives only your mobile number and the message itself (both are listed in section 3a). Opting out and getting help. Reply STOP to any text message to stop them; Twilio, which delivers them, replies once to confirm and blocks further text messages from our number to yours until you reply START. Reply HELP for help, or email support@bookiq.ai. You can also ask us to stop at privacy@bookiq.ai or, if the business you booked with gives you access to its client portal, change your communication preferences there. Message frequency varies with your bookings. Message and data rates may apply. How long we keep it. The record of your agreement is kept with your client record at the business you booked with, for as long as that record exists or until it is deleted on request. When a business deletes a client on the BookIQ.ai website, the client is marked inactive and nothing is erased, as our Data Processing Agreement says. A booking request sent through a booking form also notes whether the box was ticked, and the phone number given; it is kept with the business’s booking requests, even if the client record is deleted, and the business cannot delete it from inside BookIQ.ai. To have either deleted, ask the business, which can ask us to delete it, or email privacy@bookiq.ai, and we will pass the request to the business. Twilio keeps its own record of a STOP until you reply START. When someone phones a business’s BookIQ.ai number, Twilio also receives the calling number, because it carries the call; section 2b says what happens on a call. 2b. Why We Are Allowed To Use It, and How Long We Keep It Sections 1 and 2 say what we collect and what we do with it. This section sets out, purpose by purpose, the legal basis we rely on and how long the information stays. Where we name a basis we mean: contract — we need it to give you the service you asked for; legal obligation — a law requires us to keep or produce it; legitimate interests — we rely on our own interest in running and protecting the service, weighed against yours, and you can object under section 6; and consent — you chose it and can withdraw it at any time. Australian privacy law does not use those labels: under the Australian Privacy Principles we collect only what we reasonably need for the functions described here, and we say below which of them need your consent either way. - Creating and running your account. Uses your name, email address, phone number, password or the sign-in identity you chose, your business details, and the record of which version of these documents you accepted and when. Legal basis: contract — there is no account without it; and legal obligation for the acceptance record itself, which is the evidence of consent we are required to be able to produce. How long: while your account is active, then on the deletion timetable in section 5. - Running a business’s bookings, clients, staff and messages. Uses everything you and your clients put into BookIQ.ai — appointments, client contact details and notes, service, staff and pricing records, and messages in the in-app inbox. Legal basis: contract with the account holder; and, for information about a business’s own client, the basis the business itself relies on, which clause 4a of the Terms of Service requires it to have. How long: for as long as the business keeps the record. Be clear about what that means: nothing deletes a booking, a client record or a message automatically. Deleting a client on the BookIQ.ai website marks the client inactive and erases nothing, and a business cannot delete a booking request from inside BookIQ.ai. A business that wants a client’s information erased asks us, as our Data Processing Agreement says; a client can ask the business, or email privacy@bookiq.ai and we will pass the request to the business. Deleting your own account does not delete the business or its records — section 5 explains that. - Taking and reconciling payments. Uses your billing identity, the amount, currency and status of each payment, and the payment-method details Stripe returns to us (such as the card brand and last four digits). We never receive or store your full card number: Stripe collects it directly. Legal basis: contract, and legal obligation for the tax and accounting records. How long: 7 years for financial records, as section 5 says. Nothing deletes those, and an account deletion does not. - Sending email and SMS about a booking or an account. Uses your email address and mobile number, the content of the message and whether it was delivered. This covers booking confirmations, reminders, receipts, security alerts and support replies by email, and the text messages about appointments that section 2a describes. Legal basis: contract — those messages are part of the service you asked for, and for text messages we also rely on your agreement to receive them (section 2a); and consent for anything we describe as marketing, which is asked for separately and is never sent by text message. How long: the delivery record is kept with the message it relates to. You can stop text messages at any time by replying STOP (section 2a). - Push notifications to the BookIQ mobile app. Uses the push token your device issues and the content of the notification. Legal basis: consent — your phone asks you before we can send any, and turning notifications off withdraws it. How long: until you turn notifications off, sign out on that device, or your account is deleted, at which point the device tokens are removed with it (section 5). - Product analytics and error monitoring on the website, in your browser. Uses product usage events, device and request information, and the diagnostics we need to reproduce a fault. Legal basis: consent, and only consent. Nothing is initialised until you accept on the cookie banner; declining, or using the reset button in section 3, stops it. How long: for as long as PostHog and Sentry hold it under our settings with them — they are named in section 3a. Withdrawing consent stops any further collection but does not by itself erase what was already sent; ask us at privacy@bookiq.ai if you want that too. - Crash and error reports from the BookIQ iOS and Android apps. When one of the apps crashes or hits an unexpected error, it sends a report to Sentry, which is named in section 3a. The apps do not ask you first: they have no cookie banner and no setting that turns reporting off, and it starts when the app starts. Uses the error itself and where in the app’s code it happened; the app’s version and build; the make and model of your device, the version of its operating system, and its state at the time — such as free memory and storage, battery level, screen size, the kind of network connection, language and time zone; a short trail of what the app had just been doing, such as the screens it opened and the requests it made (the address of each request, not its contents); and an identifier for that installation of the app, which is replaced if you remove the app and install it again. In the iOS app a report also carries a code calculated from an identifier Apple gives our apps on your device, the device model and the app’s own id; that code can stay the same after a reinstall. Nothing in the apps puts your account, your name, your email address, your phone number or your business on a report, and the apps send no screenshots and no recordings of your screen. Two limits, stated because they are true. First, a report includes the text of the error and, in the iOS app, the titles of the screens that were open; the apps strip what they recognise as an email address, a sign-in token or a long number from that text where they can, but we cannot promise it will never contain something that was typed in or shown on screen. Second, the apps do not put your location on a report, but Sentry may add an approximate one — city, region and country — which it works out from the network address a report arrives from. Legal basis: legitimate interests — an app on your phone cannot be fixed until we can see that it failed. We use these reports to find and fix faults in the apps and for nothing else. How long: for as long as Sentry holds them under our settings with it. A report is not tied to an account, so deleting your account does not remove it and we cannot look yours up from your account; if you want a report from your device deleted, email privacy@bookiq.ai with the device model and roughly when the app failed, and we will delete what we can identify from that. If you do not want these reports sent at all, the only way to stop them is not to use the apps; in your browser, the website sends nothing of this kind without your consent. - Keeping the service secure and investigating misuse. Uses sign-in events, IP addresses, device identifiers and audit records of who changed what. Legal basis: legitimate interests — protecting accounts and being able to investigate an incident; and legal obligation where a law requires the record. How long: it depends on the record, and a single number would be wrong for most of them. A sweep runs weekly inside our database over a register of audit tables and deletes or archives what is past its age: most entries on that register are set to 12 months, and the audit trails behind invoices, tax, payments and consent are set to 7 years, for the same statutory reason section 5 gives for financial records. Two limits on that sweep, stated because they are true rather than because they are flattering. First, a newly created audit table joins the register automatically but joins it switched OFF, so until a person reviews it and switches it on, nothing deletes it — discovery is automatic, enabling is not. Second, the sign-in log kept by the service that authenticates you — a row for every authentication and account-security event on your account, which today means sign-ins and sign-outs, session refresh and revocation, sign-up, password, re-authentication and email-confirmation requests, password changes, second-factor enrolment and use, and changes to or deletion of the account itself, recording the account it belongs to, the email address involved, the method and the time, and, for the second-factor events, the IP address they came from — sits outside that sweep, and outside the erasure list in section 5, and is not on an automatic deletion timetable today. Ask us at privacy@bookiq.ai and we will delete your entries from it: every row in that log carries the id of the account it belongs to, so yours can be identified and removed. - The AI features. Uses the text of prompts and the documents you upload. No feature of BookIQ.ai records audio or sends audio to OpenAI. Section 3a names the provider. Legal basis: contract — you switch the feature on and ask for the result. How long: your own search, voice and AI conversation history is erased with your account (section 5), and the audit record of AI requests is one of the 12-month entries on the register described in the security purpose above. There is no setting inside BookIQ.ai today that lets a business choose a shorter period for it; if you need one, email privacy@bookiq.ai and we will tell you what we can do. The AI receptionist, which answers phone calls, has its own entry below. - The AI receptionist for phone calls. When a business switches on the AI receptionist, an AI assistant answers calls to its BookIQ.ai number, including calls the business forwards there from its own number. The assistant can tell a caller about the business’s services, prices, opening hours, free appointment times and which of its team can be booked, book an appointment the caller has agreed to after hearing it read back, or take a message for the business. It cannot look up, change or cancel an existing booking. We do not offer it to a business whose profile in BookIQ.ai says it provides health services, because callers to those businesses may tell the assistant about their health. What happens on a call. The first thing every caller hears is: “Hi, you’ve reached [the business’s name]. I’m their AI assistant. This call is transcribed so I can help you, and it isn’t recorded.” It is spoken before anything else and cannot be interrupted, the business cannot change or remove it, and we record when it was played. The business’s own greeting, if it has one and it does not contradict the announcement, follows it. Twilio carries the call and turns what the caller says into text as they speak, using the speech services named in section 3a; that text goes to OpenAI, which writes the assistant’s reply as text, and Twilio turns the reply into speech. We do not give OpenAI the number the caller is calling from, or any digit of it: when the assistant reads a booking back, the last four digits it says are added by our own software. A phone number the caller says during the call, such as a number to call them back on, does reach OpenAI as part of what they said. If the assistant cannot carry on — for example because something has failed — Twilio asks the caller to leave a message and turns what they say into text in the same way. The call is not recorded: BookIQ.ai keeps no audio of it, and we do not ask Twilio or anyone else to keep any audio of it or a transcript of it. What it uses. The number calling, the number called, the time and length of the call, the text of what the caller and the assistant said, the time the announcement was played, and what came of the call — a booking, a message, or neither. A booking made on a call, with the caller’s name, number and any email address they gave, becomes part of the business’s records like a booking made online (the entry for running a business’s bookings above), and so does a message, with any number the caller gave to be called back on. The business is told what happened by email and, if its owner uses the BookIQ app, by a push notification; these include the caller’s number, and they can include when the call was made, what the caller said and a short summary the assistant wrote. Notices about calls that ended before anything was booked or a message was left, or that could not be completed, are limited to a set number for each business each hour and each day, and above that limit no notice is sent for such a call. The business’s part. The business decides to switch the assistant on and which number it answers, and we answer its calls for it. If it forwards its own number to BookIQ.ai, only the business can remove that forward, with its phone company, and until it does, its calls keep arriving at BookIQ.ai. Legal basis: contract with the business that switched the assistant on; and, for information about the caller, the basis the business itself relies on, as for its other clients (see the Data Controller section). The announcement at the start of every call is how a caller is told. How long: the text of a call and the record of what came of it are kept for 90 days after the call and then deleted. A booking or a message the call produced stays with the business’s records after that, and the email and the notification the business received are its own copies, which that deletion does not reach. Twilio keeps its own record of each call — the numbers, the time and the length — under its terms with us. It also logs the requests it sends our servers during a call and our replies, which for a message left after a failure include the text of that message: Twilio says its console keeps those logs for 90 days, and its request inspector can keep an exact copy of each request and reply for 30 days; it can also keep the text it was given to speak in its logs for up to 30 days. OpenAI keeps what we send it for up to 30 days to check for abuse, unless the law requires it to keep it longer or it needs it to protect its services or anyone else from harm; under its terms for the way we use its API it does not otherwise store it, apart from an encrypted cache it uses to process requests faster, and it does not use it to train its models unless we opt in, which we have not. We do not use calls to train any AI model. Twilio’s terms for its AI features (its Predictive and Generative AI/ML Features Addendum) let Twilio process what passes through a call to provide those features, to comply with the law, to make those features available and improve their performance, functionality, safety and security — which, in Twilio’s words, includes without limitation development and model training to detect, investigate and prevent security incidents, network exploits and abuse, spam, and violations of Twilio’s Acceptable Use Policy — and to improve, train or fine-tune those features solely for our benefit in connection with our use of them. They do not let Twilio use it to improve, train or fine-tune its other AI features, or any related models we do not use, or pass it to a speech service so that service can train or fine-tune its own base model, unless we accept further terms that allow it. If you phoned a business. Ask the business you phoned. You can also email privacy@bookiq.ai with the number you called, the number you called from and roughly when; we will find the record, pass your request to the business and tell you that we have. - Regional defaults, weather, travel time, public holidays and QR images. Uses your IP address to pick a sensible currency and time zone, an appointment’s coordinates for weather and travel estimates, and the value encoded into a QR code. Section 3a names each provider and what it receives. Legal basis: legitimate interests — showing you the right defaults without making you configure them. How long: we do not keep the lookup beyond answering it, except for an address-lookup cache that is cleared daily, and except where the answer is saved onto the record it belongs to. - An account or channel you connect. Uses whatever the integration you switched on sends and receives — the third group in section 3a lists them. Legal basis: consent — nothing is sent until you connect the account, and disconnecting it withdraws that consent. How long: until you disconnect it. The other provider keeps its own copy of what it received, under its own terms, and we cannot delete that for you. - Meeting our legal obligations and defending claims. Uses financial records, the record of which documents you accepted, and material relevant to a dispute, a chargeback or a regulator’s enquiry. Legal basis: legal obligation, and legitimate interests in establishing, exercising or defending legal claims — the GDPR calls those Art. 17(3)(b) and 17(3)(e), which section 5 already relies on. How long: 7 years for financial records; for anything else, for as long as the claim or the limitation period that applies to it. Where we rely on legitimate interests you can object under section 6, and we will stop unless we have compelling grounds we can show you. Where we rely on consent you can withdraw it at any time; that stops what happens next but does not undo what was already done while the consent stood. 3. Cookies & Tracking We use cookies for sign-in and, with your permission, for product analytics (PostHog) and error monitoring (Sentry). On your first visit we ask whether you accept analytics & error-monitoring cookies. You can change your choice at any time using the button below — it will reset your preference and show the banner again on the next page load. That banner is on the website. The BookIQ iOS and Android apps have no banner, and you are not asked before they send a crash or error report; section 2b sets out what those reports carry. Reset cookie preferences 3a. Subprocessors The list below names the third parties that process personal information on our behalf so that BookIQ.ai can run. Which of them apply to you depends on the features you use: the core platform subprocessors are involved in every account, and the rest are engaged only when you turn on the relevant feature or connect the relevant account. We keep this list current and we update it before engaging a new subprocessor that processes personal information. If you would like to know more about any of them, email privacy@bookiq.ai. A mobile number given with an agreement to receive text messages, and the record of that agreement, are not shared with, sold to or made available to any company on this list for marketing or promotional purposes; for those text messages, the only companies on this list that handle the number or the record are Supabase, which stores both, and Twilio, which receives the number to deliver each message. - Core platform — used for every account - Supabase (Sydney, Australia) — primary database, authentication and file storage. Receives everything you and your clients enter into BookIQ.ai. - Vercel (United States, with a global edge network) — website and application hosting. Receives web request metadata including IP addresses; requests are served from the edge location closest to the visitor, which may be outside Australia. - Stripe (United States) — payments and subscription billing. Receives billing identity, payment-method metadata, and subscription and invoice records. - Resend (United States) — sending transactional email. Receives recipient email addresses and message content. - Migadu (Switzerland) — receiving email sent to our addresses. Receives inbound message content. - Sentry (United States) — error and performance monitoring on the website in your browser, only with your consent; and crash and error reports from the BookIQ iOS and Android apps, which are sent without asking you first (section 2b). From the website it receives error reports, device and request information, and session diagnostics used to reproduce a fault; on-screen text is masked before it is sent. From the apps it receives the crash and error reports section 2b describes, and no session diagnostics. - PostHog (United States) — product analytics, only with your consent. Receives product usage events and device information. - Google (United States) — Sign in with Google, and Google Maps for addresses and geocoding. Receives the sign-in profile you choose to share and the addresses looked up. - Apple (United States) — Sign in with Apple. Receives the sign-in identity you choose to share. - Expo (United States) — delivery of push notifications to the BookIQ mobile app. Receives device push tokens and notification content, and passes the notification to Apple’s or Google’s push service for final delivery to the device. - Twilio (United States) — delivering text messages (section 2a), and carrying phone calls to a business’s BookIQ.ai number, including calls the business forwards to it. Receives the mobile number and the content of each text message, and for each call the number calling, the number called, the time and length of the call and the sound of the call while it is in progress. When the AI receptionist answers a call, Twilio also turns the caller’s speech into text and the assistant’s replies into speech, using the speech services named at the end of this list, and it keeps logs of the requests it sends our servers during the call, of our replies and of the text it was given to speak, for up to 90 days (section 2b says which log keeps what). Twilio does not record the call for us. - OpenAI (United States) — the AI features (the in-app assistants, document understanding, semantic search, and the AI receptionist). Receives prompt content and uploaded documents; and, for a call the AI receptionist answers, the text of what the caller says — never the audio — and the business’s own information the assistant needs to answer, such as its services, prices, opening hours, free appointment times and the names of team members who can be booked. We do not give it the number the caller is calling from, or any digit of it; a phone number the caller says, such as one to call them back on, reaches it as part of what they said. Section 2b says what OpenAI keeps and that it does not train its models on it. - Location, scheduling and utility services - ip-api.com (processing location not published by the provider) — approximate location from an IP address, used to set regional defaults such as currency and time zone. Receives the visitor’s IP address. - Open-Meteo (European Union) — weather for an appointment’s location. Receives appointment coordinates. - OSRM (community-hosted; processing location not published) — travel-time estimates between two points. Receives origin and destination coordinates. - goQR (Germany) — generating QR-code images for payment and sharing links. Receives the encoded value, which can include a booking or invoice reference, and the IP address of whoever views the code. - Nager.Date (European Union) — public-holiday calendars. Receives a country code and a year only, and no personal information. - Accounts and channels you connect — used only if you connect them - Square (United States), PayPal (United States), Alipay (China) and WeChat Pay (China) — payments taken through a payment account you connect. Receive payer identity and transaction data. - Meta (WhatsApp Business, Facebook, Instagram — United States), LINE and LINE Pay (Japan and Asia-Pacific), WeChat (China), Telegram and Viber (processing location not published), and Kakao (South Korea) — messaging channels you connect. Receive your clients’ channel identifiers or phone numbers and the content of the messages sent. - X (Twitter) and LinkedIn (United States) — publishing posts from a social account you connect. Receive the post content and media you publish. - Slack (United States) and Zoom (United States) — team notifications and meeting links. Receive notification content, and the participant name, email and scheduling details for a meeting. - Microsoft (Outlook and Microsoft 365; region depends on your Microsoft tenant) — calendar, contacts and email integration. Receives calendar events, contacts and email metadata. - HubSpot (United States) — CRM sync. Receives client contact records. - Xero (processing location depends on your Xero account), Intuit QuickBooks (United States), MYOB (Australia) and Mailchimp (United States) — accounting and marketing sync. Receive invoice and client billing records, and for Mailchimp, client email addresses and engagement data. - Toast (United States) — point-of-sale sync. Receives order and customer records. - Statutory recipients — not our subprocessors - Government e-invoicing portals (Mexico, Brazil, Italy) — where you issue an electronic invoice that a country’s law requires to be filed, the invoice is transmitted to that country’s tax authority, including your client’s identity and tax identifiers. Those authorities are statutory recipients, not processors acting on our behalf. - Configured in our software but not enabled today - Our software also contains integrations for Anthropic, Microsoft Azure OpenAI, Microsoft Azure Cognitive Services Speech, Amazon Web Services (Amazon Polly and Amazon Transcribe), Google Gemini, Google Cloud Speech-to-Text, Google Cloud Text-to-Speech, Google Cloud Translation, DeepL, Mapbox, HERE Technologies and SendGrid. None of them is enabled on BookIQ.ai today and no personal information is being sent to them. We will update this list before enabling any of them. Google Cloud Speech-to-Text, Google Cloud Text-to-Speech and Amazon Polly in that list mean BookIQ.ai’s own connections to those services, which remain off. When Twilio uses Google or Amazon for a call, it does so as Twilio’s own subprocessor, as the last entry in this list says. - Phone calls answered by the AI receptionist — used only if a business switches it on - Speech services Twilio uses for a call — Deepgram and Google turn the caller’s speech into text; ElevenLabs, Amazon Polly and Google turn the assistant’s text into speech. Twilio’s list of its subprocessors places Deepgram, Google’s speech-to-text and Amazon’s speech services in the United States and ElevenLabs in the United States and the European Union, and does not say where Google’s text-to-speech runs. Which of them handles a call depends on the language the business’s line answers in and on how we set the line up; Twilio also says that if the speech-to-text service chosen for a transcription cannot start because of an outage, it uses the other one, Google or Deepgram, instead. Twilio engages them as its own subprocessors under its terms with us. The speech-to-text services receive the caller’s voice while the call is in progress; the text-to-speech services receive the text of what the assistant says. 3b. Where Your Information Is Processed BookIQ.ai is operated from Australia and your account data is stored in Sydney, Australia. Some of the subprocessors listed above operate outside Australia — principally in the United States, and in the European Union and Switzerland — so using BookIQ.ai involves disclosing personal information to overseas recipients. If you connect one of the optional accounts or regional payment and messaging services listed in section 3a, personal information may also be disclosed in that provider’s country, including Japan, South Korea, China, Mexico, Brazil and Italy. The country for each subprocessor is shown in section 3a where we are able to state it. A call the AI receptionist answers is processed outside Australia, including a call to an Australian business: Twilio carries it, its speech services handle the caller’s voice and the assistant’s replies — in the United States, according to Twilio’s list of its subprocessors, which also places ElevenLabs in the European Union and does not say where Google’s text-to-speech runs — and OpenAI writes the replies in the United States. The part of our own software that passes the call between Twilio and OpenAI may run in the United States too. The part that looks up the business’s services and free times and makes a booking runs in Sydney, Australia, and the record of the call is stored there with the rest of the business’s information. Where personal data is transferred out of the European Economic Area or the United Kingdom, we rely on the data-processing terms offered by each subprocessor, which for these transfers incorporate the European Commission’s Standard Contractual Clauses, or on an adequacy decision where one applies. If you would like more detail about a particular transfer, contact us at privacy@bookiq.ai. 4. Data Security We implement appropriate technical and organizational measures to protect the security of your personal information. However, please note that no method of transmission over the Internet or electronic storage is 100% secure. 4a. Which Uploads Are Publicly Readable Images you publish as part of your public presence — your business logo, banner, and service photos — are stored in publicly-readable storage and can be viewed by anyone with the image link, including people who are not signed in; everything else you upload, including profile photos, documents, and any media you mark as not public, is stored privately and is served only through short-lived links issued to you or to the business you are booking with. 4b. If There Is a Data Breach If personal information we hold is lost, or is accessed or disclosed without authorisation, we treat it as a suspected data breach, contain it and investigate it. What we then owe you is set by law, and we commit to it here so that you can hold us to it: - In Australia, under the Notifiable Data Breaches scheme in Part IIIC of the Privacy Act 1988 (Cth), we assess a suspected breach within 30 days of becoming aware of it. If we conclude it is an eligible data breach — one likely to result in serious harm — we notify the Office of the Australian Information Commissioner and the people at risk as soon as practicable after reaching that conclusion. - Where the GDPR applies to the information, we notify the relevant supervisory authority within 72 hours of becoming aware of the breach, unless it is unlikely to result in a risk to people’s rights and freedoms; and where it is likely to result in a high risk to them, we tell the affected people directly and without undue delay. - How we will tell you. By email, to the address on your account. If we cannot reach you that way we publish the notice on bookiq.ai. It will say what happened, what information was involved, what we have done about it, and what we suggest you do. - If it affects your clients’ information. Where you use BookIQ.ai to hold information about your own clients and a breach affects it, you may have your own duty to notify them and the regulator. We will give you the detail you need in order to do that, and we will not treat that as your problem alone. If you think you have found a security problem in BookIQ.ai, please tell us at privacy@bookiq.ai rather than publishing it, and give us a reasonable chance to fix it. 5. Data Retention We retain your personal data only for as long as necessary to provide our services and comply with legal obligations: - Active accounts: Data is retained while your account is active - Deleted accounts: When you ask us to delete your account we schedule the erasure 30 days out, and you can cancel it at any point in that window. On the 30th day your personal data is irreversibly anonymised or deleted — your name, email address, phone number, address and profile photo; your sign-in identities, passkeys, two-factor factors and active sessions; your device tokens and notifications; your search, voice and AI conversation history; and the IP addresses and device identifiers recorded against you in our audit logs. One record is deliberately named here rather than left for you to assume: the sign-in log kept by the service that authenticates you — a row for every authentication and account-security event on your account, which today means sign-ins and sign-outs, session refresh and revocation, sign-up, password, re-authentication and email-confirmation requests, password changes, second-factor enrolment and use, and changes to or deletion of the account itself, recording the account, the email address involved, the method and the time, and, for the second-factor events, the IP address they came from — is not erased with your account today, and neither are the few IP addresses it holds. Ask us at privacy@bookiq.ai and we will delete your entries from it: every row in that log carries the id of the account it belongs to, so yours can be identified and removed. Before you confirm, we show you the exact list, generated from your own account, of what will be removed and what will be kept. - Files you uploaded for a business are not erased with your account: deleting your account does not delete the business you run on BookIQ.ai. Its bookings, staff records and financial records carry on, so the files you uploaded on the business’s behalf stay with the business — its branding (logo and banner), its service, portfolio and partner-directory media, the documents attached to its records, and its e-invoices. Images the business publishes stay publicly readable (see section 4a). Two things keep them: this is the business’s own material rather than your personal data, and e-invoices and business documents are separately held under statutory record-keeping duties — GDPR Art. 17(3)(b) (compliance with a legal obligation) and Art. 17(3)(e) (establishment, exercise or defence of legal claims). E-invoices and other financial records follow the 7-year period below; the rest are kept for as long as the business keeps them, and the business can delete them from inside BookIQ.ai at any time. If you believe a particular file is your own personal data, email privacy@bookiq.ai and we will assess it individually and delete it where Art. 17 applies. - Phone calls answered by the AI receptionist: the text of a call and the record of what came of it are kept for 90 days after the call and then deleted (section 2b). They are kept with the business’s records, not with an account holder’s own information, so deleting a business owner’s account does not delete them sooner and does not keep them longer. A caller who wants the record of a call deleted sooner can ask the business, which can ask us to delete it, or email privacy@bookiq.ai, and we will pass the request to the business. - Financial records: Transaction data is retained for 7 years as required by Australian tax law - Audit logs: Each audit table is entered on a retention register with an age against it, and the weekly sweep described in section 2b deletes or archives the entries of every table on that register that has been switched on. Most of the switched-on tables are set to 12 months; the audit trails behind invoices, tax, payments and consent are set to the 7-year period above instead. We are not going to round that up into a promise about every log we hold, because section 2b names two things the sweep does not reach: a table that is on the register but has not been switched on, which nothing deletes, and the sign-in log kept by the service that authenticates you. - Backups: We keep encrypted backups of our production database. Data you delete from the live service can remain in a backup for a short period afterwards — no more than 30 days — and is then overwritten in the normal backup cycle. We do not restore deleted personal data from backup except where we are required to. 6. Your Data Rights (GDPR) If you are a resident of the European Economic Area (EEA), you have certain data protection rights: - Right to access: Request copies of your personal data - Right to rectification: Request correction of inaccurate data - Right to erasure: Request deletion of your personal data. Section 5 sets out what a deletion removes, what it keeps and why; you can start one at bookiq.ai/legal/delete-account - Right to restrict processing: Request limitation of data processing - Right to data portability: Receive your data in a structured format - Right to object: Object to processing of your personal data If you phoned a business that uses the AI receptionist, the record of your call is information that business keeps about you; section 2b says how to ask about it. 6a. Complaints If you think we have mishandled your personal information, or we have not answered a request under section 6, tell us first. Email privacy@bookiq.ai with “Complaint” in the subject and tell us what happened and what you would like us to do. We will answer you in writing within 30 days, as section 7 commits. If we need longer than that we will tell you why, and when to expect our answer. If you are not satisfied with our answer, or we do not answer in time, you can take it further: - In Australia — to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au (https://www.oaic.gov.au), which carries its current complaint form and contact details. The OAIC normally asks you to complain to us first and to allow us 30 days to respond, which is why the paragraph above comes first. - In the European Economic Area or the United Kingdom — to the data-protection supervisory authority for the country you live or work in, or where the problem happened. In the United Kingdom that is the Information Commissioner’s Office at ico.org.uk (https://ico.org.uk). - Anywhere else — to the privacy or data-protection regulator for your country. If you tell us where you are, we will point you at the right one. Complaining to us is not a precondition of anything else. It does not limit any other remedy you have, and it does not affect your rights under the Australian Consumer Law or any other law that cannot be excluded. 7. Contact Us If you have any questions about this Privacy Policy or want to exercise any of your data rights above, please contact us at privacy@bookiq.ai. We will respond within 30 days as required by GDPR. Back to Sign Up (/signup.html)|Terms of Service (/terms-of-service.html)