November 16, 2026

Data Ownership: Who Controls Your Community’s Data?

Data ownership matters when you run community engagement for a council, agency or utility. You collect names, email addresses, postcodes and sometimes age or gender, alongside people’s honest opinions about things that affect their street, their town or their kids’ school.

People hand that over because they trust you with it. So before you choose or renew an engagement platform, it’s worth asking a simple question. Once that data is collected, who actually controls it?

With Engagement Hub, you do. We host your data in Sydney and don’t transfer personal information overseas. You control who can access it.

The quick version

Here’s how Engagement Hub handles your data:

  • You own and manage all of it.
  • Your site administrators and nominated project admins control access to your data. There are 15 access permissions built into Engagement Hub so you can define exactly what access each administrator has e.g. just to one project, no access to SRM etc
  • Our staff can only see it if you give them access, say for troubleshooting or training.
  • We store your data on Amazon Web Services (AWS) in Sydney. The hosting infrastructure holds ISO 27001:2022 and CSA STAR Level 2 certifications.
  • We don’t transfer personal information overseas.
  • We encrypt data in transit with TLS 1.3. We use AES-256 to encrypt stored data and backups.
  • The platform helps you meet the Australian Privacy Act 1988, the Australian Privacy Principles and the New Zealand Privacy Act 2020.

What does data ownership actually mean?

Most software vendors say you own your data. However, ownership on paper doesn’t explain who can access it day to day.

In practice, data ownership means your organisation decides who can see, use and share the information you collect. So before choosing a platform, ask these four questions:

  1. Who can access your data? Only your administrators, or the vendor’s staff too?
  2. Where does the platform store it? In which country, and which laws apply?
  3. How does the vendor use it? Only to support your engagement, or for other purposes too? Does the vendor share it with anyone else?
  4. Can you control access within your team? Can you choose what each person sees and track their activity?

And data sovereignty?

Data sovereignty is the idea that information is governed by the laws of the country where it’s collected and stored. For an Australian organisation, keeping the data here keeps it under Australian privacy law. It sounds like a technical point, but it matters a great deal when the data belongs to your community.

How Engagement Hub supports your data ownership

Engagement Hub is Australian-owned community engagement and stakeholder relationship management (SRM) software. We launched in 2016, and our clients include all levels of government, corporates and not-for-profits. Here’s how we deal with each of those four questions.

Only your team can see your data

You own and manage your data. Your site administrators can see it, and so can any project administrators you nominate. That’s it.

Sometimes you’ll want our help, maybe to troubleshoot something or train new staff. In that case you can give us access, and while we have it we work under your privacy statement as a third-party service provider. Otherwise, we can’t see your stakeholders or their submissions.

It stays in Australia

We host everything on Amazon Web Services in Sydney, in infrastructure certified to ISO 27001:2022 and CSA STAR Level 2. Our Privacy Policy says it plainly: we don’t transfer any personal information overseas. So your community’s data stays under Australian law.

We don’t share it

Your engagement data isn’t shared with us, and it isn’t shared with any third party. We don’t use AI in the software as we believe the risk is too great to open your consultation and SRM data to AI at the moment.

You decide who sees what

Not everyone on your team needs access to everything. For example, you might want someone to manage two projects without viewing stakeholder details. Engagement Hub’s 15 permission settings let you set those limits.

In addition, our Governance Log records admin and user activity. No one can edit those records, so you can check who did what and when.

Security behind the scenes

Your data is encrypted in transit with TLS 1.3, and at rest and in every backup with AES-256. We monitor the platform around the clock, every day of the year. We also run manual and automated penetration testing, alongside intrusion detection and DDoS protection. And your administrators can make multi-factor authentication compulsory for admin and stakeholder accounts.

Your community keeps control of their own details

People who register on your site get their own dashboard. From there they can update their details, change their preferences, unsubscribe from emails or delete their account. Bulk emails only go to people who’ve agreed to receive them, which keeps you on the right side of the Spam Act.

It’s all designed to help you meet the Privacy Act 1988, the Australian Privacy Principles and the New Zealand Privacy Act 2020. Our Security & Compliance page has the full detail.

Common questions about data ownership

What is data portability, and why does it matter?

Data portability means being able to move your information between systems in a usable format. For community engagement, that includes keeping submissions connected to the right projects and stakeholder records. An export should preserve the context you need to understand and use the information.

How can we avoid data lock-in when choosing software?

Check the export process before signing, and ask to see a sample. Confirm whether it includes attachments, activity history and links between records, rather than just a basic spreadsheet. Agree on export formats, costs and support so moving platforms remains a practical option.

Who owns the reports and insights created from our data?

Don’t assume the same terms cover source data and everything the platform creates from it. Contracts may treat reports, analytics and anonymous statistics differently. Check your rights to download, reuse and retain those outputs, including after your subscription ends.

Can a software provider use our data to train AI?

Engagement Hub does not use AI within the software. Many clients use AI under their own AI policies by exporting data and inputting to their AI tools. If you are using AI, check the terms for each AI feature and any external provider it uses. Using AI to analyse submissions is different from using those submissions to train a model. Ask whether training is permitted, whether you can opt out and how long the provider retains inputs and outputs.

What happens to our data when a software contract ends?

Your agreement should explain how you retrieve your records, when access ends and what the provider retains. Confirm the export deadline and deletion process, including backups. Before closing the account, check that your exported records are complete and usable.

Want to understand your data controls?

Before choosing an engagement platform, check who can access your information, how the provider can use it and what happens when you leave

Want to see it for yourself?

Data ownership is part of keeping your community’s trust. Before choosing an engagement platform, ask who can access the information you collect, where it is stored and how your organisation controls its use.

If you’d like a closer look, book a free 30-minute demo or ask for our full Security & Compliance Statement.

popular pages
Comparing online engagement & Stakeholder Management software?
leading sentiment analysis software
Featured posts