Content
@
0 reply
0 recast
0 reaction
rish
@rish
if using Neynar managed signers (separate from SIWN) to create signers under your brand, you can now *sponsor* those signers Users will see signers under your brand, but you pay for them instead of the user h/t @shreyas-chorge, @avneesh 🪐 PS - no changes to SIWN as part of this, reach out if qs bit.ly/4czybHi
2 replies
6 recasts
26 reactions
Jai
@jaivsdawrld
Hmm. Which signer would you say will be the most suitable for a project that requires custom branding but avoids the complexity of storage management?
1 reply
0 recast
0 reaction
rish
@rish
"neynar managed signers" https://docs.neynar.com/docs/which-signer-should-you-use-and-why#neynar-managed-signers you only need to store uuids, we manage the underlying signer for you
1 reply
0 recast
0 reaction
Jai
@jaivsdawrld
Okay that makes sense but how do you then ensure data privacy and security in this managed setup? Just asking for transparency.
1 reply
0 recast
0 reaction
rish
@rish
wdym by data privacy? the content is on an open network and the signers are registered on the protocol under your brand so anyone can look at the protocol and tell what was written through signers registered to you. what is the data you're looking to keep private? the signers are stored securely on our end and are never transported over the wire. only interaction is through UUIDs. UUIDs can be rotated if needed and are tied to your API key so if needed, you can simply rotate your API key from the dev portal and that will kill access via your previous key
1 reply
0 recast
1 reaction
Jai
@jaivsdawrld
Sorry I’m just replying. I was thinking the UUIDs is data that needs to be protected. Hence why I asked bout data privacy in regards to that.
0 reply
0 recast
0 reaction
