/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Google is open sourcing its differential privacy library, which it uses to securely draw insights from data sets containing sensitive user information

Google is making differential privacy available to anyone  —  Google today announced that it is open-sourcing its so-called differential privacy library …

The Verge Nick Statt

Context & Ripple Effects

This is the third privacy tooling release from Google in roughly six months of 2019: after TensorFlow Privacy brought differential privacy into its machine learning framework in March and Private Join and Compute opened a way to compute over other parties' confidential data in June, the company is now handing out the very library it uses internally to draw insights from sensitive user data.

That sequence matters because it converts privacy techniques Google previously treated as proprietary infrastructure into shared developer tooling — a playbook it kept running years later with [[a:1157383|the video-blurring and encrypted-computation technologies released under Protected Computing]].

First-order effects

  • Developers and researchers gain direct access to the same differential privacy implementation Google uses on sensitive user data sets, rather than having to reimplement the technique themselves.

Second-order effects

  • Rivals building analytics or ML platforms face pressure to match Google's open privacy tooling or explain why their own implementations stay closed — the same dynamic Private Join and Compute set off for cross-organization computation.

Third-order effects

  • If the pattern holds, differential privacy shifts from a specialist research technique toward a default expectation for products that touch personal data, with Google's open-source releases functioning as de facto reference implementations regulators and auditors can point to.

The trend: Google is steadily converting its internal privacy infrastructure into open-source tooling, making privacy-enhancing technology a competitive baseline across the industry.

Discussion

  • @leakissner Lea Kissner on x
    Want some differential privacy? Please don't roll your own — like cryptography it's subtle and quick to anger. Google has released as open-source code which was built for *mumblemumble handy privacy infrastructure thing*. It has some nice advantages: 🧵 https://www.wired.com/...
  • @wired @wired on x
    Google is releasing a new homegrown differential privacy tool that includes an interface to make it easier for more developers to actually implement the protections. https://www.wired.com/...
  • @tedonprivacy Ted on x
    Folks, today I am SO EXCITED that Google colleagues and I are open-sourcing our ✨ differential privacy library ✨ for anyone to use. I've been waiting & pushing for this for a while now! I can't wait to see what other folks & organizations do with it! 🌈 https://github.com/...
  • @tedonprivacy Ted on x
    Finally, we explain this code & paper release in a shiny blog post that gives a few real-world examples of what it can do and how we use it for. https://developers.googleblog.com/ ...