DocsUninstall & data

Help

Uninstall & data

Akev keeps its settings, rules, CA and saved traffic in one data directory per user. Uninstalling the app leaves that directory in place, so a reinstall picks up where you left off. To remove Akev completely, undo what it set up, uninstall it, then delete its data.

Nothing is sent anywhere when you uninstall. There is no account or licence server to sign out of, and your licence key isn't tied to the computer: keep it (it's in your purchase email and in your account) to use it again.

The data directory

System Default data directory
Linux ~/.local/share/akev ($XDG_DATA_HOME/akev when that variable is set)
macOS ~/Library/Application Support/akev
Windows %LOCALAPPDATA%\akev, that is C:\Users\<you>\AppData\Local\akev
Docker image /data inside the container; the download page mounts the volume akev-data there

On Windows it's in the local profile, not the roaming one that domain profiles copy between machines, and Akev's CA key gets an access list that only your account can use.

To see the directory in use, open Settings → About → Data directory. akev start prints it as Data, and akev ca path prints the CA certificate inside it.

  • The desktop app always uses the default data directory.
  • The akev command line uses it too, unless you pass --data-dir DIR or set AKEV_DATA_DIR.
  • --ephemeral (and akev capture, which is always ephemeral) neither reads nor saves settings and rules. Without --data-dir, it uses a temporary folder named akev-… in the system's temporary directory, deleted when Akev exits, with a CA of its own.

On Linux and macOS, Akev creates the directory readable only by you, and the files holding keys and tokens too.

What's in it

Path What it holds
ca.pem, ca.key Akev's CA certificate and its private key, generated for this installation. Regenerating the CA keeps the previous pair as ca.pem.bak and ca.key.bak.
ca-bundle.pem Your system's CA certificates plus Akev's, for terminals and containers.
settings.json Your settings and interface preferences. It can hold client-certificate passphrases.
rules.json Your rules.
settings.json.bak, rules.json.bak A settings or rules file that couldn't be read, moved aside.
license.json Your Akev Pro licence key, and when the trial started.
daemon.json Address, access token and process id of the running instance, for the CLI. Removed when Akev exits.
open-ui.html The private page akev start opens the UI with. Removed when Akev exits.
sessions/ Saved sessions (<id>.akev, each with a <id>.json description), autosave.akev and autosave-previous.akev. See sessions.
spill/ Bodies moved out of memory when the memory budget is reached. The files are deleted automatically, so it's normally empty.
protos/ Imported protobuf schemas (files/) and their URL mappings (mappings.json).
wireguard.json The WireGuard server's and device's keys.
profiles/ Profiles of browsers launched from Connect (profiles/chrome, profiles/firefox…), with their cookies, logins and history.
logs/ Akev's own log (akev.log, with akev.log.1 and akev.log.2), and the output of programs it launched: browsers, terminals, Electron apps. See troubleshooting.
crashes/ Crash reports (crash-<time>.txt), the newest 30, with secrets scrubbed out.
akev.lock, instance.json The lock that keeps one Akev per data directory, and who holds it.
exports/ Where AI agents' HAR exports go (see MCP).
terminal/ Scripts for terminals launched from Connect (and akev-off.cmd on Windows).
docker/ Environment files for the Docker and Podman snippets.
java/ A Java truststore with the Akev CA, for Java tools.
jvm/ The agent Akev loads into JVMs you attach to, and the list of attached JVMs (attached.json).
android/ The copy of the CA Akev pushes to Android devices.
system-proxy-backup.json Your previous system proxy settings, while System Proxy is on (or after a crash).
android-proxy.json Android devices Akev set a proxy on, while that is the case.
recovery/ The same two records for runs that used another data directory.
trial.json macOS only; see below.

Most of these only appear once you use the feature they belong to.

Outside the data directory

The Pro trial. When you start the 14-day trial, Akev records its start in trial.json in your user account's configuration directory, which every data directory reads. That is why the trial runs once per user account on a computer, not once per data directory.

System Location of trial.json
Linux ~/.config/akev/trial.json ($XDG_CONFIG_HOME/akev when that variable is set)
macOS ~/Library/Application Support/akev/trial.json, in the default data directory
Windows %APPDATA%\akev\trial.json, in the roaming profile, outside the data directory

The desktop app's window. The desktop app keeps its window size and position (and, on Linux and Windows, its web view's data) in folders named after its app id, dev.akev.desktop:

System Folders
Linux ~/.config/dev.akev.desktop, ~/.local/share/dev.akev.desktop
macOS ~/Library/Application Support/dev.akev.desktop
Windows %APPDATA%\dev.akev.desktop, %LOCALAPPDATA%\dev.akev.desktop

Snap and flatpak browsers launched from Connect keep their Akev profile inside their own sandbox: ~/snap/<browser>/current/akev-profiles or ~/.var/app/<app id>/data/akev-profiles.

Data directories you chose with --data-dir or AKEV_DATA_DIR are wherever you put them.

Before you uninstall

Back up what you want to keep: Settings → Data → Export configuration saves your settings and rules in one file, and saved sessions can be downloaded from Settings → Data → Saved sessions.

