Data protection

Privacy policy

Last updated: 13 August 2026

This is a courtesy translation. This policy is governed by the GDPR and by Spanish law, so in the event of any discrepancy the Spanish version prevails.

1. Data controller

Name

Yaddiel Samper Leal

Tax ID (NIF)

61439429N

Address

C. Camino La Rambla 5, El Ortigal, 38297 San Cristóbal de La Laguna, Santa Cruz de Tenerife, Spain

Privacy contact email

procesos.comercial@protonmail.com

2. This site collects no data by itself

This website is static and has no forms, no sign-up and no private area. It asks for no data and sends nothing to any server of ours. If you want to get in touch, the buttons open your email client or WhatsApp: the conversation starts when you decide to write.

3. What is processed when you write

Data

Whatever you include in your message: usually your name, email or phone number, the name of your office and whatever you want to tell us.

Purpose

To reply to you, to prepare the demonstration if you ask for one and to follow up commercially on that request.

Legal basis

Your own request: the legitimate interest in dealing with an enquiry you started (art. 6.1.f GDPR) and, if an agreement is reached, performance of the contract (art. 6.1.b).

Retention

For as long as the conversation lasts and, afterwards, for as long as needed to meet legal obligations or handle possible claims. If you ask us to delete your data, it is deleted.

Recipients

Nobody, other than the email provider we use to reply to you (Proton AG, Switzerland), acting as a data processor. Your data is not passed to anyone else and is not sold to third parties. Switzerland is outside the European Economic Area, but the European Commission recognises its level of protection as adequate, so your message is handled with the same safeguards. Apart from that provider, what you write to us travels to no other recipient. (The technical logs of the server hosting this site are a different matter and are explained in point 5.)

4. Cookies

This site uses no cookies. There is no analytics, no advertising pixels and no fonts or scripts loaded from other domains: the typefaces are served from this same domain, alongside the rest of the page, and the only JavaScript file is ours. That is why you will not see a banner asking for your consent: there is nothing to consent to. You can check it in the "Network" tab of your browser's developer tools.

5. Server logs

As with any page on the internet, the hosting provider (Vercel Inc., based in the United States) keeps technical logs of visits, which may include the IP address, the date and the browser. They are used to keep the service running and secure, and those logs are managed by the provider itself under its own data processing terms. We do not consult them, do not exploit them and do not cross-reference them with any other data. The United States is outside the European Economic Area, so that transfer is governed by the provider's own data processing terms and by the safeguards it applies; if you want the detail, write to the email in point 1.

6. Your rights

You can request access to your data, its rectification or its erasure, as well as restriction of or objection to processing and data portability, by writing to the email given in point 1. We will reply within the legal deadline.

If you believe we have not dealt with your request properly, you can lodge a complaint with the Spanish Data Protection Agency (www.aepd.es).

7. Your clients' data is a different matter

This policy covers this website only. If your office goes on to use Proce.SOS, your own clients' data is processed under a separate data processing agreement, in which your office is the controller and we are the processor. That document is signed before starting and is not part of this page.

Inside the tool, any processing with artificial intelligence goes through a commercial API — never a consumer interface — and the default provider is Anthropic PBC. The tool also lets your office connect a specific agent's chat to OpenAI, L.L.C. or Google Ireland Ltd. using its own key and its own account: in that case that provider joins your chain of processors, with your contract and your invoice, and it is up to you to record it in your record of processing activities. Document reading (contracts, deeds, identity documents) does not use that route: it always goes through the default provider.