Privacy Policy

Version 2.3, valid from 23 November 2026. We take the protection of your personal data seriously and process it only as described here. If anything is unclear, write to contact@aivatarconsulting.com.

1. Who is responsible

Aivatar Consulting Asbrede, sole proprietorship of Elias Asbrede, Bordackerstrasse 34, 8610 Uster, Switzerland, UID CHE-138.756.271, is responsible for the processing described here (controller). Contact for all data protection matters: contact@aivatarconsulting.com. We have not appointed a data protection officer and are not required to. Our representative in the EU under Art. 27 GDPR is Data Protection Representative Limited (DataRep), 77 Camden Street Lower, Dublin, D02 XE80, Ireland. You can reach DataRep through the form at [datarep.com/data-request](https://www.datarep.com/data-request/); please name Aivatar Consulting Asbrede.

2. Scope and legal framework

This policy explains how we process personal data when you visit aivatarconsulting.com or erechnungjetzt.de (erechnungjetzt.de is our information site about Aivatar E-Rechnung; orders and accounts run on aivatarconsulting.com), use the Aivatar software (for example Aivatar OS, Aivatar E-Rechnung, Marketing OS, Sales OS and the free tools), buy from us, contact us, or are a business contact of ours. It applies under the Swiss Federal Act on Data Protection (FADP) and, where it applies to you, the EU General Data Protection Regulation (GDPR). Legal bases under the GDPR: performance of a contract or steps before one (Art. 6(1)(b)), legal obligations under the law of the EU or a member state (Art. 6(1)(c)), our legitimate interests in operating, securing and marketing our business (Art. 6(1)(f)), and your consent (Art. 6(1)(a)), which you can withdraw at any time. Under the FADP we process data on the same grounds. Allocation under the GDPR: delivery and security of the website: point (f). Google Analytics and Google Ads: point (a) and section 25(1) of the German TDDDG. Account, software, order, billing and support: point (b). Retention under the Swiss Code of Obligations (Art. 958f CO): point (f), our interest in meeting the duties that apply to us. Contact requests: point (b) or (f). Marketing e-mails: point (a), and point (f) for existing customers. Connected accounts: point (b). For persons named on our customers' invoices, the customer as controller determines the legal basis. FightPlans (fightplans.com) is also operated by us and has its own privacy notice; the sections on hosting, payments, recipients, transfers and your rights apply there as well.

3. Visiting our website

When you open a page of aivatarconsulting.com or erechnungjetzt.de, our server (Hostinger, Frankfurt) processes your IP address, date and time, the page requested, the referring page and your browser and device type. We need this to deliver the website, keep it secure and find errors (legitimate interest). Server access logs are deleted after 14 days. Fonts are served from our own server. The order page of Aivatar E-Rechnung calls a server function at Supabase when it loads; Supabase then receives your IP address and browser details. Your browser loads the Google tag (for Google Analytics and Google Ads) from Google only after you agree in the cookie banner; without consent, loading a page does not contact Google. Statistics with Google Analytics and Google Ads conversion measurement run only after you agree in the cookie banner. If you came through one of our Google Ads, Google can then tell us that an ad led to an order (counted in aggregate; no personalised ads or remarketing). Details and the list of all cookies and similar technologies are in our Cookie Policy. If you move from erechnungjetzt.de to aivatarconsulting.com through an order button, we take over a consent to Google Analytics and Google Ads given there; details are in the cookie policy.

4. Account, software and customer content

For an account we process your name, e-mail address, company, password (stored only as a hash) and your settings; for each use of the software also the content you enter or upload, usage data (for example which function ran, credits used) and technical logs. Purpose: providing the software you signed up for (contract). Where customer content contains personal data of other people (for example invoices with contact persons in Aivatar E-Rechnung, contacts and e-mails in Sales OS, or e-mails in a connected mailbox), our customer decides about it and is the controller; we process that data only on the customer's instruction, as a processor under our data processing agreement (AVV/DPA). If you are such a person, please contact the customer; we will forward requests we receive. Aivatar E-Rechnung: your billing software sends invoices to a dispatch mailbox on your own mail server. Our server fetches this mailbox, creates and validates the e-invoice and sends it on your behalf from this mailbox to your invoice recipient, by IMAP and SMTP or, for a mailbox connected through the Microsoft sign-in, through its interface (Microsoft Graph). Mailboxes at Gmail or Google Workspace are connected over IMAP and SMTP with an app password; we do not use Google's Gmail interface for Aivatar E-Rechnung. We store the mailbox passwords or access tokens encrypted in a vault. We do not store e-mails without an invoice, and we keep fetched invoice e-mails for at most 90 days. We act as your processor for this; the details, all sub-processors and the deletion rules are set out in the data processing agreement (AVV) (also as a PDF). You can ask us at any time to delete your account at contact@aivatarconsulting.com. Deleting the account ends running subscriptions and removes the data linked to it, except the records we must keep (section 13). While your Aivatar E-Rechnung contract runs, we delete the account and the archive only on your instruction in text form after you have exported the archive; after the contract ends, section 13 applies.

5. Orders and payments

Payments are processed by Stripe. Stripe receives your name, e-mail address, billing address, payment details and the purchase; we receive the payment status, the last digits and type of the card, and the invoice data, never your full card number. We use the data to execute the contract, collect payments, send invoices and meet bookkeeping duties (10 years). Stripe also uses data for fraud prevention as its own controller; see the Stripe Privacy Policy. For FightPlans coach subscriptions, the payment runs through the coach's own Stripe account (Stripe Connect). Managed plans of Aivatar E-Rechnung are invoiced and you pay them by bank transfer; for this we receive from our bank the account holder's name, the bank details, the amount and the payment reference.

6. Contact and e-mail

Messages through the contact form are stored in our database and sent to us by e-mail via Brevo; e-mails to us arrive in our Microsoft 365 mailbox. We use the data to answer you and, if it leads to one, for the business relationship (legitimate interest, steps before a contract). Contact form submissions are deleted after 2 years. We no longer offer Ask Avi, the former assistant on our website. Rated questions and answers from before are deleted at the latest 12 months after they were rated.

7. AI functions

Many functions use AI language models, for example to research companies, draft texts, extract invoice data, transcribe audio or create images. Every function that works with your content uses an open AI language model run by Nebius B.V. (Netherlands); the developer of the model receives no data. Every invoice in Aivatar E-Rechnung is read in this way too. We reach the model through OpenRouter, Inc. (USA) as a technical gateway. Routing is fixed to Nebius, with no fallback to other hosts, and Zero Data Retention is enforced: neither OpenRouter nor Nebius stores your inputs or the outputs, and neither uses them for training. Scanned invoices without readable text are turned into page images by our own server in Frankfurt or by your browser; photos and page images are read by the same model. There is no separate text recognition at another provider. For documents with readable text, Aivatar E-Rechnung replaces IBAN, VAT ID, tax number, e-mail addresses and telephone and fax numbers with placeholders before the hand-over and puts them back only into the result; these values then do not reach the AI language model. Names and postal addresses cannot be replaced this way, and for scans and photos no replacement is possible. Nebius does not name a fixed place of processing: its data centres are mostly in the EU/EEA (Finland, France, Iceland) and in the United Kingdom, and group companies are also located in the USA and Israel. Processing outside the EU can therefore not be excluded (section 12). Only web search (search queries) and the transcription of dictation and live-stream audio use the other providers listed in section 11, and image generation receives only an image description. If you store your own key for an AI provider, your requests run on your own account with that provider under its terms and privacy policy. We store your key encrypted in a vault and use it only for your requests. The Prototype Builder builds prototypes in an automated pipeline at GitHub using Anthropic's Claude; your specification is sent there for that purpose. AI output is not a decision about you. We do not make decisions based solely on automated processing that have legal or similarly significant effects on you.

8. Research functions and public data

Research functions (for example account research, lead discovery, risk and ESG analyses) read publicly available sources: company websites through our own crawler on our server, public registers and open data such as OpenStreetMap and Wikidata, and web search through Exa. Such sources can contain business contact data of people (for example a managing director named in an imprint). When a customer runs such a function, the customer is the controller of the results and must have a legal basis to use them, in particular for contacting people.

9. Business contacts and our own outreach

We process business contact data (name, company, role, business e-mail address and telephone number, the source, and our correspondence) when you write to us, send us an enquiry or are a customer, in order to answer you and to manage the business relationship. We send marketing e-mails only with your prior express consent (Art. 6(1)(a) GDPR) or within the statutory exception for existing customers (Art. 6(1)(f) GDPR, section 7(3) of the German UWG). We do not send unsolicited marketing e-mails to persons or companies that have not written to us. From earlier research, business contact data from public sources (company websites and their imprint, public registers, business directories) may be stored with us; we do not use it for marketing e-mails without consent and delete it after the periods in section 13. Where data does not come from you, we tell you the source and your right to object at the latest when we first contact you. Our mails are sent from our Microsoft 365 mailbox; for drafts we use AI language models through OpenRouter, Inc. (USA), which can run at providers outside Switzerland and the EU. You can object at any time with a short reply or an e-mail to contact@aivatarconsulting.com. We then delete your data and keep only the e-mail address on a block list so that we never contact you again.

10. Connected accounts

You can connect accounts at other providers so the software can act on your instruction: Google (YouTube, Search Console and Analytics, Gmail), Microsoft (Outlook mailbox and calendar through Microsoft Graph), LinkedIn, Meta (Instagram and Facebook), TikTok, Bluesky, Mastodon, dev.to, WordPress, Ghost, Twitch, or an e-mail mailbox via IMAP/SMTP. For Search Console and Analytics you instead grant read access to our service account in your own property. We store the access tokens or passwords in our database, encrypted at rest (mailbox passwords and AI keys in an encrypted vault), and use them only for the actions you start or configure: publishing approved content, sending approved e-mails, reading data for your reports, or reading incoming invoices. When you disconnect an account in the software, we delete the stored access data. To withdraw the permission at the provider as well, also remove our app in the security settings of your account there (for Google: myaccount.google.com/permissions).

10a. Use of Google API Services (YouTube)

When you connect a YouTube channel to Marketing OS, Aivatar Consulting accesses your YouTube account through Google's OAuth 2.0 flow. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. By connecting, you also agree to the YouTube Terms of Service; see the Google Privacy Policy. Scopes we request: How we use the data: Storage and retention:

  • https://www.googleapis.com/auth/youtube.upload, required so Marketing OS can publish the videos you have uploaded to your account on your behalf.
  • https://www.googleapis.com/auth/youtube.readonly, required so Marketing OS can read your channel ID and name to display "Connected as <your channel>" in the dashboard and confirm uploads succeeded.
  • https://www.googleapis.com/auth/youtube, required so Marketing OS and Stream Studio can manage what you published through them: update titles, descriptions and thumbnails of your videos, read your uploads list, and read your live broadcasts and live chat while you stream.
  • We only use Google user data to perform the action you initiated (publishing your video, generating its description, fetching channel status).
  • We do not use Google user data to serve advertising, build user profiles, or improve any unrelated product.
  • We do not transfer Google user data to third parties except as needed to provide or improve the user-facing features of Marketing OS, to comply with applicable law, or with your explicit consent.
  • We do not allow humans to read your Google user data unless we have your affirmative agreement, it is necessary for security purposes (e.g. investigating abuse), to comply with applicable law, or for our internal operations and even then only when the data has been aggregated and anonymized.
  • We never use Google user data, video content or transcripts to train, fine-tune or evaluate any AI model.
  • OAuth access and refresh tokens are stored encrypted at rest in our database (Supabase, EU region, Ireland) and used only to make API calls on your behalf.
  • Your video files are uploaded directly to our server (Hostinger, Frankfurt, Germany), processed by AI workers (transcript, metadata, thumbnail, short clips), uploaded to YouTube, and then automatically deleted from our servers, typically within hours of the final short publishing.
  • You may disconnect your YouTube channel from Marketing OS at any time via the Channels page. Disconnecting deletes the stored access and refresh tokens from our database.
  • You may also revoke Marketing OS's access directly at myaccount.google.com/permissions.

11. Recipients and service providers

We do not sell personal data. We share it only with the recipients below: with service providers who process it on our behalf under data processing agreements, with providers that partly act as controllers of their own (for example Stripe for fraud prevention and Google for ad measurement), with the platforms you connect, with authorities where the law requires it, and with professional advisers bound to confidentiality. The table covers the whole website and all Aivatar products. For Aivatar E-Rechnung we use only Supabase, Hostinger, OpenRouter, Nebius, Brevo and Microsoft, as listed in the data processing agreement (Annex 2); all other rows concern other products or the website and receive no invoice data.

  • Supabase Pte. Ltd., Singapore (on Amazon Web Services) — Database, sign-in, file storage, server functions | All account and app data | EU (Ireland); support access from the USA and Singapore (Standard Contractual Clauses)
  • Hostinger International Ltd. — Server for the website, video processing, e-invoice validation and PDF generation, fetching and sending through the Aivatar E-Rechnung dispatch mailbox, our own web crawler | Website requests, uploads, documents, e-mails in the dispatch mailbox | Germany (Frankfurt); weekly backup of the server in France
  • Cloudflare, Inc. — Protection and delivery of traffic to fightplans.com | IP address, request data | Global network, USA
  • Stripe Payments Europe Ltd. and Stripe, Inc. — Payments, subscriptions, invoices, customer portal | Name, e-mail, address, payment data, transactions | Ireland, USA
  • Brevo GmbH (Berlin) — System e-mails: sign-up, password reset, contact confirmation, notifications; for Aivatar E-Rechnung, alerts about errors and held invoices | E-mail address, name, e-mail content (for e-invoices: name of the invoice recipient, invoice number, recipient address, error text) | France and Belgium (EU); support access from the USA and India (Standard Contractual Clauses)
  • Microsoft Ireland Operations Ltd. (Microsoft 365) — Our own mailbox and e-mail correspondence | E-mails, contacts | EU; access by Microsoft Corporation (USA) possible
  • Nebius B.V. (Netherlands), host of the open AI language model we use (the developer of the model receives no data) — AI language model for every function that works with your content: Sales OS, Marketing OS, research synthesis and reading invoices (text, photos and page images) in Aivatar E-Rechnung | The prompt and the content needed for the task; Zero Data Retention: inputs and outputs are not stored and never used for training | Data centres mostly in the EU/EEA (Finland, France, Iceland) and in the United Kingdom; processing outside the EU cannot be excluded; group companies also in the USA and Israel (Standard Contractual Clauses)
  • OpenRouter, Inc., a US software company we use to reach the AI language models, and the providers it reaches for web search (Perplexity AI), dictation in Sales OS and live-stream transcription (OpenAI, Groq) — Technical gateway for requests to the AI language model (fixed to Nebius, with no fallback to other hosts; Zero Data Retention: inputs and outputs are not stored); web search and transcription. In Aivatar E-Rechnung we use only the AI language model through it, no add-on services | Requests to the AI language model in transit; search queries, audio of dictation or live streams. Providers that do not store prompts beyond the request or train on them, none in China | USA (Standard Contractual Clauses)
  • Exa Labs, Inc. (web search via OpenRouter) — Web search for research functions of other Aivatar products (not Aivatar E-Rechnung) | Search queries | USA
  • Google LLC (Gemini API) — Image generation for thumbnails and post images | Image descriptions | USA
  • Pollinations.ai — Backup image generation for video thumbnails in Marketing OS (not Aivatar E-Rechnung) | Image description only | Outside Switzerland, location not specified by the provider
  • GitHub, Inc. and Anthropic PBC — Prototype Builder: automated build of the prototype from your specification | The solution specification you submit | USA
  • Google Ireland Ltd. and Google LLC (Google Analytics, Google Ads) — Website statistics and ad conversion measurement, only with your consent | Pseudonymous usage data, shortened IP address | EU, USA
  • 5werk UG (haftungsbeschränkt), In der Steele 2, 40599 Düsseldorf, Germany — Agency: management of our Google Ads campaigns, evaluation of the ads and maintenance of the information site erechnungjetzt.de | Measurement data from Google Ads and Google Analytics (pseudonymous usage data, number and type of orders from ads; collected only with your consent). No access to customer accounts, order data or invoices | Germany
  • Platforms you connect (Google: YouTube, Search Console, Analytics, Gmail; Microsoft; LinkedIn; Meta: Instagram and Facebook; TikTok; Bluesky; Mastodon; dev.to; WordPress; Ghost; Twitch) — Publishing, sending and reading on your instruction (section 10) | The content and account identifiers needed | Location of the respective provider, often the USA
  • Esri Inc. and CARTO — Map tiles in Risk Intelligence | IP address when the map loads | USA, EU
  • OpenStreetMap (Overpass API) and Wikidata — Public company data for research functions | Search terms only | EU
  • IndexNow (search engines such as Microsoft Bing) — Notifying search engines of new public pages | Page addresses only | USA

12. Transfers abroad

Our main systems are in the EU (Ireland, Germany, France, Belgium). Some providers are located in or access data from the USA. Where a country does not have adequate data protection recognised by Switzerland or the EU, we rely on the EU-US and Swiss-US Data Privacy Framework where the provider is certified, or otherwise on the Standard Contractual Clauses of the European Commission, as recognised by the Swiss Federal Data Protection and Information Commissioner, together with supplementary measures. Requests to the AI language model (section 7) pass through OpenRouter, Inc. in the USA; Nebius runs its data centres mostly in the EU/EEA and in the United Kingdom, but processing outside the EU cannot be excluded. We base these transfers on the Standard Contractual Clauses of the European Commission. You can ask us for a copy of these safeguards. Safeguard per recipient: Supabase and OpenRouter: Standard Contractual Clauses (neither is certified under the Data Privacy Framework). Nebius and Hostinger: Standard Contractual Clauses where data is processed or accessed from outside the EU. Microsoft, Brevo, Stripe, Google, GitHub, Esri and Cloudflare: Data Privacy Framework, supplemented by Standard Contractual Clauses. Anthropic, OpenAI, Perplexity and Groq: Standard Contractual Clauses. Exa Labs and Pollinations.ai receive only search queries or image descriptions; we hold no certification or Standard Contractual Clauses for these two providers. We use neither of them for Aivatar E-Rechnung. For the transfers in Aivatar E-Rechnung we have documented a transfer impact assessment per recipient.

13. How long we keep data

We keep personal data only as long as needed for the purpose or required by law, and delete it automatically afterwards:

  • Account data (name, e-mail, company, settings) — As long as the account exists. After deletion, a minimal record (e-mail, name, reason) is kept for 12 months to handle disputes and misuse.
  • Customer content in the Software — Until you delete it or the contract ends, plus 30 days for export, or 90 days for Aivatar E-Rechnung (Terms section 22).
  • Aivatar E-Rechnung archive (originals, e-invoices, validation reports) — As long as your contract runs. After the contract ends you can download the archive for another 90 days; we then delete it, or earlier on your instruction in text form. We remind you by e-mail 30 days before the deletion. The statutory retention duty for your invoices (GoBD, § 147 AO, § 14b UStG) remains with you.
  • Fetched invoice e-mails from the dispatch mailbox (Aivatar E-Rechnung) — At most 90 days. E-mails without an invoice are not stored.
  • Payment, invoice and bookkeeping records — 10 years (Art. 958f Swiss Code of Obligations).
  • Contact form submissions — 2 years.
  • E-mail correspondence — As long as needed for the matter; business correspondence relevant for bookkeeping 10 years.
  • Ask Avi feedback (rated question and answer) — 12 months.
  • Rate-limit entries (IP address or e-mail with a counter) — 30 days.
  • Server access logs — 14 days.
  • Backups — Database: daily backups that are overwritten after 7 days. Server: a weekly backup that is replaced by the next one. Deleted data may still be contained in a backup until then; it is not processed further there.
  • Google Analytics data (with consent) — At most 14 months.
  • Google Ads conversion measurement data (with consent) — Cookie and click identifier 90 days. According to Google, it anonymises its ad logs after 9 months (IP address) and 18 months (cookie information).
  • Business contacts for our own outreach — As long as relevant for a possible business relationship, at most 3 years after the last contact. After an objection we delete the data and keep only the e-mail address on a block list so we never write again.
  • Access tokens of connected accounts — Until you disconnect the account.
  • Uploaded videos for Marketing OS — Deleted from our servers after publishing, usually within hours.
  • Prototypes — 30 days unless you keep them; at most the 10 newest are kept.

14. Your rights

Right to object: where we process your data on the basis of legitimate interests (Art. 6(1)(f) GDPR), you may object at any time on grounds relating to your particular situation. You may object to processing for direct marketing at any time without giving reasons. To do so, write to contact@aivatarconsulting.com. Within the limits of the applicable law you also have the right to: Send requests to contact@aivatarconsulting.com. Where we have reasonable doubts we may ask you to prove your identity. We answer within one month, and under the FADP as a rule within 30 days. You are not required by law to provide your data; without the details needed for an account and an order, however, we cannot conclude the contract. Where we process data on behalf of one of our customers (see section 4), please contact that customer; we will forward your request.

  • access the personal data we hold about you and receive a copy (Art. 25 FADP, Art. 15 GDPR);
  • have incorrect data corrected and incomplete data completed;
  • have data deleted or its processing restricted;
  • receive data you provided in a common machine-readable format, or have it transmitted to another provider (data portability);
  • object to processing based on legitimate interests, and to direct marketing at any time;
  • withdraw a consent at any time with effect for the future, for example for analytics cookies via the cookie banner or by deleting your cookies;
  • not be subject to a decision based solely on automated processing that has legal effects on you; we do not make such decisions;
  • complain to a supervisory authority. In Switzerland this is the Federal Data Protection and Information Commissioner (edoeb.admin.ch); in the EU it is the authority of your country of residence or workplace.

15. Data security

We protect personal data with technical and organisational measures appropriate to the risk, in particular: encrypted connections (TLS), mailbox passwords stored encrypted, access separated per customer so every customer sees only their own data, server access by SSH key only, a firewall and fail2ban on our server, automatic security updates, and logged admin access. No system is perfectly secure; please protect your own access data as well.

16. Children

Our services are intended for people aged 18 and over. We do not knowingly process data of children. If you believe a child has given us data, please tell us and we will delete it.

17. Changes to this policy

We adapt this policy when our processing, our providers or the law change. The version published here applies. For significant changes that affect registered users, we also inform you by e-mail.