PDF Content Extractor & Translator is designed with data sovereignty as a core principle:

┌─────────────────────────────────────────────────────────────┐
│                     YOUR MACHINE                            │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────┐ │
│  │ PDF Files   │→ │ Application │→ │ Processed Output    │ │
│  └─────────────┘  └─────────────┘  └─────────────────────┘ │
│                          ↓                                  │
│                   ┌─────────────┐                          │
│                   │ Local AI    │                          │
│                   │ (Ollama)    │                          │
│                   └─────────────┘                          │
└─────────────────────────────────────────────────────────────┘
                          ║
                          ╳ NO EXTERNAL CONNECTIONS
                          ║
┌─────────────────────────────────────────────────────────────┐
│                     INTERNET                                │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────┐ │
│  │ Cloud APIs  │  │ Analytics   │  │ Third-party Services│ │
│  └─────────────┘  └─────────────┘  └─────────────────────┘ │
└─────────────────────────────────────────────────────────────┘

Key Guarantees:

• ✅ All PDF processing happens locally
• ✅ No telemetry or analytics collection
• ✅ No data transmitted to external servers
• ✅ No API keys required for any feature
• ✅ Works completely offline after initial setup

We take security seriously. If you discover a vulnerability, please follow responsible disclosure:

For sensitive security issues:

1. Email: security@[project-domain].com (or maintainer email)
2. Subject: [SECURITY] Brief description
3. Include:
   • Description of the vulnerability
   • Steps to reproduce
   • Potential impact
   • Suggested fix (if any)

Response Timeline:

• Acknowledgment: Within 48 hours
• Initial assessment: Within 7 days
• Resolution target: Within 30 days (severity-dependent)

For non-sensitive issues:

1. Open a GitHub Issue
2. Label it with security
3. Provide detailed reproduction steps

# Example: Path validation
ALLOWED_DIRECTORIES = [
    Path.home() / "Documents",
    Path.home() / "Downloads",
    Path.home() / "Desktop",
    Path(__file__).parent.resolve()
]

def validate_path(file_path: str) -> bool:
    resolved = Path(file_path).resolve()
    return any(
        resolved.is_relative_to(allowed) 
        for allowed in ALLOWED_DIRECTORIES
    )

Recommendation: Implement regular cleanup:

# Clear files older than 7 days
find uploads/ outputs/ -type f -mtime +7 -delete

If exposing to a network:

1. Use a Reverse Proxy:

   server {
       listen 443 ssl;
       server_name pdf.example.com;
       
       ssl_certificate /path/to/cert.pem;
       ssl_certificate_key /path/to/key.pem;
       
       location / {
           proxy_pass http://localhost:5000;
           proxy_set_header Host $host;
           proxy_set_header X-Real-IP $remote_addr;
       }
   }

2. Add Authentication:

   • OAuth2 Proxy
   • HTTP Basic Auth
   • Flask-Login

3. Enable Rate Limiting:

   limit_req_zone $binary_remote_addr zone=api:10m rate=10r/s;
   
   location /api/ {
       limit_req zone=api burst=20;
       proxy_pass http://localhost:5000;
   }

4. Restrict File Uploads:

   app.config['MAX_CONTENT_LENGTH'] = 50 * 1024 * 1024  # 50MB

• Data Controller: The user operating the application
• Data Processor: N/A (no third-party processing)
• Data Retention: User-controlled (no automatic deletion)
• Data Export: All files accessible in filesystem

We use the following tools to monitor dependencies:

• Dependabot: Automated vulnerability alerts
• pip-audit: Python package vulnerability scanning
• npm audit: JavaScript dependency scanning

# Python dependencies
pip install pip-audit
pip-audit

# Check for known vulnerabilities
safety check -r requirements.txt

Before submitting a PR, ensure:

• No hardcoded secrets or credentials
• All user input is validated
• File paths use secure_filename()
• No new external network calls introduced
• Error messages don't leak sensitive information
• Logging doesn't include sensitive data
• New dependencies are reviewed for vulnerabilities

We currently do not have a formal bug bounty program. However, we deeply appreciate security researchers who help improve our security posture. Responsible disclosure will be acknowledged in our release notes and contributors list.

• Security Issues: Create private advisory
• General Issues: GitHub Issues

Last updated: 2025-12-20