1. Client-brief notice
Suggested text near “Send Brief”: “We’ll use your name, work email and project details to respond, assess fit and prepare a proposal. FormSubmit delivers your submission to our team. Please do not include passwords or sensitive personal data in your brief. Read our Privacy Policy for retention and your choices.”
The privacy link should be visible before submission, not only in the footer. Check that this wording matches the form’s real delivery path.
2. Contact-form notice
Suggested text near “Send Message”: “We use the details you provide to reply to your enquiry. FormSubmit sends the message to our inbox. Please avoid including sensitive personal information. See our Privacy Policy for details and deletion requests.”
3. Student-application notice
Suggested text before leaving for Google Forms: “Applications open in Google Forms. We ask about your skills, experience and availability and may ask for age and guardian details. We use this to assess your application and contact you about next steps. If you are under 18, review this with a parent or guardian before providing information. Read our Privacy Policy.”
This is a draft notice, not a substitute for checking the actual Google Form fields, privacy link and consent flow. The form was not accessible for inspection in this review.
4. Policy scope & recordkeeping
Update the existing Privacy Policy so its domain and form scope clearly includes the Netlify preview or any production domain and the external application form. Verify listed processors, retention, the actual recipient of form email and how data requests are handled. Keep a record of the notice and consent version accepted where required.
← All trust & terms pages · Questions: team@echelleventures.com