Search all public records

3D connections

Political receipts

Government contracts

Registers of interests

The newest additions and deletions recorded in parliamentarians' registers of interests, in their own words.

Sources: Registers of Members' and Senators' Interests, 48th Parliament ↗︎, entries as declared, not verified by OPAX; and the Queensland Register of Members' Interests, 58th Parliament ↗︎, facts and links only. Additions and deletions carry the date the register records. A gift or trip with no organisation match names one the AEC and lobbyist registers do not list under that spelling. Organisation matches to AEC Transparency Register returns, CC BY 4.0 ↗︎, the lobbyist registers and FITS use exact normalised names.

The corpus in numbers

corpus loading…

In the live index

Sources loaded

How the corpus is collected and what is known to be missing: Methods · About OPAX · OPAX on X · OPAX on Facebook · OPAX on Instagram

What OPAX is

OPAX, the Open Parliamentary Accountability Exchange, has one intent: to put as much of the open data about Australian politics as possible in one place, cross-referenced and citable, so that the blind spots become findable. What a politician said on the record, how they voted, what they declared, who gave money to their party, who lobbied whom, which grants and contracts followed: each of these is published somewhere, in its own format, under its own terms, and almost never beside the others. Put side by side, a politician who gives two hundred speeches about a problem but votes against every reform, or an industry that donates millions while its regulation stalls, leaves a paper trail. OPAX makes that trail searchable and citable. It started as speeches and donations; it now also carries the votes those speeches led to, the bills those votes decided, the government grants and contracts that sometimes follow the same money, and the registers that record who lobbies whom. Every claim on the site links back to the primary record it came from, because a blind spot is only worth finding if someone else can check it.

OPAX contains the names and images of people who have died.

What you can do here

• Ask: put a question to the speech corpus (widen it to the recorded divisions with one checkbox) and get an answer written only from the passages retrieved for it. Every claim is cited; every citation opens the actual speech at a stable, linkable page; if the record is thin on a question, the answer says so.
• Search: hybrid semantic and keyword search with reranking, filterable by speaker, party, parliament and year, with citation-ready exports.
• Money map: the largest disclosed donors in three dimensions, ringed by industry around the parties they gave to, with a year range you can drag, a words layer showing who speaks on each industry's debates, and a grants layer showing which of those donors also collect government money.
• Reports: six standing investigations — climate & energy, gambling, housing, immigration, First Nations and media ownership — drawing on parliamentary debate, government announcements, legislation and financial records, refreshed as the record grows.
• Explore: the Time Machine (dial up any year since 1998 and see what parliament was arguing about), the tide (which debates are rising or fading), the record quiz, the ledger (every disclosed donation flow in one exportable table) and who gets the grants.
• Bills: a registry of federal bills since 2013, each one linked to the divisions that decided it and the speeches made about it, with a plain-English summary of what its explanatory memorandum says.
• Encyclopedia: an entry for every parliamentarian, party, donor and topic, with quick facts, voting record, declared interests, expenses and the money map narrowed to that entity.

The record

The last two rows above are not speeches: recorded divisions and AEC donation returns share the corpus's citation and search plumbing, so they are counted here even though the donations themselves are described in full below. The speech rows are filtered to the era of currently serving parliamentarians (13 March 1993 onward), deduplicated across overlapping sources, and stripped of procedural noise (division roll-calls, chair interjections, day indexes). Federal Hansard is Commonwealth copyright, reproduced here under the CC BY-NC-ND terms that cover the official transcript; each state parliament sets its own copyright terms, and OPAX reproduces and cites speeches for research rather than republishing whole documents commercially — check the source link on any document before quoting it commercially.

Full detail, model identity and known defects: methods & how to cite OPAX · machine-readable manifest: corpus.json.

The money

Every federal donation disclosed to the AEC since 1998 is loaded — 199,233 rows — and the money map plots the 250 largest donors against 11 parties as 662 flows, built from 127,658 of those rows after excluding public funding, internal party transfers and donations from government-linked entities. Queensland, Victoria and Tasmania publish their own donation registers under an open licence, and OPAX runs the same map over each: Queensland (250 donors, 402 flows from 22,703 gifts), Victoria (250 donors, 291 flows from 3,416 donations) and Tasmania (166 donors, 172 flows from 221 donations, because its disclosure scheme is only a year old). State and federal totals are never added together, because AEC returns already fold in what a party's state branches raised.

