I stopped using Gmail about 8 years ago. The decision didn’t come as a reaction to a single incident or policy change, but as a gradual change in the way I thought about email as a system. Gmail worked fine then and still works fine now. What changed for me was not the quality of the product but the role it played in a broader ecosystem that collects and correlates data in almost every digital interaction (which sounds abstract until you realize how often you click “Sign in with Google”).
Email occupies a unique position because it quietly becomes the backbone of your online identity, linking accounts, storing transaction logs, and acting as a fallback mechanism when something goes wrong elsewhere. Once this becomes obvious, it’s hard to ignore that Gmail operates within an environment designed to data collection and I wanted my email to remain a contained tool rather than an entry point to everything.
Looking for a simpler model
Choose a practical alternative approach
The search for an alternative was based on practicality rather than ideology, as I still needed something that behaved like a normal email service without reinventing everything from scratch (no desire to self-host a mail server and spend weekends debugging SPF Records). That search led me to Proton AG and its offering, Proton Mail, which presented itself as a familiar interface built on a different set of assumptions about handling data.
Proton Mail doesn’t try to redesign email, making the transition easier on a surface level, but its underlying model changes the way messages are stored and accessed.
Messages between Proton users are encrypted by default, while communication with external recipients can be encrypted where necessary and the entire service operates under Swiss privacy laws that impose additional restrictions on data access. These details do not alter the act of writing or receiving email, but they do significantly alter the conditions under which that data exists.
The migration was slow by design.
Gradual transition without interrupting access
Moving away from Gmail required more patience than I initially expected because email addresses are bundled into a wide range of services that add up over time.
Instead of attempting a complete switch, I ran Proton Mail alongside Gmail and gradually migrated the accounts that mattered, starting with financial services, infrastructure providers, and platforms tied to work in progress. This incremental process reduced the risk of disrupting access to something important and allowed the transition to occur seamlessly.
He also made it clear that email migration is not about moving messages from one inbox to another but about updating the network of connections that depend on that address. The process dragged on for months, which was more necessary than excessive.
Living outside the Google ecosystem
Reduce dependence on Google services
Leaving Gmail introduces a broader issue about dependence on Google services, as email often sits alongside tools like Google Drive and Google Calendar in a tightly integrated workflow. Replacing everything at once would have added unnecessary complexity, so I treated each service independently and avoided forcing a full migration before suitable alternatives were available.
Over time, Proton expanded its ecosystem with tools like proton propulsionProton Calendar and the new Proton Docs, which made it easier to consolidate certain parts of my workflow without recreating the same level of interdependence found in the Google stack (or at least not the same type).
I still have a Gmail account (unfortunately)
Maintain access to legacy systems
Although Proton Mail became my primary inbox, I never deleted my Gmail account completely because it remains tied to earlier phases of my digital life, particularly university systems and accounts that were created long before I considered switching providers. It is not always worth untangling these connections, especially when they work without problems and do not require active use.
As a result, Gmail’s role has changed, as it now acts as a secondary inbox for legacy access rather than a central communication hub. Important conversations, new sign-ups, and ongoing work are all done through Proton Mail, while Gmail exists as a compatibility layer that allows me to interact with systems that still expect a Google account. This separation has proven to be practical, as it avoids unnecessary migration efforts while keeping my main workflow within a more controlled environment.
Proton Mail does it right
Focused design without unnecessary layers
The most notable change after the change is the absence of additional layers built around the inbox, as Proton Mail focuses on the core functionality without trying to extend into adjacent behaviors. The interface remains simple and the experience revolves around reading and writing emails without introducing elements designed to capture attention or guide user behavior.
Encryption is central to this approach, with messages protected both at rest and in transit, and communication between Proton users is handled automatically with no additional configuration (no changes to remember). External communication It can also be encrypted when needed, providing flexibility without complicating the default workflow. This design maintains system consistency, even if it introduces certain limitations compared to more feature-rich alternatives.
The compensations you notice
Where limitations become more visible
The differences become more apparent in areas where encryption imposes restrictions, particularly in search functionality, since the server cannot process the content of messages in the same way as a traditional email provider. Proton has fixed this issue with client-side indexing, which improves usability, but the experience still differs from the near-instant search capabilities that Gmail offers.
The integration also requires tweaking, as Proton Mail doesn’t connect as extensively with third-party services and using desktop clients like Mozilla Thunderbird involves an additional bridge app that manages encryption locally. This configuration works reliably but introduces an additional component that must be maintained.
Paying for the product changes the relationship
Subscriptions align incentives with users
The business model behind Proton Mail influences the behavior of the service, as it is based on subscriptions rather than advertising, which aligns its incentives more closely with the user. This creates a clearer boundary between functionality and data collection, as the service does not rely on mining behavioral information to generate revenue.
With Gmail, the relationship is determined by its role within a broader ecosystem that benefits from aggregated data, while Proton Mail is positioned as a standalone tool designed to perform a specific function. This distinction becomes more significant over time, especially when you consider how much personal information passes through an email account.
How does it hold up after 8 years?
Long-term reliability and constant improvements
Proton Mail has evolved significantly since I started using it, with improvements to the interface design, mobile apps, and overall performance that bring it closer to the level of refinement expected of a modern email service. The addition of related tools like Proton Drive and Proton Calendar has made it easier to maintain a consistent workflow without relying on third-party vendors for basic functionality.
Despite these improvements, the service retains its original focus, evident in its limited reach compared to broader platforms. This approach contributes to a sense of stability, as the service evolves without attempting to redefine its purpose.
Why didn’t I ever come back?
The decision to leave Gmail was not motivated by dissatisfaction with its capabilities but by a preference for a system that more closely aligns with my thinking about data ownership and privacy.
Proton Mail introduces a small amount of extra effort in exchange for more control, and over time that trade-off becomes part of the routine rather than a hindrance. After 8 years, Proton Mail seems like a natural default, while Gmail seems like a system built around a different set of priorities.
Maintaining a secondary Gmail account for legacy access has proven to be a practical compromise, as it allows me to retain compatibility when needed without reverting to a workflow that relies on it as a primary tool.
