Skip to content

DocumentPrivacy

Privacy policy

1 · Controller

Earningcode S.L.U., tax ID (CIF) B13569314, C/ José María Serna 5, local, Tomelloso (Ciudad Real), Spain. Contact for any data matter: privacidad@larstel.com. There is no data protection officer.

2 · Where the data is hosted

The data is kept with a hosting provider with servers in Spain. If you request the diagnostic from one of our LinkedIn ads, the data passes through LinkedIn first (section 8) and through Make, the service that brings it to us (section 9), and then reaches our CRM.

3 · What is collected, and from where

Only what you type into the forms: name, company, phone, email and the answers on the diagnostic form; the email address, on the subscription; the email address and the password, on client login. And, only if you tick the optional box on the diagnostic form, the click identifier of the Google ad you came from (section 12). Nothing else: no pixels, no third-party cookies. Aggregate, cookie-free audience measurement (Plausible, an EU service; the script loads from plausible.io). It identifies nobody, and there is nothing for you to accept. If you arrive from an ad or a link with campaign tags, those tags are part of the address that Plausible reads, and we also save them (campaign, medium, source) with your request. If the address carries a Google click identifier, Plausible receives it and, according to its documentation, discards its value.

We also receive data through LinkedIn ad forms (Lead Gen Forms), when someone requests the diagnostic from one of our ads: first name, last name, email, phone, company, job title, province, the approximate turnover you select, the ad you came from and the consent boxes you tick. LinkedIn pre-fills some of these fields with data from your profile; you can change them before sending, and nothing reaches us unless you send the form.

4 · What it is used for

Preparing and arranging the diagnostic · sending the monthly newsletter to whoever asks for it · giving access to the service to customers who have it under contract. We use the campaign tags to know which ad brought each request and to decide where we spend on advertising.

Data that comes through LinkedIn is used for the same things: calling you and writing to you about the diagnostic you request, and sending you the monthly newsletter only if you tick that box. The ad you came from tells us which ad works; we use it for nothing else.

If you tick the optional box on the diagnostic form, we also use the click identifier of the Google ad you came from, so that Google knows which ads lead to diagnostic requests and adjusts who sees our ads: we send it in the weekly upload after you request the diagnostic and, once your request is classified as suitable for the service, in that same upload or a later one. We use it for nothing else.

5 · Legal basis

Consent for the diagnostic and the subscription, including when they are requested through a LinkedIn form: the box you tick when you send it; performance of the contract for client login. You can withdraw your consent at any time by writing to privacidad@larstel.com or by unsubscribing from the newsletter, without affecting any processing carried out before. Legitimate interest for the campaign tags (knowing which ad works). You can object by writing to privacidad@larstel.com.

Consent also for the Google click identifier: the optional box on the diagnostic form, which is separate from the diagnostic box. If you do not tick it, we do not read that identifier, we do not store it with your request and we send nothing to Google, and your diagnostic request goes ahead just the same. You can withdraw it at any time by writing to privacidad@larstel.com (the “Withdraw this authorisation” link on the form prepares the email); we delete the identifier and stop sending from that moment, without affecting any processing carried out before. What Google has already received is handled by Google under its own policy (section 12).

6 · How long

Diagnostic data, for as long as the commercial relationship lasts and then for the legal limitation period. The subscription email address, until the person unsubscribes. We keep the campaign tags for as long as we keep the request they come with; if there is no commercial relationship, we delete them after 24 months.

Data that comes through LinkedIn, the same periods. It reaches our CRM within minutes, through Make. If that connection fails, we download it from LinkedIn by hand and move it into the CRM on the same working day or the next. The copy left in LinkedIn’s advertising tool is deleted automatically within the period LinkedIn sets.

We keep the Google click identifier for 90 days at most from the moment we collect it, and delete it earlier once we have sent the last pending action, or if the request is discarded or you withdraw the authorisation. If the classification comes after those 90 days, nothing is sent, because the identifier no longer exists. We keep the record that you ticked the box (date, time and the text you saw) while we are still sending, and for three years after you withdraw or after the last upload, so that we can prove it.

