COSMO Privacy & Permissions:
What You Need to Know
Understanding the reported privacy implications of COSMO's screen reading, on-device AI, and autonomous action capabilities.
COSMO AI Privacy Controls
Actual screenshots from the COSMO AI settings panel showing the granular privacy and permission controls available to users.
AccessibilityService and Screen Reading
One of COSMO's most notable reported features is its use of Android's AccessibilityService — a powerful system API originally designed to assist users with disabilities. When granted by the user, this permission allows COSMO to:
- Read text and content displayed on screen from any app
- Detect UI elements, buttons, and interactive components
- Monitor user interactions and navigation patterns
- Provide contextual suggestions based on current screen content
This level of access is what enables COSMO's proactive, context-aware behavior — but it also means COSMO could potentially observe sensitive information such as messages, financial data, and passwords displayed on screen.
On-Device vs. Cloud Processing
The inclusion of Gemini Nano suggests that COSMO processes much of its data locally, which has significant privacy benefits:
✅ Privacy Benefits
- Screen data processed locally
- No mandatory cloud upload of personal content
- Reduced attack surface for data breaches
- Works offline — data stays on device
⚠️ Privacy Concerns
- Some features require cloud processing
- Recall stores persistent personal data
- Unclear how long data is retained
- No documented opt-out mechanisms yet
Permission Requirements
Based on the reported feature set, COSMO would likely require the following Android permissions:
| Permission | Purpose | Sensitivity |
|---|---|---|
| AccessibilityService | Screen reading and context awareness | 🔴 High |
| Internet | Cloud AI, Deep Research, Browser Agent | 🟡 Medium |
| Calendar | Calendar Event Suggester skill | 🟡 Medium |
| Camera | Quick Photo Lookup skill | 🟡 Medium |
| Storage | Document Writer and Recall data | 🟡 Medium |
| Notifications | Proactive suggestions and alerts | 🟢 Low |
Key Privacy Questions
Since Google has not officially documented COSMO's privacy model, several important questions remain unanswered:
- What data does COSMO's Recall feature store, and for how long?
- Can users selectively disable screen reading for specific apps?
- What data is sent to Google's cloud servers vs. processed locally?
- How does COSMO handle sensitive information like passwords or banking data?
- Can users export or delete all COSMO-collected data?
Our Recommendation
Until Google provides official documentation on COSMO's privacy practices, users should exercise caution. If COSMO becomes publicly available, carefully review all permission requests and understand what data access you are granting before enabling features like screen reading and Recall.
📚 Sources
- Android Authority — AccessibilityService and permission reporting
- 9to5Google — COSMO feature and data access analysis
- Android Developer Documentation — AccessibilityService API capabilities