Privacy notice
How the application handles accounts, connected stores, saved designs and the separate public demo.
Accounts and verification
When accounts are enabled, WhopBridge stores your name, email, verification status, password hash and server-side session records. Email verification and sign-in codes are delivered through the configured email provider and stored as hashes with expiry and attempt limits. Authorized platform administrators can view workspace information and suspend or restore access; those administrative actions are logged.
Information saved in your browser
The preview saves selected templates, branding, layout blocks, store-address drafts and pixel-ID drafts in localStorage. Use Settings → Reset preview to clear the workspace preferences. The editor has a separate saved draft for each template; delete that draft from the editor or clear this site’s browser storage to remove it.
Checkout preview fields
Contact and address fields in a checkout preview are not submitted to an order API or saved by this application. The payment area is a placeholder; this preview collects no card number or payment credentials. Use example details while exploring it.
Credentials
Protected connection forms accept merchant app credentials only after authenticated email verification and sign-in. Credentials are encrypted per workspace and store before database storage. The encryption key stays in server configuration. Credentials are never returned by workspace or admin APIs or stored in browser preferences. Do not put secrets in design content or imported files.
Requests and images
Serving the app can produce technical request logs in its hosting environment. If you add a third-party image or follow an external policy/documentation link, that third party receives the normal network request and handles it under its own notice. External image requests use no-referrer where implemented.
Marketing tracking
Saving a pixel-ID draft does not install a pixel. This preview sends no app-generated marketing or purchase events. Live consent, pixel configuration and server-event delivery still require implementation.
Before a live launch
Publish the actual business contact, data-controller and processor roles, hosting/database providers and regions, retention/deletion schedule, access request process, transfer arrangements and any necessary data-processing agreement. These items are not represented as already configured here.