RecBeam
Your content stays under your control
A straightforward look at how RecBeam handles authentication, storage, and billing.
Google Sign-In
Authentication happens through Google. RecBeam never receives or stores your Google password.
Hashed session tokens
Your RecBeam session token is stored server-side only as a cryptographic hash, never in plain text.
Authenticated API access
Every library, upload and billing route requires a valid, verified RecBeam session.
Owner-scoped operations
Renaming, archiving, downloading or deleting a video or screenshot is only possible for the account that owns it.
Cloudflare infrastructure
RecBeam runs on Cloudflare Workers, with Cloudflare D1 for metadata and Cloudflare R2 for video and image storage.
Verified webhook signatures
Subscription changes from Lemon Squeezy are only accepted after verifying an HMAC signature over the exact request body.
Server-enforced plan limits
Recording length and video-count limits are enforced on RecBeam's server, not just in the extension's interface.
Temporary local recovery
A recording is kept locally only until its cloud upload is verified, or if that verification fails.
Permanent deletion
Deleting a video or screenshot removes the underlying file and breaks its public link immediately.
Share-link awareness
Share links are unlisted. Anyone with a public link can open it. Business owners can add a password, restrict access, or allow-list emails.
Billing through Lemon Squeezy
Subscription payments are processed by Lemon Squeezy, our Merchant of Record.
No direct card storage
RecBeam does not directly receive or store your complete payment-card details.