Disclaimer

Everything published on this site — articles, feature pages, the glossary, the security architecture and threat model documents — is general information about encryption, privacy and secure communication practice. It is written carefully and reviewed before publication, but it is written without knowledge of your particular circumstances.

Security decisions depend heavily on context: what you are protecting, who might want it, what the consequences of loss would be, and what obligations you are already under. Guidance that is correct for a freelance designer sharing a client login may be entirely wrong for a healthcare provider handling patient records. We cannot know which situation you are in.

We are not lawyers, and nothing here is legal advice. Where we mention regulatory concepts — data minimisation, storage limitation, the GDPR — we are describing the concept, not advising you on your obligations under it.

Specifically, because Inkrypt has no accounts, it produces no attributable access logs. Any control requiring you to demonstrate who accessed what and when cannot be satisfied by it. If you are subject to such requirements, factor that in before adopting it.

We document our cryptographic design in detail on the security architecture page precisely so it can be evaluated rather than taken on faith. We also document its known limitations on the threat model page. Both are honest accounts, and neither is a guarantee.

Inkrypt is provided as-is. If the consequences of a note being lost or exposed would be severe, use a tool with an independent audit, a support contract, and a recovery model that matches your risk tolerance.

We fact-check against primary sources and re-review pages on a schedule described in our editorial policy. Every substantial page shows a last-reviewed date. Despite that, information here may become outdated between reviews, or may simply be wrong.

If you find an error, tell us at work.securetext@gmail.com. Material corrections are published with a dated note on the affected page rather than made silently.

We link to standards documents, security guidance and third-party tools where they are genuinely useful. We do not control those sites and are not responsible for their contents, accuracy or availability. A link is not an endorsement of everything on the destination.

Where we describe another product, we do so from its own public documentation at the time of writing. Products change. Verify against the vendor's current documentation before making a decision.

You are responsible for what you put into a note, who you share it with, and how you send the password. Nothing on this site removes that responsibility.