You buy a new phone, it’s stamped “IP68” on the spec sheet, and suddenly everybody at the pool thinks your phone is an underwater action cam. What most people don’t read — or don’t want to hear — is the tiny, earnest paragraph that manufacturers tuck into product pages and manuals. This week, Google did something almost refreshingly blunt: it put that paragraph where more people will see it, and the message is simple and unsettling for convenience-loving humans everywhere: your phone leaves the factory water-resistant — but that resistance is not permanent.
Here’s the language Google added (they’ve used versions of this before, but it’s now prominent on Pixel product pages and support docs):
Designed to comply with dust and water protection rating IP68 under IEC standard 60529 when each device leaves the factory but the device is not water or dust proof. … Water resistance and dust resistance are not permanent conditions and will diminish or be lost over time due to normal wear and tear, device repair, disassembly or damage. … Liquid damage voids the warranty. See g.co/pixel/water for details.
That wording hits two notes that companies usually prefer to bury: (1) the IP rating is a factory condition, not a lifetime guarantee; and (2) if water gets in, the company treats it as evidence of accidental damage — not a covered defect. In short: IP68 ≠ “set it and forget it.”
What IP68 actually means (and doesn’t)
The “IP” code — short for Ingress Protection and defined by IEC standard 60529 — is a lab test. The first digit (6) means “dust tight”; the second (8) means the enclosure can be submerged beyond 1 meter in still freshwater for a specified time under controlled conditions. The standard tells you what the claim meant in the lab, not what will happen after a year of keys, pockets, and coffee spills. Real-world conditions — pressure spikes from waves or drops, salty seawater, chlorinated pool water, or a loosened gasket after a repair — aren’t part of that lab test.
That distinction is why the phrase “water-resistant” is a more accurate consumer shorthand than “waterproof.” Plenty of reviewers and repair technicians have documented phones that pass IP tests on day one but bleed water after a heavy bump or weeks of sweaty commutes. Google’s new emphasis is just an explicit spelling-out of what the standard already implies.
How the seals fail
Phones use a mix of gaskets, adhesives, tight tolerances, and protective coatings to keep water out. Those materials can age, deform, or lose adhesion. Physical shocks (drops, presses), heat and cold cycles, and exposure to corrosive liquids like salt or chlorine accelerate the process. Repairs that require opening the chassis are a particular risk: even competent technicians can’t reliably restore factory-grade sealing, so most manufacturers say a repair might remove or reduce the device’s IP protection.
Add to that the practical reality: manufacturers can’t prove how or when a device got wet. If they find corrosion or water inside, it’s strong evidence that the phone was exposed outside the controlled test conditions — and that becomes the legal basis for excluding the damage from warranty coverage. That’s why so many companies (Google included) explicitly exclude “liquid damage” from warranty protection.
So what’s the takeaway for users?
- Treat IP68 as “splash-proof and tolerant of accidental immersion,” not as a diving certification. It buys you forgiveness for a tumble into a sink or a spilled drink — maybe — but not for repeated submersion, high-pressure water, or saltwater adventures.
- Avoid salt and chlorine. Both are corrosive and can speed up seal degradation. If your phone touches seawater or pool water, rinse it with fresh water (if it’s safe to do so), dry it thoroughly, and let it rest before powering up. Google’s support pages walk through basic first-aid steps: remove it from the water, power it off, dry it with a cloth, and let it air-dry at room temperature.
- Back up your data often and consider extra protection. If you can’t bear the risk, use a waterproof case or a rated dry bag for activities around water. Remember: cases can restore protection for the time being, and they’re cheaper than a repair.
- Be wary after a repair. Any disassembly may break factory seals. If a device has been opened, ask the repair shop what they’ll guarantee and whether they restore IP sealing — most can’t promise original factory levels.
- If your phone dies after getting wet, don’t assume the warranty will save you. Inspect ports for corrosion or discoloration (service centers look for visual signs), and be prepared for out-of-warranty repair options.
Why Google’s bluntness matters
Phone makers have always had the same legal hooks in their warranties; what’s new is the tone. Google’s decision to put the “not permanent” language front and center reads as consumer candor — or defensive marketing — depending on how cynical you feel. For journalists and regulators, it’s an interesting shift: a major brand is telegraphing a limitation that, until now, lived mostly in help-center pages and warranty PDFs. That candor could push rivals to be clearer with customers, which is good for people who assume “IP68” means “submerge me daily with confidence.”
There’s also a regulatory angle. The U.S. Federal Trade Commission expects advertisers to have a reasonable basis for their claims; if firms market devices as “waterproof” without clear limits, that could invite scrutiny or complaints. The safer legal posture is to advertise in optimistic terms and anchor those claims with conspicuous disclaimers — exactly what Google did.
The bottom line
IP ratings are useful — they’re an engineer’s shorthand for how the device behaved in test conditions — but they aren’t a lifetime promise. Google’s message is blunt because it has to be: the physics and chemistry behind seals mean water protection is probabilistic, not permanent. If you treat your phone like a fragile, expensive camera rather than an indestructible pocket toy, you’ll keep it working longer. If you want waterproof for life, you’ll need a purpose-built rugged device or a good case — and even then, read the fine print.
Discover more from GadgetBond
Subscribe to get the latest posts sent to your email.