> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/faqs/end-customer-faqs/i-received-a-perkville-password-reset-email-i-didnt-request.-what-should-i-do.md).

# I received a Perkville password-reset email I didn't request. What should I do?

If you did not request a Perkville password reset, you can safely ignore the email. **No change is made to your account unless the reset link is used.**

If you would like to take extra precautions, you can:

* [Reset your Perkville password](https://docs.perkville.com/faqs/managing-emails-and-names/how-do-i-reset-my-password.md) to a strong, unique password that you do not use anywhere else.
* Check the email addresses associated with your Perkville account and make sure they belong to you.
* Review your recent reward redemption activity and contact the applicable business if anything looks unfamiliar.
* Secure your email account as well, including changing its password if you have reason to believe it may be compromised.

For more guidance on choosing a secure password, see [Protecting against password reuse](https://docs.perkville.com/faqs/miscellaneous/protecting-against-password-reuse.md).

If you believe your email address is associated with a Perkville account you did not create and you want the Perkville account and associated personal data permanently deleted, see [How do I delete my Perkville account and personal data?](https://docs.perkville.com/faqs/end-customer-faqs/how-do-i-delete-my-perkville-account-and-personal-data.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/faqs/end-customer-faqs/i-received-a-perkville-password-reset-email-i-didnt-request.-what-should-i-do.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
