Our products hold residents' details, complaints, job applications, business contacts and workers' details. Each one is built differently, so here is where the data sits for each, who can see it, how long we keep it, and what's still on the way.
For project directors and clients. The detail for IT and security teams is further down.
Held in the AWS Sydney region, and encrypted when stored and when it moves.
Access rules sit in the database itself and follow each person's role, so a mistake on a screen can't expose records.
Who changed a stakeholder, complaint or commitment, and when, is kept on the record.
Forms ask for what the job needs, and personal details nobody needs are cleared on a schedule.
360 automated checks of who can see and change what run before anything reaches a live project.
It runs on established website services, some of which store data outside Australia. Each project's privacy statement names them.
Some things are the same whichever product you use.
Our products are built to help project teams meet their obligations, not to replace their advice.
We ask for what the job needs and clear what nobody needs any more.
Engage runs on its own database, with the access rules built into the database itself.
The database, sign-in, file storage and server functions run on Supabase in the AWS Sydney region. Data is encrypted at rest and in transit. Supabase holds SOC 2 Type 2 and ISO 27001 certification.
Access rules are enforced by the database on every request, so a mistake in a screen can't expose data the rules don't allow.
Changes to stakeholders, interactions, commitments, complaints, tasks, social accounts, consultations, team roles and project settings are logged with who made them and when.
Personal details nobody needs are cleared automatically.
Every release runs the full test suite before it goes anywhere near a live project.
We'd rather tell you what's coming than overstate what's there.
Connect is a website built on established platforms, with the routing rules set up for each project.
The website and job listings run on Webflow, business accounts on Memberstack, and form routing on Make. Some of these services store data outside Australia, and the project's privacy statement says which and where.
Each person sees only what their part of the project needs.
Written for each project and reviewed before launch.
Things we are adding as projects ask for them.
Impact switches on inside the same console as Engage, and its access rules sit in the database in the same way.
Workers' details count only where they have said yes.
Project reports show totals, not individuals.
Tell us what your agency or partner IT team needs to see, and we'll walk them through how each product handles data.