RAKSHABYTE / features
Explore the six areas of the RakshaByte Android dashboard. Setup, permissions and connectivity determine which checks are available on your device.
Set RakshaByte as your Android caller ID and spam app. Contacts permission supports saved callers. Optional blocking covers reported numbers and strong cached spam evidence; saved contacts and unrecognized numbers are allowed. First-time callers may ring while reputation is checked.
Enable notification access in Android to check supported message notifications. Coverage depends on the text exposed by your apps and Android settings. AI message validation is optional and off by default. Enabling it sends notification text to RakshaByte and its AI provider; masking may leave personal information. Local checks remain available when AI is unavailable.
Turn on Web Shield and select RakshaByte in Android default browser settings. Suspicious links show a warning first. Links opened directly within another browser or app may bypass these checks. A link without a warning is not a guarantee of safety.
Installed-app analysis stays on the phone. App Monitor reviews Android-visible apps and readable security settings, including overlay and accessibility access. Automatic install scans use an ongoing notification. Android can limit app visibility and delay background scans. Risk signals do not prove malware or remote control.
Select a file in the Android app to inspect available metadata and local risk signals. A warning is a reason to review, not proof of malware. No local warning found does not guarantee safety. The captured green result used a harmless text file and does not demonstrate malware detection.
Use History to revisit recorded security activity and available assessment details. Safety Tips provides curated guidance, such as verifying urgent requests through a known number or a second trusted channel. It is not a live global threat feed. Screen-capture awareness applies only while RakshaByte is open.
Real Android emulator captures from 17 October 2026. Captured debug-session settings and service availability are examples.