ENCRYPT RSA — ASYMMETRIC ENCRYPTION TOOL

A clean, fast RSA encryption and decryption tool built for developers, security professionals, students, and anyone who needs to work with asymmetric cryptography on mobile.

━━━━━━━━━━━━━━━
WHAT IT DOES
━━━━━━━━━━━━━━━

Generate RSA key pairs — 1024, 2048, or 4096-bit key sizes
Encrypt any plaintext message using a public key
Decrypt RSA ciphertext using your private key
Import and export keys in PEM format (PKCS#1 and PKCS#8 supported)
Copy encrypted output directly to clipboard
OAEP and PKCS#1 v1.5 padding modes
Base64-encoded output for easy transport

━━━━━━━━━━━━━━━
HOW RSA WORKS
━━━━━━━━━━━━━━━

RSA is asymmetric encryption — you encrypt with a public key, decrypt with a private key. The public key can be shared openly with anyone. Only the private key holder can decrypt. This is the cryptographic foundation behind HTTPS, SSH authentication, code signing certificates, and secure email (PGP/S/MIME). RSA-2048 is the current industry standard; RSA-4096 is used where maximum security is required.

━━━━━━━━━━━━━━━
USE CASES
━━━━━━━━━━━━━━━

Secure message exchange — encrypt with recipient's public key, only they can decrypt
Key exchange verification — confirm RSA key pairs are correctly matched
Development and testing — verify RSA implementations in backend systems or APIs
Security education — learn and demonstrate asymmetric cryptography hands-on
Encrypting sensitive strings — for configuration secrets, API keys, or private data
PEM key inspection — import and examine RSA keys from certificates or SSH configs

━━━━━━━━━━━━━━━
KEY SIZES EXPLAINED
━━━━━━━━━━━━━━━

1024-bit — legacy only, not recommended for security-critical uses
2048-bit — current industry standard, recommended for most applications
4096-bit — maximum security, used in high-assurance environments

Larger key sizes are more secure but slower to generate and process. For most use cases, RSA-2048 provides the right balance.

━━━━━━━━━━━━━━━
FULLY OFFLINE
━━━━━━━━━━━━━━━

All key generation, encryption, and decryption happens entirely on your device. No keys, no plaintext, no ciphertext, and no operation data ever leaves your phone. No internet connection required. No server involved. Ever.

━━━━━━━━━━━━━━━
PEM FORMAT SUPPORT
━━━━━━━━━━━━━━━

Import existing RSA keys from PEM files — useful for working with keys generated by OpenSSL, SSH-keygen, or your backend infrastructure. Export generated keys as PEM-formatted text for use in other systems.

━━━━━━━━━━━━━━━
PRIVACY
━━━━━━━━━━━━━━━

No account. No analytics. No data collection of any kind. GDPR-compliant.

━━━━━━━━━━━━━━━

━━━━━━━━━━━━━━━
RSA vs AES — WHICH TO USE
━━━━━━━━━━━━━━━

RSA is asymmetric — two different keys (public and private). Use RSA when you need to send encrypted data to someone without sharing a secret key first. The recipient shares their public key openly; only they can decrypt with their private key.

AES is symmetric — one shared key encrypts and decrypts. Use AES when both parties already share a secret key, or when encrypting data for yourself. AES is faster for large data; RSA is slower but solves the key distribution problem.

In practice, most secure systems use both: RSA to exchange an AES key, then AES for the data. This is exactly how HTTPS works.

━━━━━━━━━━━━━━━
DEVELOPER WORKFLOW
━━━━━━━━━━━━━━━

Generate a key pair on-device → export the public key → share it with a counterpart → receive encrypted payload → decrypt with your private key on this device. The entire workflow runs offline, on your phone, without any server or cloud service involved.

Whether you're learning cryptography, testing an implementation, or encrypting something that genuinely needs to stay private — Encrypt RSA gives you a clean, reliable, offline tool that does exactly what it says.

By Modex Apps.