Privacy & telemetry posture
What this site actually collects, stated plainly. This page describes implemented behavior, not aspirational policy.
Analytics we use, and what they never receive
This site uses two third-party analytics services on its public pages. PostHog, a product-analytics service, shows us which pages and calls to action help visitors and how fast pages load. Google Tag Manager loads Google Analytics 4, which measures site traffic, and the tags that count conversions from our own advertising campaigns. Neither PostHog nor Google Tag Manager runs on sign-in, Lectio study, administration or team pages.
The PostHog script is served from this site's own origin at a
fixed version, and your browser checks every event against a fixed
list of allowed events and properties before it is sent. PostHog
knows an anonymous visitor by a pseudonymous identifier. When you
are signed in, PostHog knows you by your account’s internal
identifier, and your PostHog profile holds your display name and
your verified email address (see
Known-user mode). When you
react to a page or post, edit or delete a comment while signed
in, that event also carries your verified email address and
(except for a deletion) your display name (see
Reactions and comments). Every
other event is checked in your browser and any email address is
removed before it is sent. Outside your profile and those events,
PostHog never receives your name, email address, organization, phone
number, anything you type into a form, the text of anything you
select, or the full address of the page that sent you here (only
its site). Your browser sends these events to this site's own
address (/ingest), and this site's server passes them
on to PostHog. It never passes on your cookies or the address of
the page you were on. Events carry no IP address field; the server
passes on your IP address only so that PostHog can tell which
country a visit came from, as it could when your browser connected
to PostHog directly.
On the same public pages, PostHog also makes a session recording
(session replay): a reconstruction of the page’s layout and
of your scrolling, clicks and page changes, so we can see where a
page is confusing or broken. It is linked to the same pseudonymous
identifier and visit as the events above. The recording script is
served from this site, never loaded from PostHog, and everything
is masked in your browser before it is sent: every value you type
into a form or choose from a list shows only as asterisks, and
your name, email address and profile in the account menu, the
text of comments and the learning widgets are masked the same way.
The recording leaves out canvas drawings, embedded frames from
other sites, your browser’s console and the content of any
network request. It goes through the same /ingest
address, is never made on sign-in, administration, team or learning
pages, and is never made when your browser sends Do Not Track. No
heatmap is made.
Some events happen on pages where the PostHog script never runs, so this site's own server reports them to PostHog instead: starting, completing or being refused a sign-in, signing out, saving your profile, a graded knowledge-check answer and the review schedule it sets, a written explanation (its length, never its words), opening your learning record, a comment refused by moderation or spam checks, a submitted data lake request or guide signup, a contact inquiry that was sent or could not be sent, and organization changes such as creating an organization, assigning or ending a membership, a refused team action, or an assignment. The server checks each one against the same list of allowed events and properties. They carry choices and identifiers such as the sign-in method, whether an answer was correct and how confident you said you were, whether your email matched an organization, or which guide you signed up for. These server events leave out your email address, your name, anything you typed and the answer you chose; an organization is named only by its internal identifier, never its name or web domain. When reading tracking is on for your account, the server also keeps your PostHog profile current with the same display name and verified email address your browser gives it, and whether the account belongs to our team or an organization (so that internal traffic can be filtered out); the events themselves still never carry them. A signed-in reader is known by the account’s internal identifier; a form submitted without signing in, or an account that was erased, is never linked to a person. A contact inquiry sent without signing in carries the random identifier PostHog keeps for your browser, so it is counted with your other anonymous page events; it still carries only the intent you chose, the service page you came from and where you came from, never what you typed.
When you send the inquiry form on the contact page or a service sprint scoping form on any service page, this site's server emails your name, work email, organization, chosen intent, options and message to our team through Mailgun, the email service that also delivers sign-in links, so we can reply to you. An audit log of each submission is recorded in this site's secure SQLite database with a 24-month retention period (see Forms you send us below); analytics never receive what you type.
The contact page's “Book a Call” calendar is Microsoft Bookings, shown inside the page. Microsoft runs that calendar, receives the details you enter to book, and may set its own cookies under its own privacy terms. This site records that the Book a Call button was clicked. When our booking calendar is connected through Microsoft Power Automate, Microsoft also tells this site that a call was booked, with an appointment reference used only to count each booking once; this site never receives who booked, the details you enter or the appointment time, and the count is not linked to your visit.
Through Google Tag Manager, Google Analytics 4
records the pages you view, how you arrived (the referring site
and campaign tags), your browser, device type and approximate
location, and a short list of events forwarded from this site,
such as a contact-form submission or a click on a consultation
link. To recognize a returning browser it sets first-party
analytics cookies named _ga and
_ga_<ID>. Google receives your browser's IP
address with each request, as with any web request. Analytics
storage and advertising storage are granted for every visitor,
because there is no consent banner; ad personalization is turned
off. Conversion tags in Tag Manager may also set advertising
cookies so a campaign's conversions can be counted. Google
Analytics receives none of the form text, names or email
addresses described above, and Google Analytics makes no session
recording or heatmap.
The telemetry described in the sections below is first-party: collected by this site's own server, into this site's own database, for this site's own operational use.
Anonymous visitors
Ordinary page views generate anonymous, first-party event records (page path, referrer class, timing) with no identity attached. Raw anonymous events are retained for 90 days, after which they are reduced to de-identified aggregate counts kept indefinitely — the individual raw events themselves are not.
From your first page, PostHog also receives anonymous measures:
pages viewed and their titles, links and buttons used (with their
labels as shown on the page), progress through this site's forms
(which field you started on, which fields failed a check, and
whether you sent the form: field names only, never what you
typed), the audience a page is written for when you use its
contact, booking or form buttons (fixed codes such as
“ICP-01” for a type of organization and
“PER-01A” for a job role, set by the page, never
by you), how far pages were scrolled,
active reading time, the length (never the text) of text you
select, page speed, script errors (type and location only), and the
kind of site that referred you, for example a search engine or an
AI assistant. PostHog keeps a random identifier in your browser's
local storage and in a first-party cookie (named
ph_…_posthog) shared by this site's
subdomains, so it can recognize a return visit from the same
browser, whether you arrive at the site with or without
“www”. That identifier is not linked to who you
are unless you sign in, as described below.
Known-user mode (Lectio, sign-in)
Some Resource Hub pages offer an optional sign-in (a passwordless magic link, valid 15 minutes) to enable Lectio — this site's precision-education feature, which tracks whether a reader actually engaged with a specific resource, not just whether the page loaded. Signing in is never required to read anything.
When PostHog is on and you have reading tracking on, your PostHog profile also records which organization account you belong to, if any: the organization’s internal identifier, your role in it, the internal identifiers of your organization’s groups you are in, and whether your address is a company or a personal one. Each organization has its own PostHog profile with only its identifier, how it was set up, how many members and email domains it has, and whether it is still active. No organization or group name, email domain or email address is sent for this.
Before you sign in, your first page view in a browser sets a
cookie named __Host-ns_visitor. It holds a random
identifier and nothing else: no name, email address or browsing
history. Scripts on the page can’t read it, and it is sent
only to this exact site address. Our server keeps the identifier
and the time it was first seen. If you later sign in from that
browser, the identifier is linked to your account, so we can tell
that the visit before sign-in was yours. If you never sign in, it
is linked to nothing. The cookie lasts 180 days. Crawlers and
automated clients don’t receive it, and you can delete it at
any time in your browser.
Signing in sets one strictly necessary cookie,
__Host-ns_session. It holds only an encrypted
reference to your sign-in on our server, is never readable by
scripts on the page, and is sent only to this exact site address.
A sign-in lasts up to 30 days, and ends sooner if you don’t
visit for 7 days; each visit within that week extends it, never
past the 30 days. Signing out, or signing in again from the same
browser, ends the earlier sign-in at once. Records of ended
sign-ins are deleted from our server 90 days after they end.
Signing in turns on reading tracking (Lectio engagement) for your account: active reading time, scroll depth, comprehension checks and reactions on Netspective guides. It stays on for as long as you are signed in; there is no setting to turn it off, and signing out stops it. You can see your progress across the site from any guide, and you can delete your account's data at any time. Other uses of your account need their own consent scope: profile linkage (connecting your activity across sessions) or communications (contacting you about your engagement). An account with no activity is pruned after 24 months of dormancy by default.
Lectio data is also counted into public, de-identified reading benchmarks: for example, how many signed-in readers opened a page, their median active reading time, and the share who answered its comprehension check correctly. These totals never include your name, email, account, sessions or the times you read, and a figure is published only once at least five different readers stand behind it.
If you are signed in, PostHog also receives your account's internal identifier, so your visits can be understood together, and your PostHog profile is given your display name and your verified email address. Your email address and name are never added to other events, apart from the reaction and comment events described below. Detailed reading records (Lectio study events) are sent too, because reading tracking is on while you are signed in. Signing out ends this: later events are anonymous again.
Reactions and comments
Resource and service pages let you react (helpful, not helpful, needs an update) and comment, signed in or not. Comments are public. A signed-in comment shows your verified email address as its author, published on the page itself next to the comment for anyone to read. An anonymous comment shows the name you chose, or “Anonymous Reader”, and no email address is collected for it. You can edit or delete your own comments; a deleted comment that has replies stays as a placeholder, “[deleted]”, with its text and author removed, so the replies keep their place.
To count one reaction per reader and to let anonymous authors edit their comments, we store a keyed hash of your connection (address and browser), never the address itself. An anonymous author also gets a token, kept in their browser, that proves the comment is theirs.
When you react, comment, edit or delete a comment, PostHog receives an event naming the page and the action, never the comment’s text. If you are signed in, the event includes your verified email address and your display name, which are also on your PostHog profile while you are signed in. If you are not signed in, a comment event includes the name you chose, or “Anonymous Reader”, and a name you chose is saved once to the anonymous profile PostHog keeps for your browser.
Forms you send us
When you submit an engineering inquiry on our contact page, a sprint scoping request on our service pages, an architecture discovery request on the healthcare data lake page, or a checklist signup at the end of a healthcare data guide, our server records an audit log of your submission (your name, work email, organization, submitted options, and the originating page path) in this site's secure SQLite database and dispatches a notification email to our team via Mailgun. For data lake intake requests, your confirmation that the request contains no patient data is recorded alongside the submission.
All four form types are read only by Netspective administrators and retained for 24 months before being purged automatically. To limit repeat submissions and protect against automated abuse, we store a keyed hash of your connection, never the raw address itself. Analytics never receive what you type into any of these forms. To have an inquiry, request, or signup removed sooner, write to us at the address under Questions below.
Erasing your account
To have your account erased, write to us at the address under
Questions below. We then mark the account erased, and from that
moment no further analytics are sent for it. Our erasure
procedure (scripts/telemetry/erase_posthog_user.py)
deletes your PostHog profile together with the events recorded
for it, removes your email address and name from your comments
(they then show “[deleted]” as the author) and unlinks
your reactions from the account; reaction counts stay as they
are. The text of a comment stays on the page, because other
readers may have replied to it; delete a comment yourself first
if you want its text removed too.
Your analytics choices
There is no analytics consent banner: the anonymous measures above run from your first page. If your browser sends a Do Not Track signal, PostHog does not start and nothing is sent to it; Do Not Track does not change Google Tag Manager or Google Analytics 4. Signing in links analytics to your account and turns on reading tracking, as described above; signing out ends both. A content blocker in your browser can block either service.
Questions
Reach us at hello@netspective.com or (202) 660-1351.