What we record, who can see it, and what we will never do with it.

A meeting, with a start and a stop

VizField records audio when a manager presses record and stops when they press stop. It is not always-on. It does not listen between meetings, and there is no background mode. A red light is visible on the recorder for the whole time it is running.

From that audio we produce a diarized transcript (who said what, when), minutes, a one-line summary, and shorthand action items. We keep the audio because every action item points back to the moment it was said. That link is the whole point of the product.

The room, and the project team

Minutes, transcript and recording moments are scoped to the meeting and its project. People on the project team can open them from their site wall. Anyone outside the company (a client, an architect, a subcontractor) sees only what the project manager chooses to share, for as long as they choose to share it, and has to prove they own the email address it was sent to.

A meeting address such as vizfield.com/m/9f4c-2a is not a password. Opening it without access shows the project name, the date, and a sign-in gate, and nothing else.

Three commitments, not three settings

We will never produce personal productivity statistics. No talk-time, no word counts, no attendance records, no engagement scores, no ranking of individuals. Not as a feature, not as an export, not on request from an employer.

We will never aggregate meeting content into a profile of a person. Recordings stay attached to the meeting and project they came from. There is no cross-project view of an individual, because we do not build one.

We will never record covertly. If the light is off, VizField is not recording. We will not ship a build that can record without showing it.

These are not configurable. An employer paying us cannot turn them on, and we will end a contract rather than change them.

Cut, remove, seal

Anyone in a meeting can ask for part of it to be taken back, and there are exactly three things that can happen. Cut: before the meeting is shared, the segment never enters the pipeline at all. Remove: after sharing, the segment is masked and shows as removed from project view by the speaker. Seal: where a claim window is open on the project, the original is preserved but locked away from ordinary view.

We use those three words deliberately, and we don't use the phrase "permanently deleted", because until a physical purge runs end to end it would not be true. When that purge exists, this page will say so plainly.

Retention follows the project

Recordings and records are held for the life of the project plus the dispute window that applies to it, then removed on the schedule agreed with the company that owns the project. Data is stored in Australia. We do not sell it, we do not use it to train models for anyone else, and we do not share it with third parties beyond the infrastructure providers needed to run the service.

Under the Privacy Act 2020

You can ask what we hold about you, ask for a copy, ask us to correct it, or complain to the Office of the Privacy Commissioner. Email privacy@vizfield.com and we will respond within 20 working days. If you are on a site and would rather not go through your employer, write to us directly and we will deal with you, not with them.