Legal

Cookie policy

We set no tracking cookies and run no analytics. A plain visit to this website sets nothing at all.

Last updated: 22 October 2026

This is a short policy because there is very little to describe. We do not advertise, we do not profile visitors, and we do not measure you. Most of what a cookie policy usually has to explain does not apply here.

What a plain visit sets

Nothing. You can read every page on this website — the product pages, the pricing, the documentation, the glossary — without a single cookie being set, and without a single request leaving for anyone else’s server. There are no third-party scripts on these pages.

That is why you are not being asked to accept anything. A consent banner is required when a site sets cookies that are not strictly necessary. We do not set any, so there is nothing to ask you about, and we would rather not interrupt you to say so.

What we do not use

No analytics. No Google Analytics, and nothing in its place. We do not know how many people read this page.
No advertising or retargeting pixels. Nothing from an ad network, and nothing that follows you to another website.
No social media trackers. No embedded like buttons, feeds or share widgets that report back.
No chat widget. No live-chat script sitting on every page watching for something to do.
No session recording or heatmaps. Nobody is watching a replay of your mouse.
No fingerprinting. We do not identify your browser or device by any other means instead of cookies.

The cookies we do set, and when

Three things can cause a cookie to be set, and all three are the result of something you chose to do. These are strictly necessary — the site cannot do what you asked without them — so they do not require your consent.

If you put something in your order. Our shop remembers what is in your basket while you move between pages and check out. Without this, the basket would empty itself on every click.
If you log in to an account. WordPress sets cookies that keep you logged in and protect the forms you submit while you are. These are how the site knows it is still you on the next page.
If you submit a form. A security token is used to confirm the form came from this website rather than being forged elsewhere. We also count repeat submissions from the same connection to limit spam, using a one-way scrambled version of the IP address held for ten minutes — this is not a cookie and does not identify you.

Our payment provider

Payment is taken by Razorpay on its own secure payment screen. Razorpay may set its own cookies there to take and secure the payment and to prevent fraud. That screen is theirs, not ours, and your card details never reach this website. Razorpay publishes its own privacy and cookie information, which governs what happens on that screen.

Managing cookies

Every browser lets you see the cookies a site has set, delete them, and block them in future. Look for “cookies” or “site data” in your browser’s privacy settings.

Because we set nothing on a plain visit, blocking cookies costs you nothing while you are reading. It will stop you ordering or logging in, because the basket and the login need them to work at all.

The plugin, on your own website

This policy covers this website. W3Bullhorn running on your own site is yours, and its cookie behaviour is covered by your policy, not ours. Worth knowing for that: the plugin sets no tracking cookies and includes no analytics or third-party scripts of its own, so it does not add anything to your site that you would have to disclose or ask consent for. If you record where an applicant came from, that is a feature you switch on deliberately and describe in your own policy.

Changes to this policy

If we ever add something that sets a cookie which is not strictly necessary, we will ask for your consent before it runs, and update the date at the top.

Contact us

Questions about this policy: hi@bullhornforwordpress.com. How we handle personal information generally is in our privacy policy.