Skip to main content

GDPR and privacy settings in Brizy Cloud

Chris S.

Hi,

Here are a few questions related to GDPR and data privacy: 

  1. How can I know if the fonts I use in Brizy Cloud are GDPR compliant? Am I right to believe that Google fonts are not allowed under GDPR regulations? 

  2. Although I have set "search engine visibility" off in project's settings, each new page or blog post I create comes with its individual "search engine visibility" set to 'on'. Is it possible to have them aligned with the global project parameters?

  3. In Brizy Cloud, where can I access images/files I previously uploaded? How can I reuse them or delete them if unused? Can I turn off the search engine visibility of an image off? Can I check and modify an image's parameters (alt name, description etc.) to impact SEO?

Thank you!

0

Comments

5 comments

Date Votes
  • KC George
    • Edited

    Hi Chris,

    How can I know if the fonts I use in Brizy Cloud are GDPR compliant? Am I right to believe that Google fonts are not allowed under GDPR regulations?

    Brizy Cloud uses Bunny.net as the font hosting provider (and not Google Fonts). When hosting a website with Brizy Cloud, you would be the controller and Bunny.net would be your processor as per the GDPR definitions. GDPR requires that the controller use only processors providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that processing will meet the requirements of the Regulation and ensure the protection of the rights of the data subject. https://gdpr.eu/article-28-processor/

    Bunny.net guarantee that no personally identifiable data is stored from your users that access your services through them. https://bunny.net/gdpr/  Hence as per Article 28 of the GDPR, bunny.net can be considered a GDPR complaint processor.

    In the past, Google Fonts used to track the IP address of the users when a website accessed fonts from them. After the Regional Court of Munich ruling in Jan 2022, in July this year, Google discontinued tracking IP addresses of users while delivering fonts. Google Fonts FAQ at https://developers.google.com/fonts/faq/privacy states that 

    IP addresses are not logged or stored on Google’s servers and are not analyzed for any purpose.

    As on today as per Article 28 of the GDPR, Google Fonts should be considered a GDPR compliant processor. However a widespread perception exists around the world that they are not compliant. Especially in Germany Google fonts is perceived as non GDPR compliant.

    Although I have set "search engine visibility" off in project's settings, each new page or blog post I create comes with its individual "search engine visibility" set to 'on'. Is it possible to have them aligned with the global project parameters?

    Most users want their websites to be visible to search engines. By default Search Engine visibility is enabled for all projects, pages and posts. You will have to disable search engine visibility individually for each page/post. 

    In Brizy Cloud, where can I access images/files I previously uploaded? How can I reuse them or delete them if unused? Can I turn off the search engine visibility of an image off? Can I check and modify an image's parameters (alt name, description etc.) to impact SEO?

    Brizy Cloud does not provide an Image Library at the moment. Image library is included as part of our public roadmap https://trello.com/c/BJgBX0Wj. Reusing of images is not possible at the moment.

    To disable indexing of images of a specific page, please add this code to the page header.

    <meta name="robots" content="noimageindex">

    You can add Alt Text to images here. https://jmp.sh/CiwSUEeV Brizy Cloud does not have a provision to add an image description. 

    0
  • Chris S.

    Hi KC George,

    Thank you for the detailed answer re Google Fonts, it is really helpful!

    Most users want their websites to be visible to search engines. By default Search Engine visibility is enabled for all projects, pages and posts. You will have to disable search engine visibility individually for each page/post. 

    What is the point of having a parameter at project level then? The risk is really high to miss one individual page or post setting. It seems that all users' needs would be met (not just the majority) if the project-level SEO-visibility parameter would supersede individual pages/posts settings, wouldn't it?

    Can you please also clarify if there is a risk that an unused asset can be found via a search engine (as I understand I cannot delete them manually)?
    For example: what if an employee consents to having his/her picture on a website and later requests to have all information deleted (as per GDPR)? Can I be sure it won't be found later as an isolated asset stored on your servers?

    Thank you! 

     

    0
  • KC George
    • Edited

    Hi Chris,

    Project level Search Engine Visibility setting overriding Page Level setting may not work for all users. For example, consider a scenario where an entire website needs to be indexed except the Thank you page (after newsletter subscription) and legal documents. In this case, the Search Engine Visibility would be Enabled at the Project Level and for the Thank you page and legal docs, it would be Disabled.

    Unused assets can be deleted. We have made deleting of assets difficult to avoid deleting hundreds of assets at the same time by mistake. Before an asset can be completely deleted every content added to the asset must be first removed. For example, let's say you have added a Recipe asset and have added 15 Recipes. Please delete the 15 Recipes first, then delete all custom fields before deleting the Recipe asset.

    You have the option to unpublish any custom asset by setting it as Draft. This would remove the asset from the website frontend and eventually it would be removed from the search engines as well.    

    0
  • Chris S.

    Hi KC George, 

    Thank you for your answer. I get your point re Project-level Search Engine Visibility, it makes sense.

    Re unused 'assets', I am not sure if I used the correct term: I was referring to unused images more specifically. In other words, I wanted to know what happens if I upload an image to your servers and later remove it from all pages/blog posts. Since I cannot access the image file itself and delete it from the server (or set the image itself as 'draft') there is still a risk it can be found on a search engine, correct? Which in my example (with an employee withdrawing consent to use their picture) could be an issue.

    Thanks for your patience, I just want to make sure I get it right.

     

    0
  • KC George

    Hi Chris,

    Your question was

    What happens If I upload an image to your servers and later remove it from all pages/blog posts

    When you upload an image to a Brizy Cloud page/ blog post and later remove it, the images are de-linked from the pages/ posts and image paths are removed from your pages/ blog posts. Since any reference to the image paths are removed, there is no way to access those images.

    You can also request Google to remove the images that are part of their index. Please watch this video for the procedure https://youtu.be/4nZcCDfYDfE You can also read more about it here Remove an image from Google Pleas read this section of the page

     

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

Ask a Question