Privacy

This is a personal site that sells nothing directly. It collects an email address if you ask for the demo, and measures aggregate traffic through Google Analytics. Both are described below, plainly.

Analytics: Google Analytics, one third-party request

Every page loads Google Analytics (tag G-JELENGERFL) from Google's servers. This is the only request this site makes to anyone else's server. Google sets a cookie (_ga, lasting up to two years) that lets it recognise a returning browser, and in doing so receives your IP address, the pages you viewed and when. Google processes that data under its own terms and may use it across its services; this site uses it only to see aggregate numbers — how many people read, from which countries, on which pages.

This is a change from how the site used to run, which was with no analytics at all. The trade was made knowingly: knowing which posts people actually read decides what gets written next, and Google's measurement was chosen over a self-hosted alternative for the same reason everything else here is boring and standard. If you prefer not to be measured, any browser blocking third-party cookies or an ad-blocker with privacy lists stops it entirely — the site works identically without it.

The one thing collected: an email address

If you enter your address to open the OMMAIS demo, that address is stored. Alongside it, three things:

• the date and time you entered it;
• the two-letter country code the network hands over with the request;
• which page you were on when you entered it.

It is also checked, at the moment you submit, whether the domain actually receives mail — so a typo like gmial.cmo can be told apart from a working address. The answer is stored as a yes or no beside it.

Not collected: your IP address, your browser or device, your operating system, your passphrase, anything you typed into the demo, which models you chose, what the models answered, the names or contents of any file or folder you indexed, or any image you attached. Those never reach this site — see below.

Why it is kept: to know how many people tried the software, and to be able to say when the next version is out. It is not sold, rented, shared or handed to any third party, and there is no mailing platform involved — the addresses sit in a database belonging to this site and nowhere else.

The demo runs on your computer, not on this site

The OMMAIS demo drives the AI models installed on your own machine, through your own Ollama. Your prompts, the models' replies, anything you paste into the context box, any files or folders you index, and any image you attach are handled entirely inside your browser and your own computer. They are never uploaded here, because there is nowhere for them to go — this site has no server that can run a model, no endpoint that accepts a model's output, and no endpoint that accepts a file.

The one exception: letting an expert look something up

There is a checkbox in the demo labelled “Let experts look things up”. It is off unless you switch it on, and it is one of only two features on this page that send anything off your machine — the other is a cloud provider you connect yourself, below.

With it on, an expert that needs a fact it is unsure of — something after its training cutoff, a current figure, a specific paper — can ask for a lookup. Your browser then queries Wikipedia, Wikidata, DuckDuckGo and Crossref directly. What goes to them is the short search phrase the expert asked for, not your whole prompt, not your files and not the conversation.

Those requests go from your browser straight to those services. They do not pass through this site, and there is deliberately no proxy here that could see them: routing them through this server would hide your address from Wikipedia and reveal your queries to me, which is the worse trade. Each of those services has its own privacy policy and will see your IP address, exactly as if you had visited them yourself.

The interface says when a lookup is running and which seat asked for it, and the summary under each answer records how many lookups left your machine. Leave the box unticked and none of this happens.

The other exception: a cloud provider you connect

Under Cloud providers in the demo's setup you can use models from OpenRouter, Groq, Google Gemini, Mistral, OpenAI, Anthropic and others, with your own API key. Nothing is connected unless you paste a key, and until you do, every model runs on your own machine as described above.

Once you choose a cloud model for a seat, the prompts that seat is given — your question, and whatever context the demo passes it — go from your browser straight to that provider, under your account and its privacy policy. They do not pass through this site, and neither does your key. The interface marks every cloud model with its provider and whether it is free, on a free tier, or paid; paid models are billed by the provider to your account, not by this site.

Your keys are kept in the tab's memory and forgotten when it closes. If you set a passphrase, they are instead encrypted with it and saved in your own browser alongside your sessions — never in plain text, and never sent here. Disconnect removes a key from this device.

The optional passphrase, and what it does

The demo asks for an email address and, optionally, a passphrase. They are not the same kind of thing and it is worth being exact about the difference:

• The email address is sent to this site and stored, as described above.
• The passphrase is never sent anywhere. It is not stored, not transmitted, not hashed-and-uploaded, and not recoverable. Your browser turns it into an encryption key on your own machine and the key is discarded when you close the tab.

If you set one, your conversations and the index of any files you added are encrypted with that key and written into your browser's own storage on your own device. Coming back and entering the same address and passphrase decrypts them. There is no account on this site — nothing to log into, no password reset, and no way for me to help if the passphrase is forgotten, because I have never had it. Anyone else using the same computer sees encrypted bytes they cannot read.

Leave the passphrase blank, or press Continue without saving, and nothing at all is stored: the conversation exists only while the tab is open and is gone when you close it, which is how the demo behaved before this option existed.

The encryption uses your browser's built-in cryptography (PBKDF2 to turn the passphrase into a key, AES-GCM to encrypt with it). That costs a fraction of a second of your processor, once, when you sign in. Nothing runs in the background, and nothing here mines cryptocurrency or uses your machine for any purpose other than the models you asked it to run.

What is stored in your own browser

None of this is cookies and none of it is ever transmitted. It sits in your browser's storage, readable only by this site, on your device:

• orchestra-demo-seats — which model you picked for each seat, so the demo does not ask again next time.
• orchestra-demo-joined — a single flag so the demo does not ask for your address twice in one session. Cleared when you close the browser.
• orchestra-demo-email — the address you entered, so a returning visit does not make you retype it. Also cleared when you close the browser.
• Only if you set a passphrase: a database named orchestra-demo, holding your saved conversations and the index of any files you added. Everything meaningful in it is encrypted. The parts left readable are the ones the interface needs before it can decrypt anything: an identifier derived from your address, the date each item was saved, how many turns a conversation has, and which embedding model indexed your files. Your messages, the answers, the conversation titles, the file paths and the file contents are all inside the encrypted portion.

Clearing site data in your browser removes all of it, including the saved sessions — permanently, since there is no copy anywhere else. The demo also offers an Export button, which writes those sessions to a file you keep; that file is still encrypted and still needs the same address and passphrase to open.

Links out, and one that earns a commission

Books link to Amazon, papers to SSRN, software to Gumroad. Those are other companies' sites with their own privacy practices, and once you click through you are on their terms rather than these. The Amazon links carry an Associates tag, which means a purchase may earn a small commission at no cost to you — disclosed on every page carrying one — and it is Amazon, not this site, that sets a cookie when you arrive there.

Server logs

The site is hosted on Cloudflare, which keeps short-lived operational logs of requests the way every web host does, in order to serve traffic and stop abuse. That is Cloudflare's processing under their own terms, not analytics collected for me, and no profiles are built from it.

Having your address removed

Email eric.varney@yahoo.com and ask. No form, no account to log into, no reason required — the row is deleted. You are welcome to ask what is stored about you, and the honest answer will be short: one address, one date, a country code and a page name. Your saved sessions are not on that list because they are not here — they are on your own device, and clearing this site's data in your browser is what deletes those.

Children

Nothing here is aimed at children, and the demo requires installing developer software before it does anything at all. If you believe a child has entered an address, use the email above and it will be removed.

Changes

If what the site collects changes, this page changes with it — it is written from the code rather than from a template, and every claim on it was checked against the built site.

Last updated 20 September 2026.