Cookie Policy | Male Vitalis

Effective 5 November 2026

1. What this policy covers

This Cookie Policy explains browser storage and externally loaded resources used by Male Vitalis at malevitalis.info. It should be read together with the Privacy Policy, which describes contact messages and wider personal-information handling. The word cookie is sometimes used broadly, but the main preference record here uses localStorage, a different browser storage mechanism. This policy distinguishes the two so readers can understand what is actually implemented. The site contains no user accounts, shopping cart, advertising network, embedded social feed, or analytics dashboard. Reading an article does not enroll you in a marketing programme or create a health profile.

2. Necessary session storage on the contact page

The contact page uses a PHP session cookie named MVSESSID. Its purpose is to associate the browser with a random anti-forgery token and recent submission timing. This helps the server validate a form submission and reject rapid repeats. The cookie is marked HttpOnly and SameSite=Lax, and Secure when the connection uses HTTPS. It does not contain your message text or email address. It is a browser-session cookie rather than a persistent advertising identifier. Browsers with session-restore features may retain session cookies across a restart, so closing a window is not always equivalent to clearing stored data.

3. The preference record

The site stores your selected mode in a localStorage item named mv_consent. The record contains the choice and a timestamp. It is used on later visits to apply the preference and avoid repeatedly displaying the banner. The site treats a record older than 180 days as expired, removes it when encountered, and asks for a new choice. localStorage does not itself have a built-in expiry time; the expiry is enforced by the site's script when it runs. The preference record does not contain a list of articles read, search terms, contact messages, or personal demographic information.

4. Functional choice

Functional allows the necessary preference record and contact-form session while declining optional externally hosted fonts. Page text uses local system fallback fonts, and the article links, menu, filters, and contact controls remain available. Core presentation styles are served from this website and remain available in Functional mode. Choosing Functional closes the banner and stores that choice when browser storage is available. It does not prevent you from changing your mind later through Cookie preferences in the footer.

5. Partial choice

Partial enables the optional Google Fonts resource for the two typefaces used in the design: Manrope and Source Sans 3. The browser requests the stylesheet from fonts.googleapis.com and font files from fonts.gstatic.com. Those services receive the technical information ordinarily needed to respond to a network request, such as an IP address and browser details. The site does not send contact-form fields or article-search text to the font service. No analytics or marketing category is activated by Partial. This option is a defined limited preference, not a hidden selection of advertising partners or an instruction to install future optional tools.

6. Accept All choice

Accept All enables every optional resource currently implemented, which at present means the same Google Fonts resource enabled by Partial. The two modes are stored distinctly, but their current network behavior is the same because there are no optional analytics or advertising scripts. Accept All is not prospective permission for unknown future tracking. If the site introduces a materially different optional service, the policy and preference interface must be updated and a fresh choice obtained before that service runs where required. None of the three choices changes the articles available to you or makes payment necessary to continue reading.

7. Changing a preference

Use the Cookie preferences button in any page footer to reopen the preference dialog. It describes the current options and lets you select Accept All, Partial, or Functional again. A new choice replaces the existing record and starts a new 180-day preference period. Switching to Functional removes the optional font stylesheet from the current page and prevents it being loaded on subsequent visits while the choice remains valid. It cannot undo requests already made or erase files retained in the browser's resource cache. You may clear cached files separately using your browser's settings if you want to remove those local copies.

8. Browser controls and restricted storage

Most browsers let you clear cookies and site data for a particular domain, block storage, or browse in a private session. Exact menu names vary by browser and device. Clearing site data removes the saved choice, so the banner may appear again. Blocking session cookies can prevent the contact form from validating its anti-forgery token. If localStorage is unavailable, the preference control still applies the choice in the current page, but it cannot remember it on another page or visit. The interface reports that limitation. A browser-level setting may also block externally hosted fonts or scripts independently of the site's preference.

9. Other scripts, searches, and external links

The local js/runtime.min.js file manages menus, FAQ panels, article filtering, contact submission, the preference dialog, and the banner. No optional plugin bundle is required. Blog searching filters the article catalogue in the browser and may put the search text in the page URL for sharing or reloading. The application does not send search terms to a separate search provider. External reference links open the named third-party websites when you follow them; those websites apply their own storage policies. Ordinary HTTP caching of stylesheets and images is separate from the preference record and may occur according to browser and server settings.

10. Retention, responsibility, and contact

The preference record is treated as valid for 180 days. The contact session is reset after 30 minutes of inactivity, while deletion of old server session files also depends on hosting configuration. No first-party analytics identifiers are created by this implementation. Providers may process network logs under their own arrangements, which the site's localStorage controls do not erase. Questions about storage or a difficulty changing preferences can be sent to [email protected] or by post to Block A, Candi Rejo, Sibiru-biru District, Deli Serdang Regency, North Sumatra 20358, Indonesia. This policy describes the deployed code's intended behavior and must be updated before additional tracking or embedded services are introduced.