Security Architecture & Controls

Last updated 6 October 2026

Reigel AI SEO provides technical SEO, crawl diagnostics, and search intelligence. Because our platform interacts with client websites, Google APIs, and third-party AI systems, we implement defense-in-depth security engineering across all layers of our application.

Secure Transport & Headers

All web and API traffic is encrypted in transit using Transport Layer Security (TLS 1.2+). Production endpoints enforce HTTP Strict Transport Security (HSTS), X-Content-Type-Options: nosniff, X-Frame-Options: DENY, and restrictive permissions policies.

Authentication & Session Management

User passwords are encrypted with salted bcrypt hashes. Browser authentication sessions use hardened, HttpOnly cookies flagged with Secure and appropriate SameSite protections, ensuring tokens are inaccessible to JavaScript context.

Mutating requests enforce Double-Submit Cookie CSRF defenses and verify origin authenticity. Refresh tokens rotate upon consumption, and token reuse triggers automatic revocation of active refresh sessions.

Multi-Tenant Isolation

Data is strictly segregated by organization and project. All API operations authenticate principals server-side and verify organization membership. Database queries enforce tenant boundaries, ensuring users cannot access or tamper with data belonging to other workspaces.

Integration Credential Encryption

OAuth access and refresh tokens for third-party services (such as Google Search Console, Google Analytics 4, and Google Business Profile) are encrypted at rest using AES-256-GCM. Encryption uses unique nonces and cryptographic authentication tags. Plaintext integration tokens are never logged or exposed to the client.

Crawler SSRF & Network Defense

Our automated website crawler is fortified against Server-Side Request Forgery (SSRF) and DNS rebinding:

  • Refusal of private, local, loopback, and carrier-grade IPv4/IPv6 address blocks (including 127.0.0.1, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, ::1, and unique local addresses).
  • Refusal of cloud metadata addresses (including 169.254.169.254).
  • Real-time DNS socket resolution validation before connection and on every redirect hop.
  • Strict protocol restriction accepting only http: and https:.

Rate Limiting & Crawler Politeness

API surfaces are protected by rate limiters to guard against abuse and credential attacks. The crawler honors site robots.txt directives, enforces concurrency bounds, and spaces requests politely.

Repository & Code Fix Safety

Any future code fix proposals operate on a strict human-in-the-loop model: code fixes generate pull requests for human review on GitHub. Fixes are never automatically merged or pushed directly to production branches. Repository contents are treated strictly as untrusted data.

Vulnerability Disclosure & Reporting

We welcome responsible disclosure of security vulnerabilities. If you believe you have discovered a security issue, please contact:

TODO: BUSINESS OWNER INPUT REQUIRED (e.g., [email protected])

Please include steps to reproduce, affected endpoints, and allow reasonable time for remediation before public disclosure.