Privacy, without the fog.

Last updated: August 29, 2026

ScreenLens is local-first. Recording, editing, project recovery, and local export do not require an account or an upload. Cloud rendering and pseudonymous product analytics are separate, optional actions you choose.

Who operates ScreenLens

ScreenLens is operated by Better Brain Lab LLC and developed byHesham Mashhour. Questions and privacy requests can be sent tocontact@hesham.us.

1. Data that stays on your device

When you use the free, local workflow, ScreenLens handles the following inside your Chrome browser profile:

• video from the tab you explicitly select;
• tab audio, microphone audio, and camera video only when you enable them;
• cursor positions, clicks, scrolling, and viewport dimensions used for editing effects;
• named non-text keys and explicit Ctrl, Command, or Alt shortcuts used by the optional shortcut overlay;
• project settings, annotations, imported editing assets, recovery revisions, recording settings, and limited local diagnostics.

ScreenLens does not record standalone printable characters or keyboard events from password fields, inputs, textareas, selects, or content-editable elements. It does not collect DOM selectors for clicked elements.

Local data remains until you delete it, clear extension storage, or uninstall ScreenLens. A project journal keeps up to ten healthy project revisions. Deleting a recording also deletes its project journal. Exported downloads are managed by you through Chrome or your operating system.

2. Optional product analytics

Anonymous analytics is off by default. If you enable it in ScreenLens Settings and approve the optional ScreenLens API permission, the extension may send event-only product diagnostics such as export started/completed/failed, export format, resolution bucket, duration bucket, processing-speed bucket, recovery success, extension version, and a random installation identifier.

Analytics never includes session replay, autocaptured interactions, screenshots, recordings, audio, page URLs or titles, typed text, project names, annotations, raw error messages, cursor paths, or keyboard data. Events pass through the ScreenLens API, which enforces an allowlist, before they are sent to PostHog. The API disables person profiles and IP-based geolocation and does not add your IP address as an analytics property. Cloudflare may process ordinary connection information while delivering the request.

Consent is the basis for this optional processing. You can turn analytics off at any time in Settings. If this browser is connected to Pro, the narrowly scoped ScreenLens API permission may remain for cloud rendering, but analytics events stop immediately. Product-event data is retained for no longer than 12 months and is used only to understand reliability and improve user experience—not for advertising or cross-site profiling.

3. Accounts, devices, and billing

Local use needs no account. If you use ScreenLens Pro, Clerk processes sign-in and basic account information. The extension does not receive your password or Clerk browser session; it uses a one-time device approval page and stores a revocable random device token locally. The server stores only a cryptographic hash of that token.

Stripe processes checkout, subscriptions, invoices, tax-related details, and payment methods. ScreenLens does not receive or store full card numbers. Account, entitlement, device, render-usage, and subscription-status records are retained while your account is active and as reasonably required for security, support, accounting, disputes, or legal compliance.

4. Optional Pro cloud rendering

A cloud render begins only after you choose Turbo export and confirm the transfer. ScreenLens uploads the source media and the editing data needed to reproduce your requested output. Before upload, browser-tab URLs and titles are removed from the project manifest. The recording itself may visibly contain sensitive information, so review it before choosing cloud render.

Cloudflare processes uploads, job metadata, rendering, and downloadable results using R2, D1, Workers, Workflows, and Containers. Inputs and outputs are scoped to the requesting account and scheduled for automatic deletion after 24 hours. Minimal render metadata—status, duration, format, usage, timestamps, and safe error codes—may be retained for up to 30 days for support, abuse prevention, and billing reconciliation.

5. Support requests

If you email support, the contact details and message you intentionally provide are used to answer, investigate, and secure ScreenLens. Do not send passwords, tokens, confidential page contents, or recordings unless support specifically asks and you agree. Support messages are retained only as long as reasonably necessary for those purposes or legal obligations.

6. Service providers and disclosure

ScreenLens uses the following processors only for the product functions described above:

• Cloudflare — website, API, structured data, temporary media storage, and cloud rendering;
• Clerk — optional Pro authentication and account sessions;
• Stripe — optional Pro checkout, subscriptions, invoices, and billing portal;
• PostHog — optional, event-only product analytics without autocapture or replay.

ScreenLens does not sell data, serve targeted advertising, broker data, or use recording content to train AI models. Data may be disclosed if required by law, to protect users and the service, or as part of a business transaction with appropriate safeguards and notice.

7. Chrome permissions and Limited Use

ScreenLens uses Chrome permissions to capture a user-selected tab, inject the recording tracker only after your action, keep capture running in an offscreen extension document, store local data, and provide notifications. Microphone and camera permission are requested visibly only when enabled. ScreenLens does not request access to every website at installation. The ScreenLens API origin is an optional permission requested only when you enable analytics or connect Pro.

The use of information received from Google APIs complies with the Chrome Web Store User Data Policy, including Limited Use requirements. Handled data is used only to provide or improve visible ScreenLens features, maintain security, and comply with law.

8. Your choices and rights

You can delete local recordings in ScreenLens, clear extension storage, uninstall the extension, disable analytics, revoke a connected device, cancel Pro through the billing portal, or request deletion of server-side account data. Depending on where you live, you may also have rights to access, correct, export, restrict, object to, or erase personal data, and to complain to a data-protection authority.

Email contact@hesham.us to exercise a server-side data right. We may need to verify your identity before completing a request.

9. Security, children, and changes

ScreenLens uses transport encryption, short-lived upload authorization, hashed device tokens, access controls, and automatic cloud-object cleanup. No system is perfectly secure; please report suspected issues through the support page. ScreenLens is not directed to children under 13.

Material privacy changes will be disclosed before the new practice begins when required, and this page's date will be updated.