Twitter also sends the password + email + name on each keypress once the user has entered at least 6 characters on it signup page. [0]
[0]: https://twitter.com/signup [0]: https://twitter.com/signupI think there are valid reasons to store incomplete form data, but I don't think it should be used for reasons the customer did not intend (e.g. receiving emails).
For password, they start sending every character you type once the field has 6 characters in it. It then sends your full form details on every keypress (plus it has a delayed send to the same password_strength call, similar to what they do for emails). So if you type your password slowly, it will send your details twice for every keypress.