14 DAY TRIAL // Twitter announced almost a month ago that it would allow users to add geolocation data to their tweets. The feature was initially scheduled to become live yesterday but Twitter decided to push it back as it wasn't quite ready for the prime time. Still, the geolocation data feature should be launched within a few days and Twitter’s platform head Ryan Sarver has shared some of the details on how it will work, at least for developers.
Twitter has already laid out the basic details on how it will implement the local data. Users will be able to opt-in to display the location data along with every tweet. This isn't enabled by default and the user will have total control over what data is stored and displayed. The feature will also only be available in third-party clients at the beginning, Twitter cofounder Biz Stone said at the time.
“We're going to release geolocation to platform developers before we add the feature to Twitter.com. [...] Developers will have access to this new geolocation feature early which means it will most likely be available on your app of choice before it's available on Twitter's web site. Later, we'll add it to our mobile web site and Twitter.com as well,” Stone added at the time.
Now Sarver has announced several other details, according to Smarterware. Because of the sensitivity of the data Twitter has taken privacy very seriously. Users will have to opt-in to display their location and, even if the client were to send the location metadata, Twitter will drop it when it comes without even storing it. Apps will most likely include checkbox for sending the data when posting a new tweet but even so users will have to enable the feature in their settings page on the site.
Even if the users agree to opt-in, Twitter will remove the location data after 14 days completely deleting it from its servers. Developers are also encouraged not to store any information for too long for the same reason Twitter will drop it after 14 days, to avoid subpoenas. Twitter also recommends that apps display a broader area when showing the location “fuzzing” the data and the time even though on the backend the location will have full latitude and longitude data.