
Registration Pages
Part of Lead capture at business events
Handling contact-sharing permissions with partners
Set clear purposes, attendee choices and export controls before sharing business event contacts with a partner.
undefined
Before registration or partner promotion starts, agree which organisations may receive identifiable attendee details, for what purpose and on what basis. For organisations to which the Australian Privacy Principles apply, the Privacy Act 1988 sets the privacy framework, and the OAIC publishes guidance on the APPs (OAIC). Labelling a sponsor an 'event partner' does not give it the organiser's contact list. People can register without expecting separate businesses to contact them later.
Map the handovers
List every organisation that will collect, see or receive a record. Distinguish a service provider acting under the organiser's direction from a partner using details for its own sales or marketing.
Ask who controls the record, who decides the message and whether the recipient can use the details for another purpose. The contract label alone does not settle the legal treatment of a transfer.
For an organiser covered by the Australian Privacy Principles, sharing identifiable information with another entity may be a disclosure. APP 6 generally limits use or disclosure for a secondary purpose unless consent or another exception applies. APP 7 is the direct-marketing rule: an organisation must not use or disclose personal information it holds for direct marketing unless an exception applies (OAIC).
APP 5 requires reasonable steps to make people aware of collection matters, including the organisation's identity and contact details, the purposes of collection, usual disclosures and likely overseas recipients where relevant (OAIC). Which provisions apply depends on the arrangement and the proposed contact channel.
Give the attendee a specific choice
If a sponsor wants to contact attendees with its own offers, name the sponsor and describe the proposed contact before asking for a choice. Keep that choice separate from registration, event logistics and organiser contact, and make declining it possible without preventing registration. A statement that details 'may be shared with partners' may leave people unable to tell who will contact them or why.
For example: 'I agree that [organiser] may share my name and email address with [partner name] so it can send me marketing about [products or services].' Provide an unticked box labelled 'Yes, I agree'. Use wording that accurately identifies the details, partner and proposed messages, and give attendees a clear way to decline.
Record the selection, when and where it was made, the notice shown at the time, the named partner, the purpose and the fields covered. Set a documented retention period for permission records and a deadline for passing opt-outs to the partner; specify how expired records will be deleted or de-identified.
If a person declines that sharing choice, exclude their record from the corresponding export. A partner can promote the event to its own permitted audience without receiving the organiser's attendee list.
If a partner promotes the event to its own contacts, check its sending process and the event facts supplied. Do not treat that activity as permission to receive attendee details.
For an organiser's co-branded message, identify the sender and assess the message and permission. Record whether the organiser or partner will send it.
Before giving attendee details to a partner, check the disclosure basis and notice, confirm the recipient and exact fields. Limit the export to records matching the recorded choice.
If a partner markets to attendees itself, check the partner's contact basis and message obligations. Check the proposed contact channel before any transfer or campaign.
For partner emails, SMS and phone calls, check which contact-channel rules apply, including whether the Spam Act 2003 or Do Not Call Register Act 2006 applies. APP 7 does not apply to the extent those Acts or other prescribed legislation apply (OAIC). Where APP 7 applies, an organisation must allow a request not to receive direct marketing and provide a simple opt-out, such as replying 'unsubscribe' to an email, 'STOP' to a text or verbally during a call (OAIC).
Key steps for handling contact-sharing permissions with partners
- Name the sponsor and describe the proposed contact before asking for consentRequired for transparency under APP 5
- Use a clear, unticked checkbox labelled 'Yes, I agree'Separate from registration and logistics
- Record the selection, date, notice shown, partner name, purpose and fields coveredFor audit and compliance purposes
- Set a documented retention period and deletion deadline for permission recordsTo align with privacy best practice
- Exclude declined records from export to the partnerEnsures compliance with opt-out rights
Control the export and what follows
Before sharing, agree which records qualify, which fields are needed and who may access them. Set out how corrections and opt-outs will be passed on, including a named contact, a deadline and confirmation that the partner has updated its records. Record when the partner must delete or de-identify information it no longer needs.
Set out third-party handling in the commercial arrangements. If the partner is overseas, APP 8.1 requires an APP entity to take reasonable steps to ensure the overseas recipient does not breach the APPs, other than APP 1; the Australian entity is accountable for an overseas recipient's act or practice that would breach the APPs (OAIC).
Do not transfer records where permission is missing or ambiguous until the responsible team has checked the arrangement. If a disclosure is mishandled, stop further transfers, ask the partner to restrict or delete the copy, document what happened and escalate it through the organiser's privacy incident process.



