This is a legally binding German disclosure. English version provided for convenience; the German text prevails.
Privacy policy
As of 14 October 2026
1. Controller: Consensus Ventures GmbH, Maxstraße 11, 82335 Berg, Germany, datenschutz@consensus.ventures.
2. Account data: Email address, name, company/role, language, password hash, records of consent (time, text version, IP). Legal basis: Art. 6(1)(b) GDPR (contract) or Art. 6(1)(a) GDPR (consent).
3. Interest profile: Your description of what interests you and what does not, and the categories and weights derived from it. We use the profile (a) to filter your own mail (Art. 6(1)(b) GDPR) and (b) only with your separate consent (Art. 6(1)(a), Art. 7 GDPR) to deliver matching paid offers to you. You can view, change and delete the profile at any time under “My interests”. Special categories of data (Art. 9 GDPR) are discarded during analysis.
4. Objection (Art. 21 GDPR): You can object at any time, without giving reasons, to the use of your profile for delivering offers: with the switch in the settings or by email.
5. Gmail access: Consent+ uses a single Gmail permission (“read, compose and send Gmail, manage labels”) solely for features you see and use yourself: sorting incoming mail, setting labels, archiving unsuitable offers (only if you allowed it), marking mail as read, archiving it or moving it to the trash on your instruction, replying briefly to senders in your name (only if you allowed it) and placing offers submitted via Consent+ directly in your inbox. We store sender, subject, date and up to 20,000 characters of text per email for display and sorting. Access tokens are stored encrypted. You can revoke access at any time in the settings or at myaccount.google.com/permissions.
5a. Limits of use (Google “Limited Use”): Gmail data is not sold, not used for advertising and not used to train general AI models, neither by us nor by our service providers. We technically route requests to language models only to providers that neither store inputs nor use them for training. People at Consent+ do not read your email; exceptions only with your explicit consent for a specific email, to investigate abuse or security incidents, or where required by law. Gmail data is only shared with the service providers listed in section 7, and only as far as needed for the features described.
5a. Anteroom (“Vorzimmer”, optional, with your consent): If the anteroom is switched on, Consent+ reads every email that is not filtered out or filed automatically with the language model (section 7) and stores a “case” for it: a one-sentence summary, a suggestion with a short reason, a deadline if any, and your decision. Summary, suggestion and reason are deleted 30 days after the case is closed. You can switch off or pause the anteroom in the settings at any time. Legal basis: Art. 6(1)(a) GDPR (consent); for your contacts’ data Art. 6(1)(f) GDPR (handling their messages).
5b. Reply drafts (anteroom, optional): When the anteroom prepares a reply, you tap “Draft reply” or switch on an automation for a category, Consent+ creates a reply draft. For this, the email, its thread, up to five earlier emails with the same contact and your notebook are sent to the language model (section 7), only for that one draft, without being stored. The draft is saved as a draft in your Gmail. Only if you switch on “Learn style from my sent emails” does Consent+ read up to 30 of your sent emails to start with, then your new sent emails daily as well as your changes to prepared drafts, and store nothing but a short style profile (salutation, tone, length, sign-off, preferences), no content; the emails are only processed temporarily for this. Switching it off deletes the profile. Emails are only sent automatically under your rule per category, with 10 minutes to stop them and a note in the email that it was prepared. Legal basis: Art. 6(1)(b) GDPR (feature you requested); for your contacts’ data Art. 6(1)(f) GDPR (replying to their messages).
5c. Your own AI agents (optional): Under “Connect AI agents” you can give your own assistant (e.g. Claude) an access key with permissions you choose. This agent receives content from your emails only on your explicit instruction; you or that agent’s provider are responsible for the processing by the agent. Every action is logged, and you can revoke keys at any time. Senders’ agents only use the invitation link from the reply and, like people, only learn a rough fit (traffic light), never your profile. If they pay via x402 (stablecoin), we store wallet address, amount and transaction ID as a record (§ 147 AO, German Fiscal Code).
Google API Services: Limited Use disclosure. Consent+’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. Gmail, Google Calendar, Google Tasks, Google Contacts and Google Drive data is used only to provide the user-facing features described above (sorting, labelling, archiving, replying on the user’s instruction, placing submitted offers in the inbox, finding free times, holding and adding calendar events and sending invitations only after the user’s approval, managing tasks and finding contacts on the user’s instruction, and reading only those Drive files and folders the user explicitly selects for a project notebook, to answer questions, draft replies and attach documents on the user’s instruction, and, only for standing orders the user sets up, saving invoice PDFs from the user’s email into folders Consent+ creates in the user’s own Drive and, if the user connects an accounting service, uploading those invoices to that service). It is never sold, never used for advertising and never used to train generalized AI or machine-learning models. Requests to language models are routed only to providers that neither retain nor train on the data. Humans do not read user email, except with the user’s explicit consent for specific messages, for security or abuse investigations, or where required by law.
5f. Calendar, tasks and contacts (optional): If you connect your Google Calendar, Google Tasks and Google Contacts under “Appointments & tasks”, Consent+ uses the permissions “see and edit events on all your calendars”, “create, edit and delete your tasks” and “see your contacts and other contacts” solely for features you see and use yourself: finding free times for proposed meetings (across all connected accounts), entering offered times as private holds and removing them again, entering agreed appointments and, only after your approval, inviting the other party, showing you appointments and tasks in the anteroom, creating or completing tasks on your instruction and finding people when you say e.g. “Write to Anna …”. Calendar entries, tasks and contacts are only read for the respective feature and not stored. We only store the meeting negotiations Consent+ conducts itself (counterpart, subject, offered and agreed times) and your instructions with their result. Instructions are deleted after 30 days, details of the counterpart in completed negotiations after 90 days. People looking for a meeting with you only see the proposed times, never your calendar. To understand replies to meeting proposals and your instructions, the email or instruction is sent to the language model (section 7), which does not store it. You can revoke access at any time at myaccount.google.com/permissions. Legal basis: Art. 6(1)(b) GDPR (feature you requested); for your contacts’ data Art. 6(1)(f) GDPR (arranging meetings with them).
5d. Waiting list and invitations (access by invitation): If you join the waiting list, we store your email address, language, origin (e.g. invitation page) and, if applicable, who recommended you, only to tell you once that your place is available. If you sign in with Google without an invitation, we only create an account with name and address; access to your Gmail is only stored once you have been admitted. You share invitation links yourself. Consent+ does not write to anyone in your name. For redeemed invitations we store who invited whom (for the Pro credit to both). Legal basis: Art. 6(1)(b) GDPR. You can unsubscribe at any time by replying to our email or at datenschutz@consent.plus; deleting your account removes the entry.
5g. Project notebooks and selected Drive documents (optional): If you create a project notebook (a case, project or mandate), Consent+ stores for it: name, goal, status, people involved (addresses, names, roles), keywords, your notes, references to related emails, appointments and tasks, and short facts extracted from the assigned emails, each with its source. Consent+ assigns new emails to a project notebook automatically when this is certain (e.g. same thread or file number); otherwise it asks. Emails belonging to a project notebook are never filtered out. If you mark a project notebook as confidential (e.g. health), Consent+ stores no facts, only references. Consent+ only reads documents from Google Drive that you select yourself in the project notebook via the Google picker (permission “only files you select”, drive.file), Consent+ has no access to the rest of your Drive. From selected documents we store text passages for searching within the project notebook; the originals remain in Drive. On your instruction, Consent+ attaches a selected document to a draft. Removing a document or deleting the project notebook deletes the stored passages, facts and references. For summaries, email excerpts and document passages are sent to the language model (section 7), which does not store them. Legal basis: Art. 6(1)(b) GDPR (feature you requested); for data of people involved Art. 6(1)(f) GDPR (keeping the matter organised).
5h. Invoices and routines: Consent+ checks new emails with a PDF or e-invoice attachment to see whether they are invoices addressed to you and lists them in your invoice overview (issuer, number, date, due date, amount, payment method such as “already paid”, “direct debit” or “to be transferred”, any bank details stated and whether you marked it as paid). Before a payment deadline passes, Consent+ reminds you by notification (section 5e). Consent+ has no access to your bank account and pays nothing. Bank reconciliation (optional, Mac app only): If you start it, the Mac app reads the outgoing payments of the last 60 days from the banking app MoneyMoney on your Mac and transfers, per booking, only date, amount, currency, payee name, payee IBAN and payment reference, no balances, no incoming payments, no categories. Consent+ uses them to mark matching invoices as paid; bookings are deleted after 60 days. Legal basis: Art. 6(1)(b) GDPR; you can hide individual invoices. If you additionally set up a routine (e.g. “File invoices in Drive”), the following applies. For this, the email text and the text of the PDF are sent to the language model (section 7), which does not store them. The log stores: issuer, invoice number, date, amount, sender address, a bank account named in the document (only to detect changes. Consent+ always presents a changed bank account to you) and what was filed. For e-invoices (XRechnung, ZUGFeRD), Consent+ reads the data directly from the file, without a language model. The PDF itself is not stored by us but only filed in the Google Drive belonging to the receiving account, in folders Consent+ creates there (permission “only files created by Consent+ or selected by you”, drive.file). If you connect an accounting service (FastBill or Lexware Office), Consent+ transfers, only for the mailboxes you assign to that connection, the PDF and issuer, invoice number, date, due date, net, tax and gross amount to that service; the service processes the data as your provider under its own terms. We store the API key encrypted; it is deleted when you disconnect. New standing orders first present every invoice to you; only once you allow it does the assistant handle them on its own. Every filing can be undone. The log is deleted after 12 months, and immediately when the standing order is deleted. Legal basis: Art. 6(1)(b) GDPR (feature you requested); for the issuers’ data Art. 6(1)(f) GDPR (orderly filing of your receipts).
5e. Notifications on your phone (optional): If you switch on notifications, we store your browser’s or operating system’s push address for your device (Apple, Google, Mozilla or Microsoft) and two keys. Every notification is end-to-end encrypted with these keys; the push service only forwards it and cannot read it. Content: sender and one sentence on what it is about, or, if you switch off “Show sender and topic”, only a general notice. You can switch it off at any time in the settings or in your browser; the device is then deleted. Legal basis: Art. 6(1)(b) GDPR.
5i. Contacts and network (optional): Consent+ builds a contact list from your emails (sender, recipients, date, subject), your appointments and, if you connect it, your address book (Google Contacts; Apple Contacts only in the Mac app after you allow it in macOS). For each contact we store: name and addresses, details taken from email signatures (role, company, phone, profile links), each with its source, the number and times of your exchanges (no email content), an automatic assignment to circles, events such as role changes or absence, your notes, and suggestions for whom you might get back in touch with, including a draft. To read signatures, for short briefings before appointments, for searching in everyday language and for drafts, excerpts are sent to the language model (section 7), which does not store them. Network radar: For contacts in your closer circles, Consent+ retrieves publicly accessible sources that the person has listed themselves (e.g. blog feed, Bluesky, Mastodon, GitHub, YouTube) and, at most once a week, searches for news about their company via the Serper search API, only the company name is transmitted. When you click, Consent+ searches for a contact’s public LinkedIn profile via Serper (name and company are transmitted). LinkedIn: If you upload your LinkedIn export (Connections.csv) or connect LinkedIn via the official data portability interface, we match names, companies and positions of your contacts against it; we store the access key encrypted. WhatsApp: Your browser analyses a chat export; only the days and number of messages are sent to Consent+, no content. Consent+ never contacts your contacts on its own. You can mute individual contacts or “forget” them, all details about them are then deleted and the address is no longer recorded. Stored until your account or the contact is deleted. Legal basis: Art. 6(1)(b) GDPR (feature you requested); for your contacts’ data Art. 6(1)(f) GDPR (legitimate interest in maintaining your business relationships), and for public sources only to the extent the person has published them.
5j. Network care, products and “Updates from …” (optional): If you add your own products or goals, Consent+ assesses which of your contacts match (role, company, conversation topics; for the best candidates using the language model, section 7) and suggests at most three steps a day, with a draft. Emails are sent from your own mailbox and only when you send them; “never for this person” is permanent. We store the match, suggestions and their outcome (sent, reply, meeting, introduction). Updates list: If you set up a page consent.plus/profile/…, people can sign up themselves (double opt-in). We store the address, optionally the name, chosen topics, time, IP address, browser identifier and the consent text as proof; unsubscribing works with one click in every email, after which the person receives no further updates. The user operating the page is responsible for the updates; Consent+ processes the data on their behalf. Legal basis: Art. 6(1)(a) GDPR (updates) and Art. 6(1)(b) and (f) GDPR.
5k. “News from Thomas” (product news, optional): During onboarding (never pre-ticked), as a one-time notice in the app and in the settings you can subscribe to news from Thomas Huhn, occasional emails about new features, improvements and tips for Consent+. The sender is Thomas Huhn on behalf of Consensus Ventures GmbH (controller, see above); emails are sent from his mailbox to the email address of your account. Because you are signed in and your address is already verified, no confirmation email is needed. As proof we store your account, the time, IP address, where you subscribed (onboarding, notice or settings) and the consent text in the language in which it was shown to you. If you decline during onboarding, we remember this so that we do not ask again. You can unsubscribe at any time in the settings or with one click in any email; we keep the proof afterwards so that we can demonstrate the earlier consent; when you delete your account, the subscription and the proof are deleted. Published posts are also public at consent.plus/profile/thomas-huhn; images in posts are stored by us and loaded from our server. In the app we show the latest post once as a notice and remember when you hide it. Legal basis: Art. 6(1)(a) GDPR and Section 7(2) no. 2 UWG (consent); withdrawal takes effect for the future.
5l. AI agents with AgentID and questions (6 Oct 2026): When an AI agent signs in via “Sign in with AgentID” (as the sender of an offer or as your own agent that you paired), we receive a signed sign-in token from AgentID (AgentMail Inc., USA) with the agent’s identifier and verified address, possibly its name, an anonymous identifier of its owner and, only if the owner releases it, the name and address of the responsible human. We store this to label submissions, apply your rule for agents and show paired agents (Art. 6(1)(b) and (f) GDPR); deleted with the account or once the agent is no longer needed. Emails from addresses belonging to AI agents are labelled based on the sender address; nothing is transferred to third parties for this. If you ask questions via “Ask questions first”, a language model (section 7) drafts them from the offer and your topics without revealing your topics; questions and answers are stored with the delivery. If you switch on your chief of staff’s own identity, AgentMail creates a mailbox for your account group; questions are then sent via AgentMail, and accounts at services are only created when you click (you finish the sign-in in your browser).
5m. Feedback & help (7 Oct 2026): If you report a bug, an idea or a question under “Feedback & help”, we store your message, the conversation about it, a screenshot you choose to attach and, optionally, technical details (page, browser, device, technical error messages from the last 24 hours, no email contents). We only look at an affected email if you explicitly tick the box. We use a language model (section 7) to classify and answer. We also record technical error messages from browser and server (message, page, account identifier) pseudonymously to detect and fix bugs (Art. 6(1)(b) and (f) GDPR); they are deleted after 90 days, tickets together with your account.
5n. Usage statistics and origin (7 Oct 2026, updated 26 Oct 2026): To improve Consent+, we count on our own servers in the EU which features signed-in accounts use (page or feature, time, device type, no email contents) and how many visits public pages receive (only totals per day, page and source, without personal reference). Since 26 Oct 2026 we also count for signed-in accounts how flows end (for example whether a task was completed, a follow-up question came up or something failed), whether voice, text or buttons are used, whether files and search are used (only the type and size band of a file or the length of a query and the number of results, never file names or search terms), waiting times and errors. This shows us where things get stuck. A small script in the browser sends these interaction events to us in batches and stores nothing on your device. Only the operator can look at individual accounts, to find problems; every such access is logged. We delete these interaction events after 90 days; what remains are daily totals (counts per day and feature), which we delete after 400 days. We set no cookies for this and store nothing on your device; there are no third-party advertising or analytics services. If you arrive via a campaign or partner link (e.g. ?utm_campaign=… or ?ref=…), we record once at sign-up where your account came from, to evaluate advertising and pay partners their commission. The legal basis is our legitimate interest in improving the service and running it economically (Art. 6(1)(f) GDPR). You can object at any time under Settings → Account → Your data. Other events are deleted after 400 days; the origin record together with your account. If you apply as a partner, we process the details from your application (name, email, company, website, audience, planned promotion) and later the commission data to run the partner programme (Art. 6(1)(b) GDPR); partners only see totals, never customer data. If someone invites you (link /e/… or code), we store with your account who invited you, and with both accounts the Pro days granted; the inviting person sees your name or address and whether you are set up or use Pro, never any content (Art. 6(1)(b) GDPR, running the invitation programme under § 4c of the terms). To prevent self-invitations, at the first payment we check whether the same payment card was used (via Stripe, only a card fingerprint, never the card number; Art. 6(1)(f) GDPR).
5o. Bringing in others and reviews (26 Oct 2026): If you bring another AI or a person into the conversation about an item, we pass on exactly the material shown there (for example this item's email thread, attachments, files and conversation notes), and only upon your action. Access applies to this item only, expires after 14 days and can be ended at any time; every retrieval is logged. People or AIs brought in can only read, reply and suggest changes, never send. A person reviewing opens the material only with a code we send to their address. The legal basis is your legitimate interest in handling your correspondence (Art. 6(1)(f) GDPR); for an AI from your own provider you are that provider's contracting party.
5o. Slack (optional, 8 Oct 2026): If you connect Slack, we store the Consent+ app's access key for your workspace in encrypted form, plus the workspace name and your Slack user ID. Depending on your settings, we send notes about new items (sender and subject, or just a note without content) to you or to a channel; when you ask, an email to a channel, with sender, subject, date, your note and, depending on your setting, the full email text or only the summary, and, if enabled, the attachments as files; we don't read channels or messages in Slack (we only fetch channel names so you can pick one). Slack (Salesforce) processes the messages as the provider of your workspace, possibly outside the EU. The legal basis is performance of the contract at your request (Art. 6(1)(b) GDPR). You can disconnect at any time under Connections; we then also revoke the access at Slack.
5p. Profile picture (14 Oct 2026): If you sign in with Google, we take the profile picture of your Google account (part of the “profile” sign-in data) and store a copy on our servers in the EU. It appears in your account menu and on the invitation page that recipients open via the link in your email footer; your browser never loads it directly from Google. We refresh it daily; if you have no photo of your own at Google, we show your initial. Deleting your account deletes the picture. Legal basis: Art. 6(1)(b) GDPR (displaying your account) or (f) (personal invitation).
5q. Note below your emails (14 Oct 2026): Emails you send with Consent+ carry a line (always on the free plan, can be switched off with Pro) with a link generated individually for each email. For this we store the recipient address, a rough category derived from the email itself (e.g. recruiting, management, private, offer; nothing from outside sources), the wording used, the time of sending and clicking, and whether someone signed up through it. The category is never shown to the recipient. Purpose: wording the line appropriately, being promotional at most once in 30 days, and measuring which wording helps. Automatically sent replies and sensitive emails only get a factual note. Legal basis: Art. 6(1)(f) GDPR; recipients can object at datenschutz@consensus.ventures. Retention: 12 months.
5r. Tips for senders by email (14 Oct 2026): If you subscribe in the sender area, we send you a confirmation email; only after you click it do you occasionally receive tips and news for senders. We store the time and proof of subscription and confirmation, which email you received and whether you clicked a link in it. You can unsubscribe with one click in every email or in the sender area; after that we send you no more marketing. Legal basis: your consent (Art. 6(1)(a) GDPR, § 7(2) no. 2 UWG), revocable at any time.
6. Automated processing: Emails are sorted automatically. This has no legal or similarly significant effect (Art. 22 GDPR); filtered emails remain in Gmail and can be accessed at any time.
7. Recipients/processors: Hosting (Scaleway, EU), database (Neon, Frankfurt region), email classification (TypeSafe/JEV), language models for analysing your interests, preparing cases, reply drafts and instructions to the assistant (Anthropic Claude and, for preparing cases and reply drafts, OpenAI GPT via Microsoft Azure, both via OpenRouter; since 3 October 2026 via OpenRouter’s EU region, which routes requests only to data centres in the EU; only providers that do not store data for training), Google (Gmail API, sign-in) or Microsoft (Microsoft 365/Outlook mailbox via Microsoft Graph, sign-in via Microsoft Entra ID, only if you connect your Microsoft mailbox; for European business customers processed within Microsoft’s EU Data Boundary), Stripe (payments), Serper (search API for company news and LinkedIn profile search, section 5i, only the company name, or name and company, and for web research you explicitly ask the assistant for, only the resulting search query, never the content of your emails; Consent+ fetches the public web pages found itself), Resend (sending our service emails such as sign-in links and the daily summary, sending region EU/Ireland; only the recipient address and the content of that email), AgentID/AgentMail (AgentMail Inc., USA; sign-in of AI agents and, only if you switch it on, your chief of staff’s mailbox, section 5l). Senders never see your list of topics or your profile. Anyone Consent+ replies to in your name sees your name and address, as with any reply, because they wrote to you first.
8. Retention: Until your account is deleted. We then remove all data, including mirrored emails, profile and records of consent, and remove the Consent+ labels in Gmail. Excepted are records of purchases (amount, date, billing address), which we must keep for ten years under § 147 AO and § 257 HGB (German Fiscal and Commercial Codes); they are deleted afterwards and not used for anything else until then.
8a. Transfers to third countries: Google, Anthropic, OpenAI, Microsoft, OpenRouter, Serper, AgentMail and Stripe are based in the USA or also process data there (OpenRouter processes the content of your emails in the EU via its EU region; the company itself is based in the USA). The basis is the EU-US Data Privacy Framework (adequacy decision of the European Commission of 10 July 2023) where the provider is certified, otherwise the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR).
9. Senders to whom Consent+ replies on behalf of a user: If you send an offer to a Consent+ user, we process on their behalf your sender address, the subject and the text of your email in order to send you a reply with a delivery link and to prepare your offer as a draft (Art. 6(1)(f) GDPR, the recipient’s legitimate interest in organising their inbox). Using the unsubscribe link in the reply stops further notices. If you use the delivery link, sections 2 and 8 apply to your account.
10. Your rights: Access, rectification, erasure, restriction, data portability, objection, withdrawal of consent with effect for the future, and complaint to a supervisory authority.