Privacy Policy
What changed in version 1.2: we've added "Website usage counts" (under "What we collect"), describing daily totals of three actions on our website, recorded without cookies or visitor identifiers, along with the related provider, storage and retention details. Read version 1.1.
What changed in version 1.3: we've added how we handle enquiries made through our Facebook and Instagram lead forms: what we collect, how we use it, Meta's role, how long we keep it and how to opt out. Nothing else in this policy has changed. Read version 1.2.
Who we are
RoofFindings is operated by ROOFFINDINGS PTY LTD (ACN 703 331 319, ABN 18 703 331 319), Queensland, Australia ("RoofFindings", "we", "us").
This policy explains how we handle personal information in the RoofFindings app, the company web portal, our website, our free-trial request form, our Facebook and Instagram lead forms and in support.
Contact us about privacy, access, correction or complaints at support@rooffindings.com.au.
What we collect
Accounts and companies. We collect:
- your name and email address (the password you use to sign in is handled by our sign-in provider);
- your company's details: name, ABN, licence, address, phone, email, website and logo;
- your role in the company;
- your staff profile: name, position, phone, email, licence number, qualifications and typed signature name.
Inspections. We collect the information you and your company enter about inspections. This can include:
- property addresses;
- names and contact details of customers or occupants;
- claim and job references;
- notes, findings and recommendations;
- roof and interior photographs, annotations and generated reports.
When you create an inspection, the app copies your staff profile details into it so the report shows who prepared it.
Trial requests and support. If you request a free trial, we collect your name, business name, work email, mobile and answers through our application form. If you contact us, we keep the correspondence.
Enquiries through Facebook or Instagram lead forms. If you complete a RoofFindings lead form on Facebook or Instagram, Meta collects what you submit and makes it available to us. We receive your name, email address and company name, and your answers to our questions: your role, whether you carry out roof inspections or prepare insurance roof reports, and whether you or your assessors use an iPhone on site. If you don't provide these details, we may not be able to respond to your enquiry.
Technical information. We receive error and performance diagnostics (see "Diagnostics"). Some of our service providers record technical logs, including information such as IP addresses and request times.
Website usage counts. On some pages of our website we count, in total:
- how many times our free-trial page is opened;
- how many times links to it are clicked on our other marketing pages; and
- how many times its App Store button is clicked.
For each count we record only:
- the date (Brisbane time);
- the page;
- which of those three actions happened; and
- a broad channel label (our Facebook ads, our emails, or unknown), taken from tags in the link you followed.
We keep only these daily totals. Our counting tables don't store your IP address, browser or device details, cookies, the address of the page you came from, or any identifier for you or your device. We don't use these counts to identify you, to follow you across websites or apps, or for advertising targeting. We don't share them with advertising platforms.
To make a count, your browser sends a small request to our website, which our website host (Render) forwards to our own counting service on Cloudflare. Like any website request, it's handled by these providers' networks, which process technical information such as your IP address and browser details. See "Where information is stored and who processes it".
Our website is designed not to send these counts when your browser sends a Global Privacy Control or Do Not Track signal, and our counting service ignores count requests that carry either signal. Some browsers, including Safari, don't send these signals.
These totals are an approximate measure, not a complete record. Some visits aren't counted, for example:
- when a browser doesn't send the information our service requires;
- when a privacy setting or content blocker stops the request;
- when Cloudflare's automated security screening blocks a request;
- when a request fails; or
- when a daily safety limit is reached.
Where it comes from. Most information comes from you, your company and its users. Information about property owners and occupants is usually supplied by the inspecting business, not by those people directly. Photographs and notes can incidentally capture people, documents or other personal details. Please upload only what the inspection needs and what you're authorised to provide.
If you don't provide information needed for an account or inspection, that part of the service may not work. Contact us if you need to make an enquiry without creating an account.
Billing. If you subscribe, Stripe processes your payments. We share business name, billing address, contact details and company/subscription identifiers with Stripe and keep subscription, invoice, payment-status and issued-report usage records to administer billing. Stripe handles full card details; RoofFindings does not store full card numbers.
How we use it
We use information to:
- run accounts and company workspaces;
- store and sync inspections across devices;
- produce reports;
- provide support;
- find and fix faults;
- protect the service;
- respond to enquiries made through our lead forms;
- measure, in aggregate, how our website and our marketing are used, so we can improve them;
- meet legal obligations.
People in your company can see information according to their role. We may access information when it's needed for support, security or administration.
You decide who receives the reports you export. Emailing or sharing a PDF uses the mail or sharing app you choose on your device. Recipients and their email services handle their copies independently of us.
RoofFindings doesn't send inspection text or photographs to any artificial-intelligence service; its suggestions are rule-based. We won't start using inspection data for AI processing without first assessing it and giving notice.
Lead-form enquiries. We use the details from a lead form to respond to your enquiry: to send you the sample report you asked for, answer your questions and, if you ask us to, help you start a trial or arrange a walkthrough. We may follow up about that enquiry. We won't add you to ongoing marketing unless you separately agree. You can opt out of further contact at any time by replying UNSUBSCRIBE to one of our emails or by emailing support@rooffindings.com.au. If you opt out, we'll keep a record of your email address so that we don't contact you again. We don't upload lead-form details to Meta or any other platform for advertising targeting.
We don't sell personal information or use it for advertising. We have not configured analytics or advertising cookies on the RoofFindings website, and our website usage counts don't use cookies or browser storage. The linked application form is operated by Jotform and may use its own website technologies.
Diagnostics
We use Sentry to detect errors and performance problems in the app, with its data held in Sentry's European Union data region.
A diagnostic event can include:
- an internal user identifier;
- device and operating-system details;
- the app version;
- filtered technical information about what went wrong.
Our filters are designed to remove names, contact details, sign-in tokens and report content before events are sent. Sentry doesn't store your IP address, but it records an approximate city-level location derived from it. Diagnostic records aren't anonymous. They're retained according to the retention settings of our Sentry service; contact us if you need current information about diagnostic retention.
Where information is stored and who processes it
Our main database, sign-in service and private photo storage are provided by Supabase in Sydney, Australia. Backup copies of photographs are kept with Amazon Web Services in Sydney, Australia.
We also use these service providers:
- GitHub: runs our automated photo-backup jobs. Photo files pass through GitHub-hosted runners while they're copied and checked.
- Resend: sends sign-up confirmation codes, password-reset codes and team invitations.
- Stripe: processes subscription and additional-report payments and stores billing/payment information. Its processing may occur outside Australia.
- Microsoft 365: provides our business email, including support@.
- Sentry: diagnostics, as above.
- Supabase server functions: we use these for sending invitations and deleting accounts. Supabase documents them as running on regionally distributed servers closest to the user, so they may run outside Sydney.
- Render: hosts our website. Render's delivery network (which uses Cloudflare) processes visitors' IP addresses and requests, including the website usage-count requests that Render forwards to our counting service.
- Cloudflare (our counting service): receives the website usage-count requests and stores the daily totals described under "Website usage counts". Cloudflare may receive your IP address as part of these requests; we don't store it in our counting tables. We have turned off logging, tracing and log export for our counting service. Cloudflare may still keep its own operational, security and abuse-prevention records about requests under its own practices, and it applies automated security screening before a request reaches our service. Cloudflare's network operates worldwide, so these requests may be handled outside Australia. The daily totals are stored in Cloudflare's Oceania region; Cloudflare doesn't guarantee that this region means storage in Australia.
- Jotform: hosts our founding-access application form.
- Meta Platforms: provides the Facebook and Instagram lead forms and the business tools we use to retrieve lead-form details. Meta handles information on its platforms under its own privacy policy and operates globally, so this information may be handled outside Australia.
- Apple and Expo: app distribution and testing (App Store, TestFlight) and app builds. Apple receives tester names and email addresses, and any feedback or crash reports testers choose to share.
The information each provider receives depends on its function; not every provider receives inspection content.
Some of our service providers may process personal information outside Australia. Where we can reliably identify an overseas location from our configuration or the provider's documentation, we describe it in this policy. Some providers use global or regionally distributed infrastructure, so processing locations can vary. Storing our main database and photo storage in Sydney doesn't mean all personal information stays in Australia.
Security
We use technical access controls and company permissions, encrypted connections, private photo storage and encrypted photo backups to help protect information.
No system is risk-free. Copies on phones, exported PDFs and email attachments must also be protected by the people holding them. Protect your device and password, and tell us promptly if you suspect unauthorised access. If a data breach occurs, we assess it and notify affected people and the regulator where the law requires.
How long we keep information, and deletion
Ending a trial, subscription or access period doesn't delete any reports.
Deleting a report removes it from the company's list.
- A company owner or administrator can restore it within 90 days.
- After 90 days it can no longer be restored in the app, but it remains in our systems, together with its photographs and their backup copies.
- Automatic permanent removal of deleted reports isn't enabled.
- Contact us if you'd like a deleted report permanently removed. We'll consider the request against the company's record-keeping needs and the law.
Removing or replacing a photograph in a report currently leaves the original image file in storage and in our backups.
Deleting a staff account removes that person's login and profile. Reports they created stay with their company, without a link to their account. The staff details copied into those reports, including issued reports, remain part of the company's records.
Deleting a company owner's account:
- If other staff remain, ownership must first be transferred.
- If the owner is the only member, deleting the account deletes the company and all its reports and photographs from our active systems straight away, including recently deleted reports.
- If a deletion step fails, the process can be retried, and you can contact us for support.
Backups. Information removed from our active systems through an account or company deletion can remain in backups for a period after deletion:
- Database backups are retained on a rolling 7-day basis.
- For photo files removed through the account or company deletion process, the next nightly backup run records the deletion in our photo backup. The backup is configured to expire superseded copies 30 days after they're superseded.
This backup process doesn't currently remove deleted reports, or photographs that were merely removed or replaced within a report. As explained above, those records and files currently remain stored. We haven't yet completed a timed end-to-end test of backup removal, so we don't promise a fixed erasure deadline.
Copies on phones.
- The app keeps copies of reports and photographs on each phone that has opened them, so it works without a connection.
- Signing out doesn't remove these copies. They stay on that phone but aren't shown to other accounts.
- They're removed when the account is deleted in the app, when that user's app next refreshes their company membership online after they have been removed, or when the app is deleted from the phone.
- Deleting the app can also delete work that hasn't synced yet, so check reports show as synced first.
Website usage counts. We report on daily totals for up to 365 days and regularly delete totals older than that. Our counting database provider keeps automatic recovery copies that let the database be restored to an earlier point within the previous 7 days, so a deleted total can remain in those recovery copies for up to 7 days. Request information handled by Render and Cloudflare while delivering our website and these counts is kept according to their own practices.
Lead-form enquiries. We keep lead-form details and our correspondence about your enquiry for as long as we need them to deal with the enquiry and any follow-up, then delete what we no longer need, unless we need to keep it to meet a legal obligation or you have become a customer. If you opt out, we keep only what we need to honour that request. You can ask us to delete your lead-form details by emailing support@rooffindings.com.au. Meta's retention of information on its platforms is set by Meta.
Other records. Diagnostics, support email and provider logs have separate retention periods depending on the service and its configuration; contact us if you need current retention information about a particular category. Copies already exported, emailed or shared can't be recalled by us. We don't intend to keep information indefinitely and will review retention as the service develops.
Billing and financial records. Company or account deletion does not delete billing, usage, invoice, tax or payment records required for legal obligations, accounting, disputes or collection of accrued charges. Stripe customer and invoice records are retained separately. Access to retained records is restricted. Billing and financial records are kept for as long as Australian tax and corporations law requires (generally five to seven years).
Access, correction and complaints
You can ask for access to, or correction of, your personal information, ask about deletion, or make a complaint by emailing support@rooffindings.com.au.
- We may need to confirm your identity and authority.
- Where a roofing business supplied the information, we may work with that business on your request. That isn't an automatic refusal.
- If we refuse a request, we'll explain why and what you can do next.
- We aim to acknowledge requests within 7 calendar days and to respond within 30 days, and we'll explain any delay. These are targets, not a guarantee that every matter will be resolved within 30 days.
You may also contact the Office of the Australian Information Commissioner about matters within its jurisdiction: https://www.oaic.gov.au/
Changes to this policy
This page shows the current version and its effective date. We'll give reasonable notice of material changes and won't introduce new uses that need your consent simply by changing this page.