Data Processing Agreement (DPA) under Art. 28 GDPR

As at 3 October 2026 – Version 2026-10-03

English translation. The German version prevails: Auftragsverarbeitungsvertrag.

This agreement forms part of the contract between the Client (the "Controller") and FAN/IP, a sole proprietorship (Einzelunternehmen) established in Cologne (owner and address in the imprint at https://fan-ip.com/legal.html), operator of the FAN/IP platform (the "Processor"), entered into on the basis of the FAN/IP General Terms and Conditions (the "Terms"). Terms defined in the Terms have the same meaning in this agreement. "GDPR" means Regulation (EU) 2016/679 and "BDSG" means the Bundesdatenschutzgesetz (German Federal Data Protection Act); the terms "personal data", "processing", "personal data breach" and "sub-processor" have the meaning given to them in the GDPR.

Article 1. Subject matter and roles

1.1. The Processor processes personal data on behalf of the Controller for the sole purpose of providing the Platform and the services set out in the contract.

1.2. The Controller determines the purposes and the essential means of the processing: it chooses the modules, the Program rules and the data requested from Members. The Controller ensures that there is a lawful basis for each processing operation and that data subjects are informed.

1.3. Shared login credentials. A single individual may use one set of login credentials (email address and password) to join the Programs of several FAN/IP clients. For the management of the shared login credentials (creation, authentication, security, deletion), FAN/IP acts as a separate controller; it therefore does not access the Client's Program data outside the scope of this agreement.

1.4. A detailed description of the processing is set out in Annex 1.

Article 2. Instructions

2.1. The Processor processes the data only on documented instructions from the Controller, including with regard to transfers outside the European Union, unless required to do so by Union or Member State law to which the Processor is subject; in that case, the Processor informs the Controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest (Article 28(3)(a) GDPR).

2.2. The contract, this DPA, the configuration of the Space and the actions taken by Users in the administration interface constitute the Controller's instructions. Any additional instruction is given in text form (Textform).

2.3. The Processor informs the Controller without undue delay if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions.

Article 3. Confidentiality

The Processor ensures that persons authorised to process the data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality, and that they access the data only to the extent necessary for their duties.

Article 4. Security

4.1. The Processor implements the technical and organisational measures (TOMs) appropriate to the risk set out in Annex 2 (Article 32 GDPR).

4.2. The Processor may update them, provided that the overall level of protection is not reduced.

4.3. The Controller is responsible for the security of its own access: selection of Users and their roles, confidentiality of their credentials, activation of two-factor authentication for its administrators, and revocation of access for persons leaving its team.

Article 5. Sub-processors

5.1. The Controller gives the Processor general authorisation to engage the sub-processors listed in Annex 3.

5.2. The Processor informs the Controller in text form at least 30 days in advance of any addition or replacement. Within that period, the Controller may object on reasonable data protection grounds. If the parties cannot find a solution, the Controller may terminate the affected part of the service at no cost and without application of Article 10.1 of the Terms, and is refunded the unperformed portion of any amounts paid in advance.

5.3. The Processor contractually imposes on each sub-processor data protection obligations at least equivalent to those of this DPA (Article 28(4) GDPR). The Processor remains responsible to the Controller for their performance.

Article 6. Transfers outside the European Union

6.1. Data is transferred outside the European Economic Area only if there is an adequacy decision for the destination country (including, for certified US companies, the EU-US Data Privacy Framework) or on the basis of the European Commission's Standard Contractual Clauses (Implementing Decision (EU) 2021/914) and, where necessary, supplementary measures. Transfers by the Processor to a sub-processor outside the EEA without an adequacy decision are governed by Module 3 (processor to processor) of those clauses.

6.2. The planned transfers are listed in Annex 3 together with the applicable safeguard.

Article 7. Data subject rights

7.1. The Processor assists the Controller, through appropriate technical and organisational measures, in responding to requests from data subjects exercising their rights (access, rectification, erasure, restriction, data portability, objection).

7.2. The Platform provides: for Members, the download of their data and the request for erasure via their profile; for the Controller, a page for handling erasure requests and the ability to edit profiles; for the Club, Saison and Signature Plans, the export of the list of Members. The export by the Member excludes fields reserved for the team (moderation notes, fraud signals). Where the Controller needs the data to respond to an access request, or uses the Starter Plan, the Processor provides the necessary data free of charge within 5 business days.

7.3. If the Processor receives a request directly from a data subject, it forwards it to the Controller without undue delay and does not respond to it itself, unless instructed to do so.

Article 8. Personal data breaches

8.1. The Processor notifies the Controller of any personal data breach affecting it without undue delay and no later than 48 hours (24 hours on the Signature Plan where the Order Form so provides) after becoming aware of it; an initial partial notification is made even if the analysis has not yet been completed; the notification is sent to the address set out in Annex 4.

8.2. The notification contains, where possible: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point. The information may be provided in stages.

8.3. The Processor takes appropriate measures without undue delay to contain the breach and limit its consequences. It assists the Controller in notifying the supervisory authority competent for the Controller (Article 33 GDPR) and, where applicable, in communicating the breach to data subjects (Article 34 GDPR). It does not itself notify the authority or data subjects on behalf of the Controller, unless instructed to do so.

Article 9. Assistance with compliance

9.1. The Processor provides the Controller with the information reasonably necessary for its data protection impact assessments and any prior consultation of the supervisory authority (Articles 35 and 36 GDPR). Assistance beyond the provision of existing documentation may be charged at the rates then in force.

9.2. Supervisory authorities. The supervisory authority competent for the Processor is the data protection supervisory authority of the German federal state (Land) in which the Processor has its registered office: Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW, data protection authority of North Rhine-Westphalia), Kavalleriestraße 2–4, 40213 Düsseldorf. The supervisory authority competent for the Controller (and, where applicable, the lead supervisory authority) remains that of the Controller; it is set out in Annex 4. Each party informs the other without undue delay of any enquiries or measures by a supervisory authority concerning the processing under this DPA, to the extent legally permitted.

