This Cookie Policy explains how Explained How uses cookies and similar technologies when you visit ExplainedHow.com.
Explained How is an independent educational publication founded, owned, and primarily operated by Duc Nguyen.
This policy should be read together with our:
[Privacy Policy →](/privacy-policy/)
Our general principle is:
Cookies should be used for a legitimate purpose, and readers should have meaningful information and choices where applicable.
The cookies and technologies used on Explained How may change as the website develops.
This policy explains the categories of technologies that may be used, why they may be used, and how you can manage them.
What Are Cookies?
Cookies are small text files that websites can store on your computer, phone, tablet, or other device when you visit them.
Cookies may allow a website to remember information about your visit, such as:
- preferences;
- session information;
- consent choices;
- security information;
- analytics identifiers;
- advertising information.
Some cookies disappear when you close your browser.
Others may remain for a defined period or until you delete them.
The European Commission similarly distinguishes between session and persistent cookies and between cookies set by the site itself and those associated with external services. European Commission
First-Party and Third-Party Cookies
Cookies may be classified according to who places them.
First-Party Cookies
First-party cookies are placed by ExplainedHow.com or by technology operating directly on behalf of the website.
They may be used for purposes such as:
- website functionality;
- security;
- remembering preferences;
- storing consent choices.
Third-Party Cookies
Third-party cookies may be placed by external services used on the website.
Depending on which features are active, these services may include:
- analytics providers;
- advertising networks;
- video platforms;
- social-media services;
- affiliate networks;
- security providers.
Explained How does not directly control the privacy practices of independent third-party providers.
Types of Cookies We May Use
The exact cookies present on Explained How depend on which website features and services are currently active.
| Category | Purpose | Usually optional? |
|---|---|---|
| Strictly Necessary | Security, basic website operation, consent storage, authentication | Usually no |
| Preferences | Remembering user choices or interface settings | Depends on implementation |
| Analytics | Understanding how visitors use the website | Often yes |
| Advertising | Delivering, measuring, or personalizing ads | Usually yes where consent is required |
| Affiliate Attribution | Helping a retailer or affiliate network identify referrals | Often controlled by the destination service |
| Embedded Media | Supporting services such as YouTube or social content | May require consent depending on implementation |
Strictly Necessary Cookies
Some cookies or similar technologies may be required for the website to function properly.
These may support:
- security;
- fraud prevention;
- session management;
- consent preferences;
- administrative login functions;
- load balancing;
- technical website operation.
Because these technologies may be necessary to provide a service requested by the visitor or to operate the website securely, they may not always be subject to the same optional consent controls as advertising or analytics cookies.
Blocking necessary cookies may cause parts of the website to stop working correctly.
Cookie Consent Preferences
If Explained How uses a cookie consent system, the system may need to store a cookie or similar identifier recording your choice.
For example, it may record whether you:
- accepted optional cookies;
- rejected optional cookies;
- selected specific cookie categories.
This prevents the website from asking for the same preference on every page load.
A consent-preference cookie does not necessarily mean that advertising or analytics cookies have been accepted.
Preference Cookies
Preference technologies may help remember choices such as:
- interface preferences;
- language selections;
- display settings;
- other website options.
These features are intended to improve convenience.
If preference cookies are disabled, you may need to make the same selection again on a future visit.
Analytics Cookies
Explained How may use analytics technologies to understand how the website is being used.
Analytics information may help us understand matters such as:
- which articles receive visits;
- how readers move through the site;
- which devices or browsers are commonly used;
- whether pages load correctly;
- how visitors arrive at Explained How;
- where website usability can be improved.
Analytics tools may use cookies or other identifiers.
Where applicable law requires consent before non-essential analytics technologies are activated, we aim to respect that requirement.
Google Analytics
Explained How may use Google Analytics or related Google measurement technologies if those services are enabled.
Depending on configuration and consent choices, Google Analytics may process information relating to:
- interactions with pages;
- browser or device characteristics;
- referring sources;
- approximate geographic information;
- session activity.
The presence of this section does not necessarily mean Google Analytics is active at all times.
If Google Analytics is enabled, its operation should be reflected accurately in our cookie consent system and privacy disclosures.
Advertising Cookies
Explained How may display advertising in the future or through active advertising services.
Advertising technologies may use cookies or similar identifiers for purposes such as:
- delivering advertisements;
- measuring ad impressions;
- measuring conversions;
- limiting repeated advertising;
- detecting invalid traffic or fraud;
- personalizing advertising where permitted.
Advertising cookies may involve third-party providers.
Google AdSense and Google Advertising
If Explained How uses products such as Google AdSense, Google may use cookies or similar technologies in connection with advertising delivery, measurement, fraud prevention, and, where permitted, personalization.
For publishers using Google AdSense, Ad Manager, or AdMob to serve personalized advertising to users in the EEA, United Kingdom, or Switzerland, Google currently requires an appropriate Google-certified consent management platform integrated with the IAB Transparency and Consent Framework. Hỗ trợ Google
Explained How should only describe Google advertising cookies as active when the relevant advertising products are actually enabled.
Personalized and Non-Personalized Advertising
Depending on:
- your location;
- consent choices;
- applicable law;
- advertising configuration;
advertising may be personalized or non-personalized.
Personalized advertising may use information about activity or interests to help select advertisements.
Non-personalized advertising may rely more heavily on contextual information, such as the content being viewed.
Non-personalized advertising does not necessarily mean that no cookies or technical processing occur.
Some technologies may still be necessary for:
- frequency control;
- fraud prevention;
- reporting;
- security.
Affiliate Tracking Technologies
Explained How may participate in affiliate programs.
When you click an affiliate link, the retailer or affiliate network may use cookies, URL parameters, or other technologies to identify that the visit originated from Explained How.
This allows the provider to determine whether a qualifying purchase should be attributed to our referral.
Affiliate tracking may involve:
- referral identifiers;
- click identifiers;
- attribution cookies;
- transaction information.
These technologies are generally controlled by the relevant retailer or affiliate network after you leave Explained How.
Read:
[Affiliate Disclosure →](/affiliate-disclosure/)
Amazon Affiliate Links
If Explained How participates in Amazon Associates and you click an Amazon affiliate link, Amazon may use referral and tracking technologies to determine whether a qualifying purchase resulted from that referral.
Those technologies operate according to Amazon’s own policies and systems.
Explained How does not control Amazon’s cookie settings after you leave our website.
The inclusion of this section does not mean Explained How is currently an active Amazon Associate unless participation is disclosed elsewhere on the website.
Embedded YouTube Content
Explained How may embed videos from the official Explained How YouTube channel or other YouTube content.
When a YouTube player is embedded on a page, interaction with that player may result in communication with Google or YouTube.
Depending on:
- how the video is embedded;
- your browser;
- your Google account status;
- consent settings;
YouTube may process cookies or other information.
Where appropriate, Explained How may use privacy-enhanced embedding or block third-party media until relevant consent is obtained.
Facebook and Social Media
Explained How may link to or embed content from services such as Facebook.
Simply linking to a social-media page is different from embedding a third-party widget directly into the website.
An embedded feature may allow the third-party provider to receive technical information about the visit.
When such features are used, their associated cookies and privacy practices are controlled by the relevant platform.
Explained How provides a WhatsApp contact link.
A normal link to WhatsApp does not necessarily place a WhatsApp cookie on Explained How itself.
However, after you follow the link and enter WhatsApp’s website or application, WhatsApp’s own privacy and cookie practices apply.
Security Technologies
Explained How may use security services designed to:
- detect malicious requests;
- prevent spam;
- protect login pages;
- block automated attacks;
- detect fraud;
- maintain website availability.
Some security services may use cookies or similar technical identifiers.
Where those technologies are strictly necessary for website security, they may operate differently from optional analytics or advertising cookies.
Anti-Spam Services
If contact forms or comment functionality are available, anti-spam systems may process information to distinguish legitimate activity from automated or malicious submissions.
Depending on the provider, this processing may involve:
- IP addresses;
- request patterns;
- browser information;
- cookies or similar technologies.
The specific provider should be disclosed when one is actively used and its processing is relevant to visitors.
WordPress Cookies
Explained How is built using WordPress.
WordPress may use cookies in connection with functions such as:
- administrator login;
- user authentication;
- session preferences;
- comments, if enabled.
Most ordinary readers who are not logged into WordPress may not encounter the same cookies as website administrators.
The exact cookies depend on the site’s configuration and plugins.
Comments
If public comments are enabled, WordPress or related plugins may offer cookies that remember information such as:
- commenter name;
- email address;
- website.
These may exist to make future commenting more convenient.
If comments are not enabled, this category may not apply.
Contact Forms
Submitting a contact form does not necessarily require advertising cookies.
However, security or anti-spam technology associated with a form may use cookies or technical identifiers.
Any third-party form or anti-spam provider should be reflected in this policy and our Privacy Policy where appropriate.
Similar Technologies
This policy uses the term cookies for convenience, but websites may also use other technologies capable of storing or accessing information.
These can include:
- local storage;
- session storage;
- browser identifiers;
- pixels;
- tags;
- SDKs;
- tracking parameters.
Where relevant, references to cookies in this policy may also include similar technologies.
Session Cookies
Session cookies generally remain available only during a browsing session and are removed when the session or browser is closed.
They may be used for functions such as:
- temporary session management;
- authentication;
- website navigation.
Persistent Cookies
Persistent cookies remain on your device for a defined period or until deleted.
They may be used to remember:
- consent preferences;
- website settings;
- analytics identifiers;
- advertising choices.
The retention period depends on the cookie and provider.
Cookie Duration
Cookies can have different expiration periods.
Some may last:
- for a single session;
- several minutes;
- several days;
- several months;
- longer where legitimately required.
Explained How should not claim one universal duration for all cookies because third-party services may use different retention periods.
Where technically possible, the current cookie preference interface may provide additional details about individual cookies.
Current Cookie Inventory
The exact cookie names used by Explained How should be based on a scan of the live website, not copied from a generic policy template.
For that reason, we do not intentionally list cookies that may not exist on the site.
As Explained How activates services such as analytics, advertising, consent management, embedded media, or other integrations, this section should be updated with an inventory such as:
| Cookie / Technology | Provider | Purpose | Category | Duration |
|---|---|---|---|---|
| Consent preference | Explained How / CMP | Remember cookie choices | Necessary | Depends on configuration |
| Analytics identifier | Analytics provider | Website measurement | Analytics | Depends on provider |
| Advertising identifier | Advertising provider | Ad delivery/measurement | Advertising | Depends on provider |
| Affiliate tracking | Retailer/network | Referral attribution | Affiliate | Depends on provider |
This table should eventually be replaced or supplemented with the actual cookies detected on the production website.
Your Cookie Choices
Where a consent-management system is available, you may be able to choose whether optional technologies are activated.
Typical choices may include:
Accept All
Allow permitted optional categories.
Reject Non-Essential
Continue using technologies required for core functionality while preventing optional categories where supported.
Manage Preferences
Choose individual categories.
The exact wording and categories may differ depending on the consent system used.
Withdrawing Consent
Where processing relies on your consent, you should be able to withdraw that consent as easily as reasonably possible.
Explained How should therefore provide a persistent way to reopen cookie settings when a consent platform is active.
A typical footer link may be:
Cookie Settings
or:
Manage Privacy Choices
Changing a preference generally affects future cookie use.
It may not automatically delete every cookie already stored on your device.
Deleting Cookies
Most browsers allow you to:
- inspect cookies;
- delete individual cookies;
- delete all cookies;
- block cookies;
- restrict third-party cookies.
The exact controls depend on your browser.
Deleting cookies may remove stored preferences, including your previous consent choice.
As a result, the website may ask you to set your preferences again.
The European Commission similarly notes that browser controls can be used to delete or block cookies, although doing so may affect site functionality. European Commission
Blocking Cookies Through Your Browser
You may configure your browser to reject some or all cookies.
However, completely blocking cookies may interfere with:
- security features;
- login functionality;
- saved preferences;
- interactive website features.
Explained How does not guarantee that every feature will function normally when all browser storage is disabled.
Consent by Region
Privacy and cookie requirements differ between jurisdictions.
Explained How may therefore present different consent options depending on factors such as:
- visitor region;
- applicable law;
- active services;
- advertising configuration.
We do not assume that one identical cookie banner is legally sufficient everywhere.
Visitors in the EEA and United Kingdom
Depending on the services being used, certain optional cookies or similar technologies may require consent before they are activated.
Explained How aims to configure relevant technologies accordingly where applicable.
If Google advertising publisher products are used for personalized advertising in the EEA or UK, Google’s current publisher requirements include use of an appropriate certified CMP integrated with the IAB TCF. Hỗ trợ Google
Visitors in Switzerland
Google currently applies similar certified-CMP requirements to publishers serving personalized advertising using its relevant publisher products to users in Switzerland. Hỗ trợ Google
These are Google product requirements and do not by themselves represent a complete statement of all applicable privacy law.
United States Privacy Choices
Certain U.S. state privacy laws may provide users with rights regarding specific advertising or data-sharing practices.
If Explained How engages in activities that trigger those requirements, appropriate mechanisms should be implemented.
The presence of cookies does not automatically mean that Explained How legally “sells” personal information.
The answer depends on:
- the technology;
- the purpose;
- the parties involved;
- applicable law.
Global Privacy Control
Some browsers and extensions can transmit privacy preference signals such as Global Privacy Control.
Where applicable law requires Explained How to recognize such a signal for particular processing, our systems should be configured accordingly.
This is separate from ordinary browser cookie blocking.
Third-Party Services
Third-party services may modify:
- cookie names;
- retention periods;
- technologies;
- privacy practices.
Explained How does not control those changes.
For that reason, readers who interact with third-party services should also review the privacy or cookie information provided by those services.
Do Cookies Identify You Personally?
A cookie does not necessarily contain your:
- name;
- email address;
- phone number.
However, cookies and similar identifiers may still be considered personal information or personal data in some jurisdictions when they can identify or distinguish a device, browser, or individual.
For that reason, technical identifiers should not automatically be treated as anonymous simply because they do not contain a person’s name.
We Do Not Use Cookies to Fabricate Editorial Experience
Cookies and analytics may tell us how readers interact with pages.
They do not justify editorial statements such as:
“Our customers found…”
or:
“Users universally prefer…”
unless the data actually supports such a claim and the methodology is explained appropriately.
Analytics are operational data, not permission to invent research conclusions.
Cookie Data and Editorial Independence
Advertising or analytics data should not determine factual conclusions in Explained How articles.
For example, the fact that an article receives significant traffic does not change:
- the scientific mechanism;
- a technical specification;
- a correction;
- the strength of available evidence.
Our editorial standards remain separate from our analytics and monetization systems.
Children and Cookies
Explained How is a general educational publication.
We do not intentionally use the website to build behavioral advertising profiles of children in violation of applicable law.
If the site’s services or audience materially change in a way that requires additional protections, our cookie practices should be updated accordingly.
Changes to Our Cookie Technologies
Explained How may add, remove, or replace technologies over time.
For example, we may:
- introduce analytics;
- change analytics providers;
- begin displaying advertising;
- change consent platforms;
- add embedded media;
- remove an integration.
When those changes materially affect cookie use, this policy should be updated.
Changes to This Cookie Policy
We may revise this Cookie Policy when:
- our website changes;
- our service providers change;
- our cookie practices change;
- legal requirements change;
- advertising or analytics technologies are introduced.
The Last updated date should reflect meaningful changes.
We do not change the date merely to make the policy appear newer.
Contact Us About Cookies
If you have questions about cookies, tracking technologies, or privacy choices on Explained How, contact:
Duc Nguyen
Explained How
Email:
30***********@***il.com
WhatsApp:
+84 909 942 697
Facebook:
Duc Nguyen
Website:
ExplainedHow.com
For privacy-related requests, email is preferred.