At AJA RETRO, we are committed to maintaining the highest standards of transparency regarding the telemetry and data processing required to secure your server environments. This Privacy Policy details how we collect, handle, and store technical logs generated by the Software.
Data Transparency Notice
The Software operates as a JVM-level boot agent and must transmit minimal operational telemetry to function. Your server IP, port, and threat logs are transmitted exclusively to license.ajaretro.dev — your private, isolated dashboard environment.
1. Data Collection and Operational Telemetry
To deliver live threat intelligence updates and execute dashboard metrics, the Software collects the following specialized technical data:
Licensing Telemetry: The public IPv4/IPv6 address, CIDR subnet block, and runtime port of the hosting machine are securely transmitted to our validation network to confirm active commercial registration.
Threat and Security Logs: When a threat vector is intercepted, the Software aggregates data detailing the event — including the offending plugin package prefix, specific class name, target system call, and unauthorized outbound socket destination. This data is transmitted to your private Threat Sentinel Web Dashboard.
Hardware Performance Telemetry: Basic performance metrics (such as thread execution delays, memory consumption changes, and system garbage collection pauses) are compiled to facilitate lag culling via the dashboard interface.
2. Third-Party Integrations and Data Processing
Gemini AI Threat Audits: Semantic threat analysis tools utilize the Gemini API. Outbound network activities and suspicious bytecode anomalies are processed using the API credentials provided directly by the user. AJA RETRO does not control, store, or view the data payloads routed through the user's individual AI API keys.
Merchant of Record (Paddle / NOWPayments): Financial transactions, commercial billing cycles, and invoice processing are securely managed by our designated payment processors. AJA RETRO does not collect, log, or store sensitive financial identifiers, credit card credentials, or raw banking profiles. All payment metadata is handled under the respective payment processor's privacy framework.
3. Data Protection, Security, and Retention
Data Control: Server network logs and threat captures are the exclusive property of the administrator. Users maintain absolute rights to flush, download, or permanently purge event historical data directly from the web panel dashboard at any time.
Data Sharing: We do not engage in the sale, lease, or commercial distribution of your infrastructure network data, security threat profiles, or operational metrics to any third-party marketing networks or external entities.
Retention Period: Threat logs and network telemetry are retained for up to 90 days from the date of capture unless manually purged by the license owner via the dashboard.