Skip to content
Sealpaste

Delete all recent work?

This removes the 0 items saved in this browser. Your settings stay.

Stop saving recent work?

New work won't be saved in this browser. The 0 items already saved can stay or go.

About Sealpaste

Sealpaste is a set of developer tools for JSON, text, code, tokens and IDs. They run in your browser, so what you paste is worked on in this tab.

Who makes it

Sealpaste is made by Fruit Basket Labs, an independent software studio that builds one site for each kind of job. The company’s details are on its Company page.

How “not uploaded” is enforced

Every page is sent with a Content Security Policy that says connect-src 'self'. With it, the browser itself refuses any request from the page to another site, whatever the page’s code tries. Requests to Sealpaste’s own address are these four:

  • The tool-use counter: which tool, which action and a count. Never what you typed.
  • A share link, only when you press Share. It is locked in your browser with your password first, so the server keeps data it can’t read.
  • An error report: fixed fields such as the page and the kind of error, never the message or your input.
  • A report when the browser blocks something our security policy forbids: the blocked address and rule, never your text.

Check it yourself

Open your browser’s developer tools, choose Network, and use a tool: nothing you paste appears in a request unless you press Share. To read the policy itself:

curl -sI https://sealpaste.com | grep -i content-security-policy

How a paste is handled, and what a key in it triggers: Is it safe to paste? What is kept in this browser and measured: Privacy.

How the tools are checked

Each tool has its own tests, and the examples on its page are checked against the tool’s own output. Where a standard publishes test values (hashes, HMAC, JWT, UUID), the tests use them. A wrong result is a bug: tell us on the Contact page.