Privacy architecture
Your device
Chats stay here, encrypted with your key.
Kept here: Your chats
Hypercove
Passes it on. Keeps nothing you write.
Never kept: Prompts and replies
AI model
Reached incognito. Most models keep nothing.
Never sent: Who you are
We keep nothing you write. The model never learns who you are.
One of Hypercove’s guiding principles is user privacy. The platform's architecture flows from this philosophical principle, and every component is designed with this objective in mind.
Nearly all AI apps and services collect user data (personal information, prompt text, and AI text and image responses) in central servers, which they can access, and which they can (and do) share with third parties, ranging from ad networks to governments. Even if a company wants to keep this data safe, data breaches happen all the time, often unreported.
The only way to achieve reasonable user privacy is to avoid collecting this information in the first place. This is harder to do from an engineering perspective, but we believe it’s the correct approach.
Local Storage Only
Hypercove does not store or log any prompt or model responses on our servers.
When you, as a Hypercove user, make a request, it is transmitted to our proxy server, then passed to the provider that runs the model you selected. It reaches the provider incognito, with no name or account attached, and most models run with zero data retention. The response is then streamed directly back to your browser via the proxy, but without persisting it in any form of permanent Hypercove storage.
The Hypercove platform uses your local browser storage to maintain your conversation history, assuring your conversations are private to the device they originated from (this is why your conversation history differs across multiple devices you use, even under the same account). This local storage is also encrypted to prevent observation of the raw messages from the browser itself.
SSL Encryption, Standard
Your communication over Hypercove’s infrastructure is secured using SSL encryption throughout its entire journey. The text or image prompts you submit on your device are transmitted to and from our proxy service, and between our proxy service and the AI providers that run the models, over industry-standard SSL encryption. Hypercove's proxy service routes and relays your prompts to the model and back without persisting them.
End-to-End Encryption
Models marked End-to-end encrypted go further. Your message is encrypted in your browser before it leaves your device, and it can only be decrypted inside a hardware enclave (an Intel TDX trusted execution environment running on NVIDIA GPUs). Before sending, your browser checks the enclave's signed hardware report. Hypercove's proxy passes the sealed message along but cannot read it. Every end-to-end encrypted chat has a Verification Center with the raw hardware report, the GPU attestation and the encryption key, so you can check the hardware and the encryption yourself. When a reply uses web search or image generation, those tool requests run outside the enclave.
Data Collection
Hypercove collects limited information, which differs based on the account type. For all account types, Hypercove logs event data on how users use the product (such as signing in, creating new chats, organizing and filtering chats, etc.) but never logs or otherwise sees or stores any data about the text or image prompts shared between you and the AI models.
- No-Account Users: Without an account, Hypercove collects basic metadata on a user, such as timezone, browser type, and IP address.
- Free Account Users: When a Free Account is created, Hypercove collects the email address that was provided in addition to the above metadata.
- Pro Account Users: If a user pays for a Pro account with a credit card, only our payment services provider, Stripe, receives this information, which is not shared with Hypercove. If a user pays with crypto, Hypercove records the user's public key (wallet address).
Again, your conversation history is never shared with, or stored by, Hypercove. If you choose to delete your conversation history, you are deleting it from your own browser/device, which is the only place it was ever stored.
Our commitment to privacy and anti-censorship is resolute, and every decision we make is done with fidelity to these principles.
Standards & References
These protections are built on published, openly reviewed standards:
- Encryption in transit: TLS 1.3 - IETF RFC 8446
- Chat history encrypted in your browser (XSalsa20-Poly1305): NaCl secretbox
- Saved images and videos encrypted in your browser (AES-GCM): NIST SP 800-38D
- Media encryption key derivation: HKDF - IETF RFC 5869
- In-browser cryptography: W3C Web Cryptography API
- Collecting as little data as possible: NIST Privacy Framework
FAQ
Frequently asked questions
Yes. Hypercove offers a free tier so you can experience how it responds, remembers, and engages before upgrading. The free version is designed to show the real product behavior, not just a limited demo.
Ready to Experience True AI Freedom?
Start for free. Upgrade anytime for unlimited access to all features.