Article 10. Records of processing

The Processor maintains a record of all categories of processing activities carried out on behalf of the Controller (Article 30(2) GDPR).

Article 11. Audits

11.1. The Processor makes available to the Controller all information necessary to demonstrate compliance with this DPA: a description of the security measures, the list of sub-processors, and any available audit results or certifications.

11.2. If this information is insufficient, the Controller may have an audit, including inspections, carried out (Article 28(3)(h) GDPR), either itself or through an independent auditor bound by confidentiality who is not a competitor of FAN/IP, no more than once a year except in the event of a personal data breach, with 30 business days' prior notice, during business hours and without disrupting the service. The costs of the audit are borne by the Controller, unless the audit reveals a material breach.

11.3. The audit does not give access to other clients' data and, beyond what is necessary, does not give access to information covered by trade secrets.

Article 12. End of services

12.1. At the end of the contract, the Controller chooses the return of its data in accordance with Article 11.1a of the Terms, followed by its deletion.

12.2. After the export period has expired, the Processor deletes the Controller's personal data, including copies, within 30 days, unless Union or Member State law requires the data to be retained. Backup copies are deleted in their normal rotation cycle, no later than 30 days thereafter, and remain protected until then. The Processor confirms the deletion in text form on request.

Article 13. Liability

In external relations with data subjects, Article 82 GDPR applies. As between the parties, Article 17 of the Terms applies, including the maximum amount under Article 17.3 of the Terms, which also applies to breaches of the obligations under this DPA; Article 82(5) GDPR is unaffected.

Article 14. Term and order of precedence

This DPA applies for the entire term of the contract and, after its end, for as long as the Processor holds data of the Controller. In the event of any conflict between this DPA and the Terms on data protection matters, this DPA prevails.

Article 15. Governing law and place of jurisdiction

15.1. This DPA is governed by the law of the Federal Republic of Germany; the provisions of the GDPR take precedence. The United Nations Convention on Contracts for the International Sale of Goods (CISG) does not apply.

15.2. The place of jurisdiction is governed by Article 20.3 of the Terms. The Standard Contractual Clauses referred to in Article 6 are subject to their own provisions on governing law and jurisdiction.


Annex 1. Description of the processing

Item Description
Subject matter Provision of the FAN/IP Platform for the Client's Program
Duration Term of the contract, followed by the export and deletion period (Article 12)
Nature of the processing Collection via the Space, hosting, consultation, calculation of points and levels, retrieval of public post statistics, sending of notifications and emails, moderation, logging, export, pseudonymisation upon deletion, erasure
Purposes Account and membership management; operation of the Program (missions, post validation, points, levels, seasons, badges, streaks, leaderboards, challenges, leagues, questions and quizzes, contests, messaging, friends, rewards and shipments, referrals, QR code check-in, and linking of social media accounts once that module is available); minimum age verification; proof of acceptances; handling of data subject rights requests; fraud prevention; security and traceability; support
Data subjects Members; the Client's Users; invited persons whose email address is entered
Categories of personal data Identification and contact data (last name, first name, username, email address, phone number, city, country, postcode, shipping address); date of birth; TikTok and Instagram handles and public profile pictures; links, thumbnails and public statistics of posts; answers, messages, friend connections; history of points, rewards, shipments and tracking numbers; acceptances (type, version, date); data requests; fraud signals and moderation notes; the Client's internal notes; action logs; language preference; non-reversible hash of the IP address used to limit code attempts; check-ins (date, time, event or location of the QR code); referral codes and referrer–referee link; waiting list registrations; Users' two-factor authentication secret; linked social media accounts, once the module is available (identifier, handle, display name, picture, follower and post counts, recent posts and their statistics, encrypted access keys)
Sensitive data None intended. The Client undertakes not to collect any, in particular in free-text fields
Minors Minimum age set by the Client (16 by default), verified by the Platform against the declared date of birth
Retention periods Set by the Client in its privacy policy; Platform defaults: fraud signals and date-of-birth history 365 days; linked social media accounts: based on the Member's consent, deleted as soon as the Member unlinks the account, leaves the Program or deletes their account

Annex 2. Technical and organisational measures (TOMs)

Measures implemented in the Platform:

Being implemented:

Annex 3. Sub-processors

Sub-processor Service Data Location Transfer safeguard
Supabase Inc. Database, authentication, file storage All EU (Frankfurt am Main, Germany) Hosting in the EU; Standard Contractual Clauses for any access from third countries
Cloudflare, Inc. Running the application server and delivering the app All, in transit Global network; requests are mostly handled in a data centre close to the user EU-US Data Privacy Framework; Standard Contractual Clauses
Sendinblue SAS (Brevo), Paris, France Sending login and service emails, branded for the Client Email address, Program name, email content EU Not required (EU)
RapidAPI and the publishers of the tiktok-api23 and instagram-looter2 APIs offered there Retrieval of public post statistics and profile pictures Post link, social media handle United States Standard Contractual Clauses where no adequacy decision applies
images.weserv.nl Conversion of post thumbnails Public thumbnail URL, no other Member data Not set by contract Only the public image URL is sent
Stripe (Stripe Payments Europe, Ltd., Dublin, Ireland) Online payment of Starter subscriptions Client billing data only (no Member data) EU (Ireland), also United States EU-US Data Privacy Framework; Standard Contractual Clauses; see the note below

Note: the official APIs of TikTok, Meta (Instagram) and Google (YouTube) are called when a Member links their account. Their operators act as separate controllers and are not sub-processors. The payment service provider receives no Member data; it processes the Client's billing data for FAN/IP or as a separate controller, outside the scope of this DPA.

Annex 4. Contacts and supervisory authorities

FAN/IP Client
Data protection contact contact@fan-ip.com Contact address in the administration area (Emails), otherwise the email address of the owner account
Breach notification contact@fan-ip.com Email address of the owner account
Data Protection Officer Not appointed (no obligation under § 38 BDSG) To be provided by the Client, if appointed
Competent supervisory authority Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW, data protection authority of North Rhine-Westphalia), Kavalleriestraße 2–4, 40213 Düsseldorf The authority competent for the Client's seat (its lead authority, where applicable)

Version 2026-10-03 · SHA-256 of this page is recorded with each acceptance.