The newest layer is government grants. Every Commonwealth grant award published on GrantConnect since the register opened at the end of 2017 (360,058 awards, $235.5 billion, CC BY 3.0 AU) and every Queensland Government funding line since 2017-18 (230,007 awards, $85.7 billion, CC BY 4.0) are matched to the donor register by ABN wherever one is published: 763 Commonwealth recipients ($26.3 billion, 11% of the register) and 489 Queensland recipients ($3.3 billion, 4%) are also donors. On the money map itself, 30 of the 250 largest federal donors and 27 of the 250 largest Queensland donors also collected grants — $1.0 billion and $334 million between them — shown as a toggleable layer with its own flows from a single grantor node. A donor receiving a grant is a fact on the public record, not a finding; the grants explorer states plainly what share of a recipient's dollars arrived while a party it had donated to held office, and nothing stronger.

Alongside the donations sit an uncapped roster of 438 associated entities, third parties, significant third parties and political campaigners that raise or spend on politics without being a party — everything above $100,000 in any year from the AEC's own annual returns — and, separately, the parties' own lodged debts and discretionary benefits. Six lobbyist registers (federal, New South Wales, Queensland, Victoria, South Australia and Western Australia) are loaded in full: on the money map, 133 of the 250 largest federal donors also show up as a registered lobbying client or a name in a ministerial diary — 102 as lobbying clients, 92 in one of 61,499 disclosed meetings between ministers and everyone they met, from the New South Wales Cabinet Office and the Queensland Cabinet Office. Queensland alone also publishes who lobbied whom and when: 8,235 logged contacts since September 2016. A separate federal register, the Foreign Influence Transparency Scheme, tracks who works in Australia for a foreign government or political organisation for the purpose of political influence; OPAX carries the whole public register (145 registrants, 728 declared activities) and shows it on any donor, lobbying firm or parliamentarian page it matches, always with the reminder that registering is a legal disclosure, not a finding of wrongdoing.

Every donation, meeting and grant figure here is a floor, not a ceiling: disclosure schemes only require reporting above a threshold, so smaller gifts and quieter meetings leave no public trace. New South Wales and South Australia's political donations are not on OPAX at all — New South Wales' own terms forbid automated collection of its disclosure portal, and South Australia banned political donations from 1 July 2025. Western Australia, the ACT and the Northern Territory publish their donations, but under terms that do not permit republishing them here; that data is held for internal research only and nothing from those three jurisdictions appears on the site.

Votes and bills

Every recorded division OPAX could get in a structured form — 13,867 of them, federal divisions from TheyVoteForYou and state divisions parsed from New South Wales, Victorian and Queensland Hansard, 1998 to today — is a citable document in the search index in its own right, and 962 sitting and former parliamentarians (622 federal, 133 New South Wales, 122 Victorian, 85 Queensland) carry a voting record on their own page. Most questions in every chamber are decided on the voices and leave no division at all, so "no recorded vote" never means "did not vote".

A federal bill registry now covers every bill introduced from the 43rd Parliament (2013) to today: 2,969 bills, 31,377 progress events and 19,958 links out to the divisions, speeches and Acts that followed from them. 13,949 of those links are speeches that name the bill on a day it was genuinely before the chamber — checked against the bill's own progress record, not guessed from a topic string, because federal Hansard topics from 2013 on carry only the bare word "Bills". 1,698 of the 2,969 bills carry a three-sentence, model-written summary of what their explanatory memorandum or Bills Digest says, each one labelled "written by a model from the explanatory memorandum; not the record" (a further 812 were generated but held back after failing an automatic check, and are not shown).

Two gaps in the underlying speech corpus shape what a bill or a division page can show, and are worth stating plainly. There is no Senate Hansard in the corpus at all for 2014 to 2022, so a bill whose real fight happened in the Senate in that window looks quiet on OPAX no matter how contested it was. And 2024 is thin across the board — federal chamber speeches drop to 82 for the whole year — so the 47th Parliament's bills (2022–2025) reach a linked speech only 24% of the time, against 74–84% in every other parliament since 2013. Neither gap is a fault in the bill registry; both close only as more Hansard is loaded.

People

1,557 names appear as speakers in the corpus since 1993; 313 of them currently sit in a state or federal parliament. 829 portrait photographs cover just over a thousand of those names: 551 official portraits from Parliament House, fetched through OpenAustralia because the official image API blocks every identified research tool, reproduced under aph.gov.au's site-wide CC BY-NC-ND 4.0 terms; and 277 from Wikimedia Commons for state parliamentarians and pre-2006 federal members, each individually licensed — Creative Commons, public domain or CC0 — and credited by name on the person page it appears on.

