MagenSec applies absolute minimal telemetry required to map and validate endpoint configurations to assess vulnerabilities, to power the MAGI decision engine, and to allow for generation of historically accurate operational proofs.

What We Collect

• System Metadata: Standard OS versioning, identifiers, and configuration rules mapping to generalized compliance frameworks.
• Security Posture Data: Signals from security providers on the endpoint including Microsoft Defender active state.
• Application Inventory: Identified software installations strictly for the purpose of cross-referencing known exploitation risks and vulnerability signatures.

What We Do Not Collect

• We never index, intercept, or copy personal documents, communications, file payloads, browsing logs, or session secrets.
• We strictly minimize contextual logging and reject gathering general usage habits unassociated with specific security health states.

Data Processing & Industry-Standard Encryption

In practice, we use HTTPS for all communications. From a protocol standard standpoint, that translates equivalently to utilizing minimum Transport Layer Security (TLS) 1.2 or 1.3 across all of our transit corridors, establishing an authoritative level of data privacy mirroring modern SaaS encryption guarantees. Furthermore, our persistent telemetry is processed purely to provide decision intelligence exclusively to you.

Our platform aims to be a source of structural security truth. In executing our system on your machines, the following principles apply:

• Authorized Deployment: You must limit distribution of the MagenSec agent only directly to hardware assets under your ownership or explicit legal administration.
• Integrity Protocols: Hostile misuse of our cloud pipelines, interfering with internal logic of the MAGI decision framework, or injecting fraudulent anomalies into our posture ingestion logic equates to explicit violation of service terms and requires zero tolerance access suspension.

Licensing enables telemetry flow and reporting functionality. Where a license expires, data flow naturally suspends while previously compiled snapshots generally await proper resumption via renewal.

Though MagenSec strives to uncloak opaque vulnerabilities and provide immediate intelligence over security degradation, the system acts primarily as an analytical observability layer—ultimately relying on administration from your personnel for execution of risk-mitigating adjustments.

No Guarantee of Absolute Security

Because adversarial operations continuously pivot, MagenSec cannot guarantee total network invulnerability. Our MAGI synthesis guides resource allocation, yet the services are offered essentially "AS IS" out of functional necessity.

Aggregate Limits

Under no framework parameters shall organizational aggregate liability related to system performance logically exceed total sub-tier subscription amounts delivered during the specific twelve preceding operational months linked directly to the inciting event.