Personal data processing agreementHow I process your site’s logs, on your behalf.
English translation provided for convenience. The French version prevails.
Version of October 26, 2026. For any question, email lucas@lucasfonseque.fr.
This agreement governs the personal data of your site’s visitors that is contained in the logs you entrust to the log analyzer. It meets the requirements of Article 28 of the General Data Protection Regulation (GDPR). It is inspired by the example processing clauses published by the CNIL, France’s data protection authority.
It is part of the terms of use of the analyzer. Words it does not explain have the meaning given to them by the GDPR.
Who are the parties?
On one side, you: the person or organization holding the account that connects a site. For the data of that site’s visitors, you are the controller.
On the other side, the processor: the company LUCAS FONSEQUE, a single-shareholder simplified joint-stock company with share capital of €1,000, registered with the Toulouse Trade and Companies Register (RCS) under number 938 596 889. Its registered office is at 32 route d’Agde, 31500 Toulouse. It is represented by its president, Lucas Fonseque. In this agreement, “I” means this company.
What if you connect a client’s site?
If you are an agency or a freelancer, you can connect a client’s site. You then often act as their processor. I become your sub-processor.
In that case, you undertake to have your client’s written consent to engage me. You send them this agreement. You remain my only point of contact, and you pass their instructions on to me.
When does this agreement apply?
You accept this agreement by accepting the terms of use, through the checkbox provided at sign-up. It is concluded in electronic form, as Article 28 of the GDPR allows.
It applies as soon as you connect a first site. It lasts as long as the tool processes data from one of your sites. It ends when all that data has been deleted or returned, as provided below.
The processing entrusted to me
Why is this data processed?
I process your site’s logs for one reason only: to provide you with the log analyzer. In practice, this means counting your real visitors, recognizing search engine bots and AI bots, spotting fake bots and attacks, flagging errors, and showing you figures and advice.
I do not process this data for my own purposes. I do not sell it. I do not cross-reference it with other customers’ data to track a person from one site to another.
What does the tool do with the logs?
The tool receives the logs by the method you have chosen: upload script, WordPress plugin or file upload. It reads them, sorts them and calculates totals. It keeps the archives received, then deletes them. It displays the results in your account and in alert emails.
To verify a bot, the tool compares its IP address with the lists of addresses published by search engines and AI providers.
In the statistics, the tool does not keep your visitors’ IP addresses. It calculates a fingerprint from the address, the browser and a key that changes every day. This key is deleted after two days.
What data is concerned?
The data is that of your server’s access logs. For each request received by your site, one line contains the IP address, the date and time, the page requested (its address and the method used), the status code returned by the server, the size of the response, the page of origin (the referrer) and the user agent, that is, the name of the browser or bot.
The tool needs no other data. It does not ask for a name, an email address or any special category data within the meaning of Article 9 of the GDPR.
Which people are concerned?
The data subjects are the visitors to your site. The logs also contain requests from bots: search engines, AI, tools and attacks. An IP address can point to a person, even when the request comes from a bot. All lines are therefore handled with the same care.
How long is the data kept?
The log archives received are deleted after 70 days at most. Aggregated figures are kept according to the history of your plan: 30 days on Starter, 3 months on Lite, 13 months on Standard, 25 months on Advanced and Enterprise.
My commitments as processor
Following your instructions
I process the data only on your documented instructions. These instructions are this agreement, the terms of use, the settings you make in the tool (connected sites, members, viewers) and your written requests by email.
If an instruction seems to me to infringe the GDPR or another data protection rule, I tell you immediately.
If the law ever requires me to process the data differently, for example to transfer it outside the European Union, I notify you beforehand, unless the law prohibits me from doing so.
Keeping the data confidential
On my side, only Lucas Fonseque has access to your site’s data. If someone else ever needed to access it to help me, they would be bound by confidentiality and trained in data protection.
Protecting the data
I put in place security measures appropriate to the risk, as Article 32 of the GDPR requires. They are simple and realistic:
- password login to the tool;
- confirmation links valid for a limited time;
- accounts isolated from one another: each account sees only its own sites;
- encrypted access over HTTPS;
- data backups;
- automatic deletion of log archives after 70 days;
- access to the data restricted to Lucas Fonseque, on my side.
I do not hold a security certification. I update these measures when the tool changes, without ever lowering the level of protection.
The tool also applies data protection by design: it keeps as little data as possible, for as short a time as possible.
Engaging other processors
You authorize me to engage the sub-processors listed below. o2switch is the only service that receives your visitors’ logs. Stripe and HubSpot receive only your customer data, for which I am the controller: they are listed here so that you have a complete view.
| Service | What it does | Data received | Where is the data? | Receives your visitors’ logs? |
|---|---|---|---|---|
| o2switch (Clermont-Ferrand) | Hosts the application, the logs received and the figures, and sends the tool’s emails (confirmations, alerts, reports) from the same server | All the tool’s data | In France, in its own data centers | Yes |
| Stripe (Stripe Payments Europe Limited, Ireland) | Collects subscription payments | Your billing and payment data | Irish company; according to Stripe, data may be transferred to other countries, including the United States, with safeguards (Data Privacy Framework, standard contractual clauses) | No |
| HubSpot | Contact book: tracking your account | Your contact details and your answers to the first-login questionnaire | HubSpot’s European data center, located in Frankfurt (Germany) according to HubSpot; access may be possible from the United States, as HubSpot is certified under the Data Privacy Framework | No |
Before adding or replacing a sub-processor that receives your visitors’ logs, I notify you by email at least 30 days beforehand. The email states its name, what it will do and where the data will be.
During those 30 days, you can object by email, on grounds related to data protection. If no solution is found, you can disconnect your sites and cancel your subscription, free of charge. By exception to the terms of sale, the part already paid for the remaining period is then refunded to you.
Each sub-processor is bound by contract to the same obligations as I am. If it fails to comply with them, I remain fully liable to you.
Helping you respond to visitors
A visitor to your site may exercise their rights: access, rectification, erasure, objection or restriction. If they write to me directly, I forward their request to you without delay, at the email address of the account. I do not reply to them on your behalf, unless you ask me to.
I help you, as far as possible, to respond to these requests. For example, I can search for and delete the lines linked to an IP address in the archives still kept.
Notifying you of a personal data breach
A personal data breach is, for example, a loss, a leak or unauthorized access to data. If I discover one that affects your site’s data, I notify you by email without undue delay, and at the latest 48 hours after discovering it.
This email describes the nature of the breach, the categories and approximate number of data subjects and lines concerned, the likely consequences and the measures taken or proposed. It also gives a contact for more information. If I do not have all the information right away, I send it to you as it becomes available.
It is for you to notify the CNIL, and the visitors if necessary, within the GDPR deadlines. I help you to do so.
Helping you with other obligations
I help you, with the information I have, to carry out a data protection impact assessment if one is necessary, and to consult the CNIL if needed.
I keep a written record of the processing I carry out on behalf of my customers, as Article 30 of the GDPR requires.
For any question about this agreement or your data, write to lucas@lucasfonseque.fr.
Demonstrating that I comply with this agreement
On request, I provide you with the information necessary to demonstrate that I comply with this agreement and Article 28 of the GDPR.
You can also have this compliance checked, including by an inspection, by yourself or by an inspector you appoint. This inspector must be bound by confidentiality and must not be a competitor of the analyzer. You notify me by email at least 30 days beforehand. This check takes place at most once a year, except after a personal data breach or at the request of the CNIL. It is at your expense.
A check cannot give access to the data of other customers.
Your commitments as controller
You choose the lawful basis for the processing, for example your legitimate interests in measuring the traffic of your site. You check that it suits your situation.
You inform the visitors to your site. A line in your own privacy policy is often enough, for example: “This site measures its traffic from server logs, without cookies, using the log analyzer of the company LUCAS FONSEQUE, hosted in France. The logs received are deleted after 70 days at most.”
You send only access logs. Avoid having personal data in your page addresses, such as an email address in a link.
You give me your instructions in writing. You ensure compliance with the GDPR, before and during the processing.
Does the data leave the European Union?
No. Your visitors’ logs, and the figures drawn from them, stay with o2switch, in France. No transfer outside the European Union takes place for this data.
If this were to change, I would notify you as I would for a new sub-processor. The transfer would be covered by the safeguards provided for in Chapter V of the GDPR.
What happens to the data at the end?
When you disconnect a site or close your account, you can first export your figures, if your plan allows it: Standard, Advanced or Enterprise.
Then I delete the data of that site, at the latest 30 days after disconnection or closure. The copies present in the web host’s backups are deleted in turn, as the backups rotate, at the latest 90 days after. You can also ask me to delete this data sooner.
On request, I confirm the deletion to you in writing.
Liability
Each party answers for its own breaches of the GDPR, as Article 82 provides. For everything else, the liability rules in the terms of use apply, within the limits permitted by law.
If this agreement changes
A new version of this agreement is sent to you by email at least 30 days before it applies. It applies only after your agreement, given in the tool. If you do not accept it, the previous version continues to apply, or you can disconnect your sites and cancel at no cost.
An addition that only strengthens data protection, such as a new security measure, is announced to you by email and applies immediately. Changes of sub-processors follow the rules set out above.
Governing law
This agreement is governed by French law. The dispute resolution rules in the terms of use apply.
Page published on November 4, 2026 · Last updated on November 4, 2026
Start free