Cookie policy

A cookie is a small text file that a website asks your browser to store on your device. The next time you visit, your browser sends that file back, which lets the site recognise the browser you are using. A cookie does not know who you are. It knows that this browser has been here before, and whatever the site chose to write into it.

Other technologies do much the same job under different names, and this policy treats them all the same way:

• Local storage and session storage — space in your browser where a site can keep small pieces of information. We use local storage to remember your cookie choice.
• Pixels and tags — tiny images or short scripts placed on a page that quietly report a visit back to another company. This is how most advertising and analytics tracking actually works.
• Software development kits, or SDKs — code supplied by another company and built into a site or app, which can collect information as it runs.

There is also a distinction worth knowing. A first-party cookie is set by the site you are looking at — in this case swiftpaytoday.com. A third-party cookie is set by a different company whose code is running on the page, such as an analytics provider or an advertising platform. Third-party cookies are the ones that can follow you between websites.

No cookie on this site contains card details. This website does not process card payments and does not store cardholder data. Card transactions run on the PCI DSS certified platforms operated by our processing partners.

We would rather tell you the plain truth than perform a ritual. As at the date at the top of this page, swiftpaytoday.com sets what it needs to work, plus a record of the cookie choice you make. It can also load two optional third-party tags — Google Analytics 4, and the Meta (Facebook) pixel — but neither of them loads at all unless you have said yes to that particular category. If you decline, or if you simply have not answered yet, the script is never requested and no cookie from it is ever set. The typefaces are served from our own server rather than a font network, so there is no third-party call there.

The four categories described below are the framework we use. One of them — preferences — is currently empty. We describe it anyway, because the disclosure and the choice mechanism should exist before anything is added, not afterwards.

If we add anything further to the optional categories, we will update this page first, name what we have added, and it will not run until you have said yes.

These keep the site working and keep it safe. They do things like hold your place as you move between pages, help an enquiry form submit successfully, protect the forms against automated abuse, and keep the connection secure. They do not build a profile of you and they are not shared with advertisers.

The one named third party in this category is Cloudflare Turnstile, which protects the enquiry and referral forms from automated abuse. It runs on the two pages that carry a form, sets storage only for the length of the check, and is not used for analytics or advertising. It cannot be placed behind a consent choice: a bot would simply decline, and the form it defends would be the thing left unprotected.

The record of your own cookie decision belongs in this category too. If you tell us to load nothing optional, we have to remember that in order to honour it — which means storing one small item that says exactly that, and nothing else.

Strictly necessary cookies do not require your consent, in any of the countries we operate in. That is not a loophole. It is because the site cannot be delivered to you without them, and they are not used to learn anything about you beyond what is needed to serve the page you asked for. You can still block them in your browser settings, but if you do, parts of the site will stop working properly.

Preference cookies remember choices you have made so the site behaves the way you left it — for example a country or region you selected, a display setting, or a message you have already dismissed and do not want to see again.

They are not needed to make the site function. Without them the site still works; it simply forgets what you chose last time. Because they are not necessary, they only run if you agree to the optional categories.

At the moment the only thing of this sort we store is your cookie decision itself, and that sits in the strictly necessary category above, because we need it in order to respect the answer you gave us.

Analytics cookies count things. How many people visited, which pages they read, how they found the site, whether a page failed to load, how long a page took to appear. The purpose is to see patterns across a lot of visitors so the site can be made clearer and faster. It is not to identify you as an individual, and it is not to advertise to you.

Even so, analytics needs your consent here, and it stays switched off until you give it. We have chosen to treat analytics as optional everywhere, rather than only where the law demands it.

We use Google Analytics 4, provided by Google LLC in the United States, to understand which pages are useful and where people give up. It is off unless you turn it on. When you do, it sets cookies named _ga and _ga_<property> — the first lasts about two years, the second about two years — which give your browser a random identifier so a repeat visit is not counted as a new person. We have IP anonymisation switched on, and we have told Google not to use this data for advertising or ad personalisation. We do not upload your name, email or anything you typed into a form to Google. Choosing analytics does NOT switch on the advertising category below.

