Security at JoyPDF

JoyPDF's security model is fundamentally different from traditional cloud-based PDF tools. Instead of uploading your files to a remote server for processing, all operations run locally in your browser using WebAssembly (WASM) and JavaScript.

This means your sensitive documents - contracts, financial reports, medical records, legal filings - never traverse the internet. They remain on your device from start to finish. There is no server-side storage, no temporary cloud caching, and no possibility of server-side data breaches affecting your files.

This architecture eliminates entire categories of security risks:

• No data-in-transit risk for your files - they never leave the browser sandbox

• No server-side storage means zero risk of cloud-based data leaks

• No third-party access to your document contents

• No residual data - once you close the tab, processing data is released from memory

All traffic to and from joypdf.app is encrypted using TLS 1.3 with strong cipher suites. We enforce HTTPS across all endpoints and implement HTTP Strict Transport Security (HSTS) to prevent downgrade attacks.

Our DNS records are protected with DNSSEC, and we utilize Content Security Policies (CSP) to mitigate cross-site scripting (XSS) and code injection attacks.

Security headers we implement include:

• `Strict-Transport-Security` - enforces HTTPS

• `X-Content-Type-Options: nosniff` - prevents MIME type sniffing

• `X-Frame-Options: DENY` - prevents clickjacking

• `Referrer-Policy: strict-origin-when-cross-origin` - limits referrer leakage

• `Content-Security-Policy` - restricts resource loading

When you explicitly choose to use AI-powered features (AI Summary, AI Translate, AI Agent), only the extracted text content is sent to our AI processing partner via our secure API - never the original PDF file, images, or metadata.

The data flow for AI features is:

1. Text is extracted from the PDF locally in your browser

2. Extracted text is sent via encrypted HTTPS to our API endpoint

3. Our API forwards the request to the AI model provider

4. The AI response is streamed back and rendered in your browser

5. No text or response is stored on our servers after the request completes

We explicitly prohibit our AI providers from using your data for model training. This is contractually enforced.

User authentication is handled by Clerk, an enterprise-grade identity platform. Clerk provides:

• Secure password hashing with bcrypt

• Multi-factor authentication (MFA) support

• OAuth 2.0 / OpenID Connect social login

• Session management with secure, HttpOnly cookies

• Brute-force and bot protection

• SOC 2 Type II certified infrastructure

JoyPDF is designed to comply with:

• GDPR - EU General Data Protection Regulation

• CCPA - California Consumer Privacy Act

• ePrivacy Directive - EU electronic communications privacy

• LGPD - Brazil's General Data Protection Law

• PIPEDA - Canada's Personal Information Protection and Electronic Documents Act

Our zero-upload architecture inherently simplifies compliance because document data never reaches our infrastructure.

We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly to security@joypdf.app. We commit to:

• Acknowledging your report within 48 hours

• Providing regular updates on remediation progress

• Not pursuing legal action against good-faith security researchers

• Crediting researchers (with their permission) for discovered vulnerabilities