Privacy

Image representing security and privacy protection for the Privacy page

Summary

This documentation site is a static archive of technical pages. We collect no personal data, use no cookies, and run no analytics. If you share logs, screenshots, or configuration details in public forums or with support channels, treat them as permanently public unless you are using encrypted private communication.

Data collection statement

This site is a static documentation archive with the following characteristics:

  • No server-side tracking: No logs of visitor activity, page views, or user behavior.
  • No cookies: Site does not set or read cookies of any kind.
  • No analytics services: No Google Analytics, Matomo, or similar tracking platforms.
  • No user accounts: No login system, no registration, no stored credentials.
  • No forms or data submission: Site is read-only reference documentation.
  • No email capture: No newsletter signups or email collection.

What this means: Your browsing of this documentation is private. We have no technical means to identify you, track your activity, or collect personal information through this site.

Information you share voluntarily

While the site itself collects no data, you may choose to share information through external channels:

Public forums and community platforms

If you post logs, screenshots, or configuration details to forums, GitHub issues, or community discussions:

  • Treat all posted content as permanently public and searchable.
  • Forum/platform privacy policies apply (not this site's policy).
  • Content may be indexed by search engines and archived by third parties.
  • Deletion requests depend on platform policies and may not be fully honored.

Email contact (if applicable)

If you use a Contact page or email address provided on this site:

  • Email communication is unencrypted unless you use PGP/GPG.
  • We recommend encrypted communication for sensitive vulnerability reports.
  • Emails are not logged or stored beyond the response period.
  • No mailing lists or subscriber databases are maintained.

What to redact when sharing publicly

Before posting logs, configuration files, or screenshots to public channels, redact:

Credentials and secrets

  • Passwords: Any plaintext or hashed passwords in configuration files.
  • WiFi PSKs: Pre-shared keys in wpa_supplicant.conf or similar.
  • SSH keys: Public and especially private key material.
  • API keys and tokens: Authentication tokens for services.
  • Certificates: Private keys in SSL/TLS certificates.

Personal identifiers

  • MAC addresses: If you consider your device MAC address sensitive.
  • Hostnames: If they contain personal names or identifying information.
  • IP addresses: Public or private IPs if you consider them sensitive.
  • Serial numbers: Device serial numbers if they enable tracking.
  • Email addresses: In log files, error messages, or git commits.
  • Filesystem paths: Paths containing real names (/home/johnsmith/).

Safe sharing practices

  1. Sanitize logs before posting: 
    # Example: redact passwords with sed
cat myconfig.conf | sed 's/password=.*/password=***REDACTED***/' > safe-config.txt

# Remove specific lines containing secrets
grep -v "SECRET_KEY" logfile.txt > safe-log.txt

# Replace MAC addresses
sed 's/\([0-9A-Fa-f]\{2\}:\)\{5\}[0-9A-Fa-f]\{2\}/XX:XX:XX:XX:XX:XX/g' dmesg.log
  2. Use consistent placeholders: Replace secrets with ***REDACTED*** or [REMOVED] to show you've intentionally removed content.
  3. Review twice before posting: Read through sanitized content carefully. Search for your name, email, hostname.
  4. Minimize shared content: Only include relevant log sections, not entire system dumps.
  5. Use private channels for sensitive issues: Security vulnerabilities should be reported via encrypted email, not public forums.
  6. Test credentials are invalid: If you accidentally post a password, change it immediately on all systems where it was used.

This documentation links to external resources including:

  • Official upstream documentation (kernel.org, debian.org, ubuntu.com)
  • Manufacturer datasheets and specifications
  • Community resources (forums, wikis, GitHub repositories)

Disclaimer: We have no control over the content, availability, or privacy policies of linked external sites. Each external site has its own privacy policy which you are responsible for reviewing.

Link maintenance: Broken or incorrect links can be reported via the Contact page.

GDPR and user rights

For users in the European Union:

  • Right to be forgotten: Since this site collects no data, there is no data to delete. If you've posted to external forums, contact those platforms directly.
  • Data portability: Not applicable'no data is collected or stored.
  • Consent: No tracking means no consent popups or cookie banners required.
  • International access: Documentation is accessible worldwide with the same privacy guarantees.

Security recommendations

To protect your privacy when using this documentation:

  • Verify HTTPS: Ensure your browser shows https:// in the URL bar and valid SSL certificate.
  • Download integrity: Always verify SHA256 checksums of downloaded images before flashing to prevent man-in-the-middle attacks.
  • Report vulnerabilities responsibly: If you discover a security issue in the documentation or linked resources, use the Contact page or encrypted email to report privately.
  • Monitor upstream security advisories: Keep your systems updated with security patches from your Linux distribution.
  • Use trusted networks: Download images and access documentation over trusted networks, not public WiFi without VPN.

Hosting provider considerations

While this site collects no data, the hosting provider may log:

  • IP addresses for abuse prevention and load balancing
  • Access timestamps and requested URLs for operational monitoring
  • HTTP headers (user agent, referrer) in server logs

These logs are controlled by the hosting provider's privacy policy, not this site's policy. Logs are typically retained for short operational periods (days to weeks) and not shared with site administrators.

Changes to this policy

  • Date tracking: This policy is dated (see "Last updated" below). Changes are tracked in version control.
  • Notification: Major changes will be announced on the main documentation page.
  • User responsibility: Check this page periodically if you have privacy concerns.
  • Archive access: Previous versions available via git history if you need to review historical policies.

FAQ

Does this site use cookies?
No. This is a static site with no cookies of any kind. You can verify in your browser's developer tools (Application ? Cookies).
Is my IP address logged?
Not by this site. The hosting provider may log IPs for operational purposes (check their privacy policy). Site administrators have no access to visitor IP logs.
Can I request deletion of my data?
Not applicable'this site collects and stores no personal data. If you've posted to external forums, contact those platforms directly for deletion requests.
Does the site use Google Analytics or similar?
No. No analytics services of any kind are used. Your browsing is not tracked or analyzed.
How do I report a privacy concern?
Use the Contact page to describe your concern. Include specific details and URLs if applicable.
Is there a PGP key for encrypted reports?
For sensitive security or privacy reports, encrypted email is recommended. Check the Contact page for current PGP key information if available.
How long is data retained?
Not applicable'no user data is collected or retained by this site. Documentation content is versioned and retained indefinitely for reference purposes.

Contact for privacy questions

For questions about this privacy policy or concerns about data handling:

  • Use the Contact page
  • For security-sensitive issues, use encrypted email (PGP key on Contact page if available)
  • Allow 5-7 business days for response to privacy inquiries

Author: LeMaker Documentation Team
Last updated: 2026-01-12