Skip to main content

Partner Data Processing Agreement

Version 2026-11-15 · Last updated: November 15, 2026

This agreement governs the processing of personal data carried out by a partner in the Flatzer partner program when it accesses, through the Flatzer platform, the agents of its Customers and the personal data they contain. The partner accepts it during its sign-up to the program, and acceptance is a condition for accessing the agent of any Customer.

1. Parties

Flatzer.

Legal company name:
FREAKMAN VENTURES SL
Legal form:
Sociedad Limitada Unipersonal
Trading name:
Flatzer
Spanish tax ID (NIF):
B05749767
Registered office:
Plaza Villa de Castelldefels, 1, planta 9, puerta A4, 29006 Málaga, España
Commercial Registry:
Registro Mercantil de Málaga, hoja MA-201773, inscripción 1.ª
Contact email:
team@flatzer.com
Contact telephone:
+34 639 370 083

The partner. The natural or legal person admitted to the partner program who accepts this agreement in the Partner Portal, with the identification details recorded in its sign-up.

Each Customer. The Customer whose agent the partner manages under the terms of section 5 is the controller. It is also the beneficiary of the obligations the partner assumes in this agreement and may directly enforce their performance.

2. Definitions

  • Customer: the business that holds a Flatzer agent to which the partner has access.
  • End User: the person who converses with a Customer's agent or provides it with their data, for example by leaving their contact details, attaching a document or booking an appointment.
  • Platform: the Flatzer service, which includes the user area, the Partner Portal (partners.flatzer.com), the support inbox, the health alerts and the "View as the client" feature.
  • Customer Data: the personal data that Flatzer processes on behalf of the Customer in its agent and to which the partner may have access through the Platform. Section 8 sets them out in detail.
  • Link: the relationship recorded in the Platform that allows the partner to access a Customer's agent, either because the partner created it (created link) or because the Customer granted it to the partner (granted link).
  • Partner Team: the persons whom the partner registers in the Portal with one of these roles: owner, admin, member or support.
  • Annex: the "Data Processing Annex for Processing on Behalf of Customers" published on the Flatzer website, in its current version, which governs the processing Flatzer carries out as processor for its customers.
  • Program Terms: the "Partner Program Terms" and, in the Agency modality, also the "Agency Program Terms".
  • GDPR: Regulation (EU) 2016/679.
  • LOPDGDD: Organic Law 3/2018 of 5 December on the Protection of Personal Data and Guarantee of Digital Rights (LOPDGDD).

3. Scope

This agreement applies only when the partner, or any member of its team, accesses Customer Data. It does not matter in which modality the partner participates or whether the access is to consult the data, configure it or provide support.

It does not apply to activity that does not involve accessing Customer Data, in particular that of partners in the Referral modality, who never access agents. Nor does it apply to:

  • recommendations, attributions, opportunity registration and commissions, which do not involve End User data;
  • the partner's own agent, for which the partner is the Customer and to which the Annex applies;
  • the contact details of prospects and opportunities that the partner and Flatzer exchange to manage the program. Each of them processes such data as an independent controller, and Flatzer does so in accordance with its Privacy Policy.

If a partner that did not access Customer Data obtains a Link, this agreement applies to it from that moment.

4. Role of each party

The Customer is the controller of the Customer Data. It decides for what purposes and how they are processed.

Flatzer processes the Customer Data as processor for the Customer, in accordance with the Annex. When the Customer grants access to a partner, Flatzer executes that instruction: it opens access with the permissions the Platform assigns to partners, closes it when the Customer revokes it and logs each access.

The partner processes the Customer Data as processor for the Customer, on the Customer's behalf and not on behalf of Flatzer. Flatzer does not engage the partner as its sub-processor, and the partner is not part of the list of sub-processors in the Annex.

Agency modality. The chain is the one set by the Agency Program Terms:

  • the Customer is the controller;
  • the agency is its processor;
  • Flatzer is the agency's sub-processor.

The agency must have, with each Customer, a processing contract in accordance with Article 28 GDPR and the Customer's authorisation to subcontract Flatzer. The processing Flatzer carries out on behalf of the agency is governed by the Annex, which applies to the agency as contracting party, and by section 22.

If the partner processes Customer Data for its own purposes or in breach of the Customer's instructions, it shall be considered a controller in respect of that processing and shall be liable for it (art. 28.10 GDPR and art. 33.2 LOPDGDD).

5. How the processing engagement with each Customer arises

The partner may only access a Customer's agent by means of a Link. There are two ways to obtain one.

5.1 Created link. Before creating an agent that will process data of real End Users, the partner must have a documented engagement from the business: a contract, an order or a written acceptance covering the creation and management of the agent. Flatzer may ask the partner to provide evidence of it.

5.2 Before handover and in the Agency modality. While the agent remains in the partner's organisation pending its handover, and permanently in the Agency modality, the partner is the party contracting the Service with Flatzer and the agency regime of section 4 applies. When the integrator hands the agent over to a Customer that contracts with and pays Flatzer directly, any access the partner retains is governed by paragraph 5.3.

5.3 Granted link. The Customer engages the partner to process the Customer Data when it does any of the following:

  • grants it access from Settings › Team & accounts;
  • accepts an access request from the partner;
  • receives an agent created by the partner.

The engagement covers the permissions granted. By that act, the Customer accepts the obligations the partner assumes in its favour in this agreement. That acceptance and this agreement form the processing contract between the Customer and the partner in electronic form (art. 28.9 GDPR). Flatzer keeps a record of who granted the access, when and under which version of this agreement.

5.4 Own contract. The Customer and the partner may sign their own processing contract. In that case, this agreement operates as a minimum. If the two texts conflict, the one that better protects the data subjects prevails. Sections 10, 11 and 13 always apply to any access through the Platform.

5.5 Revocation. The Customer may revoke the partner's access at any time from Settings › Team & accounts. Revocation takes immediate effect in the Platform. The obligations in sections 20 and 26 remain in force afterwards. Revocation does not affect the commercial relationships between the Customer and the partner, which are governed by their own agreements.

6. Subject matter, nature and purpose

Subject matter. The engagement consists of processing the Customer Data to the extent necessary to implement, configure, maintain and support the Customer's agent in the Platform.

Nature. The processing consists of:

  • consulting and accessing the Customer Data;
  • organising it;
  • modifying the agent's configuration;
  • intervening in conversations where the permissions granted and the Platform allow it;
  • communicating with the Customer;
  • erasing data when the Customer so instructs.

It is carried out exclusively with the Platform's tools: the Partner Portal, the support inbox, the health alerts and the "View as the client" feature.

Purpose. The sole purpose is to provide the Customer with the implementation, configuration and support services it has engaged the partner to provide. Any other purpose is prohibited.

7. Duration

The engagement with each Customer begins when the Link arises and ends upon the first of the following events:

  • revocation of access by the Customer;
  • unlinking by the partner;
  • termination of the agent or the end of the Customer's subscription;
  • the end of the partner's participation in the program.

During a suspension under section 23 there is no access.

When the engagement ends, the obligations of confidentiality, erasure and liability remain in force, as does the obligation to cooperate on breaches and claims relating to the period in which there was access.

8. Data processed and categories of data subjects

8.1 Types of data. Depending on the features the Customer has enabled, and consistently with section 4 of the Annex, the partner may access:

  • Conversations: the messages between End Users and the agent, the transcriptions of voice messages and the contents of attachments.
  • Leads: name, email address, telephone number and any other data provided by the End User, together with their stages, notes and ratings (scoring).
  • Documents: the files uploaded by End Users.
  • Bookings and calendar: name, contact details, time slot and optional note of each booking, and its technical record in the Platform. The partner does not access the calendars or cloud storage services that the Customer has connected beyond what the Platform displays.
  • Agent configuration: may include data of the Customer's staff, such as names, telephone numbers or email addresses, and content from its knowledge base.
  • Customer's users: the name and role of the Customer's people who appear in the Platform.

8.2 Special categories. The Platform is not intended for processing special categories of data, but End Users may disclose them on their own initiative, for example health data in a clinic's agent. The partner will not request them, will not copy them and will only access them when strictly necessary for support.

8.3 Data subjects. The data may relate to:

  • the Customer's End Users: visitors, customers, prospective customers and persons who book an appointment;
  • the Customer's staff and users;
  • third parties mentioned in conversations or documents.

9. Documented instructions

The partner processes the Customer Data only on the documented instructions of the Customer, including with regard to international transfers. The only exception is where Union or Member State law requires it to do otherwise; in that case, it will inform the Customer before processing the data, unless that same law prohibits it.

The Customer's documented instructions are:

  • this agreement;
  • the permissions granted in the Platform;
  • the agent configuration decided by the Customer;
  • the Customer's written requests through the Platform or by email;
  • in the Agency modality, the contract between the agency and the Customer.

Instructions coming from End Users, from other third parties or from Flatzer in its own interest are not instructions of the Customer. Flatzer may only give directions on the security and operation of the Platform and on compliance with this agreement.

If the partner considers that an instruction infringes the GDPR or other data protection law, it will immediately inform the Customer and may stop executing it until the Customer confirms or modifies it.

The partner may not do any of the following without the Customer's instruction:

  • change the conversation retention period;
  • connect or disconnect integrations;
  • enable features that extend the processing, such as voice, documents or copying files to the cloud.

10. Prohibition on using the data for own purposes

The partner may not use the Customer Data for its own purposes or those of third parties. In particular, it may not:

  • Use them with artificial intelligence outside the Platform: train, fine-tune, evaluate or improve it, whether its own or a third party's, or include the data in instructions (prompts), datasets or tool tests that are outside the Platform.
  • Market to End Users: send them commercial communications, promotions or surveys of its own or of third parties, or add them to its lists, its CRM or advertising audiences.
  • Exploit them: sell, transfer, license or enrich them, combine them with other sources or use them for profiling.
  • Put them to another use: use one Customer's data in another Customer's agent or in demonstrations, sales materials or case studies. The only exception is data that has been effectively anonymised, and only with the Customer's written authorisation.
  • Act in its own name: address End Users in its own name. It may only attend to them within the Customer's service, on the Customer's behalf and through the channels the Customer has configured.

This does not prevent the partner from using the general technical knowledge it acquires, provided it does not contain personal data.

11. Processing within the Platform and prohibition on exporting

The partner processes the Customer Data only within the Platform. Outside it, the partner may not download, copy, screenshot, forward, paste into other tools or store them.

Exception. Taking data out is permitted where strictly necessary for the support the Customer has requested, for example to reproduce an incident, under these conditions:

  • the bare minimum is extracted, pseudonymised where possible;
  • it is stored in systems under the partner's control with the measures in section 14;
  • it is never entered into artificial intelligence tools outside the Platform;
  • it is erased as soon as the incident is resolved and, at the latest, after 30 days.

To report incidents to Flatzer, the partner will identify the agent and the conversation by their reference in the Platform, without copying their content. Flatzer's support channel is not a means for sending End Users' personal data.

If the Customer needs an export of its data, it will carry it out itself or the export will be delivered directly to it, or to whomever it designates, in accordance with its instructions.

12. Confidentiality and Partner Team

The partner guarantees that all persons authorised to process Customer Data have committed themselves in writing to confidentiality or are under a statutory obligation of confidentiality. That duty continues after they cease to work for the partner (art. 28.3.b GDPR and art. 5 LOPDGDD).

Only team members registered by name in the Portal may access, each with their own personal account. Shared accounts are prohibited.

The partner assigns each member the minimum role necessary: owner, admin, member or support. It also limits their scope to the agents on which they need to work. The support role may read and reply to conversations, but does not access the agent's documents or technical logs and may not modify its configuration.

The partner trains and informs its team about these obligations, including the access log in section 13.

The partner will withdraw the access of any member who stops working with it or no longer needs it, without undue delay and within a maximum of 24 hours.

The partner is liable for the acts of its team members as for its own.

13. Access log and "View as the client"

Flatzer logs every access by the partner and its team to a Customer's agent, with the name and role of the person accessing and without their IP address. It retains the log for 12 months, and the Customer may consult it at any time.

The partner will inform its team members that their accesses are logged and visible to the Customer. Flatzer processes that data in accordance with its Privacy Policy.

The "View as the client" feature is read-only and is logged. The partner will only use it for a specific support need, never to monitor or browse the agent in general, and will not attempt to circumvent its read-only nature.

The shared support inbox and the health alerts may only be used for the purposes in section 6. The "Notify the client" feature may only be used to contact the Customer's contacts about the operation of its agent.

The partner will not attempt to:

  • access agents with which it has no Link;
  • circumvent the permissions of its role;
  • extract data by automated means;
  • use Platform interfaces that Flatzer does not make available to it.

14. Security measures

Platform. Flatzer applies to the Platform the technical and organisational measures described in section 5 of the Annex, including encryption in transit, per-customer isolation and access controls.

Partner. The partner applies to its devices, accounts and organisation measures appropriate to the risk in accordance with Article 32 GDPR, taking into account the state of the art, the costs and the nature of the data. As a minimum, it:

  • Uses strong, unique passwords, stored in a password manager, and a second authentication factor whenever the Platform or the provider it signs in with offers one.
  • Uses up-to-date devices, with screen lock and disk encryption.
  • Does not use public or shared devices.
  • Applies least privilege, in accordance with section 12.
  • Does not use insecure networks without protection.
  • Has a procedure for detecting and notifying breaches, in accordance with section 19.
  • Reviews its team's accesses at least once every quarter.

The partner will not carry out security testing on the Platform without Flatzer's written authorisation.

15. Other processors

Flatzer's sub-processors. They are those listed in section 6 of the Annex. They are sub-processors of Flatzer, not of the partner, and the partner does not have to engage them. In the Agency modality, the agency will inform its Customer of that relationship and of any changes to it, in accordance with Article 28.2 GDPR.

The partner's external collaborators. Each Customer grants the partner a general written authorisation to register external collaborators, whether self-employed professionals or companies, as members of its team, under these conditions:

  • Each collaborator is registered in the Portal with their name and role, and appears in the access log.
  • The partner imposes on them, by written contract, the same obligations it assumes in this agreement (art. 28.4 GDPR).
  • The partner remains fully liable to the Customer for what the collaborator does.
  • The partner informs the Customer, upon the Customer's request, which external collaborators have access to its agent.
  • The Customer may object to a collaborator on reasonable data protection grounds. If it does so, the partner withdraws that person's access to its agent.

Apart from the above, the partner does not subcontract any processing of Customer Data. This includes not using third-party tools with that data, in accordance with section 11.

16. International transfers

Transfers made by Flatzer's sub-processors are governed by section 7 of the Annex.

Remote access to Customer Data from outside the European Economic Area is an international transfer. The partner and its team will only access from a third country if one of these conditions is met:

  • there is an adequacy decision of the European Commission, including the importer's certification under the EU-U.S. Data Privacy Framework where applicable;
  • the standard contractual clauses of Commission Implementing Decision (EU) 2021/914 have been signed, in the relevant module, together with the necessary supplementary measures;
  • there is another appropriate safeguard under Article 46 GDPR.

Where United Kingdom or Swiss law applies, the equivalent instruments will be used.

A partner established outside the European Economic Area will declare this in its sign-up and will sign the applicable clauses before its first access. Flatzer will provide the template upon request and may make access conditional on that signature.

The partner will notify Flatzer and the Customer if the location from which it accesses changes and that change gives rise to a transfer.

17. Data subjects' rights

The partner assists the Customer, by appropriate technical and organisational measures, in responding to data subjects' requests (art. 28.3.e GDPR).

If the partner directly receives a request from a data subject, it will not resolve it itself, but will forward it to the Customer within a maximum of 2 business days, with the information necessary to identify it. The request may be for access, rectification, erasure, objection, restriction, portability or relate to automated decisions.

In the Agency modality, the agency handles it as agreed with its Customer.

The partner will execute without delay, within the Platform, the Customer's instructions for responding to those rights, for example correcting or erasing a lead. Flatzer assists the Customer in accordance with section 9 of the Annex.

18. Assistance with security, breaches and data protection impact assessments

The partner assists the Customer in complying with the obligations under Articles 32 to 36 GDPR:

  • security of processing;
  • notification and communication of breaches;
  • the data protection impact assessment;
  • prior consultation with the supervisory authority.

It does so taking into account the nature of the processing and the information available to it, and in particular provides the Customer with:

  • information about its accesses;
  • its security measures;
  • its collaborators;
  • the locations from which it accesses.

The partner will cooperate with the supervisory authorities when required to do so (art. 31 GDPR).

19. Personal data breaches

The partner will notify Flatzer, at team@flatzer.com, and the Customer of any personal data breach affecting Customer Data. It will do so without undue delay and, in any event, within a maximum of 24 hours of becoming aware of it. This includes:

  • the loss of a device;
  • the compromise of a team member's credentials;
  • unauthorised access;
  • sending data to the wrong destination.

The notification will include, to the extent known, the following (art. 33.3 GDPR):

  • the nature of the breach;
  • the categories and approximate number of data subjects and records concerned;
  • a contact point;
  • the likely consequences;
  • the measures taken or proposed.

If not all the information can be provided at the same time, it will be provided in phases without further delay.

The partner will immediately take measures to contain the breach:

  • changing passwords;
  • withdrawing the affected accesses;
  • erasing improper copies.

In addition, it will preserve the evidence and cooperate in the investigation.

Notifying the supervisory authority and the data subjects is the responsibility of the Customer. The partner will not do so unless instructed in writing by the Customer or required by law. Nor will it make public statements mentioning the Customer or Flatzer without their agreement, unless required by law.

Flatzer will forward to the Customer the notifications it receives and may suspend access in accordance with section 23.

20. End of the engagement: erasure and return

When the engagement with a Customer ends, Flatzer withdraws the partner's access to the agent in the Platform.

The Customer Data remains in the Customer's account in the Platform, under its control, and follows the retention period described in section 8 of the Annex. For this reason there is no need to return data that never left the Platform.

Within 15 days following the end of the engagement, the partner will erase any copy it retains outside the Platform under section 11. It will certify this in writing if the Customer or Flatzer so requests.

If Union or Member State law requires it to retain any data, the partner will inform the Customer and will keep it blocked, solely for that purpose and for as long as that obligation lasts (art. 28.3.g GDPR and arts. 32 and 33 LOPDGDD).

Agency modality. When the agency stops managing an agent or leaves the program, the agent and its data are handed over to the Customer or to whomever the Customer designates, in accordance with its instructions, including the option for the Customer to continue with Flatzer directly. Flatzer will only deliver an export of Customer Data to the agency if the agency remains the Customer's processor and acts on its instructions, which the agency warrants.

The access log in section 13 is retained for 12 months, even if the engagement has ended.

21. Audits and information

The partner will make available to the Customer all information necessary to demonstrate compliance with Article 28 GDPR. It will allow for and contribute to audits, including inspections, conducted by the Customer or by an auditor mandated by it (art. 28.3.h GDPR).

Audits are governed by these rules:

  • They will be announced 30 days in advance.
  • They will be carried out during business hours.
  • They will be limited to one per year, unless there is a personal data breach, an authority requires it or there are reasonable indications of non-compliance.
  • The auditor will maintain confidentiality.
  • Their cost is borne by the Customer, unless a serious non-compliance is detected.

Flatzer may ask the partner for information or written confirmation that it complies with this agreement, for example:

  • the list of its team;
  • the locations from which it accesses;
  • the erasure of copies.

The partner will respond within a maximum of 10 business days. Flatzer may review the access log to detect anomalous use.

The partner will maintain, where it is required to do so, a record of processing activities as processor (art. 30.2 GDPR and art. 31 LOPDGDD). It will communicate to Flatzer, in the Portal or at team@flatzer.com, a contact person for data protection matters and, if it is required to designate one, its data protection officer (art. 37 GDPR and art. 34 LOPDGDD).

22. Flatzer's commitments

22.1 Access control. As processor for the Customer, Flatzer:

  • only opens access to the partner when the Customer grants it or the partner creates the agent under its engagement;
  • withdraws access as soon as the Customer revokes it;
  • maintains the access log;
  • applies the security measures in the Annex;
  • keeps the list of sub-processors up to date.

22.2 Changes to the Platform. Flatzer will inform the partner of changes to the Platform that materially alter how it accesses the Customer Data.

22.3 Agency modality and agents pending handover. In the Agency modality, and for agents created by the partner while they are pending handover, Flatzer acts as the partner's sub-processor. In addition to complying with the Annex, Flatzer:

  • (a) Instructions: processes the Customer Data only according to the documented instructions the partner gives it on behalf of the Customer, embodied in the agent's configuration.
  • (b) Confidentiality: guarantees the confidentiality of its authorised personnel.
  • (c) Breaches: notifies the partner, without undue delay, of personal data breaches affecting the Customer Data of its agents, with the information referred to in Article 33.3 GDPR available to it.
  • (d) Assistance: assists the partner, with the information available to it, in responding to data subjects' rights and with the obligations under Articles 32 to 36 GDPR.
  • (e) End of the engagement: when the engagement ends, erases or hands over the data in accordance with section 20 of this agreement and section 8 of the Annex.
  • (f) Audits: makes available to the partner the information necessary to demonstrate compliance and allows audits on terms equivalent to those of section 21.
  • (g) Sub-processors: gives reasonable advance notice of intended changes to the list of sub-processors, by notice in the Portal or by email, so that the partner can inform its Customer and object. If the partner objects on reasonable grounds, the parties will seek an alternative. If they do not find one, the partner may terminate the affected agents in accordance with the Program Terms.

23. Suspension of access

Flatzer may suspend the access of the partner, or of a member of its team, to one or more agents in any of these cases:

  • there are indications of non-compliance with this agreement;
  • a personal data breach has occurred;
  • anomalous accesses are detected, such as mass queries;
  • a Customer requests it in respect of its agent;
  • an authority requires it;
  • the partner's participation in the program is suspended.

In urgent cases, it may suspend access without prior notice.

Flatzer will inform the partner and the affected Customers of the suspension. The suspension does not give rise to any right to compensation.

24. Liability

Each party is liable for its own breaches of the GDPR and of this agreement, including liability towards data subjects under Article 82 GDPR.

The partner is liable to the Customer and to Flatzer for the damages, penalties and third-party claims, including those of data subjects, caused by its breaches or those of its team and collaborators. It will hold Flatzer harmless from them, including reasonable defence costs. The limitations of liability in the Program Terms do not benefit the partner in respect of these breaches.

Flatzer's liability to the partner is governed by Flatzer's general Terms and Conditions, as established by the Program Terms. Where the partner acts as a processor engaged directly by the Customer, Flatzer is not liable for the processing carried out by the partner.

Nothing in this agreement limits liability that the law does not permit to be limited, such as that arising from wilful misconduct (art. 1102 of the Civil Code), or the rights of data subjects.

Breaching this agreement is a material breach of the Program Terms. It entitles Flatzer to suspend or terminate the partner's participation, without prejudice to any other action.

25. Relationship with other documents

This agreement supplements the Program Terms and Flatzer's general Terms and Conditions.

In matters of data protection, this agreement prevails over the Program Terms. The processing Flatzer carries out on behalf of the Customer is governed by the Annex, supplemented in the Agency modality by section 22.

Sub-processors, security measures, transfers and data retention in the Platform are governed by the current version of the Annex. This agreement refers to it and does not reproduce its content.

26. Confidentiality after termination

The partner's duty of confidentiality remains in force indefinitely after the engagement ends, access is revoked or its participation in the program ends (art. 5.3 LOPDGDD). It covers the Customer Data and any non-public information about the Customers and the Platform to which it has had access.

The partner will ensure that former members of its team remain bound by that duty.

27. Versions and changes

Each version of this agreement is identified by its date. This is version 2026-11-15. Flatzer keeps a record of the version accepted by each partner.

Flatzer may amend this agreement to adapt it to regulatory changes, to the positions of the authorities, to changes in the Platform or to Customer requirements. It will notify the partner's owner and admins, by email and in the Portal, at least 30 days before the change takes effect, and will indicate what changes. The period may be shorter where required by law or for an urgent security reason; in that case, Flatzer will give notice as soon as possible.

Substantial changes. They require the partner's express acceptance in the Portal. If the partner has not accepted them by the effective date, Flatzer may suspend its access to the Customer Data until it does so. The partner may also stop accessing and request to be unlinked from the agents. Its participation in the program, insofar as it does not involve access to Customer Data, is not affected.

Non-substantial changes. These are, for example, corrections or updates to contact details, and they take effect upon publication. Updates to the Annex follow their own regime.

Previous versions may be requested at team@flatzer.com.

28. Governing law and jurisdiction

This agreement is governed by Spanish law, in particular by the GDPR and the LOPDGDD.

For any dispute between Flatzer and the partner, the parties submit to the courts and tribunals of Spain. This is without prejudice to the powers of the supervisory authorities or to the rights of data subjects to bring proceedings before the courts that have jurisdiction over them (art. 79 GDPR).

29. Contact

Communications provided for in this agreement, including notifications of personal data breaches, are addressed to team@flatzer.com. By post, they may be sent to FREAKMAN VENTURES SL, Plaza Villa de Castelldefels, 1, planta 9, puerta A4, 29006 Málaga, España.

Flatzer will handle enquiries in accordance with the requirements and time limits of the applicable law.