7 · Where the data goes, and who it is shared with

Whatever you write in any of our forms goes into our own CRM, hosted in Spain. We do not pass your data to anyone outside Earningcode S.L.U., unless the law requires it. The only exception is the optional box on the diagnostic form: if you tick it, your ad click identifier goes to Google (section 12). We do not sell your data, we do not use it for third-party advertising, and what you write in the forms does not go into any analytics tool. Audience measurement (Plausible, section 3) receives the address of each page you visit, with its campaign tags if it has any, and a few events that do not identify you, such as having started or sent a form, but never what you write; if the address carries a Google click identifier, Plausible receives it and, according to its documentation, discards its value. We keep the data from your requests for the periods in section 6, and you can ask us to delete it (section 11), except what the law obliges us to keep. Three third parties are involved with what you write, and only as processors: a hosting provider with servers in Spain and, when the request comes from an ad, LinkedIn (section 8) and Make (section 9). Google, only if you tick the box, is not our processor: it handles your click identifier as a controller in its own right (section 12).

8 · LinkedIn

Data from a LinkedIn ad form is processed by Earningcode S.L.U. as controller, just like data from this site. LinkedIn Ireland Unlimited Company (Wilton Place, Dublin 2, Ireland) collects it and keeps it on our behalf in its advertising tool until we move it into our CRM; in doing so it acts as a processor, under the data protection terms LinkedIn sets for its advertisers.

To decide who sees an ad, we choose general criteria (location, industry, company size, job title and profile language) and LinkedIn applies them using the data it holds on its network. LinkedIn carries out that processing under its own privacy policy. We receive no data about people who see an ad and do not fill in the form, only aggregate figures (impressions, clicks, submissions), and we do not upload lists of people’s data to LinkedIn. To the extent that choosing those criteria makes us controllers jointly with LinkedIn, you can exercise your rights with either of us.

This site carries no LinkedIn tag (Insight Tag) and no other advertising pixel: the site sends LinkedIn no data about your visit.

9 · Make

We do not copy LinkedIn ad form data by hand: Make brings it to us. Make is an automation service run by Celonis, Inc., a United States company, which acts as a processor under the data processing agreement Celonis sets for Make. We chose the European Union zone for our account, and that is where the data is stored and processed. Make receives only what you send in the form and delivers it to our CRM; it uses it for nothing else. To read the forms it uses a permission on our LinkedIn account that we can withdraw at any time. Make’s list of suppliers is at make.com/en/terms-and-conditions.

10 · International transfers

What comes through this site is hosted in Spain and does not leave the European Economic Area, except the Google click identifier if you tick the box (below). What passes through LinkedIn may also be processed outside the European Economic Area, in particular in the United States, by LinkedIn group companies and their suppliers. For those transfers LinkedIn applies the safeguards provided for in the General Data Protection Regulation, such as the standard contractual clauses approved by the European Commission.

Make stores and processes the data on servers in the European Union, but the service is provided by Celonis, Inc., in the United States. Technical support is provided by Celonis group companies, mainly from the Czech Republic, and also from other countries, some of them outside the European Economic Area. Some of Make’s suppliers have servers in the United States. For these transfers, Celonis, Inc. participates in the EU-U.S. Data Privacy Framework, which the European Commission considers adequate; should that framework cease to apply, the standard contractual clauses approved by the European Commission apply. Celonis group companies and Make’s suppliers are bound by contract to the same data protection obligations.

Once the data is in our CRM, it is hosted in Spain only.

Google Ireland Limited may process the click identifier outside the European Economic Area, in particular in the United States, through Google group companies and their suppliers. For those transfers Google applies the safeguards provided for in the General Data Protection Regulation, such as the standard contractual clauses approved by the European Commission.

11 · Rights

Access, rectification, erasure, objection, restriction and portability, by writing to privacidad@larstel.com, and the right to complain to the Spanish data protection authority. If the data came through LinkedIn, you can still write to us, and we also take care of the copy LinkedIn keeps on our behalf. For the data in your LinkedIn profile and your activity on LinkedIn, LinkedIn is the controller, and the rights are exercised with LinkedIn. If you ticked the optional box, the click identifier that Google has already received is handled by Google in its own right, and you can also exercise your rights with Google; we stop sending and delete ours as soon as you ask.

12 · Google

If you reached us from a Google ad and tick the optional box on the form to request the diagnostic (the same form that appears on the diagnostic page and at the bottom of the Spanish-language home page and of the Spanish-language pages for El Parte, Pedidos, Almacén, Rutas y reparto, Facturación and Tus clientes), we send Google Ireland Limited, from our CRM, the click identifier of that ad, with two signals: that you requested the diagnostic and that your request has been classified as suitable for the service, at the same time or later. We send it in the next weekly upload. We do not send your name, email address or phone number. It tells us which ads lead to diagnostic requests and lets Google adjust who sees our ads. Google handles that data as a controller in its own right, under its own privacy policy, and may also use it for its own purposes; it does not act as our processor. If you do not tick the box, we do not read that identifier, we do not store it with your request and we send nothing to Google.

This site carries no Google tag (gtag) and no advertising pixel: the site sends Google nothing about your visit. When the sending takes place, it leaves from our CRM, not from your browser.

13 · Cookies

Cookie policy.

14 · Website analytics

Who measures. EARNINGCODE SLU, the controller of larstel.com, with its own website code. We do not use cookies for this measurement.

What we measure. The pages you visit, the site and campaign you come from (the tag in the link, known as UTM), the width range of your screen (never the exact size), your browser and operating system, how far you scroll on each page and which elements you click. In the contact form, which field you use, whether it shows an error and how long you spend on it, in ranges. Never what you type.

What we read from your browser. The campaign tag that the website keeps in your browser's session storage (sessionStorage) during your visit, which is deleted when you close the tab.

Your IP address and browser. They are used only for an instant. With them we find out your country and region, whether it is an automated program and the type of network or operator you connect from, never your IP address. We keep whether it is a home or mobile operator, a company or other organisation, or a data centre. We only keep the name if it is a data centre. We also create a visitor code that stays the same across all your visits while this trial lasts. We will review the trial on 11 November 2026. The code is kept with each visit and deleted with it, after 90 days at most. The analytics database does not store your IP address or browser details. The server log of crm.larstel.com does not record the analytics requests.

If you send the diagnostic form. When you send it with the privacy box ticked, we link your visits to this website over the last 15 days to your request. We also keep some details of that submission with it: country, province or autonomous community, the network or operator you are writing from (it may be your company or your internet provider), your browser and type of device, and whether your email domain matches that network. All of this is kept with your request. If you do not send it, or if you only sign up for the newsletter or use the access form, we link nothing and we do not keep those details.

Why. To produce usage statistics, improve the website and the form, and separate visits from bots and data centres. If you send the diagnostic form, also to understand how you found us and to handle your request better. If you do not send it, we do not use this data to find out who you are. We never use it to look you up or to contact you on our own initiative.

Legal basis. For the measurement, our legitimate interest in understanding how the website is used (Art. 6(1)(f) GDPR). This measurement is exempt from consent under Article 22.2 of the Spanish Information Society Services Act (LSSI), as set out in the Spanish Data Protection Agency's guide on audience measurement tools. To link your visits and keep the submission details with your request, your consent when you tick the box (Art. 6(1)(a) GDPR). You can withdraw it at any time. If you do, we separate your visits and those details from your request and delete them.

How long. The visitor code and the rest of the data on each visit, 90 days. After that we only keep totals, with no data about your visit. Visits and details linked to your request are kept for as long as your request.

Who sees it. Only our team. We do not share it with anyone. The data is kept on a server in Spain and does not leave the European Union.

Your rights. You can object to this measurement and exercise your other rights by writing to privacidad@larstel.com. If your browser sends the Global Privacy Control signal, the measurement is not activated. If you believe we have not handled your rights properly, you can lodge a complaint with the Spanish Data Protection Agency (aepd.es).

Location data source. IP Geolocation by DB-IP, licensed under CC BY 4.0.

This is a translation of the Spanish original. In case of discrepancy, the Spanish text prevails.