# Security and data storage

Local data, server data and current limitations

Source: https://ldmanager.cc/en/docs/security/
Updated: 2026-10-19

## Steam data on your computer

Your account list, Steam passwords, maFiles, authenticator secrets and saved Steam sessions are stored locally. The public build uses %LOCALAPPDATA%/LDManager. The application does not send Steam passwords or maFiles to the LDManager profile server.

The application connects to Steam for sign-in and trading operations. Local storage does not mean offline-only operation or no communication with Steam.

## LDManager server data

The server stores Telegram ID, username, nickname, avatar, subscription, roles, chat data and LDManager sessions. Checkout adds order, status and transaction information from 2328. Steam accounts are not uploaded into your website profile.

## Encryption and limits

The website and API use HTTPS. The Windows LDManager sign-in token is protected with DPAPI. Server-signed Pro grants and the release manifest protect specific access and integrity mechanisms.

However, accounts.json, Steam passwords and maFiles are not encrypted on disk yet. Someone with file access may read them. Protecting the LDManager token does not encrypt Steam data. There is no claim of unbreakable security.

## Deletion, audit and support

Deleting an account row does not guarantee deletion of original maFiles, sessions or backups, and does not unlink Steam Guard. No one-click complete wipe is available yet. Contact support to request website profile deletion; retention rules are described in the [privacy policy](https://ldmanager.cc/privacy.html), in Russian.

No public LDManager source repository is currently published. No independent security audit is claimed. The build does not yet have a Windows publisher certificate. Report issues to [@LDManager_Support](https://t.me/LDManager_Support) without passwords, maFiles or secrets.