Encrypted metadata

[chronark]

Preliminary Checks

• I have reviewed https://unkey.com/docs for existing features that would solve my problem

• I have searched for existing feature requests: https://github.com/unkeyed/unkey/issues

• This issue is not a question, general help request, or anything other than a feature request directly related to Unkey. Please ask questions in our Discord community: https://unkey.com/discord.

Is your feature request related to a problem? Please describe.

Currently meta data is not encrypted and stores as plain text in the db, which is not suitable to store PII or other secrets.

Describe the solution

I have 2 ideas for this:

1. A flag to toggle encryption of the existing meta field
2. A new encryptedMeta field that can be used alongside the original meta, similar to how clerk has private and public metadata

Describe alternatives you have considered (if any)

No response

Additional context

No response

[linear]

ENG-1089 Encrypted metadata

[mvares]

@chronark, this could be divided into two parts: unsafe metadata and metadata

[chronark]

why "unsafe" over "encrypted"?

[mvares]

why "unsafe" over "encrypted"?

Really, "encrypted" is better

[harshsbhat]

@chronark So basically we need to add it in both the unkey SDK and the platform toggle button to encrypt it. Am I right?

[harshsbhat]

So if I am right we need to add one more toggle button here saying "Encrypt Metadata". Also similar thing for the SDK

@chronark So basically we need to add it in both the unkey SDK and the platform toggle button to encrypt it. Am I right?

[chronark]

I'd prefer a second card entirely