← SocialSpider

Security

Security at SocialSpider AI

Last reviewed November 2026

Security is foundational to everything we build. This page describes how your brand data, social connections and content are protected.

At a glance:

  • HTTPS (TLS) — encryption in transit for every page and API
  • AES-256-GCM — encryption of stored social account tokens and API keys
  • bcrypt — passwords are stored only as one-way hashes
  • No social media passwords — accounts connect through each platform's own sign-in (OAuth)

Data encryption

All data between your browser and SocialSpider is encrypted in transit with HTTPS. The access tokens for your connected social accounts, and any API keys stored in the platform, are encrypted with AES-256-GCM under a dedicated key that can be rotated. Card details never reach our servers: payments are handled entirely by Stripe.

Authentication

You can sign in with email and password, or with Google, LinkedIn or X. Passwords are stored only as bcrypt hashes and must pass a strength check. Sign-in attempts are rate-limited, password-reset links expire after 30 minutes and work once, and changing your password signs out every other session. We connect social media accounts through each platform's own OAuth sign-in, so we never see or store your social media passwords.

Infrastructure

SocialSpider AI runs on a dedicated cloud server behind Cloudflare, which provides DNS, caching and protection at the network edge. Uploaded and generated files are stored in Cloudflare R2. Production access is limited to the SocialSpider team, and every administrative action on a customer account inside the platform is recorded in a permanent audit log.

Vulnerability disclosure

If you discover a security vulnerability, please report it to [email protected]. We acknowledge reports within 24 hours and fix them in order of severity, critical issues first.

Security testing

Every code change is checked automatically with type checks, code-quality checks, unit tests and a dependency security audit, and the codebase is reviewed for security issues as part of our release process.

Incident response

We maintain a documented incident response plan. If a security incident affects your account or data, we will tell you within 72 hours of confirming it.

Contact

Security questions or reports: [email protected]

Terms of ServicePrivacy PolicyCookie PolicyData deletion