Privacy policy · November 6, 2026

Your night.
Your data.

Festive Glow follows the festive season one celebration at a time, and helps neighbours share candy on Halloween night. It has no ads, analytics SDK, background location, or account sign-up form.

An anonymous account

The live app uses Firebase Authentication to create an anonymous account with a random user ID. That ID controls your porch and prevents duplicate check-ins and reports. We do not ask you for a name, email, phone number, or address to use the app.

Lists, reminders and games

The festival screens, get-ready lists, feast plan, reminders and games work on your phone and ask for no location, camera or photos. The lines you tick, the lines you add, your guest count and dinner time, your reminder times and your best scores are stored only on your phone. They are never uploaded, logged or given to any AI model. Reminders are local notifications: the app asks for notification permission only when you tap Remind me, and it registers for no push notifications. Delete my data removes all of this, and you can turn notifications off in iOS Settings at any time.

Location and public porch content

While the app is open, location helps find lights within five miles and point toward a selected porch. Area searches send coarse geographic query ranges to Firebase. We do not store a hunter’s GPS route or live position in our database.

If you choose to host, we store your exact porch position and an approximate map position under your anonymous ID. Other app users see the approximate position. While your light is on, a user selecting it can retrieve the exact position for the compass. There is no address field, but someone guided to a porch can learn where it is.

Any candy instructions and porch photos you choose to publish are available to other app users while your light is on. Host photos are resized and re-encoded before upload. Do not include faces, names, house numbers, or contact details. A draft of your hosting settings and photos may remain on your own phone for reuse.

Checking public content before sharing

When you publish candy instructions, Google Cloud Natural Language checks the text for unsafe content and personal details. Public porch photos first pass face and text checks on your phone. If those local checks are unavailable or fail, photo sharing is disabled.

After local checks succeed, the app asks each time before sending porch photos to Google Cloud Vision and Natural Language for additional safety checks. Declining keeps those photos private; you can remove them and share instructions without photos. Local analysis results are not uploaded. The server independently checks the submitted image and any text it finds. These checks can make mistakes; use the report and hide controls for content that concerns you.

This service never receives candy-counting photos, hunter locations, or host coordinates. A short-lived private approval stores the submitted instructions and approved photo copies so the database can verify that the published content matches what was checked. Approval expires after 15 minutes. Separate abuse-prevention counters, linked to a hash of the anonymous user ID, expire after 48 hours. Automatic deletion follows expiry as described below. Turning off or deleting your account also removes your approval and its photo copies.

Check-ins, reports, and hidden hosts

A check-in stores a marker linking your anonymous ID to a light, with an expiry time. The app displays aggregate check-in counts, not a list of visitors. Hosts can see counts for each half hour. Reports store an anonymous marker, time, expiry, and the host’s aggregate report count. Report markers and counts prevent a host clearing reports by switching off and on.

The list of hosts you hide stays on your phone. Your local candy totals and check-in history also stay on your phone.

Candy photos and the ghost

Candy counting happens on your device. The app stores candy counts, not copies of candy-counting photos. The ghost uses Apple’s on-device model when available, or built-in replies. Cloud AI is disabled in the first App Store release: chat questions and candy-counting photos are not sent to Gemini.

The pretend-lights tour uses a fixed location and temporary, local data. It does not post tour porches or activity to Firebase. Starting the live app before the tour may already have created an anonymous account and fetched the event schedule. Native maps may still request map tiles.

Service providers

Google Firebase provides authentication, database storage, and this support website; Google Cloud runs the content-checking service and its Vision and Natural Language APIs. The app database is in Google Cloud’s us-west1 region. Apple Maps provides the iOS map. These services process the network and technical information needed to operate, such as IP addresses and service requests. We do not use that information for advertising or track you across other companies’ apps or websites.

The moderation providers process submitted content to supply their services, subject to Google Cloud data-protection terms. Google documents how it protects and uses Vision image data and Natural Language text. Their immediate-response APIs process content in memory, while operational request metadata may be retained for service operation and abuse prevention. These provider rules are separate from the short-lived approval copies described above.

Our moderation service’s operational request and application logs use a 30-day retention period. Request logs may contain IP addresses, user-agent information, response codes, request sizes, and timings needed for security and troubleshooting. The service does not log submitted photos, candy instructions, authorization tokens, or extracted photo text. These logs are not used for advertising or behavioural analytics.

If you email support, your email address and the information you include are used to answer the request. Please share only what is needed. You can request removal of support correspondence by replying to it.

Expiry and deletion

Real lights are limited to the configured Halloween event. Turning off removes your public light, exact position, porch photos, and host tally. Expired lights are excluded by the app, and expired exact positions and photos cannot be fetched through the app’s access rules.

Automatic database deletion runs asynchronously, usually within 24 hours of an item’s expiry. Separate expiry policies cover lights, exact positions, photos, check-ins, reports, host report totals, host tallies, content approvals, and moderation counters. Some report markers remain until the end of the event to prevent abuse.

To delete your anonymous account and saved app data, open Safety → Your data → Delete my data. Public porch data is removed before the account is deleted, and your lists, added lines, reminders and scores are cleared from your phone. Minimal activity markers already associated with other lights expire automatically as described above; aggregate counts do not identify you. Using the live app again after accepting the safety notice creates a new anonymous account.

You can also remove location and camera access in iOS Settings. The app has no background location permission. Contact support if you cannot complete deletion.

Contact and changes

Festive Glow is operated by Anubhav. Email Email support for support or privacy questions. Material changes to this policy will be reflected here with an updated date and, when relevant, in the app.