Data Processing Agreement for coaches

Last updated: 30 October 2026

Every coach who uses Macrocycle accepts this agreement with our Terms of Service. It covers the records a coach keeps about their clients, which we process on the coach's behalf.

Version 1.1 · 30 October 2026

This agreement covers the personal data a coach keeps about their clients in Macrocycle. The coach is the controller of that data. Petar Ivanov Tech EOOD processes it on the coach's behalf, as the processor. Article 28 of the GDPR requires a contract between the two, and this is that contract.

Part 1 says how the agreement is made and how it runs. Part 2 is the European Commission's standard contractual clauses between controllers and processors, adopted by Commission Implementing Decision (EU) 2021/915 of 4 June 2021 (OJ L 199, 7.6.2021, p. 18). We use their official text unchanged and have only chosen among the options they offer. The annexes to Part 2 describe our processing. Part 3 applies only to coaches established outside the EU and the EEA, in a country without an adequacy decision (Part 1, point 10).

Part 1. How this agreement works

1. Who agrees. The parties are the coach who holds a Macrocycle coach account (the controller, described in Annex I) and Petar Ivanov Tech EOOD (the processor). A coach who runs their business as a company agrees on behalf of that company.

2. How it is made. A new coach accepts this agreement in the Macrocycle Coach app when creating a coach account, by ticking the terms box on our payment page, or by paying a proforma invoice that refers to our Terms. A coach whose account existed before this agreement receives it by email at the coach account's address and on a card on the app's Home screen; tapping OK on that card, or using the app after that email, counts as acceptance. We record the date, time and version of an acceptance in the app against the coach account, and Stripe records a tick on the payment page with the payment. That makes the agreement a contract in electronic form, as Article 28(9) of the GDPR allows. The coach can save or print this page at any time, and we send a copy on request.

3. Relation to our Terms. This agreement forms part of the Macrocycle Terms of Service. Where the two conflict on the processing of personal data, the Clauses in Part 2 prevail (Clause 4).

4. Documented instructions. The coach's documented instructions to us (Clause 7.1) are this agreement, the coach's use of the app's features and settings, and any written instruction the coach emails to the contact address in Annex I.

5. New sub-processors. We tell the coach about an intended addition or replacement in Annex IV by email to the coach account's address, at least 30 days before the new sub-processor starts (Clause 7.7(a)). The coach can object by replying within those 30 days. If we cannot meet the objection, the coach may end this agreement before the change takes effect, by deleting their account, at no cost.

6. When the agreement ends. It lasts as long as the coach account exists. Deleting the coach account in the app is the coach's choice, under Clause 10(d), to have the data deleted rather than returned. A coach who wants the data returned asks us for an export before deleting the account (Annex III, "Measures for allowing data portability and ensuring erasure"). On request we confirm the deletion in writing.

7. Language. The Clauses in Part 2 are the Commission's official English and Bulgarian texts, and both are authentic. The annexes say the same in both languages; for a coach established in Bulgaria the Bulgarian annexes prevail.

8. Law. This agreement is governed by the law of the Republic of Bulgaria, like our Terms.

9. Updates. We change this agreement only by adding or updating information in the annexes (Clause 2(a)). Each version carries a number and a date, and earlier versions stay available on request.

10. Coaches outside the EU and the EEA. A coach established in a country outside the EU and the EEA that the European Commission has not recognised as giving adequate protection, for example Australia or the United States, receives their clients' records from us in that country. That is a transfer of personal data from a processor in the EU to a controller in a third country. For such a coach, Part 3 applies in addition to Part 2. It is Module Four of the standard contractual clauses in Commission Implementing Decision (EU) 2021/914. A coach in a country with an adequacy decision, such as the United Kingdom, Switzerland, Canada, New Zealand or Japan, needs no further clauses.

Part 2. Standard contractual clauses

SECTION I

Clause 1: Purpose 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 2: Invariability 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 3: Interpretation

(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 4: Hierarchy

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 - Optional: Docking clause

[Not used. The Parties have not chosen this optional clause.]

SECTION II

OBLIGATIONS OF THE PARTIES

Clause 6: Description 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 7: Obligations 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) 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 8: Assistance 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 9: Notification 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, 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 III

FINAL PROVISIONS

Clause 10: Non-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 I

List of parties

Controller(s): [Identity and contact details of the controller(s), and, where applicable, of the controller’s data protection officer]

  1. The coach
    • Name: the coach, or the coach's company, that accepted this agreement in the Macrocycle Coach app, under the name held on the coach account.
    • Address: the address the coach gives us on request or on an invoice. Under these Clauses we contact the coach at the coach account's email address.
    • Contact person's name, position and contact details: the coach, at the coach account's email address. A coach who has appointed a data protection officer tells us their contact details by email.
    • Signature and accession date: electronic acceptance in the Macrocycle Coach app, on our payment page or by email (Part 1, point 2). We record its date, time and version against the coach account.

Processor(s): [Identity and contact details of the processor(s) and, where applicable, of the processor’s data protection officer]

  1. Petar Ivanov Tech EOOD
    • Name: Petar Ivanov Tech EOOD (Петър Иванов Тех ЕООД), a single-member limited liability company registered in Bulgaria, UIC 205390030, VAT BG205390030, operating Macrocycle.
    • Address: Ovcha Kupel 2, bl. 39, ent. A, ap. 64, Ovcha Kupel district, 1632 Sofia, Bulgaria.
    • Contact person's name, position and contact details: Petar Ivanov, Manager, getmacrocycle@gmail.com, phone +359 887 652 350. The processor has not appointed a data protection officer, as it is not required to.
    • Signature and accession date: the processor agrees by publishing this agreement and accepting it with each coach, on the date of the coach's acceptance.

ANNEX II

Description of the processing

Categories of data subjects whose personal data is processed

  • The coach's clients: people the coach trains in person or online and adds to the coach's roster in the Macrocycle Coach app, whether or not they use the Macrocycle Client app.
  • People the coach adds before they become clients, for example through a spreadsheet import.
  • Clients under 18, only where the coach has the consent of a parent or guardian (Terms, section 3).

Categories of personal data processed

What the Macrocycle 1.0 apps store about a client:

  • Profile: name and nickname, sex, year of birth, height, training goal, start date, whether the client trains in the gym or online, training days, which program days the client trains alone, and contact details where the coach records them (phone, Viber, email).
  • Link to the client's own login: where the client uses the Macrocycle Client app, the invite code the coach issued and the identifier of the client's login. The login itself (name, email, sign-in method) is the processor's own account data under its Privacy Policy.
  • Training: programs with their days and exercises, target sets, repetitions and weights, progression steps, the day the client is on, and every session logged on the coach's phone or in the client app (date, status, who logged it, sets, repetitions and weight lifted).
  • Schedule and attendance: booked sessions with date, time and status, and whether a session was attended.
  • Body measurements and weight: body weight entries, tape measurements, skinfold caliper readings, and the figures the app calculates from them (body-fat estimate, fat and lean mass, BMR, TDEE, the deficit the coach picks).
  • Packages and payments the coach records: package size, sessions left, agreed price, renewal date. Macrocycle takes no part in those payments.
  • Spreadsheets the coach sends us: when the coach taps "Send it to us" on the import screen, or the app sends a file that failed to import, the email carries the file or its link. The file can hold any of the above.

Some data is stored only if a feature now hidden in the 1.0 apps is switched on (Part 1, point 5 and Annex IV, Anthropic). These are intake questionnaire answers about training history, lifestyle and health; the coach's private and shared exercise notes; exercises excluded for a client with the reason (which may be an injury); badges; AI suggestions and their inputs. Progress photos are not collected. The data model reserves a place for them, and no feature uploads any.

Sensitive data processed (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures.

Body weight, body measurements and body composition are data concerning health (Article 9 GDPR); so are injury reasons and intake health answers if those features are switched on. The coach is responsible for the legal basis, which for most coaches is the client's explicit consent (Terms, section 7). On the coach's behalf, the Macrocycle Client app asks a client who joins with an invite code for that consent and records when it was given. A coach who adds or imports a client in the Coach app confirms that they hold it. Safeguards:

  • Purpose: used only to show and calculate the client's progress for the coach and the client. Never for advertising, never sold, never used to train AI models.
  • Access: the database lets only the coach and that client read these rows (Annex III, "Measures for user identification and authorisation"). On the processor's side only Petar Ivanov has access, and he opens client records only to answer the coach's request or to fix a fault. The AI tools he works with see only aggregate counts from production, never a client's records or their identifiers.
  • Analytics and crash reports carry no measurements: usage events hold counts and fixed labels only, they are sent only for users who said yes to sharing usage data, and neither app records the screen (Annex III, "Measures for ensuring data minimisation").
  • Storage: the database is in the EU (Frankfurt). The current app versions send none of it to an AI provider (Annex IV, Anthropic).

Nature of the processing

Storage and hosting of the coach's records; synchronisation between the coach's phone, the client's phone and the server; calculations (progression targets, body-fat estimates, sessions left); display to the coach and to the linked client; backups; email delivery of spreadsheets the coach sends us, and setting up a program from them at the coach's request; deletion.

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

To provide Macrocycle to the coach, which covers managing clients, programs, sessions, check-ins and packages; letting the coach's clients see their program and log their training in the Macrocycle Client app; setting up imports the coach asks us to set up; keeping the service secure and fixing faults.

Duration of the processing

For as long as the coach account exists. The coach can delete a single client at any time (Delete client) and the whole account at any time (Delete account), and the data goes from the live database at once. Copies in Supabase's daily backups expire within 7 days. When a client withdraws their health-data consent, in the Macrocycle Client app or through the coach or us, their weigh-ins and measurements are hidden at once and deleted 30 days later, unless the client agrees again within those 30 days; backups drop them 7 days after the deletion. We delete spreadsheets sent to our support mailbox within 90 days.

For processing by (sub-) processors, also specify subject matter, nature and duration of the processing

Annex IV gives each sub-processor's subject matter and nature, and none processes the data for longer than the duration above, or the shorter retention stated for it.


ANNEX III

Technical and organisational measures including technical and organisational measures to ensure the security of the data

Description of the technical and organisational security measures implemented by the processor(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, as well as the risks for the rights and freedoms of natural persons.

The processor holds no certification of its own. Supabase, Clerk, Sentry and PostHog publish their own security reports and certifications, and the coach can ask us for them.

Measures of pseudonymisation and encryption of personal data. All traffic between the apps and the servers goes over HTTPS (TLS). Supabase encrypts the database and its backups at rest. Usage analytics identify a user only by a random login identifier, never by name or email, and crash reports carry no user identity.

Measures for ensuring ongoing confidentiality, integrity, availability and resilience of processing systems and services. Production, demo and development run in three separate Supabase projects, so test work never touches real data, and a production build cannot start without production's own keys. Production builds start with an empty roster, and the demo cast exists only off production. The apps keep a working copy on the phone and queue changes made offline until the server has them. The coach app never drops a queued change on its own: only the coach removes one, in Settings. The apps store sign-in tokens in the phone's secure keychain (iOS Keychain, Android Keystore).

Measures for ensuring the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident. Supabase takes daily backups of the production database (Pro plan), kept for 7 days. The incident runbook covers rolling back a faulty app update and fixing the database through a reviewed migration.

Processes for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures in order to ensure the security of the processing. Every change goes through a pull request with type checks, unit tests, database tests that run every migration and check the access rules, and end-to-end tests. Before merging a change we run it on an iPhone simulator, and on an Android emulator when it touches Android. The release pipeline applies database migrations to development first, then demo, then production, each only after the one before succeeded. Nobody applies them by hand.

Measures for user identification and authorisation. Coaches and clients sign in through Clerk with Google or a one-time 6-digit code sent by email; Macrocycle stores no passwords. Every table holding client data has row-level security on. The database itself checks each request against the signed-in login, and a coach reaches only their own clients and a client only their own records. No table can be read or written without a signed-in session. A client links to a coach only with the invite code the coach issued, and only the coach can edit a client's profile. Deleting an account requires a fresh code sent by email.

Measures for the protection of data during transmission. Every connection the apps and our server functions make, to Supabase, Clerk, Sentry, PostHog, Expo and Resend, uses HTTPS.

Measures for the protection of data during storage. The database and its backups are encrypted at rest by Supabase. The secret database key that bypasses the access rules is never put in an app or in the code repository. Signing out as one coach and in as another wipes the first coach's copy from the phone.

Measures for ensuring physical security of locations at which personal data are processed. No client data is kept on the processor's own premises. Data lives in the data centres of the sub-processors in Annex IV (for the database, AWS in Frankfurt through Supabase), whose physical security is covered by their certifications.

Measures for ensuring events logging. The Supabase platform logs database and API requests and server function runs. Sentry records app crashes and errors, and alerts Petar Ivanov by email when production errors appear or spike.

Measures for ensuring system configuration, including default configuration. The access rules and functions are defined in version-controlled migrations, reviewed before merge, and are the same in all three environments. The app's server functions refuse a request without a signed-in session; the only public one takes the website's waitlist form. Analytics are off in every build except production. In production nothing is sent until the user says yes when the app first asks, and the answer can be changed at any time in Settings.

Measures for internal IT and IT security governance and management. Petar Ivanov, the processor's manager, is responsible for security and is the only person with administrative access to production systems. Access uses his personal accounts at each provider. The processor uses AI coding assistants under his supervision to build and maintain the service. They may read aggregate counts from production, never the rows of client data or their identifiers.

Measures for certification/assurance of processes and products. The processor holds none. We rely on the sub-processors' certifications (see the top of this annex).

Measures for ensuring data minimisation. Crash reports carry error messages, counts and device details, never the content of a client's records, and the apps do not send a user identity to Sentry. Usage analytics carry counts and fixed labels only, are sent only for users who said yes, and leave out console logs and network requests; neither app records the screen. An import is read on the coach's phone, and only what the coach confirms on the review screen reaches the server.

Measures for ensuring data quality. The coach and the client see and correct the records in the apps. Imports show a review screen and create nothing until the coach confirms.

Measures for ensuring limited data retention. Delete client and Delete account remove the data from the live database at once, and backups expire within 7 days. A client's withdrawn health-data consent hides their weigh-ins and measurements at once and deletes them 30 days later. We delete support emails with spreadsheets within 90 days, and Sentry keeps crash reports up to 90 days (Annex II, "Duration of the processing").

Measures for ensuring accountability. We keep this agreement, the Privacy Policy and the record of each coach's acceptance. The code, the access rules and every change to them are kept in version control with their review history.

Measures for allowing data portability and ensuring erasure. The coach erases a client with Delete client, or everything with Delete account, in the app. On the coach's request we send an export of the coach's records in a machine-readable format (JSON or CSV) within 30 days, for portability.

For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller

Each sub-processor in Annex IV is bound by a data processing agreement with the processor. Where it is outside the EEA, transfers rely on the EU-US Data Privacy Framework where the provider is certified, and on the Commission's standard contractual clauses in its agreement. They delete the data they hold when the processor deletes it, or after their stated retention, and notify the processor of a personal data breach under its agreement.

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

  • Requests from clients (Clause 8). The coach can view, correct and delete a client's records in the app. We forward a request that reaches us directly to the coach within 5 working days, and we do not answer it ourselves unless the coach asks us to. A client who deletes their own login only unlinks it; their records stay with the coach until the coach deletes them.
  • Impact assessments and prior consultation (Clause 8(c)). On request we give the coach the information in this agreement and answers about our processing that the coach needs for a data protection impact assessment.
  • Personal data breaches (Clause 9). We notify the coach by email at the coach account's address without undue delay, and at the latest within 48 hours of becoming aware of a breach that affects the coach's data. Beyond the content required by Clause 9.2, the notice states when the breach happened and when we found it, which systems and sub-processors are involved, and whether the data was encrypted. We send further information as we learn it and keep a record of every breach.

ANNEX IV

List of sub-processors

The controller has authorised the use of the following sub-processors. This list is the agreed list under Clause 7.7(a); changes follow Part 1, point 5.

  1. Supabase Pte. Ltd.
    • Address: 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513.
    • Contact: privacy@supabase.com.
    • Description of the processing: hosts the database, the server functions and the backups of the production service, in AWS eu-central-1 (Frankfurt, Germany). Stores all categories of data in Annex II for the duration in Annex II. Responsible for the infrastructure; the processor is responsible for the schema, the access rules and the application.
  2. Clerk, Inc.
    • Address: 660 King Street, Unit 345, San Francisco, CA 94107, USA.
    • Contact: privacy@clerk.dev.
    • Description of the processing: sign-in for coaches and clients (name, email, Google identity, session tokens). It holds no training or body data; it holds the login that the database links to a client's records. USA, under the EU-US Data Privacy Framework and the standard contractual clauses in Clerk's agreement.
  3. Functional Software, Inc. (Sentry)
    • Address: 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA.
    • Contact: compliance@sentry.io.
    • Description of the processing: crash and error reports from the apps and the server functions, in Sentry's EU data region (Germany). Reports hold device and app details and error messages, not client records. Kept up to 90 days. Covered by the EU-US Data Privacy Framework for any access from the USA.
  4. PostHog Inc.
    • Address: 2261 Market Street #4008, San Francisco, CA 94114, USA.
    • Contact: through posthog.com/dpa.
    • Description of the processing: app usage statistics, in PostHog's EU cloud (Frankfurt), sent only for users who said yes to sharing usage data. Events carry a random login identifier, counts and fixed labels. No screen recordings. A user can change the answer at any time in Settings.
  5. Plus Five Five, Inc. (Resend)
    • Address: 2261 Market Street #5039, San Francisco, CA 94114, USA.
    • Contact: support@resend.com.
    • Description of the processing: delivers the emails that carry a spreadsheet the coach sends us, or one that failed to import, to our support mailbox. The file can hold client training and body data. USA, under the EU-US Data Privacy Framework and the standard contractual clauses in Resend's agreement.
  6. Google Ireland Limited (Google Workspace)
    • Address: Gordon House, Barrow Street, Dublin 4, Ireland.
    • Contact: through the data protection contact form in the Google Workspace Admin console.
    • Description of the processing: the processor's support mailbox, which receives those spreadsheets and the coach's emails. We delete those spreadsheets within 90 days. Google's Cloud Data Processing Addendum applies, with standard contractual clauses for any transfer outside the EEA.
  7. 650 Industries, Inc. (Expo)
    • Address: 624 University Ave FL1, Palo Alto, CA 94301, USA.
    • Contact: through expo.dev/contact.
    • Description of the processing: app update checks. Each time an app starts it sends the phone's IP address, platform, app version and a random installation identifier, and, after a crash, the error message. No client records. Covered by the EU-US Data Privacy Framework.
  8. Anthropic, PBC
    • Address: 548 Market St, PMB 90375, San Francisco, CA 94104, USA.
    • Contact: privacy@anthropic.com, or the Data Protection Officer at dpo@anthropic.com.
    • Description of the processing: AI suggestions for the coach. The current versions of both apps have every AI feature switched off. An older app version that hasn't been updated can still send a request when the coach uses one of its AI features: the training context of the client concerned (goals, recent sessions, the current program, check-in figures), to return a suggestion the coach reviews. Anthropic's commercial terms exclude using that data for model training. USA, under the standard contractual clauses in Anthropic's data processing addendum, Module Three for transfers from a processor to a processor. Anthropic is not certified under the EU-US Data Privacy Framework. We tell the coach at least 30 days before switching any AI feature back on, under Part 1, point 5.

Part 3. Transfer clauses for coaches outside the EU and the EEA

This part applies only to a coach described in Part 1, point 10. It is Module Four (transfer processor to controller) of the European Commission's standard contractual clauses for transfers of personal data to third countries, adopted by Commission Implementing Decision (EU) 2021/914 of 4 June 2021 (OJ L 199, 7.6.2021, p. 31). We use the official text of the clauses that apply to Module Four unchanged. We have left out the text of the other modules and the options we haven't chosen, and filled in the governing law and the courts. The numbers in brackets, such as (1), point to the footnotes of the official text, listed after Clause 18. The data exporter is Petar Ivanov Tech EOOD and the data importer is the coach (Annex I.A below).

SECTION I

Clause 1: Purpose and scope

(a) The purpose of these standard contractual clauses is to ensure compliance with the requirements 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 (General Data Protection Regulation) (1) for the transfer of personal data to a third country.

(b) The Parties:

  • (i) the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and
  • (ii) the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)

have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).

(c) These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.

(d) The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.

Clause 2: Effect and invariability of the Clauses

(a) These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.

(b) These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.

Clause 3: Third-party beneficiaries

(a) Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:

  • (i) Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
  • (ii) Clause 8 – Module One: Clause 8.5 (e) and Clause 8.9(b); Module Two: Clause 8.1(b), 8.9(a), (c), (d) and (e); Module Three: Clause 8.1(a), (c) and (d) and Clause 8.9(a), (c), (d), (e), (f) and (g); Module Four: Clause 8.1 (b) and Clause 8.3(b);
  • (iii) Clause 9 – Module Two: Clause 9(a), (c), (d) and (e); Module Three: Clause 9(a), (c), (d) and (e);
  • (iv) Clause 12 – Module One: Clause 12(a) and (d); Modules Two and Three: Clause 12(a), (d) and (f);
  • (v) Clause 13;
  • (vi) Clause 15.1(c), (d) and (e);
  • (vii) Clause 16(e);
  • (viii) Clause 18 – Modules One, Two and Three: Clause 18(a) and (b); Module Four: Clause 18.

(b) Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.

Clause 4: Interpretation

(a) Where these Clauses use terms that are defined in Regulation (EU) 2016/679, 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.

(c) These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.

Clause 5: Hierarchy

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

Clause 6: Description of the transfer(s)

The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B.

Clause 7 – Optional: Docking clause

[Not used. The Parties have not chosen this optional clause.]

SECTION II – OBLIGATIONS OF THE PARTIES

Clause 8: Data protection safeguards

The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses.

8.1 Instructions

(a) The data exporter shall process the personal data only on documented instructions from the data importer acting as its controller.

(b) The data exporter shall immediately inform the data importer if it is unable to follow those instructions, including if such instructions infringe Regulation (EU) 2016/679 or other Union or Member State data protection law.

(c) The data importer shall refrain from any action that would prevent the data exporter from fulfilling its obligations under Regulation (EU) 2016/679, including in the context of sub-processing or as regards cooperation with competent supervisory authorities.

(d) After the end of the provision of the processing services, the data exporter shall, at the choice of the data importer, delete all personal data processed on behalf of the data importer and certify to the data importer that it has done so, or return to the data importer all personal data processed on its behalf and delete existing copies.

8.2 Security of processing

(a) The Parties shall implement appropriate technical and organisational measures to ensure the security of the data, including during transmission, and protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access (hereinafter ‘personal data breach’). In assessing the appropriate level of security, they shall take due account of the state of the art, the costs of implementation, the nature of the personal data (7), the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects, and in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner.

(b) The data exporter shall assist the data importer in ensuring appropriate security of the data in accordance with paragraph (a). In case of a personal data breach concerning the personal data processed by the data exporter under these Clauses, the data exporter shall notify the data importer without undue delay after becoming aware of it and assist the data importer in addressing the breach.

(c) The data exporter shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

8.3 Documentation and compliance

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

(b) The data exporter shall make available to the data importer all information necessary to demonstrate compliance with its obligations under these Clauses and allow for and contribute to audits.

Clause 9: Use of sub-processors

[Not applicable to Module Four.]

Clause 10: Data subject rights

The Parties shall assist each other in responding to enquiries and requests made by data subjects under the local law applicable to the data importer or, for data processing by the data exporter in the EU, under Regulation (EU) 2016/679.

Clause 11: Redress

(a) The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.

Clause 12: Liability

(a) Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.

(b) Each Party shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages that the Party causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter under Regulation (EU) 2016/679.

(c) Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.

(d) The Parties agree that if one Party is held liable under paragraph (c), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.

(e) The data importer may not invoke the conduct of a processor or sub-processor to avoid its own liability.

Clause 13: Supervision

[Not applicable to Module Four.]

SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES

Clause 14: Local laws and practices affecting compliance with the Clauses

(where the EU processor combines the personal data received from the third country-controller with personal data collected by the processor in the EU)

(a) The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.

(b) The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:

  • (i) the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
  • (ii) the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards (12);
  • (iii) any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.

(c) The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.

(d) The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.

(e) The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).

(f) Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.

Clause 15: Obligations of the data importer in case of access by public authorities

(where the EU processor combines the personal data received from the third country-controller with personal data collected by the processor in the EU)

15.1 Notification

(a) The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:

  • (i) receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
  • (ii) becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.

(b) If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.

(c) Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).

(d) The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.

(e) Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.

15.2 Review of legality and data minimisation

(a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).

(b) The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.

(c) The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.

SECTION IV – FINAL PROVISIONS

Clause 16: Non-compliance with the Clauses and termination

(a) The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.

(b) In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).

(c) The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:

  • (i) the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
  • (ii) the data importer is in substantial or persistent breach of these Clauses; or
  • (iii) the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.

In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.

(d) Personal data collected by the data exporter in the EU that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall immediately be deleted in its entirety, including any copy thereof. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.

(e) Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.

Clause 17: Governing law

These Clauses shall be governed by the law of a country allowing for third-party beneficiary rights. The Parties agree that this shall be the law of Bulgaria.

Clause 18: Choice of forum and jurisdiction

Any dispute arising from these Clauses shall be resolved by the courts of Bulgaria.

Footnotes of the official text

  • (1) Where the data exporter is a processor subject to Regulation (EU) 2016/679 acting on behalf of a Union institution or body as controller, reliance on these Clauses when engaging another processor (sub-processing) not subject to Regulation (EU) 2016/679 also ensures compliance with Article 29(4) of Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data, and repealing Regulation (EC) No 45/2001 and Decision No 1247/2002/EC (OJ L 295, 21.11.2018, p. 39), to the extent these Clauses and the data protection obligations as set out in the contract or other legal act between the controller and the processor pursuant to Article 29(3) of Regulation (EU) 2018/1725 are aligned. This will in particular be the case where the controller and processor rely on the standard contractual clauses included in Decision 2021/915.
  • (7) This includes whether the transfer and further 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 or offences.
  • (12) As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

Annex to Part 3

Annex I.A: List of parties

Data exporter(s):

  1. Petar Ivanov Tech EOOD
    • Name: Petar Ivanov Tech EOOD (Петър Иванов Тех ЕООД), UIC 205390030, operating Macrocycle.
    • Address: Ovcha Kupel 2, bl. 39, ent. A, ap. 64, Ovcha Kupel district, 1632 Sofia, Bulgaria.
    • Contact person's name, position and contact details: Petar Ivanov, Manager, getmacrocycle@gmail.com, phone +359 887 652 350.
    • Activities relevant to the data transferred under these Clauses: hosting the coach's client records in the EU on the coach's behalf (Part 2) and making them available to the coach in the Macrocycle Coach app.
    • Signature and date: as in Part 2, Annex I.
    • Role (controller/processor): processor.

Data importer(s):

  1. The coach
    • Name: the coach, or the coach's company, that accepted this agreement, under the name held on the coach account.
    • Address: the address the coach gives us on request or on an invoice.
    • Contact person's name, position and contact details: the coach, at the coach account's email address.
    • Activities relevant to the data transferred under these Clauses: the coach's training business, for which the coach reads and manages client records in the Macrocycle Coach app.
    • Signature and date: as in Part 2, Annex I.
    • Role (controller/processor): controller.

Annex I.B: Description of transfer

Categories of data subjects whose personal data is transferred: as in Part 2, Annex II.

Categories of personal data transferred: as in Part 2, Annex II.

Sensitive data transferred (if applicable) and applied restrictions or safeguards: data concerning health, as in Part 2, Annex II, with the safeguards described there and in Part 2, Annex III.

The frequency of the transfer: continuous. Each time the coach's app syncs with the server, it receives the coach's current records.

Nature of the processing: the records stay stored in the EU (Frankfurt). The coach's phone downloads and keeps a working copy, and sends the coach's changes back.

Purpose(s) of the data transfer and further processing: to let the coach use Macrocycle for their training business.

The period for which the personal data will be retained: in our systems, as in Part 2, Annex II, "Duration of the processing". The copy on the coach's phone is removed when the coach signs out, deletes the app or deletes the account.