Liva
Privacy Policy
Dette dokument findes på dansk og engelsk. Den danske version er gældende.
This policy explains how 2036 Innovation ApS (“Liva”, “we”) processes personal data when you visit liva.so, create an account and use the Liva service.
1. Controller and contact
2036 Innovation ApS, CVR no. 39485974, c/o Cursum A/S, Ragnagade 7, 2100 København Ø. Email: team@liva.so.
Contact us with questions about this policy or to exercise your rights.
2. When we are controller – and when we are processor
Controller: We are the controller for data about users and customers that we need to provide and run the service: account and sign-in, team membership, payment and invoicing, email from us, support, security and visits to liva.so.
Processor: For content a customer adds to or connects with Liva – such as website content, articles, measurements, Google Search Console data and CMS connections – we process personal data on the customer’s behalf and instructions. This is governed by our Data Processing Agreement, which forms part of the Terms of Service.
3. Data we process
- Account: email address, hashed password (if you use one), sign-in method (email link, password or Google), sign-in times and technical data logged by Supabase Auth for security (e.g. IP address).
- Setup without an account: If you enter your website on the front page, setup starts without an account using a temporary, anonymous sign-in session (Supabase Auth). The website address, the analysis and your setup choices are stored temporarily so they carry over when you create your account at the end. If you do not create an account, everything is deleted automatically after 7 days. When you create your account with your email address, Cloudflare Turnstile may check that you are not a bot, and for the AI analyses we store a hash of your IP address for 1 day to limit abuse (legitimate interest, Art. 6(1)(f)).
- Team: which websites you can access, your role (owner, admin, editor or viewer), invitations and an audit log of changes.
- Website and content: the website address, public content we fetch from it, business profile, audience, tone and settings, topic plans, articles, images, chat messages to the Liva agent and per-request AI cost records.
- Measurements: questions, AI answers, mentioned brands, sources and keyword data; Domain Rating for the domain.
- Google data: only if you connect Google Search Console – see the Google data section below.
- Publishing: details of the connected CMS and encrypted credentials for it, and public URLs of published articles.
- Payment: Stripe customer and subscription IDs, subscription status, billing address, VAT number and invoices. We do not receive or store card numbers.
- Marketing (consent only): your cookie choice, Meta cookie IDs (
_fbp/_fbc), the first page visited and campaign parameters, and events such as account creation and purchase – see the section on ad measurement with Meta. - Statistics with Microsoft Clarity (consent only): recordings of clicks, mouse movements and scrolling on the public pages, in sign-up and in setup, and heatmaps – with typed input masked – see the section on Microsoft Clarity.
- Communication: emails we send (invitations, weekly summaries and service emails about the free days), whether an email was sent, your email preferences and messages you send us.
Liva is intended for businesses. We do not ask for special categories of data and you should not enter them.
4. Purposes and legal bases
- Creating and running your account, providing the service and team access – performance of the contract (GDPR Art. 6(1)(b)).
- Payment, invoicing and bookkeeping – contract (b) and legal obligation under the Danish Bookkeeping Act (c).
- Invitations and weekly summaries – contract (b) and our legitimate interest in keeping you informed (f). Summaries can be turned off under Settings → Team.
- Service emails to a website’s owner about the free days (first article ready, 1 day left, pause when the free days end and at most two reminders 3 and 7 days later) – legitimate interest in informing you about the status of the service (f). They stop when a subscription starts and can be turned off under Settings → Team → Email notifications. We record that an email was sent (type and time, without the email address) in Liva’s own statistics, and links in the emails contain campaign parameters (
utm_*). - Cookieless, aggregate counting of visits and of clicks on selected buttons on the public pages (how many people visit, where they come from and how many continue) – legitimate interest in understanding whether our pages and campaigns work (f). No cookies and no identifier are used; see the section on Liva’s own statistics.
- Recording how far people get in setup – including setup without an account – to find and fix places where customers get stuck – legitimate interest in operating and improving the service (f); see the section on Liva’s own statistics.
- Security, abuse prevention, debugging, cost control and defending legal claims – legitimate interest (f).
- Measuring and optimising our ads with the Meta Pixel and Conversions API, and campaign information – only with your consent (a).
- Recordings of anonymised clicks and scrolling and heatmaps with Microsoft Clarity, to find and fix places on the pages where visitors get stuck – only with your consent (a).
- Support and answering enquiries – contract or legitimate interest (b/f).
Apart from ad measurement with your consent, we do not build marketing profiles, do not sell your data and do not make decisions based solely on automated processing that produce legal effects for you (Art. 22).
5. AI processing
Liva uses the OpenAI API to analyse the website, suggest topics, write articles and images, answer in chat and suggest optimizations. Requests are sent with store:false, and under OpenAI’s API terms data sent through the API is not used to train models. OpenAI may retain requests for a limited period to prevent abuse.
For visibility measurements we ask questions about topics and industries through DataForSEO, which forwards them to the AI services being measured (ChatGPT search, Google AI Overviews, Gemini, Claude and Perplexity). The questions contain brand and topic terms, not contact details. Liva does not send Google data to AI services.
6. Google data (Search Console)
When an owner or admin chooses to connect Google, Liva requests read-only access with this single scope:
https://www.googleapis.com/auth/webmasters.readonly(Google Search Console): the list of your Search Console properties and your permission level, so you can choose the property matching the website; and total clicks, impressions, click-through rate and average position – overall, per day and for up to the 50 top pages – for the last 7, 30 and 90 days, limited to the website’s own domain. We do not retrieve search queries.
Liva does not request access to Google Analytics.
Use: The data is only shown as a traffic overview in Liva to the team of that website. It is not used for advertising, not sold, not transferred to others, not sent to AI services and not used to train AI models. Humans at Liva only read it with your permission, where necessary for security or to comply with law.
Storage: Google tokens are stored encrypted (AES-GCM) in a private table that browsers cannot access. Reports are stored per website with access control.
Revocation: You can disconnect Google in Liva’s traffic/Google settings; we then delete the encrypted tokens and stored reports. You can also remove Liva’s access in your Google Account at https://myaccount.google.com/permissions.
Limited Use: Liva’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
7. Sub-processors and other recipients
We use these providers. They may only process the data to provide their service to us.
| Provider | Purpose | Location |
|---|---|---|
| Supabase, Inc. | Database, sign-in (Supabase Auth), server functions and background jobs. | EU – AWS eu-north-1 (Stockholm, Sweden). Support and operations may take place outside the EU/EEA. |
| Cloudflare, Inc. | Hosting of liva.so (Cloudflare Pages), CDN, DNS and attack protection. Cloudflare also provides an approximate country hint used to choose the interface language. Cloudflare Turnstile protects against bots when you create your account with your email address after a setup without an account (browser and device signals and IP address; no marketing cookies). | Global network; US company. |
| OpenAI | AI analysis of the website at onboarding, topic plans, article text and images, chat with the Liva agent, optimization suggestions and measurements through the OpenAI API with web search. Requests are sent with store:false, and under OpenAI’s API terms data sent through the API is not used to train models. | United States. |
| DataForSEO | Keywords, search results and AI answers for research and visibility measurements (ChatGPT search, Google AI Overviews, Gemini, Claude and Perplexity). DataForSEO asks the questions to those services; Liva has no direct agreement with Anthropic (Claude), Google (Gemini) or Perplexity for this. Questions about topics and industries are sent – not contact details. | Outside the EU/EEA (to be confirmed in the provider’s agreement). |
| Ahrefs Pte. Ltd. | Domain Rating for the website’s domain. Only the domain name is sent. | Singapore. |
| Resend, Inc. | Transactional email: team invitations, weekly owner summaries and service emails about the free days to owners (which can be turned off). | United States. |
| Stripe Payments Europe, Ltd. | Payments, subscriptions, invoices, VAT and the customer portal. Card details are handled solely by Stripe. Stripe is an independent controller for, among other things, fraud prevention and legally required checks. | Ireland (EU); the Stripe group also processes data in the United States. |
| Google (Google Ireland Ltd. / Google LLC) | Sign in with Google; read-only access to Google Search Console when a user connects it; fonts (Google Fonts) and icons for source domains in the app. | EU and United States. |
If you consent to marketing cookies, Meta Platforms Ireland Ltd. also receives data as a joint controller – see the section on ad measurement with Meta. If you consent to Statistics, Microsoft also receives data through Microsoft Clarity – see the section on Microsoft Clarity.
We also share data with the CMS you connect yourself (e.g. WordPress, Webflow, Wix, Shopify, Ghost, Framer or Lovable) when Liva publishes articles there, and with other participating websites in the link network if you opted in – see the Terms of Service. We may disclose data where required by law.
8. Transfers outside the EU/EEA
Some providers process data outside the EU/EEA, in particular in the United States. We only transfer data with a lawful transfer mechanism: an adequacy decision (for the US: the EU-U.S. Data Privacy Framework where the provider is certified) or the European Commission’s Standard Contractual Clauses with supplementary measures where needed. Contact us for a copy of the relevant mechanism.
10. Liva’s own statistics
To improve sign-up, setup and the app, we record ourselves how far users get: page views, setup steps, error types and clicks on selected buttons (named buttons, not text). Data is sent only to Liva’s own server (Supabase in the EU) and is not shared with third parties, ad networks or analytics providers. Microsoft Clarity, which is only used with consent to Statistics, is described in the section on Microsoft Clarity.
- Cookieless visit counts (all visitors, without consent): For each page view on the public pages, when you enter a website address on the front page and when you click selected buttons (e.g. starting setup, create account, log in and language choice – only the button’s name), we record an aggregate count with the page (without query parameters), referring domain, campaign parameters (
utm_*) from the page address, device type (mobile/desktop from screen width), language, time and whether you came from another page on liva.so. Nothing is stored on or read from your device (no cookies, no local storage), no visitor or session ID and no fingerprinting is used, and the counts cannot be linked to you or to each other. Your IP address is only used briefly in memory to limit abuse, and the browser’s user agent only to filter out bots; neither is stored. Legal basis: legitimate interest in knowing how many people visit the pages, where they come from and where they drop off (Art. 6(1)(f)). - Detailed statistics (consent only): If you accept Statistics, the browser stores a random visitor ID (
liva_vid), and we record the page (without query parameters exceptutm_*), referring domain, device type (mobile/desktop from screen width), language and time. If you create an account, these events are linked to it. Legal basis: consent (Art. 6(1)(a) GDPR and the Danish cookie order). - During setup and when signed in: Without consent we only record progress through sign-up, setup and payment (e.g. which steps are viewed and completed and when, whether the “Liva is thinking…” screen was shown, whether you chose to fill in yourself, error code, the chosen way to create the account and checkout started) with a session ID for the tab, to find and fix places where customers get stuck. This also applies to setup without an account: progress is linked to the temporary, anonymous sign-in session. If you create the account, the progress stays with it. If you do not, the link is removed when the session is deleted after 7 days, and the progress is kept only with the session ID. If you start setup from the front page through a campaign link, the campaign source and name (
utm_sourceandutm_campaign, passed in the address and not stored in your browser) are recorded with the start of setup, so we can see which campaigns bring customers. Legal basis: legitimate interest in operating and improving the service (Art. 6(1)(f)). Page views with an ID and clicks are only recorded with consent. - Never: IP addresses, emails, typed text, URLs you enter, article content or free text. Only Liva’s superadministrator can see the statistics.
- Retention: 13 months; older events are deleted automatically. You can withdraw consent via Cookie settings; the visitor ID is then deleted in the browser and no further anonymous events are recorded.
11. Microsoft Clarity (consent only)
This section only applies when you give consent to Statistics. The purpose is to see how visitors use the public pages, sign-up and setup (for example where people click, how far they scroll and where they get stuck), so we can improve them.
- What is collected: Once you have accepted, the page loads Microsoft Clarity from
www.clarity.ms. Clarity records clicks, mouse movements, scrolling, page changes, screen size, browser and device information, approximate location derived from the IP address and times, and creates recordings of the visit (session replay) and heatmaps. Clarity sets cookies (_clck,_clsk) on liva.so and may set cookies on Microsoft’s own domains (e.g.CLIDandMUID). - Masking: All input fields and forms are masked, so what you type (e.g. email, website address, business description and competitors) is never recorded. On the sign-up and setup pages all text is masked, and Clarity is set to strict masking. Clarity is never used in the app when you are signed in and see customer data, or in the administration, and not for automated browsers.
- Legal basis: your consent (GDPR Art. 6(1)(a) and section 3 of the Danish Cookie Order). You can withdraw it at any time via Cookie settings; Clarity is then stopped, Clarity is told that consent was withdrawn, and we delete
_clck/_clskin the browser, as far as the browser allows. Withdrawal does not affect the lawfulness of processing before it. - Microsoft’s role: Microsoft Ireland Operations Ltd., One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, D18 P521, Ireland, provides Clarity under the Microsoft Clarity Terms of Use. Microsoft processes the data as our processor when it provides recordings and heatmaps to us, and under those terms may also use it for its own purposes (e.g. to improve and develop its products and services) under its own responsibility; to that extent Liva and Microsoft are joint controllers for the collection on liva.so. See Microsoft’s Privacy Statement.
- Transfers: Microsoft may transfer data to Microsoft Corporation in the United States. Microsoft Corporation is certified under the EU-U.S. Data Privacy Framework.
- Retention: Microsoft keeps recordings for up to 30 days and heatmaps and aggregate data for up to 13 months. The
_clckcookie expires after up to 12 months and_clskafter up to 1 day.
12. Ad measurement with Meta (consent only)
This section only applies when you give consent to marketing cookies. The purpose is to measure whether our ads on Facebook and Instagram lead to visits, sign-ups and purchases, and to optimise the ads (for example, showing them to people similar to those who signed up).
- Meta Pixel (browser): Once you have accepted, liva.so loads Meta’s script from
connect.facebook.net. It sends, among other things, the page address, time, browser information, your IP address, the_fbp/_fbccookies and events such as page views, views of the pricing and product pages, entering a website address (without the address itself), onboarding steps (only the step number and name, never what you type), account creation, start of the free period, first connection of a website (only the CMS type), first published article and subscription purchase (amount and currency). We do not send your email, name or website content through the pixel. In the app the pixel is only loaded for these events and never to measure page views. - Conversions API (server): If you gave consent and it is recorded on your account, our server sends events for account creation, free-period start, first connection of a website, first published article, purchase, renewal (amount and currency) and subscription cancellation (monthly or yearly) directly to Meta with a hashed (SHA-256) email address, a hashed user ID,
_fbp/_fbc, the browser’s user agent and – for events that happen while you use the site – your IP address. Browser and server use the same event ID, so Meta counts the event only once. - Campaign information: With your consent we store the first page you visited, any UTM parameters and whether you came via a Meta ad (fbclid) on your account when you create it, so we can see which campaigns bring customers.
Legal basis: your consent (GDPR Art. 6(1)(a) and section 3 of the Danish Cookie Order). You can withdraw it at any time via Cookie settings; this does not affect the lawfulness of processing before withdrawal. If you withdraw consent while signed in, we delete the campaign information and Meta identifiers on your account and send no further events about you to Meta.
Joint controllership: For the collection via the Meta Pixel and the transmission to Meta, Liva and Meta Platforms Ireland Ltd., Merrion Road, Dublin 4, D04 X2K5, Ireland, are joint controllers (Art. 26) under Meta’s Business Tools Terms and Meta’s Controller Addendum. Meta has undertaken to inform you about the processing and to handle requests about your rights regarding Meta’s processing; you may also contact us. Meta’s further processing (e.g. ad delivery and its own purposes) is Meta’s own responsibility – see Meta’s Privacy Policy.
Transfers: Meta may transfer data to Meta Platforms, Inc. in the United States. Meta Platforms, Inc. is certified under the EU-U.S. Data Privacy Framework; Meta also relies on the European Commission’s Standard Contractual Clauses.
Retention: _fbp and _fbc expire after 90 days (renewed on visits). Your cookie choice is stored for 12 months, after which we ask again. Consent, campaign information and a log of sent events (event type, event ID and status – no content) are kept for as long as the account exists or until you withdraw consent. Meta retains data under its own terms.
13. How long we keep data
| Data | Retention |
|---|---|
| Account, websites, team memberships, settings, articles and measurements | For as long as the account is active. Deleted no later than 30 days after the account or website is closed, or on request. |
| Setup started without an account (website address, analysis, setup choices and the temporary anonymous sign-in session) | Deleted automatically 7 days after it started if no account has been created. If you create an account, the account rules apply. |
| Hash of the IP address used to limit AI analyses without an account | 1 day. |
| Backups | Deleted data may remain in backups for up to 30 days before being overwritten. |
| Raw page content fetched from websites for analysis | 7 days (suggestion candidates 2 days). |
| Google access tokens and traffic reports | Until the connection is disconnected in Liva; the encrypted tokens and stored reports are then deleted. |
| Consent, campaign information and log of events sent to Meta (consent only) | For as long as the account exists or until consent is withdrawn (campaign information and Meta IDs are then deleted). The cookie choice is stored in the browser for 12 months. |
| Liva’s own statistics (cookieless visit counts, page views, clicks and steps in sign-up and setup) | 13 months; older events are deleted automatically every night. |
| Recordings and heatmaps in Microsoft Clarity (only with consent to Statistics) | Recordings up to 30 days; heatmaps and aggregate data up to 13 months (kept by Microsoft). |
| Accounting records (invoices and payments) | 5 years from the end of the financial year they relate to (Danish Bookkeeping Act). |
| Email queue (sent invitations and summaries) | 90 days. |
| Security and audit logs (e.g. team changes) | For as long as the website exists, at most 3 years. |
Providers’ own logs are kept according to their terms.
14. Security
- Data access is restricted per website with row-level security (RLS) in the database and roles for owner, admin, editor and viewer.
- Google tokens and CMS credentials are encrypted (AES-GCM) and cannot be read from the browser. Secret API keys exist only on the server.
- All traffic is encrypted (HTTPS). Sign-in uses PKCE, and invitations require a verified email.
- Only a limited number of approved staff have operational access; significant actions are logged.
- Card data is handled solely by Stripe.
15. Your rights
You have the right of access, rectification, erasure, restriction, data portability and to object to processing based on legitimate interest. Where you gave consent, you can withdraw it at any time. Write to team@liva.so; we normally reply within one month. Where we process the data as a processor for a customer, we forward your request to that customer.
16. Complaints
You can complain to the Danish Data Protection Agency (Datatilsynet), Carl Jacobsens Vej 35, 2500 Valby, Denmark, www.datatilsynet.dk. We would appreciate hearing from you first.
17. Changes
We update this policy when the service or providers change. Material changes are announced in the app or by email. The date and version at the top show the current edition.