Privacy Policy

Account details you give us: name, email address, company, and the role you hold on a project.

The records you create in the app: defects, inspection answers, company form answers and the signatures drawn on them, work orders, comments, the photos and files you attach, the locations you assign them to, and every status change made along the way. Each of those carries the person who made it and when. That is the point of the register, and it is retained for as long as the record is.

The details your phone saves inside a photo (when it was taken, its GPS position and compass heading, and the phone's make and model), and the position of your device when you raise a defect, or when you submit a company form that is set to record it, if your browser allows it. The position recorded with a company form is shown only to people who review or manage company forms.

Technical data: IP address, browser and device type, pages viewed, features used, and errors encountered.

To operate the service, support you, fix what breaks, and meet legal obligations. We do not sell personal data, and we do not train AI models on your records.

Your register lives in Australia. The database and the application servers run in Sydney, and the photos and files you upload are held in object storage pinned to the Oceania region.

Some service data is processed outside Australia, and it is worth being specific rather than implying otherwise: email delivery, product analytics and the AI features run on services based in the United States. What crosses the border is listed row by row below.

Database backups are held as point-in-time restore history by our database provider, in the same region as the database itself.

Every kind of service that processes your data, and where it runs:

This website runs analytics and ad conversion tracking, which set cookies and tell the analytics provider that a browser visited a page here. Its fonts are served from our own domain.

Inside the app, a product analytics service records which features are used and what errors are hit, tied to your user account so we can tell one person's broken session from a general outage.

Some features use an AI model to read what you give them and suggest something back:

• suggesting a description, classification and priority when you add a photo to a new defect;
• turning your voice into text when you dictate;
• reading a drawing for its locations, or for defect hotspots;
• suggesting which QA checklists belong in which locations;
• summarising a project's health page;
• summarising where a defect stands from the notes the reader can see;
• reading an uploaded construction programme for milestone dates;
• drafting a company form from a description you type or dictate;
• answering questions you ask the in-app assistant, where your company has it.

Each sends only what that feature needs, such as the photos and text of the defect being written, the drawing being read, the description of the form being drafted (with your company's industry, its word for a defect and the names of its newest forms), the recording of your voice or the question you ask the assistant (described below), to our AI model provider, and nothing else about your account. Your data isn't used to train models. The result comes back as a suggestion for a person to keep, change or discard.

The assistant answers questions about your records and about using IssuesId. For company admins, managers and users it sends the question you type, the last few messages of that conversation, your company's word for a defect, and whatever it looks up to answer you. Each lookup runs with your own access, so it can only read what you could open yourself. What reaches the model is the text of what it finds: a defect's description, status and location, and the names of the projects, locations, contractors and people it matches. When you ask about one defect it also gets that defect's status changes, who it is issued to, its due dates and the notes you are allowed to see. It does not read email addresses or phone numbers.

For residents the assistant only helps with using the app. It sends the question, the last few messages of the conversation, your company's word for a defect and the help text it finds, and it cannot read anyone's records. Trades, clients, field workers and building managers do not get the assistant.

The assistant keeps your conversations, meaning your questions and its answers, so you can come back to them. Only you can open yours in the app. IssuesId staff can read a company's assistant conversations when looking into a problem or improving the assistant. You can delete one conversation or all of them.

Apart from drafting a company form and the assistant, all of these are on by default, and a company admin can switch any of them off for the whole company in Settings. Drafting a company form is reaching companies in stages: once your company has it, it is on too, and a company admin can switch it off in Settings. The assistant is off until IssuesId switches it on for your company, and it is not one of the switches in Settings.

If your company connects an AI app of its own to IssuesId, that app reads what you ask it to, under that app's own terms.

You may request access to, correction of, or deletion of your personal data at any time by emailing privacy@issuesid.com. We respond within 30 days. Where a record is part of a project's audit trail, deletion may be limited to your personal details rather than the entry itself. We will tell you which applies before we act.

privacy@issuesid.com · IssuesId Pty Ltd, Level 2, 100 Collins St, Melbourne VIC 3000, Australia.