Privacy Policy

RecBeam is a screen-recording Chrome extension operated by Nexus Eclipse (Pvt) Ltd. (“RecBeam,” “we,” “us,” or “our”).

This Privacy Policy explains what information RecBeam processes, why it is processed, how recordings are stored and shared, and the choices available to users.

1. Overview

RecBeam allows users to record their screen, browser tab, camera, microphone, and supported system or tab audio.

Recordings are initially created and processed in the user’s browser. Users may then upload recordings to their RecBeam account to access them across devices and generate public sharing links.

We do not sell personal information or use recordings for advertising.

2. Information We Process

Google account information

When you sign in using Google, RecBeam receives limited account information required to create and identify your RecBeam account, which may include:

• Your Google account email address
• Your name
• Your profile image, where available
• A unique Google account identifier

RecBeam does not receive or store your Google password. Google access tokens are used temporarily for authentication and are not permanently stored in the RecBeam database.

Recordings and uploaded content

Depending on the options you select, recordings may contain screen or browser-tab content, camera video, microphone audio, system or tab audio, and information visible or audible during the recording. RecBeam processes this content only to create, store, play, and share the recording as requested by you.

Screenshots

When you capture a screenshot, RecBeam processes the captured image, together with any annotations you add in the RecBeam editor. Screenshots you choose to upload are stored in your RecBeam account separately from video recordings. Screenshot capture only ever happens after you explicitly choose “Capture this tab” or “Capture screenshot”. RecBeam does not capture pages in the background.

Recording metadata

We may store metadata associated with uploaded recordings, including recording title, duration, file size, media type, creation and upload timestamps, recording status, public sharing identifier, and account ownership association.

Authentication and session information

RecBeam creates its own session after successful Google authentication. The browser stores the active RecBeam session token locally so you can remain signed in. The RecBeam backend stores only a cryptographic hash of that session token, not the raw token.

Viewers, comments, and cookies

On a share link, depending on the owner’s settings, RecBeam may process comments, reactions, Watch Later saves, RecBeam view counts, an optional self-reported guest email (not verified), a guest display name, and a share-page session cookie (rb_viewer: HttpOnly, Secure, SameSite=Lax, up to 180 days; RecBeam stores a hash of the token). Comment and reaction posts may store the requester IP for rate limiting.

Video intelligence

If you use transcript or overview features, RecBeam sends audio from your recording to Cloudflare Workers AI (Whisper) and transcript text to Cloudflare Workers AI (Llama). RecBeam keeps the original file. RecBeam does not train RecBeam’s own models on your content and does not send Google account data to those models.

Technical and service information

When you use RecBeam’s cloud features, our hosting provider may process normal network and request information such as IP address, browser or user-agent information, request date and time, requested API route, response status, and security and diagnostic information. Cloudflare infrastructure can receive request metadata while processing Worker and storage traffic.

3. How We Use Information

We use information only to authenticate your RecBeam account; record and process media selected by you; upload and store recordings you choose to share; display your uploaded recording library; generate and copy sharing links; stream and play recordings; maintain account sessions; enforce storage, upload, security, and service limits; prevent misuse and investigate technical problems; provide support; and meet legal or regulatory obligations. We do not use recording content to build advertising profiles.

4. Local Recording Storage

Before upload, recordings may be stored in your browser using local browser storage such as IndexedDB. Local recordings are specific to that Chrome profile and device and are not automatically transferred to another computer. Local recordings may be permanently lost if you uninstall the extension, remove the unpacked extension, clear Chrome browsing or site data, delete the Chrome profile, delete the recording inside RecBeam, or lose access to the device.

RecBeam does not maintain a server backup of recordings that were never successfully uploaded. After a cloud upload is successfully completed and verified, RecBeam may remove the matching local copy to reduce local storage usage. If an upload fails or cannot be verified, the local copy is retained where possible.

5. Cloud Storage

Recordings you choose to upload are stored using RecBeam’s Cloudflare infrastructure: Cloudflare Workers for application and API processing, Cloudflare D1 for account, session, recording, and screenshot metadata, and Cloudflare R2 for uploaded video files and screenshot images. Uploaded recordings are associated with the authenticated RecBeam account that created them.

6. Billing and Subscriptions

RecBeam offers a free Starter plan and a paid Business subscription. Business subscriptions are billed and processed by Lemon Squeezy, our payment provider and Merchant of Record.

When you start a Business checkout, RecBeam's server creates the checkout session directly with Lemon Squeezy and passes only your RecBeam account email and an internal RecBeam account identifier — RecBeam's servers never see or store your full card number, CVV, or other complete payment-card details. Payment information is entered directly into Lemon Squeezy's own secure checkout.

To keep your subscription in sync, RecBeam stores your current plan (Starter or Business) and billing interval, your subscription status (for example: active, past due, cancelled, expired), Lemon Squeezy customer, order, subscription, product, and variant identifiers used to look up and manage your subscription, and renewal and cancellation/end dates.

Lemon Squeezy notifies RecBeam of subscription changes through secure, signed webhook messages. RecBeam verifies the authenticity of every webhook message before applying any change to your account, and processes each webhook event only once.

To manage your subscription — update your payment method, change plans, or cancel — RecBeam directs you to Lemon Squeezy's hosted Customer Portal. RecBeam does not build its own payment-method entry forms.

