Skip to content
Open source, AGPL v3.See the plans

Legal

Data processing agreement

Reloop Cloud processes your CRM data on your behalf. This agreement under Article 28 GDPR uses the standard contractual clauses of the European Commission, unchanged, and fills in their annexes.

Version of October 1, 2026

This English text is a translation. Only the German text is binding. Read the German text

The clauses are the text of Commission Implementing Decision (EU) 2021/915. Official text on EUR-Lex

SECTION I

Clause 1Purpose and scope

(a)

The purpose of these Standard Contractual Clauses (the Clauses) is to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation).

(b)

The controllers and processors listed in Annex I have agreed to these Clauses in order to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 and/or Article 29(3) and (4) of Regulation (EU) 2018/1725.

(c)

These Clauses apply to the processing of personal data as specified in Annex II.

(d)

Annexes I to IV are an integral part of the Clauses.

(e)

These Clauses are without prejudice to obligations to which the controller is subject by virtue of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

(f)

These Clauses do not by themselves ensure compliance with obligations related to international transfers in accordance with Chapter V of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

Clause 2Invariability of the Clauses

(a)

The Parties undertake not to modify the Clauses, except for adding information to the Annexes or updating information in them.

(b)

This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a broader contract, or from adding other clauses or additional safeguards provided that they do not directly or indirectly contradict the Clauses or detract from the fundamental rights or freedoms of data subjects.

Clause 3Interpretation

(a)

Where these Clauses use the terms defined in Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively, those terms shall have the same meaning as in that Regulation.

(b)

These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively.

(c)

These Clauses shall not be interpreted in a way that runs counter to the rights and obligations provided for in Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or in a way that prejudices the fundamental rights or freedoms of the data subjects.

Clause 4Hierarchy

In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties existing at the time when these Clauses are agreed or entered into thereafter, these Clauses shall prevail.

Clause 5 - OptionalDocking clause

(a)

Any entity that is not a Party to these Clauses may, with the agreement of all the Parties, accede to these Clauses at any time as a controller or a processor by completing the Annexes and signing Annex I.

(b)

Once the Annexes in (a) are completed and signed, the acceding entity shall be treated as a Party to these Clauses and have the rights and obligations of a controller or a processor, in accordance with its designation in Annex I.

(c)

The acceding entity shall have no rights or obligations resulting from these Clauses from the period prior to becoming a Party.

SECTION IIOBLIGATIONS OF THE PARTIES

Clause 6Description of processing(s)

The details of the processing operations, in particular the categories of personal data and the purposes of processing for which the personal data is processed on behalf of the controller, are specified in Annex II.

Clause 7Obligations of the Parties

7.1. Instructions

(a)

The processor shall process personal data only on documented instructions from the controller, unless required to do so by Union or Member State law to which the processor is subject. In this case, the processor shall inform the controller of that legal requirement before processing, unless the law prohibits this on important grounds of public interest. Subsequent instructions may also be given by the controller throughout the duration of the processing of personal data. These instructions shall always be documented.

(b)

The processor shall immediately inform the controller if, in the processor’s opinion, instructions given by the controller infringe Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or the applicable Union or Member State data protection provisions.

7.2. Purpose limitation

The processor shall process the personal data only for the specific purpose(s) of the processing, as set out in Annex II, unless it receives further instructions from the controller.

7.3. Duration of the processing of personal data

Processing by the processor shall only take place for the duration specified in Annex II.

7.4. Security of processing

(a)

The processor shall at least implement the technical and organisational measures specified in Annex III to ensure the security of the personal data. This includes protecting the data against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to the data (personal data breach). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risks involved for the data subjects.

(b)

The processor shall grant access to the personal data undergoing processing to members of its personnel only to the extent strictly necessary for implementing, managing and monitoring of the contract. The processor shall ensure that persons authorised to process the personal data received have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

7.5. Sensitive data

If the processing involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (“sensitive data”), the processor shall apply specific restrictions and/or additional safeguards.

7.6. Documentation and compliance

(a)

The Parties shall be able to demonstrate compliance with these Clauses.

(b)

The processor shall deal promptly and adequately with inquiries from the controller about the processing of data in accordance with these Clauses.

(c)

The processor shall make available to the controller all information necessary to demonstrate compliance with the obligations that are set out in these Clauses and stem directly from Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725. At the controller’s request, the processor shall also permit and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or an audit, the controller may take into account relevant certifications held by the processor.

(d)

The controller may choose to conduct the audit by itself or mandate an independent auditor. Audits may also include inspections at the premises or physical facilities of the processor and shall, where appropriate, be carried out with reasonable notice.

(e)

The Parties shall make the information referred to in this Clause, including the results of any audits, available to the competent supervisory authority/ies on request.

7.7. Use of sub-processors

(a)

OPTION 2: GENERAL WRITTEN AUTHORISATION: The processor has the controller’s general authorisation for the engagement of sub-processors from an agreed list. The processor shall specifically inform in writing the controller of any intended changes of that list through the addition or replacement of sub-processors at least 30 days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the concerned sub-processor(s). The processor shall provide the controller with the information necessary to enable the controller to exercise the right to object.

(b)

Where the processor engages a sub-processor for carrying out specific processing activities (on behalf of the controller), it shall do so by way of a contract which imposes on the sub-processor, in substance, the same data protection obligations as the ones imposed on the data processor in accordance with these Clauses. The processor shall ensure that the sub-processor complies with the obligations to which the processor is subject pursuant to these Clauses and to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

(c)

At the controller’s request, the processor shall provide a copy of such a sub-processor agreement and any subsequent amendments to the controller. To the extent necessary to protect business secret or other confidential information, including personal data, the processor may redact the text of the agreement prior to sharing the copy.

(d)

The processor shall remain fully responsible to the controller for the performance of the sub-processor’s obligations in accordance with its contract with the processor. The processor shall notify the controller of any failure by the sub-processor to fulfil its contractual obligations.

(e)

The processor shall agree a third party beneficiary clause with the sub-processor whereby - in the event the processor has factually disappeared, ceased to exist in law or has become insolvent - the controller shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.

7.8. International transfers

(a)

Any transfer of data to a third country or an international organisation by the processor shall be done only on the basis of documented instructions from the controller or in order to fulfil a specific requirement under Union or Member State law to which the processor is subject and shall take place in compliance with Chapter V of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725.

(b)

The controller agrees that where the processor engages a sub-processor in accordance with Clause 7.7. for carrying out specific processing activities (on behalf of the controller) and those processing activities involve a transfer of personal data within the meaning of Chapter V of Regulation (EU) 2016/679, the processor and the sub-processor can ensure compliance with Chapter V of Regulation (EU) 2016/679 by using standard contractual clauses adopted by the Commission in accordance with of Article 46(2) of Regulation (EU) 2016/679, provided the conditions for the use of those standard contractual clauses are met.

Clause 8Assistance to the controller

(a)

The processor shall promptly notify the controller of any request it has received from the data subject. It shall not respond to the request itself, unless authorised to do so by the controller.

(b)

The processor shall assist the controller in fulfilling its obligations to respond to data subjects’ requests to exercise their rights, taking into account the nature of the processing. In fulfilling its obligations in accordance with (a) and (b), the processor shall comply with the controller’s instructions

(c)

In addition to the processor’s obligation to assist the controller pursuant to Clause 8(b), the processor shall furthermore assist the controller in ensuring compliance with the following obligations, taking into account the nature of the data processing and the information available to the processor:

(1)

the obligation to carry out an assessment of the impact of the envisaged processing operations on the protection of personal data (a ‘data protection impact assessment’) where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons;

(2)

the obligation to consult the competent supervisory authority/ies prior to processing where a data protection impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk;

(3)

the obligation to ensure that personal data is accurate and up to date, by informing the controller without delay if the processor becomes aware that the personal data it is processing is inaccurate or has become outdated;

(4)

the obligations in Article 32 of Regulation (EU) 2016/679.

(d)

The Parties shall set out in Annex III the appropriate technical and organisational measures by which the processor is required to assist the controller in the application of this Clause as well as the scope and the extent of the assistance required.

Clause 9Notification of personal data breach

In the event of a personal data breach, the processor shall cooperate with and assist the controller for the controller to comply with its obligations under Articles 33 and 34 of Regulation (EU) 2016/679 or under Articles 34 and 35 of Regulation (EU) 2018/1725, where applicable, taking into account the nature of processing and the information available to the processor.

9.1 Data breach concerning data processed by the controller

In the event of a personal data breach concerning data processed by the controller, the processor shall assist the controller:

(a)

in notifying the personal data breach to the competent supervisory authority/ies, without undue delay after the controller has become aware of it, where relevant/(unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons);

(b)

in obtaining the following information which, pursuant to Article 33(3) of Regulation (EU) 2016/679, shall be stated in the controller’s notification, and must at least include:

(1)

the nature of the personal data including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;

(2)

the likely consequences of the personal data breach;

(3)

the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.

Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.

(c)

in complying, pursuant to Article 34 of Regulation (EU) 2016/679, with the obligation to communicate without undue delay the personal data breach to the data subject, when the personal data breach is likely to result in a high risk to the rights and freedoms of natural persons.

9.2 Data breach concerning data processed by the processor

In the event of a personal data breach concerning data processed by the processor, the processor shall notify the controller without undue delay after the processor having become aware of the breach. Such notification shall contain, at least:

(a)

a description of the nature of the breach (including, where possible, the categories and approximate number of data subjects and data records concerned);

(b)

the details of a contact point where more information concerning the personal data breach can be obtained;

(c)

its likely consequences and the measures taken or proposed to be taken to address the breach, including to mitigate its possible adverse effects.

Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.

The Parties shall set out in Annex III all other elements to be provided by the processor when assisting the controller in the compliance with the controller’s obligations under Articles 33 and 34 of Regulation (EU) 2016/679.

SECTION IIIFINAL PROVISIONS

Clause 10Non-compliance with the Clauses and termination

(a)

Without prejudice to any provisions of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725, in the event that the processor is in breach of its obligations under these Clauses, the controller may instruct the processor to suspend the processing of personal data until the latter complies with these Clauses or the contract is terminated. The processor shall promptly inform the controller in case it is unable to comply with these Clauses, for whatever reason.

(b)

The controller shall be entitled to terminate the contract insofar as it concerns processing of personal data in accordance with these Clauses if:

(1)

the processing of personal data by the processor has been suspended by the controller pursuant to point (a) and if compliance with these Clauses is not restored within a reasonable time and in any event within one month following suspension;

(2)

the processor is in substantial or persistent breach of these Clauses or its obligations under Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725;

(3)

the processor fails to comply with a binding decision of a competent court or the competent supervisory authority/ies regarding its obligations pursuant to these Clauses or to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

(c)

The processor shall be entitled to terminate the contract insofar as it concerns processing of personal data under these Clauses where, after having informed the controller that its instructions infringe applicable legal requirements in accordance with Clause 7.1 (b), the controller insists on compliance with the instructions.

(d)

Following termination of the contract, the processor shall, at the choice of the controller, delete all personal data processed on behalf of the controller and certify to the controller that it has done so, or, return all the personal data to the controller and delete existing copies unless Union or Member State law requires storage of the personal data. Until the data is deleted or returned, the processor shall continue to ensure compliance with these Clauses.

ANNEX IList of parties

Controller(s)

Name

The customer who registers a workspace on Reloop Cloud (app.reloopcrm.com). The company given at registration is decisive.

Address

The address the customer gives in the main contract or for billing.

Contact person’s name, position and contact details

The person who registers the workspace, as owner of the workspace, at the email address used to register.

Signature and accession date

Consent by ticking a box at registration. For every workspace the processor stores the time of consent, the version of these Clauses and the email address that consented.

Processor(s)

Name

Tugra Örscelik, TT HandelsLogistik

Address

Gewerbepark 14, 91350 Gremsdorf, Germany

VAT ID DE457312616

Contact person’s name, position and contact details

Tugra Örscelik, owner, contact@reloopcrm.com

Signature and accession date

The processor provides these Clauses in the version of 1 October 2026. It is bound by them from the controller’s consent.

ANNEX IIDescription of the processing

Categories of data subjects whose personal data is processed

Employees and other users of the controller who have access to the workspace.

Customers, former customers, prospects, suppliers and other business partners of the controller, and their contact persons.

All other senders and recipients of email in the mailboxes the controller connects.

Visitors of the controller’s website, when the controller embeds the tracking script.

Categories of personal data processed

Master and contact data: name, email address, phone number, position, company and postal address, where present.

Content and metadata of email: subject, body, sender, recipients and times.

Calendar entries: title, attendees and times.

Sales data: deals, amounts, stages, notes and activities.

Data derived by AI models: assessments of conversations, win back scores, drafts, conversations with the agent and a learned profile of the workspace’s mailboxes.

Publicly available company data: name, logo, industry, location and contact details from the company’s website.

Usage data of the controller’s users: sign-in data, sessions and logs.

With website tracking: page views and form submissions of visitors of the controller’s website.

Credentials for connected services: OAuth tokens, IMAP passwords and API keys.

Sensitive data processed (if applicable) and applied restrictions or safeguards

The service does not process sensitive data on purpose. Email from connected mailboxes can contain such data.

All measures in Annex III apply to this data. It stays in the workspace’s database and serves only the purposes in this Annex.

Nature of the processing

Operation of a CRM as an online service: collection, storage, organisation, analysis, retrieval, display, export, backup and erasure.

The service reads mailboxes and calendars at Google and Microsoft with read permission only. The service sends no email from the controller’s mailboxes. A person sends a draft.

Purpose(s) for which the personal data is processed on behalf of the controller

Provision of Reloop Cloud under the main contract between the Parties, namely:

Reading the connected mailboxes and calendars and storing messages, contacts and companies.

Managing contacts, companies, deals and activities.

Analysing conversations with AI models, matching contacts and companies, suggestions to win back customers and drafts of email.

Recording page views and form submissions on the controller’s website, only when the controller embeds the tracking script.

Connecting Slack and webhooks, only when the controller connects them.

Nightly backups.

Sending system email to the controller’s users: confirmation codes and notices about the trial and billing.

Duration of the processing

For the term of the main contract, including a free trial.

When the owner deletes the workspace, the service backs up the workspace’s database once and then deletes it.

When the trial or the subscription ends without payment, the service suspends the workspace. After 30 days it backs up the database once and deletes it.

The processor deletes backup copies no later than 60 days after they are made.

Processing by sub-processors

Subject matter, nature and location of processing by sub-processors are set out in Annex IV. The duration is the same as above.

ANNEX IIITechnical and organisational measures including technical and organisational measures to ensure the security of the data

Separation of workspaces

Every workspace has its own PostgreSQL database. A central registry maps every sign-in to exactly one workspace.

Sign-in to a workspace is limited to approved email addresses or domains.

User identification and authorisation

Sign-in with Google, with Microsoft or with a password.

Registration, password reset and deletion of a workspace require a six digit code by email. The code is valid for 15 minutes and allows at most 5 attempts.

Registrations are limited to 5 attempts per minute per email address and 20 attempts per minute per IP address.

Deleting a workspace requires a fresh confirmation and is limited to 5 attempts per minute.

Access to mailboxes

Google: gmail.readonly and calendar.readonly. Microsoft: Mail.Read. The service requests no permission to send.

Protection of data during transmission

Access to app.reloopcrm.com runs over HTTPS.

Connections to the sub-processors in Annex IV run over HTTPS.

Backups go to the backup server over SFTP.

Protection of data during storage

The service stores OAuth tokens, IMAP passwords and API keys encrypted with AES-256-GCM. It derives the key per purpose from a server secret.

The service encrypts the nightly backups with age before they are written to disk. The servers hold only the public key. The processor keeps the private key off the servers.

Integrity of backups

The account on the backup server can write files but cannot delete or rename them. A compromised main server therefore cannot delete the off-site backups.

Availability and timely restoration

Every night the service backs up the databases of all workspaces and the registry with pg_dump. It keeps 14 daily and 8 weekly copies on the main server and copies them to a backup server at a different host.

Before it deletes a database, the service always makes a fresh backup. Without a backup it does not delete.

A failed migration of one workspace does not stop the other workspaces.

A new version goes live only after a health check. When the check fails, the service returns to the previous version.

Logging

Before every replacement of the containers the deploy script saves their logs.

The API writes no HTTP headers, no query strings and no request bodies to its logs.

Data minimisation and limited retention

When connecting a mailbox the controller chooses how far back the first read goes.

The service deletes unconfirmed registrations after 48 hours.

The service deletes suspended workspaces after 30 days.

The service deletes archived companies, contacts and deals after a period the controller sets.

Data portability and erasure

The controller exports contacts, companies and deals as a CSV file at any time. The export defuses formulas.

The controller edits and deletes single records in the interface.

The owner deletes the whole workspace in the settings.

Review and quality assurance

The source code of the software is public under the AGPL-3.0 licence: github.com/reloopcrm/reloop.

Automated tests run before every change, including tests for security and for the separation of workspaces.

Security issues can be reported privately on GitHub as described in SECURITY.md.

Physical security

The servers are in data centres of Contabo and Hostinger (Annex IV). The physical security of the data centres lies with these providers.

Measures of the sub-processors

The sub-processors in Annex IV protect the data under their own data processing agreements with the processor.

Description of the specific technical and organisational measures to be taken by the processor to be able to provide assistance to the controller

Data subject requests (Clause 8)

The controller finds, corrects, exports and deletes data in the interface.

When a request reaches the processor, the processor forwards it to the owner of the workspace.

Breach notification (Clause 9)

The processor notifies a breach by email to the address of the owner of the workspace.

The contact point for further information is contact@reloopcrm.com.

ANNEX IVList of sub-processors

The controller authorises the sub-processors in this list under Clause 7.7(a), Option 2.

The processor announces every change of this list at least 30 days in advance by email to the address of the owner of the workspace.

On the Hosting and Hosting Pro plans the controller enters its own key for an AI provider. The service then sends text to that provider, under the controller’s own contract with it. That provider is not a sub-processor.

1. Contabo GmbH

Address

Welfenstraße 22, 81541 Munich, Germany

Description of the processing

Hosting of the main server: app, API, agent, the databases of all workspaces and the backups on the main server. Covers all data in Annex II.

Location of processing

European Union

Transfer to a third country

None.

2. Hostinger International Ltd.

Address

61 Lordou Vironos Street, 6023 Larnaca, Cyprus

Description of the processing

Hosting of the backup server: storage of the nightly backups of all databases. Covers all data in Annex II.

Location of processing

European Union

Transfer to a third country

None.

3. OpenRouter, Inc.

Address

169 Madison Avenue, New York, NY 10016, USA

Description of the processing

Routing of calls to AI models on the plans with AI included: content of email conversations, contact and company data, chat input and drafts.

OpenRouter forwards every call to the provider of the model. Drafts of email come from an OpenAI model, and OpenRouter forwards those calls to OpenAI only. For chat and analysis OpenRouter chooses the provider of the model.

Location of processing

USA

Transfer to a third country

Standard contractual clauses of the Commission under Article 46(2) of Regulation (EU) 2016/679, in OpenRouter’s data processing agreement.

4. TypeSafe AI, Inc.

Address

255 California Street, Suite 1300, San Francisco, CA 94117, USA

Description of the processing

A short check whether an email conversation is relevant to the business, before the larger model analyses it: subject and body of one conversation and the description of the controller’s business.

Location of processing

USA

Transfer to a third country

Standard contractual clauses of the Commission under Article 46(2) of Regulation (EU) 2016/679, in TypeSafe’s data processing agreement.

5. Plus Five Five, Inc. (Resend)

Address

2261 Market Street #5039, San Francisco, CA 94114, USA

Description of the processing

Sending system email to the controller’s users: confirmation codes and notices about the trial and billing. Covers email address, name and content of the system email.

Location of processing

USA

Transfer to a third country

Adequacy decision of the Commission on the EU-US Data Privacy Framework. In addition, standard contractual clauses in Resend’s data processing agreement.