# Rekeying use case

**URL:** <https://forum.algorand.co/t/rekeying-use-case/4547>\
**Category:** General\
**Tags:** rekeying\
**Created:** [October 14, 2021, 2:29pm UTC](https://forum.algorand.co/t/rekeying-use-case/4547 "2021-10-14T14:29:12Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Brad](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/brad/32/677_2.png) [@Brad](https://forum.algorand.co/u/Brad)\
**Post date:** [October 14, 2021, 2:29pm UTC](https://forum.algorand.co/t/rekeying-use-case/4547/1 "2021-10-14T14:29:12Z")

</div>

Hello, we are developing an application that will be used by hundreds or potentially thousands of users that have low technical literacy.

Wallets need to be non-custodial but we need the option to help users recover their wallets if they lose their private keys, which inevitably will happen.

Rekeying seems like a good option. However…

1. If rekeying requires the storage of a master key that can rekey other private keys would this then classify as a form of custodianship of funds?

2. Does rekeying present a security concern since the master key can rekey other private keys? How is that security concern mitigated?

I’m not a developer so apologies if these questions are easily answered via the dev portal, which I don’t fully understand!

Advanced thanks to any feedback

Brad

---

_[View the full topic](https://forum.algorand.co/t/rekeying-use-case/4547)._