Product

Features

Inkrypt does one thing: it turns text into ciphertext in your browser before anything is transmitted, and gives you controls over how long that ciphertext survives. Each page below explains one part of that, including the trade-offs it carries.

Most product feature lists are a set of claims. These pages are written to be checkable: they name the exact algorithms and parameters in use, describe what our servers actually store, and state plainly what each feature does not protect you from.

If you only read one, read the security architecture page — it is the document the rest of these are consistent with.

Encrypted notes

Write a note that is encrypted in your browser before it is stored. The server holds ciphertext it cannot read.

Password protection

The password never leaves your browser. It is stretched into a 256-bit key with 310,000 rounds of PBKDF2.

Self-destructing notes

Set a note to be destroyed after a time limit or a number of views. Shrinks the window, not the recipient's memory.

Secure link sharing

Generate a share link with its own expiry and view limit. The link alone is not enough to read the note.

Zero-knowledge

The server never holds a decryption key. Not as a policy — as an architectural property you can check.

Client-side encryption

Encryption runs on your device, before the first network request. The plaintext never crosses the wire.

AES-256-GCM

AES-256 in GCM mode: authenticated encryption that detects tampering rather than silently decrypting corrupted data.

What Inkrypt deliberately does not do

A feature list is only honest if it includes the absences. Each of these is a consequence of the encryption design rather than a gap in the roadmap — building them would require us to be able to read your notes.

No password recovery. We hold no key, so a forgotten password means a permanently unreadable note.
No search across your notes. Indexing text requires reading it; we only ever hold ciphertext.
No accounts or note list. Nothing links your notes to each other or to you — which also means nothing helps you find them again.
No file uploads. Text only, today.
No public API. An API that accepted plaintext would break the entire model.

Frequently asked questions

Is Inkrypt free to use?

Yes. Every feature described on these pages is available with no account, no payment and no trial period. There is no paid tier gating encryption strength or expiry options.

Do I need to create an account?

No. There is no signup at all — no email address, no profile, no password to remember beyond the one you set on each individual note.

Can Inkrypt store files or images?

Not currently. Inkrypt handles text: notes, credentials, code snippets and long-form documents. Binary uploads are not supported.

Which browsers are supported?

Any modern browser with the Web Crypto API — current versions of Chrome, Firefox, Safari and Edge on desktop and mobile. JavaScript must be enabled, since encryption runs in the browser.

Write your first encrypted note

No account, no email address, no download. Type a note, set a password, and share the link.

Open the notepad