DRAFT — pending attorney review. Not in effect.

WeddingRecaps Privacy Policy (DRAFT)

DRAFT for attorney review. Not legal advice. Prepared 2026-10-18 for WeddingRecaps (operated by Lipa Honig as an individual, doing business as WeddingRecaps; no LLC is formed). Placeholders are in [brackets]. Items marked DECISION need Lipa or the CEO. No mailing address is included on purpose; a business contact address gets added by counsel if required (an assumed-name/DBA filing may also be needed in New York).

Effective date: [date] · Contact: hello@weddingrecaps.com (planned; not yet active)

1. Who we are

WeddingRecaps ("we", "us") is operated by Lipa Honig, an individual doing business as WeddingRecaps. We help couples collect photos and videos from their wedding guests through a private, per-wedding upload link and QR code. We turn that footage into edited reels.

2. The short version

3. Information we collect

| From | What | Why |

|---|---|---|

| Guests | The photos and videos you upload, including embedded metadata such as the time, device and possibly **location (EXIF/GPS)** | To make reels for you and the couple. **DECISION:** strip location data on upload, or keep it |

| Everyone | Basic usage events: page views, QR scans, uploads, reel plays, and clicks on "get yours" | To run and improve the service and show couples how their QR code was used. We store a one-way hashed visitor identifier that changes daily, **not your raw IP address** |

| People who get our emails | Whether an email was delivered, opened or clicked, recorded by our email service provider | To make sure emails arrive, measure what's useful and stop emailing people who aren't reading |

| People who share a referral link | Your link/code and whether someone booked through it | To give referral rewards. We don't tell you who booked unless they agree |

| Couples | Your names, email, wedding date and billing details | To provide the service. Card payments are processed by our payment provider [Stripe]; we don't store card numbers |

We don't use face recognition or create biometric identifiers. DECISION: if editing tools ever use face detection or recognition, this section, the consent text and the retention schedule must change first (Illinois BIPA, Texas, Washington and others).

Guest contact fields and how each is used

| Field (guest upload form) | Required? | Used for delivery/service | Used for marketing |

|---|---|---|---|

| Email | **Required** | Sending your reel and messages about it | Only if you tick the separate, unticked "email me news and offers" box |

| Mobile phone (stored in E.164 format, e.g. +12125550123) | **Required** | Texting or calling you about delivering your reel (transactional only) | Only if you tick the separate, unticked SMS marketing box (see SMS terms) |

| Name | Optional | Shown to the couple with your uploads; searchable in their private gallery | Not used |

| Mailing address (line 1, line 2, city, state/region, postal code, country) | Optional | **DECISION:** only for physical delivery or keepsakes, if offered | Only if you opted in to marketing, and only for mail from WeddingRecaps. **DECISION (Lipa) — P4:** if region-tailored marketing emails are wanted, add: "your city, state or postal code may be used to choose which marketing emails are relevant to you (e.g., regional offers)." |

| X handle, Instagram handle | Optional | So we can tag or credit you if you ask, or recognize you in support requests | Not used for advertising targeting; never posted without your permission |

| Upload consent (time and text version) | **Required** | Proof of your permission to use your uploads | — |

| Email/SMS marketing opt-ins (yes/no, time, text version) | Optional, **unticked by default** | — | Proof of your marketing consent; recorded only if you tick the box |

| Hashed network identifier | Automatic | Abuse prevention and rate limiting; not your raw IP address | Not used |

Contact details are stored separately for each wedding. They are never shown to other guests, never sent back to your browser after you submit, and not shown to the couple (DECISION: confirm). We don't sell them. If you opt out of marketing, we apply that to every wedding where you used the same email or number.

SMS terms (WeddingRecaps text messages)

Opting out and deleting your contact details

4. How we use information

We use it to provide the service: storing uploads, editing reels, delivering reels by email and text, running the couple's gallery, preventing abuse (rate limiting and security), keeping records of consent, and following the law. We use sample or stock content, not guest uploads, in our own marketing unless we get separate written permission. We never use images of children in marketing.

Marketing. If you book WeddingRecaps or sign up on our website, we may email you planning tips, optional extras, review and referral requests and anniversary notes. Guests get marketing emails or texts only if they ticked the separate opt-in box. Every marketing email has an unsubscribe link and a preferences page where you can opt out of some or all marketing.

DECISION (Lipa) — P11: whether emails to guests who opted in may mention the couple whose wedding they attended (first names only, unless the couple opts out in their dashboard). Until decided, guest marketing doesn't mention couples.

5. Who sees or receives it

We don't sell personal information or share it for cross-context behavioral advertising.

6. Retention

| Data | Kept for |

|---|---|

| Raw guest uploads | 90 days after the wedding, then deleted (**DECISION**) |

| Edited reels and films | [12 months] after delivery (**DECISION**; longer storage may be offered). **DECISION (Lipa) — P8:** 12 months ends right around the first anniversary, when anniversary emails would go out. Options: extend to [13 months], or keep 12 and email the couple at least [30] days before deletion so they can download. Retention unchanged until decided |

| Guest contact details (email, phone, name, address, handles) and consent/opt-in records | As long as the related upload or reel exists; the consent record may be kept up to [3 years] as proof of permission (**DECISION**, ask counsel) |

| Marketing contacts (guests who opted in): email, first name, wedding/couple name and opt-in record | Until you unsubscribe or the related reel is deleted, whichever comes first [or: until you unsubscribe, or [N] months without opening our emails] (**DECISION, Lipa**) |

| Couple account and contact details | [N years] after the wedding, for service, records and (if you haven't unsubscribed) anniversary emails (**DECISION, Lipa**) |

| Usage events | [24 months], with no raw IP addresses |

| Backups | Purged within [30] days after deletion |

7. Your choices and rights

8. Children

WeddingRecaps isn't directed to children under 13, and we don't knowingly collect personal information from them. Guests who upload must be [18 or older, or 13 or older with a parent's permission] (DECISION; also check GDPR's age 16). Minors may appear in wedding footage. The couple and the uploading guest are responsible for having permission from parents or guardians. Contact us to remove footage of a child.

9. Security

Uploads go over HTTPS to private storage separated by wedding. There are no public links to raw media, upload links are single-use and write-only, and access is limited and logged. No system is perfectly secure; we'll notify affected people as the law requires if a breach happens (including under New York's SHIELD Act).

10. International users

We're based in the United States and store data with US-based providers (possibly in other regions through their networks). DECISION/counsel: decide whether to serve EU and UK guests and add GDPR terms.

11. Changes

We'll post updates here with a new effective date, and give notice of material changes.

12. Contact

hello@weddingrecaps.com

Questions: hello@weddingrecaps.com