privacy policy.
What Vael keeps, why it is needed, and the choices you have. Privacy starts with knowing where your data goes.
updated 8 October 2026follow your data through the system ↗on this page
operator and contact
Ilja Gwawl operates Vael. Use the help button on this website to open a private browser ticket, or Telegram support. Send privacy or account-data questions by email to vael-support@vael.email.
personal information and no KYC
Vael does not collect personal identity information about you to register an account or verify who you are. We do not ask for your real name, home address, phone number, date of birth or identity documents.
We will never require Know Your Customer (KYC) checks or similar identity verification to create, keep or use a Vael account. This includes government ID uploads, identity selfies and proof of address.
We process the account, security, mail and billing data needed to provide the service, as described below. Personal information you choose to include in mail or optional support messages is processed as part of that content.
account and security data
We store your chosen addresses, account identity, credential verifiers, sessions, app-credential settings, optional two-factor authentication, entitlements, preferences and activity needed to operate the account. Your account key is verified rather than stored as readable text. No recovery email or personal name is required to register.
Sign-in and abuse protection process connection addresses transiently. Pseudonymous security rate-limit counters expire within one hour, and their rotating keys expire within two hours. They remain in volatile memory and are not persisted as a browser identity. Vael does not use advertising analytics, browser fingerprinting or session replay. Infrastructure providers still process connection information needed to supply their services.
mail and encrypted storage
Mail bodies, attachments and headers are stored in the mail service. Search and organization use related metadata. Mail-storage volumes and rolling backups are encrypted. Website and authenticated mail-client connections require TLS; server-to-server mail uses TLS when the other provider supports it. By default the running server and its operator can decrypt stored mail.
You can turn on the encrypted mailbox in security settings. Stored mail and the search index are then sealed with a mailbox key that only you hold. Vael does not store it and cannot recover it, so mail encrypted with a lost key is gone. The server still receives mail as it arrives and, while you are signed in and unlocked, decrypts it in memory to show it to you. Dates, sizes, folders, delivery addresses and the recipients of mail you send remain readable to the server. You can turn the encrypted mailbox off again with your account number, second factor and mailbox key. Mail apps that use app passwords cannot read an encrypted mailbox.
OpenPGP messages in the browser webmail are encrypted and decrypted on your device. On the no-JavaScript site the server does this for a single page view, and says so. Ordinary email is not end-to-end encrypted, and the encrypted mailbox is not zero-knowledge.
Incoming messages can contain tracking content and connection metadata added by other senders. Website icons are on by default: Vael fetches a domain-level logo through its server and keeps a shared database cache. The remote website sees the Vael server request, not your browser address; no message identifier or account data is sent. You can turn website icons off in mail settings. Message-body remote images are blocked by default. If you approve them, Vael fetches them; the remote server can observe those requests. Any local draft recovery you enable also stores draft data in your browser.
mail health reports
Vael receives aggregate authentication and TLS reports from other mail providers. Report messages are kept for up to seven days, and aggregate domain counts for up to 90 days, within bounded storage. Reports are untrusted observations and do not guarantee delivery. Webmail preloads a limited number of messages into browser memory; this cache is cleared when your session ends.
payments
Heleket processes payment assets, networks, addresses and blockchain transactions. Vael stores order identifiers, amounts, payment status and entitlement records for billing and reconciliation. Your secret account key is not sent to Heleket. Public blockchains can expose transaction information independently of Vael.
service providers
StealthVM supplies the server infrastructure. Cloudflare supplies authoritative DNS for Vael domains and storage for encrypted off-site backups. Website HTTPS and native IMAP/SMTP mail connections connect directly to Vael’s server. The Tor and I2P mirrors connect through their respective networks. Heleket supplies cryptocurrency payment processing. Each provider also processes data under its own policies.
Spam protection queries DNS reputation services using sender infrastructure addresses, domains found in messages and, for some lists, hashes of message-related identifiers. These services and DNS resolvers can observe those queries. Malware scanning runs locally; the scanner downloads signed virus-database updates from ClamAV's distribution service.
support
Website support is optional and uses a randomly assigned visitor number, separate from your mail account or account key. A Secure, HttpOnly browser cookie remembers this support identity for 180 days. Website ticket subjects, messages and staff attachments are stored by Vael until the ticket is deleted and mirrored to a private Discord channel so the operator can respond. Telegram support remains available; Telegram processes messages and files you send to its bot. Telegram bridge payloads are removed after delivery and temporary transfer files are discarded. Copies on Telegram and Discord follow their respective retention policies, and encrypted backups follow the retention rules below. Sound and notification preferences and the last notified response identifier are saved in your browser. Desktop notifications use a generic message without ticket content. Never send account keys, passwords, recovery codes or wallet secrets.
retention, deletion and backups
Mail and account settings remain while your account is active, subject to your deletion and inactivity settings. Security access is revoked when an account is deleted. Primary and random address retirement remains permanent. Minimal deletion records are retained to prevent older backups from reactivating a deleted identity.
Encrypted backups use a rolling seven-day retention window with capacity limits. If new captures fail, the newest verified consistent snapshot is retained and can exceed seven days. Deleted content may remain in existing backups until their retention and pruning finish; deletion is not an immediate secure erase of historical storage. Billing, security and deletion metadata have operational retention separate from the live mailbox.
Backups are encrypted by Vael before transfer to Cloudflare R2 offsite storage. Cloudflare stores the encrypted backup objects. Recovery depends on separately protected recovery keys and successful backup checks.
your controls
You can export account data and mail, revoke sessions and app credentials, change image permissions, choose an inactivity policy, or delete your account. Contact us to ask about your data or rights available under applicable law.
registration protection
Vael runs its own Cap proof-of-work check for regular registration. The no-JavaScript site, Tor and I2P mirrors use a text-image challenge. Challenge records and pseudonymous limits are short-lived; there are no CAPTCHA provider calls or browser fingerprinting. Registration cookies bind the challenge to your browser and expire after 30 minutes.
Telegram account connection
Connecting Telegram is optional. If you connect it, Vael stores your Telegram user ID, the Vael account it is linked to, the permissions you chose, and connection and expiry times. The connection expires after 30 days or when you disconnect it, and security changes can invalidate it. Connection records can remain until account deletion or later cleanup and in encrypted backups. A restored backup requires a new connection. Temporary message-view requests contain a random token and message reference in volatile storage and expire after ten minutes.
The bot sends its menu and help messages through Telegram. Telegram processes those messages and controls its app and Mini App environment. Chats with bots are not end-to-end encrypted. Mail you view in the Mini App is displayed on your device; do not send account numbers or verification codes in chat. You can disconnect Telegram in the connection screen.
optional webmail plugins and open tracking
Webmail can remove supported metadata from outgoing attachment copies. Signed, encrypted or unsupported files require an explicit choice to send their original. Received originals and existing backups are not rewritten. Metadata cleaning does not redact visible text or filenames and cannot guarantee anonymity.
Open tracking is off by default. If a sender enables it, Vael adds one image pixel per message. A pixel request records only its first timestamp for the sender's Seen badge. Vael does not store recipient IP addresses, user agents, locations or request histories for this feature. Website infrastructure, including Cloudflare, processes the request. Proxies or scanners may request the image without a person reading the email; blocked images may hide actual opens.
Pixels remain active for 90 days after submission, until the sender stops tracking, or until permanent message/account deletion. A first-request timestamp stays with its sent message after tracking ends. Account exports include tracking timestamps. Encrypted backups follow the existing bounded retention policy; restoration disables restored pixels. Incoming tracking protection stays separate from outgoing tracking.