# Hybrid Custody

**URL:** <https://forum.flow.com/t/hybrid-custody/4016>\
**Category:** Product & Ideas\
**Tags:** account-model\
**Created:** [January 5, 2023, 10:03pm UTC](https://forum.flow.com/t/hybrid-custody/4016 "2023-01-05T22:03:53Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![bluesign](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.flow.com/bluesign/32/1359_2.png) [@bluesign](https://forum.flow.com/u/bluesign)\
**Post date:** [January 9, 2023, 9:25am UTC](https://forum.flow.com/t/hybrid-custody/4016/8 "2023-01-09T09:25:01Z")

</div>

> [@kate\_sills](#):
>
> it. I understand that when the user “graduates”, they’ll have their own self-custody account with a separate private key that the application knows nothing about that will be the new parent of the app-custody account, but what’s happening with the app-custody account private key?

I imagined a bit different, app-custody account is dapp’s and created for user as a sandbox, later when I have my account, then I can move stuff from there (with authaccount capability)

Technically I can add my own key and remove dapp’s key from the account too. ( if I am adventurous )

---

_[View the full topic](https://forum.flow.com/t/hybrid-custody/4016)._