Voting and entry platforms used in Australia: what their terms say
Voting platforms in Australia are, for most public contests, hosted entry tools such as Gleam and Woobox, and their terms decide what counts as one entry. Legendary Prizes states in its privacy policy that all of its competitions run through the Gleam.io website. The agency Feed reports using Gleam for a number of its clients, and the BAFANG Giveaway Trail Stage 3 hands its entry form to Woobox to process and store the data entrants submit. These tools decide, mechanically, what counts as one entry and what happens to a second one. The rules are not invented per contest; they sit in the platform's published terms and in the data the platform records on every voter. This page reads those terms, names what the tools log, and separates what the platform controls from what the organiser decides.
Fact check dated 8 October 2026.
Which entry tools Australian organisers actually run
Start with the structures that are documented. Legendary Prizes, which operates prize competitions for an Australian audience, publishes a privacy policy stating that all of its competitions are run through the Gleam.io website. That single sentence tells you the shape of the arrangement: the operator owns the prize and the rules, and a hosted platform owns the entry form, the counter and the voter record. The operator never counts votes by hand.
The same shape appears on the agency side. Feed, an Australian digital agency, says it uses Gleam for a number of its clients when it runs social competitions for them. So the platform sits behind the brand whether the organiser is a prize company running its own giveaways or an agency running a promotion for a client. A voter sees the brand; the entry mechanics underneath belong to the tool.
The third documented structure is the giveaway that routes its form elsewhere. The BAFANG Giveaway Trail Stage 3 states plainly that its competition entry form uses the third party Woobox to process and store data. Notice the verb: store. The tool is not a voting widget bolted onto a page; it holds the entries, which is why its terms, not the organiser's marketing copy, are the operative document for anything about voter data and repeat entries.
- Legendary Prizes, an Australian prize operator, states in its privacy policy that all of its competitions are run through the Gleam.io website.
- Feed, a digital agency, reports using Gleam for a number of its clients when it runs social competitions on their behalf.
- The BAFANG Giveaway Trail Stage 3 processes its entry-form data through the third-party tool Woobox.
What the terms do with duplicate entries
A duplicate entry is a data question before it is a rule question. Because the form is hosted by the tool, the tool receives every submission the same way and can compare it against what it already holds: the same email address, the same login, the same profile the voter used last time. Whether a second submission is merged, ignored or listed separately is written in the platform's terms, and that is where any reader should look first.
This is the practical difference between a hosted platform and a homemade poll. A homemade counter records whatever arrives. A hosted entry tool records what arrives together with the identifiers attached to it, because the tool's own terms require an entry to belong to a person. When Legendary Prizes routes every competition through Gleam, the reason a second entry from the same account does not simply add a second vote is mechanical, not clerical.
Read the organiser's page and the platform's terms as two layers. The organiser layer says who may enter, when the vote closes and what the prize is. The platform layer says what one entry is, how the tool identifies a voter and what happens to a repeated attempt. The BAFANG notice about Woobox processing and storing data is the platform layer speaking; the same distinction holds wherever the form is hosted.
- Duplicate-vote rules live in the platform's terms, and every entry passes through a form that those terms govern.
- A hosted counter makes one entry per person a mechanical fact, not a promise the organiser has to enforce by hand.
- Where the form stores the data, the platform's published rules are the operative document for repeat entries.
What the tool logs about each voter
An entry form cannot accept a submission for free. To create an entry the tool needs at least one identifier that distinguishes this voter from the next: an email address, an account with the platform, a social profile it asks the voter to connect. Those identifiers are what the tool stores, which is exactly why the BAFANG entry form hands its data to Woobox for processing and storage rather than keeping it on the organiser's own page.
From the identifiers follows the log. Every accepted entry has a time, a source and the identifier that authorised it; every rejected or merged duplicate has the same. This record is what an organiser inspects when a vote total looks strange and what a platform's own moderation relies on. It is also what the platform's privacy terms describe, because the stored data is personal data about the people who entered.
What this means for a voter is concrete. The vote you cast is not an anonymous click in a crowd; it is a stored entry tied to the identifier you submitted. The vote the organiser publishes at the end is a count of those stored entries. And the reason a suspicious pattern is visible at all is that the same stored entries let the tool or the organiser compare one submission against every other submission it has already accepted.
- Because the form stores its own data, the entry log is the platform's record, and the organiser queries it.
- Every entry carries the identifiers the tool needed to accept it: an account, an address, a submission time.
- The log is why a published limit is enforceable; the tool sees the second attempt arrive under the same identifiers.
What the platform controls and what the organiser decides
Split the responsibilities cleanly. The platform, Gleam or Woobox as the case may be, owns the mechanics: it receives submissions, attaches identifiers, applies its own duplicate rules and keeps the store of entries. The organiser owns everything the mechanics do not decide: eligibility, the voting window, the prize and the decision to publish a count. Legendary Prizes runs its competitions through Gleam, yet the prize and the conditions of entry remain Legendary Prizes' own.
The split matters when something goes wrong. If a vote total moves in a way nobody expected, the first place to look is the platform's log, because that is where repeat attempts under the same identifier are visible. If the pattern holds, the organiser holds the published rules and can act on them: exclude entries, reopen a vote or state how the result was reached. Neither layer does the other's job.
And the split sets the honest limit of this page. A hosted platform with stored entries and published terms is a record, and a record invites inspection; that is all it is. Nothing in the mechanics decides the winner on its own, and nothing in the terms relieves an organiser of reading what was recorded. Feed's clients get Gleam's mechanics; the campaign judgement stays with the campaign. Keep the two apart in your head and the tools become legible.
- The platform owns the mechanics: the form, the identifiers, the counter and the record of each entry.
- The organiser owns the rules around the mechanics: who may enter, what the prize is and when voting closes.
- A hosted tool gives the organiser a log to read, not a guarantee; reading the log is a decision someone makes.
Legal position
This page documents the hosted tools behind Australian public votes and the terms those tools publish. It explains what an entry platform records, how duplicate entries are handled by the mechanics, and what an organiser sees in the log. It does not rank vendors, it does not quote prices, and it does not advise anyone on how to submit extra entries past a published limit.
What we leave out
This page does not rank vendors, does not quote prices, and does not sell or buy votes for any contest; prices belong in a direct answer to a request, never on a reference page. It does not explain how to submit extra entries, automate submissions, mask an identifier or get past any platform's duplicate rules, and it never promises that an organiser will fail to notice anything. It stays out of electoral voting entirely, and out of paid surveys and television talent shows. Where the record ends, this page says so instead of guessing.
Frequently raised
The documented ones are Gleam and Woobox. Legendary Prizes, an Australian prize operator, publishes in its privacy policy that all of its competitions run through the Gleam.io website, which makes Gleam the entry platform for the whole Legendary Prizes programme. Feed, a digital agency, states that it uses Gleam for a number of its clients, so the same platform sits behind campaigns run on behalf of client brands. On the giveaway side, the BAFANG Giveaway Trail Stage 3 names Woobox as the third party that processes and stores its competition entry-form data. The pattern across all three is the same: the organiser names the prize and the conditions, and a hosted tool owns the form, the counter and the voter record. Where a specific Australian contest names its platform, that name appears in its own entry terms or privacy notice, and that is the first document to read.
The terms govern this through the mechanics of the entry. Because the form is hosted by the tool, every submission arrives with the identifier that authorised it, such as an account or an email address, and the tool can compare a new submission against the entries it already holds. What happens to the comparison is written in the platform's terms: a repeat attempt is merged into one entry, ignored, or flagged for the organiser. The operative rule is the platform's, not the organiser's marketing copy, which is why the terms matter more than the prize page. Where the tool also stores the data, as the BAFANG entry form does with Woobox, the stored record is what makes the duplicate visible at all. An organiser publishing a one-entry-per-person rule on a hosted platform is describing a limit the mechanics enforce, and the platform's own terms are where that enforcement is spelled out.
Contest platforms identify voters, and identification is the word to hold onto. A hosted entry form cannot accept a submission without at least one identifier that separates this voter from the next: an email address, an account with the platform, or a social profile the voter connects. That identifier is verified in the sense that the tool checks it exists and belongs to the person submitting, and it is stored, which is exactly why an organiser such as Legendary Prizes routes everything through Gleam and why BAFANG says Woobox processes and stores its entry data. Full identity verification, in the sense of confirming who a person is offline, is not what these tools claim to do; they confirm the identifier and record everything attached to it. The practical consequence for a reader is this: the entry is tied to the identifier you gave, the tool holds that record, and anything the organiser later checks is checked against it.
Through the log, and the log is the honest centre of this answer. Every accepted entry carries a time, a source and the identifier that authorised it; every repeat or failed attempt leaves the same kind of trace. When a vote total looks wrong, the tool's stored record is what makes the pattern visible, because the same identifiers let the platform or the organiser compare one submission against all the others it has accepted. Platforms publish their own rules against automated or duplicated entries in their terms, and an organiser holds a second layer of published rules on top: eligibility, closing time, and the decision to exclude entries or restate a result. What the tools do not offer is a promise that nothing untoward ever arrives; they offer a record thorough enough that unusual patterns leave evidence. That is the difference between a hosted platform and an anonymous click counter, and it is the only protection that actually exists.
Publication is an organiser's decision, and the platform's job is to make the count available. A hosted entry tool produces an exact count of stored entries, because that count is the direct output of the record it keeps; whether the running number is displayed on the public page, shown only at the close, or published as a final result is set by the organiser in the campaign settings. Look at the three documented structures: Legendary Prizes routes its competitions through Gleam, Feed runs Gleam campaigns for clients, and BAFANG stores its entry data with Woobox, and in none of these does the platform itself decide what the public sees. The organiser's entry terms usually say when and how results appear. If a count is published, it is a count of the stored entries after the platform's duplicate rules have been applied; if it is not published, the tool still holds the number, and the organiser can state the result whenever its own rules say to.
Entry platforms log what they needed in order to accept the entry, and the storage is explicit. The BAFANG Giveaway Trail Stage 3 says its entry form uses the third party Woobox to process and store data, and that wording is the key: the tool holds the submissions, it does not merely count them. What it holds is the identifier that authorised the entry, an email address or a connected account, together with the submission time and whatever the entry form asked for. Because these records are personal data, the platform's privacy terms describe them, and an operator like Legendary Prizes states in its own privacy policy that its competitions run through Gleam, which tells an entrant exactly where the record of their entry lives. For the voter this means the entry is retrievable, attributable and auditable: the organiser can query it, the platform can compare it against other entries, and the stored copy is the single record the final count is drawn from.