Declared shareholdings, real estate, directorships, gifts, travel and liabilities are shown for 317 sitting members — every House member (151), all but one senator (73) and every Queensland MP (93) — 10,052 declared entries in total, each one linking to the exact page of the source PDF it was read from. They are not in OPAX's ask-and-search index: the House and Senate registers are licensed CC BY-NC-ND, Queensland's terms could not even be read (they sit behind a firewall that blocked every request), and a rewritten version of a declared interest would be a derivative work in a way a fact with a link back to the original PDF is not.

Enrichments written by machines

• Topic labels: every speech is, eventually, tagged against a fixed taxonomy of 21 subjects — gambling, financial services, mining & energy, climate & environment, property & construction, housing, health, media & communications, hospitality & alcohol, defence & security, agriculture, unions & the workplace, immigration, First Nations affairs, tax & the budget, education, welfare & social services, integrity & democracy, infrastructure & transport, justice & law, and foreign affairs — applied by a mix of the hosting platform's own labeller and separate agents that read back over what it produced. The pass is still running: a speech with no topic chip yet has simply not been reached, not been checked and found to have none.
• Machine briefs: many speeches and every topic page carry a short "In brief" summary, written by a language model from that one passage alone and labelled as a machine summary. It is a reading aid, not a replacement for the speech underneath it.
• Report essays: the six standing reports retrieve live from the corpus for every section, and every factual claim is built to trace back to a real, quoted passage — but the connecting prose (the opening summary, the era-by-era narrative) is a model's synthesis of the report's own generated sections, written last. Read it as a guide to where to look, not as the finding.
• Bill summaries: 1,698 federal bills carry a three-sentence, plain-English account of what their explanatory memorandum or Bills Digest says, written by a model and checked by a mechanical rule that rejects any sentence copying nine or more consecutive words from the source. Every one carries its own attribution, because an explanatory memorandum is a bill's own sponsor explaining their own bill, not a neutral account of what it will do.
• Explain flow: the "Explain this money" walkthrough on a donor or party page is not a language model at all — its sentences are assembled by ordinary code from the same structured donation and grant figures the map itself draws on. It can still be wrong, but only the way a mail-merge can be wrong: a bad number or a mis-filed category upstream, never an invented claim.

What this cannot prove

OPAX puts the record and the money side by side. It does not draw a conclusion from them, and neither should a reader without checking the primary source first.

• Money near a decision is a pattern to investigate, not evidence of a favour.
• A division is not the whole vote: most questions in every chamber are decided on the voices, so a member with no recorded division on a bill did not necessarily do nothing.
• Every donation, meeting and grant figure here is a floor. Amounts under a jurisdiction's reporting threshold, and anything from a jurisdiction OPAX does not cover, are invisible by construction, not because nothing happened.
• Registration under the Foreign Influence Transparency Scheme, or an entry in a lobbyist register, is a legal disclosure the law requires, not a finding of wrongdoing.
• A donor receiving a grant, or a bill's sponsor sharing an industry with donors to their party, is a fact on the public record. What it means is for the reader to weigh, with the primary sources OPAX links to at every step.

The corpus's own technical limits — what Hansard is and is not, where coverage is thin, which members' records are unreliable — are on the methods page, not repeated here.

Who makes it

OPAX is a side project of Jake Tracey, of Noice. It is independent and non-partisan, built outside working hours, and the data it carries belongs to the public bodies that published it. Three things make it possible.

• Noice (noice.net.au) is a Melbourne digital agency for the AI era, building digital experiences and AI automation for government and large organisations. The craft OPAX runs on, from how a page is built to how a model is kept honest, was learned there, and the tooling comes with it.
• Progress Agentic RAG (progress.com/agentic-rag) holds the corpus. Every speech, bill, division and statement is indexed in a knowledge box on the platform, which does the retrieval, the reranking and the citation binding behind every answer on the Ask page. OPAX writes the prompts and checks the answers; the platform finds the passages.
• CorpusKit (corpuskit.org) is the open source research portal that grew alongside OPAX: point it at an empty knowledge box and it reads the corpus, designs the taxonomy and the knowledge graph around it, writes the questions worth asking and opens as a branded portal. Much of what works here was built there first, and the parts that generalise flow back to it. It is Apache 2.0, and any organisation with a body of research can use it.

If OPAX helps you find a blind spot, that is the point. If you find one in OPAX itself, a missing source, a wrong number, a jurisdiction not yet covered, the fastest fix is an issue on GitHub, below.

