Privacy policy
What we collect on this site, what for, who else sees it and how to ask us to delete it. It is not much, because this page carries no analytics and tracks nobody.
Last reviewed · 31 August 2026
Controller
The data controller is the company that owns the site. To exercise any of the rights described below, write to the email in this table.
What we collect
There is a single point where personal data enters this site: the contact form. This is what comes out of it, and why.
- Name and work email
- The ones you type into the form. We use them to reply and to carry on the conversation that starts there. The legal basis is your own request: pre-contractual steps taken at your initiative, article 6(1)(b) GDPR.
- What you tell us about the project
- The free text of the third field, which reaches the channel where we read it in full. A practical note: you do not need to put confidential company information or other people's personal data in there. The call is for the detail.
- Language, source button and referrer
- The language of the page, which CTA brought you to the form, and the previous page your browser reports. It tells us which part of the site starts conversations. Legal basis: legitimate interest in knowing what works, article 6(1)(f).
- IP address
- Used at the moment of submission to cap sending at five messages every ten minutes from the same address and keep bots out. It lives in the process's memory, is written to no database and does not travel with the message.
Who else sees it
We neither sell nor share this data for advertising. The only ones who touch it are the two providers the form needs to work:
- Slack
- The message is posted to an internal channel in the Renaiss workspace. That is where we read it and where the reply starts.
- Railway
- Hosts the server that receives the form and serves the pages.
A data processing agreement is in place with both. Where the service involves a transfer outside the European Economic Area, it relies on the safeguards in chapter V GDPR: standard contractual clauses or whichever adequacy framework applies.
How long
The message stays in the channel while the conversation is live and, at most, a year after the last contact. If it turns into a commercial relationship, the data is then governed by the contract and by the retention periods that commercial and tax law require. You can ask us to delete it sooner.
Your rights
By writing to the address above from the email you contacted us with — or proving your identity another way — you can ask us for:
- Access. What data of yours we hold and where it came from.
- Rectification. Correcting whatever is wrong.
- Erasure. Deleting it.
- Objection and restriction. That we stop processing it, or only store it.
- Portability. Receiving it in a machine-readable format.
We answer within one month. If you think we got it wrong, you can complain to the Spanish Data Protection Agency or to the supervisory authority where you live.
Security
The site is served over HTTPS. The Slack channel's address lives in a server environment variable and never reaches the browser: were it in the HTML, anyone could write into our channel from outside.
There are no analytics, no advertising pixels and no social buttons. The fonts are served from this same domain, so opening the page sends your IP address to no third party. We do no profiling and take no automated decisions about anyone based on what goes into the form.
Changes
If what we do with the data changes, this page changes and the date at the top with it. The version in force is always the one published here.
Language
This English text is here for convenience. The Spanish version is the one that governs, and it prevails if the two ever diverge.