Effective September 2026

Privacy, with
clear boundaries.

What we collect

We collect store URLs, names, email addresses, scope answers, project onboarding information, and correspondence you submit. The preview service reads public store pages and representative public product data. It does not sign into the source store or request customer lists to generate a preview.

Why we use it

We use this information to generate concepts, respond to requests, evaluate scope, verify purchases, fulfill migrations, provide support, and improve the service. Form consent covers contact about your preview or project; it is not an automatic opt-in to unrelated marketing.

Storage and service providers

Site records and preview images are stored using Cloudflare infrastructure through Sites hosting. Stripe handles checkout and card details. We retain payment identifiers and confirmation details, not card numbers. Source pages are requested from public merchant websites. Preview images are served through our controlled server path rather than loading arbitrary source URLs in your browser.

Private previews and sessions

Concept URLs are unlisted, contain an unguessable token, expire after seven days, and are marked not to be indexed. Full access also requires an unlocked browser session. A necessary, secure, HttpOnly session cookie keeps your preview and onboarding access in the same browser for up to 30 days. Avoid sharing access links. Contact us for operator-verified recovery on a new device.

Measurement

We store first-party events such as URL submissions, preview completion, unlocks, package selections, checkout starts, and verified purchases. Event records do not contain form contents or secret access links. We use a hashed network identifier for request limits rather than storing raw IP addresses in our application records. No session replay is added to private previews or onboarding.

Access and credentials

Merchant implementation access is separate from the public preview service. We sequence named-user invitations and permissions after scope review. Do not enter passwords, API secrets, payment-card data, or customer export files in contact or onboarding forms. Internal project records are restricted to approved operators.

Retention and deletion

Preview access expires after seven days. Associated lead and project records may remain for follow-up, delivery, support, dispute handling, and legitimate recordkeeping. You can request deletion of a preview, nonessential lead information, or unnecessary access through our contact form. We verify identity before deleting or releasing private information. Payment and project records may need to be retained for applicable recordkeeping obligations.

Your requests

Use Contact Sites to ask for access, correction, deletion, withdrawal of contact permission, or an explanation of how your data is used. Include the email used for the request; never include passwords or full payment-card details.