Explain the protection clearly. Explain the limits clearly too.

Protection scope

• MobileXeroz baseline protection operates at the DNS-layer domain filtering level.
• It helps stop access to known malicious or suspicious destinations before connection completes.
• The service is positioned as a low-overhead model rather than a heavy always-on security stack.
• DNS-layer controls reduce exposure, but they do not guarantee prevention of every threat category.

Onboarding by platform

• Android uses a Private DNS settings-based onboarding path.
• iPhone uses a profile-based DNS onboarding path with operating-system consent prompts.
• Both flows are one-time guided setup experiences and may require user confirmation screens.

Threat intelligence inputs

Threat decisions are generated from internally curated intelligence and selected third-party signals. Source mixes can evolve as quality and detection efficacy are reviewed. Specific provider names may be withheld for abuse resistance and commercial confidentiality.

MobileXtract boundaries

• Android supports a deeper scan and remediation workflow based on supported controls.
• iPhone follows an investigation-focused workflow with guided selective reset and post-reset verification.
• Platform differences are expected because mobile operating systems expose different security controls.

Evidence and reporting

MobileXtract can produce shareable incident reports with findings, timestamps, and remediation notes. These can support internal review, support escalation, and formal reporting workflows. Final evidentiary acceptance depends on authority procedures, chain-of-custody requirements, and case context.

Operational data retention

• RealmChannel retains minimal operational metadata needed for service reliability, billing support, abuse prevention, and onboarding troubleshooting.
• Sensitive content inspection is not the baseline model for DNS-layer protection.
• Retention windows are governed by policy and can vary by legal, fraud, and support requirements.