Security telemetry without content surveillance.

Security metadata, not personal content.

The telemetry model covers application fingerprints, contacted network domains, accessible system events and patch status — the technical signals needed to assess endpoint security posture.

In telemetry, the device is associated with a pseudonym rather than a named personal identity.

App fingerprints

Identify installed software and technical changes.

Contacted domains

Find trackers and suspicious network destinations.

System events

Understand unusual behaviour and security signals.

Update status

Assess the device’s security update posture.

Your conversations stay yours.

Automatic collection excludes messages, email, photos, contacts, call logs and location. A suspicious link or message is assessed only when you choose to submit it to the adviser.

The handling of anything you submit voluntarily must be explained in the service before that feature is used.

No automatic collection of messages, email, photos, contacts, call logs or location.

Bounded retention and cryptographic separation.

The application telemetry design discards IP addresses and imposes a 30-day lifetime on raw security events, limiting the accumulation of sensitive technical histories.

Cryptographic signatures protect updates and rules. The authorising signing key is kept offline, separate from the distribution system.

Consent includes a way out.

The initial setup and required permissions are explained before activation. Deactivation and removal depend on the Android management policies configured on a particular device.

Compatibility must therefore be checked before installation.

This website does not follow you.

archangelus.dev is made of static files. There is no JavaScript, web form, cookie, behavioural analytics, database or externally loaded resource.

Choosing to email us opens your own email client. That action happens outside the website.