STR: 1) Create a fresh profile. 2) Go to Firefox Sync, select to create a new account 3) Enter an email & password, 'accidentally' enter the age as 3 (or something less that 13). 4) Select create => A message is displayed with "You must meet certain age requirements to create a Firefox Account." 5) Try and go back to correct the age (e.g. you entered it wrongly by mistake), try restarting Firefox. => No way to get out of the age requirements limit, and no way to find out how to get out of it. => Nothing on support.mozilla.org. I ended up having to clear history for the last hour (which I suspect cleared cookies). Whilst I realise this is to prevent children from accessing FxA incorrectly, it seems a bit limiting that we don't given any information anywhere on how to get out of it, especially in case someone enters it incorrectly by accident.
This is, unfortunately, on purpose - legal compliance in this area is tricky, but broadly, we're not allowed to provide info to help underage users circumvent the age restriction here. We might be able to work with legal to come up with some clever wording to help with the "accidentally entered the wrong age" case without straying into the "I'm going to lie about my age" space, but I'm not really sure what that would look like in practice.
>Whilst I realise this is to prevent children from accessing FxA incorrectly, it seems a bit limiting that we don't given any information anywhere on how to get out of it, especially in case someone enters it incorrectly by accident. Explaining to adults how to get out of it also benefits children who should not be using the service. Current behavior is intentional per recommendations from legal. I understand that it's not ideal but it's only happening to a small minority of users. I'm closing this because I've already revisited this with legal twice. There are no obvious changes to make at this time.
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.