Privacy Policy
This Privacy Policy explains how CookiesForAI processes personal data when you visit cookiesforai.app, use its read-only MCP endpoint or data files, or email us. It is information provided under the EU General Data Protection Regulation (GDPR) and the German TDDDG. It is not a contract and you do not "accept" it. The separate Terms explain the rules for using the site, its content, the data files and the MCP endpoint.
At a glance
- CookiesForAI has no user accounts or advertising. Its only form is the contact form (section 9).
- We set no cookies. The
themesetting and your analytics choice can stay in your browser's local storage, and after you choose Accept, a random visitor number does too. - Browser analytics loads from our own domain and sends events only after you choose Accept: pages you open, time spent on a page, clicks, where you came from, your country, heatmaps and a session replay with everything you type masked (section 8).
- Vercel processes the technical request data needed to deliver and protect the site, including the contact form. We can read request logs for one day. Cloudflare delivers the logos of listed products from
img.cookiesforai.app. We have not switched on R2 data access logs, so we do not receive those access logs. - Our server sends limited, IP-free events to PostHog's EU Cloud when a browser opens a page, a known AI or search-engine crawler visits, a reader arrives from an AI assistant, a request asks for a Markdown page, or software calls the MCP endpoint. These events cannot link two visits by a person, except that an MCP call from client software we do not know may carry that software's own name (section 6). Our PostHog plan keeps these events available for one year.
- If you email us or use the contact form, Google provides the mailbox and we keep the message until the enquiry is settled, unless law requires longer retention. Cloudflare forwards email sent to hello@cookiesforai.app to that mailbox, and Resend delivers contact-form messages to it (section 9).
- You can exercise your GDPR rights, including the right to object to processing based on legitimate interests, by emailing hello@cookiesforai.app.
Contents
- Controller and privacy contact
- Scope and sources of data
- Visiting the website and request logs
- Hosting and image delivery
- Server-side measurement of page visits and AI traffic
- MCP endpoint and data-file requests
- Analytics processing by PostHog
- Browser analytics with your consent
- Email and the contact form
- Theme preference in local storage
- External links
- Recipients and international transfers
- Retention
- Legal bases and provision of data
- Your data-protection rights
- Right to object
- Complaints to a supervisory authority
- Automated decisions, profiling and changes
1. Controller and privacy contact
The controller responsible for the processing of personal data described in this Policy is the sole trader who runs CookiesForAI. The controller's full name and postal address are in our Impressum, linked at the foot of every page.
Email: hello@cookiesforai.app
You may direct questions about this Policy or requests concerning your personal data to the email address above.
2. Scope and sources of data
This Policy applies to cookiesforai.app, including requests to the read-only MCP endpoint at /api/mcp, requests for files under /data, and messages you send us by email or through the contact form.
We receive data directly from you when you email us or use the contact form. Technical request data comes from the browser or other client software that connects to the site. The limited measurement events in sections 5 and 6 are generated on our server from an incoming request. The browser events in section 8 are generated in your browser after you consent. We do not combine this data with information from other sources.
Makers of listed apps and brands (Art. 14 GDPR). Our Apps pages name the maker of each listed product as the maker shows itself in public: on its website, its App Store or Google Play page, or its legal notice. Where a maker is a person, that public name is personal data. We take it, together with facts about the product, from those publicly accessible pages, and we save a copy of each page we used so we can show where a fact comes from. We also ask the Internet Archive to keep a public copy of the page address. We never publish a maker's address, email address, phone number or photo. Purpose: a directory of independent products whose every fact can be traced to its source. Legal basis: Art. 6 (1)(f) GDPR, our legitimate interest and the public's interest in finding independent products with checked facts. Because we add products from public pages without contacting each maker, we give this notice here (Art. 14 (5)(b) GDPR). A maker can object at any time (section 16) or ask us to correct or remove a page at the address in section 1.
CookiesForAI does not provide accounts, and its only form is the contact form in section 9. We do not use visitor data for advertising, build profiles of visitors, or try to identify a person from the limited events described in sections 5 and 6.
3. Visiting the website and request logs
When a browser or other client requests a page or file, technical data must be processed so that the request can reach the server and the requested material can be returned. The same data helps keep the site stable and secure and allows attacks to be detected and addressed.
| Data | Purpose | Legal basis | Retention |
|---|---|---|---|
| IP address, date and time, requested page or file, status code, user agent and referrer | Delivering the requested material, maintaining stability and security, and defending against attacks | Art. 6 (1)(f) GDPR: our legitimate interest in operating a working and secure website | We can read request logs for one day |
We do not use these request logs to build visitor profiles or for advertising. A request cannot be delivered over the internet without processing the connection and request data needed for that delivery.
The logos of listed products are requested from img.cookiesforai.app and processed as described in section 4.
4. Hosting and image delivery
This site is hosted by Vercel Inc., 440 N Barranca Avenue #4133, Covina, CA 91723, United States. Vercel delivers our pages and files and, for that purpose, processes the request data described in section 3 on our behalf under a data processing agreement in accordance with Art. 28 GDPR.
Vercel serves requests from data centres close to the visitor and may process the data in the United States. Vercel Inc. is certified under the EU-U.S. Data Privacy Framework, which the European Commission has recognised as providing an adequate level of protection under Art. 45 GDPR. Our agreement with Vercel also includes the EU standard contractual clauses under Art. 46 GDPR.
Cloudflare, Inc., 101 Townsend St., San Francisco, California 94107, United States, delivers the logos of listed products from img.cookiesforai.app. For that purpose, Cloudflare processes IP addresses, traffic routing data and system configuration information. We have not switched on R2 data access logs, so we do not receive those access logs.
Cloudflare processes this data on our behalf under its Customer Data Processing Addendum, incorporated into the self-serve agreement we accepted, in accordance with Art. 28 GDPR. Cloudflare may process the data in the United States. Cloudflare, Inc. is certified under the EU-U.S. Data Privacy Framework. Its Data Processing Addendum, version 6.4, includes the EU standard contractual clauses, Module Two (controller to processor), under Art. 46 GDPR.
5. Server-side measurement of page visits and AI traffic
CookiesForAI exists to explain how AI systems find, read and cite information about agent skills, MCP servers and coding tools. To understand that activity, our server records an event in four limited situations: when a browser opens a page, when a request comes from a known AI or search-engine crawler, when a reader arrives through a link in an AI assistant's answer, and when a request asks for the Markdown version of a page.
When a browser opens a page, whether or not you answered the banner, the human_pageview event contains only:
- the time of the request;
- the page requested;
- the website you came from, reduced to its host name only, such as
www.google.com, or nothing when you typed the address or came from another page of this site; - two fixed words your browser sends with every page request about how the page was opened: whether it came from another website, this site or no website at all (
Sec-Fetch-Site), and whether a click or key press opened it (Sec-Fetch-User); and - whether you arrived through a link in an AI assistant's answer.
We decide that a request is a person's page load from the request itself: a request for a whole page whose user agent looks like a browser and names no crawler or script. The user agent is read for that check and then discarded; it is not recorded. The event is counted on our server while the page is delivered: no code runs in your browser for it, nothing is read from or stored on your device, and it receives a random number used only once, so two page views can never be linked to each other or to a person. Pages you open by following a link inside the site are often loaded without a new page request and are then not counted here, and software that imitates a browser may be counted. We add these events up per page and day as page views and visits; a visit is a page view opened from another website or from no website at all.
For a known AI or search-engine crawler, the event contains only:
- the time of the request;
- the crawler's name;
- the company that runs it;
- the page requested; and
- for the names
ChatGPT-User,Claude-UserandPerplexity-User, whether the request came from an address on the list the company publishes for that name, or that it could not be checked because the request had no address or the list could not be read.
To make that check, our server compares the request's IP address with the published list in memory while delivering the page and then discards it; the address is not recorded and not sent to PostHog. Software on a person's own computer can send these names (Claude Code sends Claude-User), so the check can briefly touch a person's IP address.
For a visit from an AI assistant, the event contains only:
- the time of the request;
- the assistant's website, reduced to the host name only, such as
chatgpt.com, or theutm_sourcevalue added by the assistant, reduced to the assistant's name; and - the page requested.
Crawler and AI-assistant events contain no IP address, full referrer address, query string or cookie. A visit from an AI assistant receives a random number that is used only once, so it cannot be used to link two visits by a person. Crawler events are grouped under the crawler's name. When the requested address contains our own test tag c4a_probe, the page view, crawler or AI-assistant event also carries a mark that it is one of our own test visits, so our counts leave it out; the tag's value is not recorded. Nothing is stored on the visitor's device. Our server sends the event to PostHog, described in section 7, while delivering the page.
Our server also records a markdown_fetch event when a request asks for the Markdown version of a page through an address ending in .md, a request asking for text/markdown, or the Copy page button. It contains the time, which of those three ways was used, and the page requested. If a known AI or search-engine crawler sent the request, it also contains the crawler's name and company, and for the names ChatGPT-User, Claude-User and Perplexity-User whether the request came from an address on the list the company publishes for that name, or that it could not be checked, as described above. When the requested address contains our own test tag c4a_probe, it also carries the mark that it is one of our own test visits. It records the first word of the user agent only when that word is on our list of known clients, for example mozilla or curl; otherwise it records "other" and never records the rest of the user agent. The event uses a random number once. It contains no IP address, referrer, query string or cookie, and nothing is stored on the device. Legal pages have no Markdown version.
The legal basis is Art. 6 (1)(f) GDPR. Our legitimate interest is understanding how AI systems and search engines read and cite this site and how many pages people open on it and from which websites they arrive. The processing is limited to what is needed for that purpose. In particular, no IP address or persistent identifier is kept, visits by a person cannot be connected, and no personal profile can be built. Our PostHog plan keeps these events available for one year. Your right to object is explained in section 16.
6. MCP endpoint and data-file requests
The read-only MCP endpoint at /api/mcp and the data files under /data answer requests from software such as AI agents. Each request is handled like the page and file requests described in section 3.
For each call to the MCP endpoint, our server also records an event, for at most ten calls in one request. A request the server rejects gives one event with its HTTP status. Each event contains:
- the time;
- the kind of call and the tool used;
- the name the client software gives for itself and the first word of its user agent, each recorded only when it is on our list of known clients and otherwise as "other"; no version number is recorded;
- when the client's name is not on that list, the name itself in lower case with spaces as dashes, but only when it is at most 40 characters of the letters a to z, digits, dots, dashes or underscores, begins with a letter or digit, contains a letter and has no run of five digits, so that we can add new client software to the list; any other name is recorded as "unreadable";
- whether the call came from our own monitoring; and
- the HTTP status of the answer and, if the call failed, the error code.
Search words and other input supplied by a client are used to produce the answer but are not stored by us. The answer is not recorded. The event contains no IP address. Apart from an unknown client's own name, recorded as above, which stays the same on every call from that software, its only identifier is a random number used once, so the number does not connect later calls or identify a person. Our server sends this event to PostHog as described in section 7.
The legal basis is Art. 6 (1)(f) GDPR. Our legitimate interest is understanding which tools and agents use the endpoint so that we can keep it working. The safeguards, PostHog processing, one-year availability and right to object are the same as in section 5, except that an unknown client's own name, recorded as above, is the same on every call from that software. Rules for use of the endpoint and data files appear in the Terms.
7. Analytics processing by PostHog
PostHog's browser script loads from our own domain only after you choose Accept, as described in section 8. Our server also sends PostHog the limited events described in sections 5 and 6, including Markdown requests, plus anonymous reports of server errors. Those reports contain the affected route and its type, the type of error, the request method and an error reference code, but never the error message, the address you requested or your request headers. Error reports contain no data about you.
PostHog, Inc., United States, processes those events on our behalf under a data processing agreement in accordance with Art. 28 GDPR. The events are processed on PostHog's EU Cloud in Frankfurt, Germany. PostHog and its sub-processors may access the data from the United States. That transfer is covered by the EU standard contractual clauses in the agreement under Art. 46 GDPR.
PostHog is configured to discard IP addresses. Our server forwards browser analytics requests to PostHog without your IP address or browser user agent. For browser events after consent, it adds only the two-letter code of the country that Vercel derives from the connection while delivering the request (section 8). The server-built events also contain no IP address.
8. Browser analytics with your consent
When you first visit, a banner asks whether we may count your visit. Until you choose Accept, no analytics code loads, nothing is stored for analytics and nothing is sent from your browser. The site works the same whether you accept, reject or do not choose. The page count in section 5 happens on our server either way and involves nothing in your browser.
If you accept, your browser loads PostHog's code from our own domain and sends the following events through our own domain (/ingest) to PostHog's EU Cloud, described in section 7:
| Event | When it is sent | Details of the event |
|---|---|---|
$pageview |
You open a page | None beyond the details listed below |
$pageleave |
You leave a page | The time spent on a page and how far you scrolled |
$autocapture |
You click something on a page | The element you clicked: its kind, its visible text, its place in the page and, for a link, its address without query string or fragment |
$rageclick, $dead_click |
You click the same spot several times quickly, or click something that does not respond | The same details as a click |
$$heatmap |
While you use a page | Where on the page you clicked and moved the pointer, used to draw heatmaps |
$snapshot |
While you use a page | Session replay: the page as it appeared to you, including its address as shown in your browser, and your pointer movements, scrolling and clicks, so we can watch how pages are used. Every form field and everything you type is masked in your browser and never sent. Console messages and network requests are not recorded |
outbound_click |
You follow a link to another website | The other website's host name and the page you were on |
install_copied |
You copy an install command or agent prompt | The kind, item and page you were on |
theme_toggle |
You choose light or dark appearance | The appearance you chose |
PostHog's code adds to each event: the browser name and version, operating system, device type and model, screen and window size, time zone, language, page address without its query string or fragment, page title and the site's host name; the website you came from, reduced to its origin, and the first page and referring website of your visit; and the campaign tags of the link that brought you (utm_source, utm_medium, utm_campaign, utm_content, utm_term), if it had any. Our server adds the two-letter code of your country, which Vercel derives from the connection while delivering the request; your IP address is not passed to PostHog. The event also carries random identifiers for the event, page view, session, browser tab, device and visitor. We do not use the events for advertising, create no person profiles and do not combine the events with other data.
The visitor identifier and current session are kept in your browser's local storage so that we can count returning visitors and visits that span several pages. While a tab is open, PostHog's code also keeps a copy of them, the tab's identifier, settings for the current visit and replay data not yet sent in that tab's session storage, which the browser deletes when you close the tab. They are random numbers and technical values that contain no name or contact details.
The event also says which PostHog library and version produced it, its distribution channel, whether it uses a custom host, and some of its settings: its configuration defaults, session timeout, recording status, remaining rate-limit tokens, retry-queue size, how it was initialised and how long that took. It includes the event time and initialisation time, flags saying not to look up a location or create a person profile and that the visitor is not identified, and our project token. The token identifies our PostHog project, not you. To show session replays and heatmaps, PostHog's code also loads its recording script and our project's replay settings through our own domain.
Before an event leaves your browser, we remove the IP address field and full user-agent string, personal properties, advertising click identifiers such as gclid or fbclid, and search words, and ask PostHog not to look up a location. Our server then forwards the request without your IP address or browser user agent. PostHog is configured to discard IP addresses. Surveys and feature flags are off.
The legal basis for reading device details such as screen size and language, for storing the visitor identifier and for recording the session is your consent under § 25 (1) TDDDG. The legal basis for processing the events is your consent under Art. 6 (1)(a) GDPR. You can withdraw your consent at any time with future effect under Art. 7 (3) GDPR by choosing Privacy settings at the bottom of any page, then Reject. Reject stops the analytics code and deletes the values PostHog stored in your browser. Withdrawal does not affect processing before it.
The following information is stored in your browser. We keep no copy of your choice on our server. If your browser blocks local storage, the analytics code does not start, so it never falls back to a cookie.
| Name | Storage | Set by | Purpose | How long |
|---|---|---|---|---|
c4a-analytics-consent |
Local storage | CookiesForAI | Remembers whether you chose Accept or Reject and when, so the banner follows your choice. Strictly necessary under § 25 (2) no. 2 TDDDG | Until you remove it through your browser settings |
ph_<project key>_posthog |
Local storage | PostHog's code, only after Accept | The random visitor identifier, the current session and PostHog's settings | Until you choose Reject or remove it through your browser settings |
Values starting with ph_<project key>_ or ph_replay_ |
Session storage | PostHog's code, only after Accept | A copy of the identifiers above, the tab's identifier, settings for the current visit and replay data not yet sent | Until you close the tab or choose Reject |
theme |
Local storage | CookiesForAI | Your light or dark appearance, see section 10 | Until you remove it through your browser settings |
Our PostHog plan keeps these events available for one year and session replays for 30 days.
9. Email and the contact form
If you email us, we process your email address and whatever you write or attach. We use that information to read, manage and answer your enquiry.
The legal basis is Art. 6 (1)(f) GDPR, reflecting our legitimate interest in answering enquiries. Art. 6 (1)(b) GDPR also applies where your message asks us to take steps concerning a contract or is about a contract with you.
Our mailbox is provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Your message is stored there. Google may process it on servers outside the European Union, including in the United States, where Google LLC is certified under the EU-U.S. Data Privacy Framework.
We keep the correspondence until the enquiry is settled. We keep it longer only where a legal retention duty applies.
Contact form and hello@cookiesforai.app
Using the form on our contact page is voluntary. We process your name, email address, subject and message to answer you. All four fields are needed to send the form; the name can be a nickname. The message reaches the mailbox above, and the legal bases are the same as for email. To protect the form against abuse, we also process the IP address of each form request for about ten minutes, based on Art. 6 (1)(f) GDPR, our legitimate interest in keeping the form free of abuse.
Resend (Plus Five Five, Inc., United States) delivers these messages for us as our processor under Art. 28 GDPR and processes them in the United States. Resend is certified under the EU-U.S. Data Privacy Framework, and its Data Processing Addendum also includes the EU standard contractual clauses under Art. 46 GDPR. Resend keeps contact-form data for 30 days.
Email sent to hello@cookiesforai.app is forwarded to the same mailbox by Cloudflare, Inc. (section 4), as our processor under the Customer Data Processing Addendum described there. Cloudflare keeps a record of each forwarded email, such as the sender, time and status, for 31 days.
10. Theme preference in local storage
We set no cookies. If you accept browser analytics, PostHog may briefly read cookies to check its settings, but we do not keep analytics values in cookies. If you use the switch between light and dark appearance, your browser stores that choice in local storage under the name theme, with the value light or dark.
The value is stored only after you use the switch. It never leaves your device and does not identify anyone. The storage is strictly necessary to provide the appearance setting that you asked for, so consent is not required under § 25 (2) no. 2 TDDDG. You can remove the value at any time through your browser settings. Removing it resets the preference.
11. External links
Our pages link to third-party websites, repositories and documentation for the skills, servers and tools we list. Reading a CookiesForAI page does not send data to those linked sites. If you choose a link, your browser contacts the other site and that operator's privacy information and rules apply.
12. Recipients and international transfers
We disclose personal data only to the service providers needed for the activities described in this Policy, or where a law obliges us to disclose it.
| Recipient | Role and reason | Location and transfer safeguard |
|---|---|---|
| Vercel Inc. | Processor for hosting, delivery, request logs, stability and security, including the contact form | May process in the United States; EU-U.S. Data Privacy Framework and EU standard contractual clauses |
| Plus Five Five, Inc. (Resend) | Processor for delivering contact-form messages to our mailbox | Processes in the United States; EU-U.S. Data Privacy Framework and EU standard contractual clauses |
| Cloudflare, Inc. | Processor for delivering the logos of listed products from img.cookiesforai.app and forwarding email sent to hello@cookiesforai.app |
May process in the United States; EU-U.S. Data Privacy Framework and EU standard contractual clauses |
| PostHog, Inc. | Processor for the limited server-side events in sections 5 and 6 and browser events after consent | EU Cloud in Frankfurt; possible access from the United States under EU standard contractual clauses |
| Google Ireland Limited and Google LLC | Mailbox service for email and contact-form messages | Google may process in the United States; Google LLC is certified under the EU-U.S. Data Privacy Framework |
An adequacy decision under Art. 45 GDPR means the European Commission has recognised the relevant framework as providing an adequate level of data protection. Standard contractual clauses under Art. 46 GDPR are contractual safeguards approved by the European Commission for transfers that are not based on an adequacy decision.
Transfers rely on the EU-U.S. Data Privacy Framework adequacy decision or EU standard contractual clauses, as shown in the table. You can ask us for a copy of the clauses we have agreed with Vercel, Cloudflare, PostHog and Resend.
Apart from the providers named above, we pass personal data to nobody unless a law requires us to do so.
13. Retention
We keep personal data only for the period connected to its stated purpose or for a longer period where law requires it.
| Information | Retention |
|---|---|
| Request logs available to us | One day |
R2 data access logs for logos requested from img.cookiesforai.app |
Not switched on, so we do not receive these logs |
| Page-view, AI-crawler, AI-assistant referral, Markdown-request and MCP events | Our PostHog plan keeps these events available for one year |
| Browser events sent after consent | Our PostHog plan keeps these events available for one year |
| Session replays recorded after consent | 30 days |
| Maker name and product facts on an Apps page, and our saved copies of the pages we used | While the product is listed; saved copies up to three years after removal, to answer complaints about a fact we published |
| Email correspondence, including contact-form messages | Until the enquiry is settled, longer only where a legal retention duty applies |
| Contact-form data at Resend | 30 days |
| IP address used to protect the contact form against abuse | About ten minutes |
| Cloudflare's record of each email forwarded from hello@cookiesforai.app, such as sender, time and status | 31 days |
c4a-analytics-consent local-storage value |
On your device until you remove it through your browser settings |
ph_<project key>_posthog local-storage value, after Accept |
On your device until you choose Reject or remove it through your browser settings |
| PostHog session-storage values, after Accept | Until you close the tab or choose Reject |
theme local-storage value |
On your device until you remove it through your browser settings |
When another stated period ends, the relevant information is deleted or ceases to be available to us, subject to any legal duty that requires continued storage.
14. Legal bases and provision of data
The processing described in this Policy uses the following legal bases:
- Art. 6 (1)(f) GDPR, legitimate interests: operating a stable and secure website; understanding, in a privacy-preserving way, how AI systems and search engines read and cite it, how many pages people open and from which websites they arrive, and how software uses the MCP endpoint; and answering enquiries.
- Art. 6 (1)(f) GDPR, legitimate interests: listing products by independent makers with the maker's public name and facts taken from public pages, and keeping copies of those pages as proof.
- Art. 6 (1)(b) GDPR, contract-related steps: handling an email where the enquiry concerns a contract or steps requested before a contract.
- Art. 6 (1)(a) GDPR and § 25 (1) TDDDG, consent: browser analytics after you choose Accept.
- § 25 (2) no. 2 TDDDG: storing the
themevalue locally after you request the light or dark appearance function. - § 25 (2) no. 2 TDDDG: storing your analytics choice so the site follows it.
You are not legally or contractually required to provide personal data merely to read the site. Technical request data is, however, necessary to transmit a requested page or file across the internet. If you contact us, we need enough information in your message to understand and answer it. You do not have to provide information that is unrelated to your enquiry.
15. Your data-protection rights
Subject to the requirements and limits in the GDPR, you have the right to:
- obtain confirmation of whether we process personal data concerning you and access that data under Art. 15 GDPR;
- have inaccurate data corrected and incomplete data completed under Art. 16 GDPR;
- have data erased under Art. 17 GDPR;
- restrict processing under Art. 18 GDPR;
- receive data in a portable format under Art. 20 GDPR where processing is automated and based on consent or a contract;
- withdraw consent at any time with future effect under Art. 7 (3) GDPR through Privacy settings, then Reject, without affecting earlier processing; and
- object to processing based on Art. 6 (1)(f) GDPR under Art. 21 GDPR, as explained in section 16.
To exercise a right, email hello@cookiesforai.app. Please identify the request or correspondence concerned so that we can locate relevant information without collecting unnecessary additional data. We may need to ask for information sufficient to verify that the request concerns you.
The events described in sections 5 and 6 contain no IP address or lasting personal identifier, apart from an unknown MCP client's own name described in section 6, which normally names software, not a person. The events in section 8 contain no IP address; they carry the random visitor identifier stored in your browser, which we cannot connect to your name. This may mean that we cannot connect an event to you. We are not required to collect additional identifying information solely to identify a person for a rights request, subject to Art. 11 GDPR.
16. Right to object
You may object at any time, on grounds relating to your particular situation, to processing based on Art. 6 (1)(f) GDPR. This right follows from Art. 21 GDPR.
If you object, we will stop the relevant processing unless we demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing is needed for the establishment, exercise or defence of legal claims.
Send an objection to hello@cookiesforai.app and describe the processing to which you object. Because we do not use personal data for direct marketing, there is no direct-marketing processing to opt out of.
17. Complaints to a supervisory authority
You have the right under Art. 77 GDPR to complain to a data protection supervisory authority, in particular in the EU Member State where you live, where you work, or where you believe an infringement occurred.
You may contact us first, but you do not have to do so before making a complaint.
18. Automated decisions, profiling and changes
We do not make decisions about you based solely on automated processing and do not profile you within the meaning of Art. 22 GDPR.
The "Updated" date at the top identifies the current version.