Your store data.

Hopper uses your account email to sign you in, and your connected Wix and Shiprocket accounts to carry out the shipping actions you approve. Shipping screens and PDFs need order information, including customer delivery details.

Reusable integration credentials are encrypted before database storage. They are used on the server, and are not returned to the browser after saving. Disconnecting removes the stored credential. Your workspace remains bound to its original store to keep historical records separate.

Hopper stores account details, connection identifiers, courier settings, order-sync and shipping progress and outcomes, payment access records, and requests you send us. Operational records support recovery after interrupted requests. Contact corrections for an approved sync batch are stored while it is queued or running and removed from its run payload when it reaches a terminal state. Selected order and delivery details are sent to your connected Shiprocket account to create the orders you approve. Generated order PDFs are produced on demand rather than saved as customer snapshots.

The beta uses Render for hosting and Supabase for account and database services. Sign-in email is delivered through the configured email provider. Payment details are entered with the payment provider when paid access is enabled.

Any configured usage analytics are restricted to selected activity names and counts. Credentials and buyer details are excluded. Browser session recording is not enabled.

To request an account/data deletion or ask about these practices, use the contact form. Backups and unresolved operations may need separate review before all copies can be removed. This notice must be kept up to date as the beta changes.