Skip to main content

Data Processing Annex for Processing on Behalf of Customers

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

Effective date for customers who had already contracted the Service: January 1, 2027.

This annex describes the processing Flatzer carries out on behalf of its customers (the businesses that contract the Service) acting as a data processor, and constitutes the processing contract under Article 28.3 of Regulation (EU) 2016/679 (GDPR) between the customer and Flatzer. It forms part of the Service’s contractual relationship and does not replace the Terms and Conditions or the Privacy Policy, which remain available in full. As regards processing on behalf of the customer, this annex prevails over the Terms and Conditions.

1. Identification of the parties

Processor: FREAKMAN VENTURES SL, the company providing the Service under the trade name Flatzer, with the registered office and contact details published on this page.

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

Controller: the customer contracting the Service (the business owner). Regarding the personal data that its visitors and end customers provide through the assistant —conversations, documents, voice messages, and scoring—, the customer acts as the controller and Flatzer solely as a processor handling that data under the customer’s documented instructions.

When the customer contracts the Service through an agency in Flatzer’s partner program, the agency is the party contracting with Flatzer and Flatzer processes the data as the agency’s subprocessor, under the terms of section 13. Partners to which the customer gives access to its agent act as the customer’s processors, not Flatzer’s, in accordance with section 12.

Processor contact: team@flatzer.com

2. Purpose, scope, and duration of the engagement

The engagement covers the processing necessary to deliver the contracted sales assistant: managing the conversations held through the widget and enabled channels, transcribing voice messages when the assistant supports audio, handling the documents shared in conversations, computing conversation and contact scorings, and managing bookings when the customer enables that feature. When the customer connects its Google or Microsoft account, the engagement also includes creating the event for each booked appointment in its calendar and, if the customer turns it on, saving a copy of the files visitors attach to its Google Drive or OneDrive.

Processing of the customer’s account data —registration, billing and payments, support, and service communications— is outside this engagement: Flatzer carries it out as a controller under its Privacy Policy.

Duration: the engagement lasts for as long as the customer keeps the Service contracted and, afterwards, for the time needed to return or delete the data in accordance with section 14.

Terms and Conditions · Privacy Policy

3. Controller instructions

Flatzer processes the data only on the customer’s documented instructions, including with regard to international transfers. Those instructions are embodied in the Service configuration, in the permissions the customer grants in its user area, and in the requests it sends in writing to the processor’s contact:

  • Assistant configuration: catalogue, tone, channels, integrations (including connected Google or Microsoft accounts and the copying of attachments to the customer’s cloud storage), and features enabled by the customer.
  • Retention: the conversation retention period configured by the business owner —30 days by default, adjustable between 1 and 90 days.
  • Earlier deletion: the business owner’s request to bring forward the deletion of conversations and associated data.
  • Limits of the engagement: Flatzer does not process that data for its own purposes; for example, it does not use it to train models. If Union or Member State law requires it to process the data otherwise, it will inform the customer before the processing, unless that law prohibits doing so on important grounds of public interest.
  • Partner access: granting, accepting, or revoking a partner’s access to its agent from Settings › Team & accounts is an instruction from the customer for Flatzer to open or close that access, in accordance with section 12.
  • Instructions contrary to the law: if Flatzer considers that an instruction infringes the GDPR or other Union or Member State data protection provisions, it will immediately inform the customer and may stop carrying it out until the customer amends it or confirms it in writing, justifying its lawfulness. Flatzer is not obliged to carry out a manifestly unlawful instruction.
  • Third-party instructions: Flatzer does not follow instructions from visitors or other third parties. In the Agency modality, instructions are given by the agency on the customer’s behalf, in accordance with section 13.

4. Categories of data, data subjects, and purposes

On behalf of the customer, and only when the corresponding features are active, Flatzer processes:

  • Conversation data: messages exchanged between the business’s visitors and the assistant, including the data those visitors provide (name, contact details, preferences), to handle their enquiries under the customer’s configuration.
  • Voice data: audio from voice messages, sent to Groq for transcription; Groq stores the data in the US and may apply limited exceptional retention under the applicable configuration. The resulting transcript is handled as conversation data.
  • Documents: files and their content shared in conversations, to prepare answers and quotes under the customer’s instructions. When the customer turns on file copying, the files visitors attach are also saved to the “Flatzer” folder in its Google Drive or to the Apps/Flatzer app folder in its OneDrive.
  • Scoring and bookings: conversation and contact scoring results, and the data provided to manage appointments, solely to deliver those features to the business. The name, contact details, and optional note of each booking are written into the event Flatzer creates in the Google or Outlook calendar connected by the customer, and Flatzer does not keep them in its database.
  • Data subjects: the business’s visitors, customers, and prospective customers who converse with the assistant or provide it with their data, including people who book an appointment; the customer’s staff and users whose data appears in the configuration or in the user area; and third parties mentioned in conversations or documents.
  • Special categories: the Service is not designed to process special categories of data (art. 9 GDPR), but visitors may disclose them on their own initiative, for example health data in a clinic’s assistant. It is for the customer to decide whether its assistant may ask for them, to have a legal basis and an Article 9 exception where applicable, and to assess whether it needs an impact assessment. Flatzer processes them with the same measures as the rest of the conversation data.

5. Security measures

Flatzer applies technical and organizational measures appropriate to the risk, including:

  • Encryption in transit: communications with the services use HTTPS/TLS.
  • Per-tenant isolation: agent environments run, where applicable, in containers separated per customer.
  • Access controls: access limited to authorized personnel, with administrative records of the processing.
  • Integration credentials: OAuth tokens for the Google and Microsoft accounts the customer connects are stored encrypted with AES-256-GCM, are used only by Flatzer’s server, and are deleted when the account is disconnected.

6. Subprocessors

The customer grants Flatzer a general written authorization (art. 28.2 GDPR) to engage the subprocessors on this list, which participate depending on the enabled features and the applicable configuration, and those added in accordance with this section. The list is kept consultable and up to date on this page:

  • Groq: voice-message transcription through language models when the assistant supports audio. Privacy policy
  • OpenAI: processing messages and requests through language models when configured for the tenant. Privacy policy
  • xAI: processing messages and requests through language models, as the model configured for the tenant or as a fallback model, and automated review of conversation quality when that feature is active. Privacy policy
  • Hetzner: hosting the infrastructure used to provide the Service: servers on which the agents run and object storage for voice messages and backups, in data centers in Germany and Finland. Privacy policy
  • Tavily: processing web-search queries when the assistant uses that feature. Privacy policy
  • Brave: processing web-search queries when the assistant uses that feature. Privacy policy
  • Cloudflare: delivery and protection network (reverse proxy) through which communications with Flatzer’s website, widget, dashboard, and API pass. Privacy policy
  • Vercel: hosting Flatzer’s website and dashboard, whose server functions, in the Frankfurt region, forward requests to Flatzer’s API. Privacy policy
  • Resend: sending the Service’s emails, including notices to the customer and, when the customer turns on follow-ups, the emails sent to its visitors on its behalf. Privacy policy
  • PostHog: technical and usage measurement of the widget through pseudonymous events, without message text or contact details, on servers in the European Union. Privacy policy
  • Meta: sending and receiving WhatsApp messages through the WhatsApp Business API when the number is registered in Flatzer’s business account. Privacy policy

Subprocessors participate only when the corresponding feature is active. Services the customer connects with its own account are not on this list, because they are not Flatzer subprocessors: its calendar and its documents in Google or Microsoft, the CRMs it connects (HubSpot, Pipedrive, or Airtable), its WhatsApp number when it is in its own Meta account, its Telegram bot, and the language model providers with which it contracts its own key or subscription, such as Anthropic, DeepSeek, Z.AI, OpenAI, or xAI, or its ChatGPT subscription. Following the customer’s instructions, Flatzer sends those services the necessary data, and each provider processes what it receives under the agreement the customer has with it. Stripe, which handles payments for the customer’s account, is not on this list either: Flatzer carries out that processing as a controller, under its Privacy Policy.

Flatzer imposes on each subprocessor, by contract, data protection obligations offering a level of protection equivalent to that of this annex, in particular sufficient guarantees that it will implement appropriate technical and organizational measures (art. 28.4 GDPR). Flatzer remains liable to the customer for its subprocessors’ compliance.

Changes: Flatzer will notify the customer at least 30 days in advance before adding a new subprocessor or replacing an existing one. It will do so by email to the account address and through a notice on this page, stating the subprocessor’s name, the function in which it is involved, and the place of processing. If the change is necessary for an urgent reason of security or Service continuity, such as the sudden discontinuation of a provider, the notice may be shorter and will be given as soon as possible, with the same right to object.

Objection: within the notice period, the customer may object to the change in writing on reasonable data protection grounds. Flatzer and the customer will seek an alternative in good faith, such as not using that subprocessor for the customer or turning off the function in which it is involved. If they do not find one before the change takes effect, the customer may terminate the contract for the affected Service with immediate effect and without penalty, and Flatzer will refund the already-paid portion of the unused period.

Partners in Flatzer’s partner program are not Flatzer subprocessors and are not on this list: they access the customer’s agent only on its instructions and as the customer’s processors, in accordance with section 12.

7. International transfers

Some subprocessors may process data outside the European Economic Area, including the United States. In particular, audio sent to Groq for transcription is stored in the US and may be subject to limited exceptional retention under the applicable configuration; Flatzer does not promise European residency or zero retention for this processor.

Where applicable law requires a transfer mechanism, the relevant mechanism will be used according to the provider and the applicable configuration. The available information can be requested through the contact in this annex.

8. Retention and deletion

Conversations and persisted messages are retained for the retention period configured by the business owner —30 days by default, adjustable between 1 and 90 days— and are automatically and permanently deleted once they exceed that age, unless a legal obligation requires retaining certain data.

The business owner may request the earlier deletion of those conversations and associated data at any time through the processor’s contact. Documents and scorings persisted alongside conversations follow the same retention period. Copies saved in the customer’s calendar, Google Drive, or OneDrive remain under its control and are not deleted by that process; the technical record of each file copy is kept for 90 days.

9. Assistance to the controller

Flatzer assists the customer, through appropriate technical and organizational measures and to the extent the technical configuration allows, in handling data subject requests (access, rectification, deletion, objection, restriction of processing, and portability) relating to the data processed on the customer’s behalf, through the contact in this annex.

If Flatzer receives a request directly from a data subject relating to that data, it will not resolve it on its own: it will forward it to the customer within 2 business days at most, unless the customer has asked it to handle the request on its behalf.

Taking into account the nature of the processing and the information available to it, Flatzer also helps the customer comply with the obligations under Articles 32 to 36 of the GDPR: security of processing, notification of security breaches to the supervisory authority and their communication to data subjects (section 11), data protection impact assessment, and prior consultation with the supervisory authority. To that end, it provides the customer with the available information and documentation about the Service, its security measures, and its subprocessors.

Flatzer cooperates with the supervisory authority when requested to do so (art. 31 GDPR).

10. Confidentiality of Flatzer personnel

Flatzer ensures that the persons authorized to process the customer’s data —its staff and the collaborators working for it— have committed themselves in writing to confidentiality or are under a statutory obligation of confidentiality. That duty continues after their relationship with Flatzer ends and after the engagement ends (art. 28.3.b GDPR and art. 5 LOPDGDD).

Flatzer limits access to the customer’s data to the persons who need it to provide, maintain, and protect the Service, handle a request from the customer, or comply with a legal obligation, and only to the extent necessary for that purpose. It also informs them of their data protection obligations.

11. Personal data breaches

Flatzer will notify the customer of any security breach affecting the data processed on its behalf without undue delay and, in any event, within 24 hours at most of becoming aware of it. This includes breaches reported to it by its subprocessors and those reported to it by a partner with access to the customer’s agent.

The notification will be sent by email to the customer’s account address and, where possible, also through a notice in its user area. It will include, to the extent known:

  • Nature: what happened and when and, where possible, the categories and approximate number of data subjects and records concerned.
  • Contact: the person at Flatzer from whom more information can be obtained.
  • Consequences: the likely consequences of the breach.
  • Measures: the measures taken or proposed to address the breach and mitigate its effects.

If it is not possible to provide all the information at the same time, Flatzer will provide it in phases without further delay. It will also immediately take reasonable measures to contain the breach, preserve the evidence, and document the facts, their effects, and the corrective measures.

It is for the customer, as controller, to decide whether to notify the breach to the supervisory authority and whether to communicate it to data subjects (arts. 33 and 34 GDPR). Flatzer will not do so on its behalf except on the customer’s written instruction or where required by law, and will assist it in accordance with section 9.

Notifying a breach does not imply any acknowledgment of liability by Flatzer. In the Agency modality, the notification is addressed to the agency, in accordance with section 13.

12. Partners with access to the customer’s agent

Flatzer has a partner program with three modalities: Referral, which only recommends Flatzer and never accesses agents; Integrator, which sets up and supports agents paid for by the customer; and Agency, which contracts and pays for its customers’ agents (section 13).

A partner may access the customer’s agent only in one of these two ways: because it created the agent at the customer’s request, or because the customer gave it access from Settings › Team & accounts or accepted its request. Each agent may have only one partner with active access at a time. The customer may revoke access at any time from Settings › Team & accounts, and revocation takes immediate effect.

The partner processes the customer’s data as the customer’s processor and on the customer’s behalf, not on Flatzer’s behalf. It is not a Flatzer subprocessor and is not on the list in section 6. By granting access, accepting the request, or receiving an agent created by the partner, the customer engages the partner to process the data under the terms of the “Partner Data Processing Agreement” published by Flatzer, in the version shown to the customer at that time, and Flatzer keeps a record of that version.

That agreement requires the partner, among other things, to process the data only on the customer’s instructions, not to use it for its own purposes or take it out of the platform, to maintain confidentiality, to notify security breaches within 24 hours at most, and to delete its copies upon termination. The customer may enforce the partner’s compliance directly against the partner. The customer and the partner may also sign their own processing contract; in that case, Flatzer’s agreement operates as a minimum.

As controller, the customer decides which partner to give access to and must choose one that provides sufficient guarantees (art. 28.1 GDPR). Flatzer is not liable for the processing carried out by the partner. It is liable for what falls to it: opening and closing access according to the customer’s instructions, applying the platform’s permissions, logging accesses, and applying the measures in section 5.

The partner’s permissions are limited to what the platform assigns to partners. The support role on the partner’s team can read and reply to conversations, but cannot change the configuration or view documents. The “View as the client” feature is read-only.

Flatzer logs every access by the partner and its team to the agent, including use of “View as the client”, with the name and role of the person accessing and without their IP address. The log is kept for 12 months and the customer can consult it in its user area.

Flatzer may suspend a partner’s access for security reasons or non-compliance, and will inform the customer. If the partner accesses from outside the European Economic Area, the partner data processing agreement requires it to have an appropriate safeguard in place for that transfer beforehand, such as the European Commission’s standard contractual clauses.

Partner Data Processing Agreement

13. Agency modality and agents pending handover

When the customer’s agent is contracted and paid for by an agency in the partner program, the processing chain is as follows: the customer is the controller, the agency is its processor, and Flatzer is the agency’s subprocessor.

In that case, the agency is the party contracting with Flatzer and this annex applies to it. The instructions, notifications, information requests, audits, objections to subprocessors, and other communications provided for in this annex are understood to take place between Flatzer and the agency, which acts on behalf of its customer and must pass on to the customer whatever affects it. Flatzer also assumes toward the agency the commitments in section 22 of the “Partner Data Processing Agreement”.

The agency must have a processing contract with each customer in accordance with Article 28 of the GDPR, have the customer’s authorization to engage Flatzer as a subprocessor, and inform the customer of the subprocessors in section 6 and of changes to them. The agency is liable to its customer for Flatzer’s compliance under the terms of Article 28.4 of the GDPR.

If the agency stops managing the agent, ends its participation in the program, or ceases to exist in fact or in law, the customer may contact Flatzer directly to recover its data, request its deletion, or continue with the Service by contracting it directly. Flatzer will only deliver an export of the customer’s data to the agency if the agency is still the customer’s processor and acts on the customer’s instructions.

The same applies to agents that an integrator creates in its own organization while they are pending handover: until handover, the integrator contracts with Flatzer and the chain is the one described in this section. When the customer receives the agent and contracts it directly, this annex applies between the customer and Flatzer, and any access the integrator retains is governed by section 12.

14. End of the Service: return and deletion

When the Service ends, the customer chooses whether Flatzer returns its data or deletes it. Until the cancellation takes effect, and afterwards for as long as the data remains retained under section 8, the customer may request in writing, through the processor’s contact, a copy of its conversations, leads, documents, and scorings. Flatzer will deliver it within 15 days at most, in a structured, commonly used, and machine-readable format.

When the cancellation takes effect, Flatzer deletes the agent’s runtime environment, container, and volume. Conversations and associated data are automatically and permanently deleted when the retention period in section 8 expires, or earlier if the customer requests their early deletion. If the customer has requested a copy, Flatzer will keep the data for the time needed to deliver it and will delete it afterwards.

External backups of the agent’s environment are automatically deleted when their retention period expires, which depends on the plan: 7 days on Starter, 30 days on Growth, and 90 days on Pro, or on the equivalent tiers of the Agency modality (Essential, Business, and Multi-site). While they exist, they are kept with the same security measures and are not used for any other purpose.

If Union or Member State law requires any data to be retained, Flatzer will inform the customer and keep that data blocked, solely for that purpose and for as long as that obligation lasts (art. 28.3.g GDPR and art. 32 LOPDGDD).

Whatever the customer has saved in its own calendar, Google Drive, or OneDrive remains under its control and is not deleted by this process. The partner access log is kept for 12 months, in accordance with section 12. Flatzer will certify the deletion in writing if the customer so requests.

15. Information, audits, and inspections

Flatzer makes available to the customer all information necessary to demonstrate compliance with Article 28 of the GDPR. The customer may request it through the processor’s contact, including reasonable information about the security measures applied and the current version of the subprocessor list. Flatzer will respond within 10 business days at most.

Flatzer allows for and contributes to audits, including inspections, conducted by the customer or by an auditor mandated by the customer (art. 28.3.h GDPR), under these conditions:

  • Prior notice: audits will be announced in writing at least 30 days in advance, stating their scope.
  • Frequency: no more than one per year, unless there has been a security breach, a supervisory authority requires it, or there are reasonable indications of non-compliance.
  • Form: audits will be carried out during business hours, without disrupting the Service and without access to other customers’ data or to information that would compromise the security of the platform. Flatzer may propose that the audit first be carried out on the available information and documentation; an inspection, on-site or remote, will take place when these are not sufficient.
  • Auditor: if it is not the customer itself, the auditor must be bound by a duty of confidentiality and may not be a competitor of Flatzer.
  • Cost: each party bears its own costs, unless the audit reveals a serious breach of this annex, in which case Flatzer will bear the reasonable cost of the audit.
  • Subprocessors: with respect to them, Flatzer will provide the reports, certifications, and documentation they make available to it.

Flatzer will likewise accommodate inspections by the competent supervisory authorities.

16. Changes to the annex

Each version of this annex is identified by its date. This is version 2026-11-15.

This annex may be updated to reflect the configuration actually contracted, regulatory changes, or changes to the Service; the current version is published on this page with its update date. When a change affects the customer’s rights or Flatzer’s obligations, Flatzer will notify the customer by email and in its user area at least 30 days in advance and will state what is changing. The period may be shorter where required by law. Changes to subprocessors follow the regime in section 6.

If the customer does not agree with a change that is detrimental to it, it may cancel the Service before the change takes effect, without penalty. Earlier versions may be requested through the processor’s contact.

For customers who had already contracted the Service before this version was published, it takes effect on January 1, 2027. The commitments this version adds for Flatzer apply from its publication.

17. Contact

For the queries and requests covered by this annex, you can contact us through:

Processor contact: team@flatzer.com

We will handle queries under the requirements and time limits of applicable law.