Plain-language product privacy
Local by default, portable by explicit export.
Supported project files are processed in the browser. The product vendor does not receive project inputs, previews, comments, or response files through the application.
What stays on the device
- Imported source files during the active intake session.
- Generated image and PDF-page previews.
- Project metadata, generated package records and manifest snapshots, reviewer labels, creator resolutions, revision tasks, and reconciliation state.
- Imported response contents.
- Best-effort recipient draft state where browser storage permits it. Reader keys this convenience copy to the exact distribution and manifest digest and validates it before restore.
The creator app uses product-specific browser storage. It does not maintain a local event log. The original source is not modified. Previews are re-encoded without copying EXIF, IPTC, or XMP metadata.
Network behavior
The static hosted site naturally receives ordinary page and bundled-asset requests from the browser and hosting provider. Project editing has no account or cloud database. This site counts page visits through Cloudflare: it sets no cookie, it cannot follow you from here to another site, and nothing from your work is part of the count. Optional billing loads RevenueCat code and Stripe payment fields; these provider requests do not contain review projects, previews or client responses. Offline reopening works only after the application shell and bundled support assets have loaded and cached successfully over HTTPS or localhost. A first visit, cache miss, or evicted cache still requires the site.
The product cannot describe or control the logging performed by the chosen static host, merchant checkout, email provider, or file-transfer service. Review their policies separately.
What leaves through an explicit export
Selected source bytes and local project records are not uploaded by this application. When a creator or recipient explicitly downloads or shares an artifact, the browser or operating system sends those generated bytes to the chosen save or share destination. Any later email, drive, portal, or other transfer is outside this application; the product vendor does not receive the artifact through the app.
- Review package
- Contains generated previews, project instructions, review rules, and package identifiers. It may be forwarded, copied, or screenshotted.
- Response file
- Contains decisions, favorites, comments, normalized regions, project identifiers, an optional self-entered reviewer name, and device-provided times.
- Project archive
- Contains the project model, generated derivatives, package records, imported responses, creator resolutions, revision tasks, and checksums needed for backup and restore.
- Reports
- May contain recorded filenames, reviewer labels, decisions, comments, creator resolutions, revision tasks, and local timestamps. The project activity snapshot contains no local event log.
Browser storage is not a backup
Browser data may be cleared manually, evicted under storage pressure, removed by private-browsing behavior, or lost when a site origin changes. Export a .reviewproject after meaningful work. Recipient local-file storage can vary, so recipients should download drafts explicitly.
Project storage, packages, responses, and reports are not encrypted by this product. Use storage and transfer controls appropriate to the project.
Cleanup and deletion
The storage tool inspects exact unused preview candidates before deletion and fails closed when persistent removal cannot be confirmed. Project deletion removes records the browser exposes to this application. Neither action is secure deletion or a guarantee against recovery from device backups, browser internals, recipient copies, exported files, or forensic tools.
Purchases are external
The planned one-time digital checkout is operated by a third-party merchant. Order, payment, tax, invoice, refund, and download data are handled outside this application under that merchant's terms. The final merchant and seller identity are owner-supplied launch inputs and must be disclosed before sales begin.
Privacy questions
Contact socialreminderinfo@gmail.com. Do not email confidential project files unless that channel has been agreed for the project.
Optional billing
RevenueCat receives a browser-generated billing identifier for access checks. RevenueCat and Stripe handle payment and receipt details. Review projects and responses remain local. Full project backups are available without a purchase.
Website hosting and Premium
Replyleaf is provided by Replyleaf, Ontario, Canada. Cloudflare serves ordinary page and asset requests, including connection information such as IP addresses and browser headers. Project content is processed locally. Premium and restore operations send the app-generated customer identifier or saved access code to RevenueCat; checkout sends the required purchase and payment information to the payment processor. No project files are sent for entitlement checks. Contact socialreminderinfo@gmail.com about privacy; do not email confidential projects or card details.