# Implement Bubble "Secrets" **URL:** \ **Category:** Idea\ **Created:** [October 17, 2018, 7:33am UTC](https://forum.bubble.io/t/implement-bubble-secrets/40172 "2018-10-17T07:33:05Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![NigelG](https://avatars.discourse-cdn.com/v4/letter/n/ea5d25/32.png) [@NigelG](https://forum.bubble.io/u/NigelG)\ **Post date:** [October 17, 2018, 7:33am UTC](https://forum.bubble.io/t/implement-bubble-secrets/40172/1 "2018-10-17T07:33:05Z")
AWS has a “Secrets Manager” for holding API keys. And I have recently noticed that [webstask.io](http://webstask.io) has also implemented a secrets manager. I like webtask for security stuff, as it allows me to separate out the more sensitive API keys. Even if someone gets into my Bubble App, the API keys for login authorisation are elsewhere. It would be good if Bubble were to implement a way to store API keys in the same way it does the access token for social logins. So well way from the “main” app. ---
**Author:** ![gregoryjohn](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/gregoryjohn/32/209419_2.png) [@gregoryjohn](https://forum.bubble.io/u/gregoryjohn)\ **Post date:** [October 17, 2018, 7:37am UTC](https://forum.bubble.io/t/implement-bubble-secrets/40172/2 "2018-10-17T07:37:06Z")
Really like this idea. I’m working on a Fintech application at the moment and having my Stripe keys available in plain text is defo risky. 2FA was a great idea but we could improve on that. ---
**Author:** ![AliFarahat](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/alifarahat/32/189604_2.png) [@AliFarahat](https://forum.bubble.io/u/AliFarahat)\ **Post date:** [October 17, 2018, 1:42pm UTC](https://forum.bubble.io/t/implement-bubble-secrets/40172/3 "2018-10-17T13:42:18Z")
Hey @NigelG That’s a great idea. Would love to see this especially useful when hiring a freelancer or have a member of the team access the app ---
**Author:** ![NigelG](https://avatars.discourse-cdn.com/v4/letter/n/ea5d25/32.png) [@NigelG](https://forum.bubble.io/u/NigelG)\ **Post date:** [October 28, 2018, 11:44am UTC](https://forum.bubble.io/t/implement-bubble-secrets/40172/4 "2018-10-28T11:44:23Z")
@emmanuel - what are you thoughts on this ? My use case is storing API secrets. Currently this is implemented by storing the client id and secret elsewhere, and passing the token (so no system stores everything it needs for access). But ideally I would like to keep this in Bubble, but under “lock and key”. ---
**Author:** ![emmanuel](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/emmanuel/32/27657_2.png) [@emmanuel](https://forum.bubble.io/u/emmanuel)\ **Post date:** [October 29, 2018, 1:35pm UTC](https://forum.bubble.io/t/implement-bubble-secrets/40172/5 "2018-10-29T13:35:33Z")
If the keys are made private (for instance, when defining a plugin), they are stored in a part of the application that never is sent to the client in run mode, so it’s safe. Wouldn’t it do that you need? ---
**Author:** ![NigelG](https://avatars.discourse-cdn.com/v4/letter/n/ea5d25/32.png) [@NigelG](https://forum.bubble.io/u/NigelG)\ **Post date:** [October 30, 2018, 10:05am UTC](https://forum.bubble.io/t/implement-bubble-secrets/40172/6 "2018-10-30T10:05:40Z")
Yes, that is great for hiding the keys from the client. But it would be really good if the keys could be kept away from the API connector as well. So that developers can see the parameters but not the keys ? ---
**Author:** ![tgmoron](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/tgmoron/32/111382_2.png) [@tgmoron](https://forum.bubble.io/u/tgmoron)\ **Post date:** [November 3, 2021, 3:09am UTC](https://forum.bubble.io/t/implement-bubble-secrets/40172/7 "2021-11-03T03:09:47Z")
Is there any updates on this? ---
**Author:** ![hoke](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/hoke/32/150258_2.png) [@hoke](https://forum.bubble.io/u/hoke)\ **Post date:** [December 23, 2022, 5:47pm UTC](https://forum.bubble.io/t/implement-bubble-secrets/40172/8 "2022-12-23T17:47:01Z")
follow