Security and privacy at The Wedding Pics

Guest contribution and couple management are separate flows; couples control what appears in shared views.

Plan storage dates are stated so couples can schedule original-file exports and preserve their own copies.

Security reports are triaged privately and corrections are documented when public guidance changes.

Guests use a private link made for your wedding. They do not receive your couple dashboard, password or account details. Signing in protects the controls used to manage the album, while the guest link allows only the wedding tasks you have chosen. Never put an owner password on a sign or in a group chat. If a helper needs to approve photos, give them a limited helper role where one is available, then remove it after the event.

Original photos, videos and audio are kept in a locked online store rather than a public folder. Before a file can move, the trusted part of the service checks the wedding, plan dates, available space and file rules. It then gives the phone a link that works for a short time. Large files travel straight between the guest’s browser and private storage. Smaller gallery previews are separate copies and appear only when the album’s approval settings allow them.

The page on a guest’s phone can offer helpful prompts, but the service must check the rules again in its trusted systems. Those checks cover file type, file size, album space, upload dates, approval and paid plan access. A payment provider must confirm a purchase before paid features are opened; simply landing on a success page is not enough. Guests also never write straight into the main database. These checks keep the same rules in place across different phones.

A contribution link, approved guest gallery and slideshow can have different audiences. Couples decide whether uploads remain owner-only or approved items appear in shared views. Public galleries and slideshows should show only allowed, approved media. Tell guests about the real audience before upload and provide a removal route. A QR code is only a link; the destination settings create the access model.

Use a password that you do not use anywhere else. Turn on two-step verification where it is offered; this asks for a second check as well as your password. Keep your recovery email up to date and notice unexpected login or billing messages. The National Cyber Security Centre recommends this extra check for important accounts. Do not reuse a wedding supplier password or send yours to a temporary helper. Sign out old devices and remove helper access after the final download.

Give yourselves enough time to collect, approve and download every original. Write down the upload closing date and the date online storage ends before the wedding. Download the full collection, compare the item count and open several large photos and videos. Make another backup in a separate safe place before asking for deletion. The main copy and a recovery copy may be removed at different times, so the service should explain both dates in plain language.

A guest album needs protection from automated spam, but that should not force every relative to create an account. A quick challenge can help show that a real person is uploading. The service still checks every file and wedding rule. It may also limit how many requests arrive at once, use links that expire quickly, watch for faults and retry safe background jobs. No single step creates perfect security. Several clear checks work together to keep the wedding journey reliable.

Send a security concern through the private contact route. Include the page, time, what you expected and safe steps that help the team repeat the problem. Never place another family’s private media in a public post. The team looks first at how many people could be affected and deals with urgent protection before writing a longer explanation. Help pages should be corrected whenever the product or advice changes.