Privacy Policy

1. Introduction and Scope

Datawiser LLC ("we", "us", "our"), a limited liability company organized under the laws of Utah, USA, provides the Argus platform as a specialized monitoring environment for AI training loops. This Privacy Policy describes our practices regarding the collection, processing, and protection of information when you interact with our SDK, API, and web interface.

By utilizing any component of the Argus Protocol, you expressly consent to the processing of your metadata as described herein. If you do not agree with any provision of this policy, you must terminate all authenticated sessions immediately.

2. The Metadata Firewall Protocol

The Argus architecture is built on the principle of "Zero-Visibility." We recognize that your model weights and proprietary datasets represent your most sensitive intellectual property. Our systems are physically and logically incapable of ingesting raw weight tensors or private training samples.

2.1 Telemetry Collection

We ingest only clinical training telemetry, which is defined as mathematical scalars and histograms generated by the Argus SDK during an active training loop. This includes:

• Objective Metrics: Loss scalars, learning rate schedules, and batch-level hyperparameters.
• Optimization Signals: L2-norm gradient vectors and distributional stability markers.
• Infrastructure Metadata: Instance IDs from cloud providers (AWS, GCP, Azure), GPU utilization percentages, and network latency signatures.
• Ingress Security Logs: IP addresses and browser fingerprints collected during authenticated handshakes for the sole purpose of rate-limiting and anti-abuse detection.

2.2 Sanitization Gate

All incoming pulses are passed through our Python-based Data Acceptor. This layer performs an automated forensic sweep to identify and purge any unapproved metadata keys or potential personally identifiable information (PII) before the data is committed to the Metadata Vault.

3. Use of Information

We utilize the collected metadata for strictly operational and forensic purposes, including:

• Forensic Analysis: Delivering deterministic failure detection and "step-reconstruction" reports to your dashboard.
• Autonomous Interventions: Enabling the mode="AUTO" fail-safe logic to halt training runs when anomalous divergence is detected.
• Security & Ingress: Validating the cryptographic integrity of your authenticated handshakes and preventing unauthorized API access.
• Service Optimization: Improving the accuracy of our failure detection models using aggregated, anonymized signal histograms.

Note: We do not utilize IP addresses for user tracking or profiling. Ingress IP data is purged systematically according to our security rotation protocols.

4. Transactional Communications (AWS SES)

Under the Argus Security Protocol, certain communications are deemed "Mission Critical" and cannot be disabled while a training run is active. We utilize the AWS Simple Email Service (SES) to deliver these transactional handshake pulses.

Transactional communications include: (a) handshaking and session verification, (b) security-critical alerts such as API key rotations or unauthorized ingress attempts, and (c) autonomous intervention reports confirming the engine has fired a fail-safe trigger.

5. Legal Basis and Data Processing (GDPR/CCPA)

Datawiser LLC processes personal data on the following legal bases: (i) performance of our contract with you; (ii) compliance with our legal obligations; and (iii) our legitimate interests in providing a secure and reliable monitoring platform.

5.1 International Transfers

Data is stored and processed exclusively in AWS US-EAST-1 (N. Virginia) regions. For users in the European Union, we rely on Standard Contractual Clauses (SCCs) to ensure equivalent levels of data protection for all international transfers.

5.2 Right to Erasure

You retain the right to request the deletion of your telemetry buffers at any time. Upon deactivation of your institutional account, all metadata not required for billing or legal compliance will be purged within 90 days.

6. Contact and Inquiries

All legal and privacy escalations must be directed to our secure compliance terminal. We prioritize institutional security requests with a 24-hour forensic response window.