Legal home · Search Privacy · Terms & AUP

OmniLore.AI — Frontier Search Privacy Statement

Product: OmniLore.AI (dual-seat fabric, including Chat at chat.omnilore.ai)

Document: Search-Privacy Statement (Frontier Search)

Version: 1.0

Effective: 2026-08-03

Related: Terms & Acceptable Use · ops gap analysis GAP_ANALYSIS_FRONTIER_SEARCH_PRIVACY_2026-08-03

This Statement describes how Frontier Search (web research tools used by OmniLore Chat agents, OpenClaw/CoTrinity agents, and related MCP clients) handles search queries and results. It is part of OmniLore’s user-facing privacy and acceptable-use materials.

1. What “Frontier Search” is

In OmniLore, Frontier means live web research, not hosting of “frontier” foundation models.

Typical flow:

1. Prefer local fabric knowledge (for example Goldie / tribal / Qdrant via OmniLore MCP tools).

2. On a miss (or when you or an agent explicitly request world/live knowledge), OmniLore may call frontier_on_miss / frontier_research.

3. Results are treated as an untrusted draft (trust=frontier_web, low trust strength) unless promoted under operator policy.

Frontier Search is available to authorized OmniLore users and agents on the dual-seat deployment (including chat.omnilore.ai when the OmniLore Shared Operator / MCP path is used). It is not a public internet search engine product and is not offered as an anonymous public SearXNG site.

2. How search is performed (provable architecture)

Research may use, in order, depending on configuration and availability:

Self-hosted SearXNG on OmniLore:

• Runs as container omnilore-searxng under OmniLore ops.
• Is bound to localhost only (not published as a public multi-tenant search website).
• Aggregates results from engines enabled in our configuration (currently including DuckDuckGo, Wikipedia, Google, Brave, and Bing—subject to change by operators).
• Acts as an intermediary so agents query our instance rather than a random public SearXNG host.

This aligns with SearXNG’s design as a self-hostable metasearch engine. It does not mean third-party engines never receive a query (see §4).

3. What OmniLore does and does not track

3.1 Local SearXNG instance

OmniLore’s SearXNG deployment is operated as a private infrastructure component. We do not operate it as a public instance that builds advertising profiles or sells search history. We do not provide Frontier Search to the general public as a standalone browser search engine.

3.2 OmniLore operator records (fabric governance)

When Frontier results are promoted into Goldie (including auto-promote under quality gates, when enabled), OmniLore may retain:

• The search query text
• Promotion metadata (keys such as frontier:auto:…, timestamps, result counts)
• An audit log on the control plane (for example frontier-promote.jsonl) for operations and safety

Research that is not promoted may not appear in that audit file, but may still be processed in memory and by third-party backends during the request.

Rate limiting of frontier calls is enforced on the MCP process (not a per-user private vault).

3.3 What we do not claim

We do not claim that Frontier Search is:

• Fully anonymous end-to-end
• Invisible to third-party search engines
• Free of all operator logs when results are stored
• Suitable for illegal or abusive activity

4. Third-party search providers and content

4.1 Queries leave OmniLore when external backends run

When Tavily, Google CSE, SearXNG-backed engines (Google, Bing, Brave, DuckDuckGo, etc.), Wikipedia, or similar services are used, those providers process the search query (and typically the source IP of our server). Their terms and privacy policies—not OmniLore’s—govern how they handle that data.

Industry practice for AI products that use web search is to disclose third-party search providers and that shared query content is subject to their policies. OmniLore follows that practice.

4.2 OmniLore does not control third-party content

OmniLore does not control, create, or verify the accuracy, legality, safety, or completeness of content returned by third-party search engines or web pages when Frontier Search is used.

• Rankings and snippets come from external systems.
• Web pages may be wrong, offensive, outdated, or unlawful in your jurisdiction.
• Agents may summarize untrusted drafts; you remain responsible for how you use outputs.
• Public websites that share the name “OmniLore” (for example omnilore.org) may be unrelated false friends and may be filtered on fabric-technical queries—but filters are imperfect.

4.3 Citations and trust labels

Frontier drafts should be treated as untrusted web research. Prefer fabric SoT tools for product truth about OmniLore itself. Cite URLs from tool results when relying on frontier content.

5. Multi-user / dual-seat note

OmniLore is a dual-seat, multi-user fabric (humans and agents). Frontier infrastructure (MCP, SearXNG, audit logs, Goldie keys) is shared operational infrastructure. It is not designed as a personal “private search history” product that isolates every query from operators. Authorized operators may access logs and promoted entries for security, reliability, and compliance.

6. Acceptable use (search-specific)

You must not use OmniLore Frontier Search (or any OmniLore service) to:

• Engage in illegal activity under applicable law
• Seek or distribute child sexual abuse material, or content that exploits minors
• Conduct unauthorized intrusion, malware distribution, fraud, or violent crime facilitation
• Harass, stalk, or threaten others
• Circumvent access controls or scrape in violation of law or third-party terms

OmniLore may log, rate-limit, refuse, or escalate suspected abuse. Full rules: Terms & Acceptable Use.

7. Your choices

• Prefer fabric-only answers (Shared Operator tools without web) for sensitive product or internal matters.
• Avoid putting secrets (passwords, keys, personal data of others) into prompts that may trigger Frontier Search.
• Operators may disable or reconfigure backends (Tavily, CSE, SearXNG, auto-promote) via environment gates without changing this Statement’s core duties of disclosure.

8. Changes

We may update this Statement as the dual-seat architecture evolves. Material changes will be reflected in ops SoT (ops/legal/) and the URLs linked from Chat settings. Continued use after updates constitutes acceptance where permitted by law.

9. Contact

Operator contact for privacy questions related to this dual-seat deployment: the OmniLore owner/operator (as configured for your tenancy). For product SoT questions inside Chat, use OmniLore Shared Operator tools (sot_get, architecture_card) rather than public web.

*OmniLore.AI · Frontier Search Privacy Statement v1.0 · 2026-08-03*

OmniLore.AI · dual-seat · chat.omnilore.ai