Vegferd in AI assistants — Privacy

Last updated: 22 October 2026.

This policy applies when you use Vegferd through an AI assistant, such as ChatGPT from OpenAI or Claude from Anthropic. It supplements the Privacy Policy for Vegferd, which covers the account and the app; what is stated there applies here too.

1. Who we are

Vegferd is provided by Millingly AS (organisation number 937 731 760) in Bergen, Norway, under the brand name Viti Geo. Millingly AS is the controller of the personal data described here. “We” and “us” mean Millingly AS.

Questions about privacy go to personvern@vitigeo.com.

2. In short

• The assistant is a different service from us. Your conversation is held by the provider of the assistant, under its own terms. We receive only what the assistant sends us to answer one question, and we send back only the answer.
• We do not store what you ask. Places and times are used to compute the answer and are then gone. A planned route is kept for 30 minutes under a random number, so follow-up questions can use it, with nothing linking it to you.
• You sign in with your Vegferd account, so we know who is asking, and your subscription comes with you. We keep no history of what you ask.
• Our operations log never contains the question, only which tool answered, how long it took and how many results it gave.

3. What we process, and why

3.1 The account and the connection

To use Vegferd in an assistant, you sign in with your Vegferd account and approve that the assistant may ask on your behalf. We then process:

• your email address and the user identity that links your sign-ins together (the same as in the app, section 3.5 of the Privacy Policy),
• the approval: which assistant you have granted access, and when.

The sign-in service also records the time, IP address and browser type of the sign-in, to keep the session secure. The assistant receives an access token stating that it asks for you; the token carries your user identity, not your email address.

Your subscription is looked up on the account for each question, so what you bought in the app applies in the assistant too. We do not store the lookup.

3.2 What you ask about

When you ask a question, the assistant decides what to send us. It is what is needed to answer:

• place names, addresses or coordinates for the start, destination and stops,
• departure or arrival time,
• properties of the vehicle, if you have given them (for example that it is electric, or its height),
• which ferry quay, mountain pass or stretch of road you are asking about,
• your language, and some assistants send an approximate location (city, region, country). We use it only to pick the right place when a name exists in several places in Norway, and to rank search results.

We use this to compute the answer: the route, the ferries, the messages from the Norwegian Public Roads Administration, the weather along the route, the toll and ferry prices, the charging stations and the stops. None of it is stored, with one exception: a planned route is kept for 30 minutes under a random number, so the assistant can ask about the weather, the cost, the traffic or the stops on that same route without computing it again. The number is not linked to you, and the route is deleted automatically.

Your question itself, as you typed or said it, we never see. The assistant turns it into a lookup, and we receive the lookup.

3.3 The operations log and usage limits

For each answer we write to the operations log: the time, which tool answered, how long it took, whether it found anything, how many places or routes it gave, and which sources the answer was built on. Never the places, the times or the question.

Each account has a limit on how many questions it can ask per hour and per day, so one account cannot drain the service. The limit is counted on your user identity. If a question is refused — because the limit is reached, or because the access token is not valid — your user identity may appear in the operations log together with the reason.

The cloud provider keeps a request log in front of the service with the IP address, the time and which service was called. That IP address is the assistant’s, not yours: it is the assistant’s servers that ask us.

4. The assistant

The provider of the assistant — OpenAI for ChatGPT, Anthropic for Claude, or another one you connect — processes your conversation under its own terms and its own privacy policy, as an independent controller. That covers both what you write and the answers we give, which become part of the conversation held by them.

We have no agreement with the assistant provider about your data, and we have no access to your conversation. We receive only the lookups in section 3.2 and send back only the answers to them. We never send your email address or anything else about your account to the assistant.

5. What we store, and for how long

What	For how long
A planned route: start, destination, stops, time and vehicle properties, under a random number	30 minutes, then deleted automatically
Operations log: time, tool, response time, number of results, sources. On refusal: the user identity and the reason	30 days, then deleted automatically
The cloud provider’s request log: the assistant’s IP address, time, which service was called	30 days, then deleted automatically
The approval: which assistant has access to your account	Until you revoke it, or delete the account
Account: email, user identity, sign-in sessions	Until you delete the account in the app

All of this is stored with processors in the EU/EEA (section 7). What the assistant stores, and for how long, is decided by the assistant provider (section 4).

6. Legal basis

Processing	Basis (GDPR art. 6)
The answer to what you ask, and the route kept for 30 minutes	Necessary to provide the service you request — contract (b)
The account, the approval and the subscription lookup	Contract (b)
The operations log and the usage limits	Legitimate interest (f): keeping the service secure, available and correct

7. Who processes data for us, and whom we ask

Processors — process data on our behalf, under agreement with us:

Who	What	Where
Google Cloud	Runs the servers and the operations log	Netherlands (europe-west4)
Supabase	Sign-in, the approval of the assistant and the account	Frankfurt. Supabase is a US company; see section 8
Proton	The email with the sign-in code	Switzerland

The sources we ask to answer — the Norwegian Public Roads Administration, Entur, the Norwegian Meteorological Institute, the Norwegian Mapping Authority, NOBIL and the others listed in the data sources — receive no data about you. The Meteorological Institute receives points along the route, rounded to about one kilometre.

8. Transfers outside the EEA

Supabase is a US company. Our database is in Frankfurt, but the company’s own operational data may be processed outside the EEA, under the European Commission’s standard contractual clauses (SCC, decision (EU) 2021/914). Proton is Swiss; Switzerland has an adequate level of protection under the European Commission’s decision.

The assistant provider processes your conversation where it is based, for OpenAI and Anthropic in the United States. That happens under the provider’s own terms and is not a transfer from us.

9. Your choices and rights

• Revoke access in the assistant’s settings, where connected apps or connectors are listed. The assistant can then no longer ask for you.
• Delete the account in the Vegferd app, under your account: “Delete account”. The account, the email address, the sign-in sessions and the approval are then deleted for good with us.
• The conversation with the assistant you delete with the assistant provider.

You have the right of access, rectification, erasure, objection and data portability, as described in section 9 of the Privacy Policy. Write to the address in section 1; we reply within a month. You can complain to the Norwegian Data Protection Authority, Datatilsynet (datatilsynet.no).

We make no automated decisions about you and build no profile of you.

10. Changes

If we change how we process personal data in the assistants, we update this policy and the date at the top.