Where Does AusweisApp Store Config and Logs?
AusweisApp keeps its config in OS-specific spots and talks to browsers over a local server on port 24727.
Last updated
AusweisApp stores little and connects a lot. Settings and protocol data sit in OS-standard locations that differ per platform. At runtime it exposes a local WebSocket the browser uses to reach the ID card.
No identity data accumulates in these files beyond logs and preferences. The card itself stays the credential. That is why reinstalls fix most issues: fresh config, same card, working flow.
Where AusweisApp stores this, by platform
HKEY_CURRENT_USER\Software\Governikus GmbH & Co. KG
Vendor registry key and autostart entry survive uninstall until deleted by hand. Local server listens on 127.0.0.1:24727. Logs go to the temp folder and self-delete.
~/Library/Preferences/com.governikus.ausweisapp2.plist
Preferences plist plus container folders under ~/Library/Containers. Delete both after removing the app for a clean slate. Same localhost port as Windows.
~/.config/AusweisApp2_CE/AusweisApp2.conf
User config for community builds. Official docs note the log path and keep flags in the man page. Flatpak and distro packages share this layout.
/data/data/com.governikus.ausweisapp2
Private sandbox for settings with SDK logs under the app files folder. NFC handles card access. The app holds no card data between sessions.
/var/mobile/Containers/Data/Application/<guid>/Documents
Sandboxed container with the same session-only model. Card readout runs over NFC per transaction. Nothing persists beyond preferences.
Frequently asked questions
How do I uninstall AusweisApp without leftovers?
Remove the program, then delete its leftovers by hand. Windows keeps registry entries under the vendor key plus an autostart value. macOS keeps a plist and container folders. The official FAQ lists each path.
Where is the AusweisApp log file?
Check the log in the system temp folder on desktop or the app files folder on Android. Desktop logs self-delete on exit unless started with keep flags. Support asks for this file first.
What is the port 24727 listener?
It serves the browser-to-card bridge on localhost. The eID flow calls http://127.0.0.1:24727 on desktop. A second local service or firewall rule on that port breaks identification.
Notice an outdated path? Let us know.