Privacy policy

FloConnector (“FloConnector”, “we”, “us”) is a hosted integration platform that lets the AI client you already use reach the SaaS tools your business runs on. This policy explains what we collect, why, how we protect it, and the choices you have. It covers floconnector.com, the console, and the connection endpoints we host for you.

1. Who this applies to

This policy is written for our customers, the businesses and people who register for a FloConnector account, and the authorised users they invite. For that data, the account and identity records, usage metadata, and billing history described below, we are the controller.

Where we process data on your behalf about your own customers or contacts (for example, records that live in a platform you connect), we act as a processor and you are the controller. That relationship is governed by our data processing addendum, which is the contract required by Article 28 of the GDPR and includes the EU and UK standard contractual clauses. It forms part of our terms and you accept it when you register. If you need an executed copy for your own compliance file, email support@floconnector.com.

2. Data we collect

Account and identity

When you register we collect your email address and, optionally, your name and workspace/account details. We authenticate you with a one-time code sent to your email, so we don’t store passwords. We record basic session and device information to keep your account secure.

Vendor connection credentials

When you connect a platform (for example Xero), we receive OAuth tokens that let us call that platform on your behalf. These tokens are envelope-encrypted in our application before they are written to the database. Our database never sees them in plaintext. We refresh them server-side as needed. The AI client you plug in never receives your vendor credentials.

Business data flowing through connections

To fulfil a request from your AI client, we call the platforms you’ve connected and relay the result. We operate as a proxy: we do not maintain a persistent mirror of your platform data. Where a request needs to analyse a larger dataset, we load it into an ephemeral, in-memory analytics engine that is discarded at the end of the request; the underlying records never enter the AI model’s context and are not retained by us.

What we don’t receive

The conversation you have with your AI client stays between you and your AI provider. FloConnector receives only the structured tool call your AI client chooses to make (which tool, on which connection, and the parameters needed for that call) and returns the result. We do not receive, see, or store the prompts you type, the AI’s replies, or the wider conversation. Because we don’t retain what a call returns, sensitive values that pass through a call, such as financial figures, invoice amounts, and customer records, are relayed and discarded, not collected.

Usage and audit metadata

We keep a metadata-only record of tool calls (which tool ran, on which connection, when, whether it succeeded, how much data moved, and the resulting usage count) for billing, support, security, and product analytics. This log stores metadata, never the request or response payloads themselves: we record that a call returned 400 rows, not what was in them. We keep it for the life of your account so we can show you how your connections are being used over time (see how long we keep data).

This record also identifies which member of your workspace made each call, by way of the AI client they connected, and groups calls into the session they belonged to. That is what lets a workspace see its usage broken down by person rather than as one undifferentiated total. Anyone with access to your workspace can see it, in the dashboard and in the activity export. If a member disconnects their AI client, their past calls stop naming anyone rather than being reattributed.

Billing

Payments are processed by Dodo Payments as our Merchant of Record. Your card details are handled by Dodo and their payment processors. We do not receive or store full card numbers. We retain billing records such as plan, invoices, and usage totals.

Site and support

We collect standard server logs (IP address, browser, pages requested) and any information you send us when you contact support or submit feedback.

3. How we use data

• To provide, secure, and maintain the service and your connections.
• To authenticate you and protect against fraud and abuse.
• To meter usage and bill you accurately.
• To provide support and respond to your requests.
• To understand which connectors and tools are used, so we can improve the product.
• To produce aggregated, de-identified statistics about how the platform is used.
• To comply with legal obligations.

We do not sell your personal information, and we do not use your data or the data flowing through your connections to train AI or machine-learning models.

Aggregated statistics

We may publish aggregated statistics about how FloConnector is used, and share them with third parties such as the platforms we connect to, partners, and investors. Examples of the kind of figure we mean: which connectors are most widely adopted, how many tool calls run across the platform in a month, or how often a particular kind of call succeeds.

These figures are combined across our whole customer base and carry nothing that identifies you — not your name, your email, your workspace, your account, or which platforms your business in particular has connected. We share them only in a form that cannot reasonably be traced back to you or your business, we don’t attempt to reverse them, and anyone we share them with is not permitted to either.

They are derived from the metadata-only usage record described above. They are never derived from the business data that flows through your connections, because we don’t retain it: it passes through and is discarded, so there is nothing there for us to aggregate.

4. Sub-processors we rely on

We use a small set of service providers to run FloConnector. Each is bound by contract to protect your data:

• Dodo Payments: payment processing (Merchant of Record).
• Composio: managed connectivity and OAuth for the broader connector catalogue. For connectors delivered through Composio, request and response data passes through Composio’s infrastructure to reach the platform, and Composio retains those request and response payloads under its own retention practices, which is a difference from our own systems worth knowing about. Composio is our sub-processor, and we remain fully responsible to you for how it handles your data. Our natively integrated connectors (for example Xero) call the platform directly and don’t involve Composio, so nothing in that flow is retained by anyone but the platform itself.
• Resend: transactional email (sign-in codes, notifications).
• Google reCAPTCHA: abuse protection on our sign-in pages. When you sign in, Google receives your IP address and information about your interaction with the page in order to score whether the request is automated. It is used only to protect sign-in, never to profile you, and it does not touch any data from the platforms you connect.
• Mammoth Media Pty Ltd, trading as Binary Lane: infrastructure hosting for the application and database, in Australia.
• Cloudflare R2: offsite storage for database backups. Backups are encrypted before they leave our server, using a key we do not store on that server, so the storage provider holds ciphertext only and neither they nor anyone who reached our infrastructure can read the backup contents.

Some sub-processors process data outside your country, and FloConnector itself is in Australia. Where data protection law requires a transfer safeguard, we rely on the standard contractual clauses set out in our data processing addendum, together with the UK addendum where the UK GDPR applies.

The platforms you connect are not sub-processors. Xero, QuickBooks, ServiceM8 and the rest are your own service providers under your own agreements with them. We reach them at your instruction using the scopes you grant. What they do with your data is governed by your relationship with them, not ours. The list above is only the providers that help us run FloConnector itself.

5. How long we keep data

• Account data: for as long as your account is active.
• Vendor tokens: until you disconnect the platform or close your account, after which they are deleted.
• Business data in transit: not retained; discarded at the end of each request.
• Usage metadata: the metadata-only record of individual tool calls (which tool, on which connection, which member of your workspace made it, when, whether it succeeded, and how much data moved) is retained for the life of your account. It contains no request or response payloads. We use it for billing, support, security, and the usage analytics we show you. Your dashboard displays the most recent 90 days in detail; longer periods are shown as totals.
• Billing records: invoices, plan history, and usage totals are retained as required for accounting, tax, and legal purposes.
• On account closure: your usage metadata is deleted along with your workspaces, other than billing records we are required to keep.

6. How we protect data

Vendor credentials are encrypted application-side before storage. Connections are served over encrypted transport, and every data-plane request requires a valid bearer token scoped to your workspace. Access to each connection is controlled per user, and you decide which tools an AI client is allowed to use. No security measure is perfect, but we design to store as little sensitive data as possible in the first place.

If something goes wrong

If we discover a breach affecting personal data we hold, we will tell you within 48 hours of becoming aware of it, using the email address on your account, and tell you what we know, what we are doing about it, and who to talk to. Where we are processing on your behalf, you are the one who decides whether a regulator or the affected people need to be notified, and we will give you what you need to make that call. The full commitment is in clause 9 of our data processing addendum.

7. Cookies and analytics

Our marketing website (floconnector.com) can use Google Analytics to understand which pages people find useful. It is off by default. The first time you visit we ask with a banner, and we do not load Google Analytics or set its cookie unless you accept. If you decline, no analytics cookie is set. You can change your mind at any time by clearing the flc-consent value your browser stored for our site, which brings the banner back.

When enabled, Google Analytics sets a first-party cookie to measure page visits and traffic sources. It receives nothing about the platforms you connect or the business data that flows through your connections. The console (the signed-in product) does not run Google Analytics; we understand product usage through the metadata-only tool-call log described above. We also use a small number of strictly necessary cookies for sign-in and security, which are required for the service to function and are not used for analytics.

8. Your rights and choices

Depending on where you live, you may have rights to access, correct, export, or delete your personal information, and to object to or restrict certain processing. Australian customers are covered by the Privacy Act and the Australian Privacy Principles; customers in the EEA/UK and California have rights under the GDPR/UK GDPR and CCPA/CPRA respectively. You can exercise these rights, or ask a question, at support@floconnector.com. You can also disconnect a platform or close your account at any time from the console. If you are a business answering a request from one of your own customers about data in a platform you connected, that data lives in the platform rather than with us, and clause 8 of our data processing addendum covers the help we give.

9. Children

FloConnector is a business product and is not directed to anyone under 16. We don’t knowingly collect data from children.

10. Changes to this policy

We may update this policy as the product evolves. When we make material changes, we’ll update the date above and, where appropriate, notify you.

11. Contact

FloConnector is operated by MODLL PTY LTD (ABN 79 639 342 484), based in Victoria, Australia. For any privacy question, email support@floconnector.com.