Marketing cookies are set by advertising platforms so they can recognise your browser on other websites, show you SwiftPay advertising there, and work out whether an advertisement led to an enquiry. They are the most intrusive category, because the whole mechanism depends on building a picture of your browsing across sites that have nothing to do with us.

They need your consent, and they get the strictest treatment we apply to anything on this site.

We use the Meta pixel, provided by Meta Platforms in the United States, to measure whether our advertising works. It is off unless you turn it on, and it is a separate question from analytics — accepting analytics never switches this on. When you turn it on, it loads a script from connect.facebook.net and sets a cookie named _fbp, which lasts about 90 days, and it tells Meta which page you looked at. Meta may match that against an account you hold with them. Under California law this counts as SHARING your personal information for cross-context behavioural advertising. We do not sell your personal information for money, and we do not knowingly sell or share the information of anyone under 16. You can turn this off at any time using the button on this page, and if your browser sends a Global Privacy Control signal we treat that as an instruction to leave it off without asking.

On your first visit a banner appears at the bottom of the screen. It offers Essential only and Accept all, presented with the same prominence and taking the same single click, plus a Choose individually control that lets you accept analytics without accepting advertising, or the other way round. Declining is never made harder than agreeing. Until you choose, nothing outside the strictly necessary category runs — the optional scripts are not merely inert, they are never requested.

Your decision is saved in your browser's local storage, which is how the banner knows not to interrupt you again on that browser.

You can change your mind at any time. Use the Change your cookie choices button on this page and the banner reopens with your previous answer cleared, so you can pick again. Withdrawing consent is exactly as easy as giving it, and takes effect immediately.

Two practical points. Your choice is stored per browser and per device, so a decision made on your laptop does not carry across to your phone. And if you clear your browsing data, you delete our record of that decision along with everything else, so the banner will appear again on your next visit.

Analytics and advertising are separate choices, and you can accept one and refuse the other — either from the banner's Choose individually control or from the cookie settings on this page at any time afterwards.

Cookies fall into two groups by lifespan.

• Session cookies exist only while you are on the site. Your browser deletes them when you close it. They are used for things that only matter during a single visit, such as holding your place between pages.
• Persistent cookies stay on your device after you close the browser, so the site can recognise that browser when you return. Every persistent cookie is given an expiry date at the moment it is created, and it is deleted automatically when that date passes.

Durations for the optional tags are named in the analytics and advertising sections above: _ga and _ga_<property> last about two years, and _fbp lasts about 90 days. Those are the providers' defaults and we do not shorten them. For everything we set ourselves, the principle is the shortest life that still does the job: the necessary items are short-lived or last only for the session. The record of your cookie decision is deliberately persistent — if it expired quickly, we would have to interrupt you with the banner all over again.

Third-party cookies, if we ever set any, have lifetimes decided by the third party rather than by us, and those are published in that company's own cookie or privacy policy. Whatever the expiry date says, you can delete any cookie yourself at any time through your browser.

When another company's code runs on a web page — an analytics provider, an advertising platform, an embedded video or map, a live chat widget — that company sets its own cookies, under its own name, governed by its own policy. We cannot read those cookies and we cannot control how long they last or what the company does with what it learns. This is true of every website, not just ours.

The only third-party cookies this site can set are the Google Analytics and Meta pixel cookies named above, and only after you have agreed to that category. Links to our partners take you to their own websites: once you leave swiftpaytoday.com, their cookie policies apply and this one does not. That includes Clover, which is a Fiserv product, and Nuvei.

Enquiry and quote forms are delivered to our inbox through a third-party message delivery service. It carries your message to us. It is not an advertising service and it is not used to profile you.

Before we add any third-party technology to this site we check what it collects, what the provider's own terms permit it to do with that information, and which countries it sends it to. Anything we do add goes only on the pages that genuinely need it, rather than across the whole site by default.

Separately from the banner on this site, your browser gives you direct control over cookies. Those settings apply to every website you visit, not only this one, and they will override anything you have chosen here.

