
Strict allowlists, path-safe default names, sensitive-key categories, accessor avoidance, exact counts, frozen output, and value-free removal evidence stay separate from real image inspection, EXIF stripping, authorization, storage, and privacy certification. This is the real published Genesis interface—not a stock image.
Genesis Code Store · GCD-OHR-429
Tour Photo Attachment Metadata Sanitizer
Produce a bounded share-safe projection of tour-photo attachment context while removing device, private-location, path, uploader-internal, unsafe, and unsupported metadata without echoing removed values.
An original zero-dependency metadata boundary for renter and staff tour-photo attachments. It validates opaque attachment and optional tour or property IDs, five image media types, byte size, dimensions, source, strict scalar allowlists, original-filename disclosure, sensitive-key categories, accessors, prototype-like keys, and hard field and string limits; then returns deeply frozen retained context, value-free removal evidence, exact counts, and explicit non-effect flags.
It helps an app decide whether a location is inside a chosen nearby area without doing the tracking for you.
Free ZIP download Verified ZIP · 15 files · JavaScript + TypeScript declarations + 124 tests + README + START-HERE
Free products remain subject to the written license included with the package. Free does not mean public-domain or unrestricted resale. Domain limits count websites, not individual page URLs.
Read license termsWhat it helps you do
- Strict retained-key allowlists with sensitive location, device, path, uploader-internal, and unsafe categories
- Path-safe generated filenames by default plus explicit original-name disclosure control
- Deeply frozen share projection, exact counts, value-free removal evidence, and no binary-processing claim
What this specific product actually does
Every Genesis listing has its own capabilities, workflow, automation status, limits, and proof standard—without generic promises copied from another product.
Inside Tour Photo Attachment Metadata Sanitizer
- 01Validates opaque attachment, tour, and property identifiers without accepting names, addresses, or exact geography.
- 02Accepts five explicit image media-type labels plus bounded byte size, width, height, and renter, staff, vendor, or unknown source.
- 03Retains only finite scalar values whose normalized keys appear in a strict allowlist; the default set is altText, caption, and orientation.
- 04Rejects sensitive keys from custom allowlists and removes device, private-location, path, uploader-internal, unsafe, accessor, and unsupported metadata without echoing values.
- 05Replaces original filenames with attachment plus the allowed extension by default and requires explicit opt-in before returning a sanitized basename.
- 06Returns a deeply frozen attachment projection, ordered removal evidence, category counts, and explicit proof that no file, EXIF, upload, delete, or privacy-certification operation occurred.
Share-safe attachment context without pretending metadata projection sanitizes image bytes.
The sanitizer transforms supplied facts only; the host owns binary inspection, EXIF removal, authorization, storage, sharing, privacy review, monitoring, incident response, and rollback.
This product does not modify a customer website.
Who this is built for
- 01Rental applications sharing renter or staff tour-photo attachment context across bounded internal workflows
- 02Floot and React teams separating metadata projection from a reviewed binary image-processing worker
- 03Privacy and security reviews that need deterministic value-free removal evidence without logging sensitive metadata
How you receive it
GCD-OHR-429
Verified ZIP · 15 files · JavaScript + TypeScript declarations + 124 tests + README + START-HERE
All Platforms, Floot, React / Next.js
Free
This listing is a downloadable Genesis code package. The ZIP includes reusable code and START-HERE directions.
Three steps for this product
- 01
Authorize and inspect outside the helper
Authenticate the actor, authorize the exact property, tour, and attachment, enforce upload limits, and verify and decode the image bytes in a reviewed worker.
- 02
Project only required context
Build trusted attachment facts, use the smallest reviewed metadata allowlist, keep original-name disclosure disabled unless required, and stop on every validation error.
- 03
Strip, stage, and verify the real file
Re-encode or otherwise remove binary metadata, scan and store under host policy, test representative files, use Floot Update/Publish, and verify production access and rollback.
Before & After Repair Report
Tour Photo Attachment Metadata Sanitizer · GCD-OHR-429
Report format preview. Scores and status values populate only from measurements produced by an actual run. Genesis does not invent improvements.
What Genesis Code Doctor fixed
- Only verified changes appear here.
- Each repair can show affected files, routes, checks, or rules.
- Regression checks are recorded separately from the repair itself.
Still needs attention
- Unresolved, blocked, unavailable, or not-tested items remain visible.
- Evidence links can explain why an item passed, failed, or needs review.
- Follow-up verification can be run after implementation.
Know the fit, evidence, and handoff before a repair is used.
These controls turn a code product into a traceable repair workflow. They do not claim compatibility or success that has not been verified.
Declared support is available
Declared platforms: All Platforms, Floot, React / Next.js
Exact compatibility still depends on the customer's framework version, dependencies, hosting, custom code, and current site state.
Lifecycle protection is part of the product standard.
- Compatibility is reviewed before release.
- Regression and rollback requirements stay explicit.
- Follow-up verification can be run after implementation.
Genesis keeps the recommendation tied to evidence.
- Confirm the observed problem.
- Check product fit and safety boundary.
- Apply only the authorized repair scope.
- Re-run equivalent checks before calling it fixed.
Generate a clean technical handoff in one click.
The handoff includes product identity, declared compatibility, delivery method, capabilities, safety boundary, and the verification sequence.
What this item does not claim
This sanitizer evaluates caller-supplied attachment facts only. It does not read image bytes, parse EXIF, verify a file or MIME type, decode or transcode an image, strip metadata from the actual binary, scan malware, authenticate or authorize a user, upload, store, delete, share, or certify privacy. The host owns trusted binary inspection, re-encoding, authorization, retention, access control, monitoring, incident response, and rollback.
Simple delivery when verified code is released
Free code uses Free Download. Paid code uses Add to Cart. Every released package includes a verified ZIP, README, license notice, and START-HERE directions.
Copyright © Connect Point ISP LLC. Genesis Code Doctor™. All rights reserved. Purchase or download does not transfer ownership. Except where a product expressly provides a different written license, Genesis packages may not be resold, redistributed, sublicensed, repackaged for sale, or published as a competing download.