Who we are
Bludge is operated by Jewell Group Pty Ltd (ACN 649 111 357) as trustee for Jewell Group Trust, trading as Jewell Projects (ABN 56 822 550 848). Our principal place of business is 1190 Dandenong Road, Murrumbeena VIC 3163, Australia. Our address for service is PO Box 933, Carnegie VIC 3163, Australia.
Contact [email protected] about personal information, or [email protected] about the service. You can request a copy of this policy in another accessible format.
This policy covers our website and the business software we host, configure and maintain, including enabled forms, records, communications, scheduling, payments and AI features. A business using Bludge also has its own privacy responsibilities and should provide its own privacy notice.
Our role and the business using Bludge
We handle account, enquiry, support, billing and security information to operate our own business. We also hold information that our customers collect through their systems. For that information, the customer generally decides what to collect, who can access it and what work the system performs. We process it to provide the agreed service and follow lawful instructions, with limited additional handling for our own security, billing, legal obligations and disputes.
Where a law uses controller and processor roles, those roles depend on the activity. Describing us as a processor does not remove our own Australian privacy obligations.
If your information was supplied to a business using Bludge, contact that business about its use of your information. You can also contact us; we will help identify the responsible business and address matters within our control.
Information we collect and hold
Depending on the features used, information includes:
- Account information: names, email addresses, business details, telephone numbers, account roles, authentication and account activity records. Password authentication uses password hashes rather than storing readable passwords.
- Enquiries and support: contact details, information you submit when arranging a call or requesting help, and our correspondence.
- Business records: form answers, customer and staff details, enquiries, tasks, notes, approvals, bookings, uploaded files, documents and communications. The contents depend on the business's configuration.
- Unexpected sensitive information: health, care or other sensitive details that someone supplies outside a supported use. For example, health details given to a business that does not use health mode, or put in a form that is not marked as asking for health information. If such information is received, we restrict unnecessary access and use, assess the appropriate lawful response and arrange removal or other necessary handling. It is not permission to send that information to an external AI service. Health businesses that use health mode are covered in Patient information at health businesses.
- Phone and message information: numbers, caller details, live call audio, transcripts, summaries, messages, outcomes, timestamps and actions taken during a conversation.
- Review information: for a business that uses review requests, whether a customer agreed to a review text, the mobile number it went to, when it was sent and whether its link was opened. We also hold public reviews of the business (reviewer display name, rating, words and link), review notification emails the business forwards to us, and the business's public Google rating and review count, and those of up to three nearby businesses it chooses to compare with.
- Transaction information: amounts, payment status, processor references, refunds, customer acceptance and audit evidence. Card entry takes place on Stripe-hosted payment pages. Do not give card numbers or security codes to the phone assistant or put them in ordinary forms or messages.
- Technical information: IP addresses, browser and device details, session identifiers, requested pages, security events, usage and error records.
We receive information directly from people using our website or software, from the business they deal with, and through imports, integrations, calls, emails and messages. If information needed for a particular service is not supplied, we may be unable to provide that service.
How we use and disclose information
We use information to respond to enquiries, configure and provide the agreed software, manage access, process records and communications, support users, bill for services, prevent misuse, investigate incidents and meet legal obligations. Customer-directed messages, bookings and other automated work use the information needed for the enabled workflow.
A business can switch on review requests. Bludge then texts a customer one link to leave a public review after their booking, with one reminder at most, only when the customer ticked the consent box on the booking form or agreed on the phone. Every text says how to stop them. We read the business's public reviews to show them to the business, alert it to new ones and draft replies it can post itself. Bludge does not post reviews or replies on any review site.
We do not sell personal information. Customer content is not available for another customer's use. We do not use customer content to train our own AI models. Supplier processing and retention are separate and are described below.
We disclose information to authorised users of the relevant business, suppliers needed to provide the enabled service, people or services the business instructs us to contact, professional advisers where necessary, and authorities where disclosure is required or authorised by law. We take reasonable steps to limit each disclosure to its purpose.
Automated decisions
Some parts of Bludge make decisions by computer, without a person checking each one first. A business chooses which of these to switch on, and sets their rules. The ones that can affect a person are:
- Bookings by the AI assistant. On a call or in website chat, the assistant checks availability and books a time, using the business's opening hours, booking rules and prices, and the person's name, contact details and what they ask for. It tells the person when a time isn't available. It doesn't move or cancel bookings.
- Form rules. A business can set rules that run when a record is saved, its status changes or a date arrives. A rule can change a status or a field, assign the record, set a due date, add a task, create a related record, or send an email, a text or an AI phone call. Rules use the record's answers and the person's contact details.
- Who gets texts and calls. Before sending, Bludge checks the choices a person has given. Review requests go only to customers who agreed. At a health business in health mode, texts and AI phone calls go only to patients who agreed to overseas processing, and a patient whose choice wasn't recorded is treated as not agreeing.
- Passing you to a person. The assistant passes a caller or visitor to the team, or takes a message, following the business's settings.
- Protecting the service. Bludge limits repeated sign-in codes, messages and form submissions that look like misuse. It uses the account, the time and the network address.
AI drafts, summaries and suggestions for staff are not automated decisions: a person reviews them before using them.
To ask about a decision, or to ask a person to look at it again, contact the business that uses Bludge. You can also contact us at [email protected].
AI features and phone conversations
Staff drafting features use xAI. When a permitted user requests a draft, relevant notes, record content or conversation history are sent to xAI to produce the result. These features require the organisation's AI setting and a configured service. Staff must review generated material before relying on or sending it.
Staff can email meeting notes or a transcript to their business's notes address. Bludge keeps the email only when it passes email sender checks and comes from an active staff member's own address, and saves it as a private meeting record. If the organisation's AI setting is on, the notes and transcript text are then sent to xAI to fill in the meeting details and pick out lessons about the business. These are saved without a separate review, marked as added from email, and staff can change or remove them.
Help chat with Bea. If you ask Bea a question, we send it to OpenAI with earlier chat messages, your role, the type of screen you are on and the Bludge help that applies. Bea explains how to use Bludge. It cannot look up or change your records. Leave out names, contact details, passwords and other private information.
If Bea is unsure or you mark a reply unhelpful, we may send the masked question, reply and earlier chat context to OpenAI for another check. The check may use feedback you include with that request.
We keep Help chats and any feedback you leave to improve Bludge. Before we save chat text, we mask common contact details such as email addresses, phone numbers, street addresses and card-like numbers. Other details you type may remain. The saved chat keeps your business and role. We keep request counts and usage logs separately. Bludge's authorised super admins handle requests to delete saved Help chats.
The optional business intake interview uses OpenAI for text questions and summaries, and xAI for browser voice. With your agreement, we send your intake answers, typed details and conversation to these services. Voice transcripts can be included in an OpenAI summary. You can submit the intake without using the AI interview.
If you add a business website and agree to the website notice, OpenAI helps prepare starting answers from its public pages. This website step sends the public page text and metadata. It does not add the contact details, private answers or files you enter in the intake. You can check and change the suggested answers. The written form itself does not send your answers to AI.
The phone assistant is enabled separately. It uses Twilio for telephony and xAI for live voice understanding, transcription and responses. It receives the conversation and relevant business configuration. Enabled tools can supply information needed for a request, such as services, availability and booking details. If a business publishes information for the assistant to look up, it is uploaded to xAI Files and Collections; this is stored supplier content, rather than only a passing voice stream. This publishing is not currently switched on.
A business can also add a chat to its website. Website voice works like the phone assistant and uses xAI through our voice gateway. Written website chat uses OpenAI. Each visitor message is sent to OpenAI with the earlier messages in that chat, the business's approved website answers and the results of enabled tools, such as opening hours, services, availability and booking details, so OpenAI can write the reply. Do not give passwords, card numbers or security codes in a website chat.
Talking to a person. A business can let callers and website visitors ask to talk to someone from its team. Bludge then alerts the staff members the business chooses by text message, WhatsApp, email or a Slack channel the business connects. The alert includes the visitor's name, if they gave it, and their latest message. When a staff member joins a written chat, the visitor's messages are passed to them through the same service, and the visitor sees the staff member's first name and replies. A staff member's replies are stored in Bludge with the chat. In a phone call or website voice call, Twilio rings the staff member's phone and can read them a short summary of the call first. If they accept, the caller talks with them directly. Bludge does not record or transcribe that part of the call. If they don't take the call, and the business has chosen it, Twilio texts them the caller's name, if given, their latest words and a link to the call in Bludge. The caller's phone number is not in the text.
Free AI visibility report. If you ask for a free AI visibility report at bludge.ai/ai-visibility-check, we check your website's public pages ourselves and send its address to Google PageSpeed Insights. We also send your website address, business name, type of business and area to OpenAI (ChatGPT), Anthropic (Claude) and Google (Gemini) to ask their assistants questions a customer might ask, with web search switched on. We do not send them your name or email address. We keep the answers in your report and email it to the address you give, as a PDF and a private link. We save your request as an enquiry so a person from Bludge can follow it up. We also send you occasional tips from Bludge by email, as the form says. Every tips email lets you unsubscribe. We keep reports for up to 12 months unless you become a customer, and you can ask us to delete yours sooner.
Google profile checks. When the check is available, we send your business name and area to Google Maps to look for your public business profile. We use your website address to help check if we found the right profile. To show nearby listings, we send the type of business and area. In Reviews we use the listing IDs your business chooses. We show live listing details and keep listing IDs and check records such as when you asked for a check. Use of Google Maps features and content is subject to the Google Maps terms and Google Privacy Policy.
We may also prepare a report about a business from its public details, such as its website, name, trade and area, to show the business how AI assistants describe it. We send those details to the same providers. We do not contact the business automatically.
Some Strategy & growth features use Google's Gemini models:
- AI Business Coach: a business can ask its AI Business Coach a question through a connected AI assistant. The question and any subject keywords are sent to Gemini to find matching lessons and check how well they fit. The lessons are our summaries of public videos and articles. The coach's answer also includes a short profile of the business from Bludge: its name, contact address, the plans and notes saved in its Strategy & growth workspace, and the names of the dashboards and kinds of records the person asking can see. That profile goes only to the person's connected AI assistant, not to Gemini, and includes only what that person's access allows.
- Advice sources: Gemini writes transcripts of public YouTube videos chosen as advice sources, including videos from a channel a business adds as its own advisor, and works out who is speaking in them. xAI then turns the public transcripts and articles into lesson summaries. These requests contain public material, not a business's records.
- Narrated presentations: where we have switched narration on for a business and a permitted administrator requests it, the presentation's spoken script is sent to Gemini to produce the audio.
- Search by meaning: while a business has AI access on, unless its admin switches off Search business knowledge by meaning, the text of its business knowledge, the summary fields of its sales meeting records (never the meeting notes or transcript) and its published documents are sent to Google's Gemini embedding model on Google Cloud to work out their meaning, and so are search questions. For a business in Australia this uses Google Cloud's Sydney region; for other businesses, its United States region. Bludge keeps the resulting numbers, not extra copies of the text, and deletes them when the setting is switched off.
- Short videos: where we have switched video creation on for a business and a person approves a video's script, the script is sent to Gemini to produce the voice, and descriptions of the pictures and short clips are sent to Gemini to produce them.
Video creation uses Anthropic's Claude to plan each video. When a permitted person asks for a video, Claude receives the topic and any notes, the business's name and the brand voice from its accepted brand profile. It writes a script and scene plan for a person to check. Claude also looks at still images from the draft video to check its layout. Making the voice, pictures and clips starts only after a person approves the script. The finished video is made on our own servers and added to a draft post, which still needs the normal approval before anything is posted.
Music in videos. If a business chooses AI music, we send a description of the music, such as its mood and style, to Google's Lyria to make it. A business can upload its own music instead. Uploaded music stays on our systems and is used only in that business's videos.
Presenters in videos. A video can show a person, such as the business owner, speaking for part of it. We do this only if that person agrees first, and we keep a record of their agreement. With it, we send their photo, and the speech for the moments they appear, to Hedra to make the talking pictures. If they also agree to a copy of their voice, they record a short sample, including a spoken consent sentence, and we send it to Google to make a voice that only that business's videos use. The person can withdraw their agreement at any time by contacting the business or [email protected]. We then stop using their photo and voice in new videos and ask Google to delete the voice copy. Videos already published stay the business's responsibility to take down.
A business can connect its own AI assistant, such as ChatGPT, Claude, Gemini or Microsoft Copilot, to Bludge. This needs the organisation's AI setting. The assistant receives the business information it asks for, limited to what the connecting staff member's access allows. The assistant's provider handles that information under the business's own agreement with it; it is not acting as our supplier.
The phone assistant identifies itself as AI. Call audio is transmitted to suppliers while the call is happening, and transcripts and related records are stored in Bludge. Conversations with the phone assistant are not routinely recorded as replayable audio. Live audio processing, written transcripts and supplier-held records are separate from replayable recordings. The exception is voicemail: at a health business in health mode, a caller who chooses not to use the AI phone assistant can leave a message of up to 2 minutes. They are told before the tone that it will be recorded. Twilio records it, in its Australian region for numbers that have moved there. Bludge copies the recording into its storage in Australia, attaches it to a staff-only note on a message record for the business, and then deletes Twilio's copy. It is not transcribed, by Twilio or by any AI. Any diagnostic recording must be separately enabled and must have appropriate notice, consent, restricted access and verified deletion after seven days before it is used. Provider-level recording settings and diagnostic cleanup have not yet been independently verified across all services.
Turning off staff drafting does not, by itself, disable separately enabled phone or website chat processing or remove information already stored. AI can misunderstand or generate inaccurate content. People should avoid providing unnecessary sensitive information and can ask the business for another way to communicate.
Patient information at health businesses
Some health businesses, such as clinics, keep their patients' records in Bludge. They do this only after signing a Health Information Agreement with us. Then we switch on health mode, a set of extra protections.
Who is responsible. Your health business is responsible for your information. We store and process it for them, following their written instructions. Their privacy notice explains why they collect it. To see, correct or ask about your information, contact your health business first. You can also contact us at [email protected].
Where it is kept. Your records, uploaded files and our backups are stored in Australia. Our hosting provider keeps technical logs in the United States for 7 days.
What overseas services can't see. Forms your health business marks as asking for health information are kept away from AI services and connected AI assistants. Emails about them contain a link, not your details.
What goes overseas, and only if you agree. Your health business asks whether you agree to overseas processing, and we save your answer and the date. If you weren't asked, we treat it as no.
- Phone calls: you hear a short notice first. Only if you press 1 does the AI phone assistant answer. It runs in the United States (xAI). Otherwise you reach the team or leave a message. Before the tone, you are told that your message will be recorded. It is kept with your health business's records in Australia, and it is not transcribed.
- Website chat and voice: you are asked before you start, and can contact the team instead. Written chat runs overseas (OpenAI), and voice runs in the United States (xAI).
- Texts: sent only if you agreed. They go through Twilio's United States region.
Emails go through Mailgun's United States region. Emails about health forms contain only a link.
Changing your mind. Tell your health business. They update your choice, and it applies from then on. It does not recall information already processed.
Call and chat transcripts are kept for 90 days, then deleted, as described in Security and retention. Your health business copies anything it needs into your record.
Suppliers and processing locations
Only suppliers needed for an enabled feature receive the relevant information. A customer's separately connected service also receives information according to that customer's instructions and its agreement with that service.
| Supplier | Purpose and information | Processing and storage locations |
|---|---|---|
| Fly.io | Application, database, worker and voice gateway hosting; technical and operational records | Application, database, worker and voice gateway hosting has been checked in Sydney, Australia. Fly's scheduled volume snapshots, which Fly stores in the United States, were turned off on 13 November 2026; snapshots made before then expire by 18 November 2026. Fly keeps application logs in the United States for 7 days. Other hosting records need their own location and retention checks. |
| Tigris | Uploaded files and database recovery backups | The upload and recovery buckets are private and read back as Sydney, Australia (checked 13 November 2026), and a test restore from a recovery backup worked. Historical copies, exports and backup expiry have not all been independently verified. |
| Cloudflare | Domain and network service for bludge.ai and business addresses; hosting for websites a business publishes through Bludge; the Turnstile bot check on the free AI visibility report form; receiving email sent to Bludge's review and meeting notes addresses and passing it to Bludge. Receives IP addresses, request details, page and form content as it passes through, published website files, those emails (sender, recipients, subject, message and attachments) and their sender check results, and for Turnstile the visitor's IP address and browser signals | Cloudflare runs a global network. Requests checked on 9 November 2026 were served in Sydney, but Australian-only handling is not promised. The storage location of published website files has not been verified. |
| Mailgun | Outgoing email; recipients, subjects and message contents | Outgoing email uses Mailgun's US region, which involves processing in the United States. Australian-only handling is not promised. Automatic inbound attachment of email replies to application records is not currently enabled. Emails about records on forms marked as asking for health information contain a link, not the record's details. |
| Twilio | Phone numbers, live audio, call metadata, SMS recipients and message contents. When a caller or visitor asks for a person: staff phone numbers, the spoken call summary, and WhatsApp alerts and chat messages sent to staff | Calls on Australian numbers on Bludge's main Twilio account, including the numbers Bludge sets up for a business, are handled in Twilio's Australian region (AU1). If a new number cannot be moved there, it stays in the United States region (US1) until it is moved. A separate demonstration account stays in US1. Text and WhatsApp messages are handled in US1, because Twilio does not offer messaging in AU1. AU1 call handling does not make the AI voice service Australian-only; see xAI. Voicemail messages at a health business are recorded in the number's region, then copied to Bludge's storage in Australia and deleted from Twilio. At a health business in health mode, texts and AI phone calls go only to patients who agreed to overseas processing. |
| xAI | Live phone and website voice, transcription, staff drafting, AI setup assistance, lesson summaries of public advice sources, relevant tool results and, if switched on, published business knowledge. Only if follow-up AI visibility reports with Grok are used: a business's website address, name, trade and area, and the questions asked. Where a business uses reviews and has AI switched on: the text of a public review, to draft a reply, and the text of a review notification email the business forwards, to read the reviewer, rating and words | The application uses the global API, with no Australian-only processing guarantee. Stored Files and Collections have separate storage and deletion arrangements. Account-specific processing countries and voice retention remain under review. At a health business in health mode, the phone assistant answers only after the caller presses 1, and website voice starts only after the visitor agrees. Records on forms marked as asking for health information are never sent. |
| OpenAI | Written website chat: visitor messages, approved website answers and tool results, including booking details; agreed public website preparation; optional intake text interviews and summaries; supplied answers, typed details and conversation, including voice transcripts. Free AI visibility reports: a business's website address, name, trade and area, and the questions asked. Help chat with Bea: questions, masked chat history, role, screen type and Bludge help. | The global API can process information overseas. Australian-only processing is not promised. Requests disable response storage; this is not a zero-retention service. At a health business in health mode, written website chat starts only after the visitor agrees. Records on forms marked as asking for health information are never sent. |
| Anthropic | Video planning where enabled: video topics and notes, the business's name and brand voice, and still images from draft videos. Free AI visibility reports: a business's website address, name, trade and area, and the questions asked | The global API can process information overseas. Australian-only processing is not promised. The account's retention and data-use settings have not been independently verified. |
| Hedra | Video presenters, only with the person's recorded agreement: their photo and the speech audio for the moments they appear | Hedra's service can process information overseas. Australian-only processing is not promised. Its processing locations and retention settings have not been independently verified. |
| Gemini: AI Business Coach questions and keywords, business knowledge, sales meeting summaries, published documents and search questions for search by meaning unless a business switches it off, public advice-source videos and transcripts, narrated presentation scripts where enabled, and short-video scripts and picture and clip descriptions where enabled. Lyria: descriptions of music for videos, if a business chooses AI music. Voice copies: a presenter's recorded voice sample and consent sentence, only with that person's agreement. Gemini with Google Search grounding for free AI visibility reports: a business's website address, name, trade and area, the questions asked and the assistants' answers, to read them. PageSpeed Insights: public website addresses for speed checks. Places API: the search words a business uses to find its own Google listing and nearby businesses, and the listing identifiers it chooses; Google returns public ratings, review counts and up to five recent public reviews, including reviewers' display names. For Google profile checks, Places also receives the business name and area, the business type and area for nearby listings, or the selected listing IDs. It can return public categories, addresses or service-area status, website links, phone numbers, opening hours and photo information. Google Workspace: email sent to our own addresses, such as [email protected] | Gemini requests use Google's global Gemini API, with no processing region selected, except search by meaning, which uses Google Cloud's Sydney region for Australian businesses and its United States region for others. Australian-only processing is not otherwise promised. Narration requests ask Google not to store the interaction; this is not a zero-retention service. Mailbox processing locations have not been separately verified. Records on forms marked as asking for health information are never sent to Gemini. | |
| Google Ads | Only where a business links its Google Ads account to Bludge: we read its ad results. If the business switches on sending results: ad click codes from website visits, the type and time of an enquiry or sale, and any sale amount. No names, email addresses or phone numbers | Google's advertising services process information overseas, including in the United States. Australian-only processing is not promised. |
| Meta (advertising) | Only where a business links its Meta ad account to Bludge: we read its ad results. If the business switches on sending results: ad click codes from website visits, the type and time of an enquiry or sale, and any sale amount. No names, email addresses or phone numbers | Meta's advertising services process information overseas. Its processing locations have not been verified. Australian-only processing is not promised. |
| ProductReview | For a business that sends customers to ProductReview: the review link includes a Bludge reference number for the review request, not the customer's name or contact details. If the business connects ProductReview's webhook, ProductReview sends us each new published review: its identifier, rating, reviewer display name, link and that reference number | ProductReview.com.au is an Australian service. Its processing and storage locations have not been verified. |
| Meta (WhatsApp) | Only where a business chooses WhatsApp alerts: staff mobile numbers, chat alerts, and the messages passed between a website visitor and the staff member who joins. Sent through Twilio from Bludge's WhatsApp number | WhatsApp is a global service and its processing locations have not been verified. Australian-only handling is not promised. |
| Slack | Only after a business connects its own Slack workspace: chat alerts in the channel it chooses, and the messages passed between a website visitor and the staff member who joins. We read staff members' Slack email addresses to match them to Bludge users | Messages are kept in the business's Slack workspace under its own Slack agreement and settings. Slack's processing locations for that workspace have not been verified; Australian-only handling is not promised. |
| Stripe | Enabled payment and connected-account processing; payer, business and transaction information | Handling depends on the enabled account arrangement and can involve overseas processing. The relevant contracting entity, account terms and recipient countries must be confirmed during payment setup. |
| Buffer | Social media posting after a business connects its Buffer account; approved post text, images, videos, image descriptions, chosen channels and times | Buffer schedules approved posts and publishes them to the chosen social networks, where they become public. Images and videos are shared with Buffer through temporary links. Buffer's processing locations have not been verified; Australian-only handling is not promised. |
| jsDelivr and other enabled asset providers | Browser requests for interface assets, including IP address and normal request details | Some application interfaces request external assets from international infrastructure. The public website uses locally hosted assets where available. |
Overseas recipients include providers processing in the United States. Other recipient countries depend on the enabled service and supplier account arrangements; we have not yet verified a complete country list for every supplier. Contact [email protected] for information about a particular service. We permit overseas supplier processing needed for the supported service, assess applicable safeguards and limit the information sent. Primary application and storage arrangements are kept in Australia where practical; overseas supplier processing remains possible. We assess applicable Australian Privacy Principle 8 obligations. An organisation enabling a feature does not, on its own, establish an individual's informed consent to an overseas disclosure or waive our responsibilities.
Supplier contracts and settings govern their handling. Staff text requests disable provider conversation storage; this does not remove supplier security, abuse-monitoring or legal retention. xAI's published API guidance describes default audit retention and separately stored Files and Collections; its global endpoint does not guarantee a processing region. We do not opt customer content into supplier model training, and keep optional training permissions off where offered and controllable. Supplier security, abuse-monitoring and legal retention can still apply. We do not promise zero retention or that deleting a Bludge record deletes every supplier copy.
OpenAI's API data guidance says API content is not used for model training by default. It may keep request content in abuse-monitoring logs for up to 30 days, or longer for legal or safety needs. Prompt caching can also keep temporary processing data. Disabling response storage does not remove these supplier records.
Website and advertising measurement
Counting visits. On bludge.ai, on websites Bludge hosts for a business (unless the business stops it), and on a business's own website where it adds the Bludge measurement code, we count page loads. For each one we keep the page, the type of device (phone, tablet or computer) and where the visit came from: search, social media, an ad, an email or another website. We work this out from the name of the website you came from and the tags in the link, such as UTM tags and the ad click codes Google and Meta add to ad links. We also count taps on phone numbers and email addresses, and, on a business's own website, that one of its own forms was sent. We never record what you type into a form there. We count these as daily totals. We do not keep your IP address with them, and we leave out known automated visitors.
The measurement cookie. We set a cookie called bludge_v on that website. It holds a random code and lasts up to 90 days. On a business's own website the Bludge code sets it in your browser, and some browsers, such as Safari, keep it for only 7 days. It lets us link your visits in that browser to an enquiry, chat, booking request or AI visibility check you send later, so the business can see which pages, searches and ads bring enquiries. We keep a scrambled (hashed) form of the code, not the code itself. We do not use it to follow you to other websites. If your browser does not keep the cookie, we count your page loads but not your visit, and remove the record after a day. We delete visit links after 90 days and remove ad click codes from enquiries after 90 days.
Your choice. If your browser sends Global Privacy Control, we count the page load but set no cookie and link nothing to you. You can also clear or block the cookie in your browser settings.
Advertising results. When a business uses Bludge to report on or manage its Google Ads or Meta ads, we read results such as spend, views, clicks and conversions from its ad accounts. If the business switches on sending results, we send Google or Meta the ad click code from your visit, the type of result (an enquiry or a sale), its time and any sale amount. We do not send your name, email address or phone number. Google and Meta use this under their own terms to measure and improve the business's ads.
Cookies and email preferences
We use cookies needed for sessions, authentication, security and supported preferences. The application uses a session cookie across its business subdomains. Some interface assets are requested from external providers, exposing normal browser request details to them.
The website also stores a country preference when you choose a country. That preference cookie is configured to last up to 20 years unless you clear it sooner. You can remove cookies using your browser settings, although removing session cookies can sign you out. Apart from the measurement described in Website and advertising measurement, the public pages have no separate advertising or analytics integration; customer-configured pages and enabled integrations may use additional tools and should give their own notice. We review new tracking or embedded tools before enabling them and provide any required choices.
Optional notification preferences can be changed where offered in the profile or message. Essential service, security and legally required notices may still be sent. A request to stop marketing can be sent to us or to the business sending it. Do not assume ending a call automatically blocks future contact.
Security and retention
We use access controls, business-specific permissions, secure connections and audit records. Phone transcripts, summaries and selected associated fields are encrypted at the application level. Authorised staff may access information where needed for support, security or a verified request. No system can guarantee absolute security. We assess suspected breaches. If a breach affects a customer's information, we tell that customer without undue delay, and tell affected individuals and regulators when applicable law requires it.
We keep information only for as long as needed for the purposes described here and applicable legal requirements. When no longer required, we take reasonable steps to destroy or de-identify it, subject to lawful retention duties.
Current implementation status: The schedule below is our approved retention schedule. Full phone and website chat transcripts stored in Bludge are now removed automatically 90 days after the conversation ends, unless a documented hold applies. This does not remove copies held by suppliers or in backups. Complete closed-account disposal is still being implemented, and expiry of all backups within 35 days has not been verified. Automatic deletion at those other periods is not currently assured; information can remain beyond a target while these controls are incomplete. This does not remove our obligation to assess information that is no longer needed. Contact [email protected] to request a review, deletion or an explanation of the handling of particular records.
The approved schedule is:
| Information | Retention and disposal |
|---|---|
| Video presenter photos, voice samples, voice copies and agreement records | Photos, samples and voice copies are kept while the person's agreement stands and removed when it is withdrawn. The agreement record is kept for 7 years after it ends, as evidence of what was agreed. |
| Full phone and website chat transcripts and unnecessary conversation context | 90 days after the call ends, unless a documented lawful purpose requires longer. Useful booking details and necessary summaries follow the business-record schedule. |
| Saved Help chats and feedback | Kept to improve Bludge. There is no fixed expiry date. Contact [email protected] to ask us to delete a chat. |
| Voicemail recordings at health businesses | Kept with the message record they are attached to, under the business-record schedule below. Twilio's copy is deleted once Bludge's copy is stored. |
| Diagnostic audio recordings | Seven days after creation, only where recording was specifically enabled with appropriate notice and consent. |
| Business records, supplied files, booking details, tasks and useful summaries | According to the customer's documented business purpose and applicable legal schedule. Review unnecessary information periodically; an open account alone is not a reason to retain everything. |
| Ordinary technical logs | 30 days after the event; avoid storing sensitive content. |
| Security and administrator activity records | 12 months after the event, with only necessary details retained. |
| Our sales enquiries and support correspondence | Review 12 months after the matter closes and remove unnecessary personal information; retain necessary contract, dispute or legal evidence under its applicable schedule. |
| Ordinary information in a closed account | Keep available for the 30-day export window, then remove through the disposal process, subject to necessary lawful retention. This includes associated records and attachments; provider-held knowledge and copies require their own disposal steps. |
| Recovery backups under our control | Target expiry within 35 days of backup creation. A copy made just before live-data disposal can therefore remain for up to a further 35 days. Supplier-held copies and legal holds have separate arrangements. |
| Necessary company financial records | At least seven years after the transactions covered by the records are complete, where the company record-keeping requirement applies. This is not a seven-year retention period for all conversations. |
The periods above must be applied across live records, attachments, phone actions, knowledge stores, logs and backups. Cleanup of retired xAI knowledge files and some temporary application records exists, but does not establish that the whole schedule is operating. The 30-day technical-log and 12-month security-record periods also remain subject to verification across the relevant systems. The backup period is a target until actual expiry is verified.
Necessary transaction, consent, complaint or dispute evidence may remain after other records are deleted. A requirement to retain financial evidence does not justify retaining an entire conversation indefinitely. Archiving, account closure, disabling a feature and erasure are different operations. Backups and supplier copies follow their own disposal processes; restored data must be handled consistently with earlier deletion and suppression decisions.
Access, correction and complaints
Contact [email protected] to request access or correction, raise a concern, or ask about deletion, restricted use or an unwanted communication. You can also contact [email protected] if you cannot reach us through the privacy address. Identify the business involved and enough information for us to locate the relevant records. We may verify identity or authority using proportionate checks.
Our business owner is initially responsible for privacy requests and incident coordination, reached through [email protected]. We aim to acknowledge ordinary privacy requests within two business days and provide a substantive response within 30 days, subject to applicable legal deadlines. If we need more time, we explain why. Where access, correction or deletion is limited by law or another person's rights, we explain the relevant reason and available complaint options. There is no charge for making a privacy complaint; any access charge must be permitted by law and explained in advance.
If you are dissatisfied, you can contact the Office of the Australian Information Commissioner through oaic.gov.au. You may also have rights to complain to another regulator under applicable law.
Children and other jurisdictions
The service supports Australian business customers and ordinary business operations. Australian health service providers can also keep patients' health information, but only under a signed Health Information Agreement with health mode switched on (see Patient information at health businesses). Other health and care record systems, child-focused workflows, other workflows requiring special handling of sensitive information and service arrangements for overseas customers are not supported. These uses may be considered later under a separately agreed scope and safeguards.
This scope does not guarantee that unsolicited information about children or other sensitive details will never arrive. We assess such information and restrict, remove or otherwise handle it appropriately, subject to applicable law. Customers must not deliberately configure unsupported collection or use.
Overseas suppliers can still process information for our Australian service as described above. Supporting overseas customer operations is a separate decision and would require assessment of the relevant privacy, communications and transfer obligations before activation. This policy does not itself execute a data processing agreement or international transfer instrument.
Changes
The date and version identify this policy. We update it when our handling changes and give appropriate notice of material changes before the new handling begins, obtaining additional consent where required. A policy update does not retrospectively authorise a new use of information.