@networkpro/web 1.11.0 → 1.12.3

package/static/docs/pgp-email.md

@@ -0,0 +1,152 @@
+# 📧 Encrypting Email with PGP
+
+> This guide walks you through using PGP (Pretty Good Privacy) to encrypt email using both graphical and client-based tools.
+
+PGP encryption ensures that only the intended recipient can read your email content — even if it's intercepted.
+
+---
+
+## 🔹 Option A: Outlook (Windows) with GpgOL
+
+GpgOL is a plugin included with **Gpg4win** that integrates directly into Microsoft Outlook (desktop only).
+
+### ✅ Requirements
+
+- Gpg4win (with GpgOL selected during installation)
+- Outlook 2010 or newer (desktop version)
+- Recipient’s **public key**
+
+> ⚠️ GpgOL does not work with Outlook for Microsoft 365 Web or Outlook Mobile. It is only compatible with the **desktop edition of Outlook** on Windows.
+
+### 📥 Encrypting an Email in Outlook
+
+1. Open Outlook and compose a new message
+2. Enter the recipient’s email address (must match imported key)
+3. Click the `Encrypt` button on the **GpgOL ribbon** tab
+4. Send your email
+
+> ✉️ Outlook will encrypt the email contents using the recipient's public key.
+
+### 📥 Decrypting an Email in Outlook
+
+When receiving an encrypted message:
+
+- GpgOL will automatically prompt to decrypt it using your private key
+- You may need to enter your key passphrase
+
+> 💡 Tip: Manage keys with **Kleopatra** — launch from Start Menu
+
+---
+
+## 🔹 Option B: Thunderbird (Windows/macOS/Linux)
+
+Thunderbird includes **built-in OpenPGP** support and is often preferred for privacy-focused users.
+
+### ✅ Setup
+
+1. [Download Thunderbird](https://www.thunderbird.net)
+2. Add your email account
+3. Go to: `Account Settings → End-to-End Encryption`
+4. Generate a new key, or import your existing one
+5. Import your recipient’s **public key**
+
+### 🔐 Sending Encrypted Email
+
+When composing a message:
+
+- Click the **padlock** icon to enable encryption
+- Click **sign** if you also want to verify authenticity
+- Send as usual
+
+---
+
+## 🔹 Option C: Webmail with Mailvelope
+
+**Mailvelope** adds OpenPGP support to Gmail, Outlook.com, Yahoo, and others.
+
+### 🔧 Setup
+
+1. Install [Mailvelope](https://www.mailvelope.com/) for Chrome or Firefox
+2. Import your keys or generate a new pair
+3. Use the Mailvelope overlay when composing encrypted emails
+
+---
+
+## Alternative PGP-Compatible Email Clients
+
+In addition to widely used options like Outlook (via GpgOL) and Thunderbird, several other desktop email clients offer OpenPGP support—either natively or through plugins.
+
+Notable alternatives include:
+
+- **[Betterbird](https://www.betterbird.eu/):**  
+  A privacy-focused Thunderbird fork with full PGP support.  
+  ▸ Available on Windows, Linux, and macOS.
+
+- **[eM Client](https://www.emclient.com/):**  
+  A feature-rich client with native OpenPGP integration and calendar/task support.  
+  ▸ Available on Windows, macOS, Android, and iOS.  
+  ▸ _Free tier supports 2 email accounts after a 30-day trial._
+
+> 💡 **Note:** Be sure to verify the client’s compatibility with your GPG keyring (e.g., Gpg4win or Kleopatra on Windows).
+
+---
+
+## 📱 Mobile Email Clients with OpenPGP Support
+
+For secure email on Android, the following apps support OpenPGP encryption via [**OpenKeychain**](https://www.openkeychain.org/):
+
+- **[FairEmail](https://email.faircode.eu/)**  
+  A lightweight, privacy-first email client for Android, offering built-in OpenPGP support, rich customization, and a modern, privacy-respecting interface.
+
+- **[K-9 Mail](https://k9mail.app/)**  
+  A veteran open-source Android mail client known for its simplicity and transparency. K-9 is now maintained by the Thunderbird team as part of their mobile strategy.
+
+- **[Thunderbird Mobile](https://www.thunderbird.net/en-US/mobile/)**  
+  A mobile adaptation of Thunderbird, currently built on K-9 Mail and maintained by the same team. Provides end-to-end encryption and an open-source, user-friendly experience.
+
+> ⚠️ OpenPGP support on iOS is limited due to platform restrictions.  
+> Most options are proprietary or require external tools, and may not provide full compatibility with standard PGP workflows.
+
+---
+
+## 📤 Exporting and Sharing Public Keys
+
+You can export your public key from **Kleopatra**, Thunderbird, or the command line, and share it via:
+
+- Your website
+- A keyserver (e.g., [keys.openpgp.org](https://keys.openpgp.org))
+- Your GitHub profile (e.g., in `SECURITY.md` or a `PGP-KEY.asc` file)
+
+### 🔧 Export via Command Line
+
+If you’re using GnuPG directly:
+
+```sh
+gpg --armor --export your@email.com > publickey.asc
+```
+
+This creates a text-formatted (`.asc`) version of your public key that’s easy to upload or embed.
+
+> 💡 Replace `your@email.com` with the email associated with your PGP key.
+
+---
+
+## 🛠 Troubleshooting Tips
+
+- Ensure email address in key matches recipient’s address
+- Key must be **trusted/imported** before encryption works
+- For Outlook, restart if GpgOL ribbon does not appear
+- Thunderbird may require re-indexing of OpenPGP keyring
+
+---
+
+## 📚 Learn More
+
+- [Gpg4win Documentation](https://gpg4win.org/documentation.html)
+- [How to Encrypt Emails with OpenPGP in Thunderbird (2022)](https://www.linuxbabe.com/security/encrypt-emails-gpg-thunderbird)
+- [Mozilla OpenPGP Docs](https://support.mozilla.org/en-US/kb/openpgp-thunderbird-how-does-it-work)
+- [Mailvelope Overview](https://www.mailvelope.com/help)
+
+---
+
+> 🔐 PGP protects your communication, but both parties must be using it correctly. Always test before sending sensitive content.

package/static/docs/pgp-win.md

@@ -0,0 +1,67 @@
+# 💻 Using PGP on Windows (Gpg4win & Kleopatra)
+
+## This section walks through encrypting a message or file using **Gpg4win** and its GUI tool **Kleopatra**
+
+### 📦 1. Install Gpg4win
+
+- Download from: [https://gpg4win.org](https://gpg4win.org)
+- During setup, make sure **Kleopatra** is selected.
+
+---
+
+### 🔑 2. Import the Recipient’s Public Key
+
+1. Open **Kleopatra**
+2. Click `File` → `Import Certificates…`
+3. Select the `.asc` or `.gpg` file you downloaded
+4. Confirm the fingerprint matches the published value
+
+---
+
+### ✍️ 3. Encrypt a Message (Text)
+
+1. In Kleopatra, go to `Tools` → `Clipboard` → `Encrypt`
+2. Paste your message
+3. Select the recipient’s public key
+4. Click **Encrypt**
+5. Copy or save the armored output (begins with `-----BEGIN PGP MESSAGE-----`)
+
+You can now send that encrypted message via email or any communication platform.
+
+---
+
+### 📁 4. Encrypt a File
+
+1. Right-click on any file (e.g., PDF or TXT)
+2. Choose **More GpgEX options** → **Encrypt**
+3. Select the recipient key
+4. The encrypted file will be saved with a `.gpg` extension
+
+---
+
+### 🔓 5. Decrypt a Message or File
+
+To decrypt a file:
+
+- Right-click `.gpg` file → **Decrypt and verify**
+
+To decrypt a clipboard message:
+
+- In Kleopatra, go to `Tools` → `Clipboard` → `Decrypt/Verify`
+- Paste the encrypted message
+- Kleopatra will prompt for your private key if needed
+
+---
+
+### 🧠 Tips for Windows Users
+
+- Your private key is protected by a passphrase — never share it.
+- You can export your public key for others to encrypt messages to you.
+- Kleopatra also supports **signing** files and messages to verify your identity.
+
+---
+
+📘 For full walkthroughs, see:
+
+- [Gpg4win Documentation](https://gpg4win.org/documentation.html)
+- [Kleopatra User Guide (PDF)](https://files.gpg4win.org/doc/gpg4win-compendium-en.pdf)

package/static/docs/pgp.md

@@ -0,0 +1,71 @@
+# 🔐 How to Encrypt Messages Using PGP
+
+This guide explains how to encrypt a message or file using PGP (Pretty Good Privacy) for secure communication with **Network Pro Strategies** or any contact with a published PGP key.
+
+---
+
+## 📥 1. Obtain the Recipient's Public Key
+
+You can find the official public key at:
+
+- [https://netwk.pro/pgp](https://netwk.pro/pgp)
+- Or via GitHub, Keybase, or direct contact
+
+Make sure the key fingerprint matches what the recipient advertises.
+
+---
+
+## 🔧 2. Import the Public Key
+
+Save the public key as a `.asc` or `.gpg` file, then run:
+
+```bash
+gpg --import path/to/public-key.asc
+```
+
+You can confirm the key is imported:
+
+```bash
+gpg --list-keys
+```
+
+## 🔏 3. Encrypt a Message
+
+To encrypt a plain text file (e.g. message.txt) for the recipient:
+
+```bash
+gpg --encrypt --armor --recipient recipient@example.com message.txt
+```
+
+- --armor creates ASCII-formatted output
+- Output is saved as message.txt.asc
+
+## 🔏 4. Encrypt a File (Binary or Attachment)
+
+```bash
+gpg --encrypt --recipient recipient@example.com file.pdf
+```
+
+This will create file.pdf.gpg, which you can send securely.
+
+## 🔓 Optional: Decrypting (For Testing)
+
+If you're the recipient and want to decrypt a file:
+
+```bash
+gpg --decrypt file.txt.asc
+```
+
+## 🔐 Tips
+
+- Always verify the recipient’s key fingerprint.
+- Never share your private key.
+- Use a strong passphrase to protect your keypair.
+
+---
+
+📘 For more help, see:
+
+- [GnuPG Documentation](https://gnupg.org/documentation/)
+- [A Practical Guide to GPG](https://www.linuxbabe.com/security/a-practical-guide-to-gpg-part-1-generate-your-keypair)
+- [OpenPGP Best Practices](https://help.riseup.net/en/security/message-security/openpgp/best-practices)

package/static/docs/tracking.md

@@ -0,0 +1,63 @@
+# Tracking Preferences & Privacy Signals
+
+<!-- markdownlint-disable MD018 -->
+
+## Overview
+
+This document explains how Network Pro handles analytics tracking in a privacy-aware, user-consented, and standards-compliant manner. It covers:
+
+- Tracking preference storage (cookies)
+- Browser signals (DNT and GPC)
+- Reconsent logic
+- Reactive store architecture
+
+### 🔐 Principles
+
+- **Privacy by default**: Tracking is disabled when browser signals indicate user preference (DNT/GPC).
+- **Explicit consent**: Users may opt-in or opt-out manually, overriding signals.
+- **Persistent choice**: Consent state is remembered via first-party cookies.
+- **Transparency**: The tracking status is shown to users in the UI.
+
+### 🧠 Architecture Summary
+
+- **Store**: `src/lib/stores/trackingPreferences.js`
+  - Consolidates logic for cookie preferences, browser signals, and consent state.
+  - SSR-safe, reactive, and fully declarative.
+- **Deprecated**:
+  - `utils/privacy.js` → replaced by derived store logic.
+  - `utils/trackingCookies.js` → merged into the store with SSR-safe cookie APIs.
+
+### Reactive State
+
+| Store                   | Type                      | Description                                                             |
+| ----------------------- | ------------------------- | ----------------------------------------------------------------------- |
+| `trackingPreferences`   | `Readable<TrackingState>` | Contains current tracking metadata (opt-in/out, DNT, GPC, status, etc). |
+| `trackingEnabled`       | `Writable<boolean>`       | Exposed to toggle or query PostHog tracking state reactively.           |
+| `remindUserToReconsent` | `Readable<boolean>`       | Indicates whether a consent renewal prompt should be shown.             |
+| `showReminder`          | `Writable<boolean>`       | Used by PostHog to conditionally display a reminder or banner.          |
+
+### ⏳ Reconsent Logic
+
+The derived store `remindUserToReconsent` evaluates whether a user should be reminded to re-consent to tracking.
+
+It checks for:
+
+- Manual opt-in or opt-out
+- A valid `tracking_consent_timestamp` cookie
+- Whether 6+ months have elapsed since that timestamp
+
+### ⚙️ Developer Notes
+
+- Changes to tracking preferences update cookies and reactive state
+- Reconsent timestamp is written/cleared via store utility functions
+- Use `$trackingPreferences` and `remindUserToReconsent` wherever reactive values are needed
+
+### 💡 Related Components
+
+| File                            | Purpose                                                                          |
+| ------------------------------- | -------------------------------------------------------------------------------- |
+| `+layout.svelte`                | Initializes PostHog client and service worker; references `trackingPreferences`. |
+| `PrivacyDashboard.svelte`       | UI control panel for opt-in/out toggles and consent status display.              |
+| `PrivacyContent.svelte`         | Informational content rendered in modals, footers, and standalone pages.         |
+| `stores/trackingPreferences.js` | Primary source of truth; tracks and derives tracking state.                      |
+| `stores/posthog.js`             | Encapsulates privacy-safe analytics setup and event capture logic.               |

package/svelte.config.js

@@ -23,7 +23,7 @@ const config = {
   kit: {
     // Netlify adapter configuration
     adapter: adapter({
-      edge: false, // Disable edge functions for site
+      edge: false, // Disable edge functions (optional, enable if needed)
       split: false, // Disable splitting function files (optional, enable if needed)
     }),
 

package/CODE_OF_CONDUCT.md

@@ -1,173 +0,0 @@
-<!-- =========================================================================
-CODE_OF_CONDUCT.md
-
-Copyright © 2025 Network Pro Strategies (Network Pro™)
-SPDX-License-Identifier: CC-BY-4.0 OR GPL-3.0-or-later
-This file is part of Network Pro.
-========================================================================== -->
-
-<a name="top"></a>
-
-<sup>[SPDX-License-Identifier](https://spdx.dev/learn/handling-license-info):
-`CC-BY-4.0 OR GPL-3.0-or-later`</sup>
-
-# Contributor Covenant Code of Conduct
-
-**Network Pro Strategies**  
-**Effective Date:** 3/21/2025
-
-&nbsp;
-
-## Contents
-
-- [Our Pledge](#pledge)
-- [Our Standards](#standards)
-- [Responsibilities](#response)
-- [Scope](#scope)
-- [Enforcement](#enforce)
-- [Attribution](#attribute)
-
----
-
-<section id="pledge">
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-</section>
-
-<section id="standards">
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-- Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the overall
-  community
-
-Examples of unacceptable behavior include:
-
-- The use of sexualized language or imagery, and sexual attention or advances of
-  any kind
-- Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-<sub>[Back to top](#top)</sub>
-
-</section>
-
-<section id="response">
-
-## Responsibilities
-
-Company and community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Company and community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-Network Pro Strategies reserves the right, at its sole discretion, to remove, edit, or reject any contributions that are contrary to or detrimental to its business interests.
-
-<sub>[Back to top](#top)</sub>
-
-</section>
-
-<section id="scope">
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the company or community in public spaces.
-Examples of representing our company or community include using an official email address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-<sub>[Back to top](#top)</sub>
-
-</section>
-
-<section id="enforce">
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the abuse team at [abuse@neteng.pro](mailto:abuse@neteng.pro). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances.
-
-The abuse team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.
-
-<sub>[Back to top](#top)</sub>
-
-</section>
-
-<section id="attribute">
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-The **Enforcement** section is adapted from the
-[Contributor Covenant][homepage],
-version 1.4, available at
-[https://www.contributor-covenant.org/version/1/4/code-of-conduct/][v1.4].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
-[https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[v1.4]: https://www.contributor-covenant.org/version/1/4/code-of-conduct/
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations
-
-<sub>[Back to top](#top)</sub>
-
-</section>
-
----
-
-<span style="font-size: 12px; font-weight: bold; text-align: center;">
-
-[Home](https://netwk.pro) &nbsp; | &nbsp; [Terms of Use](https://netwk.pro/terms-of-use)  
-[Privacy Policy](https://netwk.pro/privacy) &nbsp; | &nbsp; [Legal](https://netwk.pro/license)
-
-</span>
-
-&nbsp;
-
-<span style="font-size: 12px; text-align: center;">
-
-Copyright &copy; 2025  
-**[Network Pro Strategies](https://netwk.pro/)** (Network Pro&trade;)
-
-Network Pro&trade;, the shield logo, and the "Locking Down Networks&trade;" slogan are [trademarks](https://netwk.pro/license#trademark) of Network Pro Strategies.
-
-Licensed under **[CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)** and the **[GNU GPL](https://spdx.org/licenses/GPL-3.0-or-later.html)**, as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
-
-</span>

package/src/lib/stores/trackingStatus.js

@@ -1,30 +0,0 @@
-/* ==========================================================================
-src/lib/stores/trackingStatus.js
-
-Copyright © 2025 Network Pro Strategies (Network Pro™)
-SPDX-License-Identifier: CC-BY-4.0 OR GPL-3.0-or-later
-========================================================================== */
-
-/**
- * @file trackingStatus.js
- * @description Tracks state of PostHog tracking status for instant updates
- * in Privacy Policy and Privacy Dashboard.
- * @module src/lib/stores
- */
-
-import { writable } from "svelte/store";
-
-/**
- * Writable tracking status store.
- * Initialized with fallback value and updated in browser context.
- * @type {import("svelte/store").Writable<string>}
- */
-export const trackingStatus = writable("⏳ Checking tracking preferences...");
-
-// Dynamically import browser-only logic after mount
-if (typeof window !== "undefined") {
-  import("$lib/utils/trackingStatus.js").then(({ getTrackingPreferences }) => {
-    const prefs = getTrackingPreferences();
-    trackingStatus.set(prefs.status);
-  });
-}

package/src/lib/utils/privacy.js

@@ -1,81 +0,0 @@
-/* ==========================================================================
-src/lib/utils/privacy.js
-
-Copyright © 2025 Network Pro Strategies (Network Pro™)
-SPDX-License-Identifier: CC-BY-4.0 OR GPL-3.0-or-later
-This file is part of Network Pro.
-========================================================================== */
-
-/**
- * @file privacy.js
- * @description Determines whether the user allows tracking based on DNT, GPC, or manual opt-out.
- * @module src/lib/utils/
- * @author SunDevil311
- * @updated 2025-06-03
- */
-
-/**
- * Check if user has manually set tracking preference.
- * @returns {boolean}
- */
-export function hasUserManuallySetTrackingPreference() {
-  if (typeof document === "undefined") return false;
-
-  const cookies = document.cookie;
-  return (
-    cookies.includes("enable_tracking=true") ||
-    cookies.includes("disable_tracking=true")
-  );
-}
-
-/**
- * Determine if the user allows tracking based on cookies, DNT, and GPC.
- * @returns {boolean}
- */
-export function shouldTrackUser() {
-  if (
-    typeof window === "undefined" ||
-    typeof navigator === "undefined" ||
-    typeof document === "undefined"
-  ) {
-    return false;
-  }
-
-  const cookies = document.cookie;
-  const windowDNT = /** @type {any} */ (window).doNotTrack;
-  const navigatorGPC = /** @type {any} */ (navigator).globalPrivacyControl;
-
-  const dnt = navigator.doNotTrack === "1" || windowDNT === "1";
-  const gpc = navigatorGPC === true;
-
-  const manualOptOut = cookies.includes("disable_tracking=true");
-  const manualOptIn = cookies.includes("enable_tracking=true");
-
-  console.log("[Privacy] Opt-in cookie present:", manualOptIn);
-  console.log("[Privacy] Opt-out cookie present:", manualOptOut);
-
-  if (manualOptIn) return true;
-  if (manualOptOut) return false;
-
-  return !dnt && !gpc;
-}
-
-/**
- * Determines if user should be reminded to reconsent (after 6 months).
- * @returns {boolean}
- */
-export function shouldRemindUserToReconsent() {
-  if (typeof document === "undefined") return false;
-
-  if (!hasUserManuallySetTrackingPreference()) return false;
-
-  const match = document.cookie.match(/tracking_consent_timestamp=(\d+)/);
-  if (!match) return true;
-
-  const timestamp = Number(match[1]);
-  if (isNaN(timestamp)) return true;
-
-  const age = Date.now() - timestamp;
-
-  return age > 1000 * 60 * 60 * 24 * 180; // 6 months
-}