Skip to content

Privacy notice

Last updated: 12 November 2026

I run this website (www.seelig.ai) as an individual. This page explains which personal data I process when you visit the site or use its features, why I do so and who receives the data.

Controller

Yannick Seelig, 8620 Wetzikon ZH, Switzerland. E-mail: hello@seelig.ai.

For questions about data protection and to exercise your rights, contact me at this address.

In short

  • I use my own tool to analyse how visitors use the website. I set no advertising cookies. You can switch this off at any time with "Opt out of analytics" at the foot of every page, and I analyse visits from the EU and the EEA only with your consent. For the chat I also store the answered questions (see "Chat").
  • Besides the language cookie, I set cookies for this analysis (see "Cookies and browser storage").
  • Your browser reports how fast a page loaded. These measurements carry no identifier, and I store no IP address with them (see "Load time measurement").
  • What you enter yourself (contact form, order form, booking, chat, website check) goes to service providers, mostly in the USA, so that the feature works. The kinds of providers are listed below.

Visiting the website and hosting

The website runs on a hosting provider in the USA. With every request, the provider processes the technically necessary data, in particular your IP address, the time, the requested address and details of your browser. Pages are delivered through the provider's global network, and the server functions (contact form, order form, chat, website check, call and order requests from AI assistants, booking notices from the booking service) run in the USA. The purpose is to deliver the website, keep it secure and fix errors.

If an error occurs on the website, the server sends me an e-mail through my e-mail delivery service with the error message including its technical trace (stack trace), the page and the time. If a page fails with an error in your browser, your browser sends the error message with its technical trace and the page address to my server for this. Your IP address is not part of this e-mail. If an error message contains details you entered, such as a checked address, they may appear in it.

Analysing how the website is used

I analyse how you reach this website and how you use it, to improve content, offers and usability. My own script records the source of your visit (campaign data such as utm_source, click ids from advertising networks, the referring page and the landing page), the pages you visit with time on page, clicks, scroll depth, load times and technical errors, and your device type, screen size, browser, operating system, language, time zone and the country and region (such as the canton) you connect from. I also record the flow of single visits (session recording). Form inputs and the content of the chat are never recorded. I do not store your IP address.

If you send me a request through the contact form or the website check, place an order or request a quote through the order form, book a first call, or confirm a request an AI assistant prepared for you, I link the source of your visit to the entry of your request in my database, so I can see which channels lead to requests. The link runs through a random id or the order number. For the contact form and the website check, the source is also part of the e-mail I receive about your request.

The infrastructure provider in the USA receives the data, and the database provider stores it in its Frankfurt data centre (see "Recipients and transfers abroad"). No advertising network receives any of it. I delete session recordings after 90 days, single recordings I mark to improve the website after 13 months, click and page data after 13 months, and the source data of a request together with the request.

I analyse visits from the EU and the EEA only with your consent and ask for it on your first visit. Everyone else can object at any time with "Opt out of analytics" at the foot of every page. You can also withdraw your consent there. I also treat a Global Privacy Control signal from your browser as an opt-out. After that, nothing is recorded. On request I delete the data stored about your visit: write to hello@seelig.ai.

Load time measurement

To see how fast the pages load for real visitors, your browser measures five technical values for the page you open directly or reload (the Core Web Vitals and two more load timings) and sends each one once, as soon as it is final or when you leave the page or switch to another tab, to a service at vitals.seelig.ai that I run on an infrastructure provider in the USA. Each value comes with its rating (good, needs improvement or poor), the page address without parameters, the kind of navigation (for example a reload) and whether the window is narrower than 768 pixels.

Only these details and the date are stored, in a database of this provider in the EU. I store no IP address, no identifier and no cookie. The provider processes your IP address to deliver the request. I delete the measurements after 90 days.

Cookies and browser storage

