Seald

Build secure-by-design applications with the highest data security standard: end-to-end encryption. Acquired by @OVHcloud in 2026.

[Seald @SealdPrivacy]

@bsinthewild Hey Braden, since you already have authentication with Clerk, could we add a private/public key and offer end-to-end encryption to customers who need it to encrypt files, messages, etc? what do you think?

[Seald @SealdPrivacy]

@stewart what about an end-to-end encrypted Slack version?

[Seald @SealdPrivacy]

@parkerharris are you planning an “end-to-end encrypted” version of Slack for companies in sensitive areas?

[Seald @SealdPrivacy]

@angelgonzaleh With https://t.co/lTzzPagHWn

[Seald @SealdPrivacy]

🚨 Seald is now on GitHub!!

Open-source isn't just a competitive advantage,

It’s a necessity!

And what’s the foundation of cybersecurity? Trust.

How do we build trust? Through transparency.

That’s why Seald has taken the leap.

Our code is now transparent, inviting experts worldwide to contribute to the most advanced end-to-end encryption SDK on the market.

Check it out on GitHub and let’s build a more secure world together! 💪🔒

https://t.co/kx1Uf0oSh6

#OpenSource #CyberSecurity #Encryption #Seald #ZeroTrust #E2EE

[Seald @SealdPrivacy]

Seald x Stream: end-to-end encrypted chat 💬🔒

Here's an article on how to create an end-to-end encrypted chat in your application, even if you're not a security expert.

#encryption #E2EE #chat #privacyByDesign #zeroTrust

https://t.co/ag3COQA57h

[Valentin Deleplace @val_deleplace]

I had a fantastic discussion with @SealdPrivacy about implementation details when implementing End-to-end Encryption #e2ee

The devil is in the details, as often in security and cryptography 😅

Thank you so much @ReboursT and Mehdi, you rock 🤘

[Seald @SealdPrivacy]

@CerfiaFR On se bat chez @SealdHQ pour intégrer du chiffrement de bout-en-bout dans un maximum d'applications.

[Seald @SealdPrivacy]

You can also use it to have your server encrypt data for your users, for example when you collect data for your users from external services.

https://t.co/5DN3MD6war

#encryption #E2EE #coding #privacyByDesign #zeroTrust #tutorial #Seald

[Seald @SealdPrivacy]

#TipOfTheDay 💡: Allow users without Seald identity to encrypt data.

The anonymous encryption SDK enables your application to provide a way for users without Seald identity (unregistered users or users who are not logged-in) to encrypt data for users with a Seald identity.

[Seald @SealdPrivacy]

As well as any subsequent public keys that may be added, following the TOFU (Trust-On-First-Use) paradigm.

#MITM #encryption #E2EE #privacyByDesign #zeroTrust #Seald

[Seald @SealdPrivacy]

#TipOfTheDay 💡: How Seald ensures that no-one can perform a man-in-the-middle attack?

Seald created the "Sig-Chain" technology, an immutable register that records all activities such as adding an identity, joining a group, renewing keys, and more.

[Seald @SealdPrivacy]

This signature chain is unique to each user, safeguarding against the possibility of a man-in-the-middle attack.

The "Sig-Chain" serves as a mechanism that enables the verification of a user's entire set of public keys simultaneously.

[Seald @SealdPrivacy]

In case a user has a very large number of devices, or re-logs in very regularly, we advise you not to create a separate sub-identity for each connection, but simply use the identity stored on SSKS directly.

https://t.co/HHgKYnNybV

#E2EE #coding #zeroTrust #tutorial #identity

[Seald @SealdPrivacy]

#TipOfTheDay 💡: Accelerate the creation of sub-identities.

To accelerate the creation of sub-identities, you can pre-generate the private keys by calling the seald.preGenerateIdentityKeys() function in advance.

[Timothée Rebours @ReboursT]

On voulait migrer à @Sendinblue_fr pour nos emails transactionnels chez @SealdHQ. "C'est français, ça doit être bien niveau vie privée". Que nenni !
Ils ajoutent un pixel espion dans chaque email, et voici ce qu'ils me répondent quand je râle. @CNIL qu'en pensez-vous  ?

[Seald @SealdPrivacy]

Note that « databaseRawKey » must be the Base64 string encoding of a cryptographically random buffer of 64 bytes.

https://t.co/CCPRZ9SMNq

#encryption #privateKey #E2EE #coding #privacyByDesign #zeroTrust #tutorial #seald

[Seald @SealdPrivacy]

#TipOfTheDay 💡: Improve the speed of a Seald identity instantiation.

To improve the speed of instantiation, you can use « databaseRawKey » instead of « databaseKey ».

This avoids deriving the « databaseKey » with « scrypt » which is CPU intensive, especially on mobile devices.

[Seald @SealdPrivacy]

@KhaderMurtaja @VirgilSecurity ☝️

[Seald @SealdPrivacy]

End-to-end encryption explained 🛡