The uncomfortable truth about a smart security camera is that its useful features and its privacy promises are often in a tug-of-war. The more a service can inspect video in the cloud, the more it can describe activity, search footage and share access. The tighter the encryption, the less it can do.
Ring’s answer is a new default called TAKE—short for Throw Away the Key Encryption. The company says it will begin rolling it out in phases this September and make it the default for Ring customers worldwide once deployment is complete. The design is more thoughtful than an ordinary “your data is encrypted” reassurance. It is also important to say plainly what it is not: end-to-end encryption.
What Ring says TAKE changes
Under TAKE, Ring says each video uses unique, rotating encryption keys. A copy is held temporarily in a cloud secure enclave and may be made available to Ring only to run the cloud features an account has enabled. Ring says it deletes that cloud-held key after the request, leaving the customer and permitted shared users with the keys on their enrolled devices.
| Setting | Who can access keys | Cloud features and shared users | Practical trade-off |
|---|---|---|---|
| Ring’s previous default encryption | Ring protects video in transit and at rest | Available | Familiar cloud-camera convenience, with Ring operating the service. |
| TAKE (new default when fully rolled out) | Customer retains keys; Ring says it can temporarily access a cloud-held copy for enabled features | Available | More customer control, while still relying on Ring’s constrained cloud processing. |
| Optional end-to-end encryption | Only enrolled customer devices | Many cloud-dependent features and Shared Users unavailable | Strongest key isolation, with less convenience. |
The useful improvement is the temporary key model. It makes Ring’s claimed access more limited and purpose-bound than a permanent service-side key arrangement. TechCrunch reports that the company intends it to preserve features such as video search, descriptions and Smart Alerts; The Verge reports that Ring says the system also limits the video it can provide in response to law-enforcement requests.
That is a better default direction for a product category that has too often treated privacy as a setting people must discover after installation.
The word “temporary” carries the whole argument
TAKE asks customers to trust several things at once: that the secure enclave is correctly designed, that Ring exposes keys only for the features a customer selected, and that deletion happens as described. Those are testable engineering and governance claims, but they are not equivalent to a system in which the service never has a usable key.
That distinction matters most for buyers who regard a camera as an evidence device, not merely a convenience appliance. End-to-end encryption is more restrictive precisely because the provider cannot freely process the video. Ring keeps it as an optional per-device setting, while acknowledging that Shared Users and cloud-based features are not available with E2EE enabled.
For many households, the convenience bargain will be reasonable. A camera that cannot tell you whether a package arrived, or let a partner see a feed, is less useful. But “more private than before” is not a synonym for “private by design.” Ring is offering a middle path, and customers should evaluate it as one.
What to do when the setting reaches your cameras
The rollout is phased, so do not assume every Ring device changes at once. When TAKE appears in the Ring app, take five minutes to make an intentional choice:
- Review which cloud features are enabled and whether each is worth temporary cloud key access.
- Check every Shared User; access lists tend to outlive the reason they were created.
- Use E2EE for cameras covering especially sensitive spaces if you can accept the feature limits.
- Protect the Ring account itself with a unique password and its required two-step verification—encryption cannot rescue an account someone else controls.
- Revisit the setting after any new camera, household change or feature update.
This is the same basic principle GearPulse raised in our look at the WebKit Private Relay leak: a privacy label is only useful when it makes the boundary of access understandable. The real win is not a clever acronym. It is knowing who can see what, under which conditions, and how you can change that.
Bottom line
Ring’s TAKE is a welcome upgrade over treating cloud encryption as a black box. Making stronger customer-held keys the default, while preserving the features people actually buy Ring cameras for, is a serious attempt at the hard middle ground.
Just do not mistake it for end-to-end encryption. If keeping Ring from accessing usable video keys is the priority, E2EE remains the cleaner answer—at the cost of cloud features. TAKE gives buyers a more practical default; it does not remove the need to choose what kind of privacy they want.