Legal
Privacy Policy
Last updated: 17 November 2026
1. Who we are
Liivo is a service operated by Eyevinn Technology AB, a company registered in Sweden (org. nr. 556919-9952), with registered address at Vasagatan 52, 111 20 Stockholm, Sweden.
You can reach us at support@liivo.ai.
2. What data we collect
We collect the minimum information needed to operate the service:
- Prompt helper input: the app description you type into the prompt helper on this site. We send it to an AI model to generate a prompt for you, and we do not store the text itself.
- Account information: your email address and, if you pay, your billing name and payment details (processed by our payment provider, Stripe).
- App data: the apps you create using Liivo, including their configuration and content. This data belongs to you.
- Usage data: anonymous, aggregated analytics about how the service is used (page views, which buttons and links are used, and page-speed measurements), collected with privacy-friendly, cookieless analytics (Umami) that set no cookies, store nothing on your device, and collect no personal data. Because it places nothing on your device, this runs on our legitimate interest in understanding which pages work rather than on your consent, and it is on by default. You can object at any time by switching off "Usage and performance" in our cookie banner. Separately, and only with your consent, we use advertising and marketing cookies to measure our campaigns (see section 10).
- Support chat: the messages you send through the support chat on this site, any details you type into it (such as your name or email address), and the conversation history. The support chat is provided through a Chatwoot instance that we run on Eyevinn Open Source Cloud. We use it to answer your question, on the basis of our legitimate interest in helping visitors (Article 6(1)(f) GDPR), and keep the conversation for 12 months after the last message in it, then delete it. It also sets a cookie (see section 10).
- Technical logs: server logs kept for debugging and security purposes, which contain the IP address of each request. When you sign in or sign up, and in the audit logs described in section 12, we also record the IP address of the request as our platform receives it and your user agent, which is the name and version of your browser or client software. We use them for security, abuse prevention and traceability only. Tool calls made by an AI assistant on your behalf, and requests to our in-app assistant, are recorded separately and are covered by section 12.
3. What we do NOT collect
- We do not read, store, or access the conversations you have with your AI (Claude or ChatGPT). We do record the calls your assistant makes to our tools, which is a different thing and is described in section 12.
- We do not sell your data to third parties, ever.
- We do not load advertising or marketing trackers without your consent. They are off by default and load only after you accept them in our cookie banner (see section 10).
4. MCP tools and AI assistant data flows
Liivo exposes a set of MCP (Model Context Protocol) tools that AI assistants such as Claude and ChatGPT can call on your behalf. When you connect Liivo to an AI assistant and ask it to manage your apps, the assistant will invoke these tools to read and modify your Liivo data. This means the following information may be sent to the AI provider you are using (e.g., OpenAI when using ChatGPT, or Anthropic when using Claude):
- App data: the names, statuses, and settings of apps you have created with Liivo.
- App status: resource usage and health of your running apps.
- Configuration values: settings and parameters you have supplied for your apps. Sensitive access tokens stored securely by Liivo are not shared with your AI assistant. However, other app settings — including any passwords you supplied when configuring your apps — may be shared with your AI assistant.
When you use Liivo through ChatGPT, this data flows through OpenAI’s infrastructure and is subject to OpenAI’s privacy policy. When you use Liivo through Claude, this data flows through Anthropic’s infrastructure and is subject to Anthropic’s privacy policy. We have no control over how these providers handle data once it has been transmitted to them.
You choose which AI assistant to connect to Liivo and when to use MCP tools. If you prefer that your app data is not shared with a third-party AI provider, do not connect Liivo to an AI assistant.
5. How we use your data
We use your data to:
- Provide and operate the Liivo service.
- Send you important service emails (account confirmation, billing receipts, critical updates).
- Respond to your support requests.
- Improve the service through anonymous, aggregated usage analysis.
6. Legal basis for processing (GDPR)
We process your data under the following legal bases as defined by the General Data Protection Regulation (GDPR):
- Contract performance: processing necessary to provide the service you signed up for.
- Legitimate interests: security, fraud prevention, and improving the service.
- Legal obligation: keeping billing records as required by Swedish accounting law.
- Consent: for advertising and marketing cookies on this site (section 10) and, if you tick the optional box when you create your workspace, for measuring our ads on Google (section 7). You can withdraw consent at any time.
7. Data storage and transfers
We process your data using reputable infrastructure providers. Any transfer of personal data to third parties or sub-processors is governed by appropriate safeguards in accordance with GDPR requirements, including standard contractual clauses where applicable.
Named processors: Anthropic processes the text you enter into the prompt helper on this site, in order to generate a prompt for you. We send the text you type and the language of the page you are reading, and nothing else. Your IP address, your session identifier and your browsing history are not sent, and we do not store the text you typed.
When you leave feedback while changing or cancelling your plan, we send the reason you choose and any text you type, together with your workspace id, to our team’s Slack workspace so we can read it. We do not send your email address. Unlike the text you enter into the prompt helper, this message is kept in that Slack workspace.
Google (Google Ads Enhanced Conversions) receives, only if you tick the optional box when you create your workspace, a hashed copy of your email address, the Google ad click reference if you arrived from a Google ad, and the event (workspace created, first deployment, first paid plan) with its time and, where the event has them, its value, currency and an order reference. Google matches it to Google accounts so that we can measure and improve our ads on Google. Google acts as our processor under its Ads Data Processing Terms. Our contract is with Google Ireland Limited, and where Google processes the data in the United States its terms apply the European Commission's standard contractual clauses. You can withdraw at any time in your account profile at app.osaas.io, or by emailing help@liivo.ai; we then stop sending, for all your workspaces.
8. Your rights
Under GDPR, you have the right to access, correct, or delete your personal data at any time. You can also request that we restrict processing or export your data in a portable format.
To exercise any of these rights, email us at support@liivo.ai. We will respond within 30 days. You also have the right to lodge a complaint with the Swedish Authority for Privacy Protection (IMY) at imy.se.
9. Data deletion
You can ask us to delete your account at any time by emailing support@liivo.ai. Within 30 days of receiving your request, we delete your account and permanently delete all your personal data and app data, except security and audit records, which are kept as described in section 12, and, if we sent data to Google on the basis of your consent, the record of that consent and of what we sent, which we keep for 5 years after deletion only to be able to show that we had your consent. Billing records that Swedish accounting law requires us to keep (Bokföringslagen, chapter 7, section 2) are kept until the end of the seventh year after the end of the calendar year in which the relevant financial year ended.
10. Cookies
LIIVO uses strictly necessary cookies for authentication and session management. We also use privacy-friendly, cookieless analytics (Umami) that set no cookies, store nothing on your device, and collect no personal data; because nothing is placed on your device it does not require your consent, so it is on by default and you can object at any time by switching off "Usage and performance" in our cookie banner. With your consent, we additionally use advertising and marketing cookies from Google, Meta, and TikTok to measure our campaigns and show relevant ads. Advertising is a separate choice and is also off by default. You can change or withdraw either choice at any time via the Cookie Settings link in the footer, or control cookies through your browser settings; objecting to analytics reloads the page so collection stops immediately.
The support chat widget sets one cookie, named cw_conversation, when you open the support chat. It is host-only on www.liivo.ai, lasts 365 days, and is used to keep your chat conversation. The support chat is provided through a Chatwoot instance that we run on Eyevinn Open Source Cloud.
11. Changes to this policy
We may update this policy from time to time. When we do, we will update the date at the top and notify you by email if the changes are significant.
12. Operational audit logging
Three kinds of request are written to an operational audit log: every call an AI assistant makes to our MCP tools on your behalf, every request to our own in-app assistant, and every request to our explain-failure feature, which asks for an explanation of a failure. This happens on every request and it is not optional, because it is how we keep a shared platform secure, investigate abuse, and show what happened in an account.
Each entry for an MCP tool call records the time of the call, your user and account identifiers, which tool was called and what it acted on, whether it succeeded, how long it took, which AI client you connected, and the operational context of the call. Operational context means the values you passed to the tool, such as the name of an app you asked it to create, and for a failed call the error text the tool returned.
This is not the same as reading your conversation. As section 3 says, we do not read, store or access the conversation you have with Claude or ChatGPT. That conversation is never sent to us. What we record is the calls your assistant makes to us, which means that where you yourself put text into a tool, such as the description of an app you asked it to build, that text is recorded.
Requests to our own in-app assistant and to the explain-failure feature are separate from that. An entry for a request to the in-app assistant records your user and account identifiers, that it was a chat request, whether it succeeded, how long it took, where the request came from, whether tool access was switched off, and for a failed request the error text. It does not hold your message or the answer. If a message contained a secret that we removed before processing it, a further entry records the kind of secret found, not the secret. An entry for an explain-failure request records your user and account identifiers, the kind and subject of what was explained, the size of the input, whether it succeeded, how long it took, and for a failed request the error text.
In the entries of all three kinds we also record the IP address and the user agent. The IP address is the one of the request as the platform receives it from the ingress. Where a request reaches the audit log from another part of our own platform, for example from the servers of the web console, the entry holds no address for you, and when the model provider calls our tools on behalf of the in-app assistant, the entry holds the provider's address.
We record the IP address and the user agent for security, abuse prevention and traceability, and for nothing else. This is what is recorded, for how long, and who can see it:
- The audit log above (all three kinds of entry): what is described above, plus the IP address and user agent. Entries are deleted automatically after 90 days. Only platform administrators can see it.
- Token audit events: the actor, the user, the IP address, the user agent and the token action. Kept for 365 days. Managers of a workspace can see the events of their workspace, including the IP addresses, and other users see the events of their own tokens.
- Sign-in and sign-up events: the user, the IP address, the user agent and the sign-in method. Kept for 365 days. Only platform administrators can see them.
- Activity log: the record of what happened in a workspace now also holds the IP address and user agent of the person acting. It is erased when the workspace or your user account is closed. Managers of the workspace can see it.
- Staff admin console audit: the IP address and user agent of the staff member who acts in our admin console. It has no automatic expiry. Only our staff can see it.
- Ingress and service logs: contain the IP address of the request. They are retained and deleted under our general logging practices, and only our staff can see them.
Our legal basis is our legitimate interests under Article 6(1)(f) GDPR: keeping a shared platform secure, detecting abuse, and diagnosing faults. We do not ask for your consent for this log, and we want to be plain about why: consent has to be as easy to withdraw as it was to give, and a log that cannot be switched off could not honestly be described that way. An IP address is personal data, so we use the address and the user agent only for security, abuse prevention and traceability, limit who can see them as described above, and delete them on the schedule above. Because we rely on legitimate interests you can object at any time under Article 21 GDPR, and we will stop unless we can show compelling grounds that override your interests.
If you ask us to delete your data we may keep these logs for their remaining retention period, because Article 17(3)(e) GDPR allows it where a record is needed to establish or defend legal claims, and a security log is exactly that.
13. Contact
For any privacy-related questions, contact us at support@liivo.ai.