Privacy

This page covers tryjev.albertoarena.it only. It is a demo of Jev, a model made by TypeSafe AI, and it exists so you can see what a calibrated answer looks like.

The short version

The text you type is sent to TypeSafe to be judged, and the answer is sent back to your browser. Nothing you type is stored here. There is no log of your submissions, no database, and no copy kept after the answer is returned.

Because nothing is kept, there is no history to request, correct or delete. The only thing to explain is the forwarding.

Who receives what you type

TypeSafe AI receives the situation and the conditions you wrote, because judging them is what the demo does. In their words, The Services are hosted in the United States, so your text leaves the EU and the UK when you press Run.

TypeSafe state that they will not train or fine tune any artificial intelligence or machine learning models on your prompts or other Input. That is their commitment, quoted rather than paraphrased.

They publish no retention period. Their policy states a standard rather than a period: data is kept for as long as reasonably necessary to provide you with the Services, or otherwise in support of our business or commercial purposes. That is open ended, and this page would rather quote it than round it into something reassuring.

What this demo keeps

Only enough to stop the demo being abused, and to count how many people came. Each item below says what it holds and for how long:

• A counter against a hashed address. Your IP address is put through a keyed hash; the hash and a count are kept for the length of the window and then deleted. The demo itself never writes the address down.
• The web server's own access log. Like every web server, the host records the address, the page and the time of each request, on its own rotation. That is standard hosting, not something this demo adds, but it would be misleading to describe the hashing above without saying so.
• A dated copy of that access log, which this demo does add. The host deletes its own archive when each new month starts, and analytics only ever sees the visitors who agreed to it, so a nightly copy is the only complete record that anybody came. It holds what the server already wrote, addresses and browser strings included, it sits outside the public site and is readable only by this account, and it is deleted automatically after 30 days. The visit counts worked out from it are daily totals and carry no addresses.
• A note when somebody approaches a limit, holding the hashed address, which limit it was and the count. No addresses, nothing you typed. Kept for up to 90 days, then deleted automatically.
• A session cookie holding a random identifier, so a single browser cannot run the demo hundreds of times. It contains nothing else, and it is strictly necessary for a service you asked for, so it is not part of the consent question and declining analytics does not switch it off. The demo works either way.
• A daily total of how many times the demo ran. A number, attached to nobody.

Why this is allowed

Sending your text to TypeSafe happens because you asked for it by pressing Run: that is consent, and not pressing it is how you withhold it. The anti-abuse counters rest on legitimate interest in keeping a public endpoint from being used as somebody's free proxy.

One thing worth knowing

TypeSafe publish no data processing agreement and no standard contractual clauses, so there is no paperwork behind the transfer beyond your own decision to press Run. So do not paste real customer data, anything confidential, or anything about an identifiable person into this demo. Made up examples show exactly as much as real ones.

Analytics

Google Analytics 4, and only if you press Accept on the banner. Nothing is fetched from Google until you do. No script, no pixel, no request of any kind: decline, and your browser never contacts Google on this site.

That is stricter than the usual arrangement, where the tag loads on every page and merely withholds the cookie. Withholding the cookie still hands Google your address and the page you were on before you have agreed to anything, so this site does not do it.

If you do accept, Google LLC becomes a processor for what it collects: the pages you opened, where you arrived from, your browser and device, and an approximate location worked out from your address, at the level of a country or a city, and how long each page stayed open. No advertising signals, no profiling, no cross-site tracking. Google may move that data outside the EU and the UK, and keeps it for 14 months.

Google offers a set of extra measurements switched on by default, covering scroll depth, clicks on outbound links and interactions with forms. They are switched off here. The form on this site is the demo itself, and while those events would have recorded that you pressed Run rather than anything you typed, the page is easier to trust when the answer to "what else does it watch" is nothing.

The basis for this is your consent, and nothing else. Withdrawing it has to be as easy as giving it, so it is a button rather than an instruction to go and clear your browser:

Withdraw analytics consent

Cookies, all three of them

Your answer to the banner is not a cookie at all. It is kept in your browser's own storage under cookieConsent, it never leaves the machine, and it is what stops the question being asked twice.

If this goes away

There is no end date. Whenever the demo does end, everything described above ends with it: the counters, the cookies, and the log copies.

Questions to hello@albertoarena.it.