HostAxe Privacy Supplement
HostAxe product terms. This English text is authoritative; contact rox.techlead@gmail.com for clarification before acceptance.
1. Scope and controller
This notice supplements https://roxensoft.com/en/privacy-policy. For licensing, purchases, updates, support and consent records the controller is Pavlov Yevhenii Andriiovych, an individual entrepreneur of Ukraine trading as Roxensoft, taxpayer number 3704911519. Privacy contact: rox.techlead@gmail.com. Full address, recipients, international safeguards and complaint rights are in the general Privacy Policy. Acknowledgement of this notice is distinct from consent to optional marketing or tracking. Necessary licensing uses contract or applicable legitimate interests; security and fraud prevention rely on proportionate legitimate interests and legal duties. Accounting records follow applicable legal obligations. Optional consent is obtained separately where required.
2. Local data and user-selected hosts
Host profiles, saved credentials, notes, command history, aliases, automation and settings are primarily stored on the device. Protected workspace and identity material use protection bound to the OS account. PIN locking adds an access control; it does not replace a secure operating system. Active sessions, decrypted data and terminal output must exist in memory. OS compromise, administrator access, screenshots, clipboard histories, exports and remote endpoints prevent any absolute encryption guarantee. SSH and file transfers connect to hosts you select, including bastions. Ordinary licensing and update requests do not send SSH passwords, private keys, command text, workspace contents or terminal transcripts to Roxensoft. Review and redact reports or exports you choose to share with support.
3. Service requests and legal records
Licensing requests contain a random installation ID, installation public key, product, platform, application version, a device fingerprint, request timestamp and nonce. The activation key is sent only for activation. These identifiers may be personal data when linkable and are not described as anonymous. Purchase and delivery services separately process contact, order, payment status and entitlement records. Update and document delivery receive requested product/version/platform and transport information such as IP address and time; hosting/security logs may contain that metadata. Signed acceptance records contain installation binding, document versions and hashes, acceptance revision, device-declared acceptance time and a separate authoritative server receipt time. Offline acceptance is queued locally and sent at acceptance, a later launch or explicit retry. Device time is not represented as server time. Necessary service checks do not imply marketing consent. The desktop does not add advertising trackers or transmit commands for product analytics.
4. Recipients, retention and your choices
Access is limited to authorised personnel and necessary infrastructure, email, payment and professional service providers under the general Privacy Policy. International access requires applicable safeguards; no universal adequacy assumption is made. Ask for relevant recipient and safeguard details. Local data remains until you delete it; uninstalling program files may preserve it. Licensing, acceptance, recovery and fraud-prevention records are retained while needed to provide acquired rights, handle claims or meet legal duties, with periodic necessity review. Accounting records follow statutory periods. Encrypted backups follow the same access restrictions and controlled retention schedule; removal from backups may occur by expiry. You can request access, correction, deletion, restriction, objection or portability where applicable and complain to a competent supervisory authority. Identity is verified proportionately. We explain limits needed for legal obligations and purchased-right preservation. Optional consent can be withdrawn independently. Contact support before deleting an installation identity needed to recover encrypted data.