Preview and live operation

In preview mode, the supplied staff photos are examples and live submissions are disabled. When configured, school Google sign-in verifies your account. The app stores a pseudonymous account identifier, pet details, photo URL, permissions, review status, timestamps, and your vote. It does not request student IDs, grades, attendance, or passwords.

Use and visibility

Approved pet details are visible to signed-in participants. Owner emails and individual votes are not shown in the gallery. Administrators review entries and view participation totals. Submitting under the November 3, 2026 terms permits Highlands to share the photo, pet name and description on its official public social media, visible outside the school. Previous submissions retain their original permissions. The app does not post automatically. Contact the coordinator to withdraw permission.

Services and storage

Firebase provides Google authentication; Coda stores contest events, submissions, photo permissions, review decisions, and individual ballots; Netlify hosts the application and functions; Cloudinary stores uploaded images. Cloudinary image URLs can be opened by anyone who has the link, including pending images. Authorized Coda document editors can access stored ballots and pseudonymous account identifiers. The Coda document is restricted to designated administrators. Optional reports contain pet details and permissions, not individual ballots. The app stores your language choice in this browser; Firebase may persist your sign-in session. Hosting providers may process operational logs. No advertising or analytics scripts are added.

Netlify also stores the authoritative contest events and permissions. Confirmed saves are copied to Coda in the background. Deletion requests must cover Netlify records and pending copies as well as Coda and Cloudinary. Administrators must stop syncing before coordinated deletion so that removed records are not copied back.

Control and retention

During submissions you can edit your entry; edits require review again. You can withdraw before voting begins. Withdrawal hides an entry but does not delete all stored copies. Contact the school coordinator to request deletion, withdraw social permission, or correct data after voting begins. Coda event records, optional reports and Cloudinary images require administrator deletion; there is no automatic retention purge. The school must finalize its retention period before launch.