# Login

<figure><img src="/files/BIkbaMdhektD2stwJyYP" alt=""><figcaption></figcaption></figure>

I decided that Molly will *not* ask for a phone number or email during account creation. This is for the user's privacy. Whenever I download an app and it asks me for an email I dread <mark style="color:blue;">a.)</mark> giving out my email to yet another service and being identified by said email and <mark style="color:green;">b.)</mark> the inevitable thirty emails that comes from the service.&#x20;

Molly instead asks the user for a username and a personal identification number (PIN). The intention of Molly is to store data locally which means the username does not have to be unique, per se. This has the added benefit that in case of a data-breach of any kind the login data a hacker receive would not be interoperable with most other services, further exasperating the breach. Given that Molly is a healthcare technology, privacy for the user is a must, both for them and against nefarious actors.\
\
Should a user be unable to recall their PIN or username, Molly will recommend the user to create a new account and explains to the user *why* this is the protocol that exists.\
\
If the user successfully enters their username and PIN, Molly will take them to the 🏠**Home Screen**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://molly.gitbook.io/molly/login.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.