Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/dailynet/public_html/wp-content/plugins/elementor-pro/modules/loop-builder/module.php on line 200

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
What info is Google Sync exactly saving? - The Daily Net

What info is Google Sync exactly saving?

Turning on Google Sync completely changes the way you look at the web. It makes Chrome much more intuitive and parallel across devices. I like knowing that I can pull out my opened tabs from any device with Chrome, or have the same bookmarks, passwords, history and other info. But where exactly do we draw the line between an intuitive experience and a potentially dangerous privacy issue?

We can trust that Google is doing a fair job at keeping our information safe, but it is always good to stay informed about what goes on behind your screen. Renowned developer François Beaufort has given us some great information about what happens when one syncs information to a Google account.

Of course, we can already tell what is being synced by going to Advanced Sync Settings within Chrome, but here is a more detailed explanation of the exact information being saved.

Apps:
– Apps
– App settings
– App Notifications

Autofill:
– Autofill
– Autofill Profiles

Bookmarks

Extensions:
– Extensions
– Extension settings

Omnibox History:
– Typed URLs

Passwords

Settings:
– Search Engines
– Preferences
– Dictionary

Themes

Open Tabs:
– Sessions

One last thing, as soon as you enable Sync, these items are also synced:
– Device Info
– Encryption keys
– Experiments

So there is quite a bit more information there than some of us may think. You can always pick and choose wich categories you want synced and which you don’t, but we wish Google would let us choose between the sub-categories as well.

Don’t forget we usually give away a good deal of privacy for the sake of convenience. Regardless, you can take this information and make the best decision based on your needs. Will any of you be unchecking some of those Google Sync boxes in the settings?

[via François Beaufort]