Besides the language cookie, I set the following cookies to analyse how the website is used. I set no advertising cookies. If you opt out, I only set the language cookie and the cookies that remember your choice.

  • Cookie "locale": stores your language choice (German or English) for 12 months. Only this website sets and reads it, and the language switch needs it.
  • Cookie "_cap_v": a random visitor id, 13 months.
  • Cookie "_cap_s": a random session id, ends 30 minutes after your last activity.
  • Cookies "_va_ft" and "_va_ids": the source of your first visit and click ids from advertising networks, 90 days.
  • Cookie "_va_lt": the source of the current visit, 30 minutes after your last activity.
  • Cookie "_va_lnd": the source of your last visit that did not come directly, 90 days.
  • Cookie "_va_meta": the number of your visits and the date of the first one, 90 days.
  • Cookies "_cap_off", "_cap_ok" and "_cap_no": remember that you opted out of or agreed to the analysis, 13 months.
  • Cookie "_cap_fg": keeps your visitor id only until your deletion request has reached me, 30 days at most.
  • Cookie "_cap_own": marks my own devices so my visits stay out of the analysis. It is never set for visitors.
  • Storage for the analysis: "_cap_q" in local storage (localStorage), a counter of the data packets sent in your current session, and entries starting with "_va_" in session storage (sessionStorage). They remember the order of the pages of your visit and when you opened a form and started filling it in. If you opt out, these entries are deleted.
  • Session storage (sessionStorage): one entry remembers whether you paused the animation on the homepage, "audit-result" keeps the result of your last website check so it is still there when you go back, and "seelig-chat-opened" remembers that you have already opened the chat in this tab, so the analysis can tell a first opening from a repeat. All are deleted when you close the tab.
  • Local storage (localStorage): "seelig-chat" keeps your chat history, the language and the conversation number so the conversation is still there on your next visit. "seelig-chat-notice" remembers that you confirmed the notice in the chat, "seelig-chat-wide" whether you chose the wide view. These entries stay until you delete them: in the chat under "My data" with one click, or in your browser settings. Your browser sends the chat history only when you send a message in the chat (see "Chat"). "sa_bk" holds a random id for 3 hours after each click on a booking link, at most five, which links a booked first call to the source of your visit, and is only created while the visitor analytics is on. The website deletes expired ids on your next page view, the booked one once it has confirmed the booking on your return, and "Opt out of analytics" all of them. "seelig-creatures-hidden" remembers that you hid the critters, "seelig-creatures-muted" that you turned their sound off. "Show the critters" in the footer deletes the first entry again, and you can delete both in your browser settings.

Contact form and e-mail

When you write to me through the form, I process your name, your e-mail address, your message and, if you provide them, your company or website and your topic, to answer your inquiry. The form sends this information through an e-mail delivery service in the USA to hello@seelig.ai, with your address as the reply address. The same service also sends your address a short confirmation of receipt that contains none of your details. So that nobody can use the form to have strangers mailed, at most one confirmation per address goes out per day. For this, I store a hash of your e-mail address, made with a secret key. To keep track of inquiries, the website also stores your inquiry in my database at the database provider's Frankfurt data centre, namely your name, e-mail address, message, company or website, topic, language, the time and the status. If the visitor analytics is on for you, the random visitor and session ids are added, which link the entry to the source of your visit. I keep the entry until you ask me to delete it, and then delete it together with the source of the visit. The website does not write your name or e-mail address to the server logs.

E-mails to hello@seelig.ai are received by the infrastructure provider in the USA that also hosts the load time measurement, and forwarded to my personal mailbox at an e-mail provider in the USA. The same applies if you write to me directly.

Order and quote form

When you order a service or request a quote through the order form, I process your name and your e-mail address and, if you provide them, your company, your billing address, your website, your phone number, your project details and your note. I need them to check the order, to enter into and perform the contract and to invoice. My server turns them into a PDF of the order or quote and sends it through an e-mail delivery service in the USA as an e-mail to hello@seelig.ai, with your address as the reply address. The same service sends a copy of it without your project details, phone number and note to your address as a confirmation of receipt. So that nobody can use the form to have strangers mailed, at most 5 confirmations per address go out per day. For this, I store a hash of your e-mail address, made with a secret key. So that an order sent twice does not arrive twice, I also store the order number, the time and a hash of your form details, made with the same key. To keep track of orders and quote requests, the website also stores your details in my database at the database provider's Frankfurt data centre, namely your name, e-mail address, company, billing address, website, phone number, your answers to the project questions, your note, the chosen service with the options you picked and its price, the order number, the language, the time and the status. If the visitor analytics is on for you, the random visitor and session ids are added, which link the entry to the source of your visit. I keep the entry until you ask me to delete it, and then delete it together with the source of the visit. The website does not store the PDF and does not write your name or e-mail address to the server logs.

If an AI assistant prepares an order or quote request on your behalf through my API or my MCP server, I receive the same details from that assistant as from the order form. I send you an e-mail with a link to a confirmation page through my e-mail delivery service. The order is only sent once you check it there, read the terms and confirm. I then process it like an order through the form and store it in my database in the same way, with a note that it came through an AI assistant. Until then, your details are kept encrypted at the hosting provider in Frankfurt, together with the status, the service, the request timestamps and a hash of your e-mail address made with a secret key. When you confirm, I delete the details stored at the hosting provider, and the rest of the record there within 4 days, as I do with a request that is never confirmed. A request that is never confirmed never reaches my database. To limit the number of requests, I store hashes of your e-mail address, its domain (except for common e-mail providers) and the IP address the request came from, and delete them within 3 days. If you did not request anything, ignore the e-mail and nothing is ordered.

