Keyvora Privacy Policy

Keyvora runs password, hash, Base64, UUID, and JWT decoding utilities in your browser. Tool inputs are not uploaded to an application server by default.

Last updated: 13 July 2026

Local processing

Password, hash, Base64, UUID, and JWT tools run locally in your browser.

No account required

The app does not require accounts or collect tool inputs by itself.

JWT note

JWT decoding is not signature validation. Verification requires the correct secret or public key.

1. Overview

Keyvora provides browser-based utilities for password generation, strength checks, SHA-256 hashing, Base64 encode/decode, UUID generation, and JWT decoding.

By default, these tools execute locally in the browser and do not send input values to an application server.

2. Local Data

The app may store small preferences in browser local storage, including PWA install prompt dismissal.

Generated values and typed tool inputs are kept in page state unless you copy them or your browser/session preserves form data.

3. Technical Data

The hosting provider may process standard server logs such as IP address, user agent, requested URL, and timestamps for security, troubleshooting, and operation. Keyvora does not receive tool input in these logs.

4. Third Parties

The application currently includes no analytics, advertising, payment, authentication, or error-monitoring provider. Fonts are bundled through Next.js rather than requested from a third-party font service. If this changes, this section will identify the provider, purpose, and data shared.

5. Security

Password strength results are estimates. JWT decoder output is not a security validation because signature verification requires the proper secret or public key.

6. Changes

Update this policy whenever your application changes how it stores, processes, or shares data.

7. Contact

For privacy questions, email hello@keyvora.app. Do not include passwords, tokens, files, or private keys in correspondence.