Google Tag Manager was added to this site on 4 August 2026. Before that date the site loaded nothing from any third party and this page said so. It now describes what is actually collected.
The short version
- Google Tag Manager is installed (container
GTM-KJG899Q9). It is the only third party this site loads. - Do Not Track and Global Privacy Control are honoured. If your browser sends either signal, Tag Manager never loads — no script, no request, no cookie, and no tag inside it runs either.
- No geolocation lookup. Nothing here resolves your IP address into a city, region or internet provider.
- No advertising. No ad network is allowed to load, and the site sells nothing.
- No account, no login, nothing to sign up for except an optional email list.
- Nothing is sold, rented or shared.
What Google Tag Manager is, and the honest caveat
Tag Manager is not itself a measurement tool. It is a loader: a container that can load other tools — analytics, and in principle other things — based on a configuration held in Google’s console rather than in this site’s code.
What loads inside that container can be changed by the site owner at any time without altering a single line of this website. So a sentence here saying “we run exactly these tools” would be a claim this page has no power to keep.
What can be promised, because it is enforced in code and in the site’s security policy rather than in a console, is everything in the next two sections. We would rather tell you the shape of the guarantee accurately than give you a comforting list that could quietly go stale.
The intended use is ordinary: knowing which guides people actually read, so the next ones are written about the right procedures. Nobody here looks at individual readers.
Expect the usual analytics collection: which pages you viewed and in what order, roughly how long you stayed, the approximate location derived from your IP address, your device type, browser and screen size, and the site or search that sent you here. Cookies are set to recognise a returning browser. Those cookies are Google’s, not ours.
The two guarantees that are enforced in code
1. Do Not Track stops everything, permanently
The check sits in front of the container, not inside it. If your browser sends Do Not Track or Global Privacy Control, Tag Manager itself is never requested — so no tag within it can run, including any tag added in future by someone who never read this page.
That placement is deliberate. Configuring privacy on individual tags would leave the guarantee only as durable as the next console change.
2. The security policy caps what can ever load
This site sends a Content-Security-Policy that names the specific origins a browser is permitted to load anything from. Right now that list is Google Tag Manager and Google Analytics, and nothing else. A tag pointed at any other destination — an ad network, a session recorder, a third-party pixel — is refused by your browser, not merely discouraged by us.
Widening that list requires a change to this site’s code, which is a visible, recorded change rather than a console toggle. That is the part worth trusting: the set of companies that can receive anything about your visit cannot be expanded from a web console.
To be straight about the limit of this: Tag Manager is permitted to run custom code of its own inside the page. So the guarantee is about who your browser may talk to, not about what the code from those two Google origins may do once it is running.
Turning it off
- Enable Do Not Track or Global Privacy Control in your browser. This site checks for both before loading anything. Most browsers have it in privacy settings; some, including Brave and DuckDuckGo’s browser, send it by default.
- Use a content blocker. uBlock Origin and similar block Tag Manager outright. Nothing on this site breaks if you do — every page works with all scripts blocked.
- Install Google’s own Analytics opt-out browser add-on, which disables Google Analytics across every site.
You can verify this. Open your browser’s developer tools, look at the network tab, and reload a page. With a Do Not Track signal set there should be no request to any Google domain at all.
What else is collected, and by whom
Server logs
This site is hosted on Netlify. Like every web host, Netlify processes the technical information required to serve a page — IP address, the page requested, the time, and your browser’s user-agent string. We do not add to it and we do not use it to build any picture of individual readers. Netlify’s handling of that data is governed by its own privacy policy.
If you would rather not appear in any web server’s logs at all, that is a general property of the web rather than of this site, and a VPN or Tor is the usual answer.
The email list, if you join it
If you enter an email address on the homepage, that address is stored by Netlify Forms. It is used to send occasional notices about new guides and corrections, and for nothing else.
- We do not sell, rent, share or trade the list.
- We do not use it to profile you, and we know nothing about you beyond the address you typed.
- Ask and it will be deleted. No explanation needed.
The form does not require your name, and we would rather you did not give us one. An email address is enough.
Links to other sites
Following a link away from here — to SAFE SAPCR Texas, TexasLawHelp, a county clerk, a legal aid provider — takes you somewhere with its own practices. We have no control over and no visibility into what those sites do.
What is deliberately absent
An earlier placeholder at this address called a geolocation service that resolved each visitor’s IP address into a city, region and internet provider, writing the result into a hidden form. The sibling site carried the same code and it was removed on 3 August 2026.
None of it was malicious — that combination is a common template and most people who ship it never look at what it does. But a site whose readers are in contested custody proceedings has no business building a log of where they read it from. It is not here, it is blocked at the Content-Security-Policy level, and it is not coming back.
Also absent: web fonts, content delivery networks, embedded video, social widgets, session recording, heatmaps, and A/B testing tools — and each of those is blocked by the security policy described above, not merely unused. Apart from Google Tag Manager and Google Analytics, every file a page loads comes from this domain.
If you are in an unsafe situation
This site cannot see who you are, but the device you are reading on can, and so can anyone with access to it. If someone else has access to your phone or computer, consider a private browsing window, and clear your history afterwards.
If a shared account, shared phone plan or shared computer is part of what you are dealing with, the National Domestic Violence Hotline publishes guidance on covering your tracks online, and it is better than anything we could write here.
Changes
If what this page describes changes again, the page changes with it and carries a dated note at the top saying what moved, as it does now. A privacy policy that is quietly rewritten is worth nothing.
Last reviewed 4 August 2026.