Licences and reuse

OPAX's own code is open source under AGPL-3.0, at github.com/jaketracey/opax. The data behind it is not ours, and it carries a patchwork of licences rather than one. The Hansard record itself — however it reaches OPAX, through TheyVoteForYou, OpenAustralia or a state Hansard feed — is Commonwealth or state parliamentary copyright, reproduced here under CC BY-NC-ND terms (ACT Hansard is © ACT Legislative Assembly, used under CC BY-NC-ND 4.0 with attribution to the Assembly; its official portraits are excluded from that licence and are not used here); TheyVoteForYou's own compiled division data carries a separate open licence of its own (the Open Data Commons Open Database Licence). Most of the money data — AEC returns, GrantConnect and the Queensland grants portal, the Queensland and Tasmanian donation registers, the Foreign Influence Transparency Scheme register, and most lobbyist registers — is Creative Commons Attribution, in one version or another. The House and Senate registers of members' interests are licensed CC BY-NC-ND, which is why they appear on OPAX as facts with a link to the source page rather than as reproduced text; Queensland's register carries no verified licence at all, so it is treated the same cautious way. And a few sources — Western Australian, ACT and Northern Territory donations among them — are held under all-rights-reserved terms and are kept off the public site entirely; that data exists only for internal research. Every page that carries licensed data names its source and, where one applies, its licence; when the two disagree, trust the page, since licences and coverage windows both move and this paragraph will not always be the first place they are updated.

How to reach us

OPAX has no dedicated inbox. Data errors are the corrections we most want to hear about, and the fastest way to report one, ask about the methodology, or point out a source we have missed is to open an issue on the GitHub repository, where the code, the ingestion scripts and the issue tracker all live in one place.

Methods

How OPAX works, and how to cite it

What OPAX is, and is not

OPAX is a retrieval and analysis layer over public records. It is not the official record. Before publishing a quote, verify the wording at the source link on the document page. Every document links to its official origin where one exists.

Corpus construction

Speeches are included from 13 March 1993, the election that seated the longest-serving current federal parliamentarian, so nothing in the corpus predates a currently serving member. Speeches under 200 characters are excluded (procedural fragments), duplicates across overlapping sources are removed, and procedural noise (division roll-calls, chair interjections, day indexes) is stripped. The machine-readable corpus manifest, including per-source counts and the current corpus version, is at corpus.json.

Retrieval and generation

Search runs hybrid semantic + keyword retrieval with a reranking pass. Answers are generated only from retrieved passages, with citations. Embeddings: multilingual-2024-05-06. Generation model (pinned): gemini-2.5-flash-lite. Model identity may change between corpus versions and is recorded in the manifest.

Reproducibility

Searches are reproducible given a query, filters and corpus version: every export file embeds all three. Generated answers are not reproducible and must not be quoted as data. The supported method for a paper: state the question, cite the returned documents by their permanent OPAX links, and archive the export file.

Known limitations

• Hansard is a revised record ("substantially verbatim"), not a raw transcript.
• Party labels use a 15-value canonical vocabulary; some speeches carry no party label.
• State coverage windows differ by parliament (QLD only from 2024, NSW/VIC from 2015).

Corrections

• 30 September 2026, grants by seat. Grant program pages now take each seat's member and party on the grant date from the parliamentary service records, which date every change of party. They previously used the member's current party, so a member who later changed party was counted under the later party. A seat that was vacant on the grant date is now left out of the "to seats held by the government of the day" share, as awards without an electorate already were, and shown as a vacant seat. That share changed for 50 federal programs; award totals did not change.

Licence, code and corrections

AGPL-3.0. Source and issue tracker: github.com/jaketracey/opax. Data errors are corrections we want, so please report them.

Parliamentary expenses

What the expense categories mean

Every parliamentarian page on OPAX splits claimed expenses by category. Those category names are the Independent Parliamentary Expenses Authority's own, reproduced unchanged from its quarterly expenditure reports, so a figure here can be checked line by line against the published source. This page says what each one covers.

Some of these are not expense types at all. IPEA records the purpose of a trip against transport lines, so labels such as parliamentary duties or electorate duties answer why the travel happened, not what was bought. Others are entitlements paid at a set rate rather than reimbursements of receipts. Both are marked below.

Privacy

What OPAX collects and who receives it

The Open Parliamentary Accountability Exchange (OPAX) publishes the public record of Australian politics. Reading it needs no account. This page sets out what the OPAX website and iPhone app collect when you use them, which other companies receive it, how long it is kept and how to have it deleted.

Last updated 6 October 2026. This page covers the OPAX website and the OPAX app for iPhone, which is in testing.

In short

• Reading the record needs no account, on the website or in the app.
• Every request reaches OPAX's servers with your IP address, which is used to limit request rates and refuse abusive traffic.
• The website counts visits with Google Analytics and PostHog. They receive your IP address and details of your browser, but never the words you type or the answers you get. The app has no analytics.
• Questions, searches of the record's documents and search summaries go to the services that search the record and write answers. OPAX adds no account details to them.
• An account holds your email address and whatever you choose to write or save. Your email address is never shown to other members.
• Voice is optional. Your voice goes to ElevenLabs, a third-party AI provider, only during a call you start.
• You can delete your account, and what you wrote, at any time.
• OPAX shows no advertising and does not sell personal information.

Reading the record

On the website

You can read, search and ask without an account. OPAX runs on Cloudflare, so every request your browser makes reaches Cloudflare's network with your IP address, as a request to any website does.

OPAX uses the address to limit how often one address can ask questions (20 a minute), ask for suggested follow-up questions and search summaries (20 a minute), search (120 a minute) and draw share images (60 a minute). Cloudflare counts these per address over 60-second windows. OPAX also refuses some requests from networks that run automated scraping.

Sign-in, account and voice requests have limits of their own. For these, OPAX stores a counter under a SHA-256 hash of the address and the time window, not under the address itself. Expired counters are deleted during later sign-in requests, a day or more after their window ends.

Requests that OPAX's server handles are logged in Cloudflare Workers Logs. They include page loads, searches, questions, other requests for data the server works out, and analytics events passed on to PostHog. Each log entry records the address requested, which for a search includes the search words. Files the site serves as they are, such as scripts, styles and most published data files, come straight from Cloudflare's network without reaching the server, so they are not in these logs. On OPAX's Cloudflare plan the logs are kept for 7 days, as Cloudflare documents, and then deleted. Cloudflare may record connection details, such as your IP address, with each entry.

Cloudflare's own traffic and security analytics for opax.com.au also record requests with their IP addresses. Cloudflare documents that it keeps these request-level records for 31 days.

Questions and searches

Where the words you type go depends on what you are doing.

• Searches of OPAX's catalogs, such as people, parties, donors, contracts, grants, declared interests, pay and expenses, are looked up on OPAX's own server. The search words go to no other service.
• Searches of the record's documents, including the standard search of everything and searches of bill text, also send the search words and filters to Progress Agentic RAG, the service that holds the record and finds the passages that match.
• Search summaries. Unless you have turned summaries off, a search for words also asks for a short summary of the records it found, even when it searched only the catalogs. The search words, filters and those records go through Progress to a language model reached through OpenRouter.
• Questions on the Ask page and in a conversation go to Progress, which finds passages, then with those passages to the language model through OpenRouter. Follow-up questions carry the conversation's earlier turns with them.

Searches made by the voice assistant and by research tools follow the same paths. OPAX's code adds no account details or other identifier to these requests. Progress can still receive your IP address with them: Cloudflare, which runs OPAX's server, documents that it adds the visitor's IP address to requests the server makes to services outside Cloudflare, and Progress is outside it. OpenRouter is called by Progress, not by OPAX's server.

What these services keep, and for how long, is set by their own terms: Progress's privacy policy, OpenRouter's privacy policy, and the policy of the provider OpenRouter sends the request to.

So that a repeated question needs no new work, Cloudflare keeps copies of answers to opening questions, search results and summaries for between ten minutes and seven days. The copies are filed by the question, not by who asked it.

Stored in your browser

The website keeps a few things in your browser, and they last for different times.

• Two preferences stay until you clear this site's data: the kind of question you last chose in the question builder, and that you turned search summaries off. Turning summaries back on removes the second.
• Two things last only as long as the open tab: how you were reading a search, and the question and answer you carry from Ask into a conversation. That question and answer is removed as soon as the conversation opens.
• Your most recent conversations with OPAX, up to 20, so that you can return to them. Older ones drop off as new ones arrive, sooner if they take up too much space. You can delete a conversation from the conversation list; while you are signed in, that deletes the copy in your account too. If you sign in on the website, conversations are copied to your account, including ones saved before you signed in; see Community accounts.

Clearing this site's data in your browser removes what the browser holds, but not the copies in your account. The analytics cookies are described next.

Analytics on the website

