Type where you already chat
Open Telegram, WhatsApp, SMS, email, or any app with a text field. VeilType appears as your keyboard.
Android launch · $4.49 lifetime access
VeilType is a lightweight Android keyboard for private text. Type, encrypt locally, and send through Telegram, WhatsApp, SMS, email, or any app with a text field.
Encrypt messages directly inside Telegram, WhatsApp and other Android apps.
No new messenger. No VeilType cloud. Offline voice typing with optional language packs is planned next.
Tap Encrypt to see what leaves the messenger.
Secure messengers are useful, but real life is fragmented: family in WhatsApp, groups in Telegram, documents in email, codes in SMS. VeilType adds privacy where people already talk.
Open Telegram, WhatsApp, SMS, email, or any app with a text field. VeilType appears as your keyboard.
Turn text, voice, photos, videos, or files into AES-256-GCM encrypted content before the messenger receives it.
The messenger only sees ciphertext or a .veil capsule. Your private content stays inside the encrypted payload.
The recipient uses the shared key and VeilType to decrypt locally on their Android device.
Both sender and recipient need VeilType and the shared key to open encrypted capsules.
Explore the same onboarding flow used in the Android app. Everything private stays on the device.
MESSAGE
Meet me at 7 PMVeilType appears as your Android keyboard inside the chat you already use.
ENCRYPTED OUTPUT
TL1:Q8bz...kP2The messenger receives ciphertext, not your readable message.
SHARED KEY
🔒 🌙 🦊 ⚡ 🧠 🔥 🧩 🌊Keys are created and kept locally inside VeilType.
OPENED LOCALLY
Meet me at 7 PMThe recipient opens the message with VeilType and the shared key.
Write normally, encrypt from the keyboard, and send ciphertext instead of plain text.
Private text and capsules are encrypted locally with AES-256-GCM before they leave the keyboard workflow.
The privacy-critical core is positioned for public review, while premium product features can remain commercial.
Record encrypted voice messages and unlock protected audio with biometrics when needed.
Package private media and files into .veil capsules for app-to-app sharing.
Set selected messages or .veil capsules to open once on the recipient device, then become unavailable for repeat reading.
Use memorable 8-emoji shared keys instead of account-based identities.
Require device biometric confirmation before decrypting selected keys and capsules.
Quickly wipe local keys and temporary capsule data when you need the device clean.
The current launch focuses on encrypted text and capsules. The next planned upgrade is offline voice typing with optional language packs, so users download only the speech languages they need.
The goal is to keep the main app focused on the keyboard and encryption workflow instead of bundling every future voice model.
The planned voice upgrade will let users choose which offline voice languages to download, update, or delete.
The intended design is simple: internet for language download or updates, local recognition after installation.
VeilType creates AES-256-GCM encrypted .veil capsules for private content. The same format can later become the bridge to a larger file-control product without changing the core promise: encrypt locally, send anywhere, keep the core auditable.
A .veil capsule is a protected package that can contain text, voice, photos, videos, or files. It is designed to travel through the apps people already use.
For extra-sensitive content, VeilType can mark a message or capsule as one-time read, so it opens once and then locks itself from normal repeat access.
The encryption core is published for public review. The Android app, premium UI, and commercial features remain proprietary. Review the core on GitHub.
Messages and .veil capsules are encrypted locally with AES-256-GCM before they are handed to Telegram, WhatsApp, SMS, email, or another app.
Message content is encrypted and decrypted locally. VeilType does not need a cloud account to protect a message.
Keys are stored on-device. If a key is lost, VeilType cannot recover it. That is intentional.
Per-key settings can make selected messages and capsules readable once, giving sensitive content a stricter local access policy.
VeilType does not run a server that receives your message content. Messengers transport the encrypted output.
Self-destruct, one-time read, and biometric gates are app-layer protections. They help, but do not replace device security.
A simple launch offer for the Android build. No subscription. No recurring fee. Built for early users who want a privacy layer inside the keyboard, not another messenger.
After buying VeilType, share your personal invite link. Five confirmed friend purchases unlock a purchase-back reward for your original VeilType price. If a creator brought you first, the creator still receives their commission.
Your paid access becomes the purchase that can be returned after the referral target is met.
Use your personal invite link with friends who want private Android messaging.
Refunds, chargebacks, self-referrals, and fraud traffic do not count.
No. VeilType is an Android keyboard and privacy layer for the messengers you already use.
No VeilType server stores your message content. Encryption and decryption happen locally on the device.
Yes. The recipient needs VeilType and the correct shared key to decrypt messages or capsules.
A privacy keyboard must earn trust because keyboards handle typed text. VeilType is designed around local encryption, no VeilType content server, clear permissions, and an open-core trust model for the privacy-critical core.
No. Offline voice typing is planned as a future upgrade. The intended design is local recognition after the selected language pack is downloaded.
Speech models can be large. The planned language pack model keeps the app lighter and lets you store only the languages you actually use.
VeilType uses an open-core trust model: the privacy-critical encryption core is published for public audit, while the full Android product can keep commercial features. Open the published core.
VeilType uses AES-256-GCM encryption for message and capsule protection before content is sent through third-party messengers.
Text, voice messages, photos, videos, and files can be turned into encrypted output or .veil capsules.
Yes. VeilType supports one-time read settings for sensitive messages and capsules, so normal repeat opening is blocked after the first successful read.
No. VeilType is not DRM. It is a local encryption layer. Once content is decrypted on a device, normal device risks still apply.
No. Cryptography cannot stop someone from taking a screenshot or photographing the screen after content is visible.
Install VeilType, create a shared key, and send private text or capsules without asking everyone to move to a new messenger.