Last updated 7 August 2026
The short version: your conversations are answered inside a hardware enclave that nobody, including us, can look into. They are stored nowhere but your own browser, and nothing about them leaves the enclave unless you turn on a feature that tells you exactly what it sends. No accounts, no cookies, no analytics. You do not have to take this page's word for it: the enclave proves what it is running, and the app shows you the proof.
"We" means the operator of eyesoff.ai. This policy describes what the service does with data, and just as importantly, what it is built to be unable to do.
Every message is decrypted and answered inside a confidential virtual machine
(a hardware enclave) on the Enclave
fleet. The encrypted connection from your browser terminates inside that enclave: the
owner of the machine, the network in between, and we ourselves see only ciphertext.
The hardware signs a report over the exact code the enclave booted and over the key
your connection is encrypted to. The shield icon in the app shows that report, and
GET /attestation returns it raw, so you can verify the claim rather than
trust it.
Nothing. There are no accounts, no sign-in, and no server-side storage of
conversations. A chat's address (/c/<id>) is a key in your own
browser's database; the server has never heard of it and could not look it up if asked.
The enclave holds a conversation in memory while it writes the reply and never writes it
to storage. Diagnostic logs record operational events (errors, startup), not
conversation content.
With every optional feature off, nothing about your conversations leaves the enclave at all. Each feature below sends exactly what it says, and sends it from the enclave's own network address, never from your browser:
Traffic between your browser and the enclave is carried by the Enclave platform's relays. Like any carrier, they can observe connection metadata: your IP address, timing, and how many encrypted bytes moved. They cannot read any of it, because the key that would decrypt it never leaves the enclave.
None. No cookies, no analytics, no fingerprinting, no third-party scripts. The app is a single self-contained page served by the enclave itself.
Requests to the OpenAI-compatible API (/v1) run in the same enclave
under the same rules as the chat: answered in memory, stored nowhere, subject to the
same optional outbound features if the request asks for them.
eyesoff.ai is not directed at children under 13, and they should not use it.
Privacy laws give you rights over personal data an operator holds about you: access, correction, deletion, portability. We hold none, so there is nothing to request a copy of and nothing to delete; your chat history is in your browser, where deleting it is one switch. If you believe we hold personal data about you anyway, contact us and we will answer plainly.
If the service's data practices change, this page changes with them and the date at the top moves. The stronger guarantee does not live on this page: the app's source is available and the enclave attests to what is actually running, which no policy edit can quietly undo.
eyesoff.ai is a chat interface to open-weight language models running inside hardware enclaves on the Enclave platform. By using the service you accept these terms; if you do not accept them, do not use it.
What you type, attach, and generate is yours. We claim no ownership of it and take no license to it, and by design we cannot read it. You are responsible for what you submit and for having the right to submit it.
Answers are produced by machine-learning models. They can be wrong, out of date, or inappropriate, and they can be wrong while sounding certain. Output is not medical, legal, or financial advice. Verify anything that matters before acting on it; you are responsible for how you use what the models produce.
Do not use the service to break the law or to harm others. In particular, do not use it to create or spread content that is illegal, to attack third parties through the web-search or web-request features, to probe, overload, or disrupt the service or the platform it runs on, to attempt to defeat the isolation or attestation of any enclave, or to resell the service as your own. We may rate-limit or block traffic that harms the service or other people, which is the extent of the enforcement a service that cannot read its own traffic can do.
Web search, when you enable it, uses an outside search provider under that provider's own terms. Pages the enclave fetches belong to their own operators. The Enclave platform that hosts the service has its own terms for hosting and payment.
The service runs on rented capacity that comes and goes; when no GPU is available it answers on CPU, slowly, and sometimes it may not answer at all. There is no promise of uptime. Models, features, and limits change without notice, and the service may be suspended or discontinued at any time.
THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND UNINTERRUPTED OR ERROR-FREE OPERATION, TO THE FULLEST EXTENT PERMITTED BY LAW.
To the fullest extent permitted by law, we are not liable for indirect, incidental, special, consequential, or exemplary damages, or for lost profits, data, or goodwill, arising from your use of the service. Our total liability for any claim is capped at what you paid us to use the service in the year before the claim arose. Where the law does not permit these limits, they apply to the greatest extent it does permit.
We may change these terms; when we do, the date at the top of this page moves, and continued use after a change is acceptance of it. We may refuse or cut off service to traffic that violates these terms.
The app's source is available in the enclave-apps repository; questions, reports, and requests are welcome as issues there.