Privacy information.
For questions about your data: team@codeflanders.com
Draft: to be completed before publication.
The legal company details, retention periods and processing agreements still need to be confirmed. This text has not been legally reviewed.
Who runs this website
The official registration of CodeFlanders is still in progress. The legal company details will be added once they have been confirmed.
This website belongs to CodeFlanders. You can reach us at team@codeflanders.com or through the contact form.
Legal name of the data controller: to be confirmed. Enterprise number: to be confirmed. Business address: to be confirmed. VAT number, if applicable: to be confirmed.
Your contact request
We process your name, business email address and message in order to handle your question and to communicate with you. These fields are required to use the form. Your company and the topic of your question are optional. You can also email us directly.
After checking it, the server sends your message via Purelymail to our shared mailbox team@codeflanders.com. Ruben, Wissem and Zeynal have access to that mailbox. One of us can then reply to you from their own business email address. The form’s technical sending account is tickets@codeflanders.com.
The server then normally sends one automatic confirmation of receipt to the email address you entered, also via Purelymail and from tickets@codeflanders.com. That confirmation contains only a fixed text and a reference code, not a copy of your message, your name or your company. If you reply to it, your reply ends up in our shared mailbox. The same email address receives at most one confirmation of receipt per 24 hours, and we send none to a domain that cannot receive email.
To follow up on your question, we also keep it in our internal team system, which only Ruben, Wissem and Zeynal use: your name, email address, company, topic and message, and, if you are not yet a client, a record of you or your company as a prospective client. When a new request comes in, our team is notified in its internal chat channel (Discord) with only your name, your company and the topic, not the content of your message. If no collaboration follows, we delete your request and that record from the team system at the latest one year after our last contact.
To be able to follow up faster, we have your message summarised by an AI service: Claude, by Anthropic. Before that, we automatically swap your name, email address, phone number, company and other recognisable details in the text for placeholders; for this summary, Anthropic only receives that anonymised version. The filter is thorough, but not infallible with free text. Every message is always read and answered personally by one of us.
Ruben, Wissem and Zeynal can also consult the team system with their own AI assistant, likewise Claude by Anthropic, including from our internal chat channel. When one of us asks that assistant about your request or your record, Anthropic also processes what the assistant retrieves for it: your name and company as they appear on your record, and an anonymised version of your message. These details may appear in that chat channel.
We do not use this form for newsletters, profiling or automated decisions about visitors.
The legal basis for handling and following up contact requests must be determined before publication: to be confirmed.
Do not share passwords, sensitive personal data or confidential business documents through this form. If more information is needed, we will agree on a suitable way to exchange it.
Technical data and spam limiting
The server checks the origin, size and content fields of a request to limit abuse. In production, shared spam limiting is provided through Upstash Redis. For this, where a trusted hosting proxy passes on the IP address, a code is derived using a secret key. The code and counters expire after fifteen minutes. The spam limiting does not store the content of your message.
The application itself does not log contact messages. Hosting and mail processing may, however, keep technical logs. Which data these contain depends on the services and settings chosen.
To prevent repeated sending, the server also keeps, for a maximum of 24 hours, a request code derived using a secret key, a derived check value and the sending status. This record contains no readable message content or email addresses and, in production, is shared via Redis.
To prevent anyone from using the form to flood someone else’s email address with confirmations, the server keeps, for each confirmation of receipt, a code derived from the email address using a secret key, and counts how many confirmations it tries to send in total, each for a maximum of 24 hours. This record also contains no readable email addresses and, in production, is shared via Redis. Before sending a confirmation, the server looks up via DNS whether the domain of the email address can receive email.
Services that process data
Purelymail is our email provider. Upstash Redis is provided for shared spam limiting in the production environment; our internal team system also stores its data, including the requests, with Upstash. Claude by Anthropic makes the summaries of the anonymised messages and is also the AI assistant with which we can consult the team system. We use Discord for internal notifications to our team and as a chat channel with that assistant. These integrations work through the server. Your browser does not connect directly to Purelymail, Upstash, Anthropic or Discord for this.
Hosting provider: Vercel. Processor agreements: to be confirmed.
Processing locations: to be confirmed. Any transfer outside the European Economic Area and the related safeguards: to be assessed and confirmed.
How long we keep data
In our internal team system, we delete a request, and the record of a prospective client we made for it, at the latest one year after our last contact if no collaboration follows.
Retention period or deletion criteria for contact requests in our mailbox and mail processing: to be determined before publication.
Retention periods for technical hosting and mail logs: to be confirmed based on the chosen settings. The spam-limiting counters have a technical lifetime of fifteen minutes. The record that prevents repeated sending and the record of confirmations of receipt expire after at most 24 hours.
Cookies and local storage
The website does not use cookies, tracking pixels or external embeds. We also do not store any visitor data from the website in your browser’s local or session storage. Fonts are loaded from the website itself.
To know how many people visit the website and which pages they read, we count visits anonymously with Vercel Web Analytics, from our hosting provider Vercel. Nothing is stored on your device. For every page viewed, Vercel records the time, the page address, the referring website, the country or region, the device type, the operating system and the browser. Visits are recognised by a code calculated from the request that expires after 24 hours; your IP address is not stored. We only see totals, never who viewed which page, and we do not follow you across other websites.
Because we do not use non-essential cookies or other trackers, we do not show a cookie consent banner. If we add such features later, we will update this information and, where necessary, ask for consent in advance. The final hosting configuration must still be checked for additional cookies or trackers before publication.
Your rights and questions
You can ask for access to your personal data, for incorrect data to be corrected or for data to be deleted. Depending on the applicable conditions, you can also ask for the restriction or transfer of data, or object to processing.
Email your request to team@codeflanders.com. Mention which data or contact request it relates to. If necessary, we will ask for additional information to verify your identity. We will handle your request within the applicable legal time limit.
You can lodge a complaint with the Belgian Data Protection Authority.