No matching documentation found

Frequently Asked Questions (FAQs)

Find answers to frequently asked questions, technical troubleshooting steps, and operational guidance for Login AlertX v4.0 on Windows and Linux.

Yes. The background service (LoginAlertXService on Windows and loginalertx.service on Linux) runs at the system level and monitors all user accounts. On Windows, individual users can customize their own alert channels and notification preferences, while the service ensures no access events are missed even if the user interface is closed.

Yes. Session detection, AI risk scoring, and evidence capture operate 100% locally and do not require internet access:

  • Offline Queuing: When a device is offline, events and media attachments are saved to an encrypted local SQLite outbox.
  • Automatic Dispatch: As soon as internet connectivity is restored, all queued alerts are automatically dispatched in chronological order.
  • Local Network SMTP: If your environment utilizes a local on-premise mail relay, email alerts will send immediately even without WAN/Internet access.

Login AlertX is built with a strict local-first, zero-knowledge architecture:
  • All stored SMTP credentials, webhook URLs, and API tokens are encrypted locally with AES-256 and Windows DPAPI.
  • Login AlertX never transmits your passwords, tokens, event logs, webcam photos, or audio recordings to external cloud servers.
  • When using Sign in with Google (OAuth), Google tokens are refreshed locally and your master password is never stored or seen by the app.

Login AlertX requires zero desktop GUI on Linux. After installing the package, use the terminal CLI:

# 1. Run interactive configuration wizard
sudo loginalertx configure

# 2. Start and enable background daemon
sudo loginalertx start

# 3. Check live daemon health & logs
sudo loginalertx status

The loginalertx.service systemd daemon runs silently on boot and monitors SSH key/password logins, console TTYs, and sudo commands.

  • On Windows: Press Win + R, type services.msc, locate Login AlertX Service, and click Start. If the service is missing, run the installer again as Administrator and choose Repair.
  • On Linux: Inspect systemd logs via sudo journalctl -u loginalertx.service -n 50 or restart the unit via sudo systemctl restart loginalertx.service.

  • Email (Google OAuth): Open Settings and re-authenticate your Google account.
  • Email (Custom SMTP): If using Gmail with SMTP, generate a 16-character App Password from your Google Account Security settings (standard account passwords will be rejected by Google).
  • WhatsApp: Ensure your phone number includes the international country code without spaces or dashes (e.g. +15550192834 or +919876543210).
  • Slack / Teams / Discord: Use the Test Webhook button in settings to confirm the incoming webhook URL is active and valid.
  • Local Event Log: Check the Stats / Logs tab in the app. If the event is recorded locally, the trigger is functioning and the issue is related to channel credentials or outbound firewall ports (443 or 587).

  • Windows GUI: Open the app, navigate to the License tab, and click Start 30-Day Free Trial (no credit card required), or enter your purchase email and Serial Key and click Activate.
  • Linux CLI: Run sudo loginalertx license activate <SERIAL_KEY>.

Yes. All physical and visual capture features are 100% optional and disabled by default. You can independently enable or disable webcam capture, audio recordings, or desktop screenshots at any time via the Preferences / Media Capture panel or via the Linux CLI configuration.

You can download our standalone Cleanup Utility. This official tool cleanly terminates background services, unregisters scheduled tasks, and wipes local database and cache traces (%AppData%\LoginAlertX).

On Linux, run sudo loginalertx uninstall or sudo dpkg -r loginalertx.

Still Have Questions?

Our support team is happy to assist with custom deployments, enterprise licenses, or technical questions.

Contact Support →
Scroll to Top