Privacy policy
Co-Dex.eu, NoCode-X and Breezebot privacy policy
Last revised: 8 November 2026. Publication and effective date will be announced under section 14.
Confidentiality and security are core to Co‑Dex.eu BV. With NoCode‑X, we want you to build and run powerful no‑code solutions in a way that is secure, transparent and GDPR‑compliant.
This policy explains how Co-Dex.eu bv handles personal data in its own services, including co-dex.eu, NoCode-X and Breezebot, and how our role differs when we process data on behalf of customers. NoCode-X is our application platform. Breezebot is our own service built on that platform, through which customers can create apps.
We explain in plain language:
- what data we collect,
- why we use it,
- on which legal basis,
- how long we keep it,
- who we share it with (including external LLM providers),
- and what your rights are.
1. Who we are
Controller
Co‑Dex.eu BV
Albert I‑laan 23
8920 Langemark‑Poelkapelle
Belgium
Data Protection Officer (DPO): Wim Barthier
Email: [email protected]
We act as controller for our own processing purposes, such as our business contacts, service accounts and billing. We act as processor for personal data in apps, websites, actions, processes, workflows and storage that customers create, configure or run under their control. That customer is normally the controller. If the customer processes data for another controller, we may act as a sub-processor.
This distinction applies to NoCode-X, Breezebot and customer processing initiated through MCP. Technical logs and support data are classified by their actual purpose: processing on a customer's behalf remains subject to the Data Processing Agreement; processing for our own purposes is described in this notice. Choosing an AI provider or supplying an API key does not alone determine a party's legal role.
The platform measures and customer responsibilities are explained in AI and MCP data flows.
Supervisory authority - One‑Stop Shop
Our lead data protection authority under GDPR is the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit / Autorité de protection des données):
- Website: https://www.gegevensbeschermingsautoriteit.be
- Address: Drukpersstraat 35, 1000 Brussels, Belgium
You can always contact them if you’re unhappy with how we handle your data.
2. Scope of this policy
This notice covers the websites, landing pages, platforms, applications, APIs, AI interfaces, MCP services and other digital services operated or provided by Co-Dex.eu bv, including co-dex.eu, NoCode-X and Breezebot. Service-specific notices may provide further detail. It also covers our business communications, events and contact with suppliers. Physical-site activities described below apply only where those activities take place.
For customer-controlled processing in apps and processes built or operated using our services, the customer's privacy notice explains its purposes and legal basis. Our obligations as processor are set out in the DPA. This notice does not turn us into controller of all information on the platform.
For cookies and similar technologies, consult the cookie information and choices provided on the relevant website. The policy overview links to the other documents governing our services.
3. What personal data we process
Depending on how you interact with us or with apps built on NoCode‑X, we may process:
- Identification data: name, first name, email address, company, role, phone number, (where needed) date/place of birth, ID numbers when legally required (e.g. VAT, national ID in AML contexts).
- Account & platform usage data: username, roles and permissions, workspace/tenant membership, activity timestamps, feature usage, configuration changes.
- Application usage & user‑flow telemetry (for apps and websites built on NoCode‑X):
- pages/screens visited, clicks/actions, navigation paths,
- technical events and performance metrics,
- error messages and correlation IDs,
- identifiers that link events to a user, browser or device.
- Contact & communication data: emails, support tickets, chat messages, phone calls (and, if applicable, call recordings).
- Transaction & billing data: bank account number, payment references, invoice data, subscription details.
- Technical data: IP address, device and browser info, OS, timestamps, security events, cookies/IDs.
- Event data: event registrations, attendance lists, evacuation lists, streaming participation.
- Audiovisual data: CCTV images in or around our offices or event venues, livestream recordings where you appear.
- Supplier data: contact details of suppliers and their staff when we work together.
- Marketing & preference data: newsletter opt‑ins, unsubscribe/objection flags, topics or interests you share with us, basic email statistics (open/click).
We do not want to receive special categories of personal data (e.g. health data, political opinions, religion) through NoCode‑X unless strictly necessary and agreed with our customer. If our customer chooses to process such data in their app, they remain responsible as controller.
We do not intentionally offer information society services directly to children under 13 without parental consent and we do not direct marketing to children under 13.
4. Why we process your data (purposes & legal bases)
The following legal bases apply where we act as controller. Contractual necessity, Article 6(1)(b), applies only where the individual is a party to the relevant contract and the processing is necessary to perform it. For business representatives and staff of customer organisations, necessary account administration, service communications and support rely on our legitimate interests in delivering and managing the business relationship, subject to the applicable balancing assessment. Legal obligations apply where a specific obligation requires the processing.
When acting as processor, we follow documented customer instructions under the DPA; we do not substitute our own legitimate interest for the customer's lawful basis.
4.1 Authentication & authorization (NoCode‑X)
What we do
Create and manage your NoCode‑X account, log you in, assign roles and permissions, and keep tenants separated in our multi‑tenant architecture.
Examples of data
- Name, email, hashed password or SSO identifier
- Workspace/tenant membership, roles, access rights
Legal basis
- Contractual necessity - Art. 6(1)(b) GDPR
We cannot provide a secure, personalized SaaS service or protect your and your company’s IP without this.
4.2 Operational logging, security & multi‑tenancy protection
What we do
Log system and security events to ensure correct delivery and functioning of the platform and to safeguard your IP and data isolation.
This includes logging when and how you use NoCode‑X and, to a limited extent, how end users interact with apps and websites built on NoCode‑X, to detect abuse and protect the shared infrastructure.
Examples of data
- Login attempts, IP address, device/browser, timestamps
- Security events (suspicious access, rate‑limiting, failed logins)
- Audit logs (who accessed which workspace or resource, when)
Legal basis
- Legitimate interest - Art. 6(1)(f) GDPR, for our own platform security and reliability purposes. Processing on behalf of a customer follows the DPA and customer instructions.
These logs are essential to protect your and other customers’ data in a shared (multi‑tenant) environment and to investigate incidents.
4.3 Technical support & troubleshooting (incl. user‑flows and apps built on NoCode‑X)
What we do
When you or your company contact support, we may look at user‑flows and logs to reproduce and fix issues in:
- the NoCode‑X platform itself, and
- apps, workflows and websites that run on NoCode‑X.
We focus on technical and usage telemetry (what button was clicked, which page errored, which API call failed), not on reading all the business content processed by those apps, unless this is strictly necessary to solve a specific issue.
Examples of data
- Event logs: pages/screens visited, clicks/actions, feature usage
- Error logs, stack traces, correlation IDs
- Workspace/user identifiers linked to a support ticket
- Occasional content snippets if you or your company share them in a ticket or if viewing them is strictly necessary to diagnose the problem
Legal basis
- Contractual necessity - Art. 6(1)(b) GDPR
Support and debugging are part of the service you (or your company) pay for. Without diagnostic data, we often cannot solve complex no‑code issues or customer app problems.
We do not use this data for marketing.
4.4 LLM‑assisted support & DevOps (with external providers)
AI can help generate troubleshooting steps, suggest configuration fixes and explain errors. We do not independently forward production records or personal data from customer applications to AI providers. Customer content may be sent only within a customer-authorised workflow or a specific documented support instruction, with the applicable safeguards.
Build instructions, configuration text, selected error information and results may themselves contain personal data if a user includes it. We limit the information used to what is necessary and avoid credentials and unrelated business content.
For support information processed on a customer's behalf, the DPA and its sub-processing requirements apply. For our own support relationship, the controller purposes and legal bases described above apply. Permission to connect a tool is not, by itself, consent from all individuals whose data is accessible through that tool.
See AI and MCP data flows for the managed and BYOK routes, and the supply chain for the current managed providers.
4.5 Incident management & service restoration
What we do
Detect, analyse and resolve platform incidents, restore availability and integrity, and document what happened.
Examples of data
- System performance logs and monitoring metrics
- Event sequences around the incident (including how apps built on NoCode‑X were used at that time)
- Affected workspaces/tenants and features
Legal basis
- Legitimate interest - Art. 6(1)(f) GDPR, for our own platform security and reliability purposes. Processing on behalf of a customer follows the DPA and customer instructions.
We must be able to restore and maintain the service as described in our agreement.
4.6 Service reliability & capacity planning
What we do
Monitor performance and load so we can scale the platform and keep it responsive.
Examples of data
- Aggregated error rates & response times
- Feature usage volumes and concurrency
- Infrastructure load by region or environment
Legal basis
- Legitimate interest - Art. 6(1)(f) GDPR, for our own platform security and reliability purposes. Processing on behalf of a customer follows the DPA and customer instructions.
Without this, we cannot proactively manage capacity or ensure acceptable performance.
4.7 Payments, invoicing & AML
What we do
- Process your subscription and other payments
- Issue and store invoices and accounting records
- Perform Anti‑Money Laundering (AML) checks where applicable
Examples of data
- Billing name, company, VAT number, address
- Bank account number, payment references, payment status
- Where applicable: AML/KYC data required by law or payment intermediaries
Legal basis
- Legal obligation - Art. 6(1)(c) GDPR
- Contractual necessity - Art. 6(1)(b) GDPR (for billing itself)
We must comply with tax, accounting and AML laws.
4.8 Contractual & license notifications, payment reminders
What we do
- Inform you of upcoming license or subscription expiry
- Send payment reminders for overdue invoices
- Notify you about material contractual changes
Examples of data
- Admin/billing contact details
- Subscription details and expiry dates
- Invoice and payment status
Legal basis
- Contractual necessity - Art. 6(1)(b) GDPR
These messages are needed to ensure continuity of your service. You cannot opt out of these essential service communications while keeping an active account.
4.9 Events, streaming & access control (visitor context)
We use your data when you attend events, participate in streaming, or visit our sites.
Some examples (from our existing visitor policy):
-
Event registration lists
- Legal basis: performance of a contract (Art. 6(1)(b))
- Retention: typically up to 6 months after the event
-
Event streaming (public or authenticated)
- Legal basis: performance of a contract (Art. 6(1)(b))
- Retention: typically 2 weeks (online streaming) / 30 days (public streaming)
-
Evacuation lists for events (safety)
- Legal basis: legitimate interest (Art. 6(1)(f)) & safety obligations
- Retention: typically 3 months after the event
-
Access control to facilities (e.g. badges, visitor logs)
- Legal basis: legitimate interest (Art. 6(1)(f)) - physical security
- Retention: typically 1 day
-
Whistleblower procedure (if you use it)
- Legal basis: legal obligation (Art. 6(1)(c)) and/or public interest
- Retention: typically 7 years
4.10 CCTV / camera surveillance (offices & premises)
What we do
Monitor certain areas in and around our offices to prevent and investigate incidents.
Examples of data
- Video images where you may appear
- Date, time and location of footage
Legal basis
- Legitimate interest - Art. 6(1)(f) GDPR
- Legal requirements under local CCTV legislation
Retention
- Usually up to 30 days, unless an incident requires longer retention (e.g. police request).
Cameras are placed and signposted in accordance with applicable Belgian law.
4.11 Product & UX improvements (non‑marketing, aggregated)
What we do
Use aggregated and/or pseudonymized telemetry to understand how features are used, identify friction points and improve NoCode‑X and the apps built on it.
Examples of data
- Feature adoption statistics and funnels
- Anonymous or pseudonymized clickstream metrics
- Aggregated app/session performance and error trends
Legal basis
- Legitimate interest - Art. 6(1)(f) GDPR
We want to make the product better for everyone and keep innovating.
Safeguards
- Wherever possible, we work with aggregated or anonymised data that no longer identifies you.
- If we use pseudonymized data, only a very limited group within Co‑Dex.eu can re‑identify, and only when needed and logged.
- We do not use this data for advertising or sell it to third parties.
Your choice
- You may object (Art. 21 GDPR) via your account or at [email protected].
- We then stop using your identifiable data for this purpose unless we demonstrate compelling legitimate grounds (in practice, we aim to honor objections).
4.12 Internal support quality assurance
What we do
Review a limited number of support cases to verify solution quality and train our support team.
Examples of data
- Support tickets and communication history
- Relevant logs and diagnostic data for that case
- Resolution notes and timing
Legal basis
- Legitimate interest - Art. 6(1)(f) GDPR
You benefit from fast and accurate support; we need some QA to guarantee this.
Safeguards
- Access limited to supervisors/QA roles
- Reviewed only in the context of a specific case
- Retention aligned with complaint handling and legal needs
You may object, but we may still keep minimal records to prove how we handled your request.
4.13 Direct / indirect B2B marketing
What we do
- Contact you or your company to present NoCode‑X and related services, when:
- you or your company requested information, or
- we receive your professional contact data from partners or publicly available B2B sources, in a context where our services are relevant.
Examples of data
- Name, professional email, job title
- Company, industry, potential interest
- Interaction history (e.g. demo, download, event)
Legal basis
- Legitimate interest - Art. 6(1)(f) GDPR
B2B contacts generally expect some commercial communication about relevant tools.
Your choice
- Each message includes an unsubscribe link.
- You can also object at any time via [email protected].
In that case, we stop using your data for this purpose and may keep a minimal “do‑not‑contact” flag.
4.14 General product updates (feature announcements)
What we do
Inform existing users/admins about new features or significant updates to NoCode‑X that may be relevant to your current use.
Examples of data
- Name, professional email
- Workspace / subscription linkage
Legal basis
- Legitimate interest - Art. 6(1)(f) GDPR
It’s in both your interest and ours that you know what the product you’re already using can do.
Your choice
- You can opt out via the unsubscribe link or by contacting us.
- Critical safety or contractual changes may still be sent as essential service messages under Art. 6(1)(b).
4.15 Newsletter & editorial content (opt‑in)
What we do
Send a newsletter with broader content (articles, events, thought leadership, general NoCode‑X updates).
Examples of data
- Name, email
- Newsletter preferences
- Basic engagement data (opens, clicks)
Legal basis
- Consent - Art. 6(1)(a) GDPR
You only receive this if you actively subscribe.
Your choice
- You can withdraw consent at any time via unsubscribe or [email protected].
- Withdrawal does not affect past lawful processing.
4.16 AI, model choice and MCP
Customers choose which models and services to use, including compatible hosted or self-hosted services through APIs or MCP. An external AI client can call the NoCode-X MCP server within the customer's authorisation and platform permissions. The client receives the results of authorised calls and handles them under its own applicable arrangements.
Customers may also use their own provider accounts and API keys (BYOK) for embedded AI calls and integrations. Alternatively, our built-in AI connectors currently use OpenAI and Groq, with usage billed through Co-Dex. These are separate routes: BYOK does not mean that data necessarily bypasses our platform, and an external AI client is not automatically a Co-Dex sub-processor.
NoCode-X retains build instructions and results needed to facilitate the application. It does not independently send production data or personal data to third parties for AI processing. A customer's configured action, selected context or authorised MCP call can transmit such data; customers must choose the necessary information and lawful purpose. Co-Dex remains responsible for the processing it performs and for providers it engages on a customer's behalf.
Where a customer uses document search or embeddings, the processing can include source files, text fragments, numerical vectors, metadata and retrieved context. These records may contain or be linked to personal data. Customer instructions for access, retention and deletion must cover derived records as well as source files.
The AI and MCP guide explains these routes. The supply chain records managed-provider changes and the applicable notice process. No general promise of local processing, zero retention or European processing is implied by model choice or BYOK.
5. Email statistics
For certain communications (e.g. newsletters, product updates) we may collect basic email statistics such as:
- email opened or not,
- links clicked,
- bounces.
We use this to understand whether our communication is effective and relevant. Where this involves the newsletter, it is covered by your consent; for necessary or LI‑based communications it is covered by the same legal basis as that communication. You can always unsubscribe or object as explained above.
6. Do you have to provide your data?
In some cases, we need your data to:
- perform the contract (e.g. create an account, provide support, invoice you), or
- comply with the law (e.g. AML, tax).
If you refuse to provide the information that is clearly necessary, we may not be able to:
- create or maintain your NoCode‑X account,
- provide certain services or access,
- complete payments or comply with legal obligations.
For optional processing (e.g. newsletter, certain marketing, UX improvements), you can say no, object, or withdraw consent at any time.
7. Who we share your data with
We may share your personal data with:
Within Co‑Dex.eu
- Different Co‑Dex.eu entities and internal departments where needed for operations, compliance, security, support and accounting.
Financial institutions
- Banks and payment service providers to process your payments and transfers.
Government & regulated bodies
When required by law, for example:
- Tax authorities
- Supervisory authorities (e.g. central bank, data protection authorities)
- Police, prosecutors, courts, arbitration or mediation bodies
- Bankruptcy trustees and similar roles
Service providers (processors)
We use service providers to help us:
- host and maintain our infrastructure and websites
- send emails and manage ticketing/support
- provide LLM‑assisted support and other analytics/logging tools
- process payments and invoicing
- organize marketing campaigns and events
- perform research and innovation (often using aggregated or anonymized data)
Where a provider processes personal data on our behalf, we use an appropriate processing agreement. Providers engaged by us for customer-controlled processing are subject to the DPA's sub-processing arrangements. Other recipients, such as authorities or payment providers acting for their own purposes, have their own responsibilities.
For the built-in AI route, consult the supply chain. We do not authorise our providers to use customer personal data to train their general models as part of ordinary service delivery. Provider retention and other processing depend on the applicable service, contract and settings. Customers manage the arrangements for services they contract directly, including their selected external AI clients.
Research & innovation partners
Sometimes we share aggregated/anonymized data with universities or innovation partners for research. They must respect strict data protection requirements; results do not identify you.
We will never sell your personal data.
8. International transfers
If your data is transferred outside the European Economic Area (EEA), we ensure appropriate safeguards, such as:
- an adequacy decision of the European Commission, or
- Standard Contractual Clauses (SCCs) with additional technical and contractual protections.
You can ask for more information via [email protected].
Our managed core platform is hosted in Belgium and France. Customer-selected hosting can use a preferred cloud, private cloud or on-premises Kubernetes environment. This describes core hosting, not every connected service. External AI providers, MCP clients, connector runtimes and their support or metadata processing can involve other locations. See Data Residency and the supply chain. We apply the required transfer safeguards to transfers for which we are responsible; customers assess the services they contract directly.
9. How long we keep your data
We keep your data only as long as necessary for the purposes described, and in line with legal retention obligations. After that, we delete or anonymize it.
Examples:
- Platform audit and security logs: retained for at least 365 days, as described in Auditability. Longer retention must remain justified by the purpose, applicable law or a specific incident or legal claim. This is not a blanket retention period for prompts, chat transcripts or customer-created content.
- Event data: see indicative periods above (e.g. evacuation lists ±3 months, camera footage max 30 days).
- Support tickets: for the duration of the customer relationship and a limited period thereafter (e.g. typical limitation periods).
- Billing & invoicing data: up to 7-10 years in line with accounting/tax law.
- Whistleblower records: usually up to 7 years, depending on legal requirements.
- Marketing / lead data: until you object, unsubscribe, or we determine the data is no longer up to date or relevant.
- Newsletter data: until you withdraw consent or we stop the newsletter.
For customer content, build instructions and results, retention follows the service lifecycle and documented customer instructions. After conversion to a free account, application user identities (app users) are deleted after 7 days; content and free resources are hard deleted after 30 days of inactivity in the free account. These are separate deadlines. The account closure process, production deletion and the distinction from retained logs and legal records are explained in Opting out and DPA section 13. Documents, chat history and derived indexes included in a customer application follow that application's instructions. External provider copies follow the applicable supplier arrangement; closing NoCode-X does not itself delete copies in an independently contracted AI client.
Backups are governed separately by the backup arrangements. A production deletion deadline does not by itself establish when every backup or independently held copy expires. Contact our DPO for the retention applicable to a specific deployment or data category.
10. How we protect your data
We apply strong organizational and technical measures including:
- internal security policies and staff confidentiality obligations
- role‑based access control and least‑privilege principle
- encryption in transit and at rest where appropriate
- industry‑standard security for networks and applications
- logging, monitoring and incident response processes
- regular updates and security improvements
- tenant isolation and permission checks on MCP requests
- protected storage of connection credentials
- logging and confirmation of risk-sensitive actions
No security is perfect, but if a breach occurs that could have major consequences for you, we will:
- inform you without undue delay where required, and
- take all reasonable steps to mitigate the impact.
11. What you can do to protect yourself
Simple good practices help:
- Use up‑to‑date antivirus/anti‑malware and a firewall.
- Keep your devices and authentication means (tokens, cards) safe.
- Log out from applications when not in use.
- Choose strong, unique passwords and change them regularly (password managers can help).
- Be cautious with unusual emails or links asking for credentials or payment details.
12. Your GDPR rights
For processing where Co-Dex is controller, contact our DPO, Wim Barthier, at [email protected]. We may verify your identity where necessary and normally respond within one month; where a lawful extension is needed, we explain it within that period. If your request concerns a customer's application or process, that customer is the primary contact as controller. We forward requests concerning customer-controlled data to the customer and assist under the DPA.
- Right of access - you can ask which personal data we hold about you and obtain a copy.
- Right to rectification - you can ask us to correct incomplete or inaccurate data.
- Right to erasure - in certain cases (e.g. data no longer needed, consent withdrawn), you can ask us to delete your data.
- Right to restriction - you can request that we temporarily restrict processing in specific situations.
- Right to data portability - for data you provided to us, processed by automated means based on consent or contract, you can request it in a structured, commonly‑used, machine‑readable format.
- Right to object - you can object to processing based on legitimate interest (e.g. product improvement, B2B marketing, LLM‑assisted support where based on LI, product updates). We will stop unless we demonstrate compelling legitimate grounds. You can always object to direct marketing, and we will stop immediately.
- Right to withdraw consent - for processing based on consent (e.g. newsletter), you can withdraw at any time.
If you are not satisfied with our response, you can always lodge a complaint with the Belgian Data Protection Authority:
- Website: https://www.gegevensbeschermingsautoriteit.be
- Address: Drukpersstraat 35, 1000 Brussels
- Tel: +32 (0)2 274 48 00
- Email: [email protected]
13. How to contact us
For questions, requests, or complaints about privacy:
- DPO: Wim Barthier
- Email: [email protected]
- Postal mail:
Co‑Dex.eu BV - Privacy Albert I‑laan 23
8920 Langemark‑Poelkapelle
Belgium
When you contact us, we may ask for additional information to verify your identity (for example, a partially redacted copy of an ID with your national register number obscured). If we cannot reasonably identify you, we may have to respond in a more generic way to avoid disclosing data to the wrong person.
14. Changes to this privacy policy
We may update this Privacy policy from time to time, for example to reflect legal changes or new features in NoCode‑X.
- We will announce important changes at least 7 calendar days before they take effect, via the service, our website, or email (where feasible).
- The latest version will always be available on our website and will indicate the effective date at the top.
A policy update informs you about processing; continued use is not consent to a new purpose where consent is required. Contract amendments and sub-processor changes follow the applicable DPA and service terms. Managed-provider changes are recorded on the supply chain page.