How we handle your information

Who we are

AmplifyBot builds and manages digital platforms for growing businesses. We are based in Brisbane, Australia and work with clients in Australia and overseas.

This policy explains how we handle personal information collected through this website. You can reach us at hello@amplifybot.io about anything on this page.

What this policy covers

This policy applies to amplifybot.io only. Websites and platforms we build and manage for our clients are operated by those clients and are covered by their own privacy policies, not this one.

What we collect

We do not require an account and there is nothing to sign up for. There are three ways to give us personal information through this site: submitting the enquiry form, typing into the assistant, and writing a testimonial if you are a client we have invited to. All three are covered below.

When you submit an enquiry, we receive:

• Your name and email address, which the form requires
• Your phone number, business name and current website, if you choose to provide them
• The services you indicated you are interested in, and a budget range if you selected one
• The message you wrote

Alongside that, we record where the enquiry came from: the page you submitted it from, the page you first arrived on during that visit, the site that referred you, and any campaign parameters in the link you followed. If you arrived by clicking one of our Google ads, that link carries a click identifier Google adds to it, and we store that with the enquiry too — it identifies the ad click, not you. This tells us which of our own marketing is working.

We also store your browser’s user-agent string, and a one-way cryptographic hash of your IP address. We keep the hash rather than the address itself: it lets us limit how many submissions come from one source and review abuse, without us holding an identifier we have no reason to keep.

The website check asks nine questions about your business and shows you the result. It does not ask who you are, and completing it tells us nothing that identifies you. We do store the answers themselves, along with the same referral information (but not the ad click identifier), user-agent string and hashed IP address described above, because what people say about their own setup is how we decide what to build next.

The builder lead check works differently. Its answers, including any figures about your ad spend or how many jobs you win, are worked out in your browser and are not sent to us or stored anywhere when you finish. We only receive them if you choose to send them with an enquiry, and then they are kept as part of that enquiry.

The AI crawler check asks for a website address. Our server fetches that site’s homepage, robots.txt and sitemap — the same public pages any search engine reads — and shows you what it found. We do not keep the address you entered or the result. The only record is a hashed IP address and the time of the check, kept to stop the tool being misused, and deleted on the same schedule as the enquiry form’s records below.

If you then choose to send us an enquiry from the result, your answers are attached to it, so the two are connected from that point on. If you do not, the answers stay anonymous and there is nothing in them to trace back to you.

Separately, we sometimes ask a client to write a testimonial. That form is reachable only through a personal link we email you — there is no public version of it, and nothing here applies unless we have asked you. If you write one, we receive your name, your email address, your role if you give it, a rating if you leave one, and what you wrote. We also store the same user-agent string and hashed IP address described above.

We record which permissions you gave us — to publish it at all, to use your name, to name your business — along with the exact wording you agreed to. Nothing goes on the site until we have read it, and nothing goes up that you did not give us permission to put there. We publish what you wrote as you wrote it; if we would like to shorten it, we send you the shorter version and use it only if you agree. Your email address is never published. You can ask us to take a testimonial down at any time.

The assistant on this site

This site has an AI assistant you can open and ask questions. Using it is optional — the site works the same if you never do — but if you do, the conversation is stored.

For each conversation we keep:

• Everything you type into it, and everything it replies
• The page you opened it from
• Your browser’s user-agent string, and a one-way cryptographic hash of your IP address — the same hash described above, not the address itself
• Technical records of each reply: which model answered, how long it took, and how much of the model’s capacity it used

We keep the conversations for three reasons: to see which questions the assistant answers badly and correct what it knows, to check it is not saying things it should not, and to work out whether it is worth continuing to run. The hashed IP address limits how many conversations can be started from one source.

Do not type anything into the assistant you would not put in an email to us. It is a way to ask questions about what we do — it is not a secure channel, and it is not the place for anything confidential or sensitive.

Your messages are sent to Mistral AI in France, the company whose model generates the replies, which is how the assistant is able to answer at all. Their commercial terms say data sent through their API is not used to train their models. Separately from that, they run a programme that uses API data to improve their services, which accounts are included in unless it is switched off — ours is not switched off. Their handling of your message is governed by their terms rather than ours.

If a conversation leads to you sending us an enquiry, the two are linked from that point, so we can see what you had already asked before you got in touch. If it does not, the conversation stays unconnected to any name or email address.

You can ask us to delete a conversation. Email hello@amplifybot.io — see below.

Analytics

This site uses Google Analytics 4 to count visits and see which pages people actually read. We use it to decide what to write next and to tell whether the work we do on search is reaching anyone.

It records:

• The pages you view, when, and in what order
• How you arrived — a search engine, a link on another site, or directly
• Your device type, browser, operating system and screen size
• An approximate location, usually the city, worked out from your IP address
• A randomly generated identifier, stored in a cookie in your browser, so that several visits from the same browser are counted as one person rather than several
• Whether you sent an enquiry, and from which form — the contact page, the website planner, the website check or the builder lead check — and whether you finished the planner or one of the checks. Never what you wrote or answered in them

That identifier is not your name. Analytics knows that an enquiry was sent from a browser, so that we can tell which pages and which of our ads lead to enquiries — it never knows what the enquiry said or who sent it. We do not pass your name, email address, enquiry, answers or assistant conversation to Google, and we do not use analytics to build a profile of you as an individual or to follow you across other websites.

Google Signals, which would associate what you do here with the Google account you are signed into and allow advertising audiences to be built from it, is switched off on our property. If we ever turn it on, this page will say so before we do.

