Skip to content

Usage data

Usage data is on unless you turn it off. While it’s on, Olyvr sends a small set of usage events so we can see which features people use and where things go wrong. They never contain your messages, documents, file or folder names, channel or repository names, email addresses or anything else you typed or imported.

Open Settings → General → Usage data. It starts On. Click it to turn it Off: that stops sending, discards any events not yet sent, and stops including the install ID in update checks. Click it again to turn it back On.

On first launch Olyvr makes a random install ID and keeps it in state/telemetry.json in your data folder; deleting that file makes a new one.

While you’re signed in to your Olyvr account, events are also linked to that account. Olyvr’s admins can then see your usage on your account, such as how many documents and memories you keep, how many questions you ask, and how many model tokens you use: the counts in the events below, never anything they don’t contain. Events sent while you’re signed out aren’t linked to an account. The service that receives events doesn’t store your IP address.

Events go to Olyvr’s account service in batches every five minutes, with the install ID, the app version and the platform (for example mac-arm64). These are all the events, and the only fields they carry:

Event When Fields
installed The first launch of Olyvr on this computer none
updated The first launch after an update from: the previous version
reinstalled The first launch after Olyvr was installed again, or an older version was put back none
uninstalled Olyvr is removed on Windows (sent by the uninstaller) none
app_opened Olyvr starts none
active You used Olyvr in the last five minutes none
signed_in You sign in to an Olyvr account none
chat_sent You send a message to the agent route: API, subscription or local model
feature_used The first time each day you use a feature feature: chat, Today, agenda, workbench, Snapshot, Knowledge, projects, skills, documents, plugins, Workspace, local models or feedback
today_action In Today’s Focus: you start an item, a task starts, you draft or send a reply, change its mode, tick it done, dismiss it, move it to later, or reopen it action
today_tab You switch tabs in Today’s Focus tab: Today, Upcoming, Follow-up or Completed
citation_opened You open a source cited in Today’s Focus where: today
snapshot_page_created You add a Snapshot page none
snapshot_card_created You add a Snapshot card (tile) none
knowledge_edited You edit Knowledge (at most once per 10 minutes, since it saves as you type) none
source_connected You add a data source type, such as gmail or folder
source_disabled, source_enabled You switch a data source off or on type
import_finished An import you started finishes type, and whether it succeeded
plugin_installed, plugin_uninstalled You add or remove a plugin the plugin’s catalog ID, or custom
plugin_connected The first time a plugin connects on this computer the plugin’s catalog ID, such as notion, or custom
skill_installed, skill_uninstalled You add or remove a skill a standard skill’s name, or custom for your own
local_model_started You start a local model none
model_usage With each batch, if Olyvr asked a model anything since the last one how the requests reached their model (API, subscription or local), how many there were, and the number of input and output tokens they used, when the model service reports them
daily Once a day how chat reaches its model (API, subscription, local) and whose model it is (such as openai), the catalog IDs of your plugins, the types of your data sources, and how many memories Olyvr keeps: chat summaries, filled Knowledge sections and past Snapshot card versions, and how many documents are in Workspace (the numbers only)

The account service accepts only these events and fields and refuses anything else. Events are kept for 400 days, then deleted. While you’re offline, unsent events wait in state/telemetry-queue.json and go out the next time Olyvr is online; turning usage data off deletes them.

Lifecycle: downloads, updates, installs and removals

Section titled “Lifecycle: downloads, updates, installs and removals”
  • Downloads: when you download Olyvr from this site, or the app downloads an update, the update service records the version, platform and file.
  • Installs, updates and reinstalls: the installed, updated and reinstalled events above, sent the first time the new copy or version starts.
  • Active installs and removals: the app’s hourly update check carries the install ID while usage data is on. That counts active installs. On Windows the uninstaller sends uninstalled. On macOS and Linux an app can’t report its own deletion, so an install that stops checking for 30 days is counted as removed.