 out a new design for Pages (FKA documents) on Skiff. As tens of thousands of individuals and teams have signed up to use Skiff, we’ve received thousands of feature ideas and support requests via our 

. Many of these requests center on the same theme: making it easier to find and organize your information on Skiff.

Now, pages are structured with three new features: Titles, icons, and descriptions.

New page titles synchronize with your dashboard and file tree, making it easier for you to organize, find, and share pages in your workspace.

Icons enable creative customization for every page in Skiff. Click the icon at the top of every page (or to the left of page titles in the sidebar) to customize the page icon. Choose the icon and color that best fit your work.

Optional page descriptions provide additional context and information. To edit a page description, select the page’s title, and an area for description text will open. From there, add any relevant information, context, or descriptors to the page.

Comments or questions? Join our Discord here → 

So much of the difficulty with privacy and security

 products has little to do with the privacy or security itself. There’s nothing about verifying signatures or X25519 that warrants a clunky interface. And yet, we’re left with green text on black backgrounds, pop-ups that exist to dismiss, and tomes that describe arcane log in processes.

Security certainly adds new constraints. It can make good design harder. But too often, a carelessness towards design precludes the usefulness of the security in the first place. What’s the use of PGP, if your friend sends the wrong key by mistake anyway? (

Even PGP's creator got fed up with its design

Bringing user-friendly design to security matters. Technical skills cannot be a prerequisite to digital security. The people whose lives and reputations depend on it are rarely cryptographers or engineers themselves. And in a world of instant checkouts and auto-magic links even minor inconveniences can be a dealbreaker. We need to stop asking whether people care about privacy and start asking whether we, as designers and engineers, care enough about how people interact with privacy. If we’re truly to make the internet private for everyone –as we have set out to do at Skiff– usability must be front and center.

At Skiff, we’ve built a privacy-first platform for collaboration. Security is built into every feature and aspect of our product from onboarding to the emojis and the text editor. That means we've had to face usability challenges with almost everything we've built. We're still learning but along the way we've come up with a framework to help guide us. For each feature, we ask ourselves, does it:

anticipate, not dictate, a user’s actions?

make insecure behaviors difficult to perform?

require no extra effort compared to a less secure alternative?

reinforce an emotional sense of security?

People don't always follow instructions (no matter how pretty). They do what's convenient.

The principles behind these questions are hopefully straightforward: for 1 and 2, it's that users will do what's convenient regardless of any instructions; they set the constraints and decide the path, not us. For 3 and 4 – while users set the path, there's still a lot we can do to frame and organize it; it's our job to re-pave common actions and fence off undesirable ones (see image above). For 5, it's that any extra time cost should be put on us during development, not on our users; otherwise, it's impossible to be a true alternative. And 6 – for users to intuitively trust the product, the interface must reflect the underlying security.

Applying this framework to a real product is 

. Consider our account recovery process. When you forget your password on Skiff, there’s not much we can do since we don’t store passwords in any form on our servers (we use zero-knowledge proofs for authentication). Users instead need to generate a random symmetric key that they store physically. This can reduce account safety to a crumbled up piece of paper and lead to a bad experience for forgetful users.

Skiff’s design and security teams worked closely together to make this process smoother and more secure. Our security team integrated 

 to split the recovery key into three pieces. Now, one key is stored on paper, another in the browser, and a third is encrypted and stored on the server. To recover an account, two out of the three shares must be combined. This ensures that at no point can the server decrypt user data, while still giving forgetful users a backup on their browser.

Our design team, meanwhile, updated the onboarding UX to make it nearly impossible for a user to misconfigure their recovery keys. This all comes together in the most boring way possible (we hope). When you forget your password, you check your email inbox and set a new password. It just works. For all the extra implementation details, the user actually has to do 

Skiff’s public link feature follows a similar template. It implements a novel cryptographic protocol to ensure Skiff never has access to the link or document. But as far as users are concerned it’s just a toggle – same as any site.

Make no mistake – secure design isn’t always about invisibility. Being conspicuous serves a critical purpose too. Responsive indicators, well-placed labels, even sounds and animations can create a sense of security. As long as the design is honest, these components can reinforce and validate the actual security.

Other more subtle factors also play a role. When it comes to tone and voice, we’re careful to avoid exclamations, excessive emojis, and condescending descriptors like “my documents.” It's hard to trust a platform, if it's too playful.

We still have some pixels to push (like the ones in the envelope icon above).

Down to the last pixel, we also strive for every element to be aligned, centered, and perfectly set. It's not out of unbridled perfectionism. A single visual artifact puts in question all the things you can’t see. And in aggregate, it's unsettling even if subtle.

There’s a reason Skiff doesn’t default to dark mode. As tempting as monospace type and command-line interfaces can be, they alienate often more than they help. The initial coolness of feeling like a hacker might build some sense of security, but it's short-lived. Fun becomes gimmicky. And over time, these references can detach how the product looks from the how the product actually works.

We're currently putting these principles to work at Skiff, but there's still much to improve.
‍
If you’re working on your own security projects, feel free to fork and contribute to our open source design system: 

Finally, for product engineers and designers excited by the intersection of security and usability – if you want to help us craft new design patterns for a privacy-first future, 

Secure Design Patterns

allows Skiff users to effortlessly collaborate on documents by sharing end-to-end encrypted links. This enables their shared collaborators - including those without Skiff accounts - to work together, view, and edit files with end-to-end encryption.

Public, end-to-end encrypted link sharing allows users to collaborate on a document while maintaining complete privacy: Even users without Skiff accounts can save and edit the file. At all times, the link and file remain end-to-end encrypted, and Skiff never has access to the document or even the link itself. Furthermore, editing or viewing permissions can be revoked from the link at any time, to further protect control and the shared document.

Sharing a document publicly is straightforward and described below:

Click the "Share" button in the security toolbar

Under "Public Link" select the option in the dropdown that says "Anyone with the Link"

• This allows all users with the link— including those without Skiff accounts— to access the document
• Link sharing can be turned off by the user at any time to revoke access to the document

4. Toggle between "can view" and "can edit" to change the permission level you want to give to users

• These permissions can be changed at any time allowing document owners to revoke editing and/or viewing access
5. Copy the link and share it with anyone you like (note: we always recommend doing so over a secure communication channel, )
6. Based on the permission level you selected, users will be able to simply view, or directly edit the file

Users accessing a view-only document via the link won't see other users on the document, and they won't be able to edit or share the document. If the original user disables link sharing, or unshares another shared user, the link will expire, and all users using the link will no longer see the document.

Users who are link shared with editing permissions on will be able to edit the document in real-time and save new versions. Just like current document editing, all users— logged in and not logged in — can see edits in real time. While logged in users will show up as their username, when anonymous editors are active and/or editing, we generate a random username from a list of fruit names, preceded by 'anonymous' and a rank (Anonymous-Colonel-Elderberry).

Public users will not be able to view other online or shared users, and thus cannot share or change permissions on the document. At any time if the original user changes, the permissions (turns off link sharing, upgrades users to editors, etc.), the document and original link will expire and the user will need to be sent the new link in order to download the document again.

To better understand how anonymous editing works, let's consider Alice (our Skiff user), and her friend Bob (not a Skiff user).

Currently, our E2EE link sharing model already allows users without accounts to access documents shared via links. As detailed in Skiff's 

, a secure link to share a document is generated by combining the document identifier and a client-side generated random encryption key. This random link encryption key is used to encrypt the document's session key, which is used to encrypt the document. When Alice shares the link with Bob, the server first verifies that Bob has the correct link key (without the server ever needing access to the actual link encryption key), and subsequently sends the encrypted document key to Bob (which can be decrypted with the link key). If Bob is simply listed as a viewer on the document, we simply stop here.

If the shareable link is given editing permission, Bob uses a temporary authentication token to listen and send document updates and maintain real-time document state. If Bob had a Skiff account, we would create a token that cryptographically authenticates Bob's user information. Instead, because Bob is only trying to access and edit a single document without an account, we embed information about the document and Bob's access method into the token itself. This temporary access token is used while Bob listens and sends updates to the document.

Every time Bob sends an update, we verify that this temporary authentication method maintains a cryptographically valid document identifier for this editing session. If so, Bob is allowed to both send and listen to updates for a given document. In order to save the publicly editable document, we verify Bob's token contains the appropriate document identifier, and proceed to save the link-shared document.

Link sharing - which is widely used by Skiff users to work freely and collaborate securely - represents a critical piece of our usable, privacy-first platform.

Secure Public Links

, Notion is not end-to-end encrypted. Almost all productivity apps that consumers use today were not built with security in mind, including 

, Google Workspace, and other note-taking apps. Although they have invested in better security practices, data is generally stored with the most basic levels of symmetric encryption, which can leave sensitive information open to exploitation from employees, service providers, or other hackers and malicious actors.

This has led to some catastrophic data breaches, such as Evernote’s 

 that exposed millions of user accounts, including consumers’ most sensitive information stored inside their notes. For some people, this could be years of personal notes, memories, interviews, work information, health tracking, or financial information that could lead to fraud or identity theft exposed (not to mention significant personal or professional consequences). With a variety of options for writing, collaborating, and sharing online, consumers have prioritized the security and encryption of their cloud products.

Notion has become an all-in-one workspace for numerous different consumer needs, from writing wikis and todo lists to personal notes and project management. However, given this level of critical data stored inside the product, end-to-end encryption has emerged as a clear need for any product entrusted with our life’s notes and thoughts. Read on to learn more about Notion’s security practices and some excellent, consumer friendly end-to-end encrypted products.

End-to-end encryption is a type of encryption where only the communicating parties 

 and read messages, files, or notes. It works by each party generating a secret key (private key) that only they know as well as a set of public keys that can be shared with other individuals. Users’ public keys are then used to encrypt messages, while private keys are used to decrypt messages, files, or data once encrypted. In an end-to-end encrypted product, only users, and not service providers or anyone else, have access to their private key, ensuring that any encrypted data can only be decrypted on a user’s device. This has led to the emergence of the terms “

 encryption” to describe this security model.

End-to-end encryption is a different paradigm for building products, wherein users maintain all control over their data. As a result, companies have had to redesign the way products work to respect privacy out of the box. This includes writing new search algorithms that work with client-side encryption but can still perform fast, free full text search over all of a user’s data.

What is the difference between encryption and end-to-end encryption?

is a type of encryption where only the sender and receiver can see the contents of a message, or of files and notes uploaded to the cloud. This is in contrast to “encryption” as a broader term, where the contents of the message can be seen by anyone who has the encryption key - generally including a service provider. In this case, because Notion advertises “encryption” and “soc2 compliance” but not “end-to-end encryption,” this means that every Notion user is trusting Notion employees and policies to not access, improperly use, or arbitrarily remove their content.

Most productivity apps, including Notion, market security controls and encryption - generally specifying that data is secured using 

 bit encryption. However, this type of encryption is considered standard across the industry and does not add any technical guarantees that another party - Notion employees, hackers in the event of a data breach, or law enforcement - could access your notes and information.

As a result, end-to-end encryption is considered more secure because it prevents all third-parties from being able to access the contents of everything you write. Given its prevalence in messaging (see more on this below, or 

), end-to-end encryption has become a required privacy standard for all consumer communication and productivity apps.

Without end-to-end encryption, it’s critical to closely read a company’s terms of service and privacy policy. For example, Notion’s privacy policy has an extremely 

 detailing different ways your personal information might be used, or how it could be shared with third parties. This could be deeply concerning, as a company’s security policies will dictate how your life’s work stored in your Notion workspace could be shared. Even if it isn’t monetized, the risks to your sensitive information remain high without end-to-end encryption.

End-to-end encryption has become a standard in all messaging products today, including 

. This ensures that only senders and recipients can see the content of their messages, and not cloud providers or device makers.

End-to-end encryption is also a common security need for cloud storage providers, where the costs of exposing customer data, credit card information, or other sensitive information could be extremely high. Popular end-to-end encrypted cloud storage providers include Skiff and 

, whereas Microsoft OneDrive, Dropbox, and Google Drive are not end-to-end encrypted.

In some of the most alarming cases of non end-to-end encrypted providers hurting users, individuals of some productivity apps have been de-platformed and kicked out of their accounts, such as when the creator of popular TV show 

 was unexpectedly and involuntarily banned from Dropbox, or a well known journalist was removed from their 

. As a result, end-to-end encryption empowers individuals to work more creatively, freely, and effectively knowing that their personal information is kept completely private.

If you’re looking for an alternative to Notion that is more private and uses end-to-encryption, or client-side encryption, consider these products below.

 is a multi-device product for writing notes. Generally perceived as a replacement to products like Apple Notes, Standard Notes maintains highly rated native applications (iOS, Android, and more), and the company has had good transparency on their product and security features.

 is an open-source note-taking app that has become increasingly popular for consumers. Beyond simply writing, Joplin focuses on sharing features for collaborating on notes with others. Unlike Standard Notes and Skiff, however, Joplin is 

 end-to-end encrypted by default; this can be configured from inside the app. As a result, consumers looking for a simpler experience may select one of the other options.

: Skiff is a privacy-first, end-to-end encrypted workspace with products for notes, file sharing, cloud storage, and email. 

 a macOS app and mobile apps on iOS and Android for both their Pages product (notes, wikis, file storage and sharing) as well as for Skiff Mail. Skiff offers 10 GB of storage on their free plan, as well as an integrated workspace product for writing, collaboration, and sharing privately.

End-to-end encryption (E2EE) provides much-needed privacy and security benefits to consumers without any significant downsides. E2EE keeps your information private to you alone, preventing the risks from data breaches or service provider employees accessing your account information. Given how much personal information is stored in a Notion workspace, Evernote account, or note-taking app, it is critical to choose a trustworthy, end-to-end encrypted provider and join millions of consumers making this critical shift.

Is Notion end-to-end encrypted?

While Web3 might seem like a general term that characterize an abstruse set of technology, infrastructure, and finance, it may transform and re-shape every aspect of the world’s technological stack. Web3 encompasses many different areas, from cryptocurrencies and the metaverse, to decentralized autonomous organizations (DAOs) and new layer-one blockchains. A key underlying philosophy of Web3 is the core ideological belief of moving control of platforms, information, and services away from a centralized authority, and instead spreading this authority in a democratic way, where participants, creators, and individuals can govern organizations and providers, from new email services to storage layers.

This may mean owners of a particular token get to vote on any new changes to the currency’s governing protocol, such as the 

 (ENS), or creators of NFTs being compensated for their work without requiring traditional media and organizations to earn exposure and make a living.

The possibilities of Web3 are endless - partly driven by the space’s ability to attract talent and teams all 

 - in particular, Asia (Singapore/Taiwan), North America (New York and California), and Europe (Germany and more).

There is no playbook on what a successful Web3 company looks like, where there team lives, or how they operate, but there are several common practices that have been adopted by the ever-growing number of web3 companies and organizations.

There have always been hubs where certain industries have concentrated. For example, financial services is largely concentrated in New York’s 

, entertainment in Los Angeles, and tech in Silicon Valley. Web3 startups are not born in any geographical location and instead share one important similarity: They are all almost always working in distributed teams. Distributed teams help Web3 companies leverage employees and team members not only in different cities but often even in different countries and time zones, from New York and Paris to Warsaw and Auckland.

The biggest advantage to distributed teams is their ability to attract the best talent no matter an individual’s geographic location. The cons include coordination and communication challenges arising from coworkers living in different time zones - a real and serious issue that can be alleviated or mitigated by using the right tools. 

GitLab has an excellent and comprehensive guide

What productivity tools Web3 companies use

Any Web3 company needs a complete software stack to operate successfully. Requisite needs include the ability to communicate efficiently and effectively across an organization, write and collaborate on projects synchronously and asynchronously, and the ability to store company files for easy retrieval at a future date. Many teams also opt for 

, and tools that allow for community management functionality may be necessary.

There are no shortage of Web2 productivity apps, email solutions, and file storage products that accomplish this. For communicating efficiently and effectively, millions of teams opt for Slack, Gmail, or the Microsoft suite. For collaborating synchronously and asynchronously: Google Docs, Notion, 

. For storing files on the cloud: Dropbox, Google Drive, and Box are popular.

Yet, these tools generally fail to suit the myriad needs of distributed teams working on complex technical problems.

Firstly, these companies’ modus operandi is antithetical to the philosophy and beliefs that underpin the distributed web. Most companies listed above store your data on centralized servers with minimal to no oversight. They also frequently monetize and collect your data and sell it to third parties, or sell ads directly to you - all not ideal traits for teams that want to move towards democratized and decentralized organizations and collectives. For example, Gmail is not an end-to-end encrypted communication platform, and all message or email content (as well as all attachments) are accessible by the technology provider.

Finally, distributed teams using a combination of the products above may constantly have to context switch to stay productive during the workday. Swapping from a traditional email product (Gmail/Outlook) to Discord, Notion, and Dropbox can be a dizzying experience which undermines focus, efficiency and the overall enjoyment of any work process. It also becomes challenging for teams to remember where the most critical information is stored.

While many Web3 companies still use a combination the products listed above, numerous organizations have migrated to using Skiff Mail, Pages, and Drive for communication and collaboration.

Skiff: Privacy-first, Web3-native collaboration

Skiff is a comprehensive communication and collaboration ecosystem that integrates end-to-end encryption, complete privacy, and powerful collaboration into an easy-to-use experience. Today, Skiff’s product suite includes:

 - Privacy-first, end-to-end encrypted Web3 native mail for email and wallet email.

 - Privacy-first, end-to-end-encrypted real time collaboration for notes, wikis, and documents.

 - Privacy-first, end-to-end encrypted file storage that is also integrated with IPFS (distributed file storage).

 (as well through an iOS, Android, and MacOS app) make Skiff the ideal collaboration tool for Web3 companies.

We designed Skiff to meet all the most critical needs mentioned above for distributed and high-functioning teams. These include synchronizing information and communication into one platform, keeping all sensitive data private and end-to-end encrypted, and enabling seamless real-time collaboration.

 lets teams communicate internally and externally with ease and security. Every email sent between Skiff Mail users is end-to-end encrypted, and, even for unencrypted external providers, Skiff never stores a copy of any messages sent. Furthermore, Skiff Mail is available on iOS and Android, so co-workers never need to worry about missing any important email.

 empowers co-workers to collaborate both in real-time as well as asynchronously on a fully end-to-end encrypted feature-rich document editor. Using comments, mentions, and replies, team members can have engaging discussions over a period of days.

 enables individuals and companies companies to store files of all types on an end-to-end encrypted platform that is also fully compatible with the InterPlanetaryFileSystem (IPFS). IPFS storage ensures that files and data are not stored in any centralized server, increasing censorship resistance and data accessibility. For many teams around the world, particularly in Web3, this is a necessity.

Skiff’s full suite of products also solves the two big issues that Web3 companies may experience using a chaotic combination of Web2 tools: A lack of privacy and the challenges tracking information across numerous tools.

In contrast, Skiff is built on a privacy-first platform that uses public and private keys for encryption and identity. Skiff allows teams to store data decentralized on IPFS, and allows users to sign-up, log-in, and link crypto wallet to their Skiff account. Skiff currently supports MetaMask, 

, with more coming soon. Unlike typical email providers, wallet addresses are a first-class form of communication on Skiff.

Skiff also allows Web3 companies to switch seamlessly and effortlessly between its products, meaning that companies no longer have to jump across several different products. Furthermore, this enables the cost-saving measures of paying for a single subscription for multiple products. Today, the world is only at the beginning of Web3, but Skiff is working tirelessly to provide the best collaboration platforms for the future.

, or watch some of our video tutorials on our YouTube channel 

New page design

Titles

Icons

Descriptions

Secure Design Patterns

Secure Public Links

Is Notion end-to-end encrypted?

Why Web3 companies use Skiff Mail, Pages, Drive

Get access to Skiff

Become a part of our 100,000+ community.