לאתר זה תהיה פונקציונליות מוגבלת בזמן שאנו מתחזקים אותו לשיפור החוויה שלך. אם מאמר מסויים לא פותר את הבעיה שלך וברצונך לשאול שאלה, קהילת התמיכה שלנו מחכה לעזור לך ב־Twitter תחת ‎@FirefoxSupport וב־Reddit תחת ‎/r/firefox.

חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

Delete Firefox sync account after email change

  • 1 תגובה
  • 1 has this problem
  • 1 view
  • תגובה אחרונה מאת frank.aurich

more options

Hi,

during maintenance of my logins in my password manager I discovered that I still have the login data for a FireFox Sync account. I can login to that account and see my settings, but I actually want to delete the account completely. The problem: The mail address associated with that account does not exist anymore (changed the company). When trying to delete the account (or when trying to add a seconday mail address), Firefox Sync prompts me to enter a verification code that was sent by mail.

I'll never receive that code, as that original mail adress does not exist anymore.

How can I delete that FS Sync account?

Thanks, Frank

Hi, during maintenance of my logins in my password manager I discovered that I still have the login data for a FireFox Sync account. I can login to that account and see my settings, but I actually want to delete the account completely. The problem: The mail address associated with that account does not exist anymore (changed the company). When trying to delete the account (or when trying to add a seconday mail address), Firefox Sync prompts me to enter a verification code that was sent by mail. I'll never receive that code, as that original mail adress does not exist anymore. How can I delete that FS Sync account? Thanks, Frank

פתרון נבחר

Nevermind,

the mails with the verification codes came through after all. Issue resolved.

Read this answer in context 👍 0

כל התגובות (1)

more options

פתרון נבחר

Nevermind,

the mails with the verification codes came through after all. Issue resolved.