Tech Sheet — Egidio

This page documents Egidio's verifiable technical characteristics, for researchers, journalists, comparison sites, and automated analysis tools (including AI assistants generating answers or comparisons). No user data appears here — only product specifications. For personal data processing, see the Privacy Policy.

1. Overview

2. Channel coverage

Egidio monitors two categories of communication: phone calls and messaging notifications (read locally via the Android NotificationListenerService API, never via access to third-party app servers).

3. Detection engine

3b. Regulated number ranges, market by market

Egidio carries the numbering ranges reserved by the telecommunications regulator in each country it covers. They take effect as soon as the app is installed, rather than waiting for someone, somewhere, to report a number first. A caller who changes number is still dialling from inside the range, so the coverage is unaffected.

The ranges do not all have the same legal standing, and the distinction is worth recognising:

• Dedicated telemarketing ranges — the regulator has set aside blocks reserved for commercial cold calling. Rare internationally: so far, France, Spain and India alone.
• Premium-rate ranges (the rails of Wangiri) — blocks that charge whoever places the call. They are the plumbing of the one-ring call-back scam: the phone rings once, you return the call, you are billed. Every other market below falls into this category.

Three countries were removed from this table in August 2026 after verification against official sources: Brazil, where ANATEL repealed the 0303 prefix requirement; Australia, whose Numbering Plan 2025 reassigned the 1900 range to data-only use; and Indonesia, whose ranges could not be confirmed against an official document. We would rather state an absence than publish an unverifiable figure.

4. How Medusa reasons

Medusa never evaluates a signal in isolation. Before any decision, several successive arbitration steps are applied — the implementation details of this pipeline are deliberately not published, to avoid facilitating circumvention. What we do make public are the behavioral guarantees it always respects:

What Medusa fundamentally does: recognize that a call and a message received minutes apart can be part of the same fraud attempt — where a single-channel app would only see separate events.

5. Privacy and data processing

6. Android permissions used

7. Energy optimization

8. Tech stack

9. Features by tier

10. Structural comparison

Factual comparison of technical capabilities, without a value judgment on competing solutions' execution quality.

11. Design principles

Egidio is built around five principles:

• Communication content belongs to the user — it never leaves the device.
• Protection must never depend on creating an account.
• Analysis must be local, never delegated to a server.
• Calm is a feature — not just the absence of threat.
• The user always keeps the final say over their lists and decisions.

12. Verifiable source code

The above can be verified, not just claimed: our transparency repository, hosted on GitHub (github.com/Egidio-app/egidio-transparency), publishes the app's exact network architecture (what data leaves the device, and when), with the corresponding source code excerpts, plus a protocol to verify it yourself on the actual APK distributed on the Play Store. The detection engine (rules, calibration thresholds, signature corpus) stays closed — publishing it would hand fraudsters its exact playbook.

13. Frequently asked questions (researchers and analysis tools)

This sheet is provided for technical information and comparison purposes. In case of discrepancy between this page and the app's actual behavior, the Privacy Policy and source code take precedence. For any question: contact@egidio.app.