google chrome web store developer privacy policy

When Google refers to 'personal data,' it's referring to any information that you can use to identify someone. You'll see the Privacy Policy refers to personal data, so let's break down what this actually is.

Handle as little information as possible to minimize what you're transmitting.

You can only transmit it over secure connections, like HTTPS.

Secondly, from a safety perspective, personal or sensitive data must be encrypted during transmission. This is just a document setting out what data you process and how you keep it safe and secure while it's in your possession. You must draft a Privacy Policy and publish it in your Developer Dashboard if you handle personal data, and.You can find them in Google's updated list of Privacy Policy requirements, but basically, it all comes down to two obligations. But if you haven't drafted one, here's what the rules say. So if you've already drafted a Privacy Policy to comply with these laws, you're probably already complying with Google's requirements. California Consumer Privacy Act ( CCPA).

EU's General Data Protection Regulation ( GDPR).But if you're a developer and you plan on publishing an extension for download, here's how to know if you need a Privacy Policy.Īccording to global privacy laws, you need a Privacy Policy if you collect or handle any sensitive data belonging to an identifiable individual. With extensions, people can adapt their Chrome browser to their own unique needs. If you're publishing an extension on Google Chrome's Web Store, and you handle any personal data at all, then you need to write and publish a Google-compliant Privacy Policy.Įxtensions are add-ons designed to improve the user experience when someone browses the internet.

Google chrome web store developer privacy policy