The website uses Google Analytics, loaded through Google Tag Manager, and PostHog to count visits and see which features are used. Both receive the page's address with any search terms and fragments removed, and a fixed list of events: a question or search started, finished or failed, with its duration and result counts; a source opened; a download; a link followed to another site; and similar actions. They never receive question text, search words, answers, page titles, postcodes or error messages. Campaign tags in a link are kept only as a plain source, medium and campaign name; other tags and advertising click identifiers are dropped.

With each event, both services also receive details your browser shares, such as your browser and its version, operating system, device type, screen and window size, language and time zone. PostHog also receives the domain of the site that linked you to OPAX, but not the rest of its address.

Each service stores an anonymous identifier in your browser so that a returning browser and a visit can be counted. Google Analytics sets cookies whose names begin with _ga, which Google documents as lasting two years. PostHog keeps its identifier in a cookie that lasts a year and in local storage, which stays until you clear it. Neither builds a profile of you: PostHog's person profiles, session recording and surveys are off, and Google signals and advertising personalisation are off.

PostHog's cookie also records the full address you first arrived at, including any search words in it. Like every cookie for opax.com.au, it travels with your requests to OPAX's server, which does not use it and does not pass it on. OPAX removes that address from the events PostHog receives.

Your browser sends Google Analytics events straight to Google, so Google receives your IP address. PostHog events pass through OPAX's server, which forwards your IP address to PostHog's ingestion service in the United States, so that PostHog places visits by your location rather than by the server's. PostHog may store the address with the event.

Both services keep the events they receive for the retention period of OPAX's account with them, under their own terms: Google's privacy policy and PostHog's privacy policy.

If your browser sends a Do Not Track signal, neither service receives anything, though PostHog may still store its identifier in your browser. Analytics run only on opax.com.au, and community pages load none at all.

The grants map loads its map tiles from OpenStreetMap's servers, which receive your IP address.

In the iPhone app

The OPAX iPhone app is in testing. It needs no account to read. It has no analytics, no advertising and no tracking, and sends no device identifier. The seat you choose and the records it keeps for offline reading stay on your phone. Its searches look up OPAX's own catalogs of people, declared interests, pay and expenses on OPAX's server, and are not sent to Progress or to a language model. Its requests reach OPAX's servers with your phone's IP address, under the same limits and logs as the website. Pages the app opens on opax.com.au are the website, and the website sections above apply to them.

If you use the app's Use my location option when picking your electorate, iOS asks for your permission, and the app then uses one reading of your location, on your iPhone, to suggest an electorate. Your location is never sent to OPAX or anyone else, and is not stored: the app downloads every electorate's outline before it reads your location, so its requests are the same wherever you are, and only the electorate you confirm is saved. The app never asks for your location in the background.

Community accounts

An account is optional. On the website it lets you keep reading lists, take part in discussions, message other members and connect research tools. If you sign in to the iPhone app, it is the same account, and there it is needed only to talk to OPAX by voice.

What an account holds

• Your email address, to sign you in and send the emails described below. It is never shown on your profile or to other members.
• Your display name and a short bio, if you add them, the date you joined and your follower count. These are public.
• What you write and save: discussions and replies, which are public; reading lists, which are private until you share them; saved discussions, which only you see; follows, likes and blocks; and messages to other members.
• Saved conversations with OPAX. While you are signed in on the website, your conversations are copied to your account so that they appear on your other devices, including any that browser saved before you signed in. An account holds up to 50. Only you can see them.
• Your settings: who can message you, and whether you receive reply emails.

Direct messages are visible only to their two participants. OPAX stores them; they are not end-to-end encrypted. If you report a message, moderators can read that message and your reason. Likes, replies and follows can notify the member they concern. Blocking a member stops their messages, removes follows between you and hides each other's discussions while you are signed in.

Signing in

OPAX emails you a sign-in link and, when you sign in from the app, an eight-digit code as well. Each expires after 15 minutes and works once. OPAX stores only a hash of the link and a keyed hash of the code, with your email address, and deletes them a day or more after they expire, during later sign-in requests.

Signing in starts a session that lasts up to 30 days. On the website it is held in a secure cookie that page scripts cannot read; if you sign in to the app, it is held in the iPhone's Keychain, on that device only. OPAX stores a hash of the session token, the account it belongs to, when it started and ends, and whether it began on the website or in the app. It does not store your IP address or device details with a session. You can sign out on one device or on every device.

Email