If your order becomes a contract, I keep the order as a PDF, the e-mails about it and the invoices as business records for 10 years, as the Swiss Code of Obligations requires (Art. 958f CO). If no contract comes about, I delete the PDF and the e-mails once I no longer need them for your inquiry. In both cases I keep the entry in my database until you ask me to delete it.

Booking a call

You book the first call through a booking service in the USA. I process what you enter in the booking form (name, e-mail address, your company website, notes and any additional guests) to prepare and hold the call. The call runs on the same provider's video service. The provider processes this data on my behalf. After the booking the booking service reports it to me, and the website stores your name, your e-mail address, your company website, your notes, the time of the call, the language, the booking ID, the time and the status in my database at the database provider in Frankfurt. Additional guests are not stored there. If the visitor analytics is on for you, the website adds a random id to a booking link when you click it. It travels with the booking to the booking service and comes back with its notice. If you come back to my website within 3 hours, the visitor analytics links the booking to the source of your visit through this id. So that only an id that was really booked counts, and only once, I keep a hash of the id, made with a secret key, at the hosting provider in Frankfurt, and after your return a note with the same hash, both for at most 3 days. The id holds nothing about you. I keep the entry until you ask me to delete it, and then delete it together with the source of the visit.

If an AI assistant requests a first call on your behalf through my API or my MCP server, I receive your name, e-mail address, the requested time, the topic, and any notes and company website from that assistant. I send you an e-mail with a confirmation link through my e-mail delivery service. Nothing is booked until you confirm through that link. Then the details go to the booking service, as with a direct booking. Your name, e-mail address, notes and website travel encrypted inside the link itself. I do not store them until you confirm. If you confirm and the booking goes through, the website stores your name, e-mail address, the time of the call, the chosen service, the notes, the website, the language, the booking ID, the time and the status in my database at the database provider in Frankfurt, with a note that the request came through an AI assistant, and with the random visitor and session ids if the visitor analytics is on for you. I keep this entry until you ask me to delete it. At the hosting provider in Frankfurt I store the status, topic and time of the request, its timestamps and, once booked, the booking ID, plus a hash of your e-mail address made with a secret key. To limit the number of requests, I also store hashes of your e-mail address, its domain and the IP address the request came from, made with the same key. I delete the hashes used for limiting within 3 days and the request record within 30 days. If you did not request anything, ignore the e-mail and nothing is booked.

Chat

The chat is an AI assistant that answers questions about my services. When you send a message, it goes to the AI model provider together with the conversation so far (at most the last 24 messages, your messages up to 500 characters each, at most 12 questions per conversation) to generate the reply. Your browser keeps the history in local storage so it survives moving between pages and your next visit (see "Cookies and browser storage"). To improve the chat, I store every answered question: your question (at most 500 characters), the answer (at most 1500 characters), the page you asked on, the language, which question of the conversation it was, which cards the chat showed and a random conversation number your browser creates. E-mail addresses, phone numbers and IBANs are masked before storing. A second call to the same provider assigns the question one topic from a fixed list, for example an offer, prices or booking. If you rate an answer with thumbs up or down, I store the rating and your optional note (at most 300 characters, also masked) under the same conversation number. Your IP address and your name are not stored. If you write names or other details into a question yourself, they are in the stored text. The entries are kept at the hosting provider in Frankfurt and deleted after 12 months. Apart from that, the server logs only technical data (model, token counts, duration, error type), never the content. Please do not enter confidential or sensitive information in the chat.

Website check

When you have an address checked, my server fetches that page, its robots.txt and up to 30 addresses linked from it, plus the page five more times with the user agent of a browser and of four AI bots. The address also goes to a website performance analysis service, which measures the page's load time and supplies measurements from real visits, and the domain name with the technical findings goes to the AI model provider for the written analysis. For the question of what an AI search says about the website, the domain name goes to the same provider and its web search. The checked address may appear in the hosting provider's server logs. If the address itself contains personal data, such as a name, that data is affected too.

