Prepared November 3, 2026. Supplied seller/contact details are included, but final policies, support commitments, and live-launch approval remain incomplete. No effective date is assigned. Live purchasing is unavailable.
1. Draft status and responsible seller
Seller details supplied by the owner: MMP Marketing Online, Australia. Customer support: mmpmarketingonline@gmail.com.
For privacy questions, contact the supplied customer-support email. The responsible legal entity, privacy-request handling process, applicable obligations, and effective date still require confirmation. This notice is not ready to serve as the final privacy disclosure for public sales. It describes the current application and flags the decisions still needed.
2. Checkout and fulfillment records
When checkout is opened, the application creates an order containing an internal order reference, product identifier, price and currency, status, timestamps, a delivery token, and the associated Stripe Checkout Session identifier. A verified completion event may add the Stripe customer identifier, checkout email, and customer name. Processed webhook event IDs, event types, and timestamps are stored for duplicate-event handling.
These records support fulfillment and purchase-status checks. Stripe collects payment details on its hosted checkout. The application does not store card numbers, security codes, expiry dates, Stripe secret keys, or raw webhook payloads as order records.
3. Browser storage and private access links
The application uses localStorage under the key ai-lead-gen-order-sessions to remember up to 20 returned Checkout Session references in that browser. This enables local order history; it does not create an account or automatically recover access on another device.
Treat an order-status address as a private access link: a person who possesses a fulfilled order’s session reference can request its download. It may appear in browser history and infrastructure logs. A time-limited archive link can also be forwarded during its validity. Avoid sharing either link publicly.
Clearing local browser data removes the local history list, not the purchase or webhook records in the managed database.
4. Service providers and hosting
Stripe processes checkout and payment data. Manus-managed hosting, database, and object-storage services support the website, orders, and delivery. The stylesheet requests fonts from Google Fonts, which involves a browser connection to that provider. Infrastructure providers may process connection details and operational logs.
The managed project configuration reports analytics enabled. The seller must verify the platform’s actual analytics events, identifiers, storage, provider terms, and any required consent configuration before launch. This draft does not claim the site is cookie-free, that analytics are anonymous, or that consent requirements have already been satisfied.
5. Uses and marketing boundaries
The implemented purchase flow uses information for checkout, verified delivery, order lookup, and duplicate-event handling. No newsletter opt-in or launch-email subscription is implemented in this checkout flow. A purchase must not be treated as blanket permission for unrelated marketing. Any future mailing integration needs its own appropriate notice and permissions.
6. Retention, requests, and international processing
No automatic order-deletion schedule is currently implemented. Before sales, the seller must choose documented retention periods based on operational needs and applicable obligations, specify deletion and access-request handling, identify the relevant service-provider arrangements and processing locations, and assess any cross-border safeguards.
Rights and obligations vary by location. The supplied support email is mmpmarketingonline@gmail.com; the seller must still confirm a functioning privacy-request process before inviting real customer data. Do not send identity documents, card details, passwords, or consumer-lead data through an unverified channel.
7. Safeguards and review
The implementation verifies Stripe webhook signatures and checks stored fulfillment state before requesting an expiring archive URL. Server credentials are not included in frontend code. These controls do not eliminate all security risks or constitute a security certification.
Owner review is still required for staff access, logging, retention, incident response, service-provider terms, and any jurisdiction-specific disclosures. A qualified privacy adviser should review the final notice where appropriate.