Skip to content

Menu

What OPAX collects and who receives it

Last updated 16 November 2026. This page covers the OPAX website and the OPAX app for iPhone, iPad and Android.

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 the OPAX app for iPhone, iPad and Android collect when you use them, which other companies receive it, how long it is kept and how to have it deleted.

In short

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 up to 31 days.

Questions and searches

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

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 both by OPAX's server and by Progress.

When OPAX's server writes an answer in Ask, it sends the question and the retrieved records through OpenRouter to one model provider, Together, with settings in each request that exclude providers that train on prompts and require zero data retention. If that route is refused, Ask returns an error and does not use another route. When OPAX writes an answer or summary through Progress, the text goes through OpenRouter to the same provider, Together, under settings that exclude providers that train on prompts and require zero data retention. Last checked 16 November 2026.

What these services keep, and for how long, is set by their own terms: Progress's privacy policy, OpenRouter's privacy policy, terms and table of providers' data policies, and Together's privacy policy.

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.

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 or postcodes. Campaign tags in a link are kept only as a plain source, medium and campaign name; other tags and advertising click identifiers are dropped.

PostHog also receives anonymous error reports when something on a page goes wrong in your browser. A report gives the kind of error, a shortened error message and the place in OPAX's own code where it happened. Before a report is sent, any quoted text is removed from the message, and search terms and fragments are removed from any address in it. Errors from browser extensions or other sites' scripts are not sent. Google Analytics receives no error reports.

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 servers 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, iPad and Android app

The OPAX app for iPhone, iPad and Android needs no account to read, search or ask. It has no advertising and no tracking. It sends no advertising identifier and never reads your device's own identifier; it uses a random install ID that isn't linked to you. Through PostHog, it counts which screens and features are used and sends a report when the app crashes or hits an error. These go through opax.com.au, which passes your IP address on to PostHog in the United States, as it does for the website. They carry no account details or anything you type, are not linked to you, and cannot be turned off in the app. Its requests go only to opax.com.au, with your device's IP address, under the same limits and logs as the website (see Reading the record). Pages the app opens on opax.com.au are the website, and the website sections above apply to them.

App Store privacy label and Google Play Data safety

The app's privacy label on the App Store and its Data safety section on Google Play list the nine kinds of data below, each under its App Store name, with its Google Play name in brackets. None of it is used to track you. It is used to make the app work: to sign you in, run the features you use, limit abuse and keep the service running. The PostHog counts and crash reports are also used to see how the app is used and to fix faults.

The App Store label counts seven kinds as connected to your identity, and Device ID and Crash Data as not linked to you. The App Store takes one answer for each kind, so Product Interaction and Other Diagnostic Data count as connected, because of voice call records and server logs, even though the PostHog counts and crash reports in them are not linked to you. For searches and server logs, being connected is a cautious answer: they carry no account details, but a log of a request you made while signed in could be matched to your account.

Google Play asks whether data is collected or shared, not whether it is linked to you. Every kind below is collected, and none is shared: Google Play does not count data that a company handles on OPAX's behalf, such as Cloudflare or PostHog, as shared. Because the PostHog counts and crash reports carry no account details, deleting your account does not delete them; PostHog keeps them for the retention period of OPAX's account with it.

What the app sends, and where

What the app does not collect

The companies that receive data from the app are Cloudflare, ElevenLabs, PostHog, Progress Agentic RAG and OpenRouter, under Who else receives data.

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 app, it is the same account: there it lets you talk to OPAX by voice and keep your conversations with OPAX in your account. The community itself is on the website only.

What an account holds

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 on that device only: in the Keychain on an iPhone or iPad, and encrypted with a key kept in the Android Keystore on Android. 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 (MCP)

AI assistants and other research clients can read OPAX's public record through its MCP service at https://opax.com.au/mcp. It needs no account. Every tool is read-only and returns published records only. How to connect.

When an assistant uses a tool, OPAX receives the tool's name and the inputs the assistant chose, such as search words, a name or a date. OPAX does not receive your conversation, your account with the assistant's maker, or anything else about you. The request usually arrives from the assistant maker's servers, such as Anthropic's or OpenAI's, so OPAX sees their IP address, not yours. A client running on your own computer connects from your address.

OPAX uses the IP address, and a random session number it gives the client when it connects, to limit request rates: 60 tool requests a minute for one client, with a higher ceiling for one address, and a daily allowance for each network. The counters are stored as hashes and deleted after they expire. OPAX also keeps a count of how many requests and record searches arrived each hour and each day without an account, split only by whether they came from an assistant maker's servers, with nothing about who sent them. Requests are logged like any other request to OPAX's server; the log records that the service was called and the outcome, not the tool or its inputs. Searches of speeches and releases made through a tool go to Progress in the same way as a search on the website. No tool sends anything to a language model.

What the assistant's maker keeps about your use of OPAX's tools is set by its own privacy policy.

With an account. Members get their own limit, in one of two ways. A member can create keys, which are stored as hashes, expire after 90 days, can be revoked at any time and record when they were last used. Or a member can sign in from an assistant that supports it: OPAX then keeps the name the assistant gave, where it returns to, when it was connected and last used, and hashes of its access codes, which expire after an hour and are renewed for up to 60 days. The assistant can read public records as you. It cannot see your email address, lists or messages. You can remove a connected assistant in your account at any time, and deleting your account removes them all.

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 your device asks for microphone permission the first time you start a call (on Android, after the app explains why it needs it). Your agreement is stored on your device; 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, it uses OPAX's own search and Ask, so the words of the look-up go to Progress and to the language model reached through OpenRouter, 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 tied 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. In the app, tap the person icon (Account and about), then Delete account. 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

What is kept, and why

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 or app you delete from clears its saved conversations; other browsers keep their copies until you clear this site's data there, and the app on another device keeps its own until you delete them in Ask. The public record is not affected.

Who else receives data

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 an independent side project of Jake Tracey. Noice Pty Ltd publishes it, including the app on the App Store and Google Play, and is responsible for this policy.

For questions about your personal information, or a request to see, correct or delete it, email privacy@opax.com.au. For help with OPAX, email support@opax.com.au. You can also do most things yourself:

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.