Lensmor – Trade Show Footprint for LinkedIn

Description

See past and upcoming trade shows connected to a person or company—directly on LinkedIn—then draft relevant AI outreach. When you first use the extension, it asks for your account-access agreement before it checks the Lensmor sign-in session on Lensmor's own domain to recognize your account. It then uses the sign-in session and short-lived authentication tokens for sign-in and authenticated API calls, and may load your Lensmor account email, display name or avatar URL, plan and Credits. Only when you start the Lensmor login / Return to LinkedIn flow, the extension stores the current www.linkedin.com return URL and its tab, window, and Lensmor login-tab identifiers in Chrome local storage for up to 2 hours. This lets it offer an explicit Return to LinkedIn choice after Onboarding; it does not automatically close or redirect the Lensmor page. On app.lensmor.com, the extension bidirectionally synchronizes only the user-controlled Outreach Preferences used for drafting—outreach purpose, tone, and any optional meeting link or signature—between the app's localStorage and the extension's chrome.storage.local. It reconciles those local copies when the page loads, when the window gains focus, when page visibility changes, and when its 2-second local-change check detects an edit. These preferences remain locally stored until you change or clear them; uninstalling the extension removes its Chrome-storage copy but does not by itself clear the first-party app's localStorage. When a professional lookup may use Credits, the extension also stores a 15-minute transaction-safety marker in Chrome local storage so an interrupted request cannot cause a duplicate deduction. Its storage key is a SHA-256-derived opaque account/person reference and its value contains only creation and expiration times—not names, email addresses, LinkedIn URLs, raw account or personnel IDs, or event results. It is isolated by Lensmor account, may remain across sign-out or account switching, is never used after 15 minutes, and is removed during the next recovery/cache check after expiry or on uninstall. Company and person lookup data is sent to Lensmor only when you request that lookup and agree. AI-drafting data is sent only when you choose Generate and agree. The extension does not read LinkedIn authentication cookies, collect your general browsing history, or send LinkedIn messages automatically. Lensmor lets you look up a person's or company's past and upcoming trade show participation directly from the LinkedIn page you are already viewing. On a LinkedIn company page, open Exhibition Footprint to see trade shows the company has exhibited at and upcoming events where it is expected to exhibit. On a professional profile, use the same workflow to find events the person has attended and events they are expected to attend. If Lensmor finds multiple possible identities, you choose the correct match before a credit-using lookup. From the results, you can open the corresponding event records in Lensmor. Eligible Lensmor users can also create an AI-assisted LinkedIn connection note, message, or InMail draft using the visible profile and saved outreach preferences. For an existing conversation, recent visible conversation context may be used for that requested draft. Every draft is inserted into LinkedIn for review and editing. Lensmor never sends LinkedIn messages automatically. Key features: - View a company's past and upcoming trade show participation. - View events a professional has attended or is expected to attend. - Resolve ambiguous company or person matches before a chargeable lookup. - Open matched event records in Lensmor. - Draft and edit personalized LinkedIn outreach before sending. A Lensmor account is required. Company reverse lookup is available to signed-in users and uses 50 Lensmor Credits only when results are found. Professional reverse lookup requires an active eligible paid plan and also uses 50 Credits only when results are found. AI drafting requires an active eligible paid plan but does not use event-lookup Credits. Data use and control: - On supported LinkedIn company, professional and message-composer pages, the extension locally recognizes the page type and visible company or recipient identity needed to place the Lensmor action. This local recognition can occur when the page loads. It is not sent to Lensmor unless you invoke the related feature and agree; conversation text is not read until you choose Generate and agree to AI drafting. - A company lookup reads the visible company name, LinkedIn company identifier and website domain. It sends the company name and, when needed, website domain to Lensmor as search terms, plus matched Lensmor exhibitor identifiers. The LinkedIn company identifier remains in Chrome for matching and cache isolation. - A professional lookup reads the visible name, profile URL, headline, location, employer and About text. It sends the name and matched Lensmor personnel identifiers to Lensmor. The other profile fields remain in the extension for identity matching unless you separately request an AI draft. - AI drafting sends the visible recipient profile, your Lensmor Profile and saved outreach preferences or writing instructions to Lensmor and its AI provider. For an existing conversation, it can also include up to the 12 most recent messages currently loaded in LinkedIn, limited to about 4,000 characters total. - The extension asks for separate agreement before the first account-access check, company lookup, person lookup or AI draft. You can review and reset these choices in Lensmor Extension Settings. - On app.lensmor.com, outreach purpose, tone, and any optional meeting link or signature are synchronized in both directions between the app's localStorage and the extension's chrome.storage.local. Reconciliation runs on page load, window focus and page-visibility changes, and a local-change check runs every 2 seconds. These user-controlled preferences remain in the two local stores until you change or clear them. Uninstalling the extension removes the extension copy; the first-party app copy remains until you change it or clear the app's site data. - When the extension opens an attributed app.lensmor.com session, the app may send account identifiers, IP address, browser details, page views, clicks, session replay, and an indication that the session originated from the extension to an analytics service provider only for first-party product analytics, security, and reliability. LinkedIn profile, lookup, conversation, and generated-draft content is not intentionally sent to analytics or used for advertising. - Only when you start the Lensmor login / Return to LinkedIn flow, the current www.linkedin.com return URL and its tab, window, and Lensmor login-tab identifiers are stored in Chrome local storage for up to 2 hours. They are used only to offer your explicit Return to LinkedIn choice after Onboarding. - When a professional lookup may use Credits, Chrome local storage keeps a 15-minute transaction-safety marker to prevent duplicate deductions after an interrupted request. The key is a SHA-256-derived opaque account/person reference and the value contains only creation and expiration times. It stores no names, email addresses, LinkedIn URLs, raw account or personnel IDs, or event results. It is account-isolated and may survive sign-out or account switching; it is never used after 15 minutes and is physically removed at the next recovery/cache check after expiry or when the extension is uninstalled. - Conversation context is read only after you choose Generate and agree. It is not stored by the extension, and the resulting draft is never sent automatically. - Event-result cache entries expire after 24 hours and are never returned after expiry. They are isolated by Lensmor account and physically deleted during subsequent authenticated extension activity, or immediately on sign-out or account switch. If Chrome and the extension remain inactive past expiry, an inaccessible expired entry can remain until the next such activity or until the extension is uninstalled. Apart from the single temporary LinkedIn return URL described above, the extension does not collect general browsing history. It does not read LinkedIn authentication cookies, sell extension data, or use it for personalized or retargeted advertising.

Details & SEO