diff --git a/content/collaborating/repo-permissions.md b/content/collaborating/repo-permissions.md
index ea4dec9..8fbf745 100644
--- a/content/collaborating/repo-permissions.md
+++ b/content/collaborating/repo-permissions.md
@@ -17,11 +17,13 @@ You can assign teams different levels of permission for each unit (e.g. issues,
 The visibility of your repositories will depend on the visibility of your profile, as well as whether you have marked a
 repository as private. Let's break down what this means:
 
-- If your profile's visibility is set to "Limited", _all_ of your non-private repositories will only be visible to logged
+- If your profile's visibility is set to "**Limited**", _all_ of your non-private repositories will only be visible to logged
   in users.
-- If your profile's visibility is set to "Public", _all_ of your non-private repositories will be shown to everyone.
+- If your profile's visibility is set to "**Public**", _all_ of your non-private repositories will be shown to everyone.
 - If you do not want anyone (apart from [your fellow collaborators](https://docs.codeberg.org/collaborating/invite-collaborators/))
-  to see your repositories, mark your repository as "Private".
+  to see your repositories, mark your repository as "**Private**".
+  However, Codeberg's Moderation Team and infrastructure administrators can access private profiles and repositories as per the
+  [Privacy Policy](https://codeberg.org/Codeberg/org/src/branch/main/PrivacyPolicy.md#4-data-handling-by-association-bodies-third-parties).
 
 The visibility of your profile can be changed in the [Privacy settings](https://codeberg.org/user/settings).
 Be careful when you set your profile's visibility to "Limited"; Even if a repository is public, users that are