- While our classic app{" "} - uses its own authentication, the app you're using now uses a service - called Auth0 to manage account - creation and login. -
-- We made this decision because authentication is difficult to write - and maintain securely. We felt that Auth0 was the smoothest and most - secure experience we could offer, especially as a small team of - volunteers{" "} - - 😅 - -
-- - Auth0's terms of service - {" "} - commit to treating your user data as confidential information, not - to be shared with anyone else, and only to be used as part of Dress - to Impress. (The details are in Sections 6 and 7!) -
-- When signing up, Auth0 will ask for a username, password, and email - address. They store your password as a hash (which, - colloquially, is like a one-way encryption), rather than as the - plain password itself. -
-- Some user accounts were created before we moved to Auth0. For those - users, we imported their accounts from our custom database into - Auth0. This included username, password hash, and email address. -
-+ While our classic app{" "} + uses its own authentication, the app you're using now uses a + service called Auth0 to manage + account creation and login. +
++ We made this decision because authentication is difficult to write + and maintain securely. We felt that Auth0 was the smoothest and + most secure experience we could offer, especially as a small team + of volunteers{" "} + + 😅 + +
++ + Auth0's terms of service + {" "} + commit to treating your user data as confidential information, not + to be shared with anyone else, and only to be used as part of + Dress to Impress. (The details are in Sections 6 and 7!) +
++ When signing up, Auth0 will ask for a username, password, and + email address. They store your password as a hash (which, + colloquially, is like a one-way encryption), rather than as the + plain password itself. +
++ Some user accounts were created before we moved to Auth0. For + those users, we imported their accounts from our custom database + into Auth0. This included username, password hash, and email + address. +
+@@ -105,10 +111,12 @@ function PrivacyPolicyPage() {
- We also use Vercel and{" "} - Fastly for web hosting. They - store aggregate usage logs for us, but not any - personally-identifying data. + We also use Linode and{" "} + Fastly for web hosting. Linode + stores our database, and handles most web traffic dealing with + personal data. Personal data also travels through Fastly's servers + temporarily, but they only store aggregate usage logs for us, not + any personally-identifying data.