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.
Read morePassword protection
The password never leaves your browser. It is stretched into a 256-bit key with 310,000 rounds of PBKDF2.
Read moreSelf-destructing notes
Set a share to stop working after a time limit or a number of views. Shrinks the window, not the recipient's memory.
Read moreSecure link sharing
Generate a share link with its own expiry and view limit, and choose whether the key travels in the link or as a separate password.
Read moreZero-knowledge
The server never holds a decryption key. Not as a policy — as an architectural property you can check.
Read moreClient-side encryption
Encryption runs on your device, before the first network request. The plaintext never crosses the wire.
Read moreAES-256-GCM
AES-256 in GCM mode: authenticated encryption that detects tampering rather than silently decrypting corrupted data.
Read moreWhat 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.
How people use it
These are scenarios rather than customer stories — we collect no reviews and publish no testimonials. Each page walks through where secrets usually leak in that setting, and what changes when the handover happens through an encrypted note.
- DevelopersHand over API keys, connection strings and tokens without leaving them in chat history or a ticket.
- IT & DevOpsOnboarding, offboarding and emergency handoffs, without leaving credentials in a ticket forever.
- HR & recruitingSend offer details and personal data without leaving a permanent copy in an inbox.
- Agencies & freelancersExchange client credentials across organisations that share no tooling — and stop accumulating them.
- Personal useEveryday private text — shared logins, travel details, drafts you would rather not leave in a chat app.
Frequently asked questions
Are any of these features behind a paid tier?
Do I need to create an account?
Can Inkrypt store files or images?
Which browsers are supported?
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