Privacy Notice

Who we are

MomentDrops is a wedding media collection service operated by Not yet configured — contact us for these details..

Registered business address: Not yet configured — contact us for these details..

For all privacy matters, contact Not yet configured — contact us for these details..

Information we collect

Account holders (couples): first name, surname, email address, account activity and authentication events.

Event details: the names you choose to display, wedding date, venue name and location, and any welcome message you write for guests.

Guest uploads: an optional guest first name, the media file itself, and technical upload metadata such as file name, file type, size, duration and upload time.

Payments: the amount, package, payment reference and payment status returned by our payment provider. MomentDrops never receives or stores your full card details.

Operational records: storage usage, retention and deletion records, and administrative actions taken on your account.

Optional post-wedding feedback: your scored and written answers, whether you permit testimonial use, and whether you permit us to contact you for clarification.

Media uploaded to an event

Photos and videos uploaded through an event QR link are stored privately and are visible only to the account holder for that event and to authorised MomentDrops staff who need access to operate or support the service.

Media is never made public by MomentDrops, is never sold, and is not used to train any model.

Why we process information

To create and secure your account and authenticate you.

To deliver the event service you purchased: collecting guest media, generating previews, providing the gallery and enabling downloads.

To take payment and keep the accounting and transaction records that follow from it.

To keep the service secure, prevent abuse and investigate incidents.

To meet legal and regulatory obligations that apply to us.

To review optional post-wedding feedback and improve MomentDrops. Feedback is never published automatically, and testimonial or follow-up permissions are optional. A quote is only shown on our website if you gave testimonial permission and we approved it, and it shows only your chosen display name and, optionally, your wedding location and month. You can ask us to remove it at any time.

Payment processing

Payments are processed by PayFast. When you pay, you interact with PayFast directly and they process your payment information under their own privacy terms. MomentDrops receives only the confirmation and reference data needed to activate your package and keep financial records.

Service providers

We use a small number of service providers to host the application, store media and process payments. The current register of providers, their processing locations and the review status of our arrangements with them is maintained internally and is available on request to Not yet configured — contact us for these details..

Cross-border processing

Some of our infrastructure providers may store or process information outside South Africa. We maintain an internal record of each provider, the region in which information is stored, the categories of information involved, and the status of our review of the applicable safeguards.

We do not claim that a transfer is lawful merely because a provider is well known. Where a review is still outstanding, our internal register records it as outstanding.

Service performance and wedding insights

MomentDrops records a small number of first-party service events so that we can operate, secure and improve the service. These are: when a guest upload page is opened while uploads are open, when a couple views their own gallery, and when a download or export starts, completes or fails.

We do not use Google Analytics, Meta Pixel, advertising cookies, cross-site tracking, device fingerprinting or precise-location tracking, and we do not link activity at one wedding to activity at another.

Giving a guest name is optional, and a guest name is never stored in these service-event records. The records contain no names, email addresses, IP addresses, browser, user-agent or device information, locations, filenames or captions.

Opening a wedding's guest page while its upload window is open may create one first-party cookie for that wedding. It contains only a random value, is HttpOnly (unreadable by page scripts), Secure in production, SameSite=Lax, and expires after 12 hours. Each wedding has its own separate cookie.

The raw cookie value is never stored. Our servers keep only a one-way, wedding-specific digest of it, so activity at two weddings can never be matched to the same person.

Detailed service-event records are kept until 30 days after that wedding's gallery-retention period ends. They are then replaced by anonymous totals — counts and dates only — and the detailed records are deleted.

Deleting a wedding also deletes its detailed activity records, its totals and the internal wedding-insight notes we keep about supporting that wedding. Properly anonymised totals may be retained only where they can no longer identify, or be linked to, a person.

Wedding Insights exists for service operation and improvement. It is never used for advertising, profiling or marketing.

How long we keep information

Event media is retained for the retention period of the package purchased for that event, followed by a recovery grace period, after which it is permanently deleted from storage.

Account information is retained while your account is open, and is minimised when your account is closed.

Payment and accounting records are retained separately from your profile and media. The retention period applied to those records is a business configuration value (Not yet configured — contact us for these details.) and is subject to confirmation by our accountant and legal advisor. We do not invent statutory periods in software.

Post-wedding feedback is retained with its event unless a valid privacy request requires earlier deletion. Submitted feedback is final and read-only for the account holder.

How we protect information

Media is stored in private storage that is never publicly readable. Access is issued as short-lived signed links only after ownership has been verified server-side.

Database access is governed by row-level security so that one customer can never read another customer's data.

Guest upload sessions use opaque secrets stored as hashes only, in HttpOnly cookies.

Administrative actions are recorded in an internal audit log.

Your rights

You may ask us for a description of the personal information we hold about you, ask us to correct it, object to processing, or ask us to delete it, subject to any information we are required to keep.

You may exercise these rights whether or not you have a MomentDrops account.

Where a request relates to information we cannot release without being sure who you are, we will ask you to verify your identity first. We ask for the least information necessary to do this.

How to make a request

Signed-in customers can submit a request from Account → Privacy.

Anyone else, including wedding guests, can submit a request at /privacy/request or by emailing Not yet configured — contact us for these details..

Requests involving a specific photo or video are reviewed by a person. We will not confirm the existence or contents of private wedding media to someone whose identity and connection to that media has not been established.

Information Officer

Information Officer: Not yet configured — contact us for these details..

Complaints

If you are not satisfied with how we have handled your personal information, you may lodge a complaint with the Information Regulator of South Africa.

Information Regulator (South Africa) — enquiries: inforeg@justice.gov.za; complaints: POPIAComplaints@inforegulator.org.za.

Cookies and similar technology

We use first-party cookies for essential session functionality and limited service-performance measurement, including the short-lived operational cookie described below. We do not use advertising cookies or third-party analytics trackers.

• Supabase auth session

  Keeps a signed-in customer signed in and refreshes their session token.

  Strictly necessary · Browser local storage (first party)

• md_guest_session

  Identifies a guest's upload session for one event. Opaque secret; stored server-side as a hash only.

  Strictly necessary · HttpOnly cookie, Secure, SameSite=Lax, 12 hours

• md_view_…

  Measures guest upload-page opens for one wedding without identifying the guest. Contents: a random value only.

  First-party operational cookie · HttpOnly cookie, Secure in production, SameSite=Lax, 12 hours