Privacy Statement

1.1 This Privacy Statement explains how the operator of Fluid Network Studio, ABN 61 267 830 638 (“the Operator”, “we”, “us”, “our”), based in Queensland, Australia, handles personal information in connection with Fluid Network Studio (the “Tool”). Fluid Network Studio is Australian owned and developed.

1.2 We aim to handle personal information in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs), whether or not we are formally required to.

1.3 Privacy contact: admin@fluidnetworkstudio.com.

2.1 Account information. If you create an account: your email address and a password. Authentication is handled by our service provider (Supabase); your password is stored by that provider in hashed form - we never see or store it in plain text.

2.2 Projects you choose to save. If you save a network to the cloud, we store that project (the network you drew, its settings and its name/description) against your account. Cloud projects are isolated to your account by database-level access rules. Networks you do not save to the cloud never reach our servers - building and solving happen entirely in your browser, and saving to a file stores it on your own device only.

2.3 Correspondence. If you email us, we keep the correspondence so we can respond and keep a record of the request.

2.4 Billing information (paid plans). If you subscribe to a paid plan, payment is processed by Stripe. You enter your card details directly with Stripe on its secure checkout - we never see or store your full card number. Stripe gives us only limited billing information, which we store against your account to run your subscription: a Stripe customer identifier, a subscription identifier, your plan tier and your subscription status. Stripe handles your payment data under its own privacy policy (stripe.com/privacy).

2.5 Service logs and security data. We and our service providers automatically generate limited technical information needed to operate and secure the Tool, such as IP addresses, timestamps, authentication events, browser type, and error and diagnostic logs. We use this information only for security, fraud prevention, troubleshooting, performance and operation of the Tool. We do not use it to build a marketing profile of you.

2.6 What we do not collect. Beyond the categories in clauses 2.1 to 2.5, we do not collect your name, phone number, or precise location data such as GPS. The analytics described in clause 3 are aggregated and de-identified, and are not linked to your identity.

3.1 We use a privacy-friendly, cookieless analytics tool (Vercel Analytics and Speed Insights) to understand aggregate usage and performance, such as page views and load times. It sets no cookies, does not track you across other websites, and does not build a profile of you.

3.2 We use no advertising or tracking cookies, pixels or beacons.

3.3 We do not sell, rent or share personal information for marketing.

3.4 We do not send marketing email. Any email from us relates to your account or a request you made.

4.1 The Tool sets only essential session cookies used by our authentication provider to keep you signed in. They are not used for tracking or advertising, and there is nothing to opt out of - if you do not sign in, no account cookies are set.

5.1 We collect and use the information in clause 2 only to: provide the Tool and your account; store and retrieve the projects you save; respond to your requests; keep the service secure; and meet legal obligations.

6.1 We use reputable service providers to run the Tool - currently Supabase (authentication and database), Stripe (payment processing for paid subscriptions) and our website hosting provider. Your account information and saved projects are stored with Supabase in Australia (Sydney, ap-southeast-2 region). Your payment details are handled by Stripe (see clause 2.4), which processes them overseas under its own terms, and our website hosting provider and other providers may process limited technical data (such as the request logs and diagnostics described in clause 2.5) on servers outside Australia. We choose providers with strong security practices; Supabase and our host act only on our instructions in relation to your data.

6.2 We do not otherwise disclose personal information unless you ask us to, or we are required to by law.

7.1 Access to saved projects is restricted to your account by row-level security rules enforced in the database itself. Credentials are handled by our authentication provider using industry-standard hashing. All traffic to the Tool is encrypted in transit (HTTPS).

7.2 No system is perfectly secure; please use a strong, unique password. If we become aware of a data breach likely to result in serious harm, we will notify affected users and the regulator as required by the Notifiable Data Breaches scheme.

8.1 Saved projects are kept until you delete them. Account information is kept while your account is active.

8.2 You can delete any saved project yourself in the Tool. To close your account and have your account information and remaining projects deleted, email admin@fluidnetworkstudio.com from the account’s email address. We action deletion requests within 30 days, subject to any legal, accounting or fraud-prevention retention we are required or reasonably need to apply, and to our routine backup cycle (residual copies in backups are overwritten in the ordinary course).

9.1 You may ask for a copy of the personal information we hold about you, or ask us to correct it, by emailing admin@fluidnetworkstudio.com. We respond within a reasonable time and do not charge for reasonable requests.

9.2 If you believe we have mishandled your personal information, please contact us first and give us the chance to put it right; we aim to respond to privacy complaints within 30 days. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

10.1 If we change how we handle personal information (for example, if we change how we use analytics or add new features that handle personal information), we will update this statement and its “last updated” date before the change takes effect, and we will flag material changes on the sign-in page or by email.