Emails come from login.opax.com.au and are sent through Cloudflare's email service. OPAX sends sign-in emails, account deletion codes and, when someone replies to a discussion you started, a reply notification. You can turn reply emails off in Privacy & messages, and each one has an unsubscribe link. OPAX sends no newsletters or marketing email. Cloudflare's email service keeps its own delivery records, under Cloudflare's privacy policy.

Research tools

Members can create keys that let research tools search the record through OPAX's MCP service. Keys are stored as hashes, expire after 90 days, can be revoked at any time and record when they were last used. Searches made with a key go through the same search as the website.

Talking to OPAX by voice

Talk to OPAX is an optional voice assistant for signed-in members. It answers from the same public record and links its sources. It is run by ElevenLabs, a third-party AI provider.

Your microphone

OPAX uses your microphone only during a call you start. On the website, opening the voice panel does not touch the microphone: it starts when you choose Start talking, and stops when the call ends, when you close the panel and when you leave the tab. If you use voice in the app, you agree to the terms in this section once, then iOS asks for microphone permission the first time you start a call. Your agreement is stored on your iPhone; you can withdraw it at any time on the voice screen, and the app asks again before your next call. A call ends when you leave the app.

What is sent, and to whom

During a call, your voice streams through OPAX's server to ElevenLabs. ElevenLabs turns your speech into text, writes the replies with a language model that ElevenLabs runs for the assistant, and speaks them back. Anything you type during a call goes the same way. OPAX gives ElevenLabs a random identifier for the call and the call's time limit; its code does not give ElevenLabs your email address or account details. ElevenLabs can receive your IP address with the connection, because Cloudflare adds the visitor's IP address to requests that OPAX's server makes to services outside Cloudflare. When the assistant looks something up, its search runs through OPAX's own search, as described under Questions and searches.

What is kept

When OPAX last checked (9 September 2026), its voice assistant was set at ElevenLabs not to record audio and to delete transcripts after one day. ElevenLabs' own privacy policy also applies. OPAX itself keeps no recording and no transcript. The transcript you see during a call is not saved in your browser or in the app, and is never sent to analytics.

For each call, OPAX keeps a record linked to your account: its state, the seconds reserved and charged, when it started and ended, and ElevenLabs' reference for the conversation.

Your 10 minutes

Each account has 10 minutes (600 seconds) of voice in total, not each month. All members also share a monthly budget of 40,000 seconds, and no more than two calls can run at once. The call records above are how OPAX counts all three.

Starting a call reserves your remaining time, or what is left of the month's budget if that is less. Cancelling the reservation before OPAX starts connecting the call returns the time, and a reservation that is never used expires without charge. Once OPAX starts connecting the call, the time can stay charged if OPAX cannot confirm that no call ran or how it ended, for example when the connection to ElevenLabs fails partway or drops. A call that ends normally is charged for the seconds it ran. A few accounts approved by OPAX can make repeated calls of up to 10 minutes each.

Deleting your account

On the website, open Delete your account from your account page. If you have signed in to the iPhone app, Delete account under Account does the same. OPAX emails you a fresh code, and entering it removes the account from OPAX's live database at once. Deletion cannot be undone. Anyone who can receive the account's email can do it, since both signing in and the deletion code go to that address.

What is deleted

• Your email address, display name, bio and settings, and any voice access OPAX gave your account.
• Every session on every device, any unused sign-in links and codes, and your research tool keys.
• Everything you wrote or saved: discussions, replies, reading lists, saved conversations, messages you sent, likes, bookmarks, follows, blocks, reports you made, and notifications to or from you.
• Emails waiting to be sent to you, your unsubscribe links and the rate-limit counters tied to your account.

What is kept, and why

• Voice call records lose their link to your account but keep their seconds and times, because the shared monthly budget and the two-call limit depend on them; deleting them would hand back time already used. Each keeps ElevenLabs' reference for its conversation until OPAX's housekeeping, which runs every five minutes, clears it one day after the call was recorded as ended. Clearing the reference does not delete ElevenLabs' copy of the conversation, which follows the ElevenLabs settings above.
• Other members' replies to a discussion you started stay, under a placeholder titled "Deleted discussion" with no text, link or date. A conversation you were part of stays readable by the other member, with their own messages only, and takes no new messages. You are shown as "Deleted account". What other members wrote is not changed, even where it quotes you.
• Rate-limit counters for IP addresses stay until they expire.
• Emails already sent cannot be recalled.
• Recovery history. Cloudflare keeps a rolling history of OPAX's database so that it can be restored to an earlier point if something goes wrong. It is always on, and on OPAX's plan it covers the last 30 days, as Cloudflare documents. Your deleted data stays in it for up to 30 days, then is gone. OPAX runs no other scheduled backup or export of the database.

