NoughtDigital RAG Assistant

Yes. The WordPress.org package is free and open source, and includes complete Qdrant and embeddings configuration, all supported providers and credentials, content synchronisation, chat UI, semantic search, analytics, diagnostics, model and retrieval controls, custom response instructions, and embedding settings. You need your own OpenAI API key and Qdrant instance, and provider usage costs may apply.

Yes. You can use Qdrant Cloud or self-host Qdrant on your own infrastructure. The plugin validates Qdrant host URLs.

The plugin supports OpenAI (for embeddings and chat), Claude (Anthropic), Mistral AI, Grok (xAI), Gemini (Google), and Amazon Bedrock for chat generation. OpenAI is required for embeddings.

Only when the optional semantic search override is enabled in General Settings. It is disabled by default.

No, the plugin does not create any custom post types, taxonomies, or user roles. It stores settings and recent task status in WordPress options, vector-sync state in post metadata, and, when personalisation is enabled for logged-in users, recent-view history in user metadata. It also creates two database tables for optional analytics (search interactions and result performance).

The uninstall process removes the plugin's WordPress options, all noragass_recent_views user metadata, its two analytics tables, and the _noragass_vector_sync_status, _noragass_vector_sync_date, _noragass_vector_sync_error, _noragass_vector_sync_action, and _noragass_vector_sync_queued_at post metadata. It does not delete data from Qdrant or an AI provider or clear browser local storage. External data remains subject to each provider's retention and account controls and must be removed separately when required.

The plugin makes external API calls to the following services when configured:

• Qdrant - For storing and retrieving vector embeddings (your configured Qdrant instance)
• OpenAI - For generating embeddings and optional chat responses (api.openai.com)
• Anthropic (Claude) - For chat generation when Claude is selected as the AI provider (api.anthropic.com)
• Mistral AI - For chat generation when Mistral is selected as the AI provider (api.mistral.ai)
• xAI (Grok) - For chat generation when Grok is selected as the AI provider (api.x.ai)
• Google (Gemini) - For chat generation when Gemini is selected as the AI provider (generativelanguage.googleapis.com)
• Amazon Bedrock - For chat generation when Bedrock is selected as the AI provider (bedrock-runtime.{region}.amazonaws.com)

API credentials use standard WordPress database storage and are not encrypted by WordPress itself. Protect the WordPress database, backups, server, and administrator accounts accordingly. Password fields are rendered without saved values in the page HTML, and leaving a field blank preserves the existing value server-side.

External API traffic starts after an administrator configures OpenAI and a Qdrant endpoint and then syncs content or makes the chat/search features available. OpenAI is always used for content and query embeddings. The selected chat provider is used to generate answers.

1. OpenAI API: Receives prepared WordPress content for content embeddings and each semantic-search or chat query processed by the plugin for a query embedding. Prepared content can contain the title, body, excerpt, author display name, public taxonomy terms, selected custom fields and metadata, ACF scalar values, and product information. If OpenAI is also selected for chat, it receives the system instructions, visitor query, and retrieved context passages.
2. Qdrant endpoint: Receives content vectors and the content payload described in the Qdrant external-service disclosure below. Searches send a numerical query vector. The endpoint may be self-hosted or operated by Qdrant Cloud or another hosting provider.
3. Selected chat provider: Anthropic, Mistral AI, xAI, Google Gemini, or Amazon Bedrock receives the system instructions, visitor query, and retrieved content passages when selected.
4. Local analytics: Disabled by default. When enabled, search/chat interaction and engagement data is stored in the site's WordPress database and is not sent to an analytics vendor.
5. Browser storage: The chat stores up to 20 conversation messages, source context, timestamps, cross-tab synchronisation data, and the minimised state in local storage. When analytics is enabled, the last query and interaction source are also stored temporarily in local storage, and a random 32-character noragass_session cookie is set for 24 hours to associate interactions.

The plugin is free and open source under GPLv3.