Privacy policy
Celebrate: Photo Booth, by Headway Tech LLC. Last updated November 18, 2026, for app version 1.1.0 and later. Video messages and the 30-day gallery apply from version 1.3.0.
The short version. There’s no account, no sign-in, no advertising, no tracking and no analytics SDK. The booth’s photos stay on the iPad or iPhone running it. One thing leaves it while the QR code is on (it’s on for a new event; the host can turn it off): the finished picture (the strip, print or GIF) or video message goes to our server with the event’s name, its random ID and the host’s logo if there is one, so a guest’s phone can open it and the event gallery can show it. It’s deleted after 7 days, or 30 days when the host buys the 30-day gallery for that event. When the host turns on email, an address a guest types is used once to send the link, then deleted. Purchases go through Apple, and RevenueCat tells the app whether the booth is unlocked. The app checks for its own updates with a random install number. That’s all.
Who this covers
The host is the person who installs the app and sets up the booth. Guests are the people who use the booth at an event. Guests never make an account or type anything unless the host turns on email or the optional sign-up described below.
What stays on the device
Kept only on the iPad or iPhone running the booth, in the app’s own storage: the photos and GIFs taken, the finished designs, each event’s settings (name, date, look, layout), the host’s logo and background pictures, the settings PIN, the purchase state, and the last error message if the app had a problem. With Save to Photos on (it’s on for a new event; the host can turn it off in Settings), finished pictures are also saved to the device’s photo library. Deleting an event or the app deletes what the app kept; pictures saved to Photos stay there until the host deletes them.
Face filters find faces in the camera picture to place the filter. That happens on the device, frame by frame, with Google’s ML Kit face detection and Apple’s Vision framework. No picture or face data leaves the device, and nothing about a face is stored. ML Kit may send Google basic, anonymous diagnostics about how the face detection runs (such as the device model, app version and timing), as Google describes for ML Kit.
Guest sign-up (off unless the host turns it on): a guest may type an email address or phone number on the last screen. It is kept on the device for the host, who chooses what to do with it. We never receive it.
What our server keeps, and for how long
While the QR code is on (it’s on for a new event): the finished picture or video message of each session is uploaded to our server (run by Headway Tech LLC in Oregon, USA) so a guest who scans the code can open it, save it and share it. Stored beside it: a scrambled copy of a random token the app made when it was installed (so only that booth can add to its own shares), the picture’s type, the time, and, with each upload, the event’s random ID and the event name as the host typed it, which the event gallery and the party screen show. When the app sends it, the booth’s language (English or Spanish, set by the iPad or iPhone’s own language) is kept too, so the guest’s page and email come in that language; otherwise the page follows the language the guest’s phone asks for, which isn’t stored. When the host picked a logo, the app sends it for the event and it is kept with the event.
Video messages (version 1.3.0 and later, only when the host offers them): a guest records a short video with sound on the booth. The microphone is used only while a message records. The video stays on the device like a photo, and goes to our server only for the QR code, as above.
Everything is deleted 7 days after it was uploaded. When the host buys the 30-day gallery for an event, that event’s pictures, videos and logo are kept until 30 days after the purchase instead, then deleted. To confirm the purchase, our server asks RevenueCat about that one purchase, using the anonymous ID RevenueCat made and the purchase’s transaction number. The server keeps no request logs. Each day it counts requests per address to hold its limits; those counts are kept in memory and gone within the day. No guest names, no device identifiers, no Apple ID and no location are sent or kept.
Who can see a shared picture: anyone with its link, which is a random code that can’t be guessed. The event gallery and party screen show the event’s pictures to anyone with that event’s link. Neither is listed or searchable anywhere.
Email delivery (only when the host turns it on): the address a guest types is kept on our server only until the one email with the link is sent, and then deleted, or after 7 days if it could not be sent. The email is sent through Brevo (Sendinblue SAS), an email delivery service, which receives the address and the email to deliver it and keeps its own delivery records under its privacy policy. We never add the address to any list.
Purchases
Three sessions are free. The Lifetime unlock, the Event Pass and the 30-day gallery are bought through Apple. Apple handles the payment; we never see a card, a name or an Apple ID. RevenueCat, a service that handles in-app purchases for apps, tells the app whether a purchase is active. It knows the device only by an anonymous ID it makes, and keeps the purchase history under that ID, which its dashboard shows us as totals.
Updates
When it starts, the app asks Expo’s update service (expo.dev) whether a newer version of its own code is ready. That request carries the app’s version, the platform and a random install number. Nothing about the booth’s photos or events is in it.
Outside services
| Service | Used for | What it receives |
|---|---|---|
| Apple (App Store, StoreKit, AirPrint, AirDrop, Vision) | Purchases, printing, sharing, face finding | What iOS needs for each; printing and AirDrop send the picture only to the printer or person the host or guest picks. Vision runs on the device. |
| RevenueCat | Whether the booth is unlocked | An anonymous ID and the App Store purchase receipt |
| Google ML Kit | Face filters (on the device) | No pictures or face data; possibly anonymous diagnostics about the detection |
| Brevo (Sendinblue SAS), when email is on | Sending the one email with a guest’s link | The guest’s email address and that email. See Brevo’s privacy policy |
| Expo (expo.dev) | App code updates | App version, platform, a random install number |
| Our server (headwaytech.app) | The QR code, event gallery, party screen and email | The finished picture or video and the items listed above, for 7 days (30 with the 30-day gallery) |
Children
The app is for hosts running a photo booth and isn’t directed to children. Guests of any age may use a booth at an event; the host decides whether the QR code is on. We don’t knowingly collect personal information from children. A parent who wants a picture removed early can email us its link.
Your choices
The QR code is on for a new event. Turn it off in Settings and nothing is uploaded. To have a shared picture or an event’s pictures removed sooner, email [email protected] with the link, and we’ll delete it. We don’t sell or share any data, and we use it only to run the features named here.
Changes and contact
If this policy changes, the date at the top changes and the app’s release notes say so. Questions: [email protected]. Headway Tech LLC, Indiana, USA.