After deletion, OPAX's live database keeps no record of your email address. Signing up again with it creates a new account, with a fresh 10 minutes of voice. The browser you delete from clears its saved conversations; other browsers keep their copies until you clear this site's data there. The public record is not affected.

Who else receives data

• Cloudflare runs OPAX's servers, database, logs, rate limits and email, and handles every request with your IP address. OPAX's community database is held in Cloudflare's Oceania region.
• Progress Agentic RAG receives questions, searches of the record's documents and the inputs to search summaries, as set out under Questions and searches, including those made by the voice assistant and by research tools. It can receive your IP address with them. OPAX's knowledge box is in its AWS Sydney zone.
• OpenRouter, and the model provider it routes to, receives from Progress the questions, search words and passages needed to write answers and summaries.
• ElevenLabs receives voice audio, messages typed during a call and the call's random identifier, and can receive your IP address with the connection. The language model ElevenLabs runs for the assistant receives the words of the conversation through ElevenLabs. OPAX uses ElevenLabs' standard service, not one of its regional data residency services, and ElevenLabs states that it stores this data in the United States, while processing can also happen elsewhere, through its affiliates and subprocessors. Its privacy policy applies.
• Google, through Analytics and Tag Manager, receives page addresses, the events and browser details listed above and your IP address, on the website only.
• PostHog receives the same events and browser details, and your IP address forwarded by OPAX's server, on the website only, in the United States.
• OpenStreetMap receives your IP address when the grants map loads its tiles.

Children

Reading OPAX needs no account at any age. Community accounts and voice are for people aged 16 and over. OPAX does not ask for a date of birth or check anyone's age. Anyone who can receive an account's email can sign in to it and delete it at any time.

Questions and requests

OPAX is run by Jake Tracey, as an independent side project, and he is responsible for this policy.

OPAX does not yet have a private contact address. One is coming, and this page will name it. Until then:

• to delete your account and everything it holds, sign in and use Delete your account on the website (or, if you have signed in to the iPhone app, Delete account there); it asks for a fresh code sent to your email address;
• to see or change what your account holds, sign in: you can change your profile and settings, and delete your reading lists, discussions, replies and saved conversations;
• for anything that is not private, such as a question about this page or an error in the record, open an issue on GitHub. Issues there are public, so leave personal details out of them.

More help is on the support page.

Changes to this page

When this page changes, the date at the top changes with it. The page is part of OPAX's public source code, so every earlier version, and what changed, is in the history of github.com/jaketracey/opax.

Support

Help with OPAX

The Open Parliamentary Accountability Exchange brings together Australian parliamentary speeches, votes, political funding and public disclosures. Search across the records, trace connections and follow claims back to their original sources.

OPAX is independent and non-partisan. It is not a government service and is not affiliated with any parliament, government or political party. More about OPAX.

Report a wrong record or a wrong answer

You are reporting this record.

OPAX copies its records from public sources, and its answers, summaries and voice replies are written by language models from those records, so either can be wrong. To report a mistake, open an issue on GitHub with:

• the link to the record or page, or, for an answer, the question you asked and the words that are wrong;
• what is wrong;
• the source that shows it, if you have one.

Report it on GitHub

Corrections made so far are listed on the methods page.

Issues on GitHub are public, so leave personal details out of them. OPAX does not yet have a private contact address. One is coming, and this page will name it.

Your account

• Signing in. Enter your email address and OPAX emails you a sign-in link and, when you sign in from the iPhone app (which is in testing), an eight-digit code as well. Each works once and expires after 15 minutes. If nothing arrives, check your spam folder, then ask for a new one. Signing in for the first time creates your account. An account is only needed to take part in the community and to talk to OPAX by voice; everything else works without one. Accounts and voice are for people aged 16 and over.
• Signing out. Sign out on one device, or on every device from your account page on the website.
• Voice. Each account has 10 minutes of voice in total. Voice needs microphone access, which you can turn on or off in your browser's settings, or for the iPhone app in Settings.
• Deleting your account. On the website, open Delete your account; if you have signed in to the iPhone app, Delete account under Account does the same. OPAX emails you a fresh code, and entering it deletes your account and what you wrote. It cannot be undone. What is deleted and what is kept.

Privacy and the source

Privacy sets out what OPAX collects and who receives it. Methods explains how the record is built and how to cite it. OPAX's code is open source, at github.com/jaketracey/opax.