Help & guides

Yes. An entry belongs to a person, so it needs somewhere to live. Signing up takes an email address, a name, a date of birth and a password.

You can browse events, read club pages and look at published results without an account. You need one to enter, to volunteer, to join a team, or to see your own photos.

You need to be at least 16 to hold an AnyRun account. That's in the Terms of Use, and the check runs on our servers, so it applies however you sign up.

A runner aged 16 or 17 enters with a parent or guardian's agreement to the waiver, collected on the entry form. Under-16s can't hold an account or enter. Age also decides age-group results where an event uses them.

Your running record on AnyRun: every race you've entered here, your results, and the distances behind them. It has a permanent passport number that is yours alone, for good.

It's also where the sharing studio lives: pick a card design, choose a photo, and export an image of a result to share. Locked designs unlock as you run more.

Because of what an account can reach. If you hold a role in an organisation, your sign-in can see other people's entry details, so that account is asked for a second factor.

Set it up in account settings with any authenticator app. Keep the recovery codes somewhere safe; they're the way back in if you lose the phone.

Find the event from events or an organiser's link, pick your distance, and follow the entry form. You'll confirm your details, accept the event's waiver, choose any add-ons, and pay.

Your entry is confirmed the moment payment succeeds. You'll see it on your account straight away and get an email confirmation.

The event's own waiver, which the organiser publishes and which you read on the entry form. We record which version you accepted and when, and you can re-read your accepted copy any time from the entry on your account.

Plus the Participant Terms for the platform side. The race is the organiser's; the platform is ours.

You pay one platform fee on the whole cart, with GST added to it, both itemised at checkout, and that total is what you're charged. Some organisers absorb it or split it. Whichever they've chosen, the cart shows you exactly where your money goes.

A runner account is free to hold. The entry price is the organiser's; the fee is ours.

Extras the organiser sells alongside the entry: a shirt, a meal, parking, a photo pack. You choose them in the same cart, and they appear on the same order.

Some are posted to you and some are collected on race day; the organiser says which, and their note appears with the item.

Where an event offers teams, you can create one and share a join code, or join one somebody sends you. Everyone still holds their entry and pays for it. A team only groups those entries together.

Team results are worked out from the members' individual results. You can see your teams from your account.

Big fields don't start at once. An organiser can split a distance into waves that set off a few minutes apart, so the start is safer and less congested.

Some events let you choose your wave when you enter, up to each wave's capacity. Others allocate waves later, usually by predicted finish time so people run with a similar pace.

It's on your race hub and on your entry. When an organiser allocates waves, you get a notification in the app and an email telling you your wave and when it starts. Times are shown in the event's own local time.

If a wave shows as full, it is full. You'll be offered one with room, and if you're already in that wave you keep your place.

Where the organiser allows it, yes. You start the transfer from your entry; the person receiving it accepts, fills in their details and accepts the waiver. A waiver signed by you doesn't bind them.

The organiser sets whether transfers are open and until when. If the option isn't there, they've closed it for that event.

The organiser's published refund policy governs, and you see it before you pay. Ask them through the event's contact details; refunds are approved and issued on their side.

The platform fee and its GST are not refundable, and an organiser's refund tools cannot return them. A refund returns the entry price: on a A$22.17 payment for a A$20.00 entry, A$20.00 comes back, and the A$1.97 fee and its A$0.20 GST stay with AnyRun. Your account shows these numbers before you confirm a withdrawal. If the organiser cancels the event, a refund request for the entry price opens for you, whatever the stated policy says, and the fee and its GST stay with AnyRun then too.

None of this displaces your rights under the Australian Consumer Law, which cannot be signed away.

Cancelling opens refund requests for every paid order on that event. You'll be told by email, and the platform pages the notice, so it reaches everyone however big the field is.

Results come from the event's timing. When the organiser publishes them they appear on the event's results page and on your account, and you're notified.

Photos are matched to you by reading the bib number in the picture. We do not use face recognition.

You can unmatch any photo from your own account. It stops being yours and stops appearing in your gallery. Photo controls live in account settings.

The photograph belongs to whoever took it and stays in the organiser's library; what you control is the link between it and you, and whether it can be featured publicly.

Only where you've opted in. The public start list is opt-in, and published results follow the event's own settings.

If you cancel or your entry is refunded, you drop off the public start list even if you'd opted in. Opting in to appear as a participant isn't permission to be listed as one when you aren't.

