Symphony of Grace 2026

Your information.
Handled with care.

This page explains how the SOG ’26 registration website handles information you submit. For questions or requests, contact soghelpdesk.com@gmail.com.

What the registration form collects

Your selected category, age group where applicable, participant or responsible person’s name, contact number, church or organisation, group size, signed consent form, and your agreement to the event rules and this notice. A registration ID, submission time and fee/payment status are recorded with your entry.

How organizers use it

Authorized organizers use these details to manage entries, check eligibility and church limits, contact participants, review consent, plan the programme and reconcile fees. For an under-15 entry, a parent or guardian should provide the contact number and authorize the submission.

Private storage and backups

Registration records are stored in a private Supabase database, and consent files in private storage. An Excel copy helps authorized organizers manage entries. A separate private backup is held on Vercel. Consent forms and exports are not public, and temporary download links expire.

Payments and external links

This site does not collect card details or take online payments. Fees may be paid at the venue. WhatsApp, map and email links open separate services with their own privacy practices.

Access, corrections and deletion

Contact the helpdesk with your registration ID to request access, a correction, or deletion. Organizers will verify the request and explain any records that need to be retained for event administration. Owners can remove an entry from active lists and exports. Deleted entries, consent files and payment history stay in a private, recoverable archive with an audit record; contact the helpdesk for a permanent erasure request. This site does not automatically delete registrations or backups on a fixed date.

Technical information

Hosting providers process technical access information to operate the service. The application uses a one-way hash of the connection’s IP address for rate limiting. Personal form fields are not sent to analytics. Organizer sign-in uses secure session cookies; participant details are not saved in your browser’s local storage.