SocialCampus

Trust

Security

Your clients trust you with their brand accounts. Here is how SocialCampus keeps that trust, request by request.

Last updated

1. Every client is walled off

  • Each request is checked against the database for who you are, which clients you can open, and what your role allows.
  • A client ID sent by the browser or the AI is ignored. The server decides.
  • “No access” and “does not exist” look the same, so nothing leaks about other clients.
  • Automated tests check that one client can never see another client’s data.

2. Sign-in and sessions

  • Passwords are hashed with Argon2id.
  • Session cookies are httpOnly, Secure and SameSite=Lax. We store only a SHA-256 hash of the session token.
  • Sign-in attempts are rate-limited, and repeated failures lock sign-in for 15 minutes.
  • Every change request must carry a custom header, which other websites cannot send.

3. Connected accounts

  • Clients connect accounts through each platform’s own sign-in, using Composio. No password ever changes hands.
  • Login tokens are held by Composio, never in our database.
  • Each client has its own private Composio identity, never shown in the browser or to the AI.
  • Connection links work once and expire after 15 minutes.

4. AI guardrails

  • The AI only gets tools that are allowed for that client and that client’s connected accounts.
  • Account IDs are stripped from what the AI sends and receives.
  • Actions that post, send or spend wait in the Approval Center with the exact details. An approval runs once, and only once.
  • Every AI tool call and every decision is written to an activity log.

5. Secrets

AI provider keys stay in server settings and are never stored in the database or sent to the browser. Secrets saved in the app, like the SMTP password, are encrypted with AES-256-GCM.

6. Infrastructure

  • Runs in Docker on a dedicated server, with only the web and API reachable, behind HTTPS.
  • A database and file backup runs every night and is kept for 14 days.
  • Restores are tested: our last drill restored a full backup and matched every table.

7. Report a vulnerability

Found a security issue? Email [email protected] with the steps to reproduce it. We reply within 2 working days and will not take action against good-faith research.