Before I move forward with publishing things publicly and linking to it from our web site, I;d need to know a bit more about how to rewrite our own privacy policy (note: we’re EU based, so GDPR has real, actual teeth for us). Since for those components of our website that we could store on space and the DO CDN that comes with it (optionally), becomes part of our website, we need to cover it, but the general DO privacy policy is not focussed on our visitors downloading components from a DO space. Is there an easy to read privacy policy from DO that covers anonymous use of spaces only ? (one of the GDPR requirements is to have easy to read non-techie descriptions). It shoudl at least cover and cookie, access log etc. ESp. as IP adresses are considered identifying information and logs tend to contain them …
For all clarity: the DO space would be “public” access. so nobody needs to login on DO or anything like that.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
