Website under development
VKrypt is a privacy-first layered encryption project using Encoded64 input processing, Argon2id-derived inner key material, salted 64-character mapping, a 64 x 64 custom chained cipher and an OpenPGP final protection layer.
The public website is being built carefully before the encryption and decryption tools are made available. The current build now focuses on Argon2id key derivation, Encoded64 validation, production privacy controls, timestamp-only routine metadata, legal clarity and public-safe transparency reporting.
What is VKrypt?
VKrypt is being designed as a stateless public tool. Users arrive, encrypt or decrypt, receive their result and leave without creating a public account, profile, dashboard, inbox or saved message history.
Accepted text is validated as UTF-8, emojis are rejected, and the input is converted into unpadded Base64url before the custom cipher runs.
The keyword/passphrase is processed through Argon2id before it influences VKrypt's internal key stream.
A kdf_salt supports Argon2id derivation, while a separate cipher_salt varies the generated 64-character mapping.
A deterministic Base64url mapping is generated from the Argon2id-derived inner key stream and cipher salt.
The controlled Encoded64 text is transformed through a 64 x 64 chained grid before OpenPGP wrapping.
The VKrypt package is wrapped with OpenPGP as the final recognised protection layer.
VKrypt will not be able to recover messages if the keyword/passphrase, OpenPGP key or passphrase is lost.
Routine production metadata is limited to midnight showing cipher use, this is retained until midnight and then purged.
VKrypt privacy rule
No accounts. No message storage. No session history. No tracking. No analytics. No hidden collection.
In production, VKrypt must not store plaintext, keywords/passphrases, encoded plaintext, kdf_salts, KDF request metadata, derived inner keys, inner key streams, cipher_salts, generated mappings, custom ciphertext or OpenPGP encrypted output. Routine production metadata is timestamp-only, retained until midnight, then permanently deleted.
Policy pages planned
The updated build treats the Privacy Policy, Terms of Service and Transparency Policy as first-class public pages. They will explain collection, retention, acceptable use, recovery limits, timestamp-only routine metadata, Argon2id-enhanced v1.8 processing and the no-account model in plain language.
VKrypt processes encryption and decryption requests only for the time needed to return the result to the user. In production, VKrypt does not store plaintext, keywords or passphrases, salts, derived keys, mappings, custom ciphertext, OpenPGP output, message history, user accounts, tracking data or analytics. Only limited temporary operational metadata may be retained where required, and this is permanently deleted under VKrypt’s ephemeral deletion model.
By using VKrypt, users agree to use the service lawfully, responsibly and without attempting to abuse, disrupt, reverse engineer, overload or attack the system. Users are responsible for keeping their own keywords, passphrases, private keys and encrypted outputs secure, and understand that VKrypt cannot recover lost messages or restore deleted data. VKrypt may apply reasonable technical safeguards, such as request-size limits, maintenance mode and abuse protection, to protect the service without creating public user accounts, tracking profiles or stored message history.
VKrypt’s transparency promise is simple: no public accounts, no message storage, no session history, no tracking, no analytics and no hidden collection. VKrypt only processes data temporarily to complete the encryption or decryption request, does not keep the materials needed to recover messages, and permanently deletes limited operational data under its ephemeral deletion model.
Roadmap
The roadmap below reflects the Version 1.8 direction at holding-page level, without turning this temporary page into the full public website.
Confirm Encoded64 Mode, Argon2id KDF, no emojis, no-data production model, no cookies and the permanent VKrypt motto.
Keep the live site as a focused holding page while the future public structure, legal pages and clean URLs are prepared behind the scenes.
Keep private services, configuration, KDF logic and cipher logic outside the browser-accessible public folder.
Build kdf_salt generation, Argon2id derivation, KDF metadata validation, parameter bounds and test vectors.
Generate salted 64-character mappings from the Argon2id-derived inner key stream and cipher_salt.
Implement the Encoded64 chained grid, numeric totals, reverse lookup and decryption round-trip.
Package version, mode, KDF metadata, salts and custom ciphertext before OpenPGP wrapping.
Allow full debug visibility in development only, with clear warnings that real user data must not be used there.
Build administrator management with MFA direction, KDF profile visibility, sanitised views and no public user login.
Enforce timestamp-only routine production metadata and no storage of message, keyword, KDF, salt, mapping or cipher material.
Delete timestamp records after at midnight and prepare public-safe transparency and legal request summaries.
Complete KDF benchmarking, security hardening, hosting-log review, privacy regression checks and a clean production launch reset.
Latest update
The landing page now reflects the Version 1.8 direction while remaining a coming-soon page only: Encoded64 processing, emoji rejection, Argon2id-derived inner key material, kdf_salt and cipher_salt handling, salted 64-character mapping, 64 x 64 chained cipher work, OpenPGP wrapping, timestamp-only routine production metadata and the no-account privacy model.
Contact
For security reports, feedback and general enquiries, use the dedicated VKrypt contact address below.
VKrypt is not affiliated with, endorsed by or sponsored by OpenPGP, Base64url, Argon2id, or any third-party standard, protocol, process, library or codebase referenced by the project. All such technologies and works remain the property of their respective authors, maintainers, contributors, rights holders and licensors.
