Back to home

Privacy Policy

Information about how we handle your personal data

This document is only partly translated so far. Sections with an English version are shown in English, the others in German. Only the German version is binding.

Der Schutz Ihrer personenbezogenen Daten ist uns ein wichtiges Anliegen. In dieser Datenschutzerklärung informieren wir Sie darüber, welche Daten wir erheben, wie wir sie verarbeiten und welche Rechte Ihnen zustehen. Obwohl LF Digital Solutions LLC als US-Unternehmen nicht unmittelbar der DSGVO unterliegt, richten wir uns freiwillig nach den hohen europäischen Datenschutzstandards, da sich unser Angebot vorrangig an Nutzer im europäischen Raum richtet.


1. Verantwortliche Stelle

Verantwortlich für die Verarbeitung personenbezogener Daten im Zusammenhang mit diesem Dienst ist:

LF Digital Solutions LLC 30 N Gould St Ste N Sheridan, WY 82801, USA

Vertreten durch: Finn Stolle (Managing Member) E-Mail: help@kontavio.com

Einen gesonderten Datenschutzbeauftragten haben wir nicht bestellt, da dies nach geltendem Recht nicht erforderlich ist. Für alle Datenschutzanfragen wenden Sie sich bitte direkt an die oben genannte E-Mail-Adresse.


2. Grundsätze der Datenverarbeitung

Wir verarbeiten personenbezogene Daten nur, soweit dies zur Bereitstellung unseres Dienstes erforderlich ist oder Sie eingewilligt haben. Dabei beachten wir die Grundsätze der Datensparsamkeit und Zweckbindung. Konkret bedeutet das:

  • Wir erheben nur Daten, die für die jeweilige Funktion tatsächlich benötigt werden.
  • Wir verkaufen, vermieten oder handeln keine personenbezogenen Daten.
  • Wir betreiben kein Profiling. An ein Werbenetzwerk (Meta) geben wir Daten nur mit Ihrer Einwilligung weiter (Punkt 6.6).
  • Wir setzen keine Analyse-Dienste von Drittanbietern und keine Social-Media-Plugins ein. Das Meta-Pixel laden wir nur, wenn Sie im Cookie-Banner „Marketing“ erlauben (Punkt 6.6). Unsere eigene Seitenstatistik läuft auf unserem Server, ohne Cookies und ohne Einträge im Speicher Ihres Browsers (Punkt 3.4). Klick-Kennungen aus Anzeigen speichern wir nur mit Ihrer Einwilligung (Punkt 7).

English translation of the changed parts:

  • We do not do any profiling. We pass data to an advertising network (Meta) only with your consent (section 6.6).
  • We do not use analytics services from third parties and no social media plugins. We load the Meta pixel only if you allow "Marketing" in the cookie banner (section 6.6). Our own page statistics run on our server, without cookies and without entries in your browser's storage (section 3.4). We store ad click IDs only with your consent (section 7).

3. Erhebung und Speicherung personenbezogener Daten

3.1 When you visit the website (without registering)

When you open our website, your browser sends our server your IP address, the address you opened, your browser's identifier (user agent) and, where present, the address of the referring page (referrer), because that is how the web works. We need the IP address to deliver the page to your device. We also count in the server's memory how many requests arrive from the same IP address within a short time, to limit abuse such as mass login attempts. We discard these counters after one hour at the latest. The IP address is not stored in the process.

For every request to the application's interface, our server writes a log line with the method, the path without the parameters from the address, the status code and the response time. The IP address, user agent and referrer are not in it. We use this log to find errors and outages.

Our own page statistics are covered in section 3.4, error logs in section 3.5.

Legal basis: Legitimate interest in providing the website securely and reliably (Art. 6 (1) (f) GDPR).

3.2 Bei Registrierung und Nutzung der Anwendung

Für die Registrierung und Nutzung von Kontavio erheben und verarbeiten wir:

Kontodaten:

  • E-Mail-Adresse (für Login, Passwort-Wiederherstellung und Benachrichtigungen)
  • Passwort (wird ausschließlich als bcrypt-Hash gespeichert — wir haben zu keinem Zeitpunkt Zugriff auf Ihr Klartext-Passwort)

Geschäftsdaten, die Sie eingeben:

  • Firmen-/Entity-Daten (Name, Adresse, Rechtsform, Steuer-ID, Bankverbindungen)
  • Kundendaten (Name, Firma, Adresse, Kontaktdaten, Steuer-ID)
  • Lieferantendaten (Name, Kategorie)
  • Rechnungsdaten (Positionen, Beträge, Währungen, Status)
  • Bankkontodaten (Kontobezeichnung, Bank, Währung)
  • Transaktionsdaten (Betrag, Datum, Beschreibung, Kategorie)

Diese Daten werden ausschließlich für die Bereitstellung der von Ihnen genutzten Funktionen verarbeitet und nicht für andere Zwecke verwendet.

Rechtsgrundlage: Vertragserfüllung (Art. 6 Abs. 1 lit. b DSGVO) — die Daten sind zur Erbringung des Dienstes erforderlich.

3.3 When you contact us

If you send us an email, we store your message and email address to handle the request and answer follow-up questions.

Through the contact form you send us your name, email address, a subject and your message. Our server does not put these details in the database. It sends them straight away through our email provider Resend (section 6.2) to our mailbox help@kontavio.com, with your address as the reply-to address. The mailbox is hosted by IONOS SE in Germany. Resend also sends a short confirmation of receipt to the address you entered, which repeats none of your details. To keep out automated submissions, the form contains a field people cannot see, and we limit the number of requests per IP address (section 3.1).

We delete requests sent by email or through the form once they are fully handled, at the latest after 6 months, unless retention obligations apply.

Legal basis: Legitimate interest in handling requests (Art. 6 (1) (f) GDPR) or pre-contractual measures (Art. 6 (1) (b) GDPR).

3.4 Our own page statistics (no cookies)

We count for ourselves which pages of our website people open, how visitors find us and where they leave. We set no cookie for this and put nothing in your browser's storage, neither localStorage nor session storage. No third party is involved, and the data stays on our server.

