Scrapbooking plugin privacy

The photo upload that hands a stranger forty years of your family's faces, names, and dates

A custom-scrapbook order can look like a craft project and a shipping address. It is also a form that asks for photo uploads spanning decades, the names and relationships behind each face, wedding and birth dates, and — for the memorial package — who died and when. A craft order built to celebrate a family quietly assembles the best-labeled facial-recognition training set that family will ever produce, held in an uploads folder with guessable URLs. Photo-upload, face-name, relationship, wedding-date, birth-date, memorial-who-died, and memorial-when fields are configured, not documented defaults. Optional family albums go in the site uploads folder. An order is not proof those people exist or consented. A face-name answer is a stored note, not a verified identity. A page request is not proof anyone ordered a scrapbook. The page URL can say scrapbooking even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and albums, whether uploads URLs are guessable, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a facial-recognition claim, a biometric-law claim, a defamation claim, or a GDPR or other compliance assessment.

Scan your site for third-party requests

The scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded files, gallery albums, email inboxes, staff permissions, vendor accounts, or backups.

Where scrapbook orders, photo uploads, and albums go

Order forms, uploads, and galleries handled on your WordPress site

Check which photo-upload, face-name, relationship, wedding-date, birth-date, memorial-who-died, or memorial-when fields you enable, who can open form entries and albums, where uploaded family photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after an order that never became a book. Notification emails can also copy the same face labels and file links off-site. One table can name every face, every wedding date, and who died next to a shipping address, even when the book is never printed. Ask your web vendor not to collect memorial-who-died next to decades of labeled faces on the first public form, not to store birth dates next to contact details in one open submissions list, and to purge unused photo batches after the order date. A privacy-policy page does not by itself limit who can export an order list. A stored order is not proof those people consented.

Albums or tags handled by a vendor

Some gallery or marketing tools load a vendor script or sync albums to a vendor host. That path can re-expose the same labeled faces. Review which gallery connectors and tags you enable, account access, and retention there. Keep memorial and family-album pages off vendor sync if you do not want that copy. A browser scan cannot inspect stored face labels, wedding dates, or memorial-who-died answers. A "family keepsake" badge is not a verified storage path.

Scrapbooking order, photo-upload, and gallery setups

No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.

Three plugins reviewed from public documentation. Specialty scrapbook design SaaS without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Forminator Forms – Contact Form, Payment Form & Custom Form Builder

Documented self-hosted form builder (plugin version 1.58.1). The listing states Forminator stores and organizes submissions so you can sort, analyze, and manage responses, and includes a free file-upload field with multi-file support. Version 1.58.1 helper-fields.php forminator_upload_root() writes under the WordPress uploads directory plus /forminator/, with per-form hashed subfolders from forminator_get_upload_path(). upload.php stores files through that path. Photo-upload, face-name, relationship, wedding-date, birth-date, memorial-who-died, or memorial-when questions are fields you add; they are not documented defaults. A family photo album is a set of files you accept; that file type is not a documented default. An order is not proof those people exist or consented. A face-name answer is a stored note, not a verified identity. A cancelled memorial scrapbook still leaves the who-died field and labeled faces in the submissions list. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long an order row sits after a request that never became a book is not a documented default of the plugin.

Scrapbook order form entries stored in WordPress; photo uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
Iptanus File Upload

Documented frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. A decades-spanning family photo set is a batch of files you accept; that file type is not a documented default. An uploaded face is a file, not proof the person consented to be labeled. Deleting a form entry later does not by itself prove the photos were removed from the uploads path or from a cloud destination you enabled. Guessable uploads URLs can expose those faces without a login. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot.

Family photo uploads stored under the site wp-content pathBrowser hosts not verifiedNot assessedNot tested
  • None
NextGEN Gallery

Documented gallery plugin when it serves photos from your WordPress install. On resize it copies camera metadata from the original onto the generated file. The listing does not document stripping GPS from the original upload. A scrapbook proof gallery or workshop album is a gallery you create; album titles and captions that name faces, weddings, or memorials are labels you configure. Neither is a documented default. A gallery page request is not proof anyone ordered a scrapbook. The page URL can say scrapbooking even when no form is submitted. Social-feed galleries are not this row. Consent timing is not tested here. Review who can open albums, whether captions label faces next to dates, and how long originals and resized copies stay reachable.

Photo albums served from your WordPress install, including camera metadata on resized filesBrowser hosts not verifiedNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Photo-upload, face-name, relationship, wedding-date, birth-date, memorial-who-died, or memorial-when fields often depend on the fields you configure. A scrapbook order is not proof those people exist or consented. A face-name label is a stored note, not a verified identity. A gallery page request is not proof anyone ordered a scrapbook. The page URL can say scrapbooking even when no form is submitted. The labeled faces and memorial dates can sit after the book is never printed. This page is about a craft order that labels decades of family faces, not a gallery display page alone, not a ghostwriting told-life-story intake, not a pet-cremation memorial-grief transaction, and not a guestbook condolence entry. Ask your web vendor who can open entries and albums, whether uploads URLs are guessable, whether EXIF GPS stays on resized files, and how long records and backups are kept. A "family keepsake" badge is not a verified storage path. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess facial recognition, biometric law, or defamation. Review stored records, uploaded files, albums, connected services, exports, notification emails, and backups.

Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-scrapbooking-plugin-privacy