1. Scope
This policy applies to the Verbiqo website and desktop application. Verbiqo is designed to work with AI infrastructure selected by the user or their organization, including local models, organization-managed endpoints, and explicitly selected external providers.
2. Information processed by the desktop application
When you request a rewrite or document summary, Verbiqo processes the text you deliberately select or the document you deliberately choose. It sends that content and the required instructions only to the AI endpoint configured in the application.
By default Verbiqo sends only what you selected. Verbiqo can also read a limited amount of text immediately before and after your selection, up to 500 characters on each side, which helps a rewrite match the surrounding tone and lets a drafted reply see the message thread it belongs to. This is off unless you turn on Send the text around my selection in Settings. When it is on and you have configured an organization endpoint or external cloud provider, that surrounding text leaves the device along with your selection. Explain and Translate never use it. Organizations can enforce the setting through managed configuration.
When you summarize a document, Verbiqo reads the file you choose on your device, without changing it, and sends its text to the configured endpoint. If that endpoint is outside your device, Verbiqo asks for confirmation before the text is sent.
Verbiqo does not maintain prompt history, response history, or analytics containing your writing. Application settings, trial state, licences, connection details, and provider credentials are stored locally using operating-system storage such as macOS Keychain or Windows Credential Manager where applicable. An optional diagnostic log, off unless you enable it, records which steps ran, their sizes and timings, and any error messages, never your text.
3. When Verbiqo contacts verbiqo.app
Verbiqo also asks verbiqo.app, at most once a day, for two published files: the current version number, and the list of revoked licence identifiers. Both are the same constant files for every installation. The requests carry no identifier, no version, no licence and no cookie; they identify themselves only as “Verbiqo”, the same for every installation. Verbiqo keeps no record of who asked. Like any website, our hosting provider sees the network address a request comes from, as described in section 9. Verbiqo compares the version on your device and does not send it with these requests; the trial check in section 4 does. Both checks fail silently: if they cannot reach the site, Verbiqo continues to work exactly as before. You can turn them off in Settings, and organizations can enforce that through managed configuration.
4. Licence activation and trial checks
Unlike the two published files above, licence activation carries an identifier. To tie a licence to a computer and count its seats, Verbiqo derives a device ID from the computer's hardware identifier using a one-way hash, so the hardware identifier itself never leaves the device. When you activate, renew, or deactivate a licence, Verbiqo sends verbiqo.app the licence it was issued, that device ID, and the name the computer goes by. The name is the computer's name unless you change or clear it in Settings › Licence, or your administrator sets it. It is shown only to whoever holds the licence key, in its list of seats, so they can tell the computers apart. An activated licence renews at most once a day. If it cannot connect, it keeps working for up to 37 days. We keep, for each licence, the device ID and name of each computer holding a seat, when it was activated and when it last renewed, so that seats can be counted and freed. A seat that has not renewed within 37 days is removed, and a seat that is deactivated is removed at once. Your network address is used only momentarily to limit repeated requests and is not kept with these records.
While the site checks are turned on and the trial is running, Verbiqo also sends the device ID, the date its trial started, the version of Verbiqo and whether it runs on macOS or Windows, so that reinstalling does not restart a trial and so that we can count how many trials are in use on each version. We store only a keyed hash of the device ID, the earliest start date and the date of the latest check; the answer can make a trial shorter, never longer. The count records, at most once a day for each trial, the version, the platform and how many days into the trial it is, never the device ID or its hash, so it shows how many trials are in use, not whose; counts are kept for up to three months. Turning the site checks off stops this check. Apart from the computer's name described above, no name, email address, text, or usage information is sent by any of these requests. Licences issued for computers without internet access need no activation or renewal and send nothing to verbiqo.app; the checks in section 3 still run on those computers unless they are turned off.
5. The clipboard
Verbiqo reads and replaces text directly through the operating system's accessibility interfaces where the target application supports it. Some browsers, editors, and text fields require a keyboard and clipboard compatibility path instead. When that fallback is active, Verbiqo shows a notice before an action runs, captures the existing clipboard, and restores it after the operation, including non-text items and failure paths.
To read a selection through this path, Verbiqo sends Cmd+C (Ctrl+C on Windows) to the target application. The target creates the clipboard item containing your original selected text, and macOS does not allow Verbiqo to mark an item created by another process as private. A clipboard-history application may therefore retain that original selection before Verbiqo restores the previous clipboard.
For replacement, Verbiqo controls the temporary clipboard item and marks it as concealed and transient, asks compatible clipboard managers not to record it, and restores the previous clipboard shortly after the paste is consumed. These markers are defence in depth, not an operating-system security boundary: the operating system does not enforce them, and a clipboard manager may ignore them. Verbiqo cannot detect or erase copies already retained by another application.
You can disable clipboard fallback in Verbiqo Settings. Organizations can enforce that choice through managed configuration. If you work with confidential, personal, regulated, or proprietary information, review any active clipboard-history tools and either disable their history or disable Verbiqo clipboard fallback where retention is not acceptable.
6. Local, organization, and external AI providers
If you use a model on the same device, the text remains on that device. If you configure an organization endpoint or external cloud provider, the submitted text leaves the device and is handled under that provider's or organization's security, logging, retention, and contractual policies. Verbiqo displays an explicit boundary warning for supported external cloud providers and before sending a selected document off the device. Verbiqo is not the operator of those providers and does not receive what you send them.
7. Connected systems
Verbiqo can connect to monitoring, logging, and database systems you configure, such as Prometheus, Splunk, or PostgreSQL. Verbiqo contacts them directly from your device, with read-only requests. To answer questions quickly it keeps a local map of what a monitoring server watches, such as service, host, and measurement names, on your device. When you ask a question, the question and the relevant measurements, names, and results are sent to your configured AI endpoint so it can interpret them; none of it is sent to Verbiqo. If you set up the optional semantic index for a monitoring server, measurement names, their descriptions, and service and host identifiers, but no measured values, are sent to the embedding service you name. On macOS and Windows, saved connection passwords, API keys and tokens are kept in the Keychain or Credential Manager; connection settings and certificate paths are kept in a file only your account can read. Client certificate and key files remain at the paths you provide. On Linux, the command line keeps connection secrets in an owner-only local file. A Splunk directory password is stored in the operating system's credential storage only after Splunk accepts it and you choose to save it; otherwise Verbiqo keeps the scoped session key. We recommend least-privilege monitoring credentials. Organizations can disable extensions through managed configuration.
Connected-system investigations exclude secret stores, such as Kubernetes Secrets and database password settings. Sensitive values encountered in permitted results, such as tokens in log lines, are masked before being sent to the model. This differs from excluding those stores altogether.
Conversation content and returned evidence are held in memory until the conversation closes, unless you export it. Separately, Verbiqo keeps a local access record of statements, commands and requests it sent, with their account, time and outcome, but not the conversation or returned results. Sign-in secrets are masked and request bodies are represented by size and fingerprint. The record rotates at 20 MB with up to five files kept; your organization can require it and forward it to its SIEM, whose retention policy then applies. PostgreSQL, MySQL and SQL Server settings reviews also retain the last 20 local readings per connection, including counters and masked short statement texts, for before-and-after comparisons. Monitoring maps and metadata caches are local records described in the data guide.
8. The command line tool
The optional command line tool runs on your device and follows the same rules as the app: it sends the text you give it, and data from any system you attach, only to the AI endpoint you configure for it, and it keeps no history.
9. Website and enquiries
The website does not use an application database to store enquiries. If you submit the contact form, we process your email address and selected enquiry type to deliver the message to our support mailbox, prevent abuse, and respond to you. Enquiries are delivered by Cloudflare's email service to a mailbox hosted by Google.
The website and verbiqo.app services are hosted on Cloudflare, which processes ordinary technical request information, such as network addresses, needed to deliver and protect the service. The website uses no cookies for tracking and no advertising or analytics scripts. We count downloads of each release file by country, as Cloudflare already determines it for routing; nothing that identifies a visitor is recorded with that count.
10. Retention and disclosure
Verbiqo does not store desktop prompt or response bodies on a Verbiqo server. Licence and seat records described in section 4 are kept for as long as the licence is in force and as reasonably needed afterwards for records and disputes. Contact messages may remain in our business mailbox for as long as reasonably necessary to handle the enquiry, maintain business records, resolve disputes, or comply with legal obligations. We do not sell personal information.
11. Security
We use reasonable technical and organizational safeguards appropriate to the service. No method of storage or transmission is completely secure. Organizations are responsible for securing the inference endpoints, networks, models, credentials, and administrators they configure for Verbiqo.
12. Your choices and rights
You control which AI provider Verbiqo uses, whether to submit selected content or documents, which systems to connect, and whether the site checks run.
Shrevin Global Technologies Pvt. Ltd. is responsible for the personal information described in this policy. Subject to applicable law, including India's Digital Personal Data Protection Act, 2023, you may ask us for a summary of the personal information we hold about you, ask us to correct, complete, update, or erase it, withdraw consent where we rely on it, and nominate another person to exercise these rights on your behalf. Because we hold licence and trial records only against a hashed device ID, we may need you to tell us your licence ID or device ID to find them.
Grievance and privacy contact. Questions, requests, and complaints about personal information can be sent to our Grievance Officer at hello@verbiqo.app, marked “Privacy”. We will acknowledge your request and respond within the time required by applicable law. If you are not satisfied with our response, you may be able to complain to the Data Protection Board of India or to the data protection authority where you live.
13. Where information is processed
We are based in India. Our hosting and email providers, Cloudflare and Google, may process the limited information described in sections 4 and 9 in other countries, under their own safeguards. What you send to an AI provider is processed wherever that provider operates, under its terms.
14. Children
Verbiqo is a work tool and is not directed at children. We do not knowingly collect personal information from anyone under 18. If you believe a child has sent us personal information, contact us and we will delete it.
15. Changes
We may update this policy as Verbiqo develops. The current version and its update date will be published on this page. If a change materially affects how we handle your personal information, we will also give notice on the website or with the release notes of the app version it applies to before the change takes effect.