Last Updated: October 16, 2026
ElasticLens – Elasticsearch Monitor & Query Tool (“ElasticLens,” “the extension,” “we,” or “our”) is an independent Chrome extension that helps users connect to, inspect, monitor, search, manage, and export data from Elasticsearch clusters configured by the user.
ElasticLens is not affiliated with, sponsored by, or endorsed by Elasticsearch B.V. or Elastic.
ElasticLens handles information only when required to provide its user-facing features.
When a user creates or saves an Elasticsearch connection, ElasticLens may store the following information in the user’s local Chrome extension storage:
Connection name
Elasticsearch server URL
Authentication type
Elasticsearch username
Elasticsearch password
Elasticsearch API key or other authentication credentials
Currently selected connection
This information is used only to connect to Elasticsearch endpoints selected by the user.
When the user accesses a configured cluster, ElasticLens may process information returned by that Elasticsearch endpoint, including:
Cluster health and version information
Node and resource metrics
Index names
Index mappings and settings
Index aliases
Index statistics
Shard allocation information
Data streams
Snapshot repositories
Snapshot metadata
Snapshot lifecycle policies
Elasticsearch documents and document fields
Search requests and results
Aggregation results
Query performance measurements
Elasticsearch tasks
Error responses and diagnostic information
ElasticLens displays and processes this information inside the extension. It is not transmitted to the ElasticLens developer.
ElasticLens may store the following information in the user’s local Chrome extension storage:
Saved Elasticsearch connection profiles
Connection credentials
Active connection selection
Query history
Query performance history and comparisons
REST request history
Saved queries
Alert rules
Per-index alert thresholds
Active and historical alert information
Metric history
Error logs
Saved AI explanations
User interface preferences
Theme and navigation preferences
Auto-refresh settings
Selected indices
AI provider configuration
Custom AI endpoint configuration
Optional AI provider API keys
Ollama endpoint and model settings
ElasticLens does not operate a developer-controlled database for this information.
When the user chooses an export action, ElasticLens may create files containing:
Search results
Query results
Connection backup information
Optional connection credentials, when explicitly selected by the user
Exported files are downloaded directly to the user’s device. Users are responsible for securing exported files, especially connection backups that include credentials.
AI features are optional and operate only after the user configures an AI provider and initiates an AI action.
Supported AI options may include:
OpenAI
Anthropic Claude
Google Gemini
OpenRouter
Mistral
A user-configured OpenAI-compatible HTTPS endpoint, such as RunPod
Ollama running locally on the user’s computer
Depending on the action selected by the user, ElasticLens may send the following information to the selected AI provider:
Natural-language questions
Elasticsearch Query DSL
Search requests
Selected product or document text
Elasticsearch field names
Index names
Mapping and field-type information
Mapping conflict details
Elasticsearch error messages
Error types, status codes, and root causes
Up to 20 matching Elasticsearch documents or aggregation results when the user enables Use index data
Snapshot names and repository names
Snapshot status and timestamps
Snapshot index names
Snapshot shard counts
Up to 20 snapshot failure reasons
Other metadata required to perform the user-requested AI action
AI features may be used to:
Generate Elasticsearch queries
Answer questions about selected index data
Explain Elasticsearch errors
Explain mapping conflicts
Analyze snapshot status and failures
Recommend diagnostic or recovery steps
Generate embeddings for semantic search
Assist with Elasticsearch configuration and operations
Snapshot AI analysis sends snapshot metadata only. It does not send snapshot contents and cannot create, restore, or delete snapshots.
AI-generated recommendations are informational. Elasticsearch write operations remain separate actions and may require user confirmation.
When the user selects a cloud AI provider, the relevant information and the user-supplied API key are sent directly to that provider or endpoint.
Cloud AI providers process information according to their own privacy policies and terms.
OpenRouter and custom OpenAI-compatible endpoints may route requests through infrastructure or models selected by the user.
When Ollama is selected, ElasticLens restricts requests to a configured loopback address on the same computer, such as:
http://localhost
http://127.0.0.1
Ollama requests are not sent to the ElasticLens developer.
AI provider API keys are supplied by the user and stored in the user’s local Chrome extension storage. ElasticLens uses a key only to make requests to the corresponding provider selected by the user.
The ElasticLens developer does not receive these keys.
ElasticLens uses information only to provide its disclosed purpose and user-facing functionality, including:
Connecting to user-configured Elasticsearch clusters
Authenticating with those clusters
Displaying cluster health and resource metrics
Browsing and managing indices
Running Elasticsearch searches and aggregations
Building Elasticsearch Query DSL requests
Displaying and exporting results
Managing aliases
Assisting with reindex operations
Detecting mapping conflicts
Viewing and managing snapshots
Displaying shard allocation
Running user-entered REST requests
Saving local query and REST history
Saving reusable queries
Evaluating alert rules
Displaying browser notifications
Providing optional AI-assisted features
Restoring the user’s local extension settings between sessions
ElasticLens does not use information for:
Advertising
Personalized advertising
Retargeting
Selling user data
Data brokerage
Unrelated profiling
Determining creditworthiness
Lending decisions
ElasticLens sends Elasticsearch requests directly to the endpoint selected and configured by the user.
These requests may include:
Authentication credentials
Elasticsearch queries
REST request bodies
Index and cluster operations
Data required to perform the action requested by the user
The ElasticLens developer does not receive these requests or responses.
Users should use HTTPS for remote or production Elasticsearch endpoints. Local HTTP endpoints may be used for local development.
When a user explicitly initiates an AI feature, ElasticLens sends the necessary request and relevant content directly to the selected AI provider.
ElasticLens does not automatically send Elasticsearch information to an AI provider merely because a provider is configured.
Index documents or aggregation results are sent only when the user enables Use index data and submits a chatbot request.
ElasticLens does not currently collect or transmit usage analytics, behavioral analytics, advertising identifiers, or telemetry to the ElasticLens developer.
The storage permission is used to save user-created settings and local extension information, including:
Connection profiles
Credentials
Query and REST history
Saved queries
Alert configuration
Metric history
Error logs
AI provider configuration
User preferences
The notifications permission is used to display browser or operating-system notifications for:
Elasticsearch alert rules explicitly enabled by the user
The user-initiated Test notification action
Notifications contain only the configured cluster label and alert summary. They are not used for advertising and can be disabled in Alert Management.
ElasticLens requests access to HTTP or HTTPS hosts only when required to connect to a user-configured service, including:
Elasticsearch endpoints
Supported cloud AI APIs
Custom OpenAI-compatible endpoints
A local Ollama endpoint
Host access is optional and is not automatically granted during installation.
Chrome may ask the user to approve access to a specific host when the user saves or tests a connection or provider.
ElasticLens uses approved host access only to make direct API requests to the configured service. It does not read, monitor, or modify ordinary websites or general browsing activity.
If host access is declined, the associated connection or provider remains unavailable until the user grants permission.
Users can review or remove granted host access through Chrome’s extension settings.
The declarativeNetRequestWithHostAccess permission is used only for compatibility with a user-configured custom OpenAI-compatible endpoint.
Some compatible endpoints reject requests containing a Chrome extension Origin header. ElasticLens may create a session-only rule that removes that header only for the exact custom endpoint host approved by the user.
ElasticLens does not use this permission to:
Monitor browsing activity
Inspect ordinary website traffic
Block ordinary websites
Redirect ordinary websites
Modify requests to unapproved hosts
Track users
Users may enable notifications for configured Elasticsearch alert rules.
Alert evaluation may include:
Cluster health
Disk usage
Snapshot recency
Index document counts
Index storage size
Other explicitly configured thresholds
Alert settings and alert history remain in local Chrome extension storage.
Users can disable notifications through ElasticLens or Chrome’s notification settings.
ElasticLens may communicate with the following services only when configured or initiated by the user:
User-configured Elasticsearch endpoints
OpenAI
Anthropic
Google Gemini
OpenRouter
Mistral
User-configured OpenAI-compatible endpoints
Local Ollama
Each third-party service processes information according to its own terms and privacy policy.
ElasticLens does not sell user data or share information with advertisers, analytics providers, or data brokers.
Locally stored extension information remains in the user’s Chrome profile until one of the following occurs:
The user removes the information through ElasticLens
The user clears the extension’s stored data
The user removes the extension
Chrome removes the extension’s local storage
ElasticLens does not retain Elasticsearch content or AI requests on a developer-controlled server.
Retention by Elasticsearch endpoints, AI providers, custom endpoints, or locally operated services is governed by those services and the user’s own configuration.
Users control:
Which Elasticsearch clusters they connect to
Which credentials they provide
Which permissions they approve
Which queries and REST requests they run
Which write operations they confirm
Which results they export
Whether alert notifications are enabled
Whether AI functionality is configured
Which AI provider is selected
Whether index data is included in an AI request
Which local records are saved or deleted
Whether connection backup files include credentials
Users should connect only to Elasticsearch environments they are authorized to access.
ElasticLens relies on Chrome extension storage and Chrome’s extension security model for locally stored settings and credentials.
Users should:
Use HTTPS for remote Elasticsearch and AI endpoints
Protect Elasticsearch and AI credentials
Restrict Elasticsearch permissions to the minimum necessary
Avoid including credentials in exported backups unless required
Store exported files securely
Use trusted AI providers and custom endpoints
Review AI-generated recommendations before applying changes
Avoid using production data when testing destructive operations
ElasticLens does not publicly disclose authentication information.
ElasticLens is a developer and administrative tool and is not directed to children.
ElasticLens does not knowingly collect children’s personal information through a developer-controlled service.
ElasticLens’s use and transfer of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
Information is used or transferred only as necessary to provide or improve the extension’s disclosed, user-facing functionality.
ElasticLens does not:
Sell user data
Transfer user data to advertising platforms or data brokers
Use user data for personalized advertising
Use user data for retargeting
Use or transfer user data to determine creditworthiness
Use or transfer user data for lending purposes
Allow the ElasticLens developer or other humans to read user data, except where the user gives explicit consent for support, where required for security, or where required by law
This Privacy Policy may be updated when ElasticLens features, permissions, third-party integrations, or data practices change.
The Last Updated date will be revised whenever material changes are made.
Where required, material changes to data handling will also be disclosed through the extension interface or Chrome Web Store listing.
Developer: FinSocial Digital Systems
Email: info@finsocialdigitalsystems.com
Website: https://finsocial.tech/