Security & Data Handling
Account and licence server for existing customers
This domain hosts the account and licence backend that TIA Openness Manager used and that AnyAutomation Studio still signs in to. This page describes what that backend receives, how it protects your account and where the data is kept. Everything about the software itself, from local processing to the encrypted vault, is on the security page of AnyAutomation Studio.
Account and Licence Backend
Licence Server: The Only Outbound Connection
The only data the software ever transmits to our licence server is:
- Customer ID (assigned at purchase)
- Hardware ID (a local fingerprint of your workstation, derived from hardware identifiers; it is the same for every Windows account on that workstation)
- Windows account ID (a second local fingerprint, derived from the Windows account you are signed in with, so that sign-ins by different people on one workstation can be told apart; the account name itself is never transmitted)
- Timestamp
Apart from your account e-mail address and the technical details of the request itself, that is the full payload. No engineering data, no project metadata, no usage statistics, no file names.
Verification guarantees:
- Licence responses are digitally signed. A tampered or forged response is rejected by the software before it is trusted.
- A licence response is checked against the binding recorded at activation, so it cannot be reused outside the installation it was issued for.
- Rate limiting protects against brute-force probing of customer IDs.
The software operates offline for up to 14 days between validations, useful for engineering workstations without permanent internet access.
Account System: Authentication & Web Portal
Licences are bound to your personal account so hardware switches, plan changes and team seats can be self-managed without contacting support.
- Passwordless sign-in: authentication uses a 6-digit one-time code delivered by email (single-use, 15-minute validity, stored only in encrypted form). No passwords exist, so none can be phished, stolen or leaked
- Session protection: on suspected token theft, all session tokens of the account are revoked completely
- Origin protection on all authentication endpoints prevents cross-site calls from unauthorized domains
- Hardware-switch limit: up to 3 switches per rolling 30 days as protection against licence sharing (more frequent switches via support)
- Shared workstations: sign-ins from different Windows accounts on the same workstation are recorded as separate bindings, so one licence passed around a team on a single PC is visible to us
Data Location
The account and licence backend runs in the EU. Account data does not leave the European jurisdiction.
Stored on the server: your e-mail address, the subscription status and the hardware binding. Payment data is held by the payment provider, not by us.
See the Privacy Policy for the formal data-protection notice.
Local Data of TIA Openness Manager
TIA Openness Manager stored its data under your Windows user profile at:
%LocalAppData%\TiaOpennessManager
This includes log files, user settings and the encrypted vault file. None of these paths were synced, uploaded or shared by the software. The vault file opens unchanged in the Password Vault of AnyAutomation Studio with the same master password, and export folders created with TIA Openness Manager can be imported there directly.
Questions?
For questions about data handling, the account backend or compliance:
Email: support@tiaopenessmanager.ch
See also our Legal Notice for provider information.
© 2025-2026 AnyAutomation. All rights reserved.
Security and data handling in AnyAutomation Studio
Local processing of TIA Portal projects, no telemetry, credential storage, the encrypted Password Vault, AI features that stay inactive until you configure a provider, and signed releases: all of this is described on the security page of AnyAutomation Studio.