# Privacy concerns with gstatic.com \[Theme: Universal\]

**URL:** <https://discourse.gohugo.io/t/privacy-concerns-with-gstatic-com-theme-universal/3871>\
**Category:** support\
**Created:** [August 10, 2016, 10:48pm UTC](https://discourse.gohugo.io/t/privacy-concerns-with-gstatic-com-theme-universal/3871 "2016-08-10T22:48:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![rdwatters](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/rdwatters/32/2848_2.png) [@rdwatters](https://discourse.gohugo.io/u/rdwatters)\
**Post date:** [August 11, 2016, 5:03am UTC](https://discourse.gohugo.io/t/privacy-concerns-with-gstatic-com-theme-universal/3871/2 "2016-08-11T05:03:07Z")

</div>

Yes, you can host all those files locally.  
There are numerous added benefits to doing it, in fact…especially if you’re at the point in your development where you’re setting cache-control headers.

Here’s what you should do:

1. Host the google fonts locally
2. Host your own css
3. The only reason to use the maps API is if you’re displaying maps on your site. _Are_ you using maps for anything? If not, you can probably get rid of it…

---

_[View the full topic](https://discourse.gohugo.io/t/privacy-concerns-with-gstatic-com-theme-universal/3871)._
