Freelancers · Practical guide
A freelancer’s contact form: ask for less and inform in the right place

A contact form should ask for the information needed to reply, explain how it will be used at the time it is collected and route the message to a space you control. For a freelancer, a short form and a clear handling process are often more useful than a pile of fields and generic tick boxes.
Start from the reply you need to give
Write down the task the form should make possible: answering a question, making first contact or preparing an appointment. For each field, ask what would prevent you from replying if you did not collect it. A phone number, a postal address or an attachment are not automatically necessary.
Distinguish mandatory and optional fields in the interface. If you never phone at first contact, making the number mandatory creates a collection that is hard to explain. For a simple enquiry, a reply address and a message may be enough, depending on your business.
Frame the free-text message
A text box lets visitors explain their needs, but also send sensitive information you did not ask for. Add a short, suitable instruction: do not include a password, an identity document or medical details if your service does not require them.
In its sheet “Managing software development” dated 14 March 2024, the CNIL, the French data protection authority, recommends building data protection in from the design stage, in particular through data minimisation, and avoiding free-text fields, which are sources of additional, unnecessary or excessive data collection. If a free-text message remains essential to understand the enquiry, the instruction above becomes all the more useful. Read its development recommendations (in French). If documents are essential later on, offer a suitable channel at that point.
Inform in the right place
Provide concise information next to the form and easy access to the relevant details: controller, purposes, legal basis, recipients, retention period or criteria, rights and contact. The exact elements depend on your processing. According to the CNIL, the GDPR requires information that is concise, transparent, intelligible and easily accessible, as defined in its Articles 12, 13 and 14.
The CNIL sample privacy notices (in French) are starting points to adapt: the CNIL itself presents them as basic illustrations, built around a fictitious company called ABCD, to be adapted or completed, and not as templates valid in every situation. Do not copy the name of a fictitious company, a retention period or a legal basis without linking them to the way you actually work.
Do not use one tick box for everything
An “I accept the GDPR” box explains neither how the data is used nor the appropriate legal basis. Handling a contact request may rely on a basis other than consent, depending on its purpose. Determine it and explain it rather than choosing a tick box out of habit.
Signing up to a newsletter is a different use. If you offer it, keep that choice separate from the contact request and apply the rules in the guide to email marketing. Sending a question must not be automatically interpreted as a subscription.
Follow the message after the send button
Identify the form, any provider, the inbox, the notifications and the file into which you copy the enquiry. A copy of the message in several tools must serve a purpose and have a retention rule.
Also check who can access attachments and whether they are protected against public access. The provider’s contract is covered in the guide to processors. The visible form is only the start of the journey.
Test the journey with fictitious data
Run an authorised test with a fictitious name, a test address under your control and a harmless message. Check receipt, the copies created, the response to the visitor and how missing fields are handled. Do not run a test that would send a message to a real client: the CNIL advises against using real personal data for development and testing.
Keep the result and the corrections needed. A confirmation shown on screen does not prove that the message arrived in the right place. Finally, link this processing to your record and your retention rule.
Describe each field in a short sheet
To prepare the discussion with your provider, write one line per field: visible label, purpose, mandatory or optional status, recipient and storage location. Add the expected behaviour when a value is missing or contains an error. This worksheet makes it possible to link the text displayed to the way the message is handled.
Also specify the expected format: the CNIL recommends enforcing input formats that minimise the data collected. If only the year of birth is useful, for example, the field must not allow the month and day to be entered; a drop-down menu can limit the choices. It also points out that checks carried out in the visible part of a form can be bypassed and should be backed up by server-side checks. The answer depends on your service; it cannot be deduced from a form template.
A short acceptance test with three fictitious requests
Try, in turn, an ordinary request, a request without the optional field and an incorrect entry. For each one, note the message shown to the visitor and whether it actually arrives in the intended inbox or tool. An on-screen acknowledgement and receipt by your team are two results to check separately.
Also open the notification received: does it contain the entire message when a simple reference would be enough for your organisation? If a failure prevents sending, is the alternative contact method visible? This journey provides precise corrections to request from the provider, without using a real client file.
Sources and limitations
This guide draws on the public sources below. It explains documented features and a suggested method, without testing your account or device. Settings may vary by version and plan. Legal information concerns France and the EU where specified and is not individual legal advice. Sources may be in French.