Alongside this, my server reads up to 20 pages of the website, found through the sitemap or the links on the home page, and fetches up to 30 internal addresses linked from them to find dead links. The text of these pages (at most 700 words per page) goes to the AI model provider to find spelling, translation and date errors, as long as the daily limit for this text check is not reached. Before that, I replace e-mail addresses, phone numbers and IBANs in the text with placeholders. How the text reaches the provider is explained under "Text check through my AI subscriptions". I store the report of this page check (checked addresses, findings, quoted text) at the hosting provider in Frankfurt so I can go through it with you in a booked call. Before storing it, I replace e-mail addresses, phone numbers and IBANs in quoted text with placeholders. It contains no data about you as a visitor, and I delete it after 90 days. If you book a call, the report number is in your booking.

If you enter your e-mail address, I receive an e-mail through my e-mail delivery service with your address, the checked website, the chosen language and the result you saw (score, findings, analysis). I use the address to send you concrete improvements for your website and to follow up on your reply. The website also stores your e-mail address, the checked website, the language, the time and the status in my database at the database provider in Frankfurt, with the random visitor and session ids if the visitor analytics is on for you. I keep the entry until you ask me to delete it. No newsletter, no sharing.

Website check in AI assistants

The website check is also available as an app for AI assistants and as an MCP server for other AI assistants. When an assistant calls it, I receive the address to check and the chosen language. I do not receive your conversation. What the assistant itself does with your input is governed by its provider's terms and privacy policy. The check itself runs through my own service providers, as described below.

The fast check fetches the page, its robots.txt and up to 30 addresses linked from it. The full check reads up to 20 pages of the website and fetches up to 30 internal links. The home page address goes to the website performance analysis service, and the text of the pages (at most 700 words per page) goes to the AI model provider to find spelling, translation and date errors, as long as the daily limit for this is not reached. Before that, I replace e-mail addresses, phone numbers and IBANs in the text with placeholders, and the text takes the same route to the provider as in the website check on this site (see "Text check through my AI subscriptions"). Pages that the website's robots.txt closes to my checking crawler are not fetched.

I store the results of both checks (checked addresses, findings, quoted text) at the hosting provider in Frankfurt and delete them after 90 days. Before that, I replace e-mail addresses, phone numbers and IBANs in quoted text with placeholders.

To limit how many checks one person can run, I store a hash, made with a secret key, of the anonymous user number the assistant's app platform sends for this purpose, or, for other calls, such a hash of your IP address. I delete these hashes within 3 days. None of it is used for advertising.

Text check through my AI subscriptions

Until 29 October 2026 the text check of the website check, including the app for AI assistants, could run through one of my own subscriptions with the AI model provider instead of the provider's API. In that case the already masked page text, together with the fixed check instructions, sat for at most 15 minutes in a queue at a database provider (Frankfurt region), and a program on my computer in Switzerland sent it to the provider. I have ended this route. Since then the text check runs only through the API.

For the checks through this route, the AI model provider's consumer terms and privacy policy applied. The provider's company based in Ireland processed the text as an independent controller, not on my behalf. In each of these accounts, use for training AI models is switched off. According to the provider, the data is then not used for training and is deleted after 30 days. Content that the provider flags for a possible policy violation is kept for up to 2 years and may be used to train its safety models. The provider processes the data in the USA and other countries and bases the transfer there on standard contractual clauses. I will tell you which provider this is on request to hello@seelig.ai.

During the test both routes ran side by side, and you got the result from the API. For the comparison I stored the findings of both routes (page address, quoted text, error and fix) and the duration at the database provider in Frankfurt, with the time rounded to the hour. They contain no data about you as a visitor. They are deleted within 14 days of being stored, so by 12 November 2026.

Abuse protection

To prevent abuse, I limit the number of requests per IP address: contact form 3, order form 5, website check 5, page check 5, AI search in the website check 3, e-mail unlock 5, chat 20 and error reports from the browser 10 per hour. For this, the IP address is held only in the server's working memory. It is not stored in a database or in logs and is discarded when the server instance restarts. The chat also has a daily limit per IP address. For this, I store a hash of your IP address, made with a secret key, and delete it within 3 days. The confirmations of receipt from the contact form and the order form, call and order requests from AI assistants and the website check in AI assistants have their own limits based on hashes, see "Contact form and e-mail", "Order and quote form", "Booking a call" and "Website check in AI assistants".

Music page

The "Spotify" page linked in the footer shows album and artist images that your browser loads directly from the servers of the music streaming service whose tracks it shows. The service receives your IP address, browser details and the information that the request comes from www.seelig.ai. Links to tracks and artists lead to that service, where its privacy policy applies.

Recipients and transfers abroad

These kinds of service providers receive personal data. For the USA, Swiss law treats protection as adequate only for companies certified under the Swiss-U.S. Data Privacy Framework. For the others, the transfer relies on standard contractual clauses, as stated for each recipient. On request to hello@seelig.ai, I will tell you which provider is behind a category and send you a copy of the standard contractual clauses.

