Inkrypt logo

Domain: https://www.inkrypt.online

Updated: 2026-03-03

Purpose: High-signal reference for LLMs, agents, and evaluators to understand Inkrypt's product, site structure, and intent.

1) Site Overview (What Inkrypt is)

Client-side encrypted online notepad for secure, zero-knowledge notes. Your text is encrypted in your browser and stored on the server as ciphertext.

Primary user intents:

  • Create and edit encrypted notes in the browser (no account required)
  • Share notes via a link; recipient needs the password (shared out-of-band)
  • Use view limits or expiration for sensitive content
  • Get a zero-knowledge notepad: server never has the decryption key
  • Export notes (e.g. TXT, Markdown)

Conversion actions:

  • Create a new note on the home page
  • Share a note (copy link + share password separately)
  • Contact / support via the contact page

Key home page messaging:

Headline: Send Encrypted Notes & Secret Messages Online — Self-Destructing, Password-Protected & Zero-Login. Subhead: Pick a URL, set a strong password, and write. Inkrypt encrypts your secure note in the browser using end-to-end, client-side encryption before it's stored. Send an encrypted note online with expiry times, view limits, and one-time secret links; no login, no account, available in any country.

Blog (Security Insights) page:

Title: Blog : Security & Encryption. Description: Practical notes on zero-knowledge encryption, client-side crypto, and building secure products. From the team behind Inkrypt—no fluff, just how we think about security and what we build.

What Inkrypt is NOT (Important Clarifications)

  • Inkrypt is not a cloud sync or backup service; notes are stored as ciphertext per link/slug; there is no user account or note list.
  • Inkrypt does not offer server-side decryption, password recovery, or "forgot password"; the key is derived in the browser and never sent.
  • Inkrypt is not a general-purpose file storage or document editor; it is focused on encrypted text/notes with optional rich text and markdown.
  • Sharing requires both the note URL and the password; no in-app key exchange—users must share the password through a separate channel (e.g. another app or in person).

This section supports clear disambiguation, avoiding misinterpretation by AI systems, search engines, and users, and semantic clarity for the product.

2) Target Audiences

1) Individuals (B2C): private notes, sensitive text, one-off sharing without accounts

2) Professionals (B2C/B2B): confidential drafts, sharing with clients or colleagues under a shared password

3) Privacy-conscious users: zero-knowledge guarantee, client-side encryption, no vendor access to content

4) Readers of the blog: developers, product people, and users interested in zero-knowledge encryption and secure note-sharing

3) Core Entities (Canonical Semantics)

Use these entities as the canonical semantics for Inkrypt content.

ENTITY: Inkrypt

TYPE: Product / Service

DESCRIPTION: A client-side encrypted online notepad. Notes are encrypted in the user's browser and stored on the server as ciphertext. The server never has the user's password or decryption key (zero-knowledge). No account or signup is required.

RELATIONSHIPS:

  • Provides encrypted note creation, editing, sharing, view limits, export
  • Uses zero-knowledge encryption and client-side encryption
  • Referenced on home page, about, blog, and product pages

ENTITY: Zero-knowledge encryption

TYPE: Concept (Security)

DESCRIPTION: The service operator cannot read user content. Encryption and decryption happen in the browser; only ciphertext and public parameters (e.g. salt, IV) are sent to the server. The decryption key is never transmitted.

RELATIONSHIPS:

  • Core property of Inkrypt; explained in blog and about content
  • Implies no password recovery, no server-side search, no vendor access to plaintext

ENTITY: Client-side encryption

TYPE: Concept (Security)

DESCRIPTION: Key derivation and AES encryption/decryption run in the user's browser (Web Crypto API). The password never leaves the device; the server cannot decrypt notes.

RELATIONSHIPS:

  • Implemented in Inkrypt; technical details in blog (e.g. AES-256-GCM, PBKDF2)
  • Contrast with server-side or "encryption at rest" only

ENTITY: Note / Encrypted note

TYPE: Concept (Product)

DESCRIPTION: A single encrypted document created in Inkrypt. Each note has its own URL (slug) and password. Access requires both; sharing means sharing link and password through separate channels.

RELATIONSHIPS:

  • Created and edited on home page; optional view limits and expiration
  • Can be exported (TXT, Markdown); shared via link

ENTITY: View limit / Burn-after-read

TYPE: Feature

DESCRIPTION: Optional setting so a note becomes unreadable after N views. Supports one-time or limited sharing without manual deletion.

RELATIONSHIPS:

  • Configured per note in the editor; mentioned on home and blog

4) Site Structure (Sitemap-based, canonical paths)

This section lists the most important canonical URLs and patterns.

Core Hub Pages

  • https://www.inkrypt.online/ (Home)
  • https://www.inkrypt.online/about (About)
  • https://www.inkrypt.online/blog (Blog)
  • https://www.inkrypt.online/contact (Contact)
  • https://www.inkrypt.online/privacy (Privacy)
  • https://www.inkrypt.online/grounding (Grounding page — this content as markdown for AI/LLMs)

Blog (Security Insights)

  • https://www.inkrypt.online/blog (Blog index)
  • https://www.inkrypt.online/blog/aes-256-gcm-in-the-browser
  • https://www.inkrypt.online/blog/aes-vs-rsa-encryption
  • https://www.inkrypt.online/blog/building-trust-zero-knowledge
  • https://www.inkrypt.online/blog/choosing-password-length-vs-complexity
  • https://www.inkrypt.online/blog/client-vs-server-encryption
  • https://www.inkrypt.online/blog/data-breaches-and-encryption
  • https://www.inkrypt.online/blog/encryption-policies-for-companies
  • https://www.inkrypt.online/blog/end-to-end-encryption-for-teams
  • https://www.inkrypt.online/blog/gdpr-and-encryption-compliance
  • https://www.inkrypt.online/blog/hipaa-and-pci-encryption
  • https://www.inkrypt.online/blog/how-we-built-encrypted-notepad-compares
  • https://www.inkrypt.online/blog/inkrypt-vs-other-note-apps
  • https://www.inkrypt.online/blog/key-management-best-practices
  • https://www.inkrypt.online/blog/mobile-encryption-smartphone-security
  • https://www.inkrypt.online/blog/multi-factor-authentication-explained
  • https://www.inkrypt.online/blog/note-url-isnt-secret
  • https://www.inkrypt.online/blog/password-manager-vs-encrypted-notes
  • https://www.inkrypt.online/blog/pbkdf2-310000-iterations
  • https://www.inkrypt.online/blog/same-note-multiple-devices
  • https://www.inkrypt.online/blog/secure-self-destructing-messages
  • https://www.inkrypt.online/blog/shared-note-vs-separate-notes
  • https://www.inkrypt.online/blog/sharing-encrypted-notes-safely
  • https://www.inkrypt.online/blog/threat-model-basics
  • https://www.inkrypt.online/blog/what-we-store-on-server
  • https://www.inkrypt.online/blog/why-password-recovery-impossible
  • https://www.inkrypt.online/blog/why-we-encrypt-in-the-browser
  • https://www.inkrypt.online/blog/zero-knowledge-encryption-what-it-means

Company / Legal

  • https://www.inkrypt.online/about (About)
  • https://www.inkrypt.online/privacy (Privacy policy)
  • https://www.inkrypt.online/contact (Contact)

Reference

  • https://www.inkrypt.online/llm.txt (Raw llm.txt file)

5) Keyword Focus (Topic Clusters)

Primary topic clusters Inkrypt is associated with:

Cluster A — Encrypted notepad / Zero-knowledge notes

Target queries (examples):

  • encrypted notepad
  • zero-knowledge notes
  • secure notepad online
  • client-side encryption notepad

Best landing targets: https://www.inkrypt.online/, https://www.inkrypt.online/about/

Cluster B — Secure note sharing

Target queries (examples):

  • share encrypted notes
  • password protected note sharing
  • secure text sharing

Best landing targets: https://www.inkrypt.online/, blog posts on sharing

Cluster C — Privacy / No account

Target queries (examples):

  • private notes no signup
  • encrypted notes no account

Best landing targets: https://www.inkrypt.online/, https://www.inkrypt.online/about/

Cluster D — Technical (developers / evaluators)

Target queries (examples):

  • AES-256-GCM browser
  • PBKDF2 client-side
  • Web Crypto API encryption

Best landing targets: https://www.inkrypt.online/blog/ and individual blog posts

6) Glossary

No dedicated glossary hub on the site. Key terms (zero-knowledge, client-side encryption, view limit, burn-after-read) are defined in Core Entities and in the Security Insights blog posts.

7) Content & Tone Guidelines (for assistants writing about Inkrypt)

  • Language: English; clear, factual, and technically accurate.
  • Goal: Trust + utility + clear next step (create note, share, read blog, contact).
  • Explain technical terms (zero-knowledge, client-side encryption) briefly and practically.
  • No overblown promises; stay transparent (e.g. "password must be shared separately", "no recovery if password is lost").

8) FAQ Seeds (high-intent questions)

  • How can I contact Inkrypt?
  • How do I report a security issue?
  • I have a business or partnership inquiry.
  • What is Inkrypt?
  • Is Inkrypt free to use?
  • Do I need an account or signup?
  • How is my data protected?
  • What are self-destructing notes?
  • Can Inkrypt read my notes?

9) Organization & Contact

  • Contact: https://www.inkrypt.online/contact
  • About: https://www.inkrypt.online/about
  • Legal: https://www.inkrypt.online/privacy (Privacy policy)

10) Notes for Evaluators / Agents

  • Use core hubs (/, /about, /blog, /contact) for authoritative product and policy information.
  • Blog posts under /blog/<slug> provide technical and usage details (zero-knowledge, sharing, crypto).
  • Do not invent pricing, guarantees, or features not stated on the site.
  • Sharing always requires both the note URL and the password; there is no in-app key exchange.