Privacy and your data
A short summary of where your information goes. The Privacy Policy is the full and binding version.
Where your information goes
| What | Goes to | When |
|---|---|---|
| The text you select | Your chosen AI service only | When you choose an action |
| Up to 500 characters around it | Your chosen AI service only | Only if you turn on Send the text around my selection |
| A document's text | Your chosen AI service only | When you summarize it, after you confirm if the service is outside your computer |
| Results from connected systems | Your chosen AI service only | When you ask about them |
| Measurement names and descriptions, never values | The embedding service you named | Only if you set up the optional semantic index for Prometheus |
| Your licence, a one-way device ID, and the computer’s name on the licence | verbiqo.app | When a licence key activates, and once a day while it is active. The name is your computer’s name unless you change or clear it in Settings › Licence. It is shown only to whoever holds the licence key, in its list of seats. |
| The device ID, trial start date, and Verbiqo’s version and platform (macOS or Windows) | verbiqo.app | Once a day during the trial, while update checks are on. Trials are counted per version, never by device. Details |
| Nothing that identifies you | verbiqo.app | A daily check for a new version and revoked licences |
Verbiqo never sends your text, your questions or what it read to verbiqo.app. With an AI service on your own computer, those stay on your computer. Verbiqo still connects to the systems you attach, and to verbiqo.app for the licence, trial and update checks above, which carry none of that content.
What Verbiqo keeps
- No conversation history. Conversations are held in memory until you close them, and are saved only if you export one.
- Readings for follow-ups: for PostgreSQL, MySQL and SQL Server, each settings review keeps a reading of the server’s counters (and short statement texts as the server records them, without values) on your computer, the last 20 per connection, so Did the changes help? can compare before and after.
- On your computer only: settings, your licence, API keys and connection details, the map of your monitoring servers, and for each Kubernetes connection the cluster’s names (namespaces, workloads, services), read as metadata only and kept in a
k8s-mapsfolder for ten minutes. If your organization limits questions per hour, also the times each system was asked in the last hour. - The access record, always on: every statement, command or request Verbiqo sent to a connected system, as it was sent, with the connection, account, time and outcome, in
access-log.jsonl(~/Library/Application Support/Verbiqo/on a Mac,%LOCALAPPDATA%\Verbiqo\on Windows). Not your question, the answer, or what came back. A sign-in is recorded with its secret masked. Your organization may collect it. What it holds. - A diagnostic log, only if you turn it on, which records steps and timings, never your text.
What goes where, and for how long
| Kind of data | Where it goes | Why | How long it is kept |
|---|---|---|---|
| Conversation content: your questions, selections, documents and answers | The AI service you configured, and nowhere else | To answer | By Verbiqo: in memory until you close the window. By the AI service: its own terms |
| Evidence read from your systems | Masked as it is read, then to your AI service | To investigate | In memory for the conversation. Readings for follow-ups: the last 20 per connection. The Prometheus map: names and descriptions, entries older than 30 days pruned |
| Credentials and connection settings | Passwords, keys and tokens in the macOS Keychain or Windows Credential Manager. The rest in a file only your account can read. The Linux command line keeps connection secrets in that restricted file; client certificate and key files stay at the paths you supply | To connect | Until you remove the connection |
| The access record | A file on your computer. Your organization’s SIEM if it sets that up | So security teams can see what was read | Up to five files of 20 MB, oldest removed first |
| Licence and trial records | verbiqo.app | To count seats and keep a trial from restarting | A seat until it is freed, or 37 days without a renewal. See the Privacy Policy for the trial record |
Your controls
| To | Do this |
|---|---|
| Keep everything on your computer | Use a model on your own computer, such as Ollama. How |
| Stop the daily checks | Turn off Tell me when a new version is available in Settings. |
| Avoid clipboard-history copies | Turn off Allow keyboard/clipboard fallback for compatible apps. Why |
| Stop reading your systems | Turn off Let Verbiqo read databases and other systems, or remove a connection. |
In an organization, your administrator may set some of these for you, and a signed privacy policy may block or redact some kinds of data before anything is sent. What administrators can control.