I do not share your data for advertising and I do not sell it.

  • Hosting provider, USA: hosting, server functions, logs, storage of the chat questions, the page check reports, call and order requests from AI assistants and the hashes of booked booking ids (Frankfurt region). Certified under the Swiss-U.S. Data Privacy Framework.
  • E-mail delivery service, USA: sending the contact form, order, website check and confirmation e-mails with their PDFs and the error notifications to me. Standard contractual clauses with the Swiss adaptations.
  • AI model provider, contracting company based in Ireland: chat replies and their topic assignment, the website check analysis, the text check of the subpages and the AI search (a query with web search). Data is stored in the USA, and processing can also run in other countries. Standard contractual clauses with a Swiss addendum. According to the provider, inputs and outputs are not used for training and are deleted within 30 days. If the provider flags content for a possible policy violation, it keeps it for up to 2 years.
  • The same AI model provider, company based in Ireland, as an independent controller: the text check through my AI subscriptions until 29 October 2026 under its consumer terms, see "Text check through my AI subscriptions". Processing in the USA and other countries, standard contractual clauses.
  • Database provider based in Singapore: the comparison data of the ended text check through my AI subscriptions until it is deleted on 12 November 2026, and the database and storage for the website analysis and for the inquiries from the contact form and the website check, the orders and quote requests, the booked first calls and the confirmed call requests from AI assistants (Frankfurt region). Standard contractual clauses with a Swiss addendum.
  • Booking service, USA: booking and video calls. Not certified under the Swiss-U.S. Data Privacy Framework. According to the provider, the transfer relies on standard contractual clauses.
  • Website performance analysis service, companies in the USA and Ireland: measurements for the website check. The US company is certified under the Swiss-U.S. Data Privacy Framework.
  • Infrastructure provider, USA: receiving and forwarding e-mails to hello@seelig.ai, the load time measurement (stored in the EU) and receiving the analytics data. Certified under the Swiss-U.S. Data Privacy Framework, plus standard contractual clauses.
  • E-mail provider, USA: my mailbox. Certified under the Swiss-U.S. Data Privacy Framework.
  • Music streaming service, Sweden: images on the music page. Sweden has adequate data protection.

Retention

I keep personal data only as long as the purpose requires or the law demands. I delete the page check report and the results of the website check in AI assistants after 90 days, and the hashes used for limiting it within 3 days. I delete jobs of the text check through my AI subscriptions within 15 minutes and the comparison data after 14 days. Stored chat questions, answers and ratings are deleted after 12 months. I delete session recordings after 90 days, and marked recordings and click and page data of the analysis after 13 months. I delete the records of order requests from AI assistants at the hosting provider within 4 days, those of call requests from AI assistants within 30 days and the hashes used for limiting within 3 days, as well as the hashes used for limiting the confirmations of receipt and the details kept against duplicate orders. I keep e-mails from the contact form and the website check, and bookings, as long as your inquiry and any work together require. I keep the database entries of inquiries from the contact form and the website check, of orders and quote requests, of booked first calls and of confirmed call requests from AI assistants until you ask me to delete them. An e-mail to hello@seelig.ai is enough. I keep orders that become a contract as a PDF, with the e-mails about them and the invoices, for 10 years as business records (Art. 958f CO), and the PDFs and e-mails of other orders and quotes as long as I need them for your inquiry. I keep error notifications as long as I need them to fix the error. I delete load time measurements after 90 days.

Your rights

You can ask me at any time which personal data I process about you. You can also ask for a copy of your data in a common format, for incorrect data to be corrected and for your data to be deleted, and you can object to the processing. Write to hello@seelig.ai. I may ask you to confirm your identity.

If you believe I do not process your data correctly, you can contact the Swiss Federal Data Protection and Information Commissioner (FDPIC, www.edoeb.admin.ch).

Visitors from the EU

Where the EU General Data Protection Regulation (GDPR) applies to you, I base the processing on steps prior to entering into a contract (Art. 6(1)(b) GDPR) for inquiries through the form, by e-mail or through a booking, on the contract (Art. 6(1)(b) GDPR) for orders through the order form, on a legal obligation (Art. 6(1)(c) GDPR) for keeping business records, and on my legitimate interest in a working and secure website (Art. 6(1)(f) GDPR) for hosting, security, load time measurement, chat and the website check, and on your consent (Art. 6(1)(a) GDPR) for analysing how the website is used. You also have the right to restrict processing and to lodge a complaint with the data protection authority of your country of residence.

Changes

I update this notice when the website or the services it uses change. The version published on this page applies.