Skip to main content

Overview

Velatir for Desktop needs a small set of operating system permissions to run as a background agent and deliver the browser extension. Everything is requested at install time, and the list is short on purpose: there is no microphone, camera, location, or full-disk access.

Windows

The installer asks for administrator rights once. It uses them to place the files and register the background service. After that, the CLI asks for elevation only for commands that change configuration or restart the agent. Velatir then runs as a background service that starts automatically, so it keeps working across reboots without anyone needing to launch it. A tray icon shows when it is running.

macOS

The installer asks for an administrator password once, the standard macOS installer flow. There is no kernel extension and no patching of system frameworks.
Velatir runs as a background service, so macOS 13 and later tells the user it “added items that can run in the background” and offers to switch them off. Separately, macOS holds notifications from a newly installed app back until the user opts in. On managed Macs, two quiet-install profiles settle both before the user sees either. Download them from the builder on Enterprise deployment.

Next steps

How it works

What the desktop client does on each device.

Enterprise deployment

Silent install and MDM rollouts.

Data privacy

What Velatir stores and how it scrubs sensitive content.

Troubleshooting

Diagnose approval and first-run issues.