How to collect party photos from guests with Madali
The camera roll is not the hard part. Getting everyone's pictures into one place is. At a small party, the usual result is a few photos in a group chat, several more promised later, and the best ones still sitting on somebody else's phone.
A better system has four parts: decide where the files will live before the party, give guests one simple way to add them, keep new uploads private until the host reviews them, and ask two or three people to remember to take pictures.
Choose the home for the photos before the party
Use a place the host controls and can keep after the event. With Madali, the host connects Google Drive and Madali creates a private folder for that celebration. The media files and their display copies live in that Drive folder. Madali keeps the event metadata and protected Drive references needed to run the gallery; it does not keep a permanent media copy in Firebase Storage.
Put the upload path inside the invitation
Do not make guests hunt for a second link after the party. Once a guest saves their RSVP and accepts the photo terms, the same private browser invitation can show Add a photo when the host has uploads open. The guest does not need the Madali app or a Madali account. In the app, eligible event members can take a photo or choose one they already have.
The browser flow chooses one image at a time. That small limit is useful at a gathering because it encourages people to add the pictures worth keeping instead of dumping an entire camera roll.
If your first problem is getting the answer at all, start with the no-app RSVP guide.
Give two or three people the job, not one person
One official photographer can miss the party while documenting it. Instead, ask two or three people for different kinds of pictures: one person for the room and decorations, one for people talking and laughing, and one for the cake, toast, or main moment. Everyone else can still contribute, but the whole memory of the day does not depend on one phone.
Keep uploads private first
A new Madali upload does not go straight into the group gallery. The host can see what arrives. After processing and screening, the uploader can see their own approved photo. Other guests see only the photos the host chooses to publish.
The host can close uploads at any time, set a per-person allowance from 1 to 50 photos, and choose up to 200 processed photos for the shared gallery.
What happens to location data
Madali's official app and browser upload flows re-encode the image before permanent storage. The app explicitly removes the JPEG metadata blocks that can contain EXIF, XMP, and GPS data, and the browser creates a fresh JPEG through the browser canvas. Madali also creates smaller display copies without EXIF metadata.
Screening is a guardrail, not a promise
Uploads are screened with Google Cloud Vision SafeSearch before they can be shared. Photos that are still processing, fail processing, or are quarantined do not enter the guest gallery. Screening cannot guarantee that every objectionable image will be caught.
Visible photos also have a Report action. A report records the photo for host review; it does not automatically hide the photo. The host can remove it from the gallery and block further uploads when needed.
Which Madali option includes photos?
Event photos are a host-paid feature. Madali offers a single-celebration option and account-wide options inside the app. The single-celebration option can be activated for an eligible stand-alone event and collection remains available through 30 days after that event's scheduled start. Continuous Circle photo memory needs an account-wide option. Guests and helpers never pay.
After collection closes
Closing collection does not remove the folder from the host's Google Drive. Madali also keeps read access to a gallery that was legitimately opened, even after its paid collection period ends. The host still controls the Drive files, so important memories should be backed up like any other files you care about.
One invitation for the answer and the pictures.