With every page view, your browser sends our server:

  • the page you opened, without the parameters in the address, and the page title,
  • on the first page view, the domain of the website you came from (for example google.com, without the rest of the address),
  • campaign parameters from the link (utm_source, utm_medium, utm_campaign, utm_content, utm_term) and, where present, a partner's referral code,
  • how you use the page: how far you scroll, which sections you see and which links and buttons you click,
  • for forms on the website (signup, waitlist, company setup): that you started a form and, if you leave it without submitting, the name of the last field you used (for example “Email”), never its content.

From your IP address and your browser's identifier (user agent) we compute a hash with a key. We create the key from random numbers for every day and delete it once the day is two days old. After that, not even we can recreate the hash from an IP address and user agent, and we cannot recognise the same visitor on two different days. We do not store the IP address or the user agent; from the user agent we only derive the device type, browser and operating system. Visits from search engine crawlers and other bots are not counted. In the app (except the onboarding right after signing up), the admin area, the partner portal, on the login page and on pages you open through a personal link (a shared timesheet, a review link, confirming your email address, resetting your password, taking over an account a partner set up for you, or setting up partner access) we count no page views, only single steps such as a successful login or email confirmation.

We combine the individual events into daily figures, without the hash: per page, per move from one page to the next (for this we link views with the same hash on the same day in their order) and per signup step. We normally delete the individual events after two days, at the latest after 90 days. Data on how a page is used (scroll depth, sections seen, clicks) is stored as daily counters per page from the start, without the hash. Everything is evaluated in aggregate only, never for individual visitors.

Inside the logged-in app we count, anonymously, where users get stuck: several quick clicks on the same spot, clicks on elements where nothing happens, switching back and forth between pages, help searches without a result, the same form error several times, and errors in the browser. We count per page of the app and per day, without any link to your account: we store no user ID and no hash for it, nor what you saw or typed in the process, and nothing is placed in your browser. We replace the page address with a pattern without identifiers (for example “/app/customers/id”). We delete the counters after 13 months. If this counting is tied to your consent to the “Analytics” category (section 7), we count only if you have agreed. We use the figures to improve the app and evaluate them in aggregate only. If you get stuck on the same spot in the app several times, your browser uses these in-memory counters to show a hint about the assistant and the help centre, and if you choose “No thanks” there, we save that on your account for seven days so the hint does not come straight back; how often the hint is shown and accepted is counted anonymously per page, as above.

When you sign up, the form sends along the page your visit started on, the domain of the referring website and the campaign parameters. Your browser keeps these only in memory while the page is open. With your account we store the channel derived from them (for example search engine, AI assistant, social network, newsletter, ad or direct visit), the source, the landing page and the campaign parameters. We do not store the hash with your account. A completed signup or email confirmation is counted as a step in the statistics, without any link to your account.

We also receive aggregated figures from Google through Google Search Console on the search terms for which our pages were shown and clicked in Google Search. These figures contain no information about individual people.

Legal basis: Our legitimate interest in understanding and improving our website, our app and our marketing (Art. 6 (1) (f) GDPR). You can object to this processing (section 10).

3.5 Error logs, problem reports and feature requests

Automatic error logs. If our server cannot answer a request or a program error occurs in the application, we store the error message, the page without parameters from the address bar, the application version, your browser's identifier (user agent) and, if you are signed in, the link to your account. We do not store the contents of forms or requests. We delete the link to your account after 14 days; what remains is a summary of the error without personal data. When an error occurs for the first time or a fixed error comes back, our team gets an email and a task in our self-hosted task management system (on a Hetzner server in Germany). Both contain only the error message and technical details, nothing about you.

