SAPauto Privacy Policy
Last updated: 14 October 2026
1. Scope and contact
This policy covers the SAPauto web service and Windows Agent, including its Microsoft Store package. SAPauto is operated by Konstantin Lokshin. For privacy requests, contact support@sapauto.ru.
2. Information and purposes
SAPauto does not remember your SAP Logon password or sign in to SAP on your behalf. You sign in through SAP GUI; the Agent works with an existing authenticated session. Your SAP username may appear in recording metadata.
We process the following information to provide the service:
- Account: login, display name, account identifiers, permissions and authentication records, to provide access. The web service uses a session cookie to keep you signed in. A real name is not required.
- Agent and device: installation and connection identifiers, computer name, operating system, Agent version and connection status, to link your computer and operate the Agent.
- SAP and workspace: SAP session details (system, client, window title and readiness), automation definitions, recordings, selected files, entered values, execution history, results and diagnostics, to record and run selected automation and synchronize results. Recordings and execution data may contain SAP screen content and personal or confidential business information.
- Support and logs: support email addresses, messages and attachments, and technical request and error logs, to respond to requests and diagnose problems.
The Agent exchanges connection, device, SAP session and work data with the SAPauto service you link it to. Only submit information you are authorized to use and share.
3. Storage, protection and sharing
Agent configuration, pending results and diagnostics are stored locally under your Windows account. The Agent stores its SAPauto service connection token in Windows Credential Manager. Connections to the public service use HTTPS; service access is controlled by account and workspace permissions. Other local files rely on Windows account and file access controls.
Service data and support email are hosted on VDSina in Moscow, Russia; backups are stored in Yandex Object Storage in Russia. These providers process data to provide hosting and backup services. Workspace participants can access shared content within their permissions. If you connect an external client or service, requested information is exchanged with its provider under that provider's privacy policy.
4. Retention
Account records, shared workspace content, support correspondence and backups have no scheduled automatic deletion period. Accounts remain inactive when access ends. Technical logs are rotated or limited by storage; diagnostics retained with workspace records follow workspace retention.
Exiting, unlinking or uninstalling the Agent does not delete previously uploaded records; local files may also remain. Deleting active service data does not immediately erase backup copies. Personal-information requests, including requests concerning backups, are reviewed under applicable requirements.
5. Your controls and requests
You choose the Agent connection and content submitted for automation or recording. Exit the Agent to stop background communication, or unlink it to revoke a service connection. Revoke external-client authorization to stop further access through that connection.
Contact us to request access to, correction of or deletion of your information. Identify the information and its location; we may verify your identity or authority. A request about one person's information does not automatically require deletion of other participants' shared content and does not limit applicable personal-information rights. Before removing local files, resolve pending work and delivery; support can help.
The current policy and its revision date are available on this page.