When we advertise on Google, our Analytics property is linked to our Google Ads account so that Ads can count which ad clicks led to an enquiry. That shares the “an enquiry was sent” record described above with Google Ads, and nothing more. Personalised advertising is switched off on that link, so no advertising audience is built from visits to this site.

Google states that it does not store the IP addresses it uses to work out that approximate location. We have no way to verify that ourselves, so it is written here as their claim rather than as ours.

The analytics data is held by Google and processed in the United States, so this is an overseas disclosure. It is the only third party contacted simply by loading a page, and the tag it loads is the only script on this site that comes from anywhere but us.

If you would rather not be counted, Google publishes a browser add-on that opts you out of Google Analytics everywhere (search for "Google Analytics opt-out browser add-on"). Any tracker blocker or a browser that blocks third-party scripts will also stop it. Nothing on this site behaves differently if you do — there is no wall, and no feature depends on it.

What we do not do

As currently built, this website:

• Sets no cookies except the analytics one described above
• Runs no advertising scripts, and carries no ads
• Does not build a profile of you or track you across other sites
• Does not sell, rent or trade personal information to anyone

Until 9 September 2026 this page said there were no analytics on the site at all, and promised that if that changed the page would say what they collect before they were switched on. That is what this revision is: the analytics section above was written and published in the same change that turned Google Analytics on, not afterwards.

Third parties

Loading a page contacts Google, for the analytics described above. Pages with a form, and the assistant once you open her, also contact Cloudflare, described next. Nothing else: the typefaces are served from this website rather than from Google Fonts, and there are no other external stylesheets, fonts or images anywhere on the site.

The forms on this site — the contact page, the website planner, the website check, the builder lead check, the AI crawler check and the testimonial form — and the start of a conversation with the assistant are protected by Cloudflare Turnstile, which checks that a person rather than a bot is filling them in or starting the chat. It runs in your browser and sends Cloudflare, a United States company, information about your browser and how the page is being used, which Cloudflare handles under its own privacy policy. We receive only its yes-or-no answer.

Enquiries and assistant conversations are stored in a PostgreSQL database hosted by Binary Lane, an Australian company, on servers in Australia. Some things do leave the country. Analytics goes to Google, as covered above, and the form check to Cloudflare. When you send an enquiry, a copy of it is emailed to us through Resend so that a person sees it rather than it sitting in a database unread; Resend processes data in the United States, so the contents of your enquiry go there. Our mailboxes are provided by Microsoft 365, and we reply from there; Microsoft handles that email under its own terms and may process it outside Australia. The assistant’s replies are generated by Mistral AI in France, as described above.

We do not otherwise disclose your information, except where we are required to by law.

Why we use it

We use what you send us to:

• Read and reply to your enquiry
• Prepare a scope and quote if you ask for one
• Understand which of our own marketing brings in enquiries
• See which pages are read, so we know what is worth writing more of
• Prevent spam and abuse of the form

We do not add you to a marketing list because you sent an enquiry. If we ever start sending a newsletter, it will be something you opt into separately.

How long we keep it

We keep an enquiry for two years from the last time we were in touch with you about it. If it was spam, we delete it within ninety days. If you become a client, we keep it for as long as we are working together and for seven years afterwards, because those are business records we have to hold.

Conversations with the assistant are kept in full for twelve months. After that we strip out everything that points at you — what was said, and the one-way hash of your address — and keep only the bare shape of the exchange: when it happened, how many turns it ran, and whether one of our guardrails rewrote a reply before it was sent. We keep that stripped-down record for up to seven years, because it is what we would rely on if anyone ever told us the assistant had said something it should not have. Then it goes too.

The records we keep to stop the enquiry form and the AI crawler check being abused are deleted after thirty days.

A testimonial we published stays while it is on the site. If you ask us to take it down, we take it down, and thirty days later we erase what you wrote and your contact details — keeping only a dated note that a testimonial existed and was withdrawn, for six years, so we can show what happened if anyone ever asks. If you write one and we never publish it, it is deleted after twelve months, and so is an invitation nobody used.

Analytics is the exception to the paragraph below, because we do not hold it. Google keeps that data on its own systems, and deleting it is a request to them rather than something our nightly job can reach. The periods set on our property are two months for the individual events — the record that you viewed a particular page at a particular time — and fourteen months for the identifier that links several visits from one browser together. That fourteen months restarts each time the same browser comes back, so it measures time since your last visit rather than since your first. Google keeps the aggregate counts built from all this indefinitely; those are totals, with nothing in them that points at one person.

None of this depends on someone remembering. A job runs every night and applies these periods, and the periods themselves are held in the database rather than only written here, so this page and what actually happens cannot quietly drift apart.

You can ask us to delete your enquiry or a conversation sooner. See below.

Accessing, correcting and deleting your information

Email hello@amplifybot.io and you can ask us to:

• Tell you what personal information we hold about you
• Correct anything that is wrong or out of date
• Delete your enquiry, or a conversation with the assistant, and the information attached to it
• Take down a testimonial you gave us, for any reason or none

We will respond within thirty days, which is the timeframe the Australian Privacy Principles set. We may need to confirm who you are before acting on a request.

Security

The site is served over HTTPS and enquiry data is held in an access-controlled database. IP addresses are hashed rather than stored directly. No system is perfectly secure, and we cannot guarantee the security of information transmitted over the internet.

Complaints

If you are unhappy with how we have handled your personal information, contact us first at hello@amplifybot.io so we can try to resolve it.

If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.

Changes to this policy

If we change what we collect or how we use it, we will update this page and the date shown at the top. Material changes will be reflected here before they take effect.