A privacy-minded desktop stack for financial review calls

A financial adviser sharing a portfolio review has two screens to manage: the one the client sees and the one that contains the adviser’s working material. A CRM tab, a downloaded statement, a password manager, or an incoming notification can become part of the meeting if the wrong window is shared.

A practical stack separates the records, the meeting, and the desktop. Use an approved CRM for client context, encrypted storage for documents, and targeted window cloaking for sensitive apps that must remain open during the call. None of those layers replaces firm policy or a proper test. Together, they reduce the chance that a screen-share mistake becomes a disclosure.

Start with the systems of record

Keep the CRM as the place for client details and meeting notes, rather than scattering working information across desktop files and chat messages. Before a call, open only the record and material needed for that client. Avoid leaving another client’s page or a broad search-results view in the background.

Store statements, tax documents, and other sensitive files in an encrypted storage service approved by the firm. Set access according to the firm’s rules, and retrieve only the documents needed for the review. Encryption helps protect stored or transmitted files, but it does not stop an authorized user from accidentally showing an open document to a client. That is a separate desktop problem.

Do not assume that a familiar CRM or storage provider is approved for every kind of client information. Confirm the firm’s retention, access, and vendor requirements before choosing tools. The software stack should follow those rules, not define them.

Add a screen-share boundary

Membran Digital’s NoCapture hides selected windows and apps from screen-sharing applications including Zoom, Teams, and OBS. Its features include per-window cloaking, title masking, global hotkeys, and a live preview. That makes it a possible boundary between what an adviser keeps open for reference and what appears in a shared desktop session.

For a call, identify the windows that should stay private, such as the CRM, encrypted file store, or password manager. Cloak those windows and share only the specific presentation or document intended for the client. Title masking can help keep real window titles out of places such as Alt+Tab and the taskbar; it is not a substitute for hiding the window itself. The live preview gives the adviser a way to check what the sharing setup sees before discussing account details.

NoCapture has a Free plan at $0 for two windows, a Pro plan at $5 per month, and a Teams plan at $49 per month. It is available on Windows 10/11, macOS, and Linux. Plan choice is a practical matter of how many windows and seats the firm needs; it says nothing by itself about whether the workflow meets the firm’s compliance obligations.

Make the test part of the routine

1. Prepare the meeting from the approved client record. Close unrelated tabs and documents, and confirm that the file being reviewed belongs to the right client.

2. Set the intended share target in the meeting application. Cloak the private windows with NoCapture, then check its live preview and the meeting’s own share preview where available.

3. Run a test with the same computer, operating system, meeting app, display arrangement, and sharing mode planned for the client call. Check notifications, task switching, and any window that might open unexpectedly. Do not treat one successful test on a different setup as proof for every setup.

4. During the call, share the prepared client-facing material rather than navigating through the whole desktop. Keep a short pause before switching documents so the adviser can confirm the next screen is appropriate.

5. After the meeting, close the shared material and follow the firm’s records and retention process. Screen privacy does not determine how meeting recordings, notes, or downloaded files should be handled.

This layered approach has trade-offs. Cloaking is targeted, so it requires deliberate window selection and can be misconfigured. It also does not correct an incorrect share target, an exposed document inside the shared app, or a client record placed in an unapproved service. If the meeting platform or operating system changes, retest rather than assuming the old routine still works.

For teams choosing a technical baseline, Membran Digital’s earlier comparison of OBS capture paths and window cloaking is useful background on why capture behavior deserves testing. For an adviser, the operational point is simpler: check the exact view a client will receive, not just the windows you intended to hide.

Keep the boundary visible to the team

Write down which CRM, storage, meeting, and desktop tools are approved, and give advisers a short pre-call checklist. A second person can review the setup for higher-risk calls. Treat that review as a control, not a guarantee. The strongest routine combines data minimization, approved systems, deliberate sharing, and a verified privacy boundary on the desktop.