Privacy Policy v1.0

Effective Date: December 3, 2025

This Privacy Protocol document outlines the measures taken to protect user privacy within this repository and portfolio application. Our policy is designed around the core principle of Zero-Collection Privacy by Design for all public interactions.

1. Data Collection & Analytics

We are committed to operating this repository without collecting, storing, or analyzing visitor data. The following measures are strictly enforced:

• Zero-Tracking Policy: We do not use third-party analytics (Google Analytics, etc.), server-side IP logging, geographical location tracking (GeoIP), or user-agent fingerprinting.
• No Personal Identifiable Information (PII): We do not collect names, email addresses, phone numbers, or any other PII from public visitors.
• No Cookies for Tracking: Cookies are not used for tracking, profiling, or behavioral analytics. Session cookies are used strictly to maintain state for administrative access (e.g., login status) and are immediately destroyed upon logout or session expiry.

2. Technical Footprint Minimization

The system is architected to leave the smallest possible digital footprint on the user's device:

• No Local Storage or IndexedDB: The application does not write data to the client's Local Storage or IndexedDB.
• No Third-Party Scripts: Except for essential, universally recognized frameworks (e.g., Tailwind CSS via CDN for styling), no external scripts that could compromise privacy are loaded.
• Referrer Policy: HTTP headers are configured (`Referrer-Policy: strict-origin-when-cross-origin`) to minimize the amount of information sent to other sites if a user clicks an external link.

3. Administrative Access Security (Internal Data Handling)

Data handling for the secured administrative login is governed by these stringent internal rules:

• Encrypted Credentials: Passwords are not stored in plain text. They are secured using bcrypt with a strong salt and hashing algorithm.
• Mandatory 2FA: Access requires verification via a Time-based One-Time Password (TOTP) using Speakeasy, ensuring credential exposure alone is insufficient for access.
• Session Management: Admin sessions are secured using Express Sessions with protective flags (`httpOnly`, `secure`, `SameSite: Lax`).

4. Changes to This Protocol

This protocol may be updated periodically. Any changes will be posted here immediately, and the revision date will be adjusted. Continued use of the public repository constitutes acceptance of the current protocol.

5. Contact & Inquiries

For any questions regarding this protocol, please refer to the contact methods provided on the main repository dashboard.

« Return to Dashboard