Undo what Akev set up

  1. Quit Akev. A clean exit turns System Proxy off and restores your previous settings, clears the proxy on Android devices it set up over ADB, restores JVMs it attached to, removes the CA files it copied into running containers, and closes the browsers and terminals it launched. If Akev crashed at some point, start it once and quit it: the start restores the system proxy settings a crashed run left behind and clears the proxy on its Android devices once they're connected (see the system proxy is still set). JVMs a crashed run attached to are listed in Connect → Running JVM; Restore them there, or restart them.
  2. Transparent capture: run the commands under When you're done; Akev can't remove the redirect rules itself. See transparent capture.
  3. Devices:
    • Android: a device that was disconnected when Akev quit keeps its proxy; clear it with adb shell settings put global http_proxy :0. Remove the Akev CA from the device's user certificates (under Encryption & credentials; the wording varies by vendor) and delete Download/akev-ca.crt.
    • iPhone and iPad: set Configure Proxy back to Off and remove the profile in Settings → General → VPN & Device Management.
    • Proxies you entered by hand on any device: switch them off.
    • WireGuard: delete the Akev tunnel in the WireGuard app. Left on, it cuts the device off the internet while Akev isn't running.

Remove the CA from trust stores

Akev changes your system's trust store only when you click Trust in Settings → Certificates → Trust on this computer, so only the places where you (or that button) installed its CA need cleaning. Do this before deleting the data directory: some of the commands read ca.pem, and akev ca commands generate a new CA when none exists.

The quickest way: in Settings → Certificates → Trust on this computer, click Remove next to every store that says Trusted. Trust by hand, below it, shows the commands for this computer, each with a To remove it later block that already contains this CA's path and fingerprint. Remove trust again covers every platform. In short:

bash
# Linux: added with `trust anchor --store` (Fedora, RHEL, Arch, openSUSE)
sudo trust anchor --remove "$(akev ca path)"
# Linux: copied to /usr/local/share/ca-certificates (Debian, Ubuntu)
sudo rm /usr/local/share/ca-certificates/akev-ca.crt && sudo update-ca-certificates --fresh
# Linux: Chrome and Chromium's own NSS database
certutil -d sql:$HOME/.pki/nssdb -D -n 'Akev CA'

# macOS: System keychain (or without sudo and -d: the login keychain)
sudo security remove-trusted-cert -d "$(akev ca path)"
  • macOS: after removing the trust setting, delete the certificate itself in Keychain Access.
  • Windows: run certmgr.msc → Trusted Root Certification Authorities → Certificates and delete the Akev certificate. If you installed it for Local Machine (all users), remove it from the local computer's store instead.
  • Firefox: a CA you imported into your own profile is listed under Firefox's Settings → Privacy & Security → Certificates. Browsers launched from Connect need nothing: they trust the CA through their Akev profiles, which go with the data directory (and the snap and flatpak folders above).

Every CA carries a random id in its name (O=Akev, OU=<id>, CN=Akev CA), so after regenerating you may find several Akev CA entries. Remove all of them.

Uninstall the app

Package How to remove it
macOS (.dmg or .app.tar.gz) Quit Akev and move Akev from Applications to the Trash.
Windows installer (-setup.exe) Settings → Apps → Installed apps (Windows 10: Apps & features) → Akev → Uninstall.
Windows MSI The same, under Akev.
Linux AppImage Delete the .AppImage file.
Linux .deb sudo apt remove akev
Linux .rpm sudo dnf remove akev
Command line (.tar.gz, .zip) Delete the akev binary (akev.exe on Windows).
Docker docker rm -f akev, then docker volume rm akev-data (the data) and docker image rm ghcr.io/akevdev/akev:<version>.

The Windows installer's uninstaller offers Delete the application data. Ticked, it removes the desktop app's dev.akev.desktop folders and Akev's data directory (%LOCALAPPDATA%\akev, and %APPDATA%\akev), and takes Akev's CA out of your account's Trusted Root store if it was added there. Left unticked, everything stays for a later reinstall. The other packages never delete your data: see delete the data.

Delete the data

Once the CA is out of your trust stores and nothing points at Akev any more, delete the data directory and the other folders. On Linux:

bash
rm -rf ~/.local/share/akev ~/.config/akev ~/.config/dev.akev.desktop ~/.local/share/dev.akev.desktop

On macOS:

bash
rm -rf ~/Library/Application\ Support/akev ~/Library/Application\ Support/dev.akev.desktop

On Windows, in PowerShell:

powershell
Remove-Item -Recurse -Force -ErrorAction SilentlyContinue "$env:LOCALAPPDATA\akev", "$env:APPDATA\akev", "$env:APPDATA\dev.akev.desktop", "$env:LOCALAPPDATA\dev.akev.desktop"

Also delete any directory you used with --data-dir or AKEV_DATA_DIR, and the akev-profiles folders of snap or flatpak browsers.

This removes the CA's private key, your licence key, saved sessions and everything else listed above. If you reinstall later, Akev starts fresh with a new CA.

Type to search guides, the CLI and the API.