Privacy

Privacy overview

This page summarizes the data handling visible in the current version of the site. It is an informational overview, not a substitute for jurisdiction-specific legal advice.

Current stack

A lightweight PHP content site with static guides, outbound links, and limited first-party interaction.

Third-party layer

The current analytics behavior is tied to PrivacyCounter and the policies of any destination sites you visit.

Main boundary

Reading a guide page and moving into an external test flow are separate privacy contexts that should be evaluated separately.

This page is a practical privacy overview, not a maximal legal document. It is meant to describe the data-handling behavior that is visible from the current site setup: static informational pages, outbound links, and a third-party analytics script. If those technical facts change, this page should change with them.

What this site currently does

  • Serves informational pages about IQ testing and score interpretation
  • Loads a third-party analytics script from PrivacyCounter
  • Links out to third-party pages, including the external test flow
  • Does not currently expose a public contact form or account system on-site

Analytics

The current site includes a third-party analytics script from PrivacyCounter. Third-party analytics providers may collect technical data such as page visits, browser details, or approximate usage patterns according to their own systems and policies.

Because the analytics layer is external, readers should understand that this page can only describe the site’s visible integration, not override the provider’s own policies. If the analytics vendor changes its data practices, that may matter even when the visible site markup looks similar. That is why the provider itself is linked in the references below.

Outbound links

Some calls to action lead to external sites. When you follow one of those links, you leave Reliable IQ Test and become subject to the privacy and data practices of the destination website. That includes the external test flow.

From a user perspective, this is one of the most important privacy boundaries on the site. Reading a guide page and entering a different test or result flow are not the same event. A privacy-aware reader should evaluate both environments separately.

Current limitation

Because this site may evolve, the privacy overview should be reviewed whenever new forms, cookies, embedded services, or account features are added.

Cookies and local storage

The site itself is currently built as a lightweight PHP front end with static informational content. If third-party tools set cookies or similar identifiers, that behavior is controlled by those external services rather than by a custom on-site user account system.

This means the simplest way to evaluate privacy exposure today is to separate first-party behavior from third-party behavior. The current site does not expose sign-in, messaging, or payment features, but third-party analytics or destination sites may still introduce their own tracking mechanics.

What is not currently visible on-site

  • No public user account system.
  • No on-site payment checkout.
  • No first-party contact form collecting messages directly through the site interface.
  • No newsletter signup flow published on the current pages.

How to evaluate privacy changes

If future updates add forms, newsletters, payment processing, or more advanced tracking, this page should be replaced with a fuller privacy policy describing data categories, retention, lawful basis where relevant, and user rights.

In other words, the current overview is only adequate because the present site architecture is relatively simple. If the product layer becomes more complex, the privacy documentation will need to move from “overview” to a proper policy with more specific operational detail.

Sources and further reading

Continue reading

Use these pages to see how privacy, contact flow, and site methodology fit together in the current trust stack.

Contact

See the current path for correction requests and transparency questions.

Methodology

Review how the site approaches evidence, limitations, and content updates.

About

Understand the site’s scope, intended use, and current content direction.