Privacy

We would rather tell you exactly what happens than publish a page of legal boilerplate. Everything below is what the site actually does; if you find something here that doesn't match, tell us and we'll fix the site or fix the page.

Google Analytics

Every page loads Google Analytics 4 (property G-MSG5XNGRDK). It is how we know whether anyone is finding the directory, and which resources are worth keeping up to date. It records a pageview when you open a page, and from that Google derives:

• the page you opened, and the page or search that sent you here;
• an approximate location from your IP address — city level, not an address;
• your device type, browser, operating system and screen size;
• a randomly generated visitor ID, so a return visit is not counted twice.

That data is sent to Google and held on Google's servers, under Google's privacy policy and outside our control. We can see the reports; we cannot see who you are, and we do not try to find out.

What we have switched off

Analytics ships with more than measurement turned on. In assets/js/analytics.js we disable:

• Google signals — no linking your visit to a Google account;
• Ad personalisation — nothing here feeds advertising profiles;
• Cross-device tracking — no stitching your phone to your laptop.

There are no advertising tags, no remarketing pixels, no social media trackers and no third-party scripts other than the Analytics tag itself.

Turning it off

Analytics never loads at all if your browser sends Do Not Track or Global Privacy Control. Neither signal is legally binding in Australia. We honour both anyway, because a visitor who has said no has said no.

• Global Privacy Control is built into Firefox, Brave and DuckDuckGo, and available as an extension elsewhere. See globalprivacycontrol.org.
• Do Not Track is a setting in most browsers' privacy preferences.
• Any content blocker that blocks googletagmanager.com also works, as does Google's own opt-out browser add-on.

The site's information and Directory remain readable without JavaScript. Public forms that use a bot check are the exception: their pages explain when JavaScript is needed rather than failing silently.

What is stored on your device

The accessibility and display panel can save two local preferences, and only when you choose something other than the defaults. Picking Light or Dark saves thsa-theme. Text size and spacing, line height, font, contrast, link emphasis, motion, decorative-image, cursor and reading-guide choices are kept together in thsa-accessibility.

Those values stay in this browser's local storage. They contain no name, identifier, pages visited or pointer position; our code does not send them to the server or Google Analytics. Choosing Reset all removes both entries and returns the colour theme to System. They are not cookies, and clearing your browser data also removes them.

Google Analytics may set its own cookies in your browser. Blocking it, or sending one of the signals above, prevents that.

Maps on listing pages

Where we have a confirmed location for a practice, the listing page embeds a map from OpenStreetMap. Loading that map means OpenStreetMap receives your IP address and the map's coordinates, in the same way visiting any OpenStreetMap page would. Listings without a confirmed location show the address as text and load nothing.

Server logs

Like any web server, ours records each request: your IP address, the time, the page, the referring page and your browser's user-agent string. These logs are used to keep the site running and to investigate abuse. They are not linked to Analytics data and are not shared.

View counts on listing pages

Each directory listing shows how many different people have opened it. To count you once rather than once per visit, our own server takes your IP address and your browser's user-agent string, joins them to a secret value that never leaves the server, and stores the resulting one-way hash. Your IP address itself is not stored in that record, and the hash cannot be turned back into it by anyone who does not hold the secret.

That record holds three things: which listing, the hash, and the first time it was seen. Nothing else is kept against it — not which other pages you opened, not when you came back, and it is not joined to anything else we hold. It can answer "how many different people opened this listing" and it cannot answer "who" or "what else did they read".

This is ours, not Google's: it runs on our own server and the data stays there. If your browser sends Do Not Track or Global Privacy Control, you are not counted — your browser doesn't send the request, and the server declines it as well. The number still displays; you just aren't part of it. Blocking JavaScript also stops the count, and the page still shows the total as at the last time it was rebuilt.

Public-form bot protection

Our feedback, contact and practitioner listing request forms use Cloudflare Turnstile to distinguish people from automated submissions. When one of those forms loads, your browser connects to Cloudflare. The resulting verification token and your network address are checked with Cloudflare when you run or submit the form. We do not send the contents of your form fields to Cloudflare.

Practitioner listing requests

A listing request contains the requester's name and email, the practitioner's professional contact details, a private reason for the request, and the proposed public description. We keep it in our private administration database for as long as needed to assess and maintain the Directory.

Before a request can be submitted, the proposed listing details and the private reason are sent to OpenAI for a structured completeness check. The requester's name and email, and the private practitioner or administrator email, are excluded from that AI check. OpenAI's response is preliminary feedback only; a THSA volunteer makes the decision. The API request is sent with storage disabled. Your raw network address is not sent to OpenAI; we include a one-way pseudonymous safety identifier for abuse monitoring.

When you contact us

If you email us, or send a listing request, we keep that message for as long as we need it to reply and to maintain the directory. We don't add you to anything. There is no mailing list to be added to.

Because the site is run by volunteers rather than staffed, we have an alert emailed to us when something arrives, so it isn't left sitting unread. That alert goes through Brevo, an email provider, and tells us your name and the address you gave so we know who has written in. By default it does not include what you wrote — we open the message in our own admin system to read it, and the text stays in our database rather than going through Brevo. We can turn message text on if a volunteer needs it in their inbox, so treat anything you send as capable of reaching an ordinary email account.

If something is sensitive enough that this matters to you, our what we never do list still holds — but a phone call to one of the crisis services may suit you better than a web form.

Directory listings

The directory publishes professional contact details — practice name, address, phone, website — for practitioners who work affirmingly with trans and gender-diverse people. It holds no information about the people who see them.

If you are listed and want your entry corrected or removed, email us and we will action it. You don't need to give a reason.

What we never do

• Sell, rent or trade anything about you.
• Run advertising, or share data with ad networks.
• Ask you to create an account. There isn't one.
• Tell anyone which practitioner you looked at. The view count on a listing is a total and nothing else — never a list of who visited, and never linked to you.

Changes to this page

If we add or remove anything that collects data, we update this page at the same time. Last reviewed 3 August 2026.