Privacy notice
How booking information is handled.
Last updated 2 September 2026
Information collected
The booking form collects the requested session, venue, organisation, estimated attendance, point-of-contact name, email address and telephone number, optional remarks, and an optional participant namelist.
Why it is used
The information is used to reserve and review the RPP request, contact the point of contact, prepare the deployment schedule, manage namelists, and maintain an operational record of actions taken.
Where it is processed
The booking interface is hosted on Cloudflare Pages. Operational booking records, uploaded namelists, email delivery and the deployment schedule remain in the authorised Google Workspace and Apps Script environment used by the 4th Division Community Engagement Branch.
Who can access it
The public does not have access to booking records or the deployment workspace. Access is restricted to approved CEB members, with separate permissions for schedule editing and booking approval.
Retention and enquiries
Records are retained according to the applicable operational and records-management requirements. For a correction or privacy enquiry, contact the Community Engagement Branch using the contact details in your booking correspondence.
Private-workspace cookie
The private workspace uses a secure session cookie to keep an approved member signed in on that browser. The public booking form does not create a staff account.
Workspace performance and access records
Recently read workspace data is temporarily stored in the current browser tab to make navigation faster. Access is checked before that data is reused, and sign-out clears the tab cache. Avoid shared browser profiles and sign out on shared computers. Member email addresses, permissions and access changes are stored in the Google Apps Script environment; additions, removals and permission changes are included in the operational action history.