Wix publishes its own privacy policy, and it covers Wix Inc. as a company: what it does with your account and billing data as a site owner. It does not cover what your specific site collects from the people who visit it, because Wix has no way to know which forms you've built, whether you've turned on Bookings or Stores, or which apps you've installed from the App Market. That's a document only you can write, and it needs to match your actual setup rather than a generic template.
Here's how to build one that actually reflects what a Wix site collects: Ascend and Automations contact-form storage, Wix Bookings and Wix Stores checkout data, and the App Market's third-party app permissions.
Ascend and Automations quietly become a CRM
Every contact form on a Wix site, whether it's a simple Contact block or a multi-field form built with Wix Forms, feeds into Wix's built-in contact list (visible under Contacts in your site dashboard). If you're on a Wix Ascend plan, that same data also flows into Ascend's marketing and automation tools: email campaigns, automated follow-up sequences, and lead-scoring features that treat every form submission as a new contact record rather than a one-time message.
This matters for a privacy policy because it changes what you're actually doing with the data. A form that just forwards a message to your inbox is a narrow, one-time use. The same form feeding into Ascend Automations means that submission can trigger an automated email sequence, get tagged, and sit in a contact database indefinitely, a materially different use that needs its own line in your policy rather than being folded into "we use your information to respond to inquiries."
Wix Automations (the workflow tool available even outside Ascend) works the same way structurally: if you've built an automation that reacts to a form submission, a cart abandonment, or a new site member by sending an email or updating a contact tag, that's a form of automated processing worth naming, not just the initial data collection.
Wix Bookings and Wix Stores collect different data
Wix Bookings and Wix Stores are separate apps within the Wix ecosystem, and they collect distinct data sets that a single generic sentence like "we collect information you provide" doesn't adequately describe.
Wix Bookings, used for appointment scheduling and class sign-ups, collects a client's name, email, phone number, and whatever intake or booking-form fields you've added, plus a booking history tied to their client profile. If your booking flow asks for anything sensitive, health details for a wellness or medical-adjacent business, for instance, that's a specific data type worth naming rather than leaving implicit inside a general "booking information" line.
Wix Stores, the ecommerce app, collects a fuller checkout data set once someone buys something: shipping and billing address, phone number, order history, and payment details processed through Wix Payments or a connected gateway such as Stripe or PayPal. Wix itself does not store full card numbers; the payment processor does, but your policy should still name whichever processor handles checkout, since that's the entity actually holding sensitive payment data.
What each Wix commerce app collects
| What it collects | Must be named | |
|---|---|---|
| Wix Bookings | Name, email, phone, intake answers | Bookings, plus sensitive fields |
| Wix Stores checkout | Address, phone, order, payment | Wix Payments or your connected gateway |
| Wix Ascend / Automations | Form submissions as contact records | The automated email or tagging use |
| App Market apps | Whatever its permissions allow | Each app by name, not as a group |
If you run both apps on the same site, say a service business that also sells retail products, both data sets need their own mention. Treating "checkout" as one undifferentiated category glosses over the fact that a booking client and a store customer may be entirely different people giving you different information for different reasons.
The App Market is the part most Wix privacy policies miss
The Wix App Market is where most third-party data collection on a Wix site actually happens, and it's the piece most site owners forget to audit before writing their policy. Chat widgets, review collection tools, upsell and cross-sell apps, popup builders, and analytics add-ons are all installed as separate apps, each with its own data practices and its own permission scope.
When you install a Wix app, it requests specific permissions (access to site visitors' contact info, order data, or site content, for example), which you can review at any point under Settings > Permissions & Roles or from the app's own settings page in your dashboard. Each app with meaningful data access is effectively a separate data processor, the same way a Squarespace or Shopify integration would be, and naming a handful of examples ("chat and review apps") is weaker than naming the specific apps actually installed, because a visitor or a regulator reading your policy has no way to check what "chat and review apps" actually means for their own data.
Before drafting this section, go through your installed apps list one by one, note what each one actually does and what data it touches, and write your policy around that specific list rather than a generic third-party disclosure that could describe any Wix site.
- We may use third-party apps for chat, reviews, and marketing.
- No names, no way for a visitor to check what's actually installed.
- Our live chat is powered by [App Name], which may collect your name and message content.
- Our review widget is [App Name], which collects your name, email, and submitted review text.
Wix's own analytics and session cookies
Separate from any app you've installed, Wix sets its own session cookies (including one commonly named svSession) to keep a visitor's session and shopping cart working across page loads, along with basic site analytics available through your dashboard's Analytics panel. This runs by default on a live Wix site, independent of whether you've added Google Analytics or Google Tag Manager through Wix's supported integrations. A policy that only mentions Google Analytics, because that's the only tracking tool the site owner consciously added, is missing Wix's own baseline analytics and session handling, which still needs a line of its own.
Where to publish and link it on Wix
Wix has a dedicated spot for this: from your site dashboard, go to Settings > Business Info, or search for "Privacy Policy" directly in the dashboard search bar, and Wix will let you add or link a Privacy Policy page that several templates surface automatically in the footer. If your footer doesn't show it automatically, add the link manually to your site's footer or navigation menu, since a policy that exists but isn't linked anywhere doesn't meet the disclosure requirement it's meant to satisfy.
If you're running Wix Stores, also confirm the checkout flow itself links to your policy. Most Wix checkout templates show a small legal-links row near the payment button once a Privacy Policy page is set in your dashboard, but it's worth checking after any template or checkout customization.
Get a Wix-accurate policy without starting from scratch
Auditing every form, app, and connected tool on a Wix site by hand is tedious, and it's easy to miss an app that was installed months ago and forgotten. Our Privacy Policy Generator builds a policy around your actual data sources, forms, bookings, store checkout, and installed apps, so the document you publish reflects your real Wix setup instead of a generic template that glosses over the App Market.
For the equivalent guide on another platform, see our Shopify privacy policy guide or Squarespace privacy policy guide, or read the anatomy of a compliant privacy policy for a section-by-section breakdown of what a finished policy should contain.
The information in this article is for informational purposes only and should not be construed as legal advice on any matter, and does not create a lawyer-client relationship.
