Australian/onshore data posture
Core engagement data is hosted in Australia to support local governance, public sector review, and procurement requirements.
Trust Security, privacy, and AI governance
Security and data governance for community engagement teams.
Communiti is built for teams handling community feedback, sensitive local issues, and public decisions. Keep data governed, keep ownership with the customer, and keep AI outputs reviewable.
Security pillars
Three commitments that guide our trust posture.
Security is not treated as a vague enterprise promise. Communiti focuses on the controls buyers ask about first: data location, data ownership, and lifecycle governance.
-
-
Customer ownership and no model training
Your uploaded materials, feedback records, transcripts, survey responses, and project data remain your organisation's data and are not used to train models.
-
Lifecycle controls
Engagement data can be retained, deleted, or de-identified when it is no longer required, subject to legal, reporting, contractual, and operational obligations.
Trust posture
Plain-language answers for security, privacy, and governance review
Use this page as a starting point for internal champions, managers, IT, procurement, and governance teams reviewing Communiti.
Australian and onshore data storage and processing
For public sector and community-facing work, data location matters. Communiti is designed around Australian hosting for core engagement data, with current hosting and subprocessor details available for procurement review.
- Australian hosting posture for core customer engagement data
- Subprocessor transparency for IT and procurement review
- Designed for councils, agencies, utilities, and engagement consultants
- Plain-language security material available for internal assessment
Your data remains yours
Community engagement data is not generic content. It may include lived experience, local vulnerability, demographic information, and feedback connected to public decisions. Communiti uses customer data to provide the platform, not to train models.
- Customer materials and engagement records remain customer-owned
- No training of foundation models or Communiti platform models on customer data
- Outputs remain connected to the source material used to produce them
- Privacy and data handling details available for governance review
Lifecycle controls for engagement data
Engagement records should be kept while they are needed for delivery, reporting, auditability, support, or legal requirements, then deleted or de-identified when they are no longer required.
- Retention aligned to project and contract requirements
- Deletion when data is no longer required
- De-identification where aggregate reporting can continue without identifying individuals
- Export-ready records for customer-controlled reporting and retention
Engagement data
How Communiti protects engagement data
Communiti protects engagement data across the workflow: collection, ingestion, review, analysis, reporting, and follow-up.
Key commitments
-
Encrypted data handling
Data is encrypted in transit and at rest to reduce exposure while it moves through the engagement workflow.
-
Role-aware access
Access can be aligned to project responsibilities so teams can collaborate without making every record broadly available.
-
Source-linked evidence
Themes, summaries, and reporting outputs can stay connected to original comments, transcripts, submissions, and supporting evidence.
-
Subprocessor transparency
Communiti maintains subprocessor information so IT and procurement teams can assess provider purpose and location.
-
Reviewable workflows
Important outputs can be checked by people before they are used in reporting, follow-up, or decision-support material.
-
Export-ready records
Teams can preserve reporting and compliance materials outside the platform when their governance process requires it.
AI governance
AI with human review
Communiti uses AI as a reviewable assistant, not an unreviewable autopilot. The answer should never be "because the AI said so." Teams need editable outputs, visible caveats, and evidence they can trace.
With commercial off-the-shelf tools
AI outputs can sit outside the engagement record.
-
Project context has to be rebuilt through prompts, exports, and manual uploads
-
Outputs can become detached from the governed engagement record
-
Findings may sound confident even when evidence is thin, skewed, or incomplete
-
Review trails are harder to defend when summaries cannot link back to source feedback
With Communiti
AI works inside a reviewable engagement workflow.
-
Project, survey, response, and reporting context stay inside the workflow
-
Outputs are editable and reviewable before use
-
Findings can stay connected to source evidence, caveats, and original feedback
-
Important actions stay behind human review and approval gates
Questions
Security and data FAQs
Practical answers about data residency, ownership, model training, lifecycle controls, traceability, and reviewable AI.
Where is Communiti data hosted?
Core customer engagement data is hosted in Australia. For procurement review, request the current security and capability pack, including hosting and subprocessor details.
Do you train AI models on our data?
No. Customer data is not used to train foundation models or Communiti platform models.
Who owns the data we upload or collect?
Your organisation retains ownership of the materials and engagement records you provide or collect through the platform.
Can AI outputs be reviewed and edited?
Yes. Communiti is designed around human review. AI-assisted summaries, analysis, reports, and suggested actions should be reviewed before use.
Can findings be traced back to the original feedback?
Yes. Communiti Analysis is designed so themes and insights can be traced back to original comments, transcripts, submissions, and supporting evidence.
What happens when data is no longer required?
Data can be deleted or de-identified when it is no longer required, subject to contractual, legal, reporting, and operational obligations.
Do you support procurement and IT review?
Yes. Communiti can provide a security and capability pack for IT, procurement, governance teams, managers, and internal champions.
Does Communiti replace professional judgement?
No. Communiti helps teams work faster, but people still review outputs, apply context, make decisions, and remain accountable for the engagement process.
Need security material for IT or procurement?
Request a concise security and capability pack covering Communiti's data handling, AI governance, hosting posture, subprocessors, and product controls.
Stay close to the future of community engagement
Product notes, practical field guides, and evidence-led thinking for teams working under public scrutiny.