Nice Move, Google — What Took You So Long?
What Took You So Long? — In a move that is being interpreted by many as a cannon shot across Facebook's bow, Google has changed the terms of service on its contacts API — the programming interface that allows developers to automatically pull your contacts from Gmail and other services.
Context & Ripple Effects
This move closes a loop opened three years earlier. In late 2007, a small move by Facebook showed how much leverage sat in who controls the social graph, and analysts argued that email and cellphone contacts are the real social graph — the address book every network wants to import. Since then, Gmail's contacts API has been the free on-ramp: any service, Facebook included, could let users pull their Gmail connections in without giving anything back.
On November 5, 2010, Google rewrote those terms of service so that pulling contacts out requires letting users export them back in — reciprocity enforced by contract. TechCrunch framed the same story twice the same day, as a demand that Facebook 'can't import our user data without reciprocity' and as the moment 'data protectionism begins in earnest,' which tells you how widely it traveled and how quickly it was read as a shot across Facebook's bow rather than a routine policy update.
First-order effects
- Apps that import Gmail contacts into closed networks — Facebook's contact finder most visibly — face losing programmatic access to Gmail's address books until they offer users an equivalent export path.
- Developers whose products sit on one-way contact ingestion must build reverse-export features or re-engineer around manual uploads, turning a free API into a conditional one overnight.
Second-order effects
- Facebook is pushed to decide whether to open an equivalent contacts-export channel for Google and other services or absorb the friction of losing fresh Gmail imports — the exact asymmetry Google's terms are designed to eliminate.
- Other large holders of contact data (Yahoo, Microsoft, mobile carriers) come under pressure to attach the same reciprocity strings, since Google has established the template that one-way extraction is no longer the default.
Third-order effects
- If reciprocity terms spread, the 2007-era assumption of an openly importable social graph gives way to bilateral data treaties between platforms — user relationships becoming gated assets each gatekeeper controls, with developers negotiating access rather than taking it.
- Users end up holding the nominal right to move their own contacts, but only along corridors the platforms mutually approve, shifting the battleground from feature competition to terms-of-service design.
The trend: The social web is moving from open contact-portability toward platform data protectionism, as the address books once treated as common infrastructure are recast as competitive moats.