Security Overview & Practices

1. Executive Summary

At ServeScan, the security, integrity, and availability of your restaurant data and digital menus are core architectural priorities. Our infrastructure is built using modern serverless edge architecture, rigorous cryptographic standards, and strict multi-tenant isolation to ensure maximum reliability and defense-in-depth against unauthorized access, data loss, and cyber threats.

2. Authentication, Single Sign-On & Cryptography

• Password Hashing: Passwords for direct accounts are hashed using PBKDF2 (Password-Based Key Derivation Function 2) with a SHA-256 HMAC hash, executed over 100,000 computation iterations, combined with a unique, cryptographically secure 16-byte salt per user generated via crypto.getRandomValues. Passwords are never stored in plaintext or accessible to staff.
• Google OAuth 2.0 / OpenID Connect: For users authenticating with Google, authentication is completed via secure OAuth 2.0 handshake protocols. ServeScan verifies signed identity tokens directly against Google's public JWKS endpoints, exchanging them for internal session tokens without ever receiving or handling your Google account password.
• Strict Password Hardening: Registration requires a minimum 8-character password enforcing lowercase letters, uppercase letters, numerical digits, and special characters.
• Stateless Token Security (JWT): Authenticated administrative sessions utilize signed JSON Web Tokens (HS256) with short-lived expiration windows (7 days). Session tokens are transmitted exclusively inside HTTP-only, Secure, SameSite=Strict/Lax cookies, effectively neutralizing Cross-Site Scripting (XSS) token exfiltration and Cross-Site Request Forgery (CSRF) exploits.

3. Multi-Tenant Architecture & Data Segmentation

• Database Scoping (Cloudflare D1): ServeScan operates on a relational serverless SQLite architecture via Cloudflare D1. Every database query, mutation, and read operation is strictly scoped to the authenticated tenant's UUID (tenantId).
• Object Storage Isolation (Cloudflare R2): Uploaded restaurant media assets are stored in isolated prefix hierarchies (${tenantId}/${mediaKey}.webp). Direct cross-tenant access to unauthorized media keys is blocked.
• Role-Based Access Control (RBAC): Built-in middleware verifies user roles (owner, staff, superadmin) prior to granting access to sensitive menu configuration, billing management, and administrative endpoints.

4. Infrastructure, Network & Edge Defense

• Serverless Edge Compute (Cloudflare Workers): ServeScan backend APIs and server-side rendering (SSR) frontends run inside lightweight, sandboxed V8 isolates distributed across Cloudflare's global edge network. This eliminates traditional virtual machine (VM) operating system vulnerabilities, unpatched system libraries, and server-side daemon exploits.
• DDoS Mitigation & Rate Limiting: Global Anycast DNS and automated Cloudflare Layer 3, 4, and 7 DDoS protection shield the platform against traffic floods and malicious denial-of-service attempts.
• End-to-End TLS Encryption: All network communication between diners, administrators, APIs, and storage endpoints is encrypted using modern TLS 1.3 / TLS 1.2 protocols.
• Edge Caching & High Availability: Public digital menus leverage the Cloudflare Cache API (caches.default) to deliver sub-second menu loading times globally while insulating the primary database from sudden high-volume restaurant traffic spikes.

5. Media & File Upload Hardening

• Strict Whitelist Validation: File uploads are strictly validated at both the client and server edge layers against accepted MIME types (image/jpeg, image/png, image/webp). Executable files, scripts, PDFs, and unauthorized binaries are rejected.
• Upload Size Restrictions: Hard quota enforcement restricts individual image uploads to a maximum of 5 MB, with total storage caps governed by account subscription tiers (25 MB Starter, 250 MB Pro).
• Client-Side Optimization: Images are cropped and converted to web-optimized WebP formats, stripping unsafe EXIF metadata prior to permanent storage in Cloudflare R2.

6. Payment Processing Compliance

ServeScan does not process, store, or transmit raw payment card details on its servers. All payment transactions are offloaded to certified third-party providers:

7. Vulnerability Disclosure & Bug Reporting

We value the contributions of the security research community. If you discover a potential vulnerability or security flaw within ServeScan, please disclose it to us responsibly: