Your information
Privacy policy
Last updated: 31 August 2026
This page explains what happens to anything you send MBDev through this site. It describes how the site actually works rather than repeating a generic template: every statement below matches something verifiable in its code and its hosting.
Who is responsible
MBDev is the freelance practice of Mikael Bergeron, based in Quebec. There is no team and no subcontractor: he receives the requests and he is accountable for the personal information.
For any question about this page or about your information: contact@mb-dev.ca
What the form collects
The request form collects only the following. Four fields are needed in order to reply to you; the rest are optional and can be left empty.
- Required: the project type, your description of the project, your name, your email address.
- Optional: the budget range, the timeline, your company name, your Discord handle, any extra details.
- Recorded automatically: the language you filled the form in, and the date it was received.
- Your IP address is held in memory for one minute, solely to limit how many submissions can be sent. It is never written anywhere.
- The form contains a hidden field meant for bots. If it is filled in, the request is discarded without being stored.
The detailed project journey
There is a second, longer journey for describing a project step by step. It collects the same categories as the short form, plus the following — all optional except your name and email address.
Your answers are kept in your browser while you fill it in, so nothing is lost if you close the tab. That draft lives on your device and nowhere else: it is not transmitted until you send, it is erased as soon as the send succeeds, and it expires after seven days.
- Your phone number, your Discord handle and your preferred way of being contacted, if you choose to give them.
- Your answers about the project: type, desired features, goal, current problem, intended audience, what you already have.
- Up to five web addresses you give as examples, and your notes. Those addresses are stored as-is: they are never opened or fetched automatically.
- The time elapsed between opening the form and sending it, used solely to spot automated submissions.
Why this information
To reply to you, understand your project, prepare an estimate and follow up on the exchange. That is the only use.
Nothing is used for outbound prospecting, there is no mailing list, and your information serves no purpose other than the one you sent it for.
Where it is stored
Requests are written to a file on a dedicated server located in Beauharnois, Quebec, rented from the hosting provider OVH. They are not handed to a third-party cloud service for storage.
Mikael Bergeron accesses it over a secured connection. As with any hosting arrangement, the provider has physical access to the machine.
The site's technical log keeps the date, the project type, the budget range and a file identifier for each request received — not your name, and not your email address. That trace makes it possible to confirm a submission arrived, and to find the matching file.
Who else can technically process it
No information is sold or disclosed for commercial purposes. Some providers are nonetheless involved in running the site and can technically process your information:
- OVH — hosts the server, in a data centre in Quebec.
- Cloudflare — all of the site's traffic passes through its network, which handles routing, encryption and protection against attacks. Cloudflare also routes email sent to contact@mb-dev.ca. Company based in the United States.
- Discord — each time a request comes in, an alert is posted to a private channel. It contains only the project type, the budget range, the timing and a file identifier: not your name, not your email, not your own words. Company based in the United States.
- Google — email routed to contact@mb-dev.ca lands in a Gmail mailbox. Company based in the United States.
Information leaving Quebec
Partly, yes. The main storage of requests stays in Quebec. However, the alert sent to Discord and the email routed to Gmail are handled by companies based in the United States, and the site's traffic passes through Cloudflare's network, which is also American.
The Discord alert is deliberately thin, whichever form you used. It contains only the project type, the budget range, the desired timing, the language and a file identifier. Your name, your email, your phone and your own words are not in it: they stay in the storage in Quebec, and that is where they are read.
These providers are used because they are dependable and because they let a one-person practice run a secure site. If you would rather your information did not leave Quebec, just say so in your message and we will agree on another way to correspond.
How long it is kept
For as long as it takes to handle your request and follow up on it. A request is deleted as soon as you ask, and at the latest twenty-four months after the last exchange.
If an engagement comes out of your request, the information tied to that engagement is kept for as long as the related accounting and legal obligations require.
Your rights
You can ask to see the information held about you, to have it corrected, to have it deleted, or to withdraw your consent. Write to contact@mb-dev.ca; you will get an answer within thirty days.
If that answer does not satisfy you, you can file a complaint with the Commission d'accès à l'information du Québec.
Cookies and analytics
This site sets a single cookie, named NEXT_LOCALE. It remembers the language you chose so you are not asked again on every visit. It does nothing else and cannot identify you.
There is analytics in place: Cloudflare Web Analytics. The site is served behind Cloudflare's network, and it is Cloudflare that adds a small measurement script to the pages it delivers — it is not part of this site's code. That script records page views and load times, and sends them to Cloudflare.
What we can establish, because it is verifiable in the browser: this measurement sets no cookie, and NEXT_LOCALE remains the only cookie on this site. What we consult is a table of aggregate statistics — visits, pages viewed, countries, browsers. It shows us no named data, and we do not attempt to identify anyone, or to match a visit with a request we received.
What we cannot guarantee on your behalf: what Cloudflare does with those measurements inside its own systems. That falls under its privacy policy, not ours. We would rather write it that way than promise you something we do not control.
There is no advertising cookie, no social network pixel and no share button.
How it is protected
The following measures are in place. They are reasonable and proportionate rather than absolute: no system is impenetrable, and claiming otherwise would be dishonest.
- Every page is served over an encrypted connection.
- The server exposes no web port to the internet: traffic reaches it through an encrypted tunnel.
- Access to the server uses a key, not a password.
- The form limits how many submissions can be sent per minute, per address.
- Access to received requests is restricted to Mikael Bergeron.
- Data submitted through the form is validated before being stored.
What is not done
To leave no room for doubt:
- Your information is not sold, rented or traded.
- No automated decision is made about you, and no profile is built. The detailed journey does produce internal markers — “this project involves payments”, “the budget is undefined” — but those are observations about the PROJECT, not about you, and nothing is decided automatically from them.
- No unsolicited commercial message is sent to you.
- The site is not aimed at minors and does not seek to collect their information.
Changes to this page
If how the site works changes — a new provider, a new field in the form — this page is updated and the date at the top changes. Earlier versions are not kept online; write to us if you need to know a previous state.
