Privacy
What we keep, and why.
Last updated 31 October 2026
Flashalive is a photo booth app that runs in a web browser. It takes photographs at parties and puts them on guests’ phones. This page says what it collects to do that, who can see it, and how to have it removed.
Who we are
Flashalive is a Wade.Technology product, provided by Wade Technology. Questions about this page, or about your information, go to [email protected].
Two kinds of people use it. Hosts set up an event and run the booth. Guests stand in front of it. A guest needs no account and gives us nothing to get their photos.
What we collect
Host accounts
Hosts sign in with Google or Apple through the Wade.Technology sign-in service (auth.wade.technology). Flashalive receives an account id, your email address and your name, and records which events you host or help run, and in what role.
The access request form asks for your name, your email address and a line about your event. It is passed to the sign-in service so a person can approve you by hand. You may also add a phone number. It is optional, it lets Steward, our support assistant, recognise you when you call for help, we never call you unless you ask, and we never share it.
Events
What you enter about an event: its name, venue and city, time zone, booth settings, and the brief you give Higgins — who the day is for, how to spot them (what they will be wearing), and the occasion or theme.
If you upload a photo of your invitation, it is sent to our AI service once, to read the details off it so you do not have to type them. The picture itself is not stored. The details it reads are filled into the form for you to check and save.
Photos
Each photo taken at the booth is stored, with its size and the date and time it was taken, grouped by the guest’s turn at the booth. Photos are kept in Wade.Technology’s storage: on our own server, or in Cloudflare R2 cloud storage. They are served to you through this site, never from a public storage address.
We count how many times each guest’s link is opened, so the host can see how many guests picked their photos up.
Requests to take a photo down
Under every photo a guest can see there is an Ask to remove this photo button. A request records the photo, the event, the time, and a note of up to 280 characters if the guest writes one — and later, whether the host hid the photo or dismissed the request. It does not record who asked: no name, no email address, no account and no IP address. To stop the button being pressed over and over, the server keeps a scrambled form of the requesting address in memory for ten minutes, scrambled with a key that is never written down and changes whenever the server restarts.
Guest lists and the gallery email
A host may paste a guest list — names and email addresses, and any short label they add — so that after the event everyone on it gets one email with a link to the event’s photos. The event’s hosts are added to the list too. Nothing is sent until a host has seen the list and scheduled the email. We record, for each address, whether the email went out.
The email contains a greeting, the event’s name, the name of the person it was for if the host gave one, the number of photos, and the link. It is sent from a wade.technology address through our mail provider, Migadu.
“Keep these forever”
A guest may give their email address on their gallery page to keep an account for their photos. The address goes to the Wade.Technology sign-in service, which sends them a link to sign in with. Once they sign in, we record that the account belongs to that event and to their turn at the booth, so the photos are there on any phone later.
Hosts can also invite co-hosts, operators or guests by email; the address is stored with the invitation.
Statistics
Hosts see counts for their own events: turns at the booth, photos, links opened, accounts kept, and how Higgins’s AI calls went (how long they took and what they cost). None of this goes to an advertiser.
Visitors to our public pages
On our own public pages (the home page, pricing, tips, privacy, terms, sign-in and the order and welcome pages) we count what visitors do, so we can see whether the site is clear and fix what is not. We do it ourselves, on our own server. There is no Google Analytics, and we do not fingerprint your device. The one outside service on these pages is Meta’s pixel, for our Facebook and Instagram ads, described below. We never track the pages a guest uses to see their photos, the booth or the host pages.
- What we count: the page you opened, the site you came from (its name only), any campaign tag on the link, how far down the page you scrolled, which buttons you pressed (such as Order now, See pricing, Try it now), which kind of event you picked, the words you typed into “Something else”, and whether you tried the demo (if you turned the camera or sound on or off, and how long you watched). If you order, we connect that order to the same browser, so we can see which visits lead to an order.
- Your camera in the demo: the demo asks your browser for the camera when you open it. You can say no, or untick Use my camera, and Higgins shows a sample photo instead. If the camera is on, Higgins looks once, the way he does at the booth: one small still frame goes to our AI gateway so he can see who is there and direct you by where you stand. It is used for that one request and not stored or logged. Then the one picture Higgins takes is held in our server’s memory for 10 minutes so the code at the end can open it on your phone, then it is deleted. Closing the demo deletes it at once. It is never written to disk, never put in a gallery and never tied to you, and only someone holding that code can see it. We also note that the camera was switched on or off.
- What we keep about you: a random number in a cookie, your approximate location (country, state and city, never your street address or exact position) taken from your connection, and only the kind of device (phone, tablet or computer). Your IP address is never stored: we keep a scrambled form of it that changes every day, so it cannot follow you from one day to the next. We do not store your browser’s details.
- If you ask not to be tracked: if your browser sends Global Privacy Control or Do Not Track, we set no cookie, give you no number, keep none of your words, and count your visit only as part of a total.
- How long: the counts are kept for 13 months. The words you type (to Steward or into “Something else”) are kept for 90 days, with email addresses, phone numbers, street addresses and web links hidden before they are stored.
Facebook and Instagram ads (Meta)
We advertise on Facebook and Instagram. To learn which ads bring people who actually use Flashalive, our public pages load the Meta pixel, and our server tells Meta (through its Conversions API) when one of these steps happens: a visit to a public page, pressing Try it now, creating an account, creating a free event, pressing Order now, and a paid order. Meta, Inc. receives these under its own privacy policy.
- What Meta receives: which of those steps happened and when, the page address, the campaign tag on the link, your IP address and browser type, and Meta’s own cookies (
_fbp, and_fbcif you came from an ad). For a paid order we also send the order’s email address scrambled one-way (SHA-256), as Meta requires, so Meta can match the order to an ad; the address itself is never sent. We never send your name, phone number or photos. - Where it is not used: never on the booth, on an event’s pages, or on any page a guest uses to see their photos. On the host pages the pixel loads only at the moment you create an account or a free event, to report that one step.
- If you ask not to be tracked: if your browser sends Global Privacy Control or Do Not Track, the pixel does not load and our server sends Meta nothing about you. You can also manage ad tracking in your Facebook or Instagram settings.
Higgins and the camera
Higgins is the booth’s photographer. When the booth’s AI setting is on (it is on unless the host turns it off), the booth sends one small still frame from the camera when a guest starts, and a small copy of each photo just taken so he can react to the pose, to Wade.Technology’s AI gateway (Aspen). The gateway passes it to an AI model, run by a third-party AI provider, which reads the scene and writes Higgins’s next lines. The event’s brief goes with it.
These frames are not stored and not logged by Flashalive. Each is used for that one request. (The photos themselves are stored, as above.)
To pitch his tone, the model makes a rough read of the group: how many people, how they are grouped, the general energy, and a broad sense of the age mix (for example, whether children seem to be there). That read is used for that shoot and shown on the booth’s operator panel. It is not stored, and Higgins never says it aloud: anything he would say about a person’s age, gender, body, skin, ethnicity, disability, clothing or looks is blocked before it is spoken. He addresses people by where they stand.
What is stored, for the host’s Higgins log: the head count, the tone he chose, the lines he said, and a short note on what he reacted to, described by position and action. No image is kept with it.
Higgins does not recognise faces or identify anyone. If the host tells him who the day is for and what they are wearing, he may greet someone by that name when he sees that outfit — nothing more.
His voice is generated from the text of each line through the same gateway. No image is sent for that.
Who can see the photos
- Anyone holding a link or QR code. The code shown after a guest’s turn opens that turn’s photos. A single-photo code opens one photo. The gallery link in the email opens every visible photo of the event. These links work without signing in, so whoever has one can see what it opens. We store only a scrambled form of each link, never the link itself, and we do not record who was given which link.
- Every guest, unless the host says otherwise. By default an event’s photos are shared with its guests, and the booth says so on screen before anyone steps up: “Photos from this booth are shared with this event’s guests.” A host can instead choose each guest sees only their own set. Then the gallery link and the gallery email are switched off, the booth says the photos go to the guests in them and the hosts, and each guest’s own code and any single-photo code still work.
- Guests at the booth. For thirty minutes after a turn, the booth can show it among at most twelve recent turns, so a guest who missed their code can find it.
- The event’s hosts and operators see every photo of the event.
- Wade.Technology staff who run the service can reach stored photos when they need to, for example to answer a removal request.
A host or operator can hide a photo: it disappears from every gallery and link but still exists, and can be brought back. Only a host can delete one: it is removed from the gallery and from our storage, and it cannot be brought back.
A host can reset the gallery link: every gallery link handed out so far, including the one in the email, stops working at once, and a new one is made. The codes guests scanned at the booth are not affected.
Guest galleries, single-photo pages and the photos themselves tell search engines not to index them.
How long we keep it
Photos are deleted automatically. A full event keeps its photos for 90 days after the booth closes (the booth is open for 48 hours from midnight on the event date). A free trial event keeps them for 14 days. A host can pay to keep an event for a year; each purchase adds 365 days. We email the host 14 days and 3 days before the deletion date, and a host can download every photo as one ZIP at any time before then.
When the date arrives, the photo files, the photos, the guest list, the gallery and photo links, the requests to take a photo down and the Higgins log for that event are all deleted, and the links stop working. A link stops working at the deletion date even if the files are still being removed. A host can also delete an event, or a single photo, at any time, or you can ask us to. Deleting a photo deletes the requests about it. We keep a record of purchases (the email address, order number and amount) for our accounts, and a count of how many free trial events an account has made, after an event is gone.
Events created before 17 October 2026 are not deleted on a schedule; they stay until the host deletes them, or until you ask us to.
Cookies and storage on your device
When you sign in, we set one cookie, rc_session, that keeps you signed in on that device for up to thirty days. It cannot be read by scripts on the page. Signing out removes it. A guest who only opens their photos gets no cookie from us.
On the public pages above we also set one cookie, rc_vid, a random number that lets us tell a returning visitor from a new one. It lasts at most 13 months, scripts on the page cannot read it, and we do not set it if your browser sends Global Privacy Control or Do Not Track. Delete it in your browser at any time. Each browser tab also keeps a random session number in its own memory while the tab is open.
Meta’s pixel sets its own cookies on the public pages: _fbp (a random number, up to 90 days) and, if you came from a Facebook or Instagram ad, _fbc (the ad click). We set a short cookie, rc_px, for up to ten minutes after you create an account or a free event, so the page can report that step; it holds no personal information. None of these are set if your browser sends Global Privacy Control or Do Not Track.
The device running the booth keeps its own booth settings (camera calibration, voice, style) in the browser’s local storage. Nothing else is stored on your device by Flashalive.
Help from Steward
Anyone visiting this site, signed in or not, may ask Steward, Wade.Technology’s assistant, a question from the chat button. What you type, the last few turns of the conversation and the page you are on are sent to Steward to answer it, and the answer comes back to you. If you are signed in as a host, your name, email address and a summary of your own events (their names, dates, status and photo counts) go with it. If you ask for something Steward cannot do, such as a fix or a refund, the conversation is passed to our team, with your email address if you were signed in. Nobody else’s events are shared. Please keep passwords and payment details out of the chat. Steward runs on Wade.Technology’s AI gateway; the questions are not used for advertising. On the public pages, if you are not signed in, we keep your question and Steward’s answer for 90 days, with email addresses, phone numbers and street addresses hidden, so we can see what visitors need and improve the answers. We do not keep the words of a signed-in host’s chat. We limit how many questions one address can ask, by keeping a scrambled form of the address in memory for a short time; the address itself is not written down.
Your choices
- To see what we hold about you, or to have it deleted, email [email protected].
- To have a photo of you removed, press Ask to remove this photo under it: the host sees the request and can hide it at once. You do not have to say who you are. You can also ask the host directly, or email us and we will.
- To be taken off a guest list, ask the host, or email us.
Changes
When what Flashalive does with information changes, this page changes with it, and the date at the top moves.
See also the terms of use.