Problem reports and feature requests. If you report a problem through "Report a problem" or ask for a feature through "Request a feature", we store your message, the link to your account (name, email address) and, unless you untick them, technical details (page, version, your browser's identifier (user agent), window size, and for problems the IDs of the latest errors). We only store a screenshot if you add one yourself. In the AI assistant you can also let the assistant write a report or request; only the text the assistant shows you first and you confirm is sent, without technical details and without the conversation. Section 6.3 applies to the processing in the AI assistant. The report reaches our team by email, with your email address as the reply-to address, and as a task in the task management system named above; your name and email address do not appear there. You get a confirmation of receipt by email. We delete reports, requests and screenshots after 6 months.

Legal basis: Legitimate interest in an application that works correctly and securely (Art. 6 (1) (f) GDPR); for problem reports and feature requests also the performance of the user agreement (Art. 6 (1) (b) GDPR).

3.6 Reviews

Asking for a review. At the earliest 14 days after you sign up, and only once you actually use Kontavio (for example after sending an invoice), we ask you for a review on the dashboard, at most three times and 30 days apart. For this we store how often and when we asked and whether you do not want to be asked again. If we ask you personally for a review, you get a link that is valid for 30 days; we store only a check value of that link.

Your review. When you submit a review, we store the stars, your text, the language, the name and the description of yourself you enter for publication, and whether you agreed to publication, with the time and the version of the consent text. Our team gets an email about every new or changed review.

Publication. Only if you agreed and we approve the review do we show it with the name and description you entered on our website (home page, pricing, partner page). We may shorten the name and translate the text into the other language; we do not change the content. Without your consent, only your stars count towards the average rating shown.

You can change or withdraw your review at any time through the menu at the top right; a withdrawn review is deleted. You can also withdraw your consent to publication there at any time.

Legal basis: For publication, your consent (Art. 6 (1) (a) GDPR); for asking and for storing the review, our legitimate interest in knowing how satisfied users are (Art. 6 (1) (f) GDPR).


4. Cookies und Session-Management

Cookies setzen wir nur, soweit sie technisch notwendig sind. Beim Login wird ein Session-Cookie gesetzt, das folgende Eigenschaften hat:

  • Enthält ausschließlich einen zufällig generierten Token (keine personenbezogenen Inhalte)
  • Ist als HTTP-only markiert (kein Zugriff durch JavaScript im Browser)
  • Ist als Secure markiert (wird nur über HTTPS übertragen)
  • Ist als SameSite=Strict markiert (wird bei Anfragen von fremden Websites nicht mitgeschickt)
  • Gilt höchstens ein Jahr
  • Wird bei Logout automatisch gelöscht

Den Token selbst speichern wir nirgends sonst in Ihrem Browser. Im localStorage merkt sich die App unter signed_in nur, dass auf diesem Gerät eine Anmeldung besteht. Der Eintrag enthält keine Zugangsdaten und wird bei der Abmeldung gelöscht. Für das Partner-Portal gilt dasselbe mit einem eigenen Cookie (partner_session, höchstens 30 Tage, Punkt 13.1).

Wir setzen keine Tracking-Cookies, Analyse-Cookies, Werbe-Cookies oder Cookies von Drittanbietern ein. Für optionale Einträge im Speicher Ihres Browsers fragen wir über das Cookie-Banner nach Ihrer Einwilligung (Punkt 7). Unsere eigene Seitenstatistik kommt ohne Cookies und ohne solche Einträge aus (Punkt 3.4).

Rechtsgrundlage: Technisch notwendige Cookies sind nach § 25 Abs. 2 TDDDG von der Einwilligungspflicht ausgenommen.

English translation of the changed parts:

We only set cookies where they are technically necessary. ... The session cookie is marked HTTP-only (no access by JavaScript in the browser), Secure (sent over HTTPS only) and SameSite=Strict (not sent with requests from other websites), and it lasts one year at most.

We store the token itself nowhere else in your browser. In localStorage, the app only notes under signed_in that this device is signed in. The entry contains no credentials and is deleted when you sign out. The partner portal works the same way with its own cookie (partner_session, 30 days at most, section 13.1).

We do not use tracking cookies, analytics cookies, advertising cookies or third-party cookies. For optional entries in your browser's storage, we ask for your consent through the cookie banner (section 7). Our own page statistics need neither cookies nor such entries (section 3.4).

Legal basis: Technically necessary cookies are exempt from the consent requirement under Section 25 (2) TDDDG.


5. Hosting und Infrastruktur

5.1 Hetzner Cloud

Our website and application are hosted by:

Hetzner Online GmbH Industriestr. 25 91710 Gunzenhausen Germany

The app and the database run on Hetzner servers in Germany (Falkenstein data centre, Saxony). For individual tasks we transfer data to providers in the USA: to Stripe for payments, to Resend for sending emails and, if you have switched on AI features, to Groq. Section 6 sets out which data that is and on what basis it is transferred.

Hetzner processes data on our behalf and is bound by contract as a processor under Art. 28 GDPR. Hetzner has access to the server infrastructure, but not to the application data itself, as this is stored encrypted in the database.

More information: Hetzner privacy policy

5.2 Datenbank

Alle Anwendungsdaten werden in einer PostgreSQL-Datenbank gespeichert, die ausschließlich auf unserem Hetzner-Server in Deutschland läuft. Die Datenbank:

  • Ist nicht über das öffentliche Internet erreichbar
  • Kommuniziert ausschließlich über localhost (127.0.0.1) mit der Anwendung
  • Ist durch Passwortauthentifizierung geschützt
  • Speichert sensible Daten (wie Passwörter) nur in gehashter Form

5.3 SSL/TLS-Verschlüsselung

Die gesamte Kommunikation zwischen Ihrem Browser und unserem Server ist durch TLS-Verschlüsselung (HTTPS) geschützt. Die SSL-Zertifikate werden automatisch über Let's Encrypt bereitgestellt und verwaltet. Eine unverschlüsselte Übertragung (HTTP) wird automatisch auf HTTPS umgeleitet.


6. Drittanbieter und Auftragsverarbeiter

6.1 Enable Banking (Open Banking / PSD2)

Wenn Sie die optionale Open-Banking-Funktion nutzen, um Ihre Bankkonten zu verbinden, werden Sie zur Autorisierung an Enable Banking weitergeleitet.

Enable Banking Oy Heimolankatu 4 33100 Tampere Finnland

Enable Banking ist ein von der finnischen Finanzaufsicht (FIN-FSA) zugelassener und PSD2-zertifizierter Kontoinformationsdienstleister (AISP). Bei der Nutzung gilt:

  • Der Zugriff erfolgt ausschließlich lesend (read-only) — es können keine Zahlungen oder Überweisungen ausgelöst werden
  • Wir erhalten ausschließlich Kontoinformationen (IBAN, Kontostand) und Transaktionsdaten (Buchungsdatum, Betrag, Verwendungszweck)
  • Der PSD2-Consent (Ihre Einwilligung) ist auf maximal 90 Tage begrenzt und muss dann aktiv erneuert werden
  • Nach Ablauf des Consents werden keine weiteren Daten abgerufen
  • Sie können den Consent jederzeit direkt bei Ihrer Bank oder über unsere App widerrufen

Rechtsgrundlage: Einwilligung (Art. 6 Abs. 1 lit. a DSGVO) — Sie erteilen die Einwilligung aktiv während des OAuth-Flows bei Ihrer Bank. Zusätzlich: Vertragserfüllung (Art. 6 Abs. 1 lit. b DSGVO).

6.2 Resend (sending emails)

Every email Kontavio sends goes through the Resend service.

Plus Five Five, Inc. (Resend) 2261 Market Street #5039 San Francisco, CA 94114, USA

Which emails go through Resend:

  • Account and security: confirming your email address when you sign up and after a change, a notice to the previous address after a change, password resets, a notice when an AI app gets access to your account, the waitlist confirmation and the invitation from the waitlist.
  • Deadlines: reminders of your LLC's deadlines, 60, 30, 7 and 1 day before.
  • Trial and subscription: welcome, notes during and at the end of the trial, purchase confirmation, tips on features in the first weeks after purchase, a reminder before a renewal and a notice when a payment fails. If your trial ends without a purchase, we write to you up to three times afterwards and once a year for the Form 5472 season. You can object to these emails at any time with a short reply.
  • What you send yourself: invoices to your customers, the LLC tax report and the Form 5472 PDF to an address you enter, timesheets for approval and the message that they were approved or rejected.
  • Form 5472 and partners: questionnaires, reminders and queries from your formation partner, handing your case to the filing service (section 13.5), invitations to an account a partner set up for you (section 13.3), and emails to partners (confirming the address, access to the partner portal, approval, password resets).
  • Contact and reports: messages from the contact form to us and the confirmation to you (section 3.3), confirmations of receipt for problem reports and feature requests (section 3.5).
  • Internal notifications to our team (section 13.6).

Resend receives the recipient's email address and, where given, name, the sender, subject and content of the email including attachments (for example an invoice as a PDF). Resend processes this data on our behalf to deliver the emails.

Transfer to a third country: Resend is based in the USA. Plus Five Five, Inc. is certified under the EU-U.S. Data Privacy Framework (checked on 11 November 2026 at dataprivacyframework.gov). The transfer is therefore based on the European Commission's adequacy decision (Art. 45 GDPR). In addition, Resend's data processing agreement, which is part of its terms of service, incorporates the European Commission's standard contractual clauses (Art. 46 (2) (c) GDPR).

Legal basis: For emails about your account, deadlines and subscription and for emails you trigger yourself, the performance of the user agreement (Art. 6 (1) (b) GDPR). For the emails after a trial without purchase, replies to contact requests and internal notifications, our legitimate interest in staying in touch with users and prospects and in running the service reliably (Art. 6 (1) (f) GDPR).

Note: You can also download invoices as a PDF and send them yourself.

6.3 Groq (AI features)

We use the Groq API for our AI features. These features require your explicit consent and are switched off by default.

Groq, Inc. Mountain View, CA, USA

When data is sent to Groq: Only if you have agreed to AI processing in the settings under "Privacy & AI" and use one of the features below. Without your consent no data is sent to Groq.

What each feature sends:

  • Importing bank statements (PDF, CSV): for CSV files the first lines, for PDFs the text of the statement, so that columns, transactions, balance and period can be recognised. This contains booking date, amount, currency, payment reference and the names of payees and payers. We replace IBANs with a placeholder before sending.
  • Category suggestions: description, amount and currency of the transaction, a few recently categorised transaction texts and the names of your customers (without their email address), so a payment can be matched to the right customer.
  • AI assistant: your messages, the conversation so far and the page of the app you are on (page name, page title, active company). The AI assistant also fetches the data from your account it needs for its answer (for example invoices, customers, transactions, deadlines, tax filings or document names) and passes it to Groq. Access keys such as share links are removed first. If you open the assistant through the “Looking for something?” hint, the labels of the last buttons you clicked are included with the page details.
  • Reading formation documents (onboarding): Only if our own analysis on the server cannot find an important field does the text of the document go to Groq, or for scanned documents images of the first pages. Such documents contain, for example, the company name, address, EIN, formation date and the names of the members or the registered agent.

Storage at Groq: By default Groq does not store requests. For troubleshooting or when abuse is suspected, Groq may log inputs and outputs for up to 30 days. Groq may not use the data to train AI models. Data is transferred encrypted over HTTPS.

Transfer to a third country: Groq is based in the USA and processes data in the USA and other countries where Groq or its subprocessors operate. Groq is not certified under the EU-U.S. Data Privacy Framework. The transfer is based on the European Commission's Standard Contractual Clauses (Art. 46 (2) (c) GDPR), which Groq's data processing addendum treats as agreed together with its terms of service.

Legal basis: Consent (Art. 6 (1) (a) GDPR). You can withdraw your consent at any time in the settings under "Privacy & AI". Withdrawal does not affect the lawfulness of processing before it. Without active consent, manual column mapping for imports and filling in the onboarding by hand remain available.

6.4 Stripe (Zahlungsabwicklung)

Für die Abwicklung von Abonnement-Zahlungen nutzen wir Stripe.

Stripe, Inc. San Francisco, CA, USA

Bei der Buchung eines kostenpflichtigen Plans werden Sie auf die Checkout-Seite von Stripe weitergeleitet. Dabei werden folgende Daten an Stripe übermittelt:

  • E-Mail-Adresse (zur Zuordnung des Kunden)
  • Gewählter Tarif und Preis

Stripe erhebt und verarbeitet zusätzlich:

  • Zahlungsdaten (Kreditkarte, SEPA, etc.) — diese werden ausschließlich bei Stripe gespeichert und sind für uns nicht einsehbar
  • Rechnungsadresse (falls von Stripe erhoben)
  • IP-Adresse und Geräteinformationen (zur Betrugsprävention)

Wir speichern lediglich die Stripe-Kunden-ID und Abonnement-ID, um den Zahlungsstatus zu verwalten. Zahlungsdaten (Kreditkartennummern etc.) werden zu keinem Zeitpunkt auf unseren Servern gespeichert.

Da Stripe seinen Sitz in den USA hat, liegt ein Drittlandtransfer vor. Stripe nutzt angemessene Schutzmaßnahmen gemäß Art. 46 DSGVO (Standardvertragsklauseln) und ist unter dem EU-U.S. Data Privacy Framework zertifiziert.

Weitere Informationen: Stripe Datenschutz

Rechtsgrundlage: Vertragserfüllung (Art. 6 Abs. 1 lit. b DSGVO) — die Zahlungsabwicklung ist zur Erbringung des kostenpflichtigen Dienstes erforderlich.

6.5 Direct connections to Wise, Mercury, Airwallex and Interactive Brokers

Besides open banking (section 6.1), you can connect accounts directly through your provider's interface. You create your own access key with your provider and enter it in Kontavio:

  • Wise (api.wise.com): profiles, balances and statements of your Wise accounts with the transactions (date, amount, currency, payment reference, counterparty).
  • Mercury (api.mercury.com): accounts with balance and transactions.
  • Airwallex (api.airwallex.com): account details, balances and transactions.
  • Interactive Brokers (Flex Web Service): a statement with positions, cash balances and the value of your portfolio, which you set up there as a Flex Query.

We fetch this data read-only when you start a sync and then automatically at regular intervals while the connection is active. We only send your access key and the query (for example the period) to the provider; the data itself is already held by your provider, with whom you have your own contract and whose privacy policy applies to it. With us, the fetched data is stored on our servers in Germany (section 5). We store the access key encrypted. If you disconnect, we stop fetching data. For Interactive Brokers we delete the key at that point; for Wise, Mercury and Airwallex it stays stored encrypted until you delete your account.

Legal basis: Performance of the contract (Art. 6 (1) (b) GDPR): you use the feature to see your accounts in Kontavio.

If you allow the "Marketing" category in the cookie banner, we use Meta's pixel and Conversions API. They tell us whether our ads on Facebook and Instagram lead to visits, signups and paying customers, and Meta uses this to decide where to show our ads. Without this consent your browser does not load the pixel and we send nothing to Meta.

Meta Platforms Ireland Ltd. Merrion Road, Dublin 4, D04 X2K5, Ireland

In the browser (Meta pixel): On the public pages of our website, not in the app, the partner portal or on shared links, your browser loads a script from Meta. It sets the cookies _fbp (an identifier of your browser) and, if you arrive through a Meta ad, _fbc (the ad's click ID), both for 90 days. It reports page views, visits to the pricing and feature pages and your signup to Meta. Meta receives your IP address, details about your browser and the address you opened.

From our server (Conversions API): If you allowed "Marketing" at signup or later in the app, we report your signup, the completion of onboarding and the first payment of a subscription (amount and currency) to Meta. For this we send your email address and your account ID only as a hash (SHA-256), the values of _fbp and _fbc and details about your browser, and at signup also your IP address. Meta receives nothing from your bookkeeping, your companies or your documents. For later reports we store _fbp, _fbc and the browser details with your account, but not your IP address.

We and Meta are joint controllers for collecting the data on our website and transmitting it to Meta (Art. 26 GDPR). The agreement for this is Meta's Controller Addendum. Meta alone is responsible for any further processing. Meta may transfer data to Meta Platforms, Inc. in the USA; Meta is certified under the EU-U.S. Data Privacy Framework. You can exercise your rights under section 10 with us and with Meta.

More information: Meta's privacy policy

Legal basis: Your consent (Section 25 (1) TDDDG, Art. 6 (1) (a) GDPR). You can withdraw it at any time through "Cookie settings". The pixel then no longer loads, we delete _fbp and _fbc from your browser and send no further reports. If you withdraw while signed in to the app, we also delete the values stored with your account.


On your first visit to our website we show a cookie banner. There you decide which optional entries we may store in your browser. Until you have decided, we store none of them, and no optional category is preselected in the banner's settings. Your choice is kept as cookie_consent in your browser's localStorage.

These entries exist (name, where it is stored, purpose, duration). The only recipient is Kontavio, except for the Meta pixel (section 6.6):

Essential (always active):

  • session (cookie, HTTP-only) and signed_in (localStorage): keep you signed in to the app. Only the cookie holds the sign-in key; signed_in just notes that you are signed in. Until you sign out; the cookie for one year at most.
  • partner_session (cookie, HTTP-only): keeps partners signed in to the partner portal. Until sign-out, 30 days at most.
  • cookie_consent (localStorage): your choice in the cookie banner. Until you change it or clear the site data in your browser.
  • content_checksum_content and content_collection_content (localStorage): a cache of our website's public texts (blog, help, legal pages) that your browser creates when you move to such a page within the website. It contains nothing about you. Until we change the content or you clear the site data.
  • Settings you make yourself, in localStorage until you clear the site data: a closed promotion banner (promo-banner-dismissed-…), the plan you picked on the pricing page until after signup (kontavio_signup_plan) and, in the app, the layout of the AI assistant (assistant_layout), closed hints (tier_hint_…, discovery_dismissed_…, kontavio_partner_welcome_seen), counters that decide when we show a plan hint (invoice_count_…, manual_import_count), and a marker for an open payment in the filing service (tf-awaiting:…).
  • In session storage, until you close the tab: closed trial hints (trialBannerDismissed, trial_downgrade_preview_dismissed_…) and the time of a loading error (kv-chunk-error-at), so the page reloads only once after an update.

Functional (optional):

  • kontavio_ref (session storage): If you arrive through a partner's referral link, we store their referral code so it is kept until registration and prefilled in the signup form (section 13.2). Until you close the tab.

Analytics (optional): This category stores nothing and switches nothing on at the moment. Our own page statistics need no consent because they store nothing in your browser (section 3.4). If we ever use something here, we will update this policy first.

Marketing (optional):

  • kontavio_attribution (localStorage): first-touch attribution. If you arrive through an ad or an external link, we store campaign parameters, ad click IDs (fbclid, gclid), the domain of the referring website and the landing page. If you register, we store these details with your account to see which channel brings new users. Of these, only the click ID fbclid goes to Meta, as part of the Conversions API (section 6.6). Until you withdraw your consent or clear the site data.
  • _fbp and _fbc (Meta cookies): the Meta pixel, with an identifier of your browser and the click ID of a Meta ad (section 6.6). 90 days.

You do not control AI features (Groq, section 6.3) through the cookie banner but in the settings under "Privacy & AI".

You can change your choice at any time using the "Cookie settings" link in the website footer (on the signup page, below the form). Withdrawal takes effect immediately: we delete the entries of the categories you deselect from your browser and stop reading them. The referral code from the link you just arrived through is still used for the page statistics and shown in the signup form, without being stored (section 13.2).

Legal basis: Consent (Section 25 (1) TDDDG, Art. 6 (1) (a) GDPR) for the optional categories; Section 25 (2) TDDDG and legitimate interest (Art. 6 (1) (f) GDPR) for essential entries. Evaluating registration data by channel is based on our legitimate interest in measuring our marketing (Art. 6 (1) (f) GDPR).


8. Datenweitergabe an Dritte

Eine Weitergabe Ihrer personenbezogenen Daten an Dritte erfolgt nur:

  • An die unter Punkt 6 genannten Auftragsverarbeiter, soweit dies zur Leistungserbringung erforderlich ist
  • Wenn Sie ausdrücklich eingewilligt haben
  • Wenn wir gesetzlich dazu verpflichtet sind (z. B. auf Anordnung einer Behörde oder eines Gerichts)
  • In den unter Punkt 13 beschriebenen Fällen: an Zahlungsdienste für Partner-Auszahlungen sowie, wenn Sie den Form-5472-Fragebogen abschicken, an Ihren Gründungspartner oder an den Empfänger, den Sie wählen
  • An Meta zu Werbezwecken, nur wenn Sie im Cookie-Banner „Marketing“ erlauben (Punkt 6.6)

Eine darüber hinausgehende Weitergabe findet nicht statt. Zu Werbezwecken geben wir Daten nur mit Ihrer Einwilligung an Meta weiter (Punkt 6.6).

English translation of the changed parts:

  • In the cases described in section 13: to payment services for partner payouts and, when you submit the Form 5472 questionnaire, to your formation partner or to the recipient you choose
  • To Meta, for advertising purposes, only if you allow "Marketing" in the cookie banner (section 6.6)

9. Speicherdauer und Löschung

Wir speichern personenbezogene Daten nur so lange, wie es für den jeweiligen Verarbeitungszweck erforderlich ist:

DatenartSpeicherdauer
Zähler gegen Missbrauch mit IP-Adresse (Punkt 3.1)Höchstens 1 Stunde, nur im Arbeitsspeicher
Einzelereignisse der Seitenstatistik (Punkt 3.4)In der Regel 2 Tage, spätestens 90 Tage; danach nur zusammengefasste Tageszahlen ohne Hashwert
Tagesschlüssel für den Hashwert der Seitenstatistik (Punkt 3.4)Bis der Tag zwei Tage zurückliegt
Fehlerprotokolle mit Bezug zu Ihrem Konto (Punkt 3.5)14 Tage
Problemmeldungen, Funktionswünsche und Screenshots (Punkt 3.5)6 Monate
Bewertungen (Punkt 3.6)Bis Sie sie zurückziehen oder Ihr Konto löschen
Session-CookiesBis zum Logout oder Ablauf
Kontodaten (E-Mail, Passwort-Hash)Bis zur Kontolöschung
Geschäftsdaten (Rechnungen, Kunden, Transaktionen)Bis zur Kontolöschung, mindestens jedoch gemäß gesetzlicher Aufbewahrungsfristen
Kontaktanfragen per E-Mail und Kontaktformular (Punkt 3.3)Bis zur vollständigen Bearbeitung, max. 6 Monate
Open-Banking-DatenSolange der PSD2-Consent aktiv ist; synchronisierte Transaktionen bleiben als Ihre Geschäftsdaten gespeichert
Zugangsschlüssel für Wise, Mercury und Airwallex (Punkt 6.5)Verschlüsselt bis zur Kontolöschung; abgerufene Buchungen bleiben als Ihre Geschäftsdaten gespeichert
Zugangsschlüssel für Interactive Brokers (Punkt 6.5)Bis Sie die Verbindung trennen oder Ihr Konto löschen
Meta-Kennungen und Browserangaben für die Conversions API (Punkt 6.6)Bis Sie die Einwilligung widerrufen oder Ihr Konto löschen

Nach Löschung Ihres Kontos werden alle personenbezogenen Daten innerhalb von 30 Tagen unwiderruflich gelöscht, sofern keine gesetzlichen Aufbewahrungspflichten (z. B. handels- oder steuerrechtliche) einer früheren Löschung entgegenstehen.

English translation of the changed parts:

Type of dataStorage period
Abuse counters with the IP address (section 3.1)One hour at most, in memory only
Individual events of the page statistics (section 3.4)Normally 2 days, at the latest 90 days; then only aggregated daily figures without the hash
Daily key for the page statistics hash (section 3.4)Until the day is two days old
Error logs linked to your account (section 3.5)14 days
Problem reports, feature requests and screenshots (section 3.5)6 months
Reviews (section 3.6)Until you withdraw them or delete your account
Access keys for Wise, Mercury and Airwallex (section 6.5)Encrypted until you delete your account; fetched transactions stay stored as your business data
Access key for Interactive Brokers (section 6.5)Until you disconnect or delete your account
Meta identifiers and browser details for the Conversions API (section 6.6)Until you withdraw your consent or delete your account
Contact requests by email and contact form (section 3.3)Until fully handled, at most 6 months

10. Ihre Rechte

Sie haben folgende Rechte in Bezug auf Ihre personenbezogenen Daten:

  • Auskunftsrecht (Art. 15 DSGVO): Sie können jederzeit Auskunft über die bei uns gespeicherten personenbezogenen Daten verlangen, einschließlich der Verarbeitungszwecke und Empfänger.
  • Recht auf Berichtigung (Art. 16 DSGVO): Sie können die Berichtigung unrichtiger oder die Vervollständigung unvollständiger Daten verlangen. Viele Daten können Sie direkt in der App selbst korrigieren.
  • Recht auf Löschung (Art. 17 DSGVO): Sie können die Löschung Ihrer Daten verlangen, sofern keine gesetzlichen Aufbewahrungspflichten entgegenstehen. Sie können Ihr Konto jederzeit selbst löschen.
  • Recht auf Einschränkung der Verarbeitung (Art. 18 DSGVO): Sie können unter bestimmten Voraussetzungen die Einschränkung der Verarbeitung Ihrer Daten verlangen.
  • Recht auf Datenübertragbarkeit (Art. 20 DSGVO): Sie können verlangen, dass wir Ihnen Ihre Daten in einem strukturierten, gängigen und maschinenlesbaren Format (z. B. CSV, JSON) zur Verfügung stellen. Unsere Export-Funktionen (CSV-Export für Reports und Transaktionen) unterstützen dies.
  • Widerspruchsrecht (Art. 21 DSGVO): Sie können der Verarbeitung Ihrer Daten aus Gründen, die sich aus Ihrer besonderen Situation ergeben, jederzeit widersprechen, sofern die Verarbeitung auf einem berechtigten Interesse beruht.
  • Recht auf Widerruf der Einwilligung: Soweit die Verarbeitung auf Ihrer Einwilligung beruht (z. B. Open Banking), können Sie diese jederzeit mit Wirkung für die Zukunft widerrufen.

Zur Ausübung Ihrer Rechte wenden Sie sich bitte an: help@kontavio.com

Wir bearbeiten Ihre Anfrage unverzüglich, spätestens innerhalb von 30 Tagen (Art. 12 Abs. 3 DSGVO).


11. Beschwerderecht bei einer Aufsichtsbehörde

Wenn Sie der Ansicht sind, dass die Verarbeitung Ihrer personenbezogenen Daten gegen geltendes Datenschutzrecht verstößt, haben Sie das Recht, sich bei einer zuständigen Datenschutz-Aufsichtsbehörde zu beschweren. Sie können sich dabei an die Aufsichtsbehörde Ihres Wohnsitzes, Ihres Arbeitsplatzes oder des Ortes des mutmaßlichen Verstoßes wenden.


12. Sicherheitsmaßnahmen

Wir setzen umfangreiche technische und organisatorische Maßnahmen zum Schutz Ihrer Daten ein:

  • Verschlüsselung: Alle Datenübertragungen sind TLS-verschlüsselt (HTTPS)
  • Passwort-Hashing: Passwörter werden mit bcrypt gehasht — eine Rückrechnung ist nicht möglich
  • Session-Sicherheit: Die Anmeldung steckt in einem HTTP-only-, Secure- und SameSite-Cookie, das Skripte im Browser nicht auslesen können. Schreibende Anfragen nimmt die App nur von ihrer eigenen Adresse an
  • Content-Security-Policy: Der Browser lädt auf unseren Seiten keine Skripte von fremden Servern nach und sendet Daten nur an unseren eigenen Server
  • Netzwerksicherheit: Die Datenbank ist nicht öffentlich zugänglich
  • Standort: App und Datenbank laufen auf Servern in Deutschland; Übermittlungen in die USA stehen in Punkt 6
  • Zugriffskontrolle: Strenge Trennung der Daten zwischen verschiedenen Nutzern und Entities

English translation of the changed parts:

  • Location: The app and the database run on servers in Germany; transfers to the USA are listed in section 6
  • Session security: Your sign-in sits in an HTTP-only, Secure and SameSite cookie that scripts in the browser cannot read. The app accepts write requests only from its own address
  • Content Security Policy: On our pages, the browser loads no scripts from other servers and sends data only to our own server

13. Partner program, referrals and Form 5472

13.1 Data of our partners

If you take part in our partner program (see Partner Program Terms), we process:

  • Account and program data: name, email address, language, description of your channels, partner type, status, referral code, agreed conditions, login times and failed login attempts. We store your password only as a bcrypt hash. If you also have a Kontavio account under the same confirmed email address, we link the two automatically. You then log in with your Kontavio account.
  • Settlement data: commission entries with amount, currency, rate and status, payouts, self-billed invoices.
  • Tax and payout data: tax number, VAT ID, payout method and the related details (for example IBAN or PayPal address).
  • W-8BEN self-certification: full name, citizenship, permanent residence address, foreign tax ID, date of birth, your confirmation with typed name and time.
  • Questionnaires for your clients: your questionnaire template in every saved version (which standard questions you hide or reword, which questions of your own you add) as well as due dates, personal messages, reminders, follow-up questions and status changes for the questionnaires you send to your clients.

For the partner portal we set a separate, technically necessary session cookie (partner_session) with the same properties as described in section 4.

Purposes: reviewing your application, running the partner portal, calculating and paying out commissions, issuing self-billed invoices, documenting to US tax authorities that no withholding tax was due.

Legal basis: performance of the contract and pre-contractual measures (Art. 6 (1) (b) GDPR). For retention and documentation obligations under EU or member state law, Art. 6 (1) (c) GDPR. For documentation under US tax law, our legitimate interest in complying with these rules (Art. 6 (1) (f) GDPR).

Recipients: For payouts we transmit name, amount, payment reference and your bank details or PayPal address to the payment service used for the payout (currently Wise or PayPal). These services process the data as independent controllers. We send emails to partners via Resend (section 6.2). Tax authorities receive data only where we are legally required to provide it.

Retention: Account and program data for as long as the partnership exists and afterwards for as long as commissions still accrue or are being settled. If you delete your linked Kontavio account, the partner record with the commission history remains until settlement is complete. We keep settlement, self-billing and payout data and the W-8BEN details until the statutory commercial and tax retention periods have expired, at most ten years after the end of the calendar year of the last payout.

13.2 Attribution of referrals

If you come to Kontavio through a partner, we attribute your account to that partner so they receive a commission. There are two ways this happens.

Referral code (no browser storage): If you open a referral link, the partner's code appears visibly in the registration form. You can delete it there or enter a code yourself. If you register with a code, we store the attribution to this partner with the date and type of attribution and, where applicable, a benefit linked to the code (for example a discount or a longer trial).

Browser storage (only with consent): If you have accepted the "Functional" category in the cookie banner, we store the code from the link in your browser's session storage (kontavio_ref) so it is kept on the way to registration. The entry disappears when you close the tab.

Visits through the link: Our page statistics (section 3.4) also record the referral code from the link on page views, without storing anything in your browser. From this, the partner only sees the number of visitors, no individual data.

What the partner sees: the date of your registration, your plan, the status of your subscription and the commission amounts. The partner does not see names, email addresses or the content of your account. If a partner referred you personally, they may be able to infer from this which plan you use.

Legal basis: For attribution and commission settlement, our legitimate interest in a working partner program (Art. 6 (1) (f) GDPR); for a benefit linked to the code, performance of the contract (Art. 6 (1) (b) GDPR). For counting visits through the link, likewise our legitimate interest (Art. 6 (1) (f) GDPR). For browser storage, your consent (Section 25 (1) TDDDG, Art. 6 (1) (a) GDPR), which you can withdraw at any time in the cookie settings.

Retention: We store the attribution for as long as your account exists and afterwards for as long as commissions from it are being settled or retention periods apply.

13.3 Accounts a partner set up for you (information under Art. 14 GDPR)

Some partners, for example the agency that formed your LLC, prepare a Kontavio account for their clients. In that case we did not receive your data from you but from this partner.

Which data: your name, email address and language, and your LLC's company data (name, state, formation date, EIN, business and mailing address, owner and ownership percentage, registered agent and renewal date). Optionally, the partner uploads up to four documents: Articles of Organization, EIN confirmation, Operating Agreement and ITIN letter.

Source: the partner named in the invitation. The data does not come from publicly accessible sources.

Purposes: We prepare an account you can take over, invite you by email, remind you once and attribute the account to the partner for their commission (section 13.2).

Legal basis: Until takeover, our legitimate interest in providing you with the account your partner set up for you (Art. 6 (1) (f) GDPR). When creating the account, the partner confirmed to us that there is a client relationship and that you agree to the setup. We protect your interests as follows: nobody can log into the account before you take it over, not even the partner. We do not send you any marketing. You can decline with one click, and we delete accounts that are not taken over after 90 days. Once you take over the account, we process the data to perform the user agreement with you (Art. 6 (1) (b) GDPR).

Who is responsible for what: The partner is responsible for transmitting the data to us. From receipt onwards, we are the controller for processing at Kontavio. We are not the partner's processor. Please address questions about the transmission to the partner and questions about processing at Kontavio to help@kontavio.com.

What the partner sees afterwards: Until takeover, the details they entered and the names of the files they uploaded. After takeover, only the status "Active". They do not see bookkeeping, invoices, account transactions or documents. The exception is the Form 5472 questionnaire for the LLC they set up: section 13.5 describes what they see there.

Retention: If you decline or the partner withdraws the invitation, we delete the prepared account with all transmitted data and documents immediately. If you do not accept the invitation, we remind you after 14 days and delete everything after 90 days. After takeover, section 9 applies.

Objection: You can object to the processing before takeover at any time (Art. 21 GDPR). The easiest way is "Decline account and delete data" in the invitation.

13.4 Reading formation documents for partners

Partners can upload formation documents so that Kontavio reads the company data from them before an account is created. In this step we act on behalf of the partner (Art. 28 GDPR). We return the values to the partner and store nothing permanently in the process. If the partner chooses to have scans read by AI, we transmit the documents to Groq for this purpose (section 6.3). The partner makes this decision for their clients, because at this point the clients do not yet have an account and therefore no AI setting of their own. If the partner then creates an account, section 13.3 applies.

13.5 Form 5472: questionnaire and who receives your information

In the Form 5472 questionnaire you put together the information a tax consultant needs to complete Form 5472 and the pro forma 1120, including company data, EIN, details about the owner and about transactions between you and your LLC. A PDF can be created from it. Who receives your information depends on who files:

  • LLC set up by a partner: For the LLC your partner set up for you, that partner receives your information. They can send you their questionnaire through Kontavio for this, with a due date and possibly a personal message. Their questionnaire is based on our standard questionnaire. The partner can hide or reword questions and add questions of their own. In detail:
    • While you fill it in, the partner sees the status (sent, in progress, submitted) and how many questions per section are answered, but no answers.
    • Once you have submitted, they see your answers in the partner portal, including the values Kontavio pre-filled from your profile and bookkeeping, each with a note on where the value comes from. They can export the answers as a PDF.
    • Follow-up questions: The partner can ask follow-up questions about individual answers. You answer them in Kontavio and can change the answer concerned. We store who changed an answer and when. The partner sees the previous and the new answer.
    • Status and reminders: The partner can set the status, for example "for signature" or "filed", and send you reminders in their own words. These emails contain a link, but no answers.
    • Limits: The partner cannot change your answers. Their access ends when the connection to them ends, for example because they leave the partner program. None of this applies to other companies in your account.
    • Responsibility: The partner processes what they view or export in the partner portal as an independent controller, to prepare the filing for you. They are responsible for the content of the questions they add themselves.
  • Your own tax agent: You download the PDF or have us send it to an email address you enter yourself.
  • Request to Kontavio: If you request our filing service, your case with the PDF and your contact details goes to a mailbox of the Kontavio team and to the tax consultant we engage for the filing service. The tax consultant uses it to complete Form 5472 and the pro forma 1120, handles your case on our behalf and is bound to confidentiality.

Legal basis: Your information is passed on because you submit the questionnaire or choose the route, and serves the performance of the contract with you or pre-contractual measures at your request (Art. 6 (1) (b) GDPR). The same applies to follow-up questions, the change history, the status and reminders. For the LLC set up by a partner, the route to the partner is fixed. The questionnaire points this out at the top. That the partner sees status and progress before you submit is based on our legitimate interest and that of your partner in meeting the due date together (Art. 6 (1) (f) GDPR). They see no content in doing so. You can object to this at any time (Art. 21 GDPR), for example by email to help@kontavio.com.

Sending and storage: We send the emails via Resend (section 6.2). To avoid sending a PDF twice, we store a check value for each delivery, but no recipient address. For every questionnaire your partner sends you, we store the version of their questions, so that it remains clear what you answered. Your answers, follow-up questions and the change history are part of your business data and are stored in accordance with section 9.

13.6 Internal notifications to our team

For operations we send ourselves email alerts, for example when a Form 5472 case could not be delivered, a payment does not match a case, or AI costs reach a budget. These emails contain only a case number and a link to our admin area, no names, EIN, PDFs or amounts. Messages from the contact form go to help@kontavio.com.

Legal basis: our legitimate interest in reliable operations (Art. 6 (1) (f) GDPR).


14. Änderungen dieser Datenschutzerklärung

Wir behalten uns vor, diese Datenschutzerklärung bei Bedarf anzupassen, um sie an geänderte Rechtslage, neue Funktionen oder geänderte Datenverarbeitungen anzupassen. Die jeweils aktuelle Fassung ist stets auf dieser Seite abrufbar. Bei wesentlichen Änderungen, die Ihre Rechte betreffen, werden registrierte Nutzer per E-Mail informiert.

Stand: 17. November 2026