DXB MCP Extension Privacy Policy

Effective and last updated: 15 October 2026

This policy covers DXB MCP, the Chrome extension that lets you explore public DXB Interact market information, navigate pages and change filters through chat or voice. It describes the extension’s handling of data. Your use of the DXB Interact website and Google’s services is also subject to their respective policies.

Information the extension handles

  • Your Gemini API key: used to authenticate your requests with Google. You supply your own key and use your own Google project’s quota and billing.
  • Messages and voice: the text you send, audio you choose to record or stream, transcripts, and the assistant’s responses.
  • Connected page context: the public DXB page URL, selected filters, permitted page controls and public market results needed to answer your request. The extension does not request general browsing history or access to unrelated websites.
  • Preferences: your selected connection mode, consent, action permission, speech preference and optional local relay pairing token.

The extension does not read DXB account cookies, passwords or private profile fields. Its tool catalogue excludes property-specific private reads and removes known credential, contact and unit-number fields from structured results before sharing them with Gemini. Text you choose to send may still contain personal information; avoid sending sensitive details that are unnecessary for your request.

How information is used and shared

After you agree to the connection notice, messages, transcripts, audio and permitted page context are sent to Google Gemini to provide the requested conversation, transcription and site actions. In the default direct mode, your key is sent only to Google’s API host, never to DXB servers, page scripts or the model prompt. HTTPS requests use a key header; live voice uses Google’s WSS endpoint with its required key query parameter.

If you explicitly select the advanced local relay mode, messages and recorded dictation pass through the relay you run on your own device at 127.0.0.1:8788 before reaching Google. The relay uses the Gemini key you configure there; it is not a DXB-hosted chat service. Live voice requires the direct connection.

Public market-data requests and navigation still reach DXB Interact and its website services. Ordinary website or service request logs are governed by those services’ policies. The extension adds no advertising, analytics or third-party tracking SDK and does not send chat or audio to a DXB chat-storage service.

Data is used to provide the extension’s user-facing features. The extension does not sell personal data or use or transfer it for advertising, creditworthiness or lending decisions. Its use and transfer of user data follow the Chrome Web Store User Data Policy, including the Limited Use requirements.

Microphone and spoken replies

Dictation begins only when you press the microphone button, stops after at most 45 seconds, and produces a transcript for you to review before sending. Live conversation begins only when you press Start voice. During a live call, microphone audio streams continuously to Google until you mute, end the call, close the panel or reach the 15-minute call limit. Spoken requests may change the site’s public filters or navigate immediately, subject to your action-permission setting.

End call stops microphone tracks, playback, the live connection and pending actions. The extension does not keep a background recorder after the panel closes. The microphone permission helper briefly checks permission and immediately stops its stream. Spoken responses may be audible to people nearby. Outside live calls, optional Read replies aloud uses Chrome or operating-system speech services and installed voices.

Storage, retention and deletion

By default, your Gemini key stays in trusted extension session storage for the browser session. Remember my key on this device opts into local extension storage in that Chrome profile. The extension does not use Chrome sync for keys. This storage is not a separate encrypted vault; someone with access to your device or browser profile may be able to access it.

Connection preferences and any local relay pairing token are stored locally. Conversations and audio buffers are kept in memory for the active session rather than deliberately saved as chat or audio files. New chat clears the extension’s text conversation; each new live call starts a fresh live context. Closing the panel releases its in-memory conversation.

Use Remove my saved key to clear the Gemini key from both session and local extension storage. Uninstalling the extension removes its Chrome-managed local settings. You can revoke or replace a key in Google AI Studio and revoke microphone permission in Chrome. These actions do not delete information already processed by Google or normal website-service logs.

Text and dictation Interactions requests set store:false; that setting does not apply to the separate Live API. Google’s own terms, data-use, retention and deletion rules apply to data it receives and may differ by your project, billing and service settings. See Gemini API terms and Google’s privacy policy.

Permissions and your choices

Side-panel permission displays the assistant. Scripting and active-tab access connect to the selected public DXB Interact tab and invoke its native WebMCP tools. Storage retains your connection choices. Host access is limited to the supported DXB origin, Google’s API and the optional loopback relay. Microphone access is requested by Chrome separately. The extension does not provide arbitrary code-execution, login, payment, claim, lead-submission or download tools.

You can decline data sharing, disable automatic site actions, mute or end a call, remove your key, or uninstall the extension. Cancelling cannot undo a page action already completed.

Questions and updates

For questions about this extension or a privacy request, use the developer support contact shown on the DXB MCP Chrome Web Store listing. Do not include an API key, password or private property identifier in your support message. Material changes to the extension’s handling of data will be reflected in this policy and, where required, its connection notice and consent flow.