Credentials and inference
Your key is held in browser memory, never persisted by INFERDEX, and sent directly to the selected provider (OpenRouter, Chutes or Groq) over HTTPS when you execute. Direct-provider catalog reads also send that provider’s key to its own API. Prompts, outputs, images and embedding inputs go to OpenRouter and its upstream providers when OpenRouter is selected; direct text requests go to Chutes or Groq. Their own retention and privacy terms apply; INFERDEX makes no zero-retention or confidential-compute guarantee.
Browser storage
Request history and conversations default to memory-only. Optional device storage is unencrypted. Favorites, explicitly saved templates and arena votes are stored locally. Settings provides export and deletion controls. Keys are never included in exports. The wallet connector may also retain public connection metadata in browser storage; use Disconnect on the wallet page and your wallet site permissions to manage that connection.
Hosting and public metadata
Public catalog and marketplace reads pass through the hosting platform and may be cached. Hosting infrastructure may process IP addresses and standard access metadata. INFERDEX has no prompt logging endpoint, advertising trackers, hosted user database or product analytics. The installable app caches only a static offline notice, never application pages, credentials or API responses. Video jobs run asynchronously at the provider; closing this app does not cancel them.
Wallet data
Connecting exposes your public address to the browser wallet integration. On-demand balance queries send the address to the official public RPC provider. We do not request seed phrases or private keys. Spraay payments require an explicit EIP-3009 wallet authorization. Prompts, responses and signatures pass through the INFERDEX payment relay to Spraay; the application does not log or persist those contents. Public settlement records may expose your address, recipient and amount on chain.
Your controls
Remove your key, disable persistence, export records or delete local data in Settings. Provider-side data must be managed directly with the provider.
Operator identity and a public support contact remain to be configured. Use the in-app documentation for setup, payment details and troubleshooting.