ContentBeamer writes to your CMS and posts to your accounts. That requires real secrets, so the handling of those secrets is documented rather than implied.
Last updated: June 28, 2026
Every API key, OAuth token and CMS credential is encrypted with AES-256-GCM under a per-tenant key. Ciphertext never appears in logs or error traces.
Organizations are the hard boundary. Every query is scoped by org id at the data layer, not the route layer, and the active org is always visible in the UI.
Strict CSP, per-org rate limits, SSRF protection on every outbound fetch (webhooks and custom image providers included), signed webhook payloads.
Only the last four characters are ever rendered. Reveal requires a held press and is not copyable in one tap.
Deleting a site, disconnecting a platform, or clearing a keyword set all require a typed confirmation. Published content on your CMS is never deleted by us.
Security is foundational to ContentBeamer. Because the Service stores credentials for the platforms you publish to, we treat the protection of that data as a first-order concern. This page summarizes how we protect your information. It is provided for transparency and is not a contract; your rights are governed by our Terms of Service and Privacy Policy.
All sensitive credentials — including CMS configurations, social platform OAuth tokens (access and refresh), and any AI provider API keys you supply — are encrypted at rest usingAES-256-GCM, with a unique, randomly generated initialization vector per credential. Decryption keys are stored separately from the database. Credentials are never returned in API responses and are decrypted only in memory, at the moment they are needed to perform an action you requested.
ContentBeamer is multi-tenant. Every data query is scoped to the owning account, so one customer's data is never exposed to another. Access to your content, sites, and connected accounts is restricted to your authenticated account.
All traffic to and from the Service is encrypted using industry-standard TLS.
Authentication is handled by Clerk, which provides secure session management and supports organization-level access controls.
We build on established, security-conscious infrastructure providers, including Vercel (hosting), Neon (database), Cloudflare R2 (storage), and Upstash (caching and queues). Payment processing is handled by Stripe; we do not store full payment card numbers.
The Service includes rate limiting to mitigate abuse, protections against server-side request forgery (SSRF) by validating outbound URLs, Content Security Policy reporting, and signature verification on automated job endpoints.
If you believe you have found a security vulnerability in ContentBeamer, we want to hear from you. Please email security@contentbeamer.com with details, and allow us a reasonable period to investigate and remediate before any public disclosure. We appreciate responsible reports and will acknowledge your contribution.
For any other security or privacy concern, contact support@contentbeamer.com.