✦

Relax, Prof. Peter’s Advisory is establishing your connections...

Cookie Policy — Prof. Peter’s Paper Trails

Last Updated: July 2026

Domain: profpeter.online

Operating Entity: Prof. Peter’s Paper Trails (Putrajaya, Malaysia)

At Prof. Peter’s Paper Trails, we prioritize transparency, digital hygiene, and complete user privacy. Our digital architecture is developed strictly in-house without third-party marketing plugins, advertising networks, or external tracking brokers. We do not sell, store, or share your data with external ad networks.

This Cookie Policy explains how and why minimal, essential cookies and local storage tokens are used on profpeter.online.

1. Our Privacy First Architecture

Unlike standard commercial platforms, our infrastructure relies on custom-developed code (no strings attached). We do not run third-party marketing or profiling scripts.

2. Categories of Cookies Used

We only deploy cookies that are strictly necessary for the site to function securely and efficiently.

A. Strictly Necessary & Functional Cookies (WordPress Core)

These cookies are mandatory for authentication, secure gateway access, and maintaining user sessions.

  • Session & Authentication Cookies: wordpress_logged_in_[hash], wordpress_sec_[hash] — Used by WordPress to manage active login sessions and verify system identity.
  • Test Cookie: wordpress_test_cookie — Checks whether your browser has cookies enabled.
  • Security & SSO Tokens: Temporary authentication query keys (yp_token) generated locally to allow single sign-on across our infrastructure (profpeter.info and profpeter.online).

B. Analytical & SEO Performance Tools (Planned)

To monitor site health, index technical search performance, and optimize content structure, we utilize standard performance integration via Google Site Kit and Google Search Console.

  • Purpose: Measuring aggregate, anonymized traffic trends, indexing errors, and search engine ranking metrics.
  • Impact: No individual profiling or cross-site tracking across secondary websites.

3. Server-Side Processing & API Integrations

We utilize several automated APIs and mail dispatch mechanisms. To protect your data, these systems operate server-side, meaning no client-side tracking cookies are stored on your computer by these services.

  • DeepL API (Paid Edition): Used strictly on our web server to translate publications dynamically. No personal user data or client cookies are transmitted to DeepL.
  • Google Gemini API (Paid Edition): Used for internal AI contextual assistance and formatting. Interactions are executed via direct server-to-server calls without client-side cookies.
  • FluentSMTP & Google Workspace (Gmail): Transactional system emails and newsletter dispatches are transmitted via secure SMTP through our official Google Workspace endpoints. Email interactions do not install tracking cookies on your device.

4. Summary Table of Cookie Declarations

Cookie / Token Name Origin Category Purpose Expiration
wordpress_test_cookie First-Party Essential Verifies if cookie storage is supported by browser Session
wordpress_logged_in_* First-Party Essential Stores authentication context for logged-in nodes Session / 14 Days
wordpress_sec_* First-Party Security Encrypted key used to protect user account data Session
yp_token First-Party Security / SSO Secure token generated for gateway cross-domain transit Temporary (7 Days)

5. How to Manage or Block Cookies

Since we only use essential functional cookies, disabling them via your browser may impact your ability to log in or navigate restricted areas.

You can manage or delete cookies at any time via your browser settings:

  • Google Chrome: Settings → Privacy and Security → Cookies and other site data
  • Mozilla Firefox: Options → Privacy & Security → Cookies and Site Data
  • Apple Safari: Preferences → Privacy → Manage Website Data

6. Questions & Data Protection Officer

If you have questions regarding this Cookie Policy or our system architecture, please contact us: