[Mac] Chromium builds shouldn't ask for access to Chrome's own secure data

components/encryptor/keychain_password_mac.mm

Index: components/encryptor/keychain_password_mac.mm
diff --git a/components/encryptor/keychain_password_mac.mm b/components/encryptor/keychain_password_mac.mm
index 7a078bf0e914b9857b2344efb75f84b625c31538..e2c7fff90a1242d371c30464213a607c2b1df0f7 100644
--- a/components/encryptor/keychain_password_mac.mm
+++ b/components/encryptor/keychain_password_mac.mm
@@ -51,8 +51,13 @@ std::string KeychainPassword::GetPassword() const {
   // These two strings ARE indeed user facing.  But they are used to access
   // the encryption keyword.  So as to not lose encrypted data when system
   // locale changes we DO NOT LOCALIZE.
+#if defined(OFFICIAL_BUILD)
   const std::string service_name = "Chrome Safe Storage";
   const std::string account_name = "Chrome";
+#else
+  const std::string service_name = "Chromium Safe Storage";
+  const std::string account_name = "Chromium";
+#endif
 
   UInt32 password_length = 0;
   void* password_data = NULL;