Lemon Squeezy processes payment data under its own privacy policy and PCI-compliant infrastructure. See Lemon Squeezy's Privacy Policy for details on how they handle payment information.

Subscription and billing records are retained for as long as your account is active and afterward as needed to meet accounting, tax, and legal obligations.

7. Public Sharing Links

When you upload a recording or screenshot, RecBeam may generate a sharing link. Anyone who has a public link may view the recording without signing in. Business owners can add a password, restrict access, or allow-list emails. You are responsible for deciding who receives the link and for ensuring that the recording does not contain information you are not authorized to share.

8. Chrome Permissions

RecBeam requests only permissions required for its functionality.

Identity

Used to sign you in through Google and establish your RecBeam account session.

Storage

Used to store extension preferences, local recording information, and the active RecBeam session within your Chrome profile.

Clipboard access

Used when you choose to copy a recording-sharing link.

Access to api.recbeam.com

Used to authenticate, upload recordings, retrieve your cloud library, and access RecBeam’s API.

Active tab (screenshot capture)

Used when you click RecBeam’s toolbar and choose a screenshot of the current tab. Chrome grants temporary access to take that picture. RecBeam does not collect browsing history, keystrokes, or mouse telemetry, and does not scrape website text into RecBeam as a dataset.

Site access for recording HUD and full-page screenshots

RecBeam may show its own recording control HUD on the page while you record, and may inject helpers for full-page or selected-area screenshots you trigger. That is RecBeam’s capture UI, not a website tracker. RecBeam requests host access needed for those features on ordinary http(s) pages.

Offscreen capture

Used so a recording can continue if you change tabs. RecBeam still records only the source you approved in Chrome’s picker or camera/microphone prompt.

Screen, tab, camera, and microphone access

Used only when you initiate a recording and approve Chrome’s permission prompts. RecBeam does not activate screen, camera, or microphone recording without user action and browser permission.

9. Third-Party Services

Google

Used for Google Sign-In and account authentication. RecBeam requests only the basic identity information required to identify and authenticate the user.

Cloudflare

Used for API hosting (Workers), database (D1), file storage (R2), and Workers AI for transcripts and summaries.

Lemon Squeezy

Used as our payment processor and Merchant of Record for Business plan subscriptions. Lemon Squeezy handles checkout, payment collection, receipts, tax calculation, and the Customer Portal used to manage a subscription. See Section 6 above for details.

These providers process information according to their own terms and privacy policies.

10. Analytics, Advertising, and Tracking

The RecBeam Chrome extension does not currently use advertising SDKs or behavioral advertising trackers. RecBeam may count views on a share link when the owner has that option enabled. That is RecBeam’s own view count, not a third-party analytics SDK. We do not sell, rent, or trade Google account information, recording content, account information, authentication information, or usage information.

11. Data Retention

Local recordings remain on the applicable device until they are uploaded and removed, manually deleted, cleared with browser data, or lost through extension or Chrome-profile removal. Cloud recordings, screenshots, and their metadata remain stored until they are deleted through an available RecBeam deletion feature, you request deletion from us, the account or service is terminated, retention is required or permitted by law, or storage cleanup is required for incomplete or abandoned uploads. Revoked or expired session records may be retained for a limited period for security and operational purposes.

12. Data Deletion Requests

You may request deletion of your RecBeam account, account information, uploaded recordings and screenshots, and associated cloud metadata. Send requests to [email protected], including the Google email address associated with your RecBeam account. We may need to verify account ownership before processing the request. Deleting the extension from Chrome does not automatically guarantee deletion of cloud recordings already uploaded to RecBeam.

13. Security

We use reasonable technical and organizational safeguards, including HTTPS encryption in transit, server-side Google-token verification, hashed RecBeam session tokens in the database, account-based recording ownership checks, separation of users’ private recording libraries, protected upload and account endpoints, and restricted access to infrastructure and stored data. No storage or transmission system can be guaranteed to be completely secure. Users should avoid recording or sharing highly sensitive information unless they understand and accept the risks.

14. Children’s Privacy

RecBeam is not directed to children under 13, or the minimum age required to consent to online services in the user’s jurisdiction. We do not knowingly collect personal information from children without appropriate authorization.

15. Legal Disclosures

We may disclose information where reasonably necessary to comply with applicable law or legal process, protect RecBeam, its users, or others, investigate fraud, abuse, security incidents, or violations, or complete a business transfer, subject to appropriate safeguards.

16. Chrome Web Store and Google API Limited Use

RecBeam’s use of information obtained from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements. Data obtained through Chrome extension permissions and Google authentication is used only to provide and improve the user-facing RecBeam functionality described in this Privacy Policy. It is not used for advertising, credit decisions, or sale to data brokers.

17. International Processing

RecBeam and its service providers may process information in countries other than your country of residence. Where required, we take reasonable steps to use appropriate safeguards for international data processing.

18. Changes to This Policy

We may update this Privacy Policy when RecBeam’s functionality, infrastructure, legal requirements, or data practices change. The revised policy will display a new “Last Updated” date. Material changes may also be communicated through the extension, website, or other appropriate means.

19. Contact

For privacy questions, data requests, or concerns, contact: