ARDI — Botazez by Omnelia SIBOTAZEZ
by Omnelia SI

Understand where your data goes.

This page describes the workspace’s current technical behaviour. Features and connected services can have different processing requirements.

Public map and feed requests

Map tiles, geocoding, camera streams, market data and other public sources can be requested through Botazez or directly from their providers. Those providers and the website host can receive connection information such as an IP address and browser headers. Their availability and policies remain separate from Botazez.

Preferences and recent work

The browser stores settings such as your style choices, recent places and supported workspace history. This is browser-local storage, not a promise of account synchronization. Clearing site data removes local settings and history.

AI engines and keys you supply

OI keeps an entered provider key in session storage by default. If you choose to remember it, the key is kept in local storage. A key needed for an AI request is sent to the Botazez server in a request header so the configured provider can process the request; it is not used only on your device.

Questions, selected context and research inputs can be sent to the selected model or research services when you use those features. Check the selected provider’s processing terms before including confidential information. Leaving a tab does not erase a key saved with the remember option; clear it through the engine settings or your browser’s site-data controls.

Optional permissions

Your location is requested when you choose the location action. If a precise fix is unavailable, the workspace can attempt a rough network-based location. Bluetooth and media features depend on browser support, permissions and the device you explicitly select.

Analytics and operations

The application includes Vercel Web Analytics. Actual collection depends on the deployment and provider settings. Optional page analytics also require a configured endpoint and site identifier; the proxy no longer sends a separate raw-IP event or an invented screen resolution.

The hosting operator controls infrastructure logs, configured analytics and retention. This interface does not promise that clearing browser storage deletes provider or hosting records. Operator contact, retention and request-handling details must be established for a public production launch.