• Google Chrome — open Settings, then Privacy and security, where you can block or delete cookies and manage them site by site.
• Apple Safari — open Settings or Preferences, then Privacy, to block cookies, manage stored website data, and use tracking prevention.
• Mozilla Firefox — open Settings, then Privacy and Security, to choose a tracking protection level and clear cookies and site data.
• Microsoft Edge — open Settings, then Cookies and site permissions, to block, allow or delete cookies.
• On a phone or tablet, the same controls sit inside the browser app's own settings, usually under Privacy.

Two things worth knowing before you change these. Blocking all cookies will break parts of most modern websites, including this one, because the strictly necessary ones are how a site keeps track of what you are doing. And clearing your cookies and site data deletes our record of your cookie choice along with everything else, so you will be asked again next time you visit.

A private or incognito window discards cookies when you close it. That means your cookie choice will not be remembered either, and the banner will appear on each new private session.

Global Privacy Control, usually shortened to GPC, is a setting available in some browsers and through browser extensions. When you switch it on, your browser sends an automatic signal to every site you visit saying you do not want your personal information sold or shared for advertising. Several US states require businesses covered by their privacy laws to treat that signal as a valid opt-out.

We honour it. If your browser sends GPC when you arrive, we record a decision to decline the optional categories straight away and we do not show you the banner at all — you have already told us what you want, and asking again would defeat the point of the signal. If you would rather change that answer, you can still open the choices from this page and do so.

Do Not Track, or DNT, is an older browser signal with a similar aim. No common standard was ever agreed for how a website should respond to it, and most sites ignore it; in practice it has been overtaken by GPC. We do not currently respond to Do Not Track signals. In any event this site does not track you across other websites, so there is nothing for that signal to switch off here.

SwiftPay sells in three countries from one website, and each of them answers the cookie question differently. Here is the short version, because it explains why you saw a banner at all.

• Australia has no cookie-specific law and no legal requirement to display a consent banner. The Privacy Act 1988 and the Australian Privacy Principles apply where cookies collect personal information, and the main duty is to tell people at or before the point of collection. The Office of the Australian Information Commissioner has been tightening its position on tracking pixels, and now expects consent that is express, informed and specific where tracking is used for targeted advertising.
• The United States has no federal cookie law, and the state privacy laws generally work on an opt-out model rather than an opt-in one. California is the strictest: letting an advertising platform set cookies on its site counts as sharing personal information, residents can opt out of that, and businesses covered by the law must honour the Global Privacy Control signal automatically. Around a dozen states now require that signal to be recognised. Most state laws also exclude people acting for their business rather than personally — which describes most people who enquire with us.
• Canada requires meaningful consent under PIPEDA. Clear notice and a working opt-out can be enough for ordinary analytics, but tracking and profiling are expected to be opt-in. Quebec's Law 25 goes furthest of the three countries: any technology that can identify, locate or profile a visitor must be switched off by default, you must be told it is in use, and you must be given a way to turn it off.

We could detect where each visitor is and show three different banners. That approach is fragile and gets the edge cases wrong, and the people it gets wrong are the ones with the least protection. So we apply the strictest standard to everyone instead: nothing beyond the strictly necessary runs until you say yes, wherever in the world you are reading this. That is why you saw a banner even if the law where you live would not have required one.

We update this page whenever what we do changes, and if we add anything in the optional categories we update it before the change goes live rather than after. The date at the top tells you when it was last revised: 16 August 2026.

If you have a question about cookies, or you want to make a request about any personal information we hold, email support@swiftpaytoday.com. You can also call +61 466 230 370 in Australia, or +1 404 910 8918 in the United States and Canada, or write to us at 5 Charles Smith Avenue, Bungarribee, New South Wales 2767, Australia. Please raise it with us first — we would like the chance to put it right.

If you are not satisfied with our answer, you can take it further. In Australia, to the Office of the Australian Information Commissioner. In Canada, to the Office of the Privacy Commissioner of Canada, or to the Commission d'accès à l'information du Québec if you are in Quebec. In the United States, to your state attorney general, and in California also to the California Privacy Protection Agency.

This page deals only with cookies and similar technologies. For everything else — what we collect through our forms, who we share it with, how long we keep it and the rights you have over it — see our privacy policy and our terms of use.