How We Protect Your Data

Infrastructure

• ✓Cloudflare Workers. Our application runs on Cloudflare's global edge network with built-in DDoS protection, WAF, and automatic TLS.
• ✓Neon PostgreSQL. Managed database with automated backups, point-in-time recovery, and encryption at rest.
• ✓Cloudflare R2. Object storage for HTML snapshots with server-side encryption.

Encryption

• ✓In transit. All connections use TLS 1.3. HTTP is automatically upgraded to HTTPS.
• ✓At rest. All stored data is encrypted with AES-256.
• ✓Credentials. CMS connector credentials are encrypted with AES-256-GCM before storage. HMAC-SHA256 is used separately to sign connector messages, not to encrypt credentials.

Authentication & Access

• ✓JWT authentication. Secure token-based auth with short-lived access tokens and refresh token rotation.
• ✓Role-based access control. Four roles (Owner, Admin, Editor, Viewer) with permission boundaries enforced at the API level.
• ✓Multi-tenant isolation. Site-data access is checked against the authenticated tenant. Authorization checks and tenant-scoped queries are used to prevent cross-tenant access.
• ✓Password security. Passwords are hashed with bcrypt. We never store or log plaintext passwords.

Budget Controls

SearchForge includes built-in budget guardrails to prevent runaway AI costs. You set monthly limits, and the system automatically pauses or downgrades operations at 80%, 95%, and 100% thresholds. Alerts are sent via webhook at each threshold.

Reporting

If you discover a security vulnerability, please report it to security@searchforgeai.com. We take all reports seriously and will respond within one business day.