Respond to enquiries
The details help Sparkles understand the request and contact the person who submitted it.
Privacy foundation
How website enquiries are handled at this checkpoint.
This interim notice explains the website’s current enquiry records. It requires client and legal review before production launch.
The Sparkles approach
The forms collect only the details needed for a first response.
Book-a-Visit and Contact submissions are saved as private WordPress records before an email notification is attempted. Authorised administrators can review the record and its notification status.
- Private WordPress records
- Consent captured
- Retention review required
Checkpoint policy foundation — client approval and production legal review are still required.
Information used
What the forms collect and why.
Contact details, nursery preferences and the message you choose to send are used to respond to your enquiry. Visit requests also ask for a broad child age band and practical visit preferences.
Route to a setting
A nursery preference helps the team identify the most relevant location.
Diagnose delivery
Administrators can see whether WordPress handed the notification to its mail system.
Control and retention
Access should stay limited and records should not be kept indefinitely.
The client must approve a specific retention schedule, controller details, lawful bases, rights process, cookie position, processors and complaint route before production.
Administrator-only
Enquiry post types are not publicly queryable and do not appear in the WordPress REST API.
Retention review
Administrators are warned to delete personal records when they are no longer needed.
Questions
Contact Sparkles for a privacy query while the final policy route is being approved.
Your next step
Come and see whether Sparkles feels right for your family.
Meet the team, explore a setting and ask about the practical details that matter to you.