Plain-English summary
- We are EmberFI Pty Ltd, an Australian company. We run a cash-flow app called Ember.
- We collect the financial information you give us: transactions you import, categories, notes. Ember does not connect to your bank, and we never see your bank password, full account number, or full card number.
- Your data lives in Australia (Supabase Sydney). Some processing happens overseas: web hosting (US), email (US), AI (Anthropic, US), and an encrypted nightly backup (GitHub, US). AI categorisation sends a redacted description of unknown merchants; Ember AI chat and insights send the parts of your financial data they need to answer (see §8).
- We do not sell your data, send marketing, share with advertisers, or share with banks, insurers or employers.
- You can export, correct, or delete everything at any time, in Settings or by emailing tech@emberfi.com.au.
The detail below is what's legally meaningful. The summary above is the short version.
1. Who we are
Ember is operated by EmberFI Pty Ltd (ACN 700 035 089), an Australian company. We are the “APP entity” responsible for the personal information collected through Ember under the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).
You can contact us at tech@emberfi.com.au about anything in this policy: questions, access requests, corrections, complaints.
This policy explains what personal information Ember collects, why, who we share it with (including service providers outside Australia), how we keep it secure, and how you can access, correct, or delete it. Your use of Ember is also covered by our Beta Terms.
2. What information we collect
Ember is a cash-flow management app. To do that, we need to collect:
- Account information: your email address and (optionally) your name. Created when you sign in.
- Financial transaction data: descriptions, amounts, dates, and account names from transactions you import. Imports happen by you (a) uploading a CSV from your bank, (b) forwarding emails to your Ember inbound address, (c) entering transactions manually, or (d) asking Ember AI to add them in chat.
- Account identifiers: only the last 4 digits of a bank account or card number, never the full number. We mask everything else on the way in.
- Categorisation, tagging and planning choices: the categories, flags (business expense, transfer, recurring, etc.), tags, notes, plans and goals you set.
- Conversations with Ember AI: the messages you send in chat and Ember's replies, stored so you can pick up where you left off, and facts you ask Ember to remember (you can see and edit these in Settings).
- Email metadata for forwarded emails: sender, subject, date. Raw email bodies and attachments are stored only as long as needed to parse them, then redacted or deleted (see §9).
- Notification subscription: if you turn on notifications, your browser's push endpoint and keys, so we can send them.
- Connected apps: if you connect an AI app (for example Claude) to Ember, a record of that authorisation, so you can see and revoke it in Settings → Ember AI → Use Ember in other AI apps.
- Product usage records: which features and screens you use and when (for example, that you completed an onboarding step, committed an import, or sent a chat message), so we can tell whether Ember is working for beta users. These records never contain transaction descriptions or amounts. We are introducing them during the beta.
- Problem reports and ideas: what you write when you report a problem or share an idea, plus the screen you were on, the app version and your browser type. If you leave Include this item's details ticked, the report also holds a snapshot of the item you reported (for example, the figures on a card, or which transaction it was), so we can check what you saw. Untick it to send only your message. We use reports only to fix problems and to reply to you.
- Web performance telemetry: basic page-load and navigation timings via Vercel Speed Insights. No third-party advertising or behavioural tracking.
We do not collect: your bank password, your full account or card number, government identifiers (TFN, Medicare, driver licence), health information, biometric data, or location data.
No bank connections. Ember does not connect to your bank and does not receive data through Open Banking / the Consumer Data Right (CDR). Every transaction we hold was provided by you, through one of the import methods above. If we ever offer bank connections, we will update this policy and ask for your consent before any bank data is collected.
3. Why we collect it
We collect the information above to:
- Provide the core service: show you your transactions, summaries, forecasts, and cash-flow insights.
- Categorise transactions automatically using a mix of deterministic rules and an AI fallback (see §8.1).
- Answer your questions in Ember AI chat and prepare insights and plan checks (see §8.2).
- Detect and prevent duplicate imports.
- Communicate with you about your account (account-related email and notifications you turned on, see §4).
- Understand how beta users use Ember, diagnose errors, and improve the product.
- Meet our legal obligations, including responding to lawful requests.
We will not use your information for any other purpose without first telling you.
4. Direct marketing (APP 7)
We do not use your personal information for direct marketing. We will not send you promotional emails, push notifications, or third-party offers. The only emails we send are operational: sign-in links, security notifications, and material changes to this policy or our terms. Push notifications are sent only if you turn them on, and only about your own finances.
If we ever decide to send marketing communications, we will tell you first and provide a clear opt-out in every message, as required by APP 7 and the Spam Act 2003 (Cth).
5. Anonymity and pseudonymity (APP 2)
Under APP 2 you have the right to deal with us anonymously or under a pseudonym where lawful and practicable. Because Ember holds your financial transaction data and supports households with shared visibility, using a real identifier (your email address) is required to keep your account secure and recoverable. You can choose any name (or no name) for display inside the app.
6. Who we share it with
Ember is a small operation. We use a short list of service providers to run it, and your data flows through them in the course of normal use. All are bound by contractual obligations and published privacy commitments.
| Provider | Role | Location of processing |
|---|---|---|
| Supabase Inc. | Database, authentication, server-side functions | Australia (ap-southeast-2, Sydney): your transaction and account data lives here. |
| Vercel Inc. | Web hosting and the servers that run the app | Ember's servers run in Sydney; Vercel's edge network and support operate globally, including the United States. Persisted data does not live on Vercel. |
| Anthropic, PBC | AI: categorisation, email and receipt parsing, Ember AI chat and insights (Claude API), including web searches Ember AI runs to answer general questions | United States. See §8 for what is sent and when. |
| Postmark (ActiveCampaign LLC) | Inbound email for forwarding; operational email delivery (sign-in links, security notifications) | United States. Used when you forward emails to your Ember inbound address, or when we send you an operational email. |
| GitHub, Inc. | Encrypted nightly backup of Ember's database | United States. Each night a copy of the database is made on GitHub's servers and encrypted there before it is stored, for 30 days. The key to read it is held offline by us, not by GitHub. |
| Your browser's push service (Apple, Google or Mozilla, depending on your device) | Delivering notifications | Varies by provider, including the United States. Only if you turn on notifications. The notification content is encrypted so the push service can't read it. |
Connected AI apps. If you connect an AI app such as Claude to Ember (Settings → Ember AI → Use Ember in other AI apps), that app can read your Ember data while connected, at your direction. What it reads is then handled by that app's provider under your own account and their privacy policy, not ours. You can disconnect at any time.
Household members. If you invite a partner into your household, they can see the household's shared accounts and transactions.
We do not sell your personal information. We do not share it with advertisers. We do not share it with insurers, employers, banks, or any other third party for commercial purposes.
We may disclose information if required by Australian law (for example, a court order or a regulator request). We will only disclose what is strictly required.
7. Cross-border disclosures (APP 8)
Some of our providers process information outside Australia (United States: Vercel, Anthropic, Postmark, GitHub; and, if you turn on notifications, your browser's push service). When we disclose your personal information to an overseas recipient, we remain accountable for that recipient's handling of it under APP 8.1.
Before using any overseas provider we check that they publish a privacy policy or data-processing agreement that aligns with the APPs, and we keep current copies of those documents in our internal records.
By using Ember you consent to these overseas disclosures for the purposes described in §3 and §8. You can limit what goes to Anthropic: switch off Settings → Ember AI → Use AI to categorise new merchants, and don't use Ember AI chat (see §8).
8. Automated processing with AI
Ember uses Anthropic's Claude models in two ways. Anthropic does not use API data to train its models, and retains request data for up to 30 days for abuse monitoring before deletion (per its commercial terms and Data Processing Addendum). Requests are processed in the United States (see §7).
8.1 Categorisation
Ember categorises transactions you don't have an existing rule for. Most categorisation is deterministic (your rules and our built-in merchant database). For unknown merchants, we send a small request to Claude to suggest a merchant and category, then save that suggestion as a rule for next time.
What we send: the transaction description, amount, an optional product hint extracted from a forwarded email subject (capped at ~200 characters), and (for receipt and email parsing) the email subject and body. Personal-information patterns are redacted server-side before the request leaves Australia: emails, phone numbers, BSB-shaped digits, credit-card-shaped digits, Australian street addresses, PO Boxes.
What we do not send: your email address, your name, your account balance, or your other transactions.
Significance: the only effect is to choose a merchant and category and create a categorisation rule. It does not change your account balance, move money, share information with third parties, or make any decision about you. Every suggestion can be overridden by a one-tap correction.
Opt-out: switch off Settings → Ember AI → Use AI to categorise new merchants. New transactions with unknown merchants will stay uncategorised until you classify them yourself.
8.2 Ember AI chat and insights
- Chat. When you message Ember AI, the conversation and the parts of your Ember data needed to answer are sent to Claude. That can include transaction descriptions, amounts, dates, merchant and category names, account names and balances, your plan, and summaries. Transaction descriptions are sent as they appear in your data and may contain other people's names (for example, a bank-transfer payee).
- Scheduled insights. On a schedule, Ember sends similar data to Claude to prepare your daily insight check, your weekly plan check, and a review of recurring charges it isn't sure about.
- What they do: explain, summarise and suggest. They never move money and don't make decisions about you. A change they propose to your records or plan is applied only when you confirm it.
- What we do not send: your email address, your password, or full account numbers (we don't hold them).
- Opt-out: chat runs only when you use it. The AI categorisation switch does not cover chat or scheduled insights; if you want scheduled insights turned off for your household, email us and we will switch them off.
This section is provided ahead of the APP 1.7 amendments (in force 10 December 2026) that require disclosure of automated decision-making involving personal information.
9. Email forwarding
If you set up email forwarding so bank CSVs and receipts land in Ember, those emails are received via Postmark and stored briefly in our database so we can parse them.
We minimise the footprint:
- The parser strips the email body, HTML, and attachments before logging. Only sender, subject, date, and a small extracted snippet are kept past initial parsing. The one exception is a bank CSV waiting for you (to map its columns, or to confirm an unfamiliar sender is yours): the file is kept until you import or dismiss it.
- A bank CSV is imported automatically only when it comes from an address on your trusted list. From any other address it waits until you say the sender is yours.
- Any remaining raw payload is automatically nulled after 90 days.
- You can revoke a forwarder at any time in Settings → Getting data in.
10. How long we keep your data
| Data | Retention |
|---|---|
| Account record (email, settings) | While your account is open. Deleted on close. |
| Transactions you imported | While your account is open. Deleted on close. |
| Categorisation rules you created | While your account is open. |
| Ember AI conversations and remembered facts | While your account is open. Deleted on close. You can edit remembered facts in Settings. |
| Product usage records | While your account is open. Deleted on close. |
| Problem reports and ideas | The item's details are removed 90 days after a report is closed; the rest is deleted after 24 months. Deleted on close. |
| Notification subscription | Until you turn notifications off or close your account. |
| Raw email payloads (Postmark) | Auto-redacted at 90 days. |
| Encrypted database backups (GitHub) | 30 days, then deleted automatically. After you close your account, your data can remain in these encrypted backups until they expire. |
| Web performance telemetry | Aggregated by Vercel; we do not retain individual logs. |
| Security audit trail (sign-ins, security-relevant events) | Up to 12 months after account close, for incident traceability. |
When your account is closed (see §11), personal information is deleted unless we are required by law to keep it.
11. Access, correction, deletion (APP 12 / APP 13 / APP 11.2)
You can:
- Download everything we hold about you in Settings → Privacy & your data, or ask us at tech@emberfi.com.au and we will provide it within 30 days.
- Correct anything inaccurate: most data is yours to edit directly inside Ember. For anything you cannot edit yourself, email us.
- Close your account and have your data deleted in the same Settings page, or by emailing us. Closing starts a 30-day grace period (sign back in to cancel); after that your data is permanently deleted, subject to the retention exceptions in §10.
Access and correction are free. We will only refuse a request in the limited circumstances allowed under the Privacy Act, and we will tell you why in writing if we do.
12. How we keep it secure (APP 11)
Reasonable steps we take, in plain language:
- All data is encrypted in transit (HTTPS / TLS 1.2+) and at rest (Supabase-managed storage encryption).
- Database access is gated by row-level security: your data is only readable by you and any household members you explicitly add.
- Account numbers are stored as last-4 only and enforced at the database layer.
- Personal-information patterns are stripped from categorisation and parsing requests before they leave Australia.
- Operational accounts (Supabase, Vercel, GitHub, the password manager, our admin email and Apple ID) are protected by multi-factor authentication.
- We follow a written breach-response plan aligned with the Notifiable Data Breaches scheme (Part IIIC of the Privacy Act).
No system can be guaranteed perfectly secure. If we believe a breach has occurred that is likely to cause serious harm, we will notify you and the Office of the Australian Information Commissioner (OAIC) as required by law.
13. Cookies
Ember sets a small number of cookies, all first-party:
- An authentication session cookie (required to keep you signed in).
- A CSRF cookie (required for safe form submissions).
- A view-mode preference (Us / Me toggle).
We do not set advertising or cross-site tracking cookies.
14. Children
Ember is not intended for use by anyone under 16. We do not knowingly collect personal information from children. If you believe a child has provided us information, contact us and we will delete it.
15. Not financial advice
Ember provides general financial information only: categorised summaries, forecasts and explanations of your own spending and savings. Nothing in the app is personal financial advice for the purposes of the Corporations Act 2001. If you want personal advice tailored to your circumstances, see a licensed financial adviser.
16. Complaints
If you think we have breached the APPs, please tell us first: email tech@emberfi.com.au with “Privacy complaint” in the subject. We will acknowledge within 7 days and respond substantively within 30 days.
If you are not satisfied with our response, you can lodge a complaint with the Office of the Australian Information Commissioner (OAIC):
- Web: oaic.gov.au/privacy/privacy-complaints
- Phone: 1300 363 992
17. Changes to this policy
We will update this policy when our practices change. The Version and Effective from at the top of the page indicate the current version; prior versions are preserved in our git history. Material changes will be notified by email to active users.