ALLUV / LEGAL
Privacy Policy.
Last updated: 29 September 2026 · Version 1.0. This policy explains how 4rce.com Digital Technologies GmbH processes personal data in connection with the alluv website and AI services.
1. Scope and privacy principles
alluv is an AI inference and related digital services platform operated by 4rce.com Digital Technologies GmbH. Our direct AI inference services follow two core principles:
- Zero Data Retention for Customer Content; and
- processing of Customer Content and AI-service Operational Data exclusively within the European Union.
Customer Content is processed only to fulfil the requested service. It is not used for model training, fine-tuning, evaluation, advertising or profiling, and it is not intentionally written to persistent application storage, content logs or backups.
2. Controller and contact
For processing where we determine the purposes and means, the controller is:
4rce.com Digital Technologies GmbH
Grafentraubach 910
84082 Laberweinting
Germany
Managing Director: Volker Geith
Commercial Register: Amtsgericht Straubing, HRB 13771
VAT ID: DE459375923
Privacy contact: gdpr@4rce.com
3. Our role under the GDPR
We generally act as controller for account and organisational information, contractual contacts, authentication, billing, customer communications, security information, limited technical usage data and legally required business records.
Where a customer submits personal data within Customer Content and we process it solely to provide the requested service on the customer’s instructions, the customer is normally the controller and 4rce.com Digital Technologies GmbH acts as processor under Article 28 GDPR. Where required, the parties will conclude a Data Processing Agreement before that processing begins.
4. Customer Content
Customer Content includes prompts, source code, documents, files, images, attachments, contextual information, model inputs and model outputs submitted to or generated through the direct alluv AI services.
Customer Content may contain personal data depending on what a customer submits. It is processed only to receive the request, perform the requested computation and return the result. Except where a customer separately provides information for support, we do not:
- retain Customer Content after processing;
- maintain conversation histories containing Customer Content;
- place Customer Content in persistent logs, analytics systems or backups;
- sell Customer Content or use it for advertising or profiling; or
- use it for training, fine-tuning, reinforcement learning, evaluation datasets, benchmarking datasets or service-improvement datasets.
5. Zero Data Retention
Customer Content is processed transiently in volatile processing memory and is not intentionally written to persistent disks, application databases, request or response content logs, observability traces containing payloads, caches for later reuse, backups, archives or model-development datasets.
After a request completes, Customer Content is released from the active application and inference context. Logging and monitoring are configured not to record Customer Content. Historical Customer Content cannot ordinarily be retrieved by our personnel because it is not retained.
Limited non-content metadata may be processed for authentication, billing, usage metering, capacity management, availability, security, abuse prevention and troubleshooting.
6. Operational Data
Operational Data may include a customer’s name, business email address, organisation, account and credential identifiers, billing and contractual information, API request counts, token or usage quantities, timestamps, selected model or service identifier, status and duration information, IP addresses where technically necessary, security information and communications with us.
Operational Data is minimised and does not intentionally contain prompts, submitted source code or documents, model inputs, model outputs or other substantive Customer Content.
7. European Union processing
Customer Content and Operational Data processed as part of the direct alluv AI inference services are hosted, processed and stored exclusively within the European Union. Production inference, monitoring, logging and supporting infrastructure for those services are located in the European Union, and access to that data is restricted to authorised access originating within the European Union.
Subprocessors used for direct AI-service processing must process the relevant personal data within the European Union, act only on documented instructions, implement appropriate safeguards and not use Customer Content for their own purposes.
8. Public website
The public alluv.ai website contains no customer accounts or Customer Content. It is a static website delivered through GitHub Pages (GitHub Inc., USA), which may process technical website-access data such as IP address, browser information, requested URL, referrer and access time. This does not affect the EU-only processing of the direct alluv AI inference services.
The website sets no cookies, uses no analytics, advertising or tracking technology, loads no external fonts, scripts or stylesheets and does not embed third-party content. More information about GitHub’s processing is available in GitHub’s privacy statement.
9. Legal bases
Where we act as controller, we process personal data under:
- Article 6(1)(b) GDPR to establish and perform contracts, administer services, authenticate users, meter usage and provide requested support;
- Article 6(1)(c) GDPR to meet accounting, tax, commercial and other legal obligations;
- Article 6(1)(f) GDPR for security, abuse and fraud prevention, service reliability, business operation and legal claims; and
- Article 6(1)(a) GDPR where consent is required. Consent may be withdrawn with future effect.
10. Retention
Customer Content has no persistent retention period. Account and contract information is retained for the customer relationship and thereafter only as needed for contractual administration, legal claims and statutory obligations. Invoices and accounting records are retained as required under German law.
Limited technical security information may be retained for a proportionate period to detect attacks, investigate incidents, prevent fraud and secure the services. Security records are configured not to contain Customer Content.
11. Customer support
Support is separate from normal AI inference processing. Because Customer Content is not retained, support personnel cannot inspect historical prompts or outputs. A customer may voluntarily provide an example, diagnostic information or reproduce an issue.
Information deliberately submitted by email or another persistent support channel is treated as support information rather than transient Customer Content. It is used only for support and administration, is not used for model training and is retained only as long as required for the support case or legal obligations.
12. Security and breaches
We apply technical and organisational measures appropriate to the risk under Article 32 GDPR. These include encryption in transit, access controls, least privilege, workload separation, network safeguards, monitoring, vulnerability and patch management, incident-response procedures, confidentiality obligations and controls designed to keep Customer Content out of persistent logs and storage.
Where we act as processor, we notify the relevant customer without undue delay after becoming aware of a personal data breach affecting data processed on that customer’s behalf. Where we act as controller, we notify the competent authority and affected individuals where Articles 33 and 34 GDPR require it.
13. Data subject rights
Subject to the GDPR’s requirements and limitations, individuals may have rights of access, rectification, erasure, restriction, portability and objection, rights concerning automated decision-making, and the right to withdraw consent.
Where we act as controller, requests may be sent to gdpr@4rce.com. Where we act solely as processor, requests should normally be directed to the relevant customer acting as controller. Because Customer Content is not retained, it may no longer exist when a later request is received.
You may lodge a complaint with a supervisory authority. The authority responsible for our company is Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 18, 91522 Ansbach, Germany, www.lda.bayern.de.
14. Automated decision-making
We do not use account, billing or Operational Data to make decisions based solely on automated processing that produce legal or similarly significant effects within Article 22 GDPR. Generation of an AI output in response to a customer request does not itself mean that we make such a decision. Customers remain responsible for assessing whether their own use of AI outputs is subject to Article 22 GDPR.
15. Marketplaces and other providers
If a customer accesses alluv through a marketplace, platform or reseller, that third party independently processes data under its own terms and privacy policy. The EU-only commitment in this policy applies to processing performed within the direct alluv AI inference services and does not alter an independent third party’s processing.
16. Changes and contact
We may update this policy to reflect changes to the services, technology, subprocessors or legal requirements. Material changes will be communicated appropriately and the current version will be published here. Changes will not retrospectively turn Customer Content processed under Zero Data Retention into retained content.
For privacy enquiries, data-subject requests or questions about this policy, contact gdpr@4rce.com.