Privacy Policy
Last updated: November 2026
This policy explains which personal data MCANISM Technology GmbH processes, why it does so and what rights you have. It covers our website www.mcanism.com, our platform Skynet (skynet.mcanism.com), our Support Center (supportcenter.mcanism.com), our AI assistant Marvin and our tracking links (api.skynet.mcanism.com). For hotelcampaign.de and chefscampaign.com, the privacy policies on those sites apply.
1. Which sections matter to you
- A visitor to our website: Section 5
- A publisher or advertiser with a Skynet account, or named there as a contact person: Sections 6, 8, 9 and 10
- An internet user who clicked an advertising link or saw an ad: Section 7
- A user of the Support Center or Marvin: Sections 8 and 9
- A job applicant: Section 11
- A visitor to our social media profiles: Section 12
Sections 2 to 4 and the overviews in sections 13 and 14 apply to everyone.
2. Controller and contact
MCANISM Technology GmbH
Cremon 11
20457 Hamburg
Germany
Represented by: Gunnar Militz
Phone: +49 40 29857160
Email for privacy requests: privacy@mcanism.com
3. Your rights
You have the right to:
- access your data and receive a copy (Art. 15 GDPR),
- rectification of inaccurate data (Art. 16 GDPR),
- erasure (Art. 17 GDPR), unless a retention duty applies,
- restriction of processing (Art. 18 GDPR),
- data portability (Art. 20 GDPR),
- withdraw any consent with effect for the future (Art. 7(3) GDPR).
Right to object (Art. 21 GDPR): Where we rely on legitimate interests, you can object at any time on grounds relating to your particular situation. You can object to direct marketing without giving a reason.
For any request, an email to the address in section 2 is enough. If you have a Skynet account, you can also request a copy of your data yourself under Settings → Privacy. We then email you a download link. For tracking we usually do not know your name. To help us find your data, please give us the value of the cookie described in section 7.4 or the order concerned.
You can also complain to a supervisory authority. Ours is: Der Hamburgische Beauftragte für Datenschutz und Informationsfreiheit, Ludwig-Erhard-Str. 22, 20459 Hamburg, Germany, datenschutz-hamburg.de.
4. General principles
Legal bases. We name the legal basis for each processing activity. These are Art. 6(1) GDPR with point (a) (consent), point (b) (contract or pre-contractual steps), point (c) (legal obligation) and point (f) (legitimate interests). Storing and reading information on your device is also governed by § 25 of the German TDDDG: it requires your consent unless it is strictly necessary for a service you requested.
Whether you must provide data. You have no legal duty to give us data. Without the fields marked as mandatory in the sign-up form, however, we cannot create an account, and without a bank account or PayPal account and tax details we cannot make payouts.
Recipients. Service providers working on our behalf are bound by contract under Art. 28 GDPR. Section 14 lists all recipients. We do not sell data.
Transfers to third countries. Some providers are based in the USA or use sub-processors there. We base these transfers on the European Commission's adequacy decision for the EU-US Data Privacy Framework, Implementing Decision (EU) 2023/1795, where the recipient is certified, and additionally on the EU Standard Contractual Clauses, Implementing Decision (EU) 2021/914. You can request a copy of the clauses.
Security. We encrypt data in transit and limit access to staff who need it for their work.
Retention. Section 13 gives the specific periods.
5. Our website www.mcanism.com
5.1 Delivery and security
We run the website on Webflow, Inc. (USA). Delivery and protection against attacks run through Cloudflare, Inc. (USA). When you visit, your IP address, date and time, the page requested, the previous page, and your browser and operating system are processed. The legal basis is Art. 6(1)(f) GDPR. Our interest is a secure and stable website. Cloudflare's _cfuvid cookie distinguishes visitors to protect against overload and expires at the end of the session. It is strictly necessary for this purpose (§ 25(2) no. 2 TDDDG).
5.2 Cookie settings
On your first visit we ask for your consent. We store your choice for 180 days in the cookies fs-cc and fs-cc-updated. You can change or withdraw it at any time through the "Cookies Settings" link in the footer. The services in section 5.4 only run if you have consented.
5.3 Contact form and spam protection
When you write to us, we process your details to answer your request. The legal basis is Art. 6(1)(b) GDPR where a contract is concerned, otherwise point (f); our interest is handling enquiries. Webflow stores the form data for us. From there it reaches our mailbox at Google Workspace by email.
To protect against automated submissions we use Cloudflare Turnstile and Google reCAPTCHA. This checks your IP address and details about your browser and usage. Google acts as our processor for reCAPTCHA. Cloudflare acts as our processor for Turnstile and is an independent controller for improving detection.
5.4 Services that need your consent
The legal basis for the following services is your consent (§ 25(1) TDDDG, Art. 6(1)(a) GDPR).
Google Tag Manager from Google Ireland Limited loads the other services. It is also loaded only after your consent.
Google Analytics 4 shows us how our website is used. Google acts as our processor. It processes approximate location, pages visited, device and browser details and a pseudonymous identifier. The _ga and _ga_* cookies expire after 400 days, and Google deletes event data after 2 months.
Google Ads measures whether our ads lead to enquiries. Google acts as an independent controller here. The _gcl_au cookie expires after 90 days.
Webmetic from Webmetic GmbH, Grünwalder Weg 32, 82041 Oberhaching, Germany, shows us which companies our visitors come from. It processes your IP address, device details and pages visited. Webmetic acts as our processor and is an independent controller for its own company database.
5.5 Fonts and libraries
The website loads fonts from Google Fonts and scripts through jsDelivr, cdnjs, ajax.googleapis.com and Amazon CloudFront. Your browser fetches these files directly from the providers, who receive your IP address in the process. The legal basis is Art. 6(1)(f) GDPR. Our interest is a fast and consistent display of the website.
6. Skynet for publishers and advertisers
6.1 Account and contract
For sign-up and the contract we process, for you and your contact persons: email address, first and last name, phone number, language, password (as a hash only), company, address, website, VAT ID, billing email addresses, ad spaces, campaigns and settings. For publishers we also process account holder, IBAN, BIC, bank address and payout threshold, and for payouts through PayPal the data of the connected PayPal account (section 6.6). Our team can add internal notes to an account and assign account managers.
The legal basis is Art. 6(1)(b) GDPR, and point (c) for tax details. If you are a contact person rather than the contracting party, the legal basis is point (f). Our interest is performing the contract with your company.
At sign-up we use Google reCAPTCHA against automated registrations (Art. 6(1)(f) GDPR). Google acts as our processor.
6.2 Cookies and local storage
skynet-refresh– Purpose: Keeps you logged in, not readable by scripts; Lifetime: 72 hoursskynet-refresh-admin– Purpose: Only for our team during "Login as"; Lifetime: Until "Login as" ends, at most 72 hoursskynet_analytics_consent– Purpose: Stores your choice on Google Analytics; Lifetime: 365 daystoken,refreshTokenand similar (local storage) – Purpose: Login; removed when you log out; Lifetime: Until logout- Language, filters, menu state, Marvin's tone (local storage) – Purpose: Your settings; Lifetime: Until you delete them
marvin.conversation, dashboard cache (session storage) – Purpose: Current chat, faster display; Lifetime: Until the tab is closed, dashboard at most 1 hour
These entries are strictly necessary for the service you use (§ 25(2) no. 2 TDDDG).
6.3 Usage analysis
With your consent we use Google Analytics through Google Tag Manager after login (§ 25(1) TDDDG, Art. 6(1)(a) GDPR). You decide in the banner and can change your choice at any time in the settings under "Privacy". If you decline, we remove the related cookies. There is no analysis on the login and sign-up pages.
6.4 Error diagnosis
To find errors we use Sentry from Functional Software, Inc. (USA). It receives technical error data, the page concerned, and browser and operating system details. We remove login tokens first and do not use session recordings. The legal basis is Art. 6(1)(f) GDPR. Our interest is error-free operation.
6.5 Invoicing and payouts
For invoices, credit notes and reminders we process your contract and payment data (Art. 6(1)(b) and (c) GDPR). Documents go by email to you and to our finance team, accounting data goes to DATEV and our tax advisers and, in an audit, to auditors and tax authorities.
Payouts to publishers are made by SEPA transfer through our bank. The bank receives account holder, IBAN, BIC, amount and document number.
6.6 Payouts through PayPal
Publishers can receive their payouts through PayPal instead of by SEPA transfer. To do so, publishers connect their PayPal account to their Skynet account. They are redirected to PayPal and consent there to PayPal sharing the following data with us: PayPal account ID (payer ID), name, email address and account verification status. We store this data in your Skynet account together with the time of verification. The connection can be removed at any time in the payout settings.
For each payout we send PayPal (Europe) S.à r.l. et Cie, S.C.A., 22-24 Boulevard Royal, L-2449 Luxembourg, this identifier, the amount, the currency and a reference with the document number. PayPal sends us the status of the payout, a transaction number and the fees incurred, which we book with the credit note.
The legal basis is Art. 6(1)(b) GDPR, and point (c) for the booking. We keep the data of the connected PayPal account for as long as the connection exists, after that like the other account data (section 13). We keep payout records for the statutory periods.
PayPal acts as an independent controller and transfers data within the PayPal group under binding corporate rules (Art. 47 GDPR). See PayPal's privacy statement.
6.7 Automated processes
These processes run automatically:
- Approval of transactions: If an advertiser does not review an open transaction within the period set for the campaign, it is accepted automatically.
- Declines by networks: If a connected partner network declines a transaction, we apply this automatically.
- Click limit: If a campaign exceeds the daily limit on an ad space, further clicks are no longer recorded.
- Commission amount: It follows from campaign rules such as country, device and price segment.
- Bot filter: Known crawlers are not recorded.
- Inactive accounts: We set accounts to "Sleeping" after 365 days without login, API use, revenue or meaningful traffic. You then receive fewer emails, your links keep working, and the account becomes active again at your next login.
In our assessment we make no solely automated decision with legal or similarly significant effect under Art. 22 GDPR. If you disagree with a result, write to us and a person will review the case. The legal basis is Art. 6(1)(b) GDPR, and point (f) for inactive accounts. Our interest there is keeping contact details current and avoiding unnecessary mail.
6.8 Logs and help from our team
We log changes to campaigns, accounts and finance data so they stay traceable. Bank details are masked in the log. For support, our team can log into your account with "Login as". The start time and the staff member's IP address are recorded. The legal basis is Art. 6(1)(f) GDPR. Our interest is security, traceability and helping with problems.
6.9 Export to Google Sheets
If you export a report to Google Sheets, you connect your Google account yourself. We store your Google email address and the access keys and only access the files created this way. The legal basis is Art. 6(1)(b) GDPR.
6.10 What other participants see
Advertisers see ad space names and performance data for their campaigns. Publishers see the performance data of their ad spaces. The legal basis is Art. 6(1)(b) GDPR.
7. Tracking of advertising links and ads
This section is addressed to internet users and fulfils our duties to inform under Art. 13 and 14 GDPR.
7.1 What this is about
MCANISM runs an affiliate network. Website operators (publishers) show advertising for companies (advertisers). If you buy or book after clicking such a link, the publisher receives a commission. For this to work, we need to know which link led to the purchase.
7.2 What data we process
- When you click or an ad is displayed: full IP address, the country and internet provider derived from it, date and time, requested address with parameters, referrer, browser, operating system, device type and the headers of the request.
- Identifiers: a random track ID, campaign and ad space identifiers and, if the publisher passes them, click IDs, sub-identifiers (ref1 to ref5, source IDs) and mobile advertising IDs (GAID, IDFA, WAID).
- When you buy or book: type of event, amount, currency, order number, shop identifier and optional reference fields of the advertiser, for hotels for example arrival and departure dates.
We do not receive buyers' names, addresses or payment details. The data is pseudonymous: we do not know your name, but we can link the identifiers to each other. It therefore remains personal data.
7.3 Where the data comes from
The data comes directly from your browser, from the publisher whose link you used and from the advertiser you bought from. Connected partner networks also report transactions to us.
7.4 Cookies
mca_<ad space identifier>– Set on: api.skynet.mcanism.com, on click or display; Purpose: Contains the track ID; Lifetime: Per campaign, 30 days by defaultmca_<campaign identifier>– Set on: The advertiser's website, only if it uses our script; Purpose: Contains the track ID so that the purchase can be attributed; Lifetime: Per campaign
With parallel tracking we set no cookie. The track ID then comes from the link.
7.5 Matching by IP address
For campaigns where this is enabled, a purchase without a track ID can be matched by IP address. The last click or display with the same IP address within the campaign period then counts.
7.6 Purposes and legal bases
We process the data to attribute purchases to the right link, calculate and settle commissions, prevent abuse and produce statistics for publishers and advertisers.
Cookies on the advertiser's website and for ad displays are stored and read with your consent (§ 25(1) TDDDG, Art. 6(1)(a) GDPR), which the operator of the website concerned obtains. This also applies to the cookie we set on a click during the redirect through api.skynet.mcanism.com: consent for it is obtained by the publisher on whose website the ad appears. We base the subsequent attribution, settlement and abuse checks on Art. 6(1)(f) GDPR. Our interest, and that of the other participants, is the correct payment for sales that were referred. For accounting records, Art. 6(1)(c) GDPR applies.
7.7 Responsibilities
Several companies take part in tracking. Each is responsible for its own part:
- The publisher is responsible for its website, for embedding the ads and for obtaining any required consent there.
- We are responsible for running the tracking technology, attribution, settlement and abuse checks.
- The advertiser is itself responsible for processing on its website and in its order process, including any consent required for our script there.
- You can exercise your rights regarding tracking with us. For a website, please contact its operator. We help where needed.
7.8 Who receives the data
- Advertisers see transactions in reports with track ID, country, device, browser and operating system, as well as click IDs, sub-identifiers and mobile advertising IDs. They do not see IP addresses in reports. When you visit their website, however, they receive your IP address directly from your browser.
- Publishers see performance data, device and browser and their own identifiers. On request we send them notifications (postbacks) with track ID, their identifiers, event type, amount and commission. They do not receive IP addresses.
- Partner networks (section 14) receive the track ID and ad space identifier through the redirect for their campaigns.
- Our team sees IP addresses in internal reports only.
- Service providers: Google Cloud for operation, database and analysis.
If an advertiser or publisher adds placeholders to a target address, individual values can also be passed on this way. With the {ip} placeholder, this includes your IP address.
7.9 Retention
We delete raw data and failed events after 90 days. We delete tracking events after four years. If they are needed for a transaction or a later event, they are kept, but we remove the IP address, internet provider, advertising IDs and sub-identifiers. We keep transactions as the basis for settlement (section 13). For statistics we keep a copy of selected event data without IP addresses in Google BigQuery. We keep this copy as long as we need it to analyse how our network develops.
7.10 What you can do
Decline cookies in the banner of the website concerned, or delete or block cookies in your browser. This ends attribution through cookies. You can also object or request erasure at any time (section 3).
7.11 Inactive links
If a link is inactive or the click limit is reached, we redirect you to a page at mcanism.nuggies.de. That page is not part of Skynet, and its own privacy notice applies there.
8. Support Center
The guides in the Support Center can be used without logging in. The Support Center runs on servers of Hetzner Online GmbH in Germany. The script generator stores the campaign, integration type and the variable names you enter, so that we can provide your script and support the setup (Art. 6(1)(b) GDPR). When a script is created, our team receives a Slack message with the campaign and event.
We also send account emails through the Support Center, such as password links, invoices and credit notes. We use Brevo for this (section 10). Sending is logged with the email address and type of message. We delete this log after one year.
The Support Center loads Google Tag Manager as well as fonts and program files from Google servers (gstatic.com, fonts.gstatic.com). Google receives your IP address and details about your browser in the process. The legal basis is Art. 6(1)(f) GDPR. Our interest is a working display of the Support Center.
9. AI assistant Marvin
Marvin is an AI assistant, not a person. Answers are generated automatically and can be wrong. Please check important details. Please do not enter special categories of personal data, passwords or data about other people.
Knowledge questions. In the Support Center and in Skynet, Marvin answers general questions from our knowledge base. Your question goes to Google. If Marvin also searches the web, Google derives search queries from it. The legal basis is Art. 6(1)(f) GDPR. Our interest is fast support.
Questions about your account. In Skynet, once you have confirmed the notice, Marvin can read data from your account, including campaigns, transactions, performance data, documents and team members. Marvin does not write or change anything. The account owner can switch this off, and under "Marvin" in the settings you can see what was read. Email addresses, phone numbers, IP addresses and advertising IDs are blocked for Marvin. The legal basis is Art. 6(1)(b) GDPR.
Provider. Answers are generated by a language model from Google. Questions about your account, and the account data read to answer them, are processed by Google Cloud (Vertex AI) in the EU. General questions go to Google's Gemini API. Google makes no commitment on the processing location there, so a transfer to the USA is possible (see section 14). According to its terms Google does not use your input for training and acts as our processor. To detect abuse, Google temporarily stores input and output, up to 55 days for the Gemini API and up to 90 days for flagged prompts on Vertex AI.
What we store.
- Chat history in the browser (Skynet): Until you close the tab or log out
- Individual knowledge questions and answers, for ratings: 24 hours
- Knowledge chats you rated, with comment: 90 days after the last activity
- Account chats you rated: 30 days
- Log of tools used, without questions and answers: 30 days
- Audit log in Skynet: 180 days
- Unanswered questions, to improve the knowledge base: Until handled by our team
- IP address for rate limiting: At most 1 day
Access by our team. Our team reads questions and answers to improve Marvin. Selected chats appear in our internal Slack for this purpose: questions asked without logging in, with their answer, without IP address and with contact, bank and payment details redacted, and questions from logged-in users with account name and redacted details. MCANISM administrators can use Marvin across accounts for account management.
10. Emails
Contract emails. We send emails about your account, password, invoices and campaigns through Mailgun (Sinch, EU region) and Brevo (Brevo GmbH, Berlin). The legal basis is Art. 6(1)(b) GDPR.
Campaign information. We inform you by email about new campaigns, changes and offers. You can switch this off at any time in the notification settings in Skynet, and every email contains a link to them. The legal basis is Art. 6(1)(f) GDPR together with § 7(3) of the German UWG. Our interest is informing you about our cooperation.
Newsletter. Publishers and advertisers with a Skynet account receive our newsletter with news about MCANISM, Skynet and our campaigns. To make the content relevant, we use your name, email address, language, account type and the partner networks of your campaigns. Brevo sends it as our processor. We do not track whether you open an email or click links. You can unsubscribe at any time in Skynet under Settings → Notifications or through the link in every email. The legal basis is Art. 6(1)(f) GDPR in conjunction with § 7(3) UWG. Our interest is informing you about our cooperation.
Important information. Messages that are necessary for your account or contract, for example about changes to the terms, security or billing, are sent to all users regardless. The legal basis is Art. 6(1)(b) and (c) GDPR.
11. Job applications
We process your application to decide on an employment relationship. This covers your contact details, documents and any further details you choose to give. The legal basis is Art. 6(1)(b) GDPR. After the process ends we delete the documents after six months, unless you allow us to keep them longer or we hire you. The legal basis for this is Art. 6(1)(f) GDPR; our interest is defending against claims.
12. Social media
We maintain profiles on LinkedIn (LinkedIn Ireland Unlimited Company) and TikTok (TikTok Technology Limited, Ireland). When you visit them, the operators process your data under their own privacy notices, also for advertising and also in the USA. We are joint controllers with the operator concerned for the visitor statistics of our pages (Art. 26 GDPR). You can exercise your rights most effectively with the operator. The legal basis is Art. 6(1)(f) GDPR. Our interest is communicating with you.
13. Retention overview
- Tracking raw data, failed events: 90 days
- Tracking events: 4 years; after that only without IP address and identifiers, if needed for transactions
- Account and contract data: Contract term; after that we delete them on request, unless a retention obligation applies
- Data of the connected PayPal account: As long as the connection exists, after that like account and contract data
- Commercial books: 10 years (§ 147 AO, § 257 HGB)
- Accounting vouchers, invoices, credit notes: 8 years (§ 147 AO, § 257 HGB, § 14b UStG)
- Business letters: 6 years
- Campaign change log: 30 days
- Other logs, "Login as": 2 years
- Support Center email sending log: 1 year
- Marvin: See section 9
- Applications: 6 months after the process ends
- Cookies: See sections 5, 6.2 and 7.4
Periods for retention duties start at the end of the calendar year.
14. Recipients overview
- Google Cloud EMEA Limited, Ireland – Purpose: Hosting of Skynet, database, files, BigQuery (region europe-west1, Belgium); Location, transfer: EU; service data possibly USA: DPF and SCC
- Google Cloud EMEA Limited, Ireland – Purpose: Mailboxes at @mcanism.com (Google Workspace); Location, transfer: EU, possibly USA: DPF and SCC
- Google Ireland Limited, Ireland – Purpose: Analytics, Ads, Tag Manager, reCAPTCHA, Gemini; Location, transfer: EU, USA: DPF and SCC
- Netlify, Inc., USA – Purpose: Hosting of the Skynet interface; Location, transfer: USA: DPF and SCC
- Webflow, Inc., USA – Purpose: Website hosting, forms; Location, transfer: USA: DPF, SCC
- Cloudflare, Inc., USA – Purpose: Website protection and delivery; Location, transfer: USA: DPF, SCC
- Hetzner Online GmbH, Germany – Purpose: Hosting of Support Center and Marvin; Location, transfer: Germany
- Mailgun Technologies, Inc., USA (Sinch) – Purpose: Email delivery; Location, transfer: EU region; USA possible: DPF
- Brevo GmbH, Germany – Purpose: Email delivery; Location, transfer: EU
- Functional Software, Inc. (Sentry), USA – Purpose: Error diagnosis; Location, transfer: USA: DPF and SCC
- Slack Technologies Limited, Ireland – Purpose: Internal communication; Location, transfer: Ireland, USA: SCC
- Webmetic GmbH, Germany – Purpose: Company recognition; Location, transfer: EU
- DATEV eG, tax advisers, banks – Purpose: Accounting, payments; Location, transfer: Germany
- PayPal (Europe) S.à r.l. et Cie, S.C.A., Luxembourg – Purpose: Payouts; Location, transfer: Independent controller; BCR, SCC
- Advertisers, publishers – Purpose: Section 7.8; Location, transfer: Worldwide possible, depending on location
- Partner networks: Awin, CJ, Impact, Partnerize, Rakuten, TargetCircle, eBay – Purpose: Campaigns and transactions; Location, transfer: Partly outside the EU; adequacy decision, DPF or standard contractual clauses of the network concerned
We also pass data to authorities and courts where we are legally required to.
15. Changes
We update this policy when our services or the law change. The version published here applies.