Privacy
policy

Who we are

FOC Capture is a construction QA and compliance platform operated by FOC Capture Pty Ltd, based in Victoria, Australia. This policy applies to the FOC Capture Android app, the web portal at app.foccapture.com.au, and the foccapture.com.au website.

We are bound by the Australian Privacy Act 1988 and the Australian Privacy Principles.

What we collect and why

Account information

• Your name and email address. Used to create and manage your account.
• Your organisation name. Used to identify your account in the platform.
• Your billing details. Processed securely by Stripe, never stored on our servers.

Google Drive access

When you connect your Google Drive, FOC Capture requests permission to:

• Create a FOC Capture folder in your Drive.
• Read and write files within that folder only. This includes photos, project records, ITP completions, and reports.
• List files within the FOC Capture folder to display them in the app.

This corresponds to the drive.file OAuth scope (https://www.googleapis.com/auth/drive.file), the most restricted Drive scope, which permits access only to files our app has created or that you have explicitly opened with our app. We cannot see, read, or list any other files in your Drive.

We do not access any files outside the FOC Capture folder. We do not read your emails, calendar, contacts, or any other Drive files. The access token is stored encrypted in our database and used only to perform actions you initiate within the app.

FOC Capture's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Project and field data

• Photos captured in the field. Stored in your Drive, referenced in our database by file ID.
• Survey coordinates and asbuilt records. Stored in your Drive as part of your project record.
• ITP completions and form data. Stored in your Drive.
• Defect records and field notes. Stored in our database, referenced to your project.
• Variation records and approval history. Stored in our database with signed PDFs in your Drive.

Compliance documents

• Contractor and employee documents you upload. Stored in Supabase Storage, accessible only to your organisation.
• Licence and ticket details. Stored in our database, visible only to your organisation.

Usage data

• Crash reports and error logs. Collected via Sentry (EU region) to help us fix bugs. Contains device type, app version, and stack traces. No project data is included in crash reports.
• Basic session information. Used to maintain your login session.

Interest registration

• If you register interest via foccapture.com.au, we collect your email address to follow up. We do not add you to any marketing list without your explicit consent.

The interactive demo

The demo at foccapture.com.au/demo lets you import your own element schedule without an account. It is the only part of this site that processes a file you supply, so it is described here in full.

Your spreadsheet is read in your browser

The file you drop in is parsed, profiled and displayed entirely by JavaScript running on your own device. Its contents are not sent to us as you work: no headers, no cell values, no rows. The single exception is the carry-over described below, which happens only if you click the button that asks for it. If you close the tab without doing that, we never held your file at all.

What the demo does send

To decide what each of your columns is for, the demo sends one small request per import. That request carries anonymous statistics about your columns and about the import itself, and nothing else:

• For each column: its position, how many values it holds, how many of those are distinct, and whether they are numeric.
• Which columns hold a constant value within each group, expressed as pairs of column positions.
• Whether the file was a .csv or .xlsx, a coarse row-count band (for example "100-499"), whether you used our sample schedule, how long you took to import, and a random session identifier generated in your browser for that visit.

The list above is the whole request. The fields we read are fixed, anything else in the body is ignored and never stored, and an entry for a column carrying a field we did not expect is rejected outright rather than logged. What we store is rebuilt from those validated numbers rather than copied out of what was sent, so nothing we write to that table is derived from a header or a cell value.

We keep these statistics to tune the column detector. The detector is deterministic, rule-based code, not a machine-learning model, and nothing from the demo is used to train one. The statistics are not linked to an account, an email address or a name, because at that point in the demo we do not have any. The session identifier is random, is created fresh on each visit, and is not used to recognise you again.

If you choose to carry the project over

The final step offers a button that creates the project for real. Only if you click it does your file itself leave the browser. It is uploaded once, together with the column mapping you confirmed, into a private storage bucket, and you are sent to sign up.

• The link that carries the upload stops working 24 hours after you click, whether or not you go on to sign up. Signing up binds the link to your account, which is what lets you pick the import back up after confirming your email, but it does not extend the window and nothing can extend it beyond that day.
• If you finish the import, the file and its record are deleted immediately, as part of the import.
• If you do not, the file is deleted by an automated cleanup that runs once a day at 02:00 UTC. A link expiring does not by itself delete anything, so deletion can lag behind the link dying: up to about 48 hours after upload.

IP addresses and the demo endpoint

The demo has no login, so it needs some limit on how often one caller can use it. The counter that does that stores a salted SHA-256 hash of the caller's IP address, together with which action was called and which hour it was called in, and deletes those counters daily. It does not store the address itself, and it is not joined to anything else. We will not call that anonymisation: the IPv4 address space is small enough that anyone holding both the stored rows and the salt could work an address back out, so it is protection against casual inspection, not a guarantee. The salt is held as a server-side secret, separately from the rows themselves.

Separately, and independently of our own code, our hosting provider Supabase records the requesting IP address in its own request logs for the endpoint the demo calls, in the same way any web server records the addresses that connect to it. Those logs are held under Supabase's own retention. We are not able to claim that no record of your IP address exists anywhere as a result of using the demo, and we would rather say so than imply otherwise.

Elsewhere in the product, where a signed-in user signs a record such as an NCR or a variation, we deliberately store the signing IP address in full, unhashed, as part of the signature evidence for that record. That is a different purpose and a different control, and it applies only to authenticated sign-off actions, never to the demo.

What we don't do

• We do not sell your data to any third party.
• We do not use your data for advertising or marketing purposes.
• We do not share your project data with other FOC Capture customers.
• We do not access your Google Drive beyond the FOC Capture folder.
• We do not store payment card details. Stripe handles all payment processing.
• We do not use your project data to train AI models, and our terms with our AI provider exclude what we send from being used to train theirs. Where the platform does use AI to read a document, we say so — see AI-assisted document reading.
• We do not use advertising networks, analytics platforms, or tracking pixels.

We have deliberately removed a claim that used to appear here — that we do not transfer data outside Australia or the EU. It was not accurate. Our web portal runs in Tokyo, payment processing involves the United States and Ireland, and email delivery is US-based. Where your data goes is set out below, in full.

Where your data is stored

Several of these are outside Australia. Under Australian Privacy Principle 8 we remain accountable for personal information we disclose overseas, and we hold data processing agreements with our critical providers.

Third-party services

FOC Capture uses the following third-party services to operate. Each has their own privacy policy.

• Google Drive. File storage for your project data.
• Supabase. Database, authentication and file storage infrastructure.
• Vercel. Web portal hosting.
• Stripe. Payment processing. Note that Stripe acts as a data controller in its own right for part of what passes through it, not only as our processor — for that portion Stripe determines its own purposes and its own privacy policy governs.
• Resend. Transactional email delivery, and receipt of email sent to project inbound addresses, including attachments.
• Sentry. Crash and ANR reporting from the Android app. What is sent is diagnostic: stack traces, thread state, device and OS details, breadcrumbs, and an account identifier. Your email address and IP address are removed before sending, and file paths are reduced to the filename. No project data, photos, drawings or records are sent.
• Anthropic. AI-assisted document reading, where enabled — see below.
• Google Play. Android app distribution and crash diagnostics.
• Microsoft. Sign-in, if you choose “Continue with Microsoft”. Microsoft authenticates your own Microsoft or work account and returns your email address and name; we never see your password, and no project data is sent.
• Google Firebase Cloud Messaging. Push notifications to the Android app. Device tokens only.

We do not use advertising networks, analytics platforms, or tracking pixels on any FOC Capture surface.

AI-assisted document reading

The platform includes features that read a document and suggest something about it — pulling values off a concrete docket, or proposing where an emailed document should be filed. Where such a feature is enabled and you trigger it, the document is sent to Anthropic PBC (the Claude API) for processing in the United States, and the response comes back as a suggestion for a person to confirm. Our terms with Anthropic exclude what we send from being used to train models.

• It is on-demand, never automatic. Nothing is sent because a document arrived. It is sent because someone pressed a button.
• Where the feature is used on inbound email, the data class is not bounded by document type. Whatever a sender attached may be processed — which can include personal information and confidential commercial terms.
• A manual path always exists. Every value these features suggest can be entered by hand instead.
• On the Android app, docket text recognition runs on the device by default. It works offline and sends nothing anywhere.

Your responsibilities

When you use FOC Capture to capture information about other people — your workers, subcontractors, visitors, or anyone who appears in a photograph — you decide what is collected and why, and you hold the primary privacy obligation for it. We hold it on your behalf. That means you are responsible for:

• Having a lawful basis to collect it, and giving those people the notice your own privacy obligations require — including that their information is held in the platform and in your own storage account.
• Obtaining consent where your circumstances require it, particularly for photographs of identifiable people, signatures, and licence or induction documents.
• Collecting only what you need. The platform holds whatever you put in it; deciding what belongs in a project record is your judgment, not ours.
• Managing who in your organisation has access, and removing it promptly when someone leaves.
• Responding to access, correction and deletion requests from those people. Ask us and we will help you find or extract what you need.

Separately, you are responsible for the accuracy of the data you supply and for checking what the platform produces against your own raw data before you rely on it. That is set out in our terms of service.

Data retention

• Your account data is retained for as long as your account is active.
• If you cancel your subscription, your account data is retained for 90 days before deletion, giving you time to export anything you need.
• Project files in your Drive are yours. Cancelling your FOC Capture subscription does not affect them.
• Crash reports are retained for 90 days in Sentry.
• A demo carry-over file is deleted on import, or by the daily cleanup described in The interactive demo above. The demo's anonymous column statistics are kept indefinitely, because there is nothing in them that identifies anyone.
• The demo's rate-limit counters are deleted daily.
• You can request deletion of your account and all associated data at any time.

Your rights

Under the Australian Privacy Act you have the right to:

• Access the personal information we hold about you.
• Request correction of inaccurate information.
• Request deletion of your account and associated data.
• Withdraw consent for data processing where consent was the basis for collection.
• Lodge a complaint with the Office of the Australian Information Commissioner if you believe your privacy rights have been breached.

To exercise any of these rights, contact us at admin@foccapture.com.au. We will respond within 30 days.

Cookies and tracking

The FOC Capture web portal uses session cookies only. Small files stored in your browser to keep you logged in. We do not use tracking cookies, advertising cookies, or any third-party analytics scripts.

The foccapture.com.au website does not use any cookies beyond what is required for basic functionality.

Changes to this policy

If we make material changes to this privacy policy we will notify active users by email and update the date at the top of this page. Continued use of FOC Capture after notification constitutes acceptance of the updated policy.

Questions or concerns