# \[Archive\] Retrieving Private Key in Unity

**URL:** <https://builder.metamask.io/t/archive-retrieving-private-key-in-unity/2442>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [September 5, 2022, 3:07pm UTC](https://builder.metamask.io/t/archive-retrieving-private-key-in-unity/2442 "2022-09-05T15:07:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![githubdiscussions](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@githubdiscussions](https://builder.metamask.io/u/githubdiscussions)\
**Post date:** [September 5, 2022, 3:07pm UTC](https://builder.metamask.io/t/archive-retrieving-private-key-in-unity/2442/1 "2022-09-05T15:07:58Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **githubdiscussions** on 9/5/2022.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

Hello, I'm trying to retrieve the private key of the user and create a new user in my game using that PK. However, if I create a player that has connected with Google and afterwards, he connects to Web3Auth with, let's say, Discord, the PK is different. How can I retrieve the unique PK of the user? (Hope my question is clear, thanks)

  
   
 Originally posted by: [voodlaiz](https://github.com/voodlaiz)  
   
 Check the discussion at: [https://github.com/orgs/Web3Auth/discussions/549](https://github.com/orgs/Web3Auth/discussions/549)

---

<div class="post-metadata">

**Author:** ![githubdiscussions](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@githubdiscussions](https://builder.metamask.io/u/githubdiscussions)\
**Post date:** [September 5, 2022, 6:04pm UTC](https://builder.metamask.io/t/archive-retrieving-private-key-in-unity/2442/2 "2022-09-05T18:04:02Z")

</div>

Hey [@voodlaiz](https://github.com/voodlaiz),

Thanks for your question.

Talking about your particular question, every private key is uniquely generated for each combination of a `verifier` and `clientId`. Each social provider has a different verifier, which means that the private key will be different for each social provider. Hence, this is causing your Discord PKs to be different from Google PKs.

Coming to a solution for this problem, you can ask our team to create an [aggregate verifier](https://web3auth.io/docs/custom-authentication/verifiers#aggregate-verifiers) for you, where you can provide multiple different login providers and a common fielding linking them. This will enable web3auth to generate the same key for both the social providers. Currently there is no self serve way of creating a aggregate verifier. You can to [get in touch](https://web3auth.io/contact-us.html) with our team and they can help you create one.

  
   
 Originally posted by: [yashovardhan](https://github.com/yashovardhan)