Security
Last updated: October 29, 2026
Our Security Philosophy
FounderPaths is built on a simple principle: the less we store, the less there is to protect. We run a static, content-focused site with no user accounts, no password database, no payment processing, and no sensitive personal data. This architecture dramatically reduces the attack surface compared to dynamic, database-driven applications.
Architecture and Infrastructure
- Static site generation: All pages are pre-rendered HTML served directly by nginx. No PHP, Python, Node.js, or database executes on page load. This eliminates entire classes of injection, deserialization, and ORM vulnerabilities.
- No user accounts or authentication: Visitors cannot create accounts, log in, or store profiles. No passwords, password hashes, session tokens, or OAuth credentials exist on our systems.
- No payment processing: We do not accept payments, store credit cards, or integrate payment gateways. Affiliate commissions are tracked by third-party networks on their infrastructure.
- Minimal data collection: We collect only what is strictly necessary (see Privacy Policy). No analytics identifiers are linked to personal identities.
Network and Transport Security
- HTTPS everywhere: TLS 1.2/1.3 enforced via Let's Encrypt certificates. HSTS header with
max-age=31536000; includeSubDomains; preload. - Certificate transparency: Certificates logged to public CT logs. We monitor for mis-issuance.
- Secure headers (all responses):
X-Frame-Options: SAMEORIGIN- prevents clickjacking.X-Content-Type-Options: nosniff- blocks MIME sniffing.Referrer-Policy: strict-origin-when-cross-origin- limits referrer leakage.Permissions-Policy- restricts browser features (camera, microphone, geolocation, payment) to none.Content-Security-Policy- restrictive policy allowing only self and essential third-party origins (Google Fonts, AdSense, Analytics).
Application Hardening
- Rate limiting: Login endpoints (where applicable) limited to 5 requests/minute per IP. API endpoints similarly protected.
- Request filtering: Blocks access to dotfiles,
xmlrpc.php,wp-login.php(WordPress scanner noise), and other common probe paths. - No server-side scripting on content paths:
.html,.css,.js, and media files are served statically with no interpreter invocation. - Subresource integrity: Critical third-party scripts (where we control the HTML) include SRI hashes.
Data Protection
- Newsletter emails: Stored with our email service provider (not on this server). Unsubscribe is one-click. We do not enrich, profile, or share subscriber lists.
- Contact form submissions: Forwarded to email; not stored in a database on this host.
- Analytics: Google Analytics 4 with IP anonymization. No User-ID feature. Data retention set to 14 months.
- Advertising: Google AdSense operates under its own privacy and security controls. We do not pass personal data to ad partners.
Operational Practices
- Automated updates: OS security patches applied within 24 hours of release. Nginx, PHP-FPM (for isolated endpoints), and Certbot kept current.
- Least privilege: Web server runs as unprivileged
www-data. Application files owned byubuntu, writable only by owner. No world-writable directories. - Logging and monitoring: Access and error logs rotated daily. Failed login attempts, 4xx/5xx spikes, and probe patterns trigger alerts.
- Backups: Daily off-site snapshots of content and configuration. Recovery tested quarterly.
Third-Party Services
We rely on a small set of reputable providers. Their security practices are their own; we evaluate them before integration and monitor for incidents.
- Cloudflare (DNS only, no proxy) - domain resolution.
- Let's Encrypt - TLS certificates.
- Google (Analytics, AdSense, Fonts) - measurement, monetization, typography.
- Email service provider - newsletter delivery.
Vulnerability Disclosure
We take security reports seriously. If you discover a vulnerability, please report it responsibly:
- Email: (preferred).
- Contact form: /contact/.
Include:
- Description of the issue and impact.
- Steps to reproduce or proof-of-concept (non-destructive only).
- Affected URL(s) or component(s).
- Your contact information for coordination.
We commit to:
- Acknowledging receipt within 2 business days.
- Providing a preliminary assessment within 7 business days.
- Remediating critical/high-severity issues within 30 days where feasible.
- Coordinating public disclosure after a fix is deployed (or 90 days, whichever comes first).
We do not offer a bug bounty program, but we will credit reporters (with permission) in our security acknowledgments.
Scope
This statement covers founderpaths.com and its subdirectories. It does not cover third-party sites linked from our content, advertiser landing pages, or external platforms where we maintain profiles (social media, etc.).
Changes
This security overview is updated when material changes occur. The "Last updated" date reflects the most recent revision.
Contact
Security questions: Contact form or email.
