Legal · privacy policy
This policy covers the hosted Nyquest app and API, the marketing and documentation sites, the Chrome extension, and the self-hosted engine. Their data flows differ. Hosted requests are processed on Nyquest infrastructure and by the model or service providers needed to fulfill them. Local extension or self-hosted compression does not by itself send prompts to Nyquest.
We process account details, requests and uploaded content, provider settings, usage, and billing records to operate the service. Signed-in browser conversations can be stored with summaries and memories for later recall. Personal API key chat-completion requests are stateless: they do not automatically create web chat history or run memory recall. Operational and billing records can still be retained.
Content needed for inference is sent to the selected provider. BYOK uses your provider account and its terms; it does not mean Nyquest never processes the request or stores your signed-in chat history. Nyquest does not use your content to train models. Providers' separate data policies and settings govern their processing.
The extension compresses supported outbound prompt text in your browser and stores preferences locally. Prompts then go to the provider you are using. A self-hosted engine runs on infrastructure you control and forwards requests according to your configuration. Nyquest's hosted retention practices do not describe a separately operated self-hosted installation.
Compression can change wording; review outputs and evaluate the profiles you enable for your workload. Local compression is not a universal guarantee that meaning or formatting is unchanged.
| Permission | Why |
|---|---|
| storage | Save your compression level preference locally |
| activeTab | Inject compression script into supported LLM chat pages |
| Host access | Intercept and compress outbound API requests on claude.ai, chatgpt.com, gemini.google.com, and grok.com |
The Chrome extension runs a content script in the page's MAIN world (rather than the default ISOLATED world) because it needs to intercept fetch(), XMLHttpRequest, and WebSocket calls made by the LLM chat interfaces.
This is the only way to compress prompt text before it is sent to the provider's servers. The script does not read responses, access cookies, or modify page behavior beyond compressing outbound prompt text.
The local extension does not require third-party analytics. The hosted service uses infrastructure, inference, payment, and communication providers to operate the product. This section does not claim that hosted requests avoid third-party processing.
When you use the Nyquest platform (the web app and API), we store applicable account content and records so the service can function, including signed-in chat history, memory, server-stored artifacts, and billing records. Local vault items may remain in your browser and require a separate backup. Access to that content is restricted to a small number of authorized personnel, who may access it only when necessary to:
Every such access to conversation content is recorded in an internal audit log (who accessed what, and when). We do not sell your content, and we do not use it to train third-party models. If you use your own provider keys (BYOK), your prompts are sent directly to that provider under their terms; we still apply the same access restrictions to any content stored on our systems.
To understand how the app is used and where it fails, the Nyquest web app records a small set of first-party product events — for example that the app was opened, a feature or theme was selected, a message was sent, or a page crashed. These events contain metadata only: they never include the text of your messages, your files, or anything you type. They are stored on our own infrastructure, are not shared with or sent to any third party, and are used solely to improve the product and diagnose problems.
Anonymous visitors are identified only by a random browser-generated identifier, not by name or account.
The nyquest.ai website logs standard web server access data (IP address, user agent, pages visited) for security and operational purposes. This data is used for security and operation of the sites, including processing by the infrastructure providers that serve them.
If you submit a demo request, your name, email, and company are stored to process your request. We use this information to respond; communication providers may process it to deliver the request or our response. We do not sell it.
Questions sent to Ask the docs are processed by embedding and language-model providers with relevant public documentation. Conversation history can remain in your browser's session storage. If you submit feedback, the question, answer, cited sources, vote, and any comment are stored to investigate and improve the service. Avoid sending passwords, API keys, or information you do not want processed by those services.
The hosted service uses HTTPS. Stored conversation and memory text is readable by the service for recall; it is not end-to-end encrypted. Stored provider credentials and backup archives use encryption. BYOK does not add end-to-end encryption to Nyquest history.
You can export account data and use the app's conversation, memory, and account deletion controls. Deleting one conversation does not necessarily remove durable facts deduplicated across conversations. Local vault items require their own export and deletion. See data controls.
A backup taken before deletion may retain a copy until it expires. Operational or billing records can also have separate retention requirements. Contact [email protected] for applicable retention details or a specific privacy request.
We publish updates at this URL with the revision date. Changes affecting the extension are also reflected in its release information where applicable.
For privacy questions or concerns: