Skip to content
Sign in Back to the screen

Data Processing Agreement pursuant to Article 28 GDPR (Glieks)

Version dated 21.10.2026 - Deutsche Fassung (verbindlich)

Courtesy translation. This English version is provided as a service for your convenience only. The German version is the only legally binding version. In the event of any discrepancy or difference in interpretation, the German version shall prevail.

Version management: This Agreement is maintained as a dated version; the version date is shown at the top of the page. The version applicable at the time the contract is concluded is named in the Terms of Use (clause 11.2) and in the order confirmation or the business offer. Any amendment to this Agreement always creates a new version; the previous version remains available for reference for contracts already in force.

Application to private individuals: Where a private individual uses Glieks exclusively for personal or household purposes, the GDPR does not apply to their own content (Article 2(2)(c) GDPR); in that case this Agreement does not apply, and the Privacy Policy applies instead. Where a private individual processes personal data of third parties via Glieks for professional or business purposes, this Agreement also applies to them.


between

the customer who has concluded the main contract for the use of Glieks with the provider (company name and address as stated in the order or the business offer) - "Controller" -

and

Glieks, sole proprietorship (owner and address: see Legal Notice (Impressum)) - "Processor" -

Preamble

This Agreement specifies the data protection obligations of the Parties in connection with the main contract existing between them for the use of the Glieks platform (Terms of Use). It applies to all processing of personal data carried out by the Processor on behalf of the Controller in the course of providing Glieks. The Controller concludes this Agreement by confirming it when placing the order via the website and by confirming it again, in the version then applicable, when its first admin account logs in for the first time; in the case of a business offer, by accepting the offer, which names the applicable version. The Processor stores the time and the version of the confirmation.

Section 1 Subject matter and duration of the Agreement

1.1 The subject matter of this Agreement is the processing of personal data by the Processor for the Controller in the course of providing the services described in Annex 1 (provision of the Glieks platform, execution of tasks in isolated run environments, storage of results and logs).

1.2 The duration of this Agreement corresponds to the term of the main contract. It does not end automatically upon termination of the main contract, but only once the deletion and return obligations under Section 11 have been fully performed.

Section 2 Nature and purpose of the processing, categories of data, data subjects

The nature, purpose and scope of the processing, the categories of personal data and the categories of data subjects are set out in Annex 1. The Controller ensures that the data and tasks it brings in via Glieks are accurately reflected in Annex 1; where new categories of data are added (in particular special categories pursuant to Article 9 GDPR), the Controller informs the Processor before they are processed for the first time. The information in Annex 1 describes the framework provided for by the product, not any knowledge of the content on the part of the Processor.

Section 3 Responsibility and right to issue instructions

3.1 The Controller is solely responsible for assessing the lawfulness of the processing pursuant to Article 6 GDPR and for safeguarding the rights of the data subjects.

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

3.3 Instructions are given in the first instance by this Agreement and its annexes and by the configuration options technically provided for in the platform (assignment of roles and permissions, security settings, deletion functions, release gate, cost limit in the form of a monthly budget). Individual instructions going beyond this are given in text form.

3.4 If the Processor considers an instruction to be unlawful, it informs the Controller without undue delay and may suspend execution until the instruction is confirmed or amended.

Section 4 Confidentiality

The Processor ensures that all persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality (Article 28(3), first subparagraph, point (b) GDPR).

Section 5 Technical and organisational measures

5.1 The Processor implements the technical and organisational measures (TOMs) described in Annex 2 pursuant to Article 32 GDPR in order to ensure a level of security appropriate to the risk.

5.2 The Processor may adapt the TOMs provided that the agreed level of protection is not undercut; it notifies the Controller of any material deterioration.

Section 6 Sub-processing

6.1 The Controller grants the Processor general authorisation to engage the sub-processors listed in Annex 3 (Article 28(2) GDPR).

6.2 If the Processor intends to engage an additional sub-processor or to replace one, it informs the Controller in advance in text form, giving at least four weeks' notice. The Controller may object to the change within this period for an important reason based on data protection law; if no objection is raised, the change is deemed approved. In the case of a justified objection which the Processor is unable to remedy, either Party may terminate the main contract with effect from the date of the change.

6.3 The Processor imposes on the sub-processor, by way of a contract or other legal act under Union or Member State law, the same data protection obligations as set out in this Agreement (Article 28(4) GDPR). The Processor is liable to the Controller for the performance of the sub-processor's obligations.

6.4 The Processor engages sub-processors that process customer data (task content, files, results, account data) only with a place of processing in Germany or in the European Union. A transfer of such data to a third country is not envisaged; should it become necessary in future, this requires a separate supplement to this Agreement (standard contractual clauses or an equivalent instrument) before the first transfer. Search terms and queries that Glieks sends to public sources and search services during research are described in Annex 2 item 12; such services do not receive any customer files.

Section 7 Assistance with data subject rights

The Processor assists the Controller by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Controller's obligation to respond to requests for exercising the data subject's rights laid down in Chapter III GDPR (Article 28(3), first subparagraph, point (e) GDPR). The Processor itself does not respond to requests from data subjects on the merits. For this purpose, it provides the Controller with the tools provided for in the platform: the customer-system-wide request for deletion (search for a person or term across inputs, results, chats and storage, deletion of all matches as a single operation with a deletion record that contains no content; in backup copies, deleted content expires in line with the retention period of the backups) and the complete export (an archive in open formats that can be triggered by an authorised person). In any event, the Controller itself remains the addressee of data subjects' claims for access, rectification and erasure, insofar as it is the controller vis-à-vis them under data protection law.

Section 8 Assistance pursuant to Articles 32 to 36 GDPR

The Processor assists the Controller in ensuring compliance with the obligations pursuant to Articles 32 to 36 GDPR, taking into account the nature of the processing and the information available to the Processor, in particular with regard to the security of processing, the notification of personal data breaches, the data protection impact assessment and the prior consultation of the supervisory authority (Article 28(3), first subparagraph, point (f) GDPR).

Section 9 Notification of personal data breaches

9.1 The Processor undertakes (organisational measure) to notify the Controller of any personal data breach that comes to its attention (Article 33(2) GDPR) without undue delay and at the latest within 24 hours of its discovery, even if not all details have been clarified at that time.

9.2 The notification contains, insofar as known at that time: the nature of the breach, the time of discovery, the scope affected, measures already taken or proposed, and a contact point for queries. The notification is made without transmitting data content, insofar as this is compatible with a proper notification.

9.3 Further findings are provided subsequently without undue delay.

Section 10 Audit rights of the Controller

10.1 The Processor makes available to the Controller all information necessary to demonstrate compliance with the obligations laid down in Article 28 GDPR and allows for and contributes to audits, including inspections, conducted by the Controller or another auditor mandated by the Controller (Article 28(3), first subparagraph, point (h) GDPR).

10.2 As no remote access is set up in production operation and emergency access is only opened on the instruction of the owner (Annex 2 item 4), the Processor fulfils this obligation through a combination of three components, which the Controller uses at its own discretion:

a) Documentation instead of on-site access. A current configuration overview, this TOM annex and - where available - audit reports or certifications by independent third parties.

b) System-generated evidence. The immutable evidence chain maintained in the customer system (available separately in the customer system) and the complete export that can be triggered by an admin, with which the Controller can itself trace the actual processing in its own customer system without the Processor having to inspect it.

c) Scheduled audit. A jointly agreed audit (on site at the hosting partner, as a remote audit or as a questionnaire) after a reasonable notice period (as a rule four weeks), at most once a year without a specific reason, and at shorter notice where there is a specific reason (for example following a breach notified under Section 9).

Section 11 Deletion and return after termination

11.1 After the end of the provision of processing services, the Processor deletes all personal data or, at the choice of the Controller, returns it and deletes existing copies, unless Union or Member State law requires storage of the personal data (Article 28(3), first subparagraph, point (g) GDPR).

11.2 Until its account is deleted, the Controller may request a complete export of all data in open file formats (inputs, results, deletion records, chats, storage, calendar, records and conversation folders as structured data and files); the evidence chain is available separately in the customer system. The Processor deletes mirrored and uploaded files 30 days after the end of the contract; documents for which a statutory retention period is running are retained until that period ends. The Processor deletes chats, conversation folders and results upon deletion of the account (on request to support). A deletion record (time, scope, executing body) is made available to the Controller.

11.3 Log and evidence data without data content (time, identifier, type of action) are retained for evidentiary purposes beyond the deletion of the content for at least 12 months from the end of the contract; they are deleted upon deletion of the customer system.

Section 12 Liability

The liability provisions of the main contract (Terms of Use, clause 9) apply to the liability of the Parties in connection with this Agreement, unless mandatory provisions of the GDPR (in particular Article 82 GDPR in relation to data subjects) conflict with them.

Section 13 Final provisions

13.1 In the event of conflicts between this Agreement and the main contract, this Agreement takes precedence with regard to the processing of personal data.

13.2 Amendments and supplements to this Agreement must be made in text form. This also applies to the annexes, with the exception of the updating of the list of sub-processors governed by Section 6.2.

13.3 German law applies.


Annex 1: Subject matter, duration, nature and purpose of the processing

1. Subject matter. The Processor provides the Glieks platform. It receives tasks in the chat and as a task, has them executed by AI agents in isolated environments, executes scheduled tasks and stores task data, intermediate states, results and logs in the Controller's customer system.

2. Duration. The processing lasts as long as the main contract, plus the run-off period under Section 11.

3. Nature of the processing. Collection, storage, organisation, alteration, retrieval, use and erasure. Data is transmitted to sub-processors under Annex 3, in particular to the respective model provider for the execution of individual model rounds, and, at the user's request, by e-mail to the user's account address; sending to third parties takes place only via a connection set up by the Controller. Deletion takes place via the trash with final deletion after 30 days, or immediately after express confirmation (Annex 2 item 7).

4. Purpose. Execution of the tasks issued by the Controller, provision of results, logs and evidence, and billing in accordance with the price list in force at the relevant time (Terms of Use clause 4.1).

5. Data subjects. Employees and agents of the Controller who use Glieks, as well as persons whose data the Controller brings into tasks and documents, for example customers, business partners or employees of the Controller. Which persons these are in the individual case depends on the content and is determined by the Controller.

6. Types of data. Access and account data of users (name, e-mail address, role, login log), usage and consumption data (time, model, consumption) and the content of the tasks and files brought in by the Controller. The nature and scope of this content are determined solely by the Controller; it may include special categories pursuant to Article 9 GDPR if the Controller brings in such data (Section 2).

7. Place of processing. The data is held in the Controller's customer system on servers of the Processor at Hetzner in Germany. Business customers receive their own customer system (own service process, own database, own keys); single seats are located in a shared customer system in which the separation of accounts is enforced on the server side on every access. Under the business offer, the customer system runs on a dedicated server on request. For individual model rounds, the content required for this purpose is processed by the respective model provider for the duration of the request, depending on the model at IONOS (Germany) or Scaleway (France), unless the Controller sets up its own model access; it is itself responsible for that. Glieks generates images via the IONOS AI Model Hub; video and audio generation runs on computing machines rented per task from IONOS in Germany.

Annex 2: Technical and organisational measures (TOMs)

This annex summarises the technical and organisational measures that the Processor has implemented for Glieks. The Processor continuously develops them further; Section 5.2 applies.

1. Separation of customers. Business customers receive their own customer system (own service process, own database, own keys). Single seats are located in a shared customer system; there, the separation of accounts is enforced on the server side on every access. On request (business offer), the customer system runs on a dedicated server. Programs that Glieks executes for a task run in isolated virtual machines with their own operating system kernel (Firecracker), which are discarded after the run. Conversational replies and simple transformations are processed directly by the service process of the customer system. Research is carried out by the service of the customer system.

2. Access control. Roles and permissions of the customer's users are checked on the server side for every request; login with password, passkey or one-time code; the first access is set up via a one-time password delivered by e-mail; second factor (confirmation via a second device or a time code) for security-relevant confirmations. The Processor expressly recommends setting up a second factor permanently for all users. Steps that Glieks classifies as having an external effect (for example sending, payment, publication) are submitted by Glieks for approval, unless the customer has set automatic execution for the respective route.

3. Encryption. Connections to the platform are encrypted (TLS). Backups in object storage are stored in encrypted form.

4. Access by operations. As a rule, operations staff do not access the content of customer systems (organisational measure); no remote access is set up in production operation. Updates reach the servers only as signed packages. Emergency access to a server is possible only after separate activation. The server reports its technical status without content; in an emergency, on instruction, additionally filtered error lines of the services. When reporting an error, the customer may attach a run log from which identifiers, e-mail addresses and file names have been removed. Access to content for support purposes takes place only after express approval by the customer (organisational measure). A terminal session to the agent program provided for in the product in runs with the customer's own account (start and end are logged) is a function for the customer, not access by operations.

5. Logging and evidence chain. Actions are logged immutably (cannot be overwritten, cannot be deleted); evaluation only in aggregated form at customer system level, with the exception of the abuse check under clause 6.8 of the Privacy Policy (no profiling, see Privacy Policy clause 13). The customer system log is kept for at least 12 months and can be exported by the customer.

6. Backup. Daily encrypted backup in IONOS object storage in Germany; monthly restore test by operations. Retention: 14 daily backups, 8 weekly backups and 12 monthly backups.

7. Deletion concept (two-track). Glieks has three independent deletion routes that serve different purposes:

8. Hardening of the run environments. Closed tool lists for run environments; resource limits; impermissible tool calls are refused and logged; if attack patterns are detected in network traffic, the run environment is terminated immediately. Secrets are kept in a key vault with restricted file permissions and are not logged. Execution environments reach the internet only via an egress with an allow list and logging; further destinations can only be enabled by the customer (Terms of Use clause 7.3).

9. Security incidents. Organisational commitment: notification to the customer at the latest 24 hours after discovery, without content, stating the scope, the blocks put in place and the next steps (Section 9 of this Agreement).

10. Hosting providers. Servers are currently rented from Hetzner Online GmbH in Germany. The Processor reserves the right to use further hosting providers with a place of processing in Germany, for example for geographically separate backup copies, to improve the service or for stable prices; new sub-processors are notified in advance in accordance with Section 6.2 and added to Annex 3. The separation of data between customers is ensured independently of this (item 1).

11. No use for training. According to their contractual terms, the model providers used (currently, for example, IONOS and Scaleway, and where applicable further providers with registered office and processing in the European Union; Annex 3 is authoritative) do not use customer content to train their own models and do not store request and response content permanently (Scaleway: only in the event of malfunctions, for up to two weeks for troubleshooting). The fact sheet of each model access states the registered office, storage location, storage period, use for training and legal basis. The Processor checks these commitments against the provider's contractual documents each time a model access is added (organisational measure).

12. Research and data retrieval. To execute tasks, the Processor queries public sources and services (for example official statistics, specialist and data sources, Google Maps Platform for location questions) and, for web search, search services based in the USA (currently Tavily, Inc.; Brave Software, Inc.; DuckDuckGo, Duck Duck Go, Inc.; Microsoft Bing, Microsoft Corporation). Search queries, location details and queries are transmitted to these services, but no files. In research carried out as part of a task, search queries are limited to a maximum of 300 characters and checked for verbatim excerpts from the customer's documents. The customer data itself is stored and processed in Germany or the European Union. These sources and search services are not sub-processors within the meaning of Annex 3; the legal basis and the basis for the third-country transfer are set out in clause 9a of the Privacy Policy.

Annex 3: List of sub-processors

Sub-processorServicePlace of processingLegal basisStatus
Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, GermanyServer hosting (machines on which the website, customer systems and run environments run)GermanyArticle 28 GDPR, data processing agreement with Hetzneractive
IONOS Cloud GmbH, Elgendorfer Str. 57, 56410 Montabaur, GermanyProvision and operation of language and image models (IONOS AI Model Hub) for the execution of model rounds; computing machines (GPU) rented per task for video and audio generation; object storage for permanent storage and daily encrypted backup. Model inference takes place exclusively in data centres in Germany; prompts and outputs are not logged and not used for trainingProcessing in the EU/EEA; inference in Germany (Berlin data centre); object storage in GermanyArticle 28 GDPR, data protection package of IONOS Cloud GmbH (version 7.4, as of 06/2023; part of the general terms and conditions, applies upon conclusion of the contract)active
IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, GermanyOperation of the Processor's e-mail mailboxes under glieks.ai and sending of system e-mails (one-time password, invitations, confirmations, invoices, notifications, results to the user's own account address)GermanyArticle 28 GDPR, data processing agreement with IONOSactive
Scaleway SAS, 8 rue de la Ville l'Eveque, 75008 Paris, FranceProvision and operation of part of the language models for the execution of model rounds on its own infrastructure without disclosure to third parties; no use of the content for training, no storage of request and response content except in the event of malfunctions (for up to two weeks for troubleshooting)European Union (France, Paris region)Article 28 GDPR, data processing agreement with Scalewayactive

Not included in this list because they are not processors: Stripe Payments Europe, Ltd. (Ireland) handles payments as an independent controller and receives only payment data of the Controller itself, no task content; Cloudflare, Inc. (USA) operates exclusively the name resolution of the domains and receives no customer data; public sources and search services under Annex 2 item 12 receive only search terms.

This list is updated in accordance with Section 6.2 each time a new model access or service provider is added. All sub-processors process customer data in Germany or the European Union; a transfer of customer data to a third country is not envisaged (see Privacy Policy clause 9).


Sources