Privacy
What this site collects, why, how long it is kept, and how to have it deleted. It is short because the site does very little: there is no analytics, no advertising, and nothing loads from a third party.
Last updated
Who is responsible for your data
Forecaist (“we”) decides why and how the information described here is processed.
You can reach us at tempmaillouis@gmail.com.
What we collect
One thing: what you type into the contact form. There is no account to create, nothing to buy, and no payment to take.
Asking for a call is optional. If you leave that part alone, none of it is sent — including your timezone, which we do not collect from people who did not ask to talk.
When you submit the form we store exactly these, and nothing else:
- Your name
- Your company
- Your work email address
- Which answer you picked to “what consumption data do you have today?”
- The message you wrote
- If — and only if — you ask for a call: the days and times of day you marked, and the timezone your browser reports
- The date and time the message arrived, in UTC
What we do not collect
This is the part most policies leave out, so it is stated plainly.
- No analytics of any kind — no Google Analytics, no page-view counting, no heatmaps, no session recording
- No advertising or tracking pixels
- No third-party embeds — no video players, maps, chat widgets or review widgets
- No fonts fetched from a third party: the typeface is served from this site, so opening the page tells nobody else that you did
- No profiling, no automated decision-making, and no sale or sharing of anything for marketing
- No newsletter, and no adding you to a sequence because you wrote to us
Cookies
This site sets no cookies. There is no consent banner because there is nothing to consent to.
If you switch the site between light and dark, that single preference is saved in your own browser's local storage. It stays on your device and is never sent to us.
IP addresses
The contact form is rate-limited so that a script cannot flood it. To do that, the server holds the IP address a submission came from in memory for a few minutes and then discards it. It is never written alongside your enquiry, and we do not use it to identify you.
Our hosting provider keeps its own server logs, as any host does. Those are the provider's records, kept for security and operations.
Why we are allowed to hold it
You sent us a business enquiry and we need the message in order to answer it. Where the law frames this as a lawful basis, the relevant ones are that the processing is necessary to take steps at your request before any contract, and our legitimate interest in replying to people who ask us about our service.
We do not rely on consent for this, because we do not do anything with the message beyond replying to it. That also means there is no marketing consent to withdraw.
Where it goes and who reads it
The submission is written to a file on our own server. We read it ourselves and reply ourselves; there is no sales team it is handed to.
We may also have the submission delivered into the messaging tool we use day to day, so that a new enquiry is noticed rather than sitting in a file. Where that is switched on, the tool's provider processes the message on our behalf under its own agreement with us.
Nothing is sold, rented, or shared for anyone else's marketing.
How long we keep it
Enquiries are deleted 24 months after our last exchange with you, unless we have gone on to work together — in which case the records that belong to that engagement are kept under the agreement covering it.
You can ask us to delete yours sooner, and we will.
Your rights
Depending on where you live, you have some or all of the following. We will act on any of them, and we will not ask you to justify the request:
- Ask for a copy of what we hold about you
- Ask us to correct anything that is wrong
- Ask us to delete it
- Object to us holding it, or ask us to restrict what we do with it
- Ask for it in a portable form
- Complain to the data protection authority where you live, if you think we have got this wrong
Changes to this page
This page was last updated on 6 September 2026. If it changes materially we will change that date, and the previous version is in this site's version history.