Encrypt text with AES-GCM.
AES-GCM Encrypt keeps its state in memory and nowhere else. That is why it forgets everything on reload, and why it cannot leak anything.
No telemetry, no analytics on what you type, no request that carries the contents anywhere. The browser does the whole job.
You will find it under Encryption, alongside 5 other tools for the same sort of job.
Supports AES-128 and AES-256 key sizes with PBKDF2 key derivation and Base64 output.
input: Secret message for Bob key: MySecretKey123!
vBfQYySZiOn+7jGTZ5Ojnice2NUWBr5kEy83vZ0A4y7Mn50YR+HPdA/IwiZkuo3E2TuU7aFD8kH46ivQALahbpbz
Yes. It is JavaScript running in this tab, so once the page has loaded it needs nothing further from the network. Put the machine in flight mode and it carries on. Nothing you do here is sent anywhere, because there is nowhere for it to go.
No. Reload the page and it starts from nothing. There is no account, no saved state and no cookie holding your last session. That is a deliberate trade: it cannot lose your data because it never keeps any.
Timing comes from performance.now(), the high resolution clock the browser provides, rather than from setInterval, which drifts by a few milliseconds every tick and compounds over minutes. What can still shift things is the browser throttling a tab in the background, so leave it visible if the timing matters.
Where a sound makes sense, it is generated with the Web Audio API rather than loaded as a file, so there is nothing to download and nothing to block. Browsers refuse to start audio until you have interacted with the page, which is why the first press is what switches it on.
Yes. The controls are sized for touch and the layout collapses to one column on a narrow screen. Bear in mind that a phone locking its screen will suspend the page, and timing stops with it.