About this policy
Engage is Fusion Party Australia's member participation and governance platform. Anyone can read public proposals and published policy. Signed-in members can discuss proposals, suggest wording changes, vote in ballots they are eligible for, and take part in branch activity.
This policy explains what personal information Engage handles, why we handle it, who can see it, how long we keep it and how you can ask about it. It applies to Engage at engage.fusionparty.org.au and to member accounts on Engage.
Engage is operated by FUSION POLITICAL PARTY INCORPORATED (ABN 20 845 177 664). Fusion Party Australia is the public name used in Engage. The party is currently registered with the Australian Electoral Commission as "votefusion.org for big ideas" (registered abbreviation "votefusion.org"). We have written this policy with reference to the Australian Privacy Principles (APPs) as a matter of good practice. Registered political parties are generally exempt from the Privacy Act 1988 (Cth) in relation to political acts and practices, and the Office of the Australian Information Commissioner (OAIC) describes registered political parties as exempt. Whether the Act applies to a particular activity is a legal question for Fusion to confirm. This policy is not a statement that the Act applies, and it is not legal advice.
This policy does not cover Fusion's main website, membership database, mailing lists or third-party websites. Fusion's existing website privacy policy describes the main website and older third-party services; it does not describe Engage. Those services may have separate privacy notices. If there is a conflict, the notice for the relevant service applies to that service.
Engage is not a confidential channel
Public proposals, comments, display names and aggregate vote counts can be read by anyone who can see that proposal. Do not use Engage for private, confidential or sensitive communications that you do not want published.
Information we collect
Account and membership information
When you sign in, we create or update an Engage account. We collect:
- your full name, as entered at sign-in or in your account;
- your email address and whether it has been verified;
- a member identifier and account timestamps;
- your platform role (member, moderator or administrator), membership status (pending, verified or suspended) and whether your account is disabled;
- branch memberships, branch administrator delegations, and who assigned or revoked them;
- if you register a passkey, your WebAuthn credential identifier, public key, signature counter, authenticator device type, backup status, transport hints and optional device label (Engage never receives your biometric data);
- if you use Google sign-in, the account identifier and profile information Google returns, such as name, email address, email-verification status and profile image.
Engage does not use a password for the sign-in methods configured in this release (email sign-in links, WebAuthn passkeys and Google sign-in).
Authentication and security information
When you request an email sign-in link, we process your email address and a single-use token. The token is stored in hashed form, expires after 10 minutes and can be used once. When you register or sign in with a passkey, Engage verifies a cryptographic WebAuthn challenge against the public key stored for your account. When you are signed in, Better Auth, the authentication library used by Engage, creates a session record. Session records may include a session identifier, the associated account, expiry time, IP address and browser user-agent. We also keep rate-limiting and security records to prevent abuse.
If you use Google sign-in, Google may return authentication tokens and account-linkage data that Better Auth stores to maintain the connection. Google handles your Google account under its own privacy policy.
Membership verification and branches
Fusion membership may be checked by an administrator or through the Underground CRM connection when it is enabled. Engage uses membership and geographic information from that connection to assess verification and branch assignment; records that cannot be resolved automatically need a manual check. Verified members can manage their branch memberships and following preferences within Engage’s eligibility rules. Authorised administrators can also manage branch records and delegated access.
Participation records
When you participate, we store the content you submit and information needed to attribute and audit it:
- proposals: title, summary, outcomes, details, supporting links or attachments, topic, stage, originating branch, governance authority, jurisdiction, publication scope, your display name and member identifier, timestamps, and each saved wording revision;
- contributions: your display name, stance, text, timestamp and endorsements. An endorsement is stored as a member identifier; the public page shows only the number of endorsements;
- formal amendments: the proposed wording, the revision it is based on, the exact block quoted by each suggestion, your member identifier, timestamps, status, revision history, any conflict flag and any administrative reason;
- Sense Box priorities: the priority title, details, optional suburb or town, topic, selected branch, submission time, consent version and whether you consented to review-then-publication. The form does not ask for your name, email address or account identifier. A priority is private to authorised reviewers until one of them explicitly publishes it. A published priority and its public discussion can be read by anyone, including people who are not signed in. Reviewer notes are never public. Priorities collected under an earlier private-review promise remain private and cannot be published without a new consent or a separate republishing process. The confirmation screen gives you a private status link containing the priority’s random identifier; anyone with that link can see the title and review status, but not reviewer notes, contact details or account data.
- votes: the ballot and proposal, the exact wording revision, your choice, an optional reason of up to 500 characters, your display name, your member identifier and the time you voted or last changed your vote;
- ballot administration: recorded outcomes, decision event references, binding events, ratification records and publication events.
Your display name is recorded with each contribution, proposal and vote at the time you submit it. Changing your account name later does not rewrite those historical records.
Administrative and audit records
Engage records some administrative actions, including role and membership changes, branch membership changes, branch creation and edits, ballot wording binding, ballot results, ratification and publication. These records include the actor's member identifier, the action, the time and, for some branch changes, before-and-after snapshots. Not every administrative action produces a complete immutable audit event. We also keep a record when a member accepts the current Terms of Use and acknowledges the current Privacy Policy, including the versions, content hashes and time of acceptance.
Story and photograph contributions
You can send a story, photographs, or both to a public invitation without an account and without being a party member. We collect what you write, the photographs and caption you attach, the name you ask us to use, any email address you give us so we can reply, and the permissions you choose for publication channels, credit, ordinary editing and AI-assisted editing. We ask you to confirm that you are 18 or over; we do not collect dates of birth or identity documents. We do not publish photographs that show identifiable children. After you send, we give you a private management link. Its code is stored only as a hash, and it lets you correct your words, remove your story from the gallery or withdraw it without an account. If you are signed in, you may optionally link the contribution to your account. We then record your member identifier, the time and the consent version. Linking does not change publication, approval or who may manage the contribution, and you can unlink it from the same page. We record the version of the consent you accepted and the time. If a reviewer approves the material, we also record the decision, the actor, the time, and where approved material is used. Photographs are stripped of location, device and other metadata before they are stored.
Aggregate interest counts
For each public invitation we count four events: the page being opened, the first interaction with the form, a contribution being accepted, and the optional account step being opened. A record contains only the invitation, a UTC date, the event type and a count. We do not record a cookie, session, IP address, account identifier or anything typed, and the counts cannot be linked to a person. Counts are kept for about 13 months, then deleted. An editor sees the totals and conversion percentages for the last 30 days.
Technical and operational information
Our servers and hosting infrastructure may record technical information such as IP address, browser user-agent, requested URL, timestamp, response status and error details. These logs support security, troubleshooting and service operation. The application database is self-hosted on infrastructure operated for Fusion and is not exposed directly to the public.
What we do not collect in this release
Engage uses Fusion-hosted Plausible Analytics to understand aggregate navigation and feature usage. It does not use advertising trackers or advertising cookies, process payment card details, or build advertising or marketing profiles. It does not ask for your date of birth, home address, phone number, health information or biometric data.
Political and sensitive information
Much of the information in Engage is sensitive information under Australian privacy law. This includes information about your membership of a political party, your political opinions, how you vote and what you say about policy. It can also reveal your branch or electorate.
We collect this information because you choose to sign in and participate, and because it is necessary to run a member participation and governance platform. We do not use it for advertising or sell it.
Some of this information is public. Your display name appears with your contributions and on proposals you author. Your comments, stance and the proposals you author can be read by anyone who can see that proposal. Aggregate vote counts are public. In a small ballot, the aggregate result can effectively reveal how a small number of voters voted, even though the application does not display individual names.
Your individual vote and optional reason are not displayed publicly. They are available to you in My Engage, to national administrators and to people granted the national permission to view identifiable ballot records. National administrators can identify how you voted, including your member identifier, display name, choice and reason. Branch administration or moderation alone does not grant identifiable-ballot access. We do not describe voting as anonymous or secret.
Identifiable ballot records
National administrators can access identifiable ballot records, including member identifiers, display names, choices and optional reasons. Do not vote or write a reason on the assumption that your choice is anonymous.
By choosing to sign in and participate, you are asking Fusion to handle this information for the purposes described in this policy. You can choose not to provide it, but you may then be unable to participate. If public attribution creates a safety or privacy risk for you, contact us at [email protected] before you post to discuss whether any alternative attribution arrangement is available while preserving membership verification.
Why we use information
We use personal information to:
- authenticate you and keep your account secure;
- verify your membership and branch eligibility;
- let you browse, discuss, propose, amend and vote in the ways your account permits;
- administer ballots, record outcomes and maintain the integrity of the exact wording voted on;
- maintain governance, ratification, publication and audit records;
- review story and photograph contributions and use approved material only within the permissions the contributor chose;
- operate, troubleshoot, secure and improve the reliability of Engage;
- respond to your requests, complaints and privacy enquiries;
- comply with legal obligations and lawful requests.
We do not sell, rent or trade personal information. We do not disclose it for advertising. We may use aggregated or de-identified participation counts for governance reporting and service operation, and we take care not to re-identify individuals.
Who can see information
Anyone
Anyone can read public proposals, published policy, recognised branch names, author display names, contributions and aggregate vote counts. Public means anyone with access to Engage, whether or not they have an account.
Signed-in members
Signed-in members can see their own account details, their own votes and reasons, their own contributions and proposals, and branch-scoped proposals for branches they belong to. Members do not receive a public member directory or other members' email addresses.
Branch administrators
Branch administrators can see and manage membership and proposal workflow for the branches explicitly assigned to them. A branch administrator does not receive identifiable ballots through that role alone; access requires national administrator status or the national permission to view identifiable ballots.
Moderators and national administrators
Moderators can review proposals and contributions and take moderation actions. National administrators can also manage member accounts, roles, branches, ballots, ratification and publication. National administrators can access identifiable ballot records. Moderators do not receive identifiable ballot records.
Story contribution reviewers
Unpublished stories, photographs, names and reply addresses are visible only to national administrators and people granted the national story-review permission. Branch administrators and moderators do not receive this access. Approved material appears publicly only in the channels the contributor chose, and the hand-off export given to the website team excludes reply addresses and internal notes.
What is not public
The following is not displayed publicly: email addresses; member identifiers; session, authentication and security records; individual votes and reasons; private or branch-restricted proposals; membership status; branch membership lists; unpublished story contributions and photographs; and administrative or audit records.
Disclosure and service providers
Engage uses a small number of external services. The implementation evidence identifies the following:
- If Google sign-in is enabled and you choose it, Google processes your sign-in request under its privacy policy. Fusion receives the account identifier and profile information Google returns, such as your name, email address, email-verification status and profile image.
- Resend
- Resend delivers Engage sign-in emails and membership verification notices. Resend receives the recipient email address, the message content (which may include your name and a single-use sign-in link) and delivery metadata. See the Resend privacy policy.
- Self-hosted infrastructure
- The Engage application and database run on infrastructure operated for Fusion. Deployment documentation does not identify a separate database-as-a-service provider. Network, hosting and reverse-proxy providers used to deliver the service may process request metadata as part of operating the service.
Access within Engage is limited to the roles described in this policy and to authorised administrators who need it. Branch administrators see membership and branch information for their assigned branches. That role alone does not grant access to identifiable ballots; such access requires national administrator status or a specific national permission. Personnel who administer the database or hosting infrastructure may also have technical access to stored records. That access is restricted to authorised operators and should be subject to confidentiality and least-privilege controls.
We may disclose information if required or authorised by law, a court or tribunal order, or to protect the safety and security of people or the service. We may also disclose it to professional advisers under confidentiality if needed for a legal or governance matter.
We do not sell personal information.
Overseas processing
Google and Resend are external service providers and may process information outside Australia. Fusion is confirming their processing locations and contractual terms. The Engage database is self-hosted on infrastructure operated for Fusion; its storage location and backup arrangements are being confirmed.
If the APPs apply, APP 8 requires Fusion to take reasonable steps before disclosing personal information overseas. Fusion should confirm whether an exception applies.
Security
Engage uses technical and organisational controls to protect personal information, including:
- HTTPS for production access through Fusion's reverse proxy;
- a session cookie that is intended to be HttpOnly and Secure in production;
- hashed, single-use sign-in tokens with a 10-minute expiry;
- rate limiting and session expiry;
- role-based access for members, moderators, branch administrators and national administrators;
- redaction of other members' ballot records for everyone except national administrators;
- a database that is not directly exposed to the public and is accessed with a scoped database user;
- audit records for sensitive governance actions;
- backups of the Engage database, stored outside the application host with access restricted to authorised operators;
No method of transmission or storage is completely secure. If you suspect unauthorised access to your account, contact us immediately.
If a data breach occurs, Fusion will contain and assess it, and notify affected individuals and the OAIC where required or appropriate.
Retention
We keep personal information only as long as needed for the purposes in this policy, including to maintain governance records. Engage does not currently apply automatic deletion schedules to most records. Story contributions have the specific schedule below.
- Account and profile
- Kept while your account is active and afterwards as needed for membership, governance, security or legal purposes. There is no automatic deletion schedule.
- Sign-in and session records
- Sign-in tokens expire after 10 minutes. Session records are kept until they expire or are revoked. Expired records may remain until routine cleanup.
- Contributions
- Kept until you or an authorised moderator deletes them, or until the proposal is deleted. Backups may retain copies for a limited period.
- Story contributions
- A withdrawal deletes the story text, name, reply address and photographs when the withdrawal is recorded; only the review record and its date remain. Declined material is deleted 90 days after the decision. Approved material is kept while it may be in use, and its reply address is deleted 12 months after approval, measured from the approval date rather than later reviewer activity. An administrator runs the retention sweep; it is dry-run by default and records what it would remove.
- Proposals and revisions
- Saved wording revisions, hashes and revision history are kept as governance records. When an administrator deletes a proposal, the live proposal and its comments are removed; revision history and vote records may remain.
- Votes and ballot records
- Kept as decision records so that ballots can be audited. They are not automatically removed when a proposal is deleted.
- Ratification and publication
- Ratification, publication, withdrawal and supersession records are kept as part of the public governance record.
- Audit and administrative events
- Kept to explain who changed what and when. Some are immutable.
- Legal acceptance records
- Kept to evidence which Terms and Privacy Policy versions a member accepted and when. Retained as part of the governance and compliance record.
- Server logs and backups
- Server log and backup retention periods are under review and will be published when finalised.
Account deletion is not currently self-service. Disabling an account prevents sign-in but does not erase records. Requests for correction or deletion can be sent to the contact address below; some records may need to be retained for governance integrity.
Access, correction and deletion
You can see your account details, votes, contributions and proposals in My Engage. You can change your display name there.
The current interface does not let you change your email address or delete your account yourself. To request access, correction or deletion, contact [email protected]. We may need to verify your identity.
We will respond within a reasonable period. We will explain if we cannot meet a request, including where a governance record must be retained.
You cannot rewrite a vote after a ballot closes. You can change your vote while the ballot is open. Correction of a factual record may be recorded as a correction or note rather than by erasing the original.
If you believe we have handled your information incorrectly, contact us first. If Fusion is covered by the Privacy Act for the relevant handling, you may also complain to the OAIC. Because registered political parties are generally exempt for political acts and practices, the OAIC may not be able to investigate every complaint. Fusion will still consider your complaint.
- OAIC
- Phone 1300 363 992 or visit the OAIC website.
Changes to this policy
We may update this policy. The current version and status appear at the top of this page. If a change materially affects how we handle personal information, we will take reasonable steps to notify members before it applies, and seek consent where required.
Owner authorisation has been recorded for this version. The effective date will be set on publication after any separate formal approval required by Fusion's rules.
Contact
For privacy questions, access, correction or deletion requests, or complaints, contact [email protected]. Legal correspondence: 254 McLeod Lane, Mansfield VIC 3722.
If you are not satisfied with our response, you may contact the OAIC at 1300 363 992 or through the OAIC website.
We may update these contact details. The current details will be published here.
Legal and organisational framework
Engage is operated by FUSION POLITICAL PARTY INCORPORATED (ABN 20 845 177 664). Fusion Party Australia is the public name used in Engage. The party is currently registered with the Australian Electoral Commission as "votefusion.org for big ideas" (registered abbreviation "votefusion.org"). The Privacy Act 1988 (Cth) and the APPs apply to many organisations. Registered political parties are generally exempt in relation to political acts and practices. The OAIC's guidance states that a registered political party is exempt. The statutory tort for serious invasions of privacy, which commenced on 10 June 2025, can apply more broadly than the APPs.
This policy is written with reference to the APPs as a matter of good practice. It does not replace Fusion's Constitution, Code of Conduct or dispute resolution processes, which also apply to members.
This policy is not legal advice. It must be reviewed and approved by an authorised Fusion representative before publication.
Document control and status
- Status
- Owner authorisation recorded for this version. Formal publication approval, if separately required, and the effective date remain outstanding.
- Legal review
- Not completed. Qualified legal review remains outstanding. Nothing in this document is a representation of legal clearance.
- Authorised approval
- Owner authorisation confirmed. The formal publication approving office-holder and approval date are not recorded.
Before publication
Owner authorisation has been recorded. Before these documents operate, record any separate formal publication approval required by Fusion's rules, set the effective date, and complete qualified legal review where required. This document is not legal advice.