Skip to main content
Platform security guideReviewed

Wix security: apps, Velo code and who can reach your site's data

Wix hosts the site and runs the platform.

Many of the settings that decide what a visitor, a member or an installed app can reach are made by you and the people you give access to: collection permissions, member settings, form recipients, apps, custom code and any Velo code a developer added. Each statement about Wix below names the Wix page it comes from. The page comes with an access matrix you fill in from your own account, plus anonymous, member and owner checks run on a duplicate site with invented records.

Wix app and Velo access matrix

Keep a spreadsheet copy of this table for each site. Rows A1 to A14 are readings of your live site: open what the third column names, or ask the person it names, change nothing, and write down what the fourth column asks for.

How to use it

Rows B1 to B6 are anonymous, member and owner checks that act only on a duplicate site you made and cut off from live apps, automations and mailing lists first, with at most two test members, invented records carrying a marker, an inbox you control, no more than three attempts at any single check, a browser only and no load. Never write a secret, key, password or customer record into the matrix. Each entry in the second column comes from a Wix page this guide cites, read on 14 November 2026.

20 rows

Wix app and Velo access matrix

RowWhat Wix's pages sayWhere to look, or what to doWhat to write down
A1. Wix account sign-in2-step verification page: the methods you can enable include the Wix app, SMS, an authenticator app and email, a passkey can also be set up, and more than one method can be on; disabling all your verification methods leaves the account protected by its password alone; a device is remembered for 30 days by default; a code is asked for only at email-and-password sign-in, not social login. Account security tips page: where several people work on a site, consider adding them as collaborators rather than sharing a password.Your own Account Settings, under 2-step verification, where the 2-step verification page puts it. Ask each collaborator to read their own and tell you.Per person: which methods are on (names only), whether they sign in with a social login, and whether anyone shares a login. Never a code, recovery code or password.
A2. Owner, collaborators and rolesRoles overview: Roles and Permissions is reached from Settings in the site's dashboard; the owner role is reassigned only by transferring the site; Admin (Co-Owner) has full access to manage, edit and publish the site, including billing and inviting people. Velo collaborators page: a role with Edit Site permissions has full access to backend files and database collections. Terms of Use, section 1.4: activities by anyone other than you who gets into the account or site settings, Contributors included, are deemed to have occurred on your behalf; section 1.5: Wix considers the site's owner to be the person or entity whose email address its records list as owner of the account the site was created under.Roles and Permissions, from Settings in the site's dashboard (roles overview). Read each person's role and the summary under it.Per person: name, role as shown, whether it includes Edit Site, Secrets Manager access (A14) or CMS Admin, whether they still need it, and who holds the account email address the site was created under.
A3. Installed appsPermissions overview: an app's scopes are declared in its setup and granted by a Wix user at installation; when an app acts on behalf of a Wix user, its permissions are the intersection of its scopes and that user's role. Frontend security page, for sites on Studio Two, Wix Studio and the Wix Editor: each installed app receives its own scoped access token. App permissions page: for an app to be approved on the app market, it must request only the permissions necessary for its functionality. Accessing apps article: installed apps are under Manage Apps in the dashboard.Manage Apps in the site's dashboard (accessing apps article). For each app, find the permissions it was granted where you can; no Wix page used here names a screen for reviewing them after installation.App, developer, who installed it and when, permissions found (or "not found"), the data it handles in plain words, whether it is still used, and who decides on keeping it. Uninstall nothing during the review.
A4. API keys on the accountGenerate an API Key page: a key grants admin access to account and site data, is made in the API Keys Manager, and reaches all sites or selected sites; you can also assign a set of permissions that determine the types of APIs each key can access; give each key the narrowest set of sites it needs, store it securely and use it only in server-side code.Ask whoever made each key for its name, the sites it reaches and its permissions; keys are made in the API Keys Manager (Generate an API Key page). The pages cited here do not say whether that screen shows a key's value, so this row does not ask you to open it: open no key, and create, reveal or regenerate nothing. Record what the key's maker tells you, and mark anything they could not confirm.Key name, sites it reaches and permissions (as the key's maker tells you), the system that uses it and where that system stores it (by name), and whether it is still needed. Never the key.
A5. Custom code snippetsCustom code article, written for the Wix Editor: snippets are added from Settings, then Custom Code in the Development & integrations section, to all or chosen pages, in the head or body; Wix does not provide support for technical issues with third-party snippets; snippets are associated with a specific domain; under frontend security measures introduced in December 2025, some snippets that previously worked may be blocked until their provider updates them.Settings, then Custom Code in the Development & integrations section (custom code article). Read each snippet's name, pages and placement, and the hosts its code loads from.Snippet name, pages, placement, host it loads from or inline, whether it shares a page with a form or a member page, whether it carries a key (yes, no or unsure, and whose; the value is never written down), owner, still needed.
A6. Who can become a memberSignup settings article: "Who can be a site member?" in Signup & Login Security sets everyone or only people you approve; asking everyone who signs up to confirm their email is a toggle Wix recommends; reCAPTCHA can be added to signup and login. Velo security best practices: if members hold any collection permission, approving members automatically is the same as giving that permission to Anyone.Signup & Login Security in the site's dashboard (signup settings article). Read; do not save.Who can join, the email confirmation setting, reCAPTCHA on signup and login, and each collection in A8 that grants members any permission. Where approval is automatic, mark those collections.
A7. Member roles and restricted pagesMember roles article: roles are made in Site Member Access, and only regular pages set as Members only appear in a role's access list. Page permissions article: any site page can be limited to roles from its settings in the editor, and its Wix Editor steps go through Pages & Menu and the page's Settings to the Permissions tab. Velo collaborators page: a hidden page on a published site can still be reached by modifying the URL. Velo security best practices: page code on a members-only or password-protected page can be viewed by any visitor.Site Member Access in the dashboard (member roles article); Pages & Menu in the editor, then each page's Settings and Permissions tab (the page permissions article's Wix Editor steps). List the pages kept out of the menu as well.Per page: who can open it as set, roles involved, whether it is only hidden from the menu, what data it shows, and whether its page code holds anything sensitive (yes or no; see A12).
A8. CMS collections you createdChanging permissions article: settings are under CMS, the More Actions icon, then Permissions & privacy; "Everyone" lets any visitor access the collection through an API even if nothing shows it; encrypting a PII field does not control who can view it. Collection permissions overview: dataset settings affect what can be done on a page, but only collection permissions can actually limit what each role can do; admins keep full access. Velo security best practices: a create or read permission set to Anyone can be used by a malicious visitor even where no page uses the collection; a visitor's personal information can be stored in a collection provided only the Site member author can read, update or delete it.CMS in the dashboard, the More Actions icon next to each collection, then Permissions & privacy (changing permissions article). Read and close without saving.Per collection: what it holds in plain words, whether it holds personal information or secrets (yes or no), the option set (Show content, Collect content or Advanced), who can view, add, update and delete, whether any page uses it, and whether the encrypted field warning shows.
A9. Wix App collectionsApp collections page: collections from the Wix Apps added to a site appear in the CMS when Wix Data is enabled, their permissions cannot be changed, and View permissions in the CMS shows them; for the Stores/Products collection, anyone can read the content and no one can create, update or delete it; when using code to perform data operations, you can override collection permission restrictions.View permissions on each app collection in the CMS (app collections page).App collection, who can read it, and whether your own code reads it with suppressAuth or elevation (A11).
A10. Form notification recipientsForm notifications article: by default a submission emails the site owner, and the notification is built with Wix Automations; the automation can be edited to choose the owner or other collaborators and to add more email addresses; people who are not collaborators are added as contacts first. On PDF copies, its email notifications section says the automation can be edited to include PDF attachments of form submissions, and its FAQ says a PDF cannot be attached using Automations and that the option must be enabled directly in the form's settings. Roles overview: Customer Relations Manager can manage contacts, forms and automations, among other things, but cannot export contacts.Automations in the dashboard, then the automation that sends each form's notification email; in its Send an email action, read the Recipients field (form notifications article). Close without saving.Per form: the automation, each recipient (role, collaborator or contact, and whose inbox), whether a PDF copy of each submission is attached and where you found that setting (the automation or the form's settings), and anyone who should no longer receive it.
A11. Backend functions the frontend can callWeb modules article: .web.js functions are exposed through web methods set to Anyone, Site Member or Admin, as restrictive as possible; .jsw files are deprecated and keep working. Velo security best practices: anyone who knows an exported function's name can call it with any arguments; a function using suppressAuth must run its own checks or filter out sensitive data, or both. Elevation page: elevated code reachable from outside gives anyone who can call it elevated access.The backend files, in the Code panel in the editor, where the web modules article says web modules can be created. Read them with the developer who wrote them.Per exported function: file, name, permission as set, what it returns, whether it uses suppressAuth or elevation, the check it makes before that (named, or none), and whether any page calls it. Per file: whether a key or other secret is written into it (yes or no; never the value).
A12. Page, public and masterpage.js codeVelo security best practices: all page and public code is visible to any visitor, including page code on members-only and password-protected pages; never use API keys in page, public or masterpage.js code; do security checks in backend code, because any check in page, public or masterpage.js code can be read, manipulated and circumvented.Each page's code and the public files, read with the developer who wrote them.Per file: whether it holds a key, token, password, an email address used as a check or another secret (yes or no; never the value), and whether it decides access in the browser.
A13. HTTP functionsCustom site APIs article: HTTP functions expose site functionality externally to you or other people, and custom site APIs are only intended for server-to-server communications. HTTP function guide: they live in http-functions.js; its optional step says they expose the site's data and functionality to anyone who calls them and recommends authenticating the caller; one way it gives is retrieving a secret key from the authentication header, using the Secrets Manager.http-functions.js under Backend & Public, then Backend (HTTP function guide). Read the file with the developer; do not call the endpoints.Per function: method and name, what it reads or changes, the outside system that calls it and its owner, and whether it checks a caller secret (yes, no or unsure). Never the secret.
A14. Secrets ManagerSecrets Manager page: holds secrets by name, such as API keys, OAuth tokens and environment configuration settings; only site collaborators with the general role of Admin (Co-Owner) or Website Manager have access to it; a transfer moves secrets to the new owner and a duplicate does not get them. Secrets API page: use secret values only in backend code; never call List Secret Info from a .web.js file with anonymous permissions; deleting a secret, or changing its name or value, breaks all code using it.Ask the developer for the name of each secret the backend code retrieves, from the code read in A11 and A13; secrets are kept in the Secrets Manager section of the site's dashboard (Secrets API page). The pages cited here do not say whether that screen shows values, so this row does not ask you to open it: open no secret, and reveal, edit or delete no value.Secret name, the file and function that use it, the service it belongs to, who can open the Secrets Manager (from A2), and any key found in code instead (A12, A13). Never a value.
B1. Make the duplicate and cut its connectionsDuplicating article: changes to the copy do not affect the live site; Duplicate Site is under the Site Actions icon on the dashboard's Home; not copied are store orders and invoices, contacts and members, email campaigns and triggered emails, settings for third-party apps, Google Operations logs and Secrets Manager secrets, and hidden elements require enabling Velo in the new site; a Studio Editor site a Wix Professional or agency built cannot be duplicated from your account. Coded sites article: code and events are kept in the copy.Duplicate the live site and name the copy as a test. Check its collections for real records and treat any as live data. List every app, automation, mailing list, HTTP function caller and outside system the copy could reach, and disconnect each on the copy. Point every form automation on the copy at an inbox you control. Limits: a duplicate you made, with your business's domain not connected; change nothing on the live site; no test members, items or attempts until every connection is cut.Copy name, date, who made it, what it lacks compared with the live site, real records found, each connection and how it was cut, and the test marker (for example WIXTEST-1114).
B2. Publish the copy and create test membersCollection permissions overview: preview runs in the admin role; to act as a member or as everyone, publish the site and visit it signed in as a member or not signed in. Signup settings article: who can join and email confirmation are set in Signup & Login Security.Publish the copy with your business's domain not connected. Create two test members, Member A and Member B, once each through the copy's own signup form, with invented names carrying the marker and addresses at the inbox you control. If the copy admits only people you approve, approve these two. Give Member A the member role your restricted pages use; leave Member B without it. Limits: only after B1 has cut the copy off from live apps, automations and mailing lists; invented members only, with every email going to the inbox you control; the copy's own signup form in a browser, once per member, with no scripts and no load.The copy's address, publish date, the two test members (invented names only), roles given, and the emails the signups produced at your inbox.
B3. Anonymous check (signed out)Velo collaborators page: a hidden page can still be reached by modifying the URL. Velo security best practices: page code on members-only and password-protected pages can be viewed by any visitor. Changing permissions article: "Everyone" lets any visitor access a collection through an API, even if the content is not presented on the live site.In a private browser window, signed out, open each members-only, role-restricted and hidden page of the copy by its address, with the browser's developer tools open. At most three attempts per page. Send nothing the pages do not send themselves. Limits: only on the duplicate from B1, cut off from live apps, automations and mailing lists; a browser only, with no scripts and no load.Per page: what loaded (content, data, code files), whether a secret appeared (yes or no, never its value), and for each collection marked Everyone in A8, which fields the page received.
B4. Member check (Member A, then Member B)Velo security best practices: a visitor's personal information can be stored in a collection provided only the Site member author can read, update or delete it, and its member comments example sets Update and Delete to Site member author. Collection permissions overview: the Item's creator view setting lets members see only items they added.As Member A, add one invented item carrying the marker through each form or input on the copy that writes to a collection, and note any address the item gets. As Member B, open the lists and pages that show those collections, then Member A's item addresses, and the restricted pages. Where the site shows Member B an edit or delete control on Member A's item, use it once. Limits: only on the duplicate from B1, cut off from live apps, automations and mailing lists; the two invented members and their invented items only, with any email going to the inbox you control; at most three attempts per check; a browser only, with no scripts and no load.Per collection and page: what Member B could see, change or delete of Member A's item, and what a member without the role could open, written beside the result your A8 and A7 settings lead you to expect.
B5. Owner checkCollection permissions overview: admins keep full access to collections. Form notifications article: the notification email goes to the recipients set in the form's automation, the site owner by default.As the copy's owner, find each invented item in the CMS and read which fields were stored. Read which emails reached your inbox. Ask each recipient listed in A10 whether anything carrying the marker reached them. Limits: only on the duplicate from B1, cut off from live apps, automations and mailing lists; read only, in a browser, changing nothing in the CMS; no load.Where each test item landed and its stored fields, each email received (sender and subject), anything that reached an address outside your inbox, and the owner's decision on each difference from what A6 to A14 led you to expect.
B6. Clean-upDuplicating article: changes made to the copy do not affect the live site, and a copy can be transferred to another account. Terms of Use, section 2.2: you undertake to save and back up your site content regularly and independently.Remove the test items and test members from the copy, and ask the owner of any other system the marker reached to remove it there. Unpublishing or deleting the copy is the owner's decision. Limits: only on the duplicate from B1; remove only test members and items carrying the marker, never a real record; a browser only, with no scripts and no load.Each record carrying the marker, where it was, who removed it and when, and what happened to the copy and who decided.

Row

What Wix's pages say

  1. A1. Wix account sign-in
    What Wix's pages say
    2-step verification page: the methods you can enable include the Wix app, SMS, an authenticator app and email, a passkey can also be set up, and more than one method can be on; disabling all your verification methods leaves the account protected by its password alone; a device is remembered for 30 days by default; a code is asked for only at email-and-password sign-in, not social login. Account security tips page: where several people work on a site, consider adding them as collaborators rather than sharing a password.
    Where to look, or what to do
    Your own Account Settings, under 2-step verification, where the 2-step verification page puts it. Ask each collaborator to read their own and tell you.
    What to write down
    Per person: which methods are on (names only), whether they sign in with a social login, and whether anyone shares a login. Never a code, recovery code or password.
  2. A2. Owner, collaborators and roles
    What Wix's pages say
    Roles overview: Roles and Permissions is reached from Settings in the site's dashboard; the owner role is reassigned only by transferring the site; Admin (Co-Owner) has full access to manage, edit and publish the site, including billing and inviting people. Velo collaborators page: a role with Edit Site permissions has full access to backend files and database collections. Terms of Use, section 1.4: activities by anyone other than you who gets into the account or site settings, Contributors included, are deemed to have occurred on your behalf; section 1.5: Wix considers the site's owner to be the person or entity whose email address its records list as owner of the account the site was created under.
    Where to look, or what to do
    Roles and Permissions, from Settings in the site's dashboard (roles overview). Read each person's role and the summary under it.
    What to write down
    Per person: name, role as shown, whether it includes Edit Site, Secrets Manager access (A14) or CMS Admin, whether they still need it, and who holds the account email address the site was created under.
  3. A3. Installed apps
    What Wix's pages say
    Permissions overview: an app's scopes are declared in its setup and granted by a Wix user at installation; when an app acts on behalf of a Wix user, its permissions are the intersection of its scopes and that user's role. Frontend security page, for sites on Studio Two, Wix Studio and the Wix Editor: each installed app receives its own scoped access token. App permissions page: for an app to be approved on the app market, it must request only the permissions necessary for its functionality. Accessing apps article: installed apps are under Manage Apps in the dashboard.
    Where to look, or what to do
    Manage Apps in the site's dashboard (accessing apps article). For each app, find the permissions it was granted where you can; no Wix page used here names a screen for reviewing them after installation.
    What to write down
    App, developer, who installed it and when, permissions found (or "not found"), the data it handles in plain words, whether it is still used, and who decides on keeping it. Uninstall nothing during the review.
  4. A4. API keys on the account
    What Wix's pages say
    Generate an API Key page: a key grants admin access to account and site data, is made in the API Keys Manager, and reaches all sites or selected sites; you can also assign a set of permissions that determine the types of APIs each key can access; give each key the narrowest set of sites it needs, store it securely and use it only in server-side code.
    Where to look, or what to do
    Ask whoever made each key for its name, the sites it reaches and its permissions; keys are made in the API Keys Manager (Generate an API Key page). The pages cited here do not say whether that screen shows a key's value, so this row does not ask you to open it: open no key, and create, reveal or regenerate nothing. Record what the key's maker tells you, and mark anything they could not confirm.
    What to write down
    Key name, sites it reaches and permissions (as the key's maker tells you), the system that uses it and where that system stores it (by name), and whether it is still needed. Never the key.
  5. A5. Custom code snippets
    What Wix's pages say
    Custom code article, written for the Wix Editor: snippets are added from Settings, then Custom Code in the Development & integrations section, to all or chosen pages, in the head or body; Wix does not provide support for technical issues with third-party snippets; snippets are associated with a specific domain; under frontend security measures introduced in December 2025, some snippets that previously worked may be blocked until their provider updates them.
    Where to look, or what to do
    Settings, then Custom Code in the Development & integrations section (custom code article). Read each snippet's name, pages and placement, and the hosts its code loads from.
    What to write down
    Snippet name, pages, placement, host it loads from or inline, whether it shares a page with a form or a member page, whether it carries a key (yes, no or unsure, and whose; the value is never written down), owner, still needed.
  6. A6. Who can become a member
    What Wix's pages say
    Signup settings article: "Who can be a site member?" in Signup & Login Security sets everyone or only people you approve; asking everyone who signs up to confirm their email is a toggle Wix recommends; reCAPTCHA can be added to signup and login. Velo security best practices: if members hold any collection permission, approving members automatically is the same as giving that permission to Anyone.
    Where to look, or what to do
    Signup & Login Security in the site's dashboard (signup settings article). Read; do not save.
    What to write down
    Who can join, the email confirmation setting, reCAPTCHA on signup and login, and each collection in A8 that grants members any permission. Where approval is automatic, mark those collections.
  7. A7. Member roles and restricted pages
    What Wix's pages say
    Member roles article: roles are made in Site Member Access, and only regular pages set as Members only appear in a role's access list. Page permissions article: any site page can be limited to roles from its settings in the editor, and its Wix Editor steps go through Pages & Menu and the page's Settings to the Permissions tab. Velo collaborators page: a hidden page on a published site can still be reached by modifying the URL. Velo security best practices: page code on a members-only or password-protected page can be viewed by any visitor.
    Where to look, or what to do
    Site Member Access in the dashboard (member roles article); Pages & Menu in the editor, then each page's Settings and Permissions tab (the page permissions article's Wix Editor steps). List the pages kept out of the menu as well.
    What to write down
    Per page: who can open it as set, roles involved, whether it is only hidden from the menu, what data it shows, and whether its page code holds anything sensitive (yes or no; see A12).
  8. A8. CMS collections you created
    What Wix's pages say
    Changing permissions article: settings are under CMS, the More Actions icon, then Permissions & privacy; "Everyone" lets any visitor access the collection through an API even if nothing shows it; encrypting a PII field does not control who can view it. Collection permissions overview: dataset settings affect what can be done on a page, but only collection permissions can actually limit what each role can do; admins keep full access. Velo security best practices: a create or read permission set to Anyone can be used by a malicious visitor even where no page uses the collection; a visitor's personal information can be stored in a collection provided only the Site member author can read, update or delete it.
    Where to look, or what to do
    CMS in the dashboard, the More Actions icon next to each collection, then Permissions & privacy (changing permissions article). Read and close without saving.
    What to write down
    Per collection: what it holds in plain words, whether it holds personal information or secrets (yes or no), the option set (Show content, Collect content or Advanced), who can view, add, update and delete, whether any page uses it, and whether the encrypted field warning shows.
  9. A9. Wix App collections
    What Wix's pages say
    App collections page: collections from the Wix Apps added to a site appear in the CMS when Wix Data is enabled, their permissions cannot be changed, and View permissions in the CMS shows them; for the Stores/Products collection, anyone can read the content and no one can create, update or delete it; when using code to perform data operations, you can override collection permission restrictions.
    Where to look, or what to do
    View permissions on each app collection in the CMS (app collections page).
    What to write down
    App collection, who can read it, and whether your own code reads it with suppressAuth or elevation (A11).
  10. A10. Form notification recipients
    What Wix's pages say
    Form notifications article: by default a submission emails the site owner, and the notification is built with Wix Automations; the automation can be edited to choose the owner or other collaborators and to add more email addresses; people who are not collaborators are added as contacts first. On PDF copies, its email notifications section says the automation can be edited to include PDF attachments of form submissions, and its FAQ says a PDF cannot be attached using Automations and that the option must be enabled directly in the form's settings. Roles overview: Customer Relations Manager can manage contacts, forms and automations, among other things, but cannot export contacts.
    Where to look, or what to do
    Automations in the dashboard, then the automation that sends each form's notification email; in its Send an email action, read the Recipients field (form notifications article). Close without saving.
    What to write down
    Per form: the automation, each recipient (role, collaborator or contact, and whose inbox), whether a PDF copy of each submission is attached and where you found that setting (the automation or the form's settings), and anyone who should no longer receive it.
  11. A11. Backend functions the frontend can call
    What Wix's pages say
    Web modules article: .web.js functions are exposed through web methods set to Anyone, Site Member or Admin, as restrictive as possible; .jsw files are deprecated and keep working. Velo security best practices: anyone who knows an exported function's name can call it with any arguments; a function using suppressAuth must run its own checks or filter out sensitive data, or both. Elevation page: elevated code reachable from outside gives anyone who can call it elevated access.
    Where to look, or what to do
    The backend files, in the Code panel in the editor, where the web modules article says web modules can be created. Read them with the developer who wrote them.
    What to write down
    Per exported function: file, name, permission as set, what it returns, whether it uses suppressAuth or elevation, the check it makes before that (named, or none), and whether any page calls it. Per file: whether a key or other secret is written into it (yes or no; never the value).
  12. A12. Page, public and masterpage.js code
    What Wix's pages say
    Velo security best practices: all page and public code is visible to any visitor, including page code on members-only and password-protected pages; never use API keys in page, public or masterpage.js code; do security checks in backend code, because any check in page, public or masterpage.js code can be read, manipulated and circumvented.
    Where to look, or what to do
    Each page's code and the public files, read with the developer who wrote them.
    What to write down
    Per file: whether it holds a key, token, password, an email address used as a check or another secret (yes or no; never the value), and whether it decides access in the browser.
  13. A13. HTTP functions
    What Wix's pages say
    Custom site APIs article: HTTP functions expose site functionality externally to you or other people, and custom site APIs are only intended for server-to-server communications. HTTP function guide: they live in http-functions.js; its optional step says they expose the site's data and functionality to anyone who calls them and recommends authenticating the caller; one way it gives is retrieving a secret key from the authentication header, using the Secrets Manager.
    Where to look, or what to do
    http-functions.js under Backend & Public, then Backend (HTTP function guide). Read the file with the developer; do not call the endpoints.
    What to write down
    Per function: method and name, what it reads or changes, the outside system that calls it and its owner, and whether it checks a caller secret (yes, no or unsure). Never the secret.
  14. A14. Secrets Manager
    What Wix's pages say
    Secrets Manager page: holds secrets by name, such as API keys, OAuth tokens and environment configuration settings; only site collaborators with the general role of Admin (Co-Owner) or Website Manager have access to it; a transfer moves secrets to the new owner and a duplicate does not get them. Secrets API page: use secret values only in backend code; never call List Secret Info from a .web.js file with anonymous permissions; deleting a secret, or changing its name or value, breaks all code using it.
    Where to look, or what to do
    Ask the developer for the name of each secret the backend code retrieves, from the code read in A11 and A13; secrets are kept in the Secrets Manager section of the site's dashboard (Secrets API page). The pages cited here do not say whether that screen shows values, so this row does not ask you to open it: open no secret, and reveal, edit or delete no value.
    What to write down
    Secret name, the file and function that use it, the service it belongs to, who can open the Secrets Manager (from A2), and any key found in code instead (A12, A13). Never a value.
  15. B1. Make the duplicate and cut its connections
    What Wix's pages say
    Duplicating article: changes to the copy do not affect the live site; Duplicate Site is under the Site Actions icon on the dashboard's Home; not copied are store orders and invoices, contacts and members, email campaigns and triggered emails, settings for third-party apps, Google Operations logs and Secrets Manager secrets, and hidden elements require enabling Velo in the new site; a Studio Editor site a Wix Professional or agency built cannot be duplicated from your account. Coded sites article: code and events are kept in the copy.
    Where to look, or what to do
    Duplicate the live site and name the copy as a test. Check its collections for real records and treat any as live data. List every app, automation, mailing list, HTTP function caller and outside system the copy could reach, and disconnect each on the copy. Point every form automation on the copy at an inbox you control. Limits: a duplicate you made, with your business's domain not connected; change nothing on the live site; no test members, items or attempts until every connection is cut.
    What to write down
    Copy name, date, who made it, what it lacks compared with the live site, real records found, each connection and how it was cut, and the test marker (for example WIXTEST-1114).
  16. B2. Publish the copy and create test members
    What Wix's pages say
    Collection permissions overview: preview runs in the admin role; to act as a member or as everyone, publish the site and visit it signed in as a member or not signed in. Signup settings article: who can join and email confirmation are set in Signup & Login Security.
    Where to look, or what to do
    Publish the copy with your business's domain not connected. Create two test members, Member A and Member B, once each through the copy's own signup form, with invented names carrying the marker and addresses at the inbox you control. If the copy admits only people you approve, approve these two. Give Member A the member role your restricted pages use; leave Member B without it. Limits: only after B1 has cut the copy off from live apps, automations and mailing lists; invented members only, with every email going to the inbox you control; the copy's own signup form in a browser, once per member, with no scripts and no load.
    What to write down
    The copy's address, publish date, the two test members (invented names only), roles given, and the emails the signups produced at your inbox.
  17. B3. Anonymous check (signed out)
    What Wix's pages say
    Velo collaborators page: a hidden page can still be reached by modifying the URL. Velo security best practices: page code on members-only and password-protected pages can be viewed by any visitor. Changing permissions article: "Everyone" lets any visitor access a collection through an API, even if the content is not presented on the live site.
    Where to look, or what to do
    In a private browser window, signed out, open each members-only, role-restricted and hidden page of the copy by its address, with the browser's developer tools open. At most three attempts per page. Send nothing the pages do not send themselves. Limits: only on the duplicate from B1, cut off from live apps, automations and mailing lists; a browser only, with no scripts and no load.
    What to write down
    Per page: what loaded (content, data, code files), whether a secret appeared (yes or no, never its value), and for each collection marked Everyone in A8, which fields the page received.
  18. B4. Member check (Member A, then Member B)
    What Wix's pages say
    Velo security best practices: a visitor's personal information can be stored in a collection provided only the Site member author can read, update or delete it, and its member comments example sets Update and Delete to Site member author. Collection permissions overview: the Item's creator view setting lets members see only items they added.
    Where to look, or what to do
    As Member A, add one invented item carrying the marker through each form or input on the copy that writes to a collection, and note any address the item gets. As Member B, open the lists and pages that show those collections, then Member A's item addresses, and the restricted pages. Where the site shows Member B an edit or delete control on Member A's item, use it once. Limits: only on the duplicate from B1, cut off from live apps, automations and mailing lists; the two invented members and their invented items only, with any email going to the inbox you control; at most three attempts per check; a browser only, with no scripts and no load.
    What to write down
    Per collection and page: what Member B could see, change or delete of Member A's item, and what a member without the role could open, written beside the result your A8 and A7 settings lead you to expect.
  19. B5. Owner check
    What Wix's pages say
    Collection permissions overview: admins keep full access to collections. Form notifications article: the notification email goes to the recipients set in the form's automation, the site owner by default.
    Where to look, or what to do
    As the copy's owner, find each invented item in the CMS and read which fields were stored. Read which emails reached your inbox. Ask each recipient listed in A10 whether anything carrying the marker reached them. Limits: only on the duplicate from B1, cut off from live apps, automations and mailing lists; read only, in a browser, changing nothing in the CMS; no load.
    What to write down
    Where each test item landed and its stored fields, each email received (sender and subject), anything that reached an address outside your inbox, and the owner's decision on each difference from what A6 to A14 led you to expect.
  20. B6. Clean-up
    What Wix's pages say
    Duplicating article: changes made to the copy do not affect the live site, and a copy can be transferred to another account. Terms of Use, section 2.2: you undertake to save and back up your site content regularly and independently.
    Where to look, or what to do
    Remove the test items and test members from the copy, and ask the owner of any other system the marker reached to remove it there. Unpublishing or deleting the copy is the owner's decision. Limits: only on the duplicate from B1; remove only test members and items carrying the marker, never a real record; a browser only, with no scripts and no load.
    What to write down
    Each record carrying the marker, where it was, who removed it and when, and what happened to the copy and who decided.

What Wix runs and what the site owner sets

For Wix website security, start with who runs what.

Wix runs the hosting and the platform. On top of that sit the choices made in your dashboard and editor: who has a role on the site, which apps are installed, what code has been added, who can join as a member, what each CMS collection lets visitors read or write, and where form submissions are emailed.

Those choices shape who can reach your customers' details, and they are what this guide and its matrix cover.

Wix describes its own side in its own pages. Its security measures overview says new sites get HTTPS automatically, that Wix uses TLS 1.2 and above and encrypts users' data at rest with AES-256, that its cloud and public interfaces are automatically scanned for vulnerabilities and misconfigurations on a regular basis, and that its security team and an external third party run penetration tests on the platform on a regular basis.

Wix's page on frontend security says that, for code in the published frontend of sites on Studio Two, Wix Studio and the Wix Editor, Wix restricts what code can do in the browser, and that each installed app receives its own scoped access token, so an app cannot reach another app's token or raise its own permissions. These are Wix's statements about its own controls. This guide does not assess them.

The same overview says Wix users can customise many of their website permissions, and that this varies with the service and features used. Wix's Velo security best practices page says that, in general, Wix takes care of a site's security without the owner having to do anything, and then lists situations where the owner has to take precautions so that sensitive data is not exposed to the site's visitors. Those situations are the subject of most of this page.

What Wix's Terms of Use place with the account owner

Wix's Terms of Use, last revised on 22 October 2026, add the account owner's side of the picture.

These passages map onto the matrix:

  • Section 1.4 lets you invite others to your account and sites and assign them roles and permissions. It says that anyone other than you who accesses your account or site settings, Contributors included, may also perform actions available to you, unless the Wix Services specifically state otherwise, and make changes to your sites and account (for a Contributor, depending on the roles and permissions you assign them), and that all such activities will be deemed to have occurred on your behalf and in your name as the account owner, whether or not you specifically authorised them. Wix strongly encourages keeping your sign-in details confidential and letting only people you trust into the account.
  • Section 1.5 says Wix will consider the owner of a site to be the person or entity whose email address its records list as the owner of the account the site was created under. For an account created directly on Wix's website rather than through a reseller, it says Wix may consider a set of principles to determine ownership, among them who has access to that email address, whose billing details were used where paid services were bought and, when applicable, the registrant of a connected external domain whose registration information is publicly available through ICANN Lookup or Wix's own database.
  • Section 2.1 includes your statement that you have obtained all the consents and permissions applicable laws require for processing, storing, collecting and publishing any personal information that is part of your site content.
  • Section 2.2 includes your undertaking to save and back up your site content, and the information you process regarding your site, including about its end users, regularly and independently.

The order of work this guide takes from them

Your own adviser can say what those clauses mean for your business. This guide takes only an order of work from them: the people who can act in your name come first, then the data your site collects and who can read it.

Collaborators, roles and the Wix account sign-in

Wix's roles overview says Roles and Permissions is reached from Settings in the site's dashboard, and that its Manage Roles page shows each role with a summary of what it grants.

The owner role can change everything and is reassigned only by transferring the site. Admin (Co-Owner) has full access to manage, edit and publish the site, including billing and inviting people, but cannot delete or transfer the site or connect a domain. Website Manager can manage, edit and publish but cannot manage billing, delete, duplicate or transfer the site.

Website Designer and Back Office Manager can both manage settings and apps. Customer Relations Manager can manage contacts, forms and automations, among other things, but cannot export contacts.

Some permissions reach further than their names suggest. Wix's Velo page on working with collaborators says a role with Edit Site permissions gives full access to the site, including its backend files and database collections. Wix's collection permissions overview lists the custom role permissions that give full admin access to every collection: Edit Site in the editor, Edit Code and Edit Site Structure in the Studio Editor, and Access developer tools for Velo.

Wix's 2-step verification page puts the setting in Account Settings in your Wix account, so ask each person with access to the site to check their own. The page lists the Wix app, SMS, an authenticator app and email among the methods you can enable, says a passkey can also be set up, allows more than one method, and says that disabling all your verification methods leaves the account protected by its password alone.

It says Wix remembers a device for 30 days by default, and that a code is asked for only when someone signs in with email and password, not with a social login such as Google or Facebook.

Where several people work on a site, Wix's account security tips page suggests adding them as collaborators rather than sharing a password.

Wix app security: installed apps, API keys and custom code

Wix's developer overview of permissions says permissions are expressed as scopes for apps and API keys, and as roles for Wix users.

An app's scopes are declared in its setup and granted by a Wix user when the app is installed. When an app acts for a Wix user, its permissions are the intersection of its scopes and that user's role. Wix's page on app permissions says that, for an app to be approved on the app market, it must request only the permissions necessary for its functionality.

Wix's help article on accessing apps lists installed apps under Manage Apps in the dashboard.

No Wix page used for this guide names a screen where an owner reviews an app's granted permissions after installation, so the matrix asks you to record what you can find and to write "not found" where you cannot.

API keys are a separate route in. Wix's page on generating one says a key grants admin access to account and site data, is made in the API Keys Manager, and can reach every site in the account or only the sites you select, and that you can also assign a set of permissions that determine the types of APIs each key can access.

The page advises giving each key the narrowest set of sites its integration needs, storing keys securely and using them only in server-side code.

One case the matrix looks for is a key made for an integration that has since been replaced.

Custom code added in site settings

Wix's custom code article, written for the Wix Editor, says snippets are added from Settings in the dashboard, under Custom Code in the Development & integrations section, to every page or to chosen pages, in the head or the body. It says Wix does not support technical issues with third-party snippets, that snippets are tied to a domain and are deleted if a different domain is assigned, and that frontend security measures Wix introduced in December 2025 may block some snippets until their provider updates them.

Wix's frontend security page counts custom code among the code that runs in a site's published frontend.

This guide's advice: list each snippet with the pages it is added to, noting any page with a form, and the host it loads from. Third-party scripts as a wider subject belong to the supply chain attacks guide.

Site members, member roles and pages that are only hidden

Wix's article on signup and login settings puts the choice of who can join under "Who can be a site member?" in Signup & Login Security: everyone, or only people you approve.

It says email confirmation is required by default only for new members already in your contacts, and that a toggle asks everyone who signs up to confirm their email, which Wix recommends. reCAPTCHA can be added to the signup and login forms.

That setting reaches further than the signup form. Wix's Velo security best practices page says that if site members hold permissions on any collection, approving new members automatically is the same as giving those permissions to Anyone, because anyone can now become a member. The matrix therefore joins the signup setting to the collection rows.

Member roles are created in Site Member Access, and Wix's article on creating them says only regular pages set as members only appear in a role's access list, while members area pages and dynamic pages are set in the editor.

Wix's article on page permissions says any site page can be limited to chosen roles from that page's settings in the editor, and its Wix Editor steps go through the page's Settings to the Permissions tab.

A page left out of the menu is a different thing from a restricted one. Wix's Velo page on working with collaborators says a hidden page on a published site can still be reached by modifying the URL. The best practices page adds that the page code of a members-only or password-protected page can be viewed by any visitor, including people without the password who are not members.

So the code behind a restricted page can be read by someone who cannot open the page itself.

CMS collection permissions and what each role can reach

Wix's CMS help article on changing permissions puts a collection's settings under CMS in the dashboard, the More Actions icon next to the collection, then Permissions & privacy, where you choose "Show content", "Collect content" or "Advanced".

"Show content" lets Everyone or Members only view the content. "Collect content" lets visitors add items but not change existing ones, with a separate choice of who can view them. "Advanced" sets view, add, update and delete for each role, including Item's creator. Wix's overview says admins keep full access whatever the setting.

Wix's overview says that, depending on the permissions applied, collection content can still be accessed when it does not appear on the live site, and that while dataset settings affect what can be done on a page, only collection permissions can actually limit the operations each role can perform.

Its article on changing permissions says that "Everyone" lets any site visitor access the collection through an API even if the content is not presented on the live site, and that encrypting a personal information field protects how the data is stored but does not control who can view it. So what a page shows is not what limits the data.

The Velo security best practices page gives the working rules for custom collections. Where a collection holds sensitive data such as personal information or secrets, Read should be granted to the Admin role only, unless there is a reason to grant it to more roles.

A malicious visitor can still add data to a collection whose create permission is Anyone, even with no form on the site, and can still read an internal collection whose read permission is Anyone. Personal information can be stored in a collection provided only the Site member author can read, update or delete it.

For an input form anyone can use, the page's example sets Create to Anyone and Read, Update and Delete to Admin.

Know these limits before you plan roles. The best practices page, read on 14 November 2026, says custom roles for site members cannot be used to set collection permissions, and that to give only members with a certain role access, the collection is set to Admin and backend code suppresses the permission check for members with that role.

The CMS overview's advanced permissions accept specific collaborator roles with CMS access, which are roles for collaborators, not for site members. Collections that come from Wix's own apps work differently: Wix's page on app collections says their permissions cannot be changed and can be read with View permissions in the CMS, and that code performing data operations can override those restrictions. The broken access control guide covers why a check on the server matters in general.

Wix Forms: who receives each submission

Wix's article on form notifications says that, by default, a submission sends an email to the site owner, and that this notification is built with Wix Automations.

It says the automation can be edited to choose who gets notified, the site owner or other collaborators, and to add more email addresses. People who are not collaborators can be notified once they are added as contacts on the site, and the article's note says site collaborators must be assigned Wix Inbox permissions.

The recipients are read from Automations in the dashboard: the form's automation, the Send an email action, Show additional settings, then Recipients.

On PDF copies, the article's section on email notifications says the automation can be edited to include PDF attachments of form submissions. Its FAQ says a PDF of the form submission cannot be attached using Automations, and that to include a PDF copy of each submission in notification emails, the option must be enabled directly in the form's settings.

This guide's advice: treat each recipient as holding a copy of every submission the automation emails them, and look in particular for a former staff member or a contact added for an old campaign. The matrix lists each form's recipients and asks whether each still needs the data. The sensitive data exposure guide covers which fields a form should collect at all.

Velo code: what visitors can read and what they can call

Sites with Velo code add a developer's code on top of those settings.

Wix's Velo security best practices page says all page and public code is visible to any site visitor, warns against putting sensitive information in it, including in the masterpage.js file, and says any check or validation in page, public or masterpage.js code can be read, manipulated and circumvented by a malicious visitor.

Backend code is not visible to visitors, but the page says a visitor who knows an exported backend function's name can call it with any arguments and examine what it returns, so exported backend code should perform validations before carrying out potentially harmful operations or returning sensitive information.

It adds that backend functions not called from public code should not be exported from .web.js or .jsw files.

Wix's article on web modules says a function in a .web.js file is exposed through a web method that checks the caller against the permission set on it: Anyone, meaning any site visitor; Site Member, meaning logged-in site members; or Admin, meaning logged-in site owners and collaborators.

It says to set each one as restrictively as possible, especially when a function passes sensitive data to the frontend or needs elevation.

Web modules made as .jsw files are deprecated, and the article says existing ones keep working. Wix's webMethod() reference adds that web methods must be defined in files with a .web.js extension.

HTTP functions are exposed to anyone who calls them

Wix's article on custom site APIs says HTTP functions expose a site's functionality externally, so that you or other people can call them, and that custom site APIs are only intended for server-to-server communications. Its examples include connecting an automation tool and receiving notifications from external webhooks.

Wix's guide to writing an HTTP function places them in a file called http-functions.js in the site's backend folder. In a step it marks as optional, the guide says HTTP functions expose the site's data and functionality to anyone who calls them and recommends authenticating the caller.

One way it gives is retrieving a secret key from the authentication header in the request, using the Secrets Manager. Whether each of your functions makes that check is something the matrix asks the developer to show you in the code.

Backend code that skips the permission check

The best practices page says many Wix Data functions accept a suppressAuth option. Wix's collection permissions overview says setting it makes the call without checking whether the current user has permission, and that only backend code can do it. The best practices page says a function that does this must do at least one of the following: run its own checks before reaching the collection, or filter sensitive data out before passing anything back to the frontend.

It gives the reason that anyone can call exported backend code, and says to suppress permission checks only when absolutely necessary.

Elevation works in a related way. Wix's developer page on elevation says it lets a call run with higher authorisation than the identity making the call has, where supported, and that when backend code that elevates is reachable from outside, anyone who can call it gets elevated access, so callers must be properly authorised before the elevation runs.

Wix's Data Collections API page, on the restricted functions that run only when elevated, warns that elevating a function allows it to be called by any site visitor.

Put those pages side by side: the web modules article says a web method set to Anyone can be called on behalf of any site visitor, and the best practices page says suppressAuth lets a backend data request reach a collection even when the visitor asking has no permission for it.

This guide's advice is to record, for each such function, the check it makes before the unchecked or elevated call and what it returns.

Wix Secrets Manager: keys belong in the backend

Wix's page on the Secrets Manager says it stores sensitive values used in a site's code, such as API keys, OAuth tokens and environment configuration settings, under names that code uses to retrieve them.

It says only site collaborators with the general role of Admin (Co-Owner) or Website Manager have access to it, that transferring a site moves its secrets to the new owner, and that duplicating a site does not copy them. The best practices page says a key for a third-party service should always be stored there and never placed in page, public or masterpage.js code.

Wix's Secrets API page says to use secret values only in backend code, and that calling List Secret Info from a .web.js file with anonymous permissions is a serious security risk that exposes secrets to potential leaks. It says to call it from a separate .js file instead, or, if it must sit in a .web.js file, to set the function's permission to Admin.

It also says deleting a secret, or changing its name or value, breaks all code that uses it.

That is one reason the matrix records secrets by name and leaves every change to the owner. If a key has already appeared somewhere it should not, the secrets exposure guide covers what to do next.

How to fill in the access matrix

The matrix works as a Wix security checklist with room for what you found.

Copy it into a spreadsheet and keep one copy per site. Rows A1 to A14 are readings of the live site's dashboard, editor and code, except that A4 and A14 ask the person who made each key or secret and open no screen. Rows B1 to B6 are the anonymous, member and owner checks. They act on a duplicate site only, within the limits set out in the next section.

  • Part A changes nothing. Open each screen the third column names, read the setting, and close it without saving. Nothing in Part A installs or removes an app, edits a role or collection, publishes the site or calls a function.
  • Names, never values. Record that a key, token or secret exists, its name and what uses it. Never copy a secret, API key, password or verification code into the matrix, and never reveal a value just to check it is still there.
  • Where a row looks at code or a collection that might hold a secret or personal information, record only whether it is present (yes, no or unsure), never the value or the record.
  • Read the code rows with whoever wrote the code. They can show you each exported function, its permission and the check it makes.
  • The third column names a screen only where a Wix page gives one, and the second column says which page. Where no Wix page gives a location, the row names what to read and you find it.
  • Put a date on each row. Fill the matrix in again when an app or a form is added, the code or the design changes, or someone with access leaves. The Wix pages behind the second column were read on 14 November 2026.

Anonymous, member and owner checks on a duplicate site

Settings show what was intended.

Using the site as a stranger, as a member and as the owner shows what each one can reach. Part B does that on a copy, so the checks run away from the live site and real customers. Wix's article on duplicating a site says changes to the copy do not affect the live site.

It lists what is not copied: store orders and invoices, contacts and members, email campaigns and triggered emails, settings for third-party apps, Google Operations logs, and secrets stored in the Secrets Manager, and it notes that any hidden elements require enabling Velo in the new site. Wix's Velo article on coded sites says code and events are kept in the new copy.

Collection content is not on Wix's list of things left behind, so treat any real records you find in the copy as live data before you begin. A copy also keeps its code without its secrets, so backend code that reads a secret may fail or behave differently there; record which.

This page's own caution: the duplicate may still be connected to live apps, automations or mailing lists until you disconnect them, so B1 lists every connection and cuts it on the copy first.

The copy has to be published for the checks to mean anything. Wix's collection permissions overview says preview runs in the admin role, and that to act as another kind of user you publish the site and visit it signed in as a member or not signed in at all.

  • Only on a duplicate you made, never the live site, and never with your business's domain connected to it.
  • Invented records only, each carrying a marker such as WIXTEST-1114, and no real person's details.
  • Every email address used goes to an inbox you control. Change each form automation's recipients on the copy to that inbox before any check.
  • At most two test member accounts, one invented item per member for each collection under check, and no more than three attempts at any single check.
  • Ordinary use of the duplicate's own pages in a browser. No scanners, no scripts, no load and no requests the pages do not send themselves.
  • Read section 2.3 of Wix's Terms of Use, quoted below, before running Part B, and where in doubt, ask Wix in writing first.

Where a review of your own Wix site stops

What the matrix captures is your settings, your code and where your data goes, as they stood on the day you filled it in.

These sit outside it:

  • Wix's own systems, its staff's access and its audits. Wix's security measures overview is where Wix describes its own controls.
  • What an installed app or a third-party snippet does on its developer's side. The matrix records what each was given or loads, not what happens next.
  • Copies already made: forwarded notification emails, exported contacts and anything an app or HTTP function caller has stored.
  • Whether a key, token or secret has already been copied somewhere. The matrix shows where each one is meant to be.
  • Anything the duplicate lacks. Apps whose settings were not copied, missing secrets and the connections you cut can each make the copy behave differently from the live site.
  • How a backend function behaves when it is sent arguments the site's own pages never send. Part B uses the site as a visitor would, and stops there.
  • Anything changed after the date written on each row.

Wix's Terms of Use on probing, scanning and testing

Before any testing tool is pointed at a site Wix hosts, read Wix's Terms of Use as they stand that day.

In the version last revised on 22 October 2026, section 2.3 lists things you agree and undertake not to do. They include disabling, circumventing, bypassing or otherwise avoiding any measures used to prevent or restrict access to the Wix Services, a User Platform, another User's account or any other systems or networks connected to the Wix Services, by hacking, password mining or other illegitimate or prohibited means; probing, scanning or testing the vulnerability of the Wix Services or any network connected to them; any action that imposes an unreasonable or disproportionately large load on the infrastructure of the Wix Services or Wix's systems or networks connected to them, or otherwise interferes with or disrupts the operation of any of the Wix Services or the servers or networks that host them or make them available, or disobeys any requirements, procedures, policies or regulations of those servers or networks; and accessing Wix Services, User Accounts, Licensed Content or User Content through any means or technology, such as scraping and crawling, other than Wix's publicly supported interfaces.

The section says failing to abide by them may result in the immediate termination of the account or of the services provided.

Section 1.2 says the Wix Services, as the Terms define them, do not include services, applications, features or components built, developed, connected or offered by a Wix User, even if presented on the Wix Website or the Wix App.

This page makes no statement about how those clauses apply to checks on your own site or its duplicate. Part A of the matrix reads settings and code. Part B uses a duplicate through its own pages within the limits above. Before anything more active, such as a scan or a penetration test of a site on Wix, get Wix's answer in writing and keep it with its date.

If you believe you have found a security issue or vulnerability, Wix's Reporting a Security Issue page asks you to contact the Wix Security team through its security contact page, and asks security researchers to send reports for its Bug Bounty program to bugbounty@wix.com.

It gives XSS and CSRF attacks, SQL injection, DNS hijacking, session vulnerabilities, an unsecured API and authentication spoofing as examples of what security issues or vulnerabilities may include.

Wix's security measures overview says Wix maintains a security bug bounty program that gives independent security researchers a platform for testing and submitting vulnerability reports. The terms of that program are not summarised here.

Wix sites and Clever Ops

This guide describes no Clever Ops service for Wix sites, and Wix's platform is not something Clever Ops tests.

Under the Clever Ops methodology a host's platform sits outside the method, and a service run by another business is excluded unless that business agrees. The matrix is informational, for the site owner, the developer who looks after the site or another provider to use.

A Wix site may send data to, or take data from, an application of yours that has its own sign-in for customers or staff, such as a system that calls the site's HTTP functions. That application, and not the Wix site, is what a scoped web application and API penetration test covers: the tester holds an account in each role to see what that role can view and alter, and sends requests to the API itself as well as through the interface.

The methodology reads each target's hosting provider testing policy before a request goes out, since some hosts want notice or written approval first.

Should Clever Ops have built or be hosting that application, the same work is called a security review instead of an independent test, and the report records who built it and who hosts it.

Clever Ops sells neither monitoring around the clock nor emergency incident response. If someone has taken over a Wix account, Wix's Reporting a Security Issue page says to fill out the Wix Account Recovery form. If you think an account, an app or a key is being misused now, bring in an incident response specialist as well.

Frequently asked questions

Wix's security measures overview describes its own controls, among them HTTPS on new sites, TLS 1.2 and above, AES-256 encryption of data at rest, regular automated vulnerability scanning of its cloud and public interfaces, and penetration tests by its own team and an external third party. This guide gives no verdict. Wix's Velo security best practices page names situations where the owner has to take precautions, such as collection permissions, exported backend functions and keys in page code, and section 1.4 of Wix's Terms of Use says activities by anyone other than you who gets into your account or site settings, invited Contributors included, are deemed to have occurred on your behalf.

Some of it. Wix's Velo security best practices page says all page and public code is visible to any site visitor, including page code on members-only and password-protected pages, and warns against putting sensitive information in it, masterpage.js included. Backend code is not visible, but the same page says a visitor who knows an exported backend function's name can call it with any arguments and examine what it returns. Wix's article on web modules says each web method is set to Anyone, Site Member or Admin.

Whoever the collection's permissions allow, whether or not a page shows the data. Wix's article on changing collection permissions says setting a collection to "Everyone" lets any site visitor access it through an API even if the content is not presented on the live site, and that encrypting a personal information field does not control who can view it. Wix's overview says admins always keep full access.

No, according to Wix's article on duplicating a site, which lists contacts and members, store orders and invoices, email campaigns and triggered emails, settings for third-party apps and Secrets Manager secrets among the content not copied. Wix's Velo article on coded sites says the code and events are kept in the copy. Collection content is not on the not-copied list, so check a duplicate for real records before using it for tests.

By default, the site owner. Wix's article on form notifications says the email is built with Wix Automations, and that the automation can be edited to notify other collaborators and more email addresses, with people who are not collaborators added as contacts first. The recipients are under Automations in the dashboard, in the Send an email action of the form's automation.

Read Wix's Terms of Use first. In the version last revised on 22 October 2026, section 2.3 says you agree not to probe, scan or test the vulnerability of the Wix Services or any network connected to them, or to take any action that imposes an unreasonable or disproportionately large load on the infrastructure of the Wix Services or Wix's systems or networks connected to them, or otherwise interferes with or disrupts their operation. This page makes no statement about how that applies to your own site, so get Wix's answer in writing first. Wix's Reporting a Security Issue page gives bugbounty@wix.com for researchers' vulnerability reports.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.