A card of a result or your passport, in a range of designs: pick a design, a photo (yours or one of the matched race shots), a shape for the platform you're posting to, and export it as an image.

Backgrounds you upload are private to you. Some designs unlock as you run more races.

From account settings, one button, and you get a machine-readable file straight away.

It covers your profile, every entry and result, orders with payments and refunds, volunteer shifts, the organisations and sponsor accounts you belong to, which photographs are matched to you and how the match was made, your notifications, the email we've sent you, your consents, and every legal document you've accepted with the version and date.

Your own details are editable in account settings. A result belongs to the event's timing. Ask the organiser to correct it, and it flows through to your account.

Ask from account settings. Each deletion is checked before it runs, because it is irreversible.

When it runs: your profile stops identifying you, your sign-in is removed, your photo matches and stored images go, your passport number is retired, and anything queued to be emailed to you is deleted so nothing arrives afterwards. What has to stay is the financial record the law requires us to keep, and results that are already part of an event's public record.

If you own an organisation you'll be asked to transfer or close it first. Otherwise the club is orphaned.

Marketing messages carry an unsubscribe link that works without signing in, and you can manage consent in account settings.

Service messages are separate and keep coming: your entry confirmation, wave placement, a refund, a race-week note, your results. Those are part of the transaction. You can't be entered in a race and opt out of being told about it.

From the console: give it a name, a web address and a type, choose who pays the platform fee, and accept the Organiser Agreement. That agreement is the working contract between us: fees, how entry money reaches you, refunds and chargebacks, and our respective responsibilities for your entrants' data.

Some organisation types (companies, councils, schools, charities) need a company email on their domain, so we can confirm you're entitled to act for them.

Five, and each one sees something different:

Owner: everything, including money, ownership and closing the organisation. Staff: day-to-day event running. Volunteer coordinator: roles, shifts and crew. Timer: results. Accountant: the finance hub and exports, and not your entrant lists: books without personal data.

Give the narrowest role that lets someone do their job. Your audit log records every role change.

You provide your ABN or ACN, and it's checked against the register's own checksum as you type, then confirmed. A verified organisation shows a credential on its public page.

A domain belongs to one organisation. An unverified claim on a domain reserves nothing. Otherwise anyone could block a real business by typing its address into a form.

Yes. Ownership transfer is a two-sided handshake: you offer it, and the person accepts. Nothing moves until both halves happen, and the whole thing is on the audit log.

The event builder walks you through sections: identity, banner, look, logistics, distances, and the rest. Every section shows you a preview of the real component, drawn from what you'll publish.

Your event stays private until you publish it. Draft events are visible to your team and to nobody else.

Yes. It copies the working parts (distances, waves, add-ons and settings) and shifts the dates, so you start from last year's event and edit it forward.

Entries, results and media stay with last year's event.

Add waves to a distance with their start times and capacities. Then choose how runners get into them: let them pick when they enter (capacity-limited, so a full wave is closed), or allocate later.

Allocation orders by predicted finish, fastest first. It's idempotent: run it twice and nobody moves twice. It also notifies every runner in the app and by email, quoting the start in the event's own local time.

Create the item, set a price and how many exist, and say whether it's posted or collected. Stock counts down as people buy, and you track fulfilment from the console.

Entries land in the console as they happen, with the money and the entrant's details together. You can search, filter and export, and correct what needs correcting.

Bibs are assigned per event and are guaranteed unique across it, including when one runner enters two distances of the same race. A bib is issued when an entry is paid, so a waitlisted entry doesn't have one yet.

When a distance is full, further entrants join its waitlist. Promoting someone re-opens their order at the current price and holds the spot for 48 hours while they pay. The entry is confirmed when they pay, and if the hold runs out they are charged nothing and keep their place in the queue. Capacity is re-checked at the moment of promotion; going over it is a second, separate step, and the audit log records that you did.

On race morning, the console's scan screen reads the code on a runner's race pass, or you type the bib. Tap once to check them in. It refuses a bib it doesn't know, an entry belonging to another organisation's event, a cancelled or refunded entry, and a bib presented beside somebody else's pass, naming which half disagreed. Tapping twice changes nothing, and every check-in is recorded against the person who made it. Owners, admins, staff and volunteer coordinators can check runners in.

Yes, and the two doors behave differently. A CSV uploaded in the console imports in one pass and then reports how many rows it added and how many it skipped. Through an integration token the file stages first: you get the counts of what would be created and what would be skipped, with sample rows, and nothing is written until you confirm the batch.

A bad row costs you only that row. Rows that pass are imported, and a row that fails is rejected with the line number and the edit that fixes it. Correct those lines and send the file again.

⚠ An imported list is personal information you collected, so your own privacy notice and lawful basis have to cover it. That responsibility is yours and the Organiser Agreement says so.

Cancelling opens refund requests on every paid order regardless of your stated policy, and notifies every entrant. The Australian Consumer Law reaches that outcome anyway for an event that doesn't happen, and the platform makes that path the automatic one.

You pay one platform fee per cart, published in dollars ex GST, with the GST on it itemised beside it for the participant at checkout. Setup, the monthly plan, a listing and an event that doesn't sell all cost A$0.

You choose the fee payer: the runner pays it on top (default), you absorb it, or you split it. Registered charities, schools and not-for-profits can ask for the community rate.

You pay one other cost beyond the per-cart fee: a A$29 ex GST payout-account authorisation, charged once when you connect your payout account and consented on the connect screen. It goes towards the Stripe Radar fraud monitoring applied to your account.

Entry money is your money. Payments are collected through our payment provider into your own connected account, and pay out to you on that provider's schedule. AnyRun is not a bank and does not hold your entry funds.

You'll onboard with the provider and meet its verification requirements before paid registrations can open. Because the money settles to you, you are the seller of the entry, which matters for receipts and GST below.

You're the seller of the entry, so the entry receipt is yours and carries your own ABN and GST treatment. If you're not GST-registered, there's no GST line, and there shouldn't be.

AnyRun invoices you separately for what you buy from us (the platform fee and any credits) with our own ABN on it. Your accountant owns the treatment of your entry prices; we show the totals and keep the records straight.

Refunds you approve are issued to your participants under your published policy, capped at the entry price. The per-cart platform fee and its GST stay with AnyRun, because the service the fee paid for was delivered at registration. That holds when you cancel the event too: your participants get the entry price back, and the fee and its GST are not part of it. Where AnyRun causes a refund, we make the order whole ourselves.

Chargebacks and disputes on your event are yours, and we may recover what we're charged as a result, except where the dispute was caused by a platform failure or our error. We can't underwrite events we don't run, and you shouldn't underwrite our mistakes.

Your sales, refunds, payouts and fees, with exports for your bookkeeping. The aggregates are sales figures. A purchase you make from us is an expense and is kept out of them, so your revenue isn't overstated.

From the comms rail in the console. You pick who it goes to, see the recipient count and the cost before you send, and the send is recorded.

500 participant emails per calendar month are included at no charge. Beyond that it's A$1.00 per 1,000 messages, metered monthly and shown on your usage page. In-app notifications are free, and you're billed only for messages that reach someone.

A service message is part of the transaction: entry confirmed, wave placed, results ready, race-week details, a refund. Everyone entered gets those.

A marketing message promotes something: next year's event, another race, a sponsor's offer. Those need consent and carry a working unsubscribe, and the platform enforces that: opting out of marketing keeps the service messages your race needs flowing.

⚠ Don't put promotion inside a service message. Under the Spam Act that turns the whole message into a commercial one, and it needs consent it doesn't have.

Create roles, then shifts under them with times, places and how many people you need. Volunteers sign up, and you see coverage at a glance and check people in on the day.

Mark the roles that involve minors as requiring a check. The platform tracks validity and expiry and shows your coordinators whether someone is covered. The underlying document details stay encrypted.

The legal obligation to apply the requirement is yours; the tracking is ours.

Create placements on your event with a tier, a location and a price, or open them to auction. Sponsors find them in the marketplace, and you approve the logo and creative before anything appears beside your event.

You keep the final say on what runs. If a sponsor breaches the content standards, the placement can be suspended.

Upload your event photography and the platform reads bib numbers to match shots to entrants. No face recognition. A runner can remove a match, and you control which images are featured publicly.

Upload race photos as JPEG, PNG or WebP. If your phone saves photos as HEIC, switch its camera format to "Most Compatible", or export the shots before you upload them.

You and your photographers confirm you hold the rights to upload the images and to have them shown as you've configured.

You have two meters, both visible on your usage page before you hit them. Storage: 10 GB for the organisation, shared by every event, with A$5 packs that lift it. A pack lasts one month; to keep the room, buy another before it lapses. Email: the 500/month above, then metered.

You get a warning before a pack lapses, and going over a meter keeps your files in place.

You are the controller: you decide what your event collects and why. We process it on your behalf to run the platform, and we're a controller for operating and securing the platform.

Where that line is unclear, whoever decided a piece of information would be collected, and why, is the controller of it. The full terms are in the Organiser Agreement: our instructions, sub-processors, breach notification within 72 hours, retention and what happens at the end.

Give them a privacy notice covering your part: what your event collects, why, and who you share it with. Ours covers the platform. Yours is especially important for imported past-entrant lists, where the lawful basis is yours to hold.

Parental or guardian consent is your responsibility, as is applying Working With Children requirements to roles involving minors.

⚠ AnyRun does not collect health or medical information, and you must not use event communications, uploads or any other field here to collect it. If your event genuinely needs a medical declaration, handle it on your own systems under your own privacy notice.

A per-organisation token that lets your own tools stage and import data programmatically. Tokens are stored hashed, are scoped to your organisation, and can be revoked at any time.

Imports through it are staged and diffed, and rate-limited per token. Terms are in the API Terms.

Open the event's volunteer page, pick a role that suits you and a shift that fits your day, and confirm. It appears under your account with the time and place.

You'll get a reminder before the day, and the organiser can send you crew information ahead of time.

Yes. Release it from your account and the next volunteer waiting is confirmed straight into it. Do it as early as you can: coverage is exactly what the coordinator is watching.

Yes. Your entry and your shift live in the same account, so you keep one login.

Check the times don't collide; the platform lets you book a shift that overlaps your own start.

When the role involves children. The organiser marks those roles, and you'll be asked to record your check before you're confirmed.

We store the reference encrypted and show coordinators only whether it's valid and when it expires. The document details stay private.

On the shift in your account: where to be, when, and who to find. If the organiser has published crew documents or a briefing pack, they're there too.

Check back the day before; organisers often add the last details late.

Create a sponsor account from your existing AnyRun account: same login, a second role. You provide your company name, a company email address, and your ABN or ACN.

You'll accept the Sponsor Terms and the Content Standards, which govern what may appear beside somebody's event.

Because the partner row beside an event has to mean something. The number is validated against the register's own checksum and confirmed before you can back or bid.

It also protects organisers: they can see who they're dealing with before their event carries your logo.

Browse the marketplace by event, audience and placement type. Some placements have a fixed price and you buy them outright; others run as an auction.

Buying puts a short hold on the slot while you check out, so it can't be sold from under you mid-payment. If the hold lapses, it returns to the market.

Place your maximum bid before the close. The auction settles at the closing time (you don't need to be watching) and the highest bid wins.

If you're outbid we tell you, and you can bid again while the auction is open.

You pay for the slot, then upload your creative. The organiser reviews it against their event and the content standards, and it goes live once approved.

Once the organiser approves the creative and the placement's window opens. Where it appears depends on what you bought: the event page, the results board, the start list and so on.

The organiser can ask for a change or decline creative that doesn't suit their event. Their race, their call.

You get aggregate figures for the placement: how many times the page carrying it was served, and how many people clicked through where your placement is clickable.

Participant personal information stays with the organiser. Sponsorship here buys visibility beside an event, and that is all it buys.

It keeps that club's events in front of you: new races and regular runs show up for you automatically.

Following is free. It doesn't enter you in anything and doesn't hand the club your details to market to; if they want to email you, that needs your consent like anyone else's.

Browse clubs and filter by where you are and what kind of running you're after. Each club page shows what it puts on, its regular runs and its upcoming events.

A club's recurring sessions: the Saturday morning 5k and its cousins. You find them on the club's page with the day, the time and the meeting place, and most are free to turn up to.

They're an open, standing invitation to turn up, so there's usually no entry to buy and no bib.

Only through something you opted into: a public start list for one of their events, or a run roster you chose to appear on.

You can withdraw that from your account, and it comes off the club's page too.

Yes. Events, clubs, event pages, course details and published results are all open.

You need an account to enter a race, volunteer, join a team, or see photos matched to you.

Go to the event's results page once the organiser has published. What you can see there is what the event has chosen to publish.

Some events show a full field and some show only the podium. That's the organiser's chosen setting, working as intended.

Because appearing publicly is opt-in for the runner and configurable for the event. Someone who hasn't opted in isn't listed. The absence is the setting working.