Why Verify Yourself?
In the digital age, trust must be earned, not assumed. While we provide transparency documentation, we believe users should have the knowledge and tools to verify our claims independently.
What You'll Learn
- How to verify the APK signature and authenticity
- How to monitor network traffic to ensure no data leaks
- How to decompile and inspect the app's actual code
- How to analyze permissions and security configurations
- How to detect malicious behavior patterns
This guide is structured in three levels: Basic for everyday users, Intermediate for tech-savvy individuals, and Advanced for security professionals and developers.
Level 1: Basic Verification EASY
No technical knowledge required. These checks can be performed by anyone in under 10 minutes.
1 Verify Official Download Source
Why: Ensure you're installing the genuine Aido app, not a malicious clone.
How to verify:
- Only download Aido from the Google Play Store or our official GitHub releases page
- Check the developer name: Rubex
- Verify the package name:
com.rr.aido - Cross-reference with our website: myaido.web.app
2 Check App Permissions
Why: Verify that Aido only requests necessary permissions and nothing suspicious.
How to verify:
- Go to Settings → Apps → Aido → Permissions
- Review each permission and compare with our Permissions Deep Dive page
- Ensure no unexpected permissions are requested (e.g., Camera, Microphone, SMS)
3 Test Network Activity (Simple Method)
Why: Verify that Aido doesn't send your data to unknown servers.
How to verify:
- Enable Airplane Mode on your device
- Open Aido and use core features (text shortcuts, clipboard manager, utility commands)
- Observe that all features work perfectly without internet
- Disable Airplane Mode and check if Aido requests network access for basic operations
4 Review Privacy Policy & Transparency Pages
Why: Understand what data Aido collects and how it's used.
How to verify:
- Read our Privacy Policy
- Review our Zero Tolerance List
- Check our Data Processing documentation
5 Test Offline Functionality
Why: If an app works perfectly without internet, it can't be secretly sending your data.
How to verify:
- Turn on Airplane Mode
- Test all core features:
- Type text shortcuts (e.g., "@em" for email)
- Use clipboard manager
- Try utility commands (.date, .reverse, etc.)
- Test font library
- Verify everything works smoothly without any errors
6 Check Play Store Reviews & Ratings
Why: Real user experiences reveal the truth about an app's behavior.
How to verify:
- Read recent reviews on Google Play Store
- Look for privacy-related complaints or data concerns
- Check if users report unexpected behavior
- Note the developer's responses to negative reviews
7 Observe Battery & Data Usage
Why: Suspicious apps drain battery with background activities and consume data secretly.
How to verify:
- Go to Settings → Battery → Battery Usage
- Check Aido's battery consumption (should be minimal)
- Go to Settings → Network & Internet → Data Usage
- Check Aido's data usage (should be near zero if you don't use online AI)
8 Verify No Ads or Trackers
Why: Apps with ads always track you. Ad-free apps are inherently more private.
How to verify:
- Use Aido for a week and observe: Do you see any ads?
- Check if there's any "Ad settings" or "Personalized ads" option
- Look for tracking prompts or consent dialogs
Pre-Installation Checks EASY
Verify safety BEFORE installing the app.
9 Check Play Store Data Safety Section
Why: Google requires developers to declare data collection transparently.
How to verify:
- Open Aido's Play Store page
- Scroll to "Data safety" section
- Check what data is collected and shared
- Verify our claims: "No data shared with third parties"
10 Research the Developer
Why: Trustworthy developers have public presence and accountability.
How to verify:
- Search for "Aido app" and "Rubex developer" online
- Check our official website: myaido.web.app
- Look for social media presence, GitHub activity, community engagement
- Check if other users are discussing the app on Reddit, Twitter, forums
11 Compare Permissions with Similar Apps
Why: Excessive permissions compared to competitors is a red flag.
How to verify:
- Find similar keyboard/clipboard apps on Play Store
- Compare their permissions with Aido's
- Aido should request similar or fewer permissions
Behavioral Observation EASY
Monitor app behavior during daily usage to spot abnormalities.
12 Verify No Automatic Background Execution
Why: Malicious apps run in background without permission to spy or steal data.
How to verify:
- Go to Settings → Apps → Aido → Battery
- Check "Background usage" - should show minimal or zero usage
- Go to Settings → Developer Options → Running Services
- Close all apps and wait 10 minutes
- Check if Aido appears in running services (it shouldn't!)
- Restart your phone and check battery stats after 1 hour
- Aido should NOT appear in battery usage if you haven't used it
13 Verify Banking & SMS Protection
Why: Verify that Aido cannot access or steal banking info, SMS, passwords, or OTPs.
How to verify:
- Test Banking Apps:
- Open your banking app (PhonePe, Paytm, Google Pay, etc.)
- Try using Aido features - they should be DISABLED automatically
- Try typing shortcuts in password/PIN fields - they WON'T work (good!)
- Aido should not interfere with UPI transactions
- Test SMS Access:
- Go to Settings → Apps → Aido → Permissions
- Verify: SMS permission should be NOT GRANTED
- Aido should NEVER request SMS permission
- Test Password Fields:
- Open any app with password/PIN input
- Aido's shortcuts should NOT work in these fields
- Clipboard manager should NOT capture passwords
- Test OTP Fields:
- Receive an OTP via SMS
- Type it manually - Aido should NOT interfere
- OTP should NOT appear in clipboard history
- No SMS permission granted (ever!)
- Banking apps work normally without Aido interference
- Passwords, PINs, and OTPs are never captured
- Aido automatically disables itself in sensitive apps
14 Verify No Auto-Start After Reboot
Why: Malicious apps auto-start after reboot to run in background without your knowledge.
How to verify:
- Check current permissions: Settings → Apps → Aido → Permissions
- Verify "Autostart" or "Run at startup" is DISABLED
- Actual Test:
- Note Aido is NOT currently running (close all apps)
- Restart your phone completely
- After restart, check Settings → Apps → Running Services
- Aido should NOT be in the list
- Open Recent Apps menu - Aido should not appear unless you opened it
15 Check for Unexpected Notifications
Why: Spammy notifications often indicate data-hungry apps.
How to verify:
- Use Aido for several days
- Check if you receive promotional notifications
- Look for requests to enable additional permissions
- Watch for "rate us" spam or intrusive popups
16 Test Contact & Call Log Access
Why: Verify Aido cannot steal your contacts, call history, or phone records.
How to verify:
- Go to Settings → Apps → Aido → Permissions
- Check these permissions are NOT GRANTED:
- Contacts
- Phone (Call logs)
- Call history
- SMS/MMS
- Aido should NEVER request these permissions
- If prompted, deny and verify app still works normally
17 Verify Camera & Microphone Protection
Why: Ensure Aido cannot record audio, take photos, or spy through camera/microphone.
How to verify:
- Go to Settings → Apps → Aido → Permissions
- Verify these are NOT GRANTED:
- Camera
- Microphone
- Check Settings → Privacy → Camera Access - Aido should not be listed
- Check Settings → Privacy → Microphone Access - Aido should not be listed
18 Verify App Size & Updates
Why: Sudden large app size increases can indicate added tracking libraries.
How to verify:
- Note Aido's current app size in Settings → Apps
- After updates, check if size changes significantly
- Read update changelogs to understand changes
- Large size increases without clear feature additions = suspicious
Community-Based Verification EASY
Leverage collective intelligence to verify trustworthiness.
19 Check VirusTotal Scan
Why: VirusTotal scans APKs with 70+ antivirus engines.
How to verify:
- Visit VirusTotal.com
- Search for
com.rr.aidoor upload the APK - Review scan results from multiple security vendors
- Check detection ratio (should be 0/70+)
20 Search for Security Research
Why: Security researchers publicly expose malicious apps.
How to verify:
- Google: "Aido app security vulnerability"
- Search Twitter for: "Aido app privacy concern"
- Check security forums and Reddit for discussions
- Look for independent security audits or reports
21 Join User Communities
Why: Real users share genuine experiences and concerns.
How to verify:
- Join Aido's user communities (Discord, Telegram, Reddit)
- Ask existing users about their privacy experiences
- Check if anyone has reported data breaches or privacy violations
- Observe developer responsiveness to concerns
Level 2: Intermediate Verification MEDIUM
Requires basic technical knowledge and tools. Recommended for tech-savvy users who want deeper insights.
22 Verify APK Signature
Why: Confirm that the APK hasn't been tampered with and is genuinely from us.
Required Tools:
How to verify:
- Extract the APK file from your device using:
adb pull $(adb shell pm path com.rr.aido | cut -d: -f2) aido.apk
- Verify the signature using jarsigner:
jarsigner -verify -verbose -certs aido.apk
- Check the certificate fingerprint:
keytool -printcert -jarfile aido.apk
23 Monitor Network Traffic
Why: Capture and analyze all network requests to ensure no unauthorized data transmission.
Required Tools:
How to verify:
- Install HTTP Toolkit or Charles Proxy on your computer
- Configure your Android device to use it as a proxy
- Install the SSL certificate on your device (for HTTPS inspection)
- Use Aido normally for 10-15 minutes, testing various features
- Review all network requests in the proxy tool
- No requests when using offline features
- Only requests to known AI APIs when using online AI features
- No analytics tracking or telemetry
- No requests to ad networks or data brokers
24 Analyze Manifest File
Why: The AndroidManifest.xml contains all permissions, services, and components. Inspecting it reveals what the app CAN do.
Required Tools:
How to verify:
- Decompile the APK using Apktool:
apktool d aido.apk
- Open
AndroidManifest.xmland review:- Permissions: Should match our documentation
- Services: Look for background services
- Receivers: Check for broadcast receivers
- Activities: Verify app entry points
25 Check Storage & Data Files
Why: Verify what data Aido stores locally and ensure nothing is being collected secretly.
How to verify:
- Using ADB, browse Aido's data directory:
adb shell
run-as com.rr.aido
ls -la - Check for databases, shared preferences, and cache files
- Use
sqlite3to inspect database contents:sqlite3 databases/aido.db
.tables
.schema
Level 3: Advanced Verification ADVANCED
For security researchers and developers. Requires programming knowledge and deep technical understanding.
26 Decompile & Inspect Source Code
Why: The ultimate verification—reading the actual code to see what the app does.
Required Tools:
How to verify:
- Decompile the APK using JADX:
jadx -d output_folder aido.apk
- Open the decompiled code in an IDE (IntelliJ IDEA recommended)
- Search for suspicious patterns:
grep -r "analytics" .
grep -r "tracking" .
grep -r "telemetry" .
grep -r "URLConnection" .
grep -r "HttpClient" . - Review key files:
AidoAccessibilityService.kt- Accessibility logicClipboardManager.kt- Clipboard handlingNetworkModule.kt- Network requestsUtilityCommandProcessor.kt- Command processing
27 Static Analysis with Security Tools
Why: Automated tools can detect vulnerabilities and suspicious code patterns faster than manual review.
Required Tools:
How to verify:
- Install Mobile Security Framework (MobSF):
docker pull opensecurity/mobile-security-framework-mobsf
docker run -it -p 8000:8000 opensecurity/mobile-security-framework-mobsf - Upload the Aido APK to MobSF at
http://localhost:8000 - Review the automated security report for:
- Hardcoded secrets or API keys
- Insecure data storage
- Weak cryptography
- Privacy violations
28 Dynamic Runtime Analysis
Why: Monitor actual app behavior at runtime to catch anything static analysis misses.
Required Tools:
How to verify:
- Install Frida on your rooted device or emulator
- Hook into Aido's process:
frida -U -f com.rr.aido
- Inject monitoring scripts to track:
- File read/write operations
- Network socket connections
- Clipboard access
- Process spawning
- Example Frida script to monitor network:
Java.perform(function() {
var URL = Java.use("java.net.URL");
URL.openConnection.implementation = function() {
console.log("Network request: " + this.toString());
return this.openConnection();
};
});
29 Binary Analysis (Native Code)
Why: If Aido includes native libraries (.so files), they need inspection too.
Required Tools:
How to verify:
- Extract native libraries from the APK:
unzip aido.apk -d extracted
find extracted/lib -name "*.so" - Load each .so file into Ghidra for disassembly
- Look for suspicious function calls:
- Socket operations
- File operations
- Encryption/decryption
30 Traffic Decryption & SSL Pinning Check
Why: Verify that HTTPS traffic isn't hiding secret data transmission.
Required Tools:
How to verify:
- Set up Burp Suite as a proxy with SSL interception
- If SSL pinning is implemented, bypass it using:
frida --codeshare pcipolloni/universal-android-ssl-pinning-bypass-with-frida -U -f com.rr.aido
- Intercept and decrypt all HTTPS traffic
- Verify request payloads and response data
Required Tools & Resources
Here's a complete list of tools you'll need for different verification levels.
- Android Settings - Built into your device
- Web Browser - To read our transparency documentation
- Play Store - For official app downloads
- ADB (Android Debug Bridge) - Download
- HTTP Toolkit - httptoolkit.com
- Charles Proxy - charlesproxy.com
- Apktool - Download
- JDK (Java Development Kit) - oracle.com/java
- JADX - github.com/skylot/jadx
- MobSF (Mobile Security Framework) - github.com/MobSF
- Frida - frida.re
- Ghidra - ghidra-sre.org
- Burp Suite - portswigger.net/burp
- objection - github.com/sensepost/objection
If you find discrepancies between our claims and actual behavior, we want to know. Contact us at: aiqknow@gmail.com
Responsible Disclosure
Security researchers: If you discover vulnerabilities during your audit, we encourage responsible disclosure.
How to Report
- Email us at: aiqknow@gmail.com
- Include detailed steps to reproduce the issue
- Allow us 90 days to patch before public disclosure
- Get acknowledged in our Hall of Fame (optional)
We do not currently offer a bug bounty program, but we deeply appreciate security research and will publicly acknowledge your contribution (with your permission).