Useful counts.
No visitor profiles.

We use aggregate website analytics to understand which sections and interactions are useful. This is website activity measurement, not a neurological assessment.

What we count

Home and literature-review page views, clicks on the review’s listed publication links, approximate countries of page views, sections viewed, navigation clicks, FAQ openings, broad traffic-source categories, signal-diagram views, page loads with at least one domain change, signal-diagram selections, contact-option views, page loads with a contact action by placement, and actions in the contact dialog. Reports cover 90 days of daily totals. Older totals are deleted when new activity is recorded or the owner refreshes the dashboard. Publication clicks use a fixed reference identifier; destination URLs are not sent to the collector. We do not connect actions into individual browsing histories.

Diagram views and first domain changes are counted once per homepage load or return. The browser keeps only temporary in-memory flags to avoid repeat counts, and sends fixed event names to daily totals. Contact-option views and first contact actions are also counted once per page arrival, overall and by fixed placement (header / menu, Research, or Contact). Temporary in-memory flags prevent repeat counts. No page-load identifier is generated or stored. Automatic animation and the initial domain display do not count as selections.

What these analytics leave out

Our custom analytics do not set cookies or use local storage, visitor identifiers, fingerprints, or advertising trackers. They do not store precise locations, IP addresses, full referring URLs, search terms, or arbitrary campaign values. They do not collect names, email addresses, phone numbers, organizations, or message contents entered in the contact form.

Country estimates

Our hosting network estimates a country from the connection’s IP address. Our analytics reads only that country code and immediately adds it to a daily country total for a page view. We do not store the IP address, city, coordinates, or individual location records, and we do not connect countries to contact actions or visitor profiles. Missing or unrecognized countries are counted as Unknown. VPNs and network routing can affect these estimates; they do not establish a person’s residence.

Traffic sources and FAQ interest

Your browser classifies recognized campaign tags or the referring website into a fixed category, such as LinkedIn, Google, email campaign, or direct / unknown. Only that category is sent to our custom analytics. Full referring URLs, arbitrary domains, and campaign text are not sent or stored by the collector. We count the first opening of each existing FAQ per page load, using a fixed question identifier. Source and FAQ counts remain independent daily totals; we do not connect them to individual people, contact actions, or countries.

Visit timing and active viewing

We group new page loads into hourly UTC totals and show daily country totals. We do not store exact visit timestamps or connect hour totals to countries. A temporary browser timer estimates foreground viewing, pausing in hidden or unfocused tabs and after 60 seconds without interaction. It sends only fixed milestones (15 seconds, 30 seconds, 1 minute, 2 minutes, and 5 minutes), once each per page arrival. These are independent daily counts by page, not exact durations or browsing histories, and are not linked to countries or identities. They do not prove reading or attention.

Your choices

The custom analytics respect browser Do Not Track and Global Privacy Control signals. Browser blocking tools may also prevent measurement. The website continues to work when analytics are blocked.

Contact and hosting

The contact tool prepares an email in your browser. Opening your email application or copying the message does not confirm that it was sent. Only the Site owner can view our custom analytics dashboard, using ChatGPT sign-in. That sign-in may use authentication cookies.

ChatGPT Sites separately provides hosting, security, and built-in traffic analytics; its platform processing is separate from the aggregate counters described here.

Questions? rainn@cerebroneurotech.com