Privacy Policy

A degoogled phone is a smartphone that has had all Google services, applications, and tracking mechanisms removed or replaced with privacy-focused alternatives. This includes removing Google Play Services, Google Play Store, Gmail, Google Maps, Chrome browser, and other Google applications that typically collect user data and send it to Google's servers.

The process of degoogling involves:

• Installing a custom Android-based operating system (ROM)
• Removing or disabling Google Mobile Services (GMS)
• Replacing Google apps with open-source alternatives
• Using alternative app stores like F-Droid or Aurora Store
• Configuring privacy-focused settings and services

FOSS stands for "Free and Open Source Software." In the context of phones, FOSS refers to mobile operating systems and applications whose source code is freely available for anyone to view, modify, and distribute. This transparency allows security researchers and developers to audit the code for privacy issues, backdoors, or vulnerabilities.

Key characteristics of FOSS phone software:

• Transparency: Source code is publicly available
• Community-driven: Developed by volunteers and privacy advocates
• No licensing fees: Free to use and distribute
• Customizable: Can be modified to meet specific needs
• Privacy-focused: No built-in tracking or data collection

Stock Android refers to the standard version of Android that comes with Google services integrated. Degoogled Android removes these Google components:

AOSP (Android Open Source Project) is the open-source version of Android maintained by Google. It provides the basic Android operating system without Google's proprietary services and applications. AOSP serves as the foundation for most degoogled Android distributions.

AOSP includes:

• Core Android operating system
• Basic system applications (dialer, messages, camera)
• Android runtime and framework
• Linux kernel and device drivers

AOSP does NOT include:

• Google Play Services
• Google Play Store
• Gmail, Chrome, Maps, or other Google apps
• Google's proprietary APIs and services

Custom ROMs are modified versions of Android that replace the manufacturer's original firmware. ROM stands for "Read-Only Memory," though modern ROMs can be updated. Custom ROMs for privacy often focus on removing Google services, enhancing security, and providing more user control.

Popular privacy-focused custom ROMs include:

• GrapheneOS: Maximum security and privacy (Pixel devices only)
• CalyxOS: Privacy-focused with user-friendly features
• LineageOS: Clean Android experience with wide device support
• e/OS: Complete Google ecosystem replacement
• DivestOS: Security-hardened LineageOS fork (discontinued 2024)

microG is an open-source implementation of Google Play Services that provides compatibility for apps that depend on Google services without actually connecting to Google's servers (in most cases). It allows many Google-dependent apps to function on degoogled phones.

microG provides:

• Push notification support (Firebase Cloud Messaging)
• Location services using alternative providers
• Google account authentication (optional)
• Maps API compatibility
• In-app purchase API (limited functionality)

Tip: microG requires signature spoofing to work properly, which some ROMs support natively while others require additional setup.

Degoogled phones provide significantly enhanced privacy compared to standard Android or iOS devices:

Data Collection Eliminated:

• No automatic location tracking and sharing
• No app usage analytics sent to Google/Apple
• No contact and calendar synchronization without consent
• No voice recordings uploaded to cloud services
• No automatic photo backup and analysis

Network Traffic Reduced:

• Studies show 50-90% reduction in network connections to tracking servers
• No constant "phone home" connections to Google/Apple servers
• DNS queries not automatically logged by big tech companies

Important: Privacy protection depends on your usage patterns. Installing apps with invasive permissions or using services that require Google accounts can reduce privacy benefits.

Security depends on the specific implementation and maintenance of the degoogled ROM:

Potential Security Advantages:

• Reduced attack surface by removing unnecessary services
• Some ROMs (like GrapheneOS) include additional security hardening
• No backdoors or undisclosed data collection mechanisms
• User has more control over permissions and network access

Potential Security Challenges:

• Delayed security updates if ROM development is slow
• Bootloader unlocking required for installation reduces hardware security
• Some security features may be disabled (SafetyNet, hardware attestation)
• Smaller development teams may miss vulnerabilities

Best Practice: Choose well-maintained ROMs with regular security updates like GrapheneOS, LineageOS, /e/OS for optimal security.

While degoogled phones significantly improve privacy, some risks remain:

Network-Level Tracking:

• ISP and carrier tracking of internet activity
• Cell tower location tracking
• Wi-Fi network logging and tracking

Hardware-Level Concerns:

• Baseband processor (cellular modem) runs proprietary firmware
• Some hardware components may have undisclosed capabilities
• IMEI and other device identifiers remain trackable

Application-Level Risks:

• Third-party apps may contain trackers
• Web browsers can still be fingerprinted
• Apps requiring network access can collect data

Degoogled phones provide several protections against surveillance, though they're not a complete solution:

Protections Provided:

• No automatic cloud backup of messages, photos, or data
• Reduced cooperation surface for data requests to tech companies
• Local data storage with user-controlled encryption
• Ability to use anonymous communication apps and networks

Limitations:

• Cellular network metadata (location, contacts called) still accessible
• Physical device seizure can compromise data if not properly encrypted
• Sophisticated attacks (IMSI catchers, malware) remain possible
• Legal requirements may still compel disclosure of some information

Important: For high-risk situations, additional operational security (OPSEC) measures are necessary beyond just using a degoogled phone. 

Contact us for additional OPSEC requirements.

Degoogled phones typically offer robust encryption capabilities:

Full Device Encryption:

• AES-256 encryption for all stored data
• Hardware-backed encryption keys (on supported devices)
• Encrypted boot process on devices with verified boot

Additional Encryption Features:

• Encrypted messaging apps (Signal, Element, Briar)
• Encrypted file storage and backup solutions
• VPN and Tor support for network traffic encryption
• Encrypted password managers and secure notes apps

Advanced Features (GrapheneOS):

• Duress PIN to wipe device under coercion
• Auto-reboot for improved encryption security
• Hardware security module integration

GrapheneOS is a security and privacy-focused mobile OS based on AOSP, designed for Google Pixel devices. It's considered the most secure Android-based operating system available.

Key Features:

• Hardened security with advanced exploit mitigations
• Sandboxed Google Play Services (optional)
• Enhanced permission model with fine-grained controls
• Regular security updates (usually same-day)
• Hardware-based security verification
• Storage and contact scopes for improved privacy

Ideal for:

• Security professionals and researchers
• Privacy advocates with technical knowledge
• High-risk individuals (journalists, activists)
• Users who prioritize security over convenience

Limitations:

• Only supports Google Pixel devices
• Steeper learning curve for average users
• Some apps may not work without Play Services
• Limited customization options

As of August 2025, CalyxOS development has been paused indefinitely due to internal organizational issues and maintainer burnout. The project previously offered a good balance between privacy and usability.

CalyxOS Previously Offered:

• User-friendly degoogled experience
• Built-in VPN service (CalyxVPN)
• microG integration for app compatibility
• Support for Pixel, Fairphone, and some Motorola devices

Current Status:

• No new releases or security updates
• Existing installations continue to work but become less secure over time
• Community discussions about potential fork or revival

Recommendation: Users currently on CalyxOS should migrate to GrapheneOS, e/OS, or LineageOS for continued security updates.

e/OS, developed by the e Foundation and commercially supported by Murena, focuses on providing a complete ecosystem replacement for Google services.

Strengths:

• Most Google-like user experience among degoogled options
• Integrated cloud services (email, calendar, drive, office)
• Wide device support including Samsung, OnePlus, Fairphone
• User-friendly installer for supported devices
• App Lounge with privacy ratings
• Advanced Privacy dashboard with tracker blocking

Considerations:

• Based on LineageOS, so security updates can be slower
• Some proprietary components in the cloud services
• Requires trust in e Foundation's infrastructure
• Performance can be slower than other ROMs

Best for: Families and users wanting a complete Google replacement with minimal learning curve.

LineageOS remains a solid foundation for privacy-focused mobile computing, though it requires more manual configuration than other options.

Advantages:

• Widest device support (400+ devices)
• Clean AOSP experience without manufacturer modifications
• Regular security updates
• Strong community support and documentation
• Extends life of older devices
• Supports microG installation

Privacy Considerations:

• No Google services by default
• Some connections to Google for network time, connectivity check
• User must manually configure privacy settings
• Can install full Google Apps if desired

Setup for Privacy:

• Install without Google Apps (GApps)
• Use F-Droid and Aurora Store for applications
• Configure DNS to avoid Google (Quad9, Cloudflare)
• Install microG if app compatibility needed

Several other options exist for privacy-conscious users as listed below which requires advance level technical knowhow. We will soon be launching other options.

iodéOS:

• French-developed ROM with built-in ad and tracker blocking
• Based on LineageOS with additional privacy features
• Supports various Android devices

Ubuntu Touch:

• Linux-based mobile OS (not Android)
• Limited device support and app ecosystem
• True open-source alternative to Android

PostmarketOS:

• Alpine Linux-based mobile OS
• Experimental, suitable for technical users only
• Can run on various older devices

PureOS (Librem 5):

• Completely free/libre mobile OS
• Hardware kill switches for privacy
• Limited to specific hardware

Several categories of apps may have issues on degoogled phones without Google Play Services:

Apps That Typically Don't Work:

• Banking apps with SafetyNet: Many require Google's integrity checking
• Google Pay/Apple Pay: Contactless payments requiring hardware attestation
• Netflix (HD content): DRM verification issues
• Some streaming apps: Widevine L1 DRM requirements
• Corporate apps: MDM (Mobile Device Management) software
• Some games: Google Play Games integration

Apps with Limited Functionality:

• Maps apps: May lack turn-by-turn navigation without Google services
• Uber/Lyft: Location services may be less accurate
• Social media apps: Push notifications may not work
• Fitness apps: May not sync with Google Fit

Solution: Many issues can be resolved by installing microG or using sandboxed Google Play Services (GrapheneOS).

Security depends on the specific implementation and maintenance of the degoogled ROM:

Potential Security Advantages:

• Reduced attack surface by removing unnecessary services
• Some ROMs (like GrapheneOS) include additional security hardening
• No backdoors or undisclosed data collection mechanisms
• User has more control over permissions and network access

Potential Security Challenges:

• Delayed security updates if ROM development is slow
• Bootloader unlocking required for installation reduces hardware security
• Some security features may be disabled (SafetyNet, hardware attestation)
• Smaller development teams may miss vulnerabilities

Best Practice: Choose well-maintained ROMs with regular security updates like GrapheneOS, LineageOS, /e/OS for optimal security.

Banking app compatibility varies significantly depending on the ROM and bank:

GrapheneOS:

• Many banking apps work with sandboxed Google Play Services
• Passes basic SafetyNet integrity checks
• Some banks still block usage due to unlocked bootloader detection

Other ROMs (e/OS, LineageOS):

• Success varies by specific banking app
• microG may help with some apps
• Many users report mixed results

Workarounds:

• Use mobile banking websites instead of apps
• Keep a separate device with stock Android for banking
• Use banks known to have less restrictive apps
• Contact your bank to report compatibility issues

Banks with Better Compatibility:

• Many credit unions
• Some European banks
• Online-only banks (varies by region)

Important: Always test banking functionality before fully switching to a degoogled phone if mobile banking is critical for you.

Several app stores provide alternatives to Google Play Store:

F-Droid (Recommended):

• 100% open-source applications
• No tracking or advertising
• Apps compiled from source code
• Security-focused with reproducible builds
• Categories: Communication, Internet, Security, Games

Aurora Store:

• Anonymous access to Google Play Store apps
• No Google account required
• Downloads APKs directly from Google
• Useful for apps not available on F-Droid

App Lounge (e/OS):

• Curated selection with privacy ratings
• Combines F-Droid and Play Store apps
• Privacy score for each application
• Progressive Web Apps (PWA) support

Other Options:

• APKPure: Third-party Android app store
• Obtainium: Direct downloads from developers
• IzzyOnDroid: F-Droid repository with additional apps
• APK sideloading: Manual installation from APK files

Best Practice: Start with F-Droid for privacy-focused apps, use Aurora Store for specific Google Play apps you need, and only sideload APKs from trusted sources.

Here are excellent FOSS alternatives to popular proprietary applications:

Communication:

• Signal: WhatsApp alternative with superior privacy
• Element: Slack/Discord alternative using Matrix protocol
• Briar: Peer-to-peer messaging, works without internet
• K-9 Mail: Email client (becoming Thunderbird Mobile)

Maps & Navigation:

• OsmAnd: Full-featured offline maps
• Organic Maps: Simple, fast offline navigation
• Magic Earth: Turn-by-turn navigation with privacy focus

Social Media:

• Tusky: Mastodon client for decentralized social networking
• NewPipe: YouTube frontend without Google services
• Barinsta: Instagram alternative (discontinued, forks available)

Productivity:

• Nextcloud: Complete office suite and cloud storage
• LibreOffice Viewer: Document viewing and editing
• Simple Tools: Calculator, calendar, gallery, notes
• Markor: Markdown text editor

Security & Privacy:

• Bitwarden: Password manager
• Aegis: Two-factor authentication
• Orbot: Tor browser for Android
• NetGuard: No-root firewall

Media:

• VLC: Universal media player
• AntennaPod: Podcast player
• Simple Gallery: Photo and video gallery
• Open Camera: Camera app with manual controls

Multiple methods exist for installing apps on degoogled phones:

Method 1: F-Droid (Easiest for FOSS apps)

1. Download F-Droid APK from f-droid.org
2. Enable "Install unknown apps" in Settings > Security
3. Install F-Droid APK
4. Browse and install apps directly from F-Droid

Method 2: Aurora Store (For Google Play apps)

1. Install Aurora Store from F-Droid
2. Launch Aurora and use anonymous login
3. Search and download apps from Google Play
4. Apps install directly without Google account

Method 3: APK Sideloading

1. Download APK files from trusted sources
2. Verify APK signatures when possible
3. Enable installation from unknown sources
4. Install APK using file manager

Method 4: ADB (Advanced)

1. Enable Developer Options and USB Debugging
2. Connect phone to computer with ADB installed
3. Use command: adb install app.apk
4. Useful for apps blocked by Play Protect

Push notifications can work on degoogled phones but require different implementations:

With microG:

• Firebase Cloud Messaging (FCM) works for many apps
• Requires microG to be installed with signature spoofing
• Most popular apps will receive notifications
• Some notifications may be delayed compared to stock Android

With Sandboxed Google Play (GrapheneOS):

• Full FCM compatibility when Play Services are installed
• Notifications work the same as stock Android
• User controls what data Play Services can access

Without Google Services:

• Apps must implement their own notification system
• Many FOSS apps use alternative push services
• Some apps use polling (checking periodically)
• Matrix/Element has its own push notification system

Alternative Solutions:

• UnifiedPush: Decentralized push notification protocol
• Ntfy: Simple notification service
• App-specific solutions: Signal, Telegram, etc. handle their own

Tip: Check notification settings for each app and consider enabling "Background App Refresh" for critical applications.

Buying pre-installed saves time and reduces risk of installation errors, especially for less technical users. Also we make it easy for you as if you are buying another phone. Buy it and start using it.

Installation depends on your specific device model and manufacturer policies:

Requirements for Installation:

• Unlockable bootloader: Essential for installing custom ROMs
• Device support: ROM must be available for your specific model
• Technical knowledge: Basic understanding of Android systems
• Warranty void: Unlocking bootloader typically voids warranty

Manufacturers with Unlockable Bootloaders:

• Google Pixel: Officially supported unlocking
• OnePlus: Most models support unlocking
• Xiaomi: Unlocking possible but may require waiting period
• Fairphone: Designed to be user-repairable and modifiable
• Some Motorola models: Official unlock codes available

Manufacturers with Locked Bootloaders:

• Most Samsung devices: Bootloader locked in many regions
• Most Huawei/Honor: No longer provide unlock codes
• Most carrier-locked devices: Additional restrictions

Check Compatibility:

1. Find your exact device model number
2. Check ROM compatibility lists (LineageOS wiki, etc.)
3. Verify bootloader unlock availability
4. Read installation guides and requirements

Risk Warning: Installation can "brick" your device if done incorrectly. Always follow instructions carefully and ensure you have recovery options.

Initial setup is crucial for maximizing privacy and security:

Basic Security Setup:

1. Set strong screen lock: Use PIN, password, or biometric
2. Enable full disk encryption: Usually enabled by default
3. Configure automatic updates: Enable for security patches
4. Review privacy settings: Disable unnecessary data sharing
5. Set up auto-reboot: For improved security (if available)

Network Configuration:

• Configure DNS servers (Quad9, Cloudflare, or Pi-hole)
• Set up VPN if desired
• Disable location services or configure privacy-friendly alternatives
• Review connectivity check and network time settings

App Installation:

1. Install F-Droid for open-source apps
2. Install Aurora Store for Google Play apps (if needed)
3. Install essential privacy tools (Signal, VPN, password manager)
4. Install microG or sandboxed Play Services (if desired)
5. Configure app permissions carefully

Data and Backup:

• Set up Seedvault backup (if available)
• Configure cloud storage alternatives (Nextcloud)
• Import contacts from previous backup
• Set up secure email and calendar

Initial setup is crucial for maximizing privacy and security:

Basic Security Setup:

1. Set strong screen lock: Use PIN, password, or biometric
2. Enable full disk encryption: Usually enabled by default
3. Configure automatic updates: Enable for security patches
4. Review privacy settings: Disable unnecessary data sharing
5. Set up auto-reboot: For improved security (if available)

Network Configuration:

• Configure DNS servers (Quad9, Cloudflare, or Pi-hole)
• Set up VPN if desired
• Disable location services or configure privacy-friendly alternatives
• Review connectivity check and network time settings

App Installation:

1. Install F-Droid for open-source apps
2. Install Aurora Store for Google Play apps (if needed)
3. Install essential privacy tools (Signal, VPN, password manager)
4. Install microG or sandboxed Play Services (if desired)
5. Configure app permissions carefully

Data and Backup:

• Set up Seedvault backup (if available)
• Configure cloud storage alternatives (Nextcloud)
• Import contacts from previous backup
• Set up secure email and calendar

Important: Don't rush to install everything at once. Test core functionality first, then gradually add apps while monitoring privacy impact.

Daily use of degoogled phones varies significantly based on your setup and needs:

Typical Daily Experience:

• Basic functions work normally: Calls, texts, camera, web browsing
• App installation different: Use F-Droid or Aurora instead of Play Store
• Some conveniences lost: Google Assistant, automatic app updates
• More manual configuration: Need to set up alternatives for various services
• Better battery life: Less background activity and tracking

Common Adjustments:

• Learning new apps for familiar functions
• Manual backup processes instead of automatic cloud sync
• Different app stores and update procedures
• Alternative authentication methods for some services

User Feedback by Technical Level:

• Technical users: Generally very satisfied, enjoy increased control
• Average users: Initial learning curve, then mostly satisfied
• Non-technical users: May struggle without support

Adaptation Period: Most users report 2-4 weeks to fully adapt to degoogled phone workflows, with significant privacy benefits once established.

Several excellent alternatives exist for navigation on degoogled phones:

OsmAnd (Recommended for Features):

• Full offline maps with turn-by-turn navigation
• Detailed maps including hiking trails, public transport
• Voice navigation in multiple languages
• Route planning with multiple waypoints
• Supports GPX files and custom maps
• Steep learning curve but very powerful

Organic Maps (Recommended for Simplicity):

• Fast, simple interface
• Excellent for walking and driving directions
• Completely offline operation
• Based on OpenStreetMap data
• No ads or tracking

Magic Earth:

• More Google Maps-like interface
• Real-time traffic data
• 3D maps and satellite imagery
• Free but not open source

Web-based Solutions:

• OpenStreetMap.org in web browser
• HERE WeGo web interface
• Google Maps in web browser (less privacy)

Tips for Best Experience:

• Download offline maps for your region before traveling
• Use multiple apps for different purposes (city vs hiking)
• Consider dedicated GPS device for serious outdoor navigation
• Contribute to OpenStreetMap to improve map quality

Multiple privacy-focused solutions exist for syncing personal data:

Self-hosted Solutions:

• Nextcloud: Complete self-hosted cloud platform
• Radicale: Lightweight CalDAV/CardDAV server
• Syncthing: Peer-to-peer file synchronization
• Baikal: CalDAV/CardDAV server

Privacy-focused Cloud Services:

• Murena Cloud: Complete ecosystem with email, calendar, contacts
• ProtonMail: Secure email with calendar (limited CalDAV)
• Tutanota: Encrypted email and calendar
• Mailbox.org: Full email suite with CalDAV/CardDAV

Setup Process:

1. Choose service: Self-hosted or privacy-focused provider
2. Install DAVx⁵: CalDAV/CardDAV sync client from F-Droid
3. Configure accounts: Add server settings to DAVx⁵
4. Import data: Upload existing contacts/calendar from backup
5. Test sync: Verify data synchronizes correctly

Recommended App Combination:

• Email: K-9 Mail, FairEmail, or Thunderbird Mobile
• Contacts: Simple Contacts Pro or native Android
• Calendar: Simple Calendar Pro or Etar
• Sync: DAVx⁵ for server synchronization

Migration Tip: Export all data from Google before switching. Use Google Takeout to download contacts, calendar, and email archives.

Streaming service compatibility varies depending on DRM requirements and implementation:

Netflix:

• App works: Basic functionality usually available
• HD content limited: May only stream in standard definition
• Download issues: Offline downloads may not work
• Depends on ROM: Some ROMs have better Widevine support

Other Streaming Services:

• YouTube: Works in browser or via NewPipe
• Amazon Prime: Similar limitations to Netflix
• Disney+/Hulu: Variable compatibility
• Spotify/Music apps: Generally work well

Workarounds and Alternatives:

• Web browsers: Many services work in mobile browsers
• Dedicated device: Chromecast, Roku, or smart TV apps
• Desktop/laptop: Stream on computer, cast to TV
• Alternative services: Consider services with better FOSS support

Technical Background:

• HD content requires Widevine L1 DRM certification
• Custom ROMs often only support Widevine L3 (SD quality)
• Hardware security requirements limit compatibility
• SafetyNet failures can block some streaming apps

Solution: If streaming is critical, consider keeping a separate device with stock Android for entertainment, or use web browsers for most services.

Mobile payment options are limited on degoogled phones, but alternatives exist:

Why Google Pay Doesn't Work:

• Requires hardware-backed key attestation
• Needs certified Google Play Services
• SafetyNet integrity checks must pass
• Banks require official Google certification

Alternative Payment Methods:

• Physical cards: Keep credit/debit cards with you
• Cash: Still widely accepted
• Bank-specific apps: Some work without Google Pay
• QR code payments: Phonepe, BHIM apps
• Smartwatch: Wear OS or other payment-enabled wearables

Regional Alternatives:

• Europe: Many banks offer their own NFC payment apps
• Asia: QR-code based payment systems
• Developing markets: SMS-based payment systems

Future Possibilities:

• Open-source payment frameworks in development
• Bank adoption of alternative attestation methods
• Hardware security modules that don't require Google

Planning Note: Always have backup payment methods available. Mobile payments should not be your only option on degoogled phones.

Several backup strategies work well without Google services:

Built-in Solutions:

• Seedvault: Included in many privacy ROMs
• Local backups: Store on encrypted SD card or USB OTG
• ADB backup: Full device backup via computer

Cloud Backup Services:

• Nextcloud: Self-hosted or third-party providers
• Murena Drive: Part of e/OS ecosystem
• ProtonDrive: Encrypted cloud storage
• Standard cloud: Dropbox, OneDrive (less privacy)

Sync Solutions:

• Syncthing: Peer-to-peer file synchronization
• KDE Connect: Sync with Linux desktop
• Resilio Sync: BitTorrent-based sync

What to Backup:

• Critical data: Contacts, calendar, messages
• Photos and videos: Often largest data category
• App data: Settings, preferences, save files
• Documents: Important files and downloads
• System settings: Wi-Fi passwords, configurations

Backup Strategy Recommendations:

• 3-2-1 rule: 3 copies, 2 different media, 1 offsite
• Automated daily: Set up automatic syncing
• Test restores: Regularly verify backups work
• Encrypted storage: Protect sensitive data