01 / Current status
The tool does not currently have an active authorized connection to Google Drive. The permissions and processing described below are planned, not live data handling.
This website has no analytics, forms, tracking pixels, advertising cookies, third-party fonts, login, or external scripts. It does not connect to Google Drive. Contact links open your email application if you choose to use them. This website is hosted on Cloudflare Pages. Cloudflare processes basic connection and security information to deliver and protect the website.
02 / Data & permissions
The proposed tool would read inventory photos and associated file metadata from the owner's Google Drive for internal inventory processing. Its planned Google Drive access uses:
drive.readonly
Read access to all Drive files the authorized account can access. The intended processing is limited to inventory files, but this intended limit does not narrow the permission granted by Google.
drive.file
Access to app-created files and files explicitly selected for the app. This is intended to support separate processed copies; it is not general write access to every Drive file.
These are proposed app permissions; processing is not active.
03 / Proposed data handling
The proposed tool would process inventory photos and associated metadata on owner-controlled systems, creating separate processed copies while preserving source originals. Necessary inventory records and photos would be retained for provenance and sales history, including sold or gifted items. Periodic review would target unnecessary duplicates rather than automatically delete inventory history.
Temporary working files and sanitized logs would have limited retention. Logs would exclude photos, file contents, access secrets, and private system details. Tool backups would use encryption and limited rolling retention; records deliberately deleted would be re-excluded during restoration. These are proposed controls and have not been verified as implemented.
Deletion would be deliberate and documented, covering processed Drive outputs, local copies, and backups as applicable. Source originals would not be deleted without an explicit request. Revoking Google access is separate from requesting deletion and would not by itself delete copies already created. The technical deletion process and backup limits remain subject to verification before processing begins.
External AI and photo research would remain off initially. Generic public product searches could be used, but private photos and Drive-derived data would not be sent to an external research provider until the vendor, data, purpose, retention, and training terms are approved and accurately disclosed.
Proposed Google-data use limits: Google data would not be sold, used for advertising, or used to train general-purpose AI models. These are proposed use limits; no verified compliance or certification is asserted.
04 / Questions & requests
Send privacy questions or deletion requests to info-h5g4@e.wear-rewear.com. Rewear Enterprises will use proportionate identity checks when necessary and document how requests are handled. This notice does not promise a fixed response time; applicable legal obligations still apply.