<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 14, 2015, at 4:33 PM, Ryan Kelly <<a href="mailto:rfkelly@mozilla.com" class="">rfkelly@mozilla.com</a>> wrote:</div></blockquote><br class=""><blockquote type="cite" class=""><div class="">We do in fact store it, since we also need it when sending emails. It's<br class="">based on the Accept-Language header used when signing up for the account.<br class=""><br class="">We don't yet expose it to reliers or provide a way for the user the edit<br class="">it, but we can and will do so eventually. If this is a priority for<br class="">you, we can bump it up our priority list accordingly.<br class=""></div></blockquote><div><br class=""></div><div>If you did expose it in an API would we still be stuck with the problem outlined here: <a href="https://github.com/mozilla/fxa-auth-server/issues/962" class="">https://github.com/mozilla/fxa-auth-server/issues/962</a> and that feels like a bigger problem. </div><div><br class=""></div><div>We’ve got a simple workaround, just storing it along with the email for now.</div></div><br class=""></body></html>