LedgerFlow
LedgerFlowA SHiRE product

Privacy Policy

Last updated 15 November 2026

1. Who we are

LedgerFlow is expense-management software operated by Ray Morrison trading as Shire 3D (ABN 49 597 815 496) ("LedgerFlow", "we", "us"). This policy explains how we handle personal information under the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).

It covers our website (ledger-flow.com.au), the LedgerFlow web workspace, the cardholder receipt app, and our emails. Contact us about privacy at 3drays85@gmail.com.

2. What we collect

WhoInformation
Business account holders (owners, accountants, managers)Name, work email, phone, business name, ABN, role, password (stored only as a one-way hash), billing country
Staff and cardholders added by a businessName, work email, mobile (optional), department, assigned company card (name and last 4 digits only), card monthly limit
ReceiptsReceipt images or PDFs, merchant, date, amount, GST, category, notes, approval history
Card and bank transactionsDate, merchant, amount, reference, which card or account it belongs to; account numbers stored masked (last 4 digits only)
Bank connections (when available)Bank account names, masked account numbers, balances and transactions shared with your consent via our banking data provider (see section 5)
Website enquiriesName, work email, company, team size, the message you send
Technical dataIP address, browser type, sign-in times, security logs

We do not collect full card numbers, card security codes or internet-banking passwords. Payment card details for your LedgerFlow subscription are collected by our payment partner, not by us.

3. How we collect it

4. How we use it

We use personal information only to run LedgerFlow for the business you work with or own:

We do not sell personal information and do not use it for advertising.

Automated processing

LedgerFlow uses software to help, not to decide, in these places:

Automated stepInformation usedWhat happensWho decides
Missing-receipt reminders and escalationCard transactions, cardholder name and email, receipt status, the business's due-time settingEmails the cardholder, then notifies owners and accountants if a receipt stays missingThe business decides any follow-up
Card-limit alertsCard spend this month, card limitEmails at 80% and 100% of the limitThe business decides any action; LedgerFlow does not block cards
Approval alertsReceipt amount, the business's approval thresholdEmails approversA person approves or rejects every receipt
Matching suggestionsMerchant, amount, dateSuggests which receipt fits a transactionA person confirms each match

LedgerFlow does not make decisions that by themselves change someone's pay, employment or credit.

5. Bank data and the Consumer Data Right

Bank feeds are not yet available in LedgerFlow. When they launch, they will be optional and only switched on by a business owner or accountant. Bank data will reach LedgerFlow through an accredited data recipient under the Consumer Data Right (CDR); you will give consent on its secure screens, and LedgerFlow will never see your internet-banking password.

We will import outgoing transactions only, to match them with receipts, and store account numbers masked. Before bank feeds go live, we will update this policy and publish a separate CDR policy explaining how CDR data is handled.

6. Who we share it with

We share personal information only with providers that help run LedgerFlow, under arrangements that limit their use of it:

ProviderWhat forWhere data may be held
GoDaddy (hosting and database)Runs the website, app and databaseUnited States (a move to Australian hosting is planned)
CloudflareWebsite security and deliveryGlobal network
ResendSends LedgerFlow emailsUnited States
Polar (merchant of record), with Stripe for card processingSubscription checkout, tax invoices, customer billing portalUnited States and other countries

We may also disclose information if the law requires it, or to protect people's safety or our rights. If LedgerFlow is sold or restructured, information may transfer to the new owner under this policy.

Because some providers are overseas, your information may be stored or processed outside Australia. We take reasonable steps, as APP 8 requires, so these providers protect it to a standard comparable to the APPs.

7. Businesses control their own workspace

Each business that subscribes decides who joins its workspace and what is uploaded. For staff and cardholder information, LedgerFlow acts on the business's instructions. A business using LedgerFlow should tell its staff it does so, for example in its own privacy policy or staff policies.

Workspaces are kept separate: one business cannot see another's data. Within a business, cardholders see only their own card, spend and receipts; owners and accountants see the whole workspace.

What we can see. LedgerFlow's own admin tools show us only each business's name, its main account holder's name and contact details, and its plan. They do not show your receipts, transactions, cards or staff. We do not look at workspace data unless you ask us to for support, or the law requires it.

If you are a staff member and want your information changed or removed, you can ask your employer, or contact us and we will work with your employer to respond.

8. Security and how long we keep it

No system is perfectly secure. If a data breach is likely to cause serious harm, we will notify affected people and the Office of the Australian Information Commissioner (OAIC) as the Notifiable Data Breaches scheme requires.

Retention. We keep workspace data while the business's subscription or trial is active. After a business cancels, we keep its data for 90 days so it can export or return, then delete it, except records we must keep by law (such as billing records). Businesses should export anything they need for their own tax-record obligations before closing their workspace.

9. Access, correction and deletion

You can ask to see the personal information we hold about you, ask us to correct it, or ask us to delete it. Email us (section 1) with enough detail to identify you. We respond within 30 days, and access is free.

We may need to confirm your identity first. If you are a staff member of a business that uses LedgerFlow, we may refer part of a request to that business, because it controls its workspace records. If we refuse a request, we will tell you why and how to complain.

10. Cookies

LedgerFlow uses only essential cookies: one that keeps you signed in (it expires after 12 hours) and security cookies set by Cloudflare to block automated attacks. We do not use advertising or tracking cookies.

11. Complaints and changes

If you have a privacy complaint, email us first (section 1). We will acknowledge it within 7 days and aim to resolve it within 30 days. If you are not satisfied, you can complain to the Office of the Australian Information Commissioner.

We will update this policy when our practices change, and show the date of the latest version at the top. For significant changes we will tell account holders by email.

Back home