Privacy Policy
Effective date: 11 November 2026
Document version 2026-11-11
This policy explains what personal information Bills Compared collects during the closed household beta, how uploaded bills are redacted and processed, who we share information with, how long we keep it and how to contact us. It should be read together with the Terms of Service.
At a glance
What we collect
- Account and household details: your email, property details, bill figures, corrections and saved comparisons.
- Other information: invitation records, feedback, usage analytics and security logs.
- Storage: the app, database and private bill storage are in Singapore.
How bills are processed
- We redact in the US: personal details are masked on systems we operate before external AI extraction.
- External AI: receives verified redacted pages and text only, with request storage disabled and bill content excluded from model training.
- Originals and working data: originals are deleted before external extraction unless held as described below; plaintext lasts at most one hour.
What we keep
- Redacted copies and figures: kept to check and improve bill reading, linked to your account for 30 days, then kept without that link.
- Security holds: uploads flagged for suspected abuse may be kept encrypted for up to 30 days, including during account deletion.
- Investigation holds: during the beta, failed uploads may be kept for up to 48 hours; deleting the upload or account ends this hold.
Your controls
- Upload is optional: enter bill figures manually instead.
- Your account and information: delete your account in the app or contact us for access, corrections, deletion or complaints. Security holds can delay final deletion.
- No advertising or data sales: we do not sell or rent personal information or share your bills with retailers.
Overview
This Privacy Policy describes the personal information we collect when you use Bills Compared, how we use and disclose it, how uploaded bills are redacted and processed, how we protect it, how long we keep it, and how to contact us about a privacy request or complaint.
Bills Compared is a closed, invitation-only household beta for electricity comparisons. It is designed for people who want to compare retailer plans using their own bill, and it is not intended for business use.
Who we are and scope of this policy
Bills Compared is operated by 0x234 Pty Ltd (ABN 91 660 024 171), an Australian proprietary limited company based in South Australia, Australia. In this policy, "Bills Compared", "we", "us" and "our" refer to 0x234 Pty Ltd.
This policy applies to the Bills Compared website, application, bill processing, invitation and referral features, service emails and support. It applies to visitors, account holders and beta members, and to people who receive an invitation.
We handle personal information in accordance with this policy and, where it applies, the Privacy Act 1988 (Cth), including the Australian Privacy Principles. Personal information means information or an opinion about an identified individual, or an individual who is reasonably identifiable.
Key terms
In this policy:
- "Bill" means an electricity bill that you upload as a PDF or images, or the figures from a bill that you enter manually.
- "Extraction" means the automated process that reads the billing period, rates, usage and charges from a redacted bill.
- "Redaction" means the masking of names, street addresses, account and payment references, NMI and meter identifiers, and other personal fields on a bill within systems we operate and manage, before external AI extraction.
- "Redacted copy" means the verified redacted pages of a bill and the text read from them. A redacted copy is not your original bill.
- "Extraction data" means the encrypted, normalised record of an extraction, including the figures read from a bill and the corrections you make when you save the bill. It excludes the original bill, its filename, its unredacted text, the raw hosted response, prompts and model reasoning.
- "Security hold" means the encrypted quarantine applied to an upload that fails, or is awaiting, a security decision.
- "Investigation hold" means the encrypted copy of an upload that failed during redaction, and any partly redacted working copy, kept for up to 48 hours during the closed beta so we can find out why and improve the process. It is viewable only by our administrators, every access is logged, and it is deleted at the end of the window or sooner when the upload succeeds on a re-run or when you delete the upload or your account.
- "Content-free aggregate" means counts and bounded technical dimensions, such as provider, layout, page count and outcome, that contain no bill content and cannot identify a person.
- "NMI" means the National Metering Identifier for an electricity connection point.
Minimum age
The service is intended for adults. You must be at least 18 years old to create an account. We do not knowingly collect personal information from anyone under 18. If you believe a child has provided personal information to us, contact us and we will delete it.
Our role in handling personal information
We decide how and why personal information is handled for account creation, sign-in, beta admission, bill processing, comparisons, security, analytics, support and legal compliance.
A bill sometimes contains information about other people, such as a joint account holder or a previous occupant. You are responsible for having the right to submit a bill. We treat all information in an uploaded bill as covered by the redaction and processing rules in this policy.
You do not provide the future user's email address when you issue a join code. For an older email invitation, we hold the recipient address supplied when it was issued and use it to send the invitation and any resend you request. Only invite people who have asked for an invitation or who you reasonably expect would welcome one.
Personal information we collect
Account and sign-in information
- Your email address, which identifies your account and receives sign-in codes and service emails.
- Sign-in records, including when a code was requested or verified, the outcome, and a hashed fingerprint of the code so that it cannot be reused. The code itself is not stored.
- The versions of the Terms of Service and Privacy Policy you accepted, and when.
- An optional display name and, once you complete setup, the postcode and state of your household.
- If you sign in through a third-party login provider, the provider name, the identifier the provider assigns to you and your username with that provider.
- Account activity timestamps, such as your last sign-in and last activity.
Household and property information
- A property name of your choosing, its postcode and state, and the customer type (residential).
- The property's NMI where you provide it or accept one found on a bill. It is used locally to match bills to the property and to check plan availability.
- The usage profile and whether the property has a smart meter, controlled load, solar, a battery or an electric vehicle.
- Household setup progress, including the current step, drafts and content-free stage timings.
Bills and comparisons
- The billing period and number of days, retailer and plan names, rates, usage, supply charges, discounts, solar export details and totals from a bill.
- Whether the figures came from an upload or manual entry, and the extraction provenance.
- The extracted result, your corrections, calculation results and saved comparisons.
People you invite
- For a new join code, its status, expiry and replacement history; the person who will use it has not provided an email address at issue. For an older email invitation, the recipient address supplied when it was issued, its status, expiry and delivery outcome. We use that address only for the invitation and any resend you request.
Support and correspondence
- If you contact us, the correspondence and the contact details you provide, so that we can respond and keep a record of the request.
Feedback and surveys
- Your answers to the short survey we offer after your first comparison, including any comments, the price you think is fair and whether you agree to be contacted about your answers.
- Feedback you send from the app, the page you sent it from and your browser's user agent. A report about a comparison also records the property, bill and plan it relates to.
Usage, security and log data
We automatically collect technical data needed to operate, secure and diagnose the service:
- IP address, browser type and version, request paths, timestamps and request outcomes.
- Authentication audit records covering the sign-in mechanism, action, result, IP address and user agent, used to detect and investigate misuse.
- We use rate-limit records for sign-in code requests, invitation issuance and email delivery, join-code entry and replacement, and upload capacity. Email request limits use a one-way hash of your email address. Invitation-entry counters are short-lived; they store one-way hashes of trusted network addresses.
- Bill-processing lifecycle records such as status, timings, page count, input type and failure codes. These records never contain bill content.
- Content-free onboarding measurements: which setup stage was reached, how long it took and the outcome.
When our first-party privacy CAPTCHA is enabled, it uses short-lived, single-use verification and a small computation in your browser to limit automated code requests. It keeps coarse counts of interaction types in your browser for up to two minutes and sends a bounded summary when you request verification. It does not read typed characters, field values or pointer coordinates. A summary that suggests synthetic interaction can require an image or audio challenge; it cannot establish that you are human or waive the computation and request limits. We do not retain these summaries on the server. We retain aggregate decision counts and short-lived verification and quota state, using keyed hashes for quota identifiers. Once a challenge is required, it can remain required across tabs with the same CAPTCHA session until it is solved or its five-minute lifetime ends. People sharing a network address may also encounter a challenge when that address reaches its short-term allowance. CAPTCHA processing runs on our own server without an external CAPTCHA or speech service. Completing the check permits a limited sign-in email request. Email sign-in still requires the separate code sent to your email address. Google sign-in is available when enabled.
We run Umami ourselves, on our own infrastructure, to understand how Bills Compared is used. Nothing is sent to Umami's company. On the five public pages (home, about, FAQs, terms and privacy) and the sign-in page it records path-only page views, which links, buttons and FAQ questions are used, how far pages are scrolled, and the sign-in steps (started, code resent, code failed and completed), never your email address or code. A Do Not Track signal from your browser turns off Umami analytics, including session replays.
For signed-in members it records, without cookies and without any account, household, property or bill identifier:
- Screen views: which type of screen was opened, such as a saved bill, and never the specific record.
- App actions: named actions such as starting a bill, choosing a plan or opening a comparison, with fixed labels such as which wizard step. Nothing you type, no amount, rate, address, NMI or name is included.
- Signals that something went wrong: an error, a blocked step, or leaving the bill wizard part-way.
- Session replays and heatmaps: a recording of how app screens are used, so we can see where steps such as adding a bill are hard to follow. Everything you type is masked; NMIs, email addresses, names, home names, postcodes and states are hidden; and home and bill references are removed from page addresses before anything is recorded. These are kept for 30 days.
Separately, the application itself records which days each account uses the app. It keeps the date only, not what was done, until the account is deleted. We use it to understand whether the service is useful and to run the beta. This activity-day record is part of running your account, so a Do Not Track signal does not affect it. Analytics sets no cookies and does not track you across websites.
Server-side error monitoring records error details and request metadata when something goes wrong. Application, supervisor and monitoring output contain no bill content.
Bills and extraction data
Bills may contain electricity usage, rates, charges, account details and property information. Bills Compared uses relevant bill information to prepare a comparison that you can review. Uploading is optional; manual entry is always available.
An upload travels over TLS and is encrypted before it is stored. Original bills and limited household information needed for processing, including NMI matching, are transferred to systems we operate and manage in the United States. We run automated security checks, text recognition and a vision model there to identify and mask names, street addresses, account references, payment references, NMI and meter identifiers, and other personal fields. We manage the processing software, access controls and retention and deletion settings within these systems.
Every final page passes mandatory checks on our systems before verified redacted pages and regenerated redacted text are sent to one or more external AI services. These services extract billing periods, rates, usage and charges. Original, unredacted bills are never sent to external AI services.
We may compare an NMI with the household record within our processing systems. When a candidate needs attention, it is shown only in a temporary, owner-only review and can be saved or dismissed without blocking the bill review. The trusted property NMI is never included in an external AI request.
Original uploads and unredacted working data are deleted after verified redaction on our systems and before external AI extraction. Plaintext working data has a one-hour maximum lifetime. An encrypted original subject to a security hold is the exception to the ordinary original-upload deletion schedule. An investigation hold is the other exception during the closed beta: the upload and any partly redacted working copy are kept for up to 48 hours, then deleted.
For every upload that passes redaction, we keep a redacted copy of the bill: the verified redacted pages and the text read from them. We also keep the extraction data: the figures read from the bill and, when you save the bill, the corrections you made. This includes uploads where external AI extraction starts but fails. NMI and meter identifiers are masked in every redacted copy.
A redacted copy and its extraction data stay linked to your account for 30 days after extraction finishes, so we can look into problems you report. After that we remove the links between the redacted copy and your account, property and bill, remove the postcode from the extraction data, and keep the redacted copy and extraction data for as long as we need them to check redaction and improve how Bills Compared reads bills, including for internal analytics.
A redacted copy is not your original bill, but it may still show the retailer, plan, billing dates and figures, and the postcode and state of the supply address, including after it is unlinked. Deleting a saved bill does not delete its redacted copy.
During first-time household setup only, the allowlisted structured setup draft and its linked sanitised extraction result can be retained for up to 30 days after the last Continue or Finish later action. They are cleared promptly when the first comparison succeeds; content-free stage times are retained for service measurement.
Security quarantine
Every upload is checked on our processing systems for signs of abuse, such as embedded instructions aimed at automated processing or unsafe images, before it reaches the redaction model. Uploads flagged for suspected abuse or awaiting a security decision may be held in encrypted security quarantine for up to 30 days for authorised security review. This is separate from the redacted copies we keep; cancelling processing does not remove a security hold, and deleting the upload or your account ends an investigation hold at once.
Security-held originals are encrypted with a separate key ring, are not sent to external AI services, and are deleted at the fixed expiry. Review or cancellation does not extend that expiry. Access to a security hold is limited to authorised staff and is audited without putting bill content in the audit record.
How we use personal information
We use personal information to:
- create your account, sign you in and confirm beta membership through invitations;
- process bills, prepare comparisons and keep your saved bills and comparisons;
- send the service emails needed to operate your account;
- administer referral invitations and send older email invitations you request;
- check redaction and improve how Bills Compared reads bills, using redacted copies, extraction data, the corrections you make when you save a bill and content-free aggregates, including for internal analytics;
- open redacted copies to investigate problems and review how the service performs;
- secure the service, prevent abuse, enforce the Terms of Service and investigate incidents;
- diagnose faults and maintain reliability;
- read and respond to feedback and survey answers, look into problems you report, and decide what to build and how to price the service;
- respond to your requests and correspondence; and
- comply with legal obligations.
No sale of data or advertising
We do not sell, rent or trade personal information. We do not show advertising, share information with advertisers or build marketing profiles.
We use external AI services under terms that exclude bill content from model training. External AI extraction requests are sent with request storage disabled.
We do not disclose bills, household details or personal information to electricity retailers.
Service communications
We send only the emails needed to operate the service: sign-in codes, a welcome message, older email invitations and notices about the outcome of bill processing. New join codes are shown to the member who issues them; we do not send them to a recipient. Processing notices tell you whether a bill is ready to review or could not be read; they do not contain the bill.
If you don't answer the feedback survey after your first comparison, we send one reminder the next day, by email unless you have already seen it in the app. It is the only reminder, and it does not contain bill details.
We do not send marketing emails during the beta. Operational alerts about the service go to our own operators and are content-free. Feedback you send from the app is emailed to our team so we can read it and reply to you.
How we disclose personal information
We disclose personal information only:
- to the service providers listed in the next section, for the purposes described there;
- to authorised staff and contractors bound by confidentiality obligations, for security review of a quarantined upload or to open redacted copies and extraction data when investigating problems and reviewing how the service performs;
- where required or authorised by law, including in response to a lawful request from a regulator, court or law enforcement body;
- to a successor as part of a merger, acquisition, restructure or sale of assets, in which case this policy continues to apply; or
- with your consent.
Third-party services
The following services support Bills Compared. The information involved is described for each.
Cloud hosting and storage
- Purpose: cloud hosting for the application and database, and private object storage for encrypted bill artefacts, redacted copies and quarantine bundles, plus the infrastructure for our US bill-processing systems. We operate and manage the bill-processing software ourselves.
- Information involved: account, household, bill and comparison data, encrypted bill artefacts, original bills and temporary working data used by our processing systems, logs and backups.
Cloudflare
- Purpose: DNS, TLS termination, caching and protection against attacks for the public site and application.
- Information involved: IP address, request metadata and the encrypted traffic that passes through it.
- External resources:Website , Privacy Policy and Terms .
External AI extraction services
- Purpose: extraction of billing periods, rates, usage and charges from verified redacted bill pages. We may use one or more external AI services for this purpose.
- Information involved: verified redacted page images and regenerated redacted text only. Requests are made with request storage disabled. Originals, unredacted pages, your email address and the trusted property NMI are never sent.
Sentry
- Purpose: server-side error monitoring to diagnose faults and improve reliability.
- Information involved: error details, request metadata and application state at the time of an error. Bill content is excluded.
- External resources:Website , Privacy Policy and Terms .
Umami
- Purpose: the analytics tool for public pages and the signed-in app. We run it ourselves on our own infrastructure, so its data is not sent to Umami's company.
- Information involved: path-only public and sign-in page views, which links, buttons and FAQ questions are used, how far public pages are scrolled, sign-in steps (never your email address or code), app screen types, named app actions, signals that something went wrong, and masked session replays and heatmaps kept for 30 days. No account, household, property or bill identifiers, typed values, cookies or cross-site tracking.
- External resources:Open-source project .
Google Fonts
- Purpose: the Material Symbols icon font used in the interface.
- Information involved: when your browser requests the font, Google may receive your IP address, browser information and the requested font family.
- External resources:Website , Privacy Policy and Terms .
Email delivery
- Purpose: delivery of sign-in codes, welcome, invitation and bill-processing emails through a transactional email provider.
- Information involved: email addresses, the content of service emails and delivery metadata. Invitation email archives that contain links are purged routinely.
- Providers: Amazon SES delivers transactional service emails from Sydney, Australia. Messages you send to our team are handled through Fastmail's US mail servers.
Data storage and overseas disclosure
We host the application and database and store account, household, bill and comparison data in Singapore. Encrypted bill artefacts, redacted copies and quarantine bundles are stored in a private object store in the same Singapore region.
We also operate and manage bill-processing systems in the United States. Original, unredacted bills and limited household information needed for processing are transferred there for automated security checks, text recognition, NMI matching and redaction. We manage the processing software, access controls and retention and deletion settings within these systems. The retention periods and security-hold and investigation-hold exceptions in this policy apply to this processing.
External AI services process only verified redacted pages and redacted text in the United States. Sentry stores error data in the United States. Cloudflare and Google operate globally distributed infrastructure.
Where we disclose personal information to an overseas recipient, we take reasonable steps to ensure that the recipient handles it consistently with this policy and the Australian Privacy Principles, including by limiting what is sent, disabling storage where the provider offers it, and relying on the provider's contractual privacy commitments.
Security
We take reasonable steps, appropriate to the sensitivity of the information we hold, to protect personal information from misuse, interference, loss, unauthorised access, modification and disclosure. Measures currently in place include:
- TLS for all traffic between your browser and the service;
- encryption at rest for uploaded bills, for redacted copies and extraction data, and for quarantine bundles, each with its own key ring;
- deletion of original uploads before external AI extraction, and a one-hour limit on plaintext working data;
- a processing worker that holds no database, storage or encryption credentials and reaches the application only over a private network;
- one-time sign-in codes with attempt limits and lockouts, and rate limits on sensitive actions;
- logged access for any authorised review of a security hold or redacted copy; and
- logs, monitoring and reports that exclude bill content.
No method of transmission or storage is completely secure, so we cannot guarantee absolute security. The security of information you keep on your own devices, forward from emails or share with others is outside our control.
Retention, deletion and backups
We keep personal information for as long as reasonably necessary to provide the service, maintain your account, meet legal obligations, resolve disputes, maintain security and prevent abuse. The table below sets out the current approach.
| Data category | Retention approach |
|---|---|
| Account, profile and legal acceptance records | Kept while the account exists, unless you delete the account or ask us to. |
| Properties, saved bills and comparisons | Kept while the account exists or until you delete them through the service where that option is available. Deleting your account deletes them too. Saved bills and comparisons have a separate account lifecycle from redacted copies and extraction data. |
| Original uploads and plaintext working data | Deleted before external AI extraction. Plaintext working data lives at most one hour. |
| Sanitised extraction result awaiting review | Expires 24 hours after completion unless saved to a bill, or up to 30 days when linked to first-time household setup. |
| Redacted copies and extraction data, linked to your account | Linked for 30 days after extraction finishes, then unlinked. If you delete your account, or ask us to, while they are still linked, we delete them together with their stored files. |
| Unlinked redacted copies and extraction data | Kept for as long as we need them to check redaction and improve the service. They are no longer linked to you. |
| Security quarantine bundles | Fixed expiry 30 days after quarantine. Not extended by review or cancellation. If you delete your account, an upload under a security hold, and the property it belongs to, are kept until the hold ends at its fixed expiry, and are then deleted too; your deletion request stays pending until then. Your account's email address is also kept, unusable, until the hold ends. |
| Investigation hold (closed beta) | Up to 48 hours. Ends sooner when the upload succeeds on a re-run, or when you delete the upload or your account. |
| Invitation and referral records | Invitation and referral records are kept for the life of the beta programme for admission and audit purposes. Records of join codes issued and replaced are kept indefinitely, including after the beta programme ends; there is no automatic purge when it ends. These records do not contain the join codes or the future user's email address. They may remain linked to the account that requested the operation or to related invitations while those records exist. Deleting an account or invitation removes its link, but does not delete the operational record. Email archives containing invitation links are purged routinely. New join-code records do not include the future user's email address; older email invitations retain the address supplied when they were issued. If you delete your account, we delete your beta membership and every invitation you redeemed or that was addressed to you. Referral records you issued are kept for programme records and are no longer linked to you; older email invitations retain the address supplied when issued. |
| Authentication, security and server logs | Kept for a limited operational and security period. If your account is deleted, authentication security logs are kept for that period no longer linked to your account. Email rate-limit records are keyed by a one-way hash of your email address. Short-lived invitation-entry counters store one-way hashes of trusted network addresses. |
| Content-free quality and onboarding aggregates | Kept indefinitely. They contain counts and technical dimensions, not bill content. |
| Support correspondence | Kept as needed to respond, maintain a record and resolve issues. |
| Survey answers and feedback messages | Kept while the account exists, unless you delete them or the account, or ask us to. A copy of each feedback message also stays in our team's email as support correspondence. |
Redacted copies and extraction data are encrypted at rest. Access by authorised staff is logged without putting bill content in the log. We do not try to re-identify unlinked copies.
Saved bills and comparisons have a separate account lifecycle from redacted copies and extraction data. Deleting a saved bill does not delete its redacted copy.
Content-free quality aggregates are kept indefinitely. They contain counts and bounded technical dimensions, not bill content, and support long-term accuracy measurement. Our self-hosted analytics records usage without account or bill details, and replays and heatmaps are kept for 30 days. The dates each account uses the app are kept until the account is deleted. Setup answers, bill values, help contents and account or household identifiers are not included in analytics.
You can delete your account while signed in, or ask us. To delete it yourself, you type "delete my account" and enter the 6-digit code we email to your address. You are signed out everywhere immediately, and deletion begins straight away.
When you delete your account, we delete the account, your profile, email addresses and linked sign-in identities, your properties, saved bills and comparisons, your onboarding data, feedback and survey answers, and legal acceptance records. We also delete your beta membership and every invitation you redeemed or that was addressed to you, and any redacted copies and extraction data still linked to your account within their 30 days, together with their stored files, and the emails sent to you that are held in our systems.
Unlinked copies are not affected because they are no longer linked to you. An upload under a security hold, and the property it belongs to, are kept until the hold ends at its fixed expiry of up to 30 days, and are then deleted too. While an upload is under a security hold, your account's email address is also kept, unusable and never used for sign-in, until the hold ends. After that it is deleted with the rest. An upload under an investigation hold is deleted with your account, which ends the hold at once. Referral records you sent are kept for programme records and are no longer linked to you. New join codes do not record the future user's email address; older email invitations retain the address supplied when they were issued. We keep the confirmation email as the record that your account was deleted. We also keep limited security records for a limited period: authentication security logs are kept no longer linked to your account. Email rate-limit records use a one-way hash of your email address. Residual copies may also remain in encrypted backups for a limited period, and a copy of each feedback message stays in our team's mailbox. We may retain limited information where the law requires it or where it is needed to resolve a dispute or prevent abuse.
Your choices and controls
- Manual entry: you can enter bill figures instead of uploading a bill.
- NMI review: a candidate NMI found on a bill is shown only to you and can be saved or dismissed.
- Remembered accounts: the sign-in screen remembers email addresses only if you ask it to, and only on that device.
- Referrals: you choose whether to invite anyone, and whom.
- Analytics: a Do Not Track signal from your browser turns off Umami analytics, including session replays. It does not affect the activity-day record, which is part of running your account.
- Account deletion: delete your account yourself while signed in, or ask us; see Retention, deletion and backups above for what this deletes and keeps.
Access, correction, deletion and complaints
You may request access to, or correction or deletion of, the personal information we hold about you by contacting us using the details below. You can also update your household details, delete saved bills, and delete your whole account directly in the application; see Retention, deletion and backups above for what account deletion includes.
We may need to verify your identity before acting on a request, and we may refuse, limit or defer a request where the law permits or requires it. We aim to respond within 30 days.
If you have a privacy complaint, contact us first with enough detail for us to investigate. We will review the complaint and respond within a reasonable period. If you are not satisfied with our response, you may contact the Office of the Australian Information Commissioner (OAIC).
Data breaches
If a data breach occurs, we will contain and assess it and, where required by the Notifiable Data Breaches scheme or other applicable law, notify affected individuals and the Office of the Australian Information Commissioner.
We will also take steps to remediate the incident and to reduce the risk of similar incidents occurring again.
Links to other websites
The service may link to retailer websites and other third-party sites, for example so that you can check a plan's current terms. Those sites have their own privacy practices, which we do not control. Review their policies before providing personal information to them.
Changes to this policy
We may update this policy from time to time, for example when the service, our providers or the law change. Each version carries a document version and an effective date at the top of this page.
Where a change is material, we will give reasonable notice before it takes effect, for example by email or by a notice when you next sign in, and we may ask you to acknowledge the new version before you continue.
Contact us
If you have questions about this policy, or wish to make a privacy request or complaint, contact 0x234 Pty Ltd at [email protected].