Effective 17 November 2026
Bilbee (https://bilbee.app) is operated by Richard Morrisson (ABN 89 650 318 493), an Australian sole trader. This policy explains what personal information we collect, why, where it's stored, who else touches it, and your rights. It's written to align with the Australian Privacy Principles (APPs).
Account information: your email address and a password. Passwords are hashed with scrypt via the Better Auth library. We never see or store your plain-text password beyond the sign-in request itself. If you choose Google sign-in instead, we receive basic profile details from your Google account (such as your name and email address) to create and secure your account. We never receive your Google password. If you choose Sign in with Apple, we receive your name (Apple shares it only the first time you sign in) and your email address, or, if you choose Hide My Email, a private address Apple creates that forwards our emails to you. We never receive your Apple Account password.
Account verification: before a new account enters Bilbee, we verify an Australian mobile number using an SMS code. We keep the phone number and verification reference only while a code is outstanding. Once the code is confirmed, we remove them and keep the last four digits and when the check passed. We do not store the SMS code. We also keep security counters to limit repeated attempts and the number of accounts one mobile can open. Those use a keyed fingerprint of the number, not the number itself.
Information you store in the app:
Billing information: if you choose a paid plan, you enter your card details on Stripe's checkout page, not ours. We keep a Stripe customer reference and your plan's status and renewal date, never your card number.
Connected integrations: if you connect optional integrations, we store what we need to use them. If you connect Stripe so your clients can pay invoices by card, we store your Stripe account ID, or your Stripe key if you added one yourself. Stripe's connection screen shows the access you're giving Bilbee, and we use it only to create card checkouts for your invoices, to close any that are no longer needed, to see when they've been paid, and to end the connection when you disconnect or delete your account. If you connect Google Calendar, we store a Google authorisation token. These are stored encrypted, and you can disconnect them at any time. If you connected through Stripe's own page, disconnecting Stripe in Bilbee also asks Stripe to end Bilbee's access to your Stripe account, and you can check or remove that access yourself in your Stripe account's settings. If you added a Stripe key yourself, disconnecting removes the key from Bilbee, and you can delete the key itself in your Stripe account.
Connected apps: if you connect an AI assistant (such as Claude or ChatGPT) or the Bilbee command line, we keep a record of the connection: which app it is, what you let it do, when you connected it and when it last used Bilbee. We store the tokens it signs in with only as hashes, which can't be turned back into the tokens. It reads what it asks for from your books, which can include your clients' details, and section 5 says where that goes. You can disconnect an app at any time from your account page, and it loses access straight away, though what it has already read stays with the company that runs it.
Technical information: like most online services, our servers keep standard logs that include technical details such as your IP address, and we use IP addresses for security protections like rate limiting. We also note when you last signed in or used Bilbee.
How you use Bilbee: we record some of what happens in your account, with the time, so we can see where people get stuck. That is when a send or a change is refused (for example because there's no business name yet, or a plan limit was reached), how a CSV import ended (counts only, never the file or its rows), when you open the tax estimate, when you draft an invoice or quote from a sentence, with what came back (a draft, a choice of client, a question, or nothing) and how the draft ended (saved as drafted, saved after changes, or left unsaved), never what you wrote or what was drafted, and each day you use a connected app (whether it was an AI assistant or the Bilbee command line, never what it read or wrote). We also count visits to the sign-up page, with where the visit came from (such as a Google search), and failed sign-up attempts, with the kind of error, without knowing who you are.
How you found us: when you sign up, we save with your new account the campaign tags on the link you arrived by (such as utm_source), an ad click identifier if the link carried one (such as Google's gclid), and the name of the website that sent you. We use these only to learn which ads and links bring people to Bilbee.
Support correspondence: if you email us (for example at support@bilbee.com.au), we keep that correspondence so we can help you and keep a record of your request.
Our weekly update: while you have an account, your name and email address are on the mailing list for our weekly update email, which Resend keeps for us. Resend records whether each update was opened and which of its links were clicked. Unsubscribing takes you off the list.
Some of what you store in Bilbee is personal information about other people: your own clients. We store and process that information on your behalf so you can invoice and keep records. We don't use your client data for our own purposes, and we don't contact your clients except to send the invoice and quote emails you ask us to send.
You're responsible for collecting your clients' details lawfully and for telling them how you use their information, where that's required.
We collect and use your information only for these purposes:
We don't use third-party analytics or advertising trackers in Bilbee, we don't show ads in Bilbee, and we never sell your data. Our public website, bilbee.com.au, counts page visits with Cloudflare Web Analytics, which uses no cookies and doesn't use your IP address to identify or track you. Our weekly update is the one email we track: Resend records whether each one was opened and which of its links were clicked, so we can see what's useful, and your email app may block that. The invoice, quote and account emails we send carry no tracking.
Bilbee is hosted on Railway, so your data, including your clients' details, is stored on Railway's servers outside Australia.
Several providers that help run Bilbee operate outside Australia. Resend delivers our email, so the invoice and quote emails you send (which can include client names, contact details and invoice contents), any receipt emails you forward, our account emails, and our weekly update with the record of whether you opened it and which links you clicked, may be processed on Resend's infrastructure, including in the United States. If you upload or forward a receipt, Anthropic processes that receipt image (outside Australia, including in the United States) to extract the expense details. If you draft an invoice or quote from a sentence, Anthropic processes what you wrote (outside Australia, including in the United States) to fill in the draft, with your clients' names, your saved items, your past invoice and quote lines (each with its client, price, number and date), how many unbilled time entries and billable expenses each client has and their dates, and whether you're registered for GST. We don't send it the contact details you keep for your clients. Stripe, which operates globally, including in the United States, processes the payment for a paid Bilbee plan and, if you connect Stripe to accept card payments, your clients' card payments. If you use Google sign-in or Google Calendar, Google processes that on its own infrastructure, which operates globally, including in the United States, and if you use Sign in with Apple, Apple, which also operates globally, including in the United States, processes that sign-in and, if you chose Hide My Email, forwards our emails to you. Every visit to bilbee.app and bilbee.com.au passes through Cloudflare's global network, which processes your IP address and the pages you request to protect and deliver them.
Under the Australian Privacy Principles (APP 8), these are cross-border disclosures, and the privacy laws in those countries differ from Australia's. We take reasonable steps to ensure our providers handle your data, and your clients' data, consistently with the Australian Privacy Principles.
Our sign-in and create-account pages load their heading font from Adobe Fonts. Adobe receives your IP address to deliver the font and information about the fonts served and the website loading them. Adobe says it does not store that IP address or use cookies to serve fonts. These requests may be processed outside Australia. We do not send your account details or bookkeeping records to Adobe.
Twilio and Cloudflare operate internationally, so mobile verification and the Turnstile security check may involve processing outside Australia. We use these checks for security, not advertising.
If you connect an AI assistant, what it reads from your books, including any of your clients' details, goes to the company that runs it (Anthropic for Claude, OpenAI for ChatGPT). You choose to send it there, so we don't take the steps described above for it, even when that company is one of our providers: it's handled under your own agreement with that company and its privacy policy, including whether it can use what it reads to train its models, and it may be handled outside Australia, including in the United States. Check those before you connect one. The Bilbee command line runs on your own computer and talks only to Bilbee, but if you let an AI assistant run it, what it shows goes to that assistant's company.
We share data only with the service providers needed to run Bilbee:
Google Calendar and the Google API Services User Data Policy: if you connect Google Calendar, Bilbee requests read-only access to the events on calendars you own (the calendar.events.owned.readonly scope), and reads only your primary calendar, for one purpose, to show your events on the Timesheet so you can turn them into billable time entries with a click. Bilbee never writes to your calendar, doesn't store your events on our servers (they're fetched live and shown to you), and doesn't use them for advertising or sell them. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. You can disconnect Google Calendar at any time from the Timesheet, which removes the stored authorisation.
We also send what an AI assistant you connect asks for to the company that runs it, because you connected it. It isn't one of our providers, even when that company is one (section 5).
We don't sell or rent your data to anyone, and we don't share it with advertisers.
Bilbee uses one essential session cookie to keep you logged in. No advertising or tracking cookies.
On bilbee.com.au and on Bilbee's sign-up and log-in pages, your browser keeps the campaign tags on the link you arrived by, any ad click identifier and the name of the website that sent you in session storage, which is cleared when you close the tab. They reach us when you sign up or log in, and we keep them only for a new account. Opening the sign-up page also sends us where the visit came from (such as a Google search), and we keep only a count of it, with nothing that identifies you.
If you generate a public link for an invoice, anyone who has that link can view the invoice, including the client details and payment details on it. Links use long random tokens designed to be unguessable, but they aren't password-protected. A link keeps working until you reset it from the invoice (Reset client link) or the invoice is deleted. Only share links with the people who should see them.
No online service can promise perfect security, but these protections are in place and we take them seriously.
If a data breach occurs that's likely to cause you serious harm, we'll notify you promptly (including what happened, what information was involved, and what we're doing about it) and we'll notify the Office of the Australian Information Commissioner (OAIC) where required.
We keep your data for as long as your account is active. It's your business record-keeping, so it stays until you say otherwise. The records of how you use Bilbee (section 2) are the exception: we keep them for 13 months, then delete them.
If you delete your account (see section 12), we delete all your data and your Stripe customer record, take you off our weekly update's mailing list, and cancel any paid plan. Copies may persist in encrypted backups for up to about 90 days before they're gone completely. Stripe keeps its own record of past payments, as payment providers are required to.
If you think we've mishandled your personal information, email support@bilbee.com.au and we'll look into it and respond as quickly as we can.
If you're not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (OAIC) at www.oaic.gov.au or 1300 363 992.
If we change this policy (for example, if we add a new service provider), we'll update the effective date at the top and notify you of material changes by email or in-app before they take effect.
Privacy questions or requests: email support@bilbee.com.au.