Returns and Refunds Policy
Tickets for Attending or Supporting Memberships are sold as non-refundable - this includes supporting memberships in the process of being upgraded to attending memberships using the installment plan.
NOTE: There is a temporary exception to the 'no refunds' rule due the convention being postponed to 2022. Please see the membership page for more information.
If you have purchased an attending membership, and then are unable to attend, you may sell your ticket on to a new member for the same amount paid. See the on-sale of tickets policy for more information.
Supporting Memberships are not able to be sold on. A supporting membership must be upgraded to an attending membership by the original ticket holder before being sold on, as per the process described in the link above.
Tickets for the Gala Dinner, and any pre- or post-convention group activities, are sold as non-refundable. However, in the case that these events are sold out, you may sell your ticket on to another attending member for the same amount paid, via a waiting list maintained by the committee. See the on-sale of tickets policy for more details.
We do not offer refunds if you change your mind, and we are unable to swap sizes for clothing items, so please choose carefully.
If a product is damaged when you receive it, then we will do our best to replace it, but please provide a valid email address and phone number with your query so we can contact you if an exact replacement is not available. In the event that we cannot provide an acceptable replacement, you will receive a full refund.
Please contact us and explain the problem within 30 days of receiving the item. We reserve the right to ask you to email photographs showing the damage before the matter can be resolved. If we ask you to post the item back to us, we will refund you for the postage. Please do not send the item back unless we request this. Returned or exchanged products must be in the condition you received them.
If you buy the item while attending the convention, please bring it into Ops - we may be able to resolve the issue then and there!
Last updated: 21st November 2020