This page explains what happens on www.jaredstyan.com when someone visits it, described only in terms that match how the site is actually built. It covers a small counting mechanism, the way pages are delivered, and what happens when a reader follows a link away from this domain.
Counts Arrivals From Search Engines
When a visitor arrives from a search engine, the site records a small set of details: the path of the page visited, the type of event, the name of the referring search engine, and, if applicable, the text of an outbound button that was clicked. This information is used only to count page views and clicks on outbound buttons — nothing more. It is not collected for visitors who arrive by other means, such as typing the address directly or following a direct link.
Uses A Session Flag To Avoid Double-Counting
To make sure a single page view is not counted more than once, the site keeps one flag in the browser for the current session. This flag does not identify the visitor personally, does not persist after the session ends, and is not used for any purpose beyond preventing duplicate counts within that visit. No other browser storage is set, and no persistent identifier is created or kept.
Serves Static Files From A Content Delivery Network
This site consists of self-contained pages with locally embedded fonts, served as static files by a content delivery network. As the hosting provider, that network processes the technical data of every request in order to deliver the page. No page depends on an outside host while it is being displayed: every file a page needs, including its fonts, comes from this domain. No third-party analytics tools and no external subresources are loaded.
Handles Outbound Links Through A First-Party Redirect
Some pages contain outbound links to third-party sites. When one of these links is followed, the click first goes to a path on this domain and is then redirected to the partner site. This first-party redirect step does not share any stored visitor data with the partner. Once the redirect completes, the partner site receives the request directly from the visitor's browser and keeps its own separate record of that visit. This site has no way to see or influence what the partner site does with that request, and it does not control the privacy practices of any site reached this way.
Confirms What Is Not Collected Or Shared
Several things are confirmed as absent from this site. There are no forms anywhere on the site, so no visitor ever types information into a field here. There are no third-party analytics services in use, no external subresources loaded from other domains, and no contact channels of any kind on the site. The site does not use cookies. It does not collect personal data such as names, e-mail addresses, account identifiers or payment details, and it does not retain personal information about any individual visitor. It has no login, no registration and no user account. Visit data collected for counting purposes is not shared with advertising networks, data brokers or outside analytics services.
Together, these absences are why the site does not ask for consent, does not require an account, and never requests a personal detail from anyone reading it. Because there are no forms and no contact channels here, readers should not attempt to submit personal data through this site, and should treat any third-party site reached through an outbound link as a separate destination with its own separate handling of whatever is sent to it.