Most privacy policies are written to be defensible. This one is written to be checkable. Everything below describes what the code on this site actually does, key by key, and the code is one unminified file you can read in view-source: /_astro/instrument.*.js, from src/scripts/instrument.js.
If anything on this page and anything in that file disagree, the file is right and we have a bug. Tell us and we will fix the page.
The short version
We record which pages you visit. It is first-party — our own code, our own server — and it involves no cookies, no third-party tags, no advertising pixels, and no data broker. We do not sell, rent, lease or trade anything, to anyone, at any price. Do Not Track and Global Privacy Control are honoured: if either is set, nothing leaves your browser.
There is no shopping cart on this site, no newsletter, no account to register for, no login, and no password. Nothing on this site takes a payment.
What we record automatically
On every page load, this site sends one message to our own server at https://n8n.codybaird.net/webhook/admen-analytics. That endpoint is ours. Nothing is copied to an analytics vendor, an ad platform or anyone else.
The message contains:
- the path of the page you are on, and the page you arrived from (
document.referrer) - a random visitor ID and a random session ID (described below) — both are generated in your browser and are not derived from anything about you
- your browser’s user-agent string and the width of your browser window
- any
utm_source,utm_medium,utm_campaign,utm_term,utm_contentorutm_idvalues that were on the link you followed - any advertising click ID that was on that link. We look for fifteen by name:
gclid,gclsrc,wbraid,gbraid,dclid(Google),fbclid(Meta),msclkid(Microsoft),ttclid(TikTok),li_fat_id(LinkedIn),twclid(X),epik(Pinterest),rdt_cid(Reddit),sccid(Snapchat),irclickid(Impact),cjevent(CJ). If you did not arrive from an ad, none of these exist and none are sent. - a coarse channel label our code guesses from the above —
paid_search,paid_social,organic_search,organic_social,email,affiliate,display,referral,directorinternal - whether Do Not Track or Global Privacy Control were detected
- a timestamp
We also record a small number of named events the same way, with the same visitor ID: apply_form_start and apply_form_submit on the application form, and benchmark_capture_submit on the benchmark question form.
We do not record what you type, keystroke by keystroke. There is no session replay, no heatmap, no scroll recorder, no mouse tracker and no form-field capture.
Every storage key this site writes
Six of these are written by the instrumentation, whether or not you ask for them. The seventh is written by the picker on the home page. All of them are visible in your browser’s developer tools under Application → Storage.
admen-vid— localStorage, no expiry. A random UUID identifying this browser. It is the durable one: it survives closing the tab, closing the browser and restarting the machine. It exists so several visits weeks apart can be read as one journey rather than as strangers.admen-sid— sessionStorage. A random UUID for this tab. Deleted when the tab closes.admen-attribution— localStorage. Your first touch: the timestamp, the page you landed on, where you came from, any campaign parameters, any click IDs, and the channel guess. Written once and never overwritten.admen-last-touch— localStorage. The same record for your most recent arrival. Overwritten each time the source changes.admen-journey— localStorage. An ordered list of those touches, one per session or per change of source, capped at the 50 most recent. When it overflows, the oldest are dropped; the first touch is kept separately inadmen-attributionso the origin is never lost.admen-clickids— localStorage. The most recent advertising click IDs, if there were any.admen-profile— sessionStorage. The three answers you give the picker on the home page: practice type, network size, primary constraint. It is used to open the right benchmark rows and the right differential on other pages. It is deleted when the tab closes, and it is not sent to the server.
If your browser blocks storage — private mode, or storage disabled — none of these are written. The site still works. The pageview message is still sent, with no-vid and no-session in place of the IDs.
Do Not Track and Global Privacy Control
Both are honoured, and honoured the same way: nothing is sent at all. Not a reduced payload. Not an anonymised one. The network request is not made.
We check navigator.doNotTrack, window.doNotTrack, navigator.msDoNotTrack and navigator.globalPrivacyControl. Any one of them set is enough.
One thing that is true and that we would rather state than have you discover: with either signal set, the keys listed above are still written into your own browser’s storage. They are not transmitted anywhere and never will be while the signal is set — the transmission is the only thing the signal governs. If you want them gone as well, use Forget me, described below, or clear site data in your browser.
What you can choose to have us keep — in your browser only
Separately from all of the above, this site offers three switches. They are off by default, each is granted separately, and each is revoked separately. They appear on this page, at the bottom, and after the picker on the home page.
- Remember my practice — practice type, network size and primary constraint, kept past the end of the tab.
- Remember my figures — the numbers you type into the tools on this site, each with the measure it was entered against and the date, in a key called
admen-record. - Remember my name — a first name and a title. Nothing else.
Everything under those three switches is written to localStorage on your own device and is never transmitted to us. There is no request in the code that could send them and no address for them to be sent to. Switching one on puts you on no list, starts no sequence, and triggers no call, no email and no text — not because we have promised to be good about it, but because the data never reaches us. Switching one off deletes what it was holding, in the same click.
Because none of it reaches us, there is no account, no login and no password. If you want a record to move to another browser, you export it as a file and import it there. That file is produced in your browser and handed to you; it is not uploaded.
Forget me
The Forget me button on the consent panel deletes every key on this site that starts with admen-, in both localStorage and sessionStorage. That includes admen-vid, the durable visitor ID. A control that left that one behind would not have forgotten anything.
What it does not do, and cannot: it does not reach back and delete records already received by our server before you pressed it. For that, email support@admen.com and say so — we will delete them and tell you when it is done.
After you press it, the next page you load starts a new random ID, because the code does not know it has met you. If you want it to stop entirely rather than start over, set Do Not Track or Global Privacy Control.
What you send us on purpose
The application form at /apply/. It asks for a group name, your name, your role, your email address, an optional phone number, and operating detail — specialty, number of locations, number of providers, revenue, stage, marketing spend, who else decides, the constraint you would name, and what you would want done in the first week. It is submitted to https://n8n.codybaird.net/webhook/admen-apply.
Attached to that submission is the attribution snapshot described above: your visitor ID, session ID, first touch, last touch, click IDs and journey. This is the point of collecting them — so that an engagement can be joined back to how it started. Nothing is attached that is not listed on this page.
The benchmark question form at /benchmarks/. It asks what you attribute a top-of-range figure to, with an optional email address. Anything published from it is aggregate and anonymised: no practice, no person and no location is ever named. As of the date below, that form has no endpoint configured and submits nothing anywhere — the confirmation you see is local.
We use what you send to reply to you, to evaluate whether we are the right fit, and to run an engagement if one begins. That is all.
Cookies
No. This site sets none. Not first-party, not third-party, not analytics, not advertising, not “essential”. The storage described above is localStorage and sessionStorage, which is not the same mechanism, is not sent automatically with every request, and is listed key by key on this page so that the distinction is not used as a dodge.
Third parties
None have access to anything collected here. There is no Google Analytics on this site, no Meta pixel, no LinkedIn insight tag, no Hotjar, no chat widget, no A/B testing tool, no consent-management vendor and no tag manager.
Our code contains one dormant hook that would dual-fire events to Google Analytics 4 if a measurement ID were ever set. It is empty, so the hook does nothing. If we ever set it, this page will say so before it goes live, and the entry will name the property.
The site is hosted on a server we control. Our own operational suppliers — hosting, email, and the SMS carriers named at the end of this page — process data on our behalf under their own terms, and none of them are given anything for their own purposes.
Children
This site is for owners and operators of healthcare groups. It is not directed at children, we do not knowingly collect information from anyone under 13, and there is nothing on it built to appeal to them. If you believe a child has sent us something, email support@admen.com and we will delete it.
Your rights
Ask us what we hold about you and we will tell you. Ask us to delete it and we will delete it. There is no form for this and no waiting period beyond the time it takes to do it — email support@admen.com. This applies wherever you live; we do not sort people by jurisdiction before deciding whether to answer.
Changes to this policy
If the code changes, this page changes with it, and the date below moves. We will not quietly widen a paragraph to cover something new. If we add a third party, this page will name it.
Contacting us
ADMEN Growth Partners 401 Congress Ave. Suite 1540 Austin, TX 78701 support@admen.com 512-568-3559
SMS and text-messaging consent
If you provide your mobile number and affirmatively opt in (by checking the SMS consent box on a form on this website, by providing written consent in an engagement agreement, or by verbally asking us to text you), Admen may send you text messages related to your inquiry, application, or engagement — such as application status updates, appointment confirmations, and service notifications. Message frequency varies. Message and data rates may apply.
Opting out
You can opt out at any time by replying STOP to any message; you will receive a one-time confirmation and no further texts. Reply HELP for help, or contact us at cody@admen.com.
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text-messaging originator opt-in data and consent are not shared with any third parties, excluding aggregators and providers of the text-message services, strictly for the purpose of enabling delivery.
Last updated: August 12, 2026