Closed beta
Beta terms and privacy
The field.tours demos are a closed beta. This page is both the terms you agree to when you use one and the privacy information behind the consent notice at the lock screen. In plain words, with nothing left in a footnote.
The short version. A personal access code logs your visit, your route through the tour and, in the tours that keep it, the entire conversation with the host — what you write or say, and everything the host says back. We store it to judge whether the host answers well. The character stories — the expeditions that moved here from exped.earth, each with a field guide — keep the counts and never the conversation. We delete it all at the end of the beta, six months after your code was last used, or the day you ask. Shared codes and declined visits are counted anonymously and never record content.
Who we are
The controller
IVAR Studios AB, org.nr 559059-5392, Sweden, is the data controller for the field.tours closed beta. field.tours is our product; the demos under /demo/ are ours, not the institutions' whose places they show.
For anything on this page — questions, access, corrections, erasure, or withdrawing your consent — write to [email protected]. A person reads it.
What we collect
Three different things, depending on how you got in
A personal access code is one we issued to you by name or by email. A shared code is one handed out at a fair or running on a kiosk. The two are treated completely differently.
With a personal code, after you accept the notice
- Your visit Which gated pages you opened and when; each unlock of your code.
- Your route Which stops you reached and in what order, whether you or the guide moved the camera, what the guide pointed at or lit up, when a session started and ended and how long it lasted.
- The whole conversation, in the tours that keep it Today that is Delsbogården. Every message you send the host — typed or spoken — and every reply, welcome, narration and follow-up the host puts on your screen. If you use the microphone, your speech is transcribed and the transcript is stored like anything else you write. The other tours, and every character story, keep only that a message was sent — never its words.
- Coarse technical context A device family (iOS, Android, Mac, Windows, Linux, other), the language you are reading in, and which rendering backend your browser used. No IP addresses, no fingerprints, no advertising identifiers.
All of it is stored against your access code — not your name, and not your email. Only the request form below, or an invitation we send, ever puts an address in our system, and it is never copied onto the code. The expeditions a personal code used to open on exped.earth have moved here as character stories, each with a field guide where a Standard tour has its host, and their data moved with them: exped.earth had the same controller and the same access codes, so what it logged under your code, including any conversation it kept under its own notice, is held here under this one, with the same retention and the same rights. Here, the character stories keep the counts and never the conversation.
With a shared code, or if you decline
Anonymous counts only: that a session happened in a tour, in a language, on a backend. No route, no conversation, no content, nothing tied to a person. Declining the notice means no personal preview — but also that nothing whatsoever is written about you.
If you ask for access
The request form on the lock screen takes your email address, and optionally a name and an organisation if you choose to give them. That is all it takes, and it is used only to decide on your request and send you a link.
If we invite you instead, one of us types your address into our dashboard and the link goes straight to it — an address you, or someone at your organisation, gave us for this beta. It is held exactly as a request is: in the one place that holds addresses, never on the code, and it is deleted after 30 days if the link is never used, or with the code once it is. The mail says as much.
Why
What it is for, and on what legal basis
Purposes. Evaluating and improving the beta — whether the host answers well, where its material runs out, where a question goes unanswered, which parts of a tour people actually reach — and administering access to it.
Legal basis for everything logged under a personal code: your consent, Art 6(1)(a) GDPR, given at the notice before you enter. You can withdraw it at any time, with effect going forward; write to [email protected] and we revoke the code and erase what is stored under it.
Legal basis for your request email: Art 6(1)(b) — steps taken at your own request before entering these beta terms. If we decline, or you never use the link, the request is deleted after 30 days.
Legal basis for an invitation we send: our legitimate interest in letting the people we work with evaluate the beta, Art 6(1)(f) — the address is used once, to send you the link, and you can object or ask us to delete it at any time at [email protected]. If you never use the link, it is deleted after 30 days.
Why the transcript is a condition of the personal preview, and not an optional extra.
The point of this beta is to find out whether an AI host gives good answers about a real place. That cannot be judged from counts: "twelve questions asked" says nothing about whether the twelve answers were right, useful, or invented. Reading the actual exchanges is the evaluation.
So the personal preview and the transcript are one thing, and we say so rather than burying it: if you would rather not have your conversation stored, decline — and ask us for a shared, counts-only code instead ([email protected]). You lose the personal link and the per-person view; you keep the tour.
Who processes it
The services behind a tour
A tour is a live 3D scene with a language model behind the chat, so parts of your visit necessarily pass through other companies. These are all of them:
- Cloudflare Hosting, the access gate, the database holding everything above, and the aggregate counters. Also Cloudflare Web Analytics, on every field.tours page and in the tours: it counts page views, the site you came from, your browser and type of device, your country and how fast the pages load, sets no cookies, stores nothing in your browser and builds no profile of you. And Cloudflare Turnstile, in the tours: before a tour may use the guide's services (the conversation, the voice, the maps), Turnstile checks in the background that a person and not a script is using the page. It runs in your browser and reads signals from it for that check alone; we learn whether the check passed, nothing else. Data resides in Cloudflare's network.
- OpenRouter, with Mistral AI and OpenAI The guide's replies are generated by Mistral AI's Mistral Small through OpenRouter; when Mistral Small is busy or down, OpenAI's
gpt-4o-miniwrites that reply instead. Your message and the tour's own material are sent for each reply — this was true before we stored anything. Logging adds storage on our side, not a new recipient. - Your browser's speech service, or OpenAI (Whisper) Speech-to-text, only when you use the microphone, and only the audio of what you said. A browser with speech recognition of its own sends it to its maker — Google in Chrome, Apple in Safari, Microsoft in Edge — under that browser's terms; one without (Firefox, a VR headset) sends it through our server to OpenAI's Whisper.
- ElevenLabs The field guides' voices in the character stories: each reply's text is sent to be turned into speech. Nothing you say goes here. A Standard tour's host answers in text.
- Cesium ion, Google and Microsoft Terrain under the 3D model from Cesium ion and, through it, Microsoft's Bing aerial imagery in Delsbogården and Google's Photorealistic 3D Tiles in Nordic Glaciers, streamed to your browser as you move. Your browser's requests reach them; nothing about your conversation does.
- Resend All email — the access link itself, the admin login links. Your address and the message sit in their sent-mail log.
Where these involve transfers outside the EEA, they rest on the EU–US Data Privacy Framework and/or the European Commission's standard contractual clauses.
Not used: advertising networks, analytics products that profile visitors across sites, social plugins, session recording or heatmaps, and — since the gate screens appear before you have agreed to anything — no third-party fonts either. The typeface on every field.tours page is served from this domain.
How long
Retention
Your rights
What you can ask for, and what happens
- Access and portability We export everything held under your code — the code's own record, your consents, every event, the full transcript, including what exped.earth logged before the expeditions moved here — as one JSON file and send it to you.
- Erasure We delete it: every event, every consent record and the code row itself, whether it was logged here or, before the move, on exped.earth. It is one action and it is not recoverable.
- Withdraw consent Same thing, going forward: we revoke the code and erase what is stored under it. Nothing you did before the withdrawal becomes unlawful, it simply stops existing.
- Rectification and restriction Tell us what is wrong or what should stop being used, and we correct it or stop.
- Complain To us first if you like, and to the Swedish authority in any case: Integritetsskyddsmyndigheten (IMY), imy.se.
One address for all of it: [email protected]. Say which access code you hold — that is what we search on, and it saves us asking.
Please note
Two practical things, and the cookies
Don't put sensitive things in the chat. Health, beliefs, politics, anything about other people — in some tours the transcript is stored, and a demo of a farmstead is no place for it. Ask about the place.
The beta is for adult evaluators. Please don't pass your link to anyone under 18; if a child uses it, an adult should be present. The tours themselves are written for school audiences too, and that is exactly why the closed beta — where conversations are recorded — is not where children belong. (Note that anyone you forward the link to sees this notice themselves before anything is logged.)
Cookies. Four, all strictly necessary, none for tracking: ft_code holds your unlocked access and the version of this notice you agreed to (30 days), ft_pending exists for the ten minutes between the notice and your answer, ft_lang remembers whether you are reading in English or Swedish so every page — this one, the lock screen, the preview itself — comes up in the same language (a year, two letters, nothing about you), and __Host-ft_admin is our own administrators' session. No advertising cookies, no cross-site tracking, no data sold or shared for anyone else's purposes — which is why there is no cookie banner to click away.