Absolutely. End-to-end encryption will always be high on our roadmap.

At the same time, we believe in a world where users shouldn’t have to encrypt everything just to protect themselves from the platform they’re using. Privacy should start with ethical intent, not just technical features. We don’t scan, monetize, or analyze user data. Not because it’s difficult, but because it’s wrong.

We’ve been exploring the idea of adding a chat service. But we haven’t yet decided which protocol would provide the most value for most people.

Right now, we’re considering XMPP and Matrix — both are solid, privacy-respecting options. Our goal is to offer something that lets people communicate with their existing contacts, not start from scratch.

We’d love your input: what would you actually use? What works best in your daily setup?

What’s the encryption situation for personal side of the service ie email, docs etc?

Currently, InlineStyle uses encryption in transit (TLS) across all services. We’re working on implementing encryption at rest, to ensure data remains inaccessible even in the event of a server breach.

As for end-to-end encryption (E2EE):

• Email: Not E2EE by default, but we support GPG for users who wish to secure their messages independently.
• Docs: Currently no E2EE, and we don’t plan to add it for collaborative editing (due to the technical limitations it brings).
• We are planning to introduce a dedicated “Locker” feature, where users will be able to store files with stronger protection, albeit without collaboration features.

If strong E2EE is essential to your workflow, tools like Proton Mail and Proton Drive are great choices. Our focus with InlineStyle is more on access to fediverse content and everyday convenience: a suite that works out of the box for people looking for alternatives without giving up too much convenience.