Privacy Policy

Last updated: 12 October 2026

This policy explains how CAAN Consulting Pty Ltd (ABN 80 696 734 693), trading as TableOne Flow, handles personal information collected through this website and through the TableOne Flow application.

What we collect

When you submit the contact form we collect your email address (required), and optionally your name, role, organisation, and a description of your current Table 1 workflow. We collect only what you choose to provide.

The TableOne Flow application also records IP addresses and user agents in the places listed under IP addresses and user agents below.

Why we collect it

Our primary use is to respond to your enquiry. If you register your interest, we also send you product updates, early access communications, and pricing information when available — you can opt out of these at any time (see Marketing emails and unsubscribing below), and opting out does not affect a reply to a direct enquiry. We do not use your information for marketing to third parties, and we do not use it to train machine learning models.

Product data — Table 1 content and audit trails

Table 1 content, criterion responses, Source records, audit trail records, and any other data you create or upload within the TableOne Flow application are your data. We do not use that content for any AI or machine-learning purpose — not for model training, model evaluation, internal QA training sets, search-index training, or tuning of any kind. Your content is not transmitted to any third-party AI or model-training service.

The Solo tier stores all project data on your device by default. Where you use the hosted service under a paid licence, in the browser or in the Windows desktop app, your product data — Table 1 content, criterion responses, Source records, audit trail records, and the announcement files, reference library files and organisation logo you upload — is stored on infrastructure located in Australia, encrypted in transit and at rest. Two things stay on your own computer when you use the desktop app: reference library files you add there, which are not uploaded, and the copies of your reports written by its automatic backup, which is off until you turn it on and saves to a folder you choose. The supporting files you record as Sources are not uploaded: TableOne Flow records each file’s name, size and fingerprint, and the file stays where you keep it.

Two limits on that, stated plainly. Email is not covered by it. Sign-in links and notification emails are delivered by a provider based in the United States, which holds the recipient address, email metadata and delivery logs there; notification subjects and bodies may include report names. The public demo is not covered by it either — the demo runs on separate infrastructure outside Australia and is not intended for real project material.

Storing data in Australia describes where it is held. It is not a statement about which country’s laws could compel disclosure: our infrastructure providers, and their parent companies, remain subject to the laws of the countries in which they are established.

IP addresses and user agents

A user agent is the line of text a browser or app sends with each request to identify its software and version. The TableOne Flow application records IP addresses, and in some places user agents, for the purposes stated below.

• Signing in. Each sign-in link, and each signed-in session when it is started or renewed, records the IP address and user agent of the request. We keep them to investigate suspected unauthorised access to an account, and delete them once they are 90 days old.
• Changes to accounts and organisations. When you change your email address or profile or close your account, or an organisation administrator invites, adds or removes a member, changes a member’s role, ends a member’s sessions, transfers ownership or closes the organisation, the record of that change includes the IP address of the request. These records exist so that changes to who can access what can be traced later. They are kept indefinitely, including after the account or organisation is closed.
• Competent Person sign-off and announcement consent. When a Competent Person signs off a report in the hosted service, or consents to an announcement, the record of that act stores the IP address and user agent of the request, alongside the name they typed and the time. They are part of the evidence of how that record was made, so they are kept for as long as the report exists, including after it is archived and after the Competent Person closes their account, and are deleted when the organisation that holds the report is closed. They are not sent to anyone who opens the report, and are not displayed in the application or printed in exported reports. The one exception is the report’s full .t1f record, which members of the organisation who can edit its reports, and the report’s current Competent Persons, can download: it includes the user agent recorded with each announcement consent, but never an IP address. A report kept on your own device records the user agent with an announcement consent in the report file.
• The public demo. Each demo session records the IP address and user agent that started it, and uses the IP address to limit how many demo sessions one address can hold at once. Both are deleted with the session when it expires, seven days after it starts.

The application also uses the IP address of each request to limit how many requests one address can make in a short period. For that it holds the address in a counter that expires at the end of the period and is then deleted automatically. Separately, the firewall in front of the hosted service logs the IP address and request headers, including the user agent, of every request, and keeps that log for one month.

Records deleted under this section can remain in our database backups until those backups expire, up to 91 days later.

How we store it

Your information is stored on infrastructure provided by Cloudflare, Inc., which is based in the United States. By submitting the form you acknowledge that your information may be stored or processed outside Australia. Overseas recipients may not be subject to the Australian Privacy Principles, though Cloudflare maintains its own privacy and security commitments.

Registration email addresses and the details submitted in an enterprise enquiry are also transmitted to Brevo (Sendinblue SAS), an email platform headquartered in France, to send confirmations and notify us of the enquiry. Enterprise notifications contain the name, email, organisation, role and any optional procurement details submitted in the form. Under the Privacy Act 1988 (Cth) (specifically Australian Privacy Principle 8), we are required to disclose that your personal information may be disclosed to this overseas recipient. Brevo maintains its own privacy and security commitments; details are at brevo.com.

Emails from TableOne Flow itself are sent using Resend, an email delivery service based in the United States. That covers the one-time access link for the demo, and the emails the product sends: sign-in links, invitations to an organisation or to a report, review requests to a Competent Person, and notices such as being mentioned in a comment or a change to an account’s email address. These emails contain the recipient’s address, the name of the person and organisation they come from, and may contain a report’s name. They do not contain report content. As above, this means that information may be disclosed to an overseas recipient under Australian Privacy Principle 8. Resend maintains its own privacy and security commitments; details are at resend.com.

If someone invites you to TableOne Flow, or names you as a Competent Person on a report, we receive your email address from them, not from you. We use it only to send you that invitation and the emails that follow from it. Each such email says who sent it and why you received it.

Registration and contact records in our application database are retained for three years from collection and then removed by a scheduled retention process. Notification emails are handled under our mailbox retention procedures. You may request earlier deletion using the contact method below; some processor backup copies may persist for their documented backup cycle.

Marketing emails and unsubscribing

Every product update, early access, or pricing email we send includes a one-click unsubscribe link, handled through Brevo. You can also opt out at any time using the contact form. Unsubscribing needs no account or password, we action requests within five business days, and the unsubscribe link in each email stays active for at least 30 days after it is sent. Opting out of these updates does not affect a direct reply to an enquiry you have sent us.

Your rights

You may request access to the personal information we hold about you, ask us to correct it, or ask us to delete it. To do any of these, use the contact form.

Analytics and cookies

This website uses Cloudflare Web Analytics to measure page views and understand how visitors find and use the site. This service is operated by Cloudflare, Inc. (the same infrastructure provider disclosed above). It does not set cookies, does not store IP addresses, and does not identify individual visitors. That describes the website’s analytics only; what the application records is set out under IP addresses and user agents.

The contact form uses a security widget to prevent automated submissions. This widget may set a short-lived functional cookie. No other cookies are set by this website.

Contact

Questions about this policy: use the contact form.