Security and data protection, built into Lensmor.

A clear view of how Lensmor protects customer account data, workspace data, and customer-specific enriched data.

Last updated August 14, 2026

Protected data streams converge through Lensmor’s security architecture.
InfrastructureCloud service controls
Data at restProtected storage
Data in transitHTTPS / TLS
Published safeguards

A clear starting point for your review

This page summarizes safeguards already described in Lensmor’s Privacy Policy and Terms of Service. It does not claim certifications or controls that have not been verified.

01

How Lensmor separates data

Public and partner-provided business information

Event, company, and professional information obtained from public event sources and, when available, event organizers or data partners.

Customer account and workspace data

Information used to operate a customer’s Lensmor account and workspace.

Customer-specific enriched data

Contact data a customer chooses to unlock or enrich is returned by integrated third-party data providers and stored in that customer’s private workspace. It remains available with the customer account through supported product and API features and is not made available to other Lensmor customers.

02

Infrastructure and data protection

Encrypted infrastructure separates data channels with managed boundaries.

Cloud infrastructure

Lensmor uses cloud infrastructure and supporting service providers to operate the service. Current providers for a specific workflow can be confirmed during a vendor review.

Storage safeguards

Lensmor applies storage safeguards designed to protect customer and customer-directed enriched data, including workspace separation and access controls. Lensmor does not use customer-specific enriched data to build a shared contact database. Architecture-specific details can be provided for the relevant engagement.

Encryption in transit

Connections between customers and Lensmor use HTTPS/TLS. Protocol and configuration details can be confirmed in a security questionnaire.

03

Production access and logging

Controlled production access

Production access is limited to authorized personnel and supported by access controls and monitored operational processes.

Sensitive log data

Operational logs are used for security and troubleshooting. Lensmor seeks to minimize sensitive information and restrict access to operational data.

04

AI processing boundaries

Public analysis signals remain separate from a private enriched data stream.

Public business context

Lensmor may send anonymized excerpts of public business content to AI providers to generate summaries or insights.

Customer-specific enriched data

AI processing depends on the feature and customer instructions. Data categories, providers, and applicable retention settings can be confirmed for the workflow under review.

05

Customer control and service providers

Export and deletion

Customers can export supported data through available product or API features. Customer-directed enriched data is generally retained with the account so authorized users can access prior results. Account deletion is handled under the Privacy Policy, including applicable backup, legal, fraud-prevention, and security retention requirements.

Privacy requests

Professionals represented in the Lensmor directory can request access, correction, or removal through the Privacy Center.

Service providers

Lensmor uses providers for cloud infrastructure, enrichment, AI-assisted analysis, payments, and product analytics. Current categories and named examples appear in the Privacy Policy.

06

Data transparency and methodology

Why a record appears

Exhibitors are companies shown on official event, exhibitor, sponsor, or related public sources. Social Signal Attendees are identified from public professional activity connected to an event. Visitors are supplied by event organizers or data partners when available. These labels explain the evidence behind a record; they do not all mean organizer-confirmed registration.

Coverage and freshness

Coverage depth varies by organizer, source availability, region, timing, and partner coverage. Monitoring may become more frequent as an event approaches. Lensmor does not claim complete coverage for every event.

Contact data and confidence

When a customer chooses to unlock or enrich a record, business contact details may be returned by integrated third-party providers. Availability and accuracy vary by provider and record, so customers should validate information that is critical to an outreach workflow.

Correction and removal

Professionals may request access to, correction of, or removal of information associated with them through the Privacy Center. Lensmor may retain limited suppression information to help prevent removed profiles from being republished.

07

Procurement support and security reporting

Security questionnaires

Send the questionnaire, product scope, and requested review date to hello@lensmor.com. Lensmor will review the applicable controls and identify supporting materials available for the engagement.

Workflow-specific scope

Data categories, provider categories, AI-processing boundaries, and applicable retention settings can be confirmed for the product workflow under review. This avoids applying one broad statement to materially different processing activities.

Policies and processing terms

The Privacy Policy, Terms of Service, and Cookie Policy describe Lensmor’s public baseline. Applicable processing or transfer terms can be discussed for the relevant customer engagement.

Report a security concern

Email hello@lensmor.com with the affected service or URL, reproducible steps, and potential impact. Please avoid accessing, changing, or retaining unrelated customer data.

Vendor security review

Ready for a vendor security review?

Send your questionnaire or request workflow-specific details about data categories, service providers, AI boundaries, retention, and applicable processing terms. Lensmor